...
Framework to provide restful services of lcm for VNF resources;
OpenStack API pass-through/proxy functions;
Support Multi VIM/Cloud Function and API list for R1
Integration with ESR/ A&AI/ESR, SO, APP-C, DCAE, and VF-C;, and SO.
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.
...
Indicate at a high level the longer term roadmap. This is to put things into the big perspective.
Define integration models with other components
Define model for Cloud resources/capabilities/EPAUltimately, the team would like to have all these components, SO, APP-C, VF-C, DCAE, SDN-C, to take advantage of a common API layer. The complete design of the common API layer is likely to be realized through the course of a few ONAP releases, and could involve code refactoring amongst some or all of these components. The plan is to work with all these teams to make sure the approach has been fully vetted and the transition does not break their functionality.
Release Deliverables
Indicate the outcome (Executable, Source Code, Library, API description, Tool, Documentation, Release Note...) of this release.
Deliverable Name | Deliverable Description |
framework | To fill outTo fill outprovide restful services mentioned above |
| VIM VES agent | To emit VIM Fcaps data |
| Keystone proxy module | For compatibility with vanilla OpenStack |
Sub-Components
List all sub-components part of this release.
Activities related to sub-component must be in sync with the overall release.
Sub-components are repositories are consolidate in a single centralized place. Edit the Release Components name for your project in the centralized page.
...
List the other ONAP projects your depends on.
Consumers of Multi-VIM/Cloud – SO, SDNA&AI/ESR, APP-C, APP-CDCAE, VF-C, DCAEProducers for Multi-VIM/Cloud – DCAE, A&AIand SO for API design and integration
Architecture
High level architecture diagram
...
List the API this release is expecting from other releases.
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.
API Name | API Description | API Definition Date | API Delivery date | API Definition link (i.e.swagger) |
To fill out
Compatible API |
Date for which the API is reviewed and agreed
To fill out
for compatibility with vanilla OpenStack and VF-C |
API Outgoing Dependencies
...
API Name | API Description | API Definition Date | API Delivery date | API Definition link (i.e.swagger) | |||||
Common API | Approach to drive common API |
| To fill out | High level description of the API | Date for which the API is reviewed and agreed | To fill out | Link toward the detailed API description |
Third Party Products Dependencies
...