...
| 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
- PNF support
- Scheduling capabilites (stretch goal)
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
Describe the MVP for this release.following use case:
Use Case: Residential Broadband vCPE (Approved)
Use Case Proposal - VNF Scale Out
And will add support to the following:
Deployment of the hybrid 5G Network (PNF/VNF)
Change Management Extensions (best effort)
Centralized Representation and Consistent Identification of Cloud Regions In ONAP (best effort)
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 Legacy server System Jira columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery project=sanbox VID and issuetype in (epic) and fixversion="Casablanca Release" serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
...
Jira Legacy server System Jira columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery project=sanbox VID and issuetype in (story) and fixversion="Casablanca Release" serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
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.
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 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
...
| Area | Actual Level | Targeted Level for current Release | How, Evidences | Comments | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Performance | 0 | 0 |
| |||||||||||||
| Stability | 1 | 2 |
| |||||||||||||
| Resiliency | 2 | 2 |
| |||||||||||||
| Security | 1 | 1 | Reaching 100% for CII passing badge; Switch to HTTPS; Integrate with AAF
|
| ||||||||||||
| Scalability | 1 | 1 |
| |||||||||||||
| Manageability | 1 | 1(with logiing v1.2 spec support) |
|
| ||||||||||||
| 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 API | Date for which the API is reviewed and agreed | To fill out |
|---|---|---|---|---|---|---|---|---|
| Link toward the detailed API descriptionScale out (endpoint TBD) | SO API for VNF scale out | TBD | TBD | TBD | ||||
| Service instantiation - /ecomp/mso/infra/serviceInstances/v6 | SO API for service instantiation with PNF support | TBD | TBD | TBD |
API Outgoing Dependencies
...
| API Name | API Description | API Definition Date | API Delivery date | API Definition link (i.e.swagger) | ||||
|---|---|---|---|---|---|---|---|---|
| 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 descriptionNA | NA | NA | NA | NA |
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 Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
...
| 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
...