...
| Project Name | Enter the name of the project |
|---|---|
| Target Release Name | Enter the name of the release you are targeting to deliverCasablanca Release |
| Project Lifecycle State | Either Incubation, Core, Mature. Refer to ONAP Charter, section 3.3 Project Lifecycle for further information |
| Participating Company List | the company participating in this release. At least 3-4 organizations, including an operator are recommended.AT&T, Amdocs, Nokia |
Scope
What is this release trying to address?
...
- S3P improvements
- VNF Scaling enhancements
- Scheduling capabilites
- PNF support
Use Cases
Describe VID will continue supporting the use case this release is targeted for (better if reference to customer use case).
Minimum Viable Product
...
following use case:
Use Case: Residential Broadband vCPE (Approved)
Use Case Proposal - VNF Scale Out
And will add support to the following:
Centralized Representation and Consistent Identification of Cloud Regions In ONAP
Change Management Extensions (partially)
Deployment of the hybrid 5G Network (PNF/VNF)
Minimum Viable Product
- Instantiation of service, vnfs and vf modules
- change management support
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 project=sanbox VID and issuetype in (epic) serverId 425b2b0a-557c-3c0c-b515-579789cceedb
...
Jira server ONAP JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery project=sanbox VID and issuetype in (story) serverId 425b2b0a-557c-3c0c-b515-579789cceedb
Longer term roadmap
...
- Fully automated deployment of new VNFs without the need of manual intervention or configuration.
- Support workflows for change management by using the SDC as a provider of workflows capabilities
- Dashboarding scheduled and ongoing change management
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
|---|---|---|
| VID application | Executable, Docker | |
| MariaDB | SQL database scheme | |
| Release documentation | ReadTheDocs, ONAP WIKI pages |
Sub-Components
List all sub-components part of this release.
Activities related to sub-components must be in sync with the overall release.
...
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 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.
VID (Dashboard OA&M) is a run-time component as appear in the diagram:
VID dependencies diagram:
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 | 1 | 1 |
| |
| Stability | 1 | 2 |
| |
| Resiliency | 2 | 2 |
| |
| Security | 1 | 1 |
| |
| Scalability | 1 | 1 |
| |
| Manageability | 1 | 1 |
| |
| Usability | 1 | 1 |
|
...
| API Name | API Description | API Definition Date | API Delivery date | API Definition link (i.e.swagger) | |||||
|---|---|---|---|---|---|---|---|---|---|
| TBD | TBD | TBD | TBD | TBD | 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 |
API Outgoing Dependencies
...
| API Name | API Description | API Definition Date | API Delivery date | API Definition link (i.e.swagger) | |||||
|---|---|---|---|---|---|---|---|---|---|
| NA | NA | NA | NA | NA | 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
Third Party Products mean products that are mandatory to provide services for your components. Development of new functionality in third party product may or not be expected.
List the Third Party Products (OpenStack, ODL, RabbitMQ, ElasticSearch,Crystal Reports, ...).
| Name | Description | Version | To fill out | To fill out | To fill out|
|---|---|---|---|---|---|
| Docker | Docker container host | Latest one | |||
| MariaDB | SQL DB | 10.1.11 |
In case there are specific dependencies (Centos 7 vs Ubuntu 16. Etc.) list them as well.
...
Describe the plan to integrate and test the release deliverables within the overall ONAP system.
Confirm that resources have been allocated to perform such activities.
- Unit tests are run automatically as part of every code merge.
- Once the final Docker image is compiled, it will be installed onto a Docker host and will be checked to ensure no errors occur during start-up.
- Functional testing will occur to ensure that the use cases are functioning correctly.
Gaps
This section is used to document a limitation on a functionality or platform support. We are currently aware of this limitation and it will be delivered in a future Release.
List identified release gaps (if any), and its impact.
...
| Jira | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
...