...
| Project Name | Enter the name of the project |
|---|---|
| Multi VIM/Cloud | Beijing |
| Project Lifecycle State | CoreIncubation |
| Participating Company | Amdocs, AT&T, ChinaMobile, Huawei, Intel, Lumina Networks, Microsoft, Mirantis, VMware, WindRiver, ZTE |
...
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)
5 Standardized Infrastructure Resource Information Model (Towards model-driven)
6 FCAPS modeling (Towards model-driven)
7 Image service (Function enhancement)
Enabling
5 Image service
6 8 Clustering service interfaces for query and placement of a group of resources (Function enhancement)
9 7 HPA resource discovery and representation for HPA awareness orchestration (Function enhancement)10 TOSCA-based orchestration to deploy workload on multiple clouds
11 MultiCloud Plugin for K8S (Function enhancement)
12 MultiCloud support for Azure (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.
...
Functionality Name | In or Out | Priority | Stretch |
| Logging Integration | In | HM | Integrate with Logging |
A&AI -Image Manager Integration | In | HM | Integrate with A&AI - on Image Manager and Resource Modeling |
| OOF | In | H | Integrate with OOF |
| VFC | In | H | Integrate with VFC on VM status part |
| APPC | In | H | Integrate with APPC on VM status part |
| DCAESO | inIn | H | Integrate with DCAE on Alert/Metrics partSO on parser adapter |
Epics
Jira server ONAP JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery project = MULTICLOUD AND issuetype = Epic AND fixVersion = "Beijing Release" serverId 425b2b0a-557c-3c0c-b515-579789cceedb
...
This release we targeted to implement MVP features and finish regression of all existing use cases. The longer goal is to intergate with different dependent modules to consume the advanced features.
1 Standardized Infrastructure Resource Information Model (Towards model-driven)
2 FCAPS modeling (Towards model-driven)
3 TOSCA-based orchestration to deploy workload on multiple clouds (Towards model-driven)
4 MultiCloud support for Azure (Function enhancement)
Release Deliverables
Indicate the outcome (Executable, Source Code, Library, API description, Tool, Documentation, Release Note...) of this release.
...
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.
...
Prior to the delivery date, it is a good practice to organize an API review with the API consumers.
| API Name | API Description | API Definition Date | API Delivery date | API Definition link (i.e.swagger) |
|---|
Clustering placement/query
Query capacity and status for a group of resources
Message bus pub/sub
Publish and subscribe events/notification
Resource Hierarchy graph
Traverse resource Hierarchy in given Cloud
Container operation
Operate containers
Azure API | southbound API deisgn |
API Outgoing Dependencies
API this project is delivering to other projects.
| API Name | API Description | API Definition Date | API Delivery date | API Definition link (i.e.swagger) |
|---|
Clustering placement/query | Query capacity and status for a group of resources | |||
Message bus pub/sub | Publish and subscribe events/notification | |||
Resource Hierarchy graphs | Traverse resource Hierarchy in given Cloud | |||
| VIM query | Query available VIMs | |||
Image upload/download | Support upload and download images |
Third Party Products Dependencies
Third Party Products mean products that are mandatory to provide services for your components. Development of new functionality in third party product may or not be expected.
List the Third Party Products (OpenStack, ODL, RabbitMQ, ElasticSearch,Crystal Reports, ...).
| Name | Description | Version |
|---|---|---|
| SO Parser Adapter in SO | Translate Tosca template into VIM function description |
...
| Risk identified | Mitigation Plan | Contingency Plan |
|---|---|---|
| APPC event integration | keep the existing way | work together on vm polling part of code |
| VFC OOF event integration | keep the existing way | work together on vm polling part of codeClustering 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
...