...
1) Microservice based TOSCA Parser with Catalogue
Use Cases
vCPE, VoLTE, CCVPN.
Minimum Viable Product
Microservice based API availableof generic TOSCA Parser
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.
...
| Deliverable Name | Deliverable Description |
|---|---|
| Microservice Parser | TOSCA Parser based on Microservice with catalogue |
| NFV Parser | Python based parser, will keep R2 release as it is |
| Javatoscachecker | Java based TOSCA checker, will keep R2 release as it is |
| Modelspec | modeling subcommitee specification publication |
...
Sub-components are repositories and are consolidated in a single centralized place. Edit the Release Components name for your project in the centralized page.
...
High level architecture diagram
At that stage within the Release, the team is expected to provide more Architecture details describing how the functional modules are interacting.
Indicate where your project fit within the Modeling project provide Parser tool in ONAP Archiecture diagram.
Block and sequence diagrams showing relation within the project as well as relation with external components are expected.
Anyone reading this section should have a good understanding of all the interacting modules.
Platform Maturity
Refering to CII Badging Security Program and Platform Maturity Requirements, fill out the table below by indicating the actual level , the targeted level for the current release and the evidences on how you plan to achieve the targeted level.
| Area | Actual Level | Targeted Level for current Release | How, Evidences | Comments |
|---|---|---|---|---|
| Performance | 0 | 0 |
| |
| Stability | 1 | 1 |
| |
| Resiliency | 1 | 1 |
| |
| Security | 1 | 1 |
| |
| Scalability | 1 | 1 |
| |
| Manageability | 0 | 0 |
| |
| Usability | 1 | 1 |
|
...
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) | |
|---|---|---|---|---|---|
| To fill out | High level description of the APIParser Microservice API | Parser Microservice api | Date for which the API is reviewed and agreed | To fill out | Link toward the detailed API description |
...
| Risk identified | Mitigation Plan | Contingency Plan |
|---|---|---|
| To fill out | To fill out | To fill out |
Resources
Fill out the Resources Committed to the Release centralized page.
Release Milestone
...