...
1 Event/Alert/Metrics federation (S3p)
2 Elastic API exposure (Towards model-driven)
3 Parallelism improvement of Multi Cloud Services (S3p)Services
4 Logging Enablement (S3p)Enabling
5 Image service (Function enhancement)
6 Clustering service interfaces for query and placement of a group of resources (Function enhancement)
7 HPA resource discovery and representation for HPA awareness orchestration (Function enhancement)
Functionalities
List the functionalities that this release is committing to deliver by providing a link to JIRA Epics and Stories. In the JIRA Priority field, specify the priority (either High, Medium, Low). The priority will be used in case de-scoping is required. Don't assign High priority to all functionalities.
...
Sub-components are repositories and are consolidated in a single centralized place. Edit the Release Components name for your project in the centralized page.
...
Please refer to below graph for a high level project scope architecture. the Fcaps part will involve data collection and event/metrics/alerts federation part as below graph.
Please refer to below chart for the even-driven framework.
...
List the API this project is expecting from other projects.
Prior to Release Planning review, Team Leads must agreed on the date by which the API will be fully defined. The API Delivery date must not be later than the release API Freeze date.
Prior to the delivery date, it is a good practice to organize an API review with the API consumers.
...
| Risk identified | Mitigation Plan | Contingency Plan |
|---|---|---|
| APPC event integration | keep the existing way | work together on vm polling part of code |
| OOF event integration | keep the existing way | work together on Clustering query and resource graphs update |
| DCAE integration | keep the existing way | identify examples of alert/metrics |
| AAI integration | keep the existing way | identify examples of HPA |
Resources
Fill out the Resources Committed to the Release centralized page.
Release Milestone
...