...
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.
...
Jira server ONAP JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery key in (MODELING-144,MODELING-140,MODELING-139,MODELING-138,MODELING-137,MODELING-136,MODELING-132,MODELING-131,MODELING-130,MODELING-129,MODELING-128,MODELING-127,MODELING-120,MODELING-119,MODELING-118,MODELING-117) serverId 425b2b0a-557c-3c0c-b515-579789cceedb
Longer term roadmap
Indicate at a high level the longer term roadmap. This is to put things into the big perspective.deliver micro service based parser for other projects in ONAP to use
Release Deliverables
Indicate the outcome (Executable, Source Code, Library, API description, Tool, Documentation, Release Note...) of this release.
| Deliverable Name | Deliverable Description | To fill out | To fill out|
|---|---|---|---|
| Microservice Parser | TOSCA Parser based on Microservice | ||
| 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
List all sub-components part of this release.
Activities related to sub-components must be in sync with the overall 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.
...
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 |
|
...
| API Name | API Description | API Definition Date | API Delivery date | API Definition link (i.e.swagger) | ||
|---|---|---|---|---|---|---|
| Parser Microservice API | Parser Microservice 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 |
...
| Jira | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
...
| 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
...