...
Sub-components are repositories and are consolidated in a single centralized place. Edit the Release Components name for your project in the centralized page.
...
Indicate where your project fit within the ONAP Architecture diagram.
Block and sequence diagrams showing relation within the project as well as relation with external components are expected.
...
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.
API Name | API Description | API Definition Date | API Delivery date | API Definition link (i.e.swagger) |
Portal Platform API | API for integration of portal applications | |||
Catalog API (SDC) | API to read the NS and VNF Catalog | |||
SO API(Modeling) | API for NS instantiation and termination | |||
MSB API | API for registration and use of micro-services bus | |||
A&AI API | API for getting inventory and image management | |||
VF-C API | API for NS instantiation and termination | |||
DataLake API | API for FCAPS (VNF/VM monitoring) | |||
External API | API for external data |
...
Please update any risk on the centralized wiki page - London Risks
Resources
Fill out the Resources Committed to the Release centralized page.
Release Milestone
The milestones are defined at the Release Planning: London and all the supporting project agreed to comply with these dates.
...
Each project must edit its project table available at Project FOSS.
Charter Compliance
The project team comply with the ONAP Charter.