...
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
...
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
...
Sub-components are repositories are consolidate in a single centralized place. Edit the Release Components name for your project in the centralized page.
...
What is currently available is documented in the APPC User Guide. This document will be updated as part of the project.
...
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) |
|---|---|---|---|---|
| SDC | REST API | TBD | TBD | Link toward the detailed API description |
| AAI | REST API | 8/23/17 | 8/23/17 | |
| MultiVIM | REST API | 8/23/17 | 8/23/17 | |
| CCSDK | OpenDayLight, SLI, and AAI Client | 8/23/17 | 8/23/17 | |
| DMaaP | API ti publish/subscribe to events sent for VNF/VM action requests. | 8/23/17 | 8/23/17 | DMaaP API |
API Outgoing Dependencies
...
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
...
Resources
Fill out and provide a link toward the Resources Committed to the Release centralized page.
Release Milestone
The milestones are defined at the Release Level and all the supporting project agreed to comply with these dates.
...
The project team comply with the ONAP Charter.
Release Key Facts
Fill out and provide a link toward the centralized Release Artifacts.