...
What is this release trying to address?
The VF-C Beijing Casablanca release has following primary objectives:
1. Improving platform maturity:enhance scalability, manageability,security,etcsecurity (i.e., S3P items)
2. Supporting use cases identified by ONAP and integration: VoLTE, vCPE,
3. Supporting Functional Requirements identified: HPA, Centralized Representation and Consistent Identification of Cloud Regions In ONAP
34. Enhancement to VF-C existing features; :
Integration with OOF 4. OOF, AAF(Strech goal)
R3 tosca data model alignment
ETSI Interface alignment(Depend on resource contribution)
Use Cases
Describe the use case this release is targeted for (better if reference to customer use case).
Use Case: Residential Broadband vCPE (Approved)
Functional Requirements:
Hardware Platform Enablement In ONAP
Centralized Representation and Consistent Identification of Cloud Regions In ONAP
VNF Auto Scaling - stretch goal
...
LCM(instantiate/terminate) for open source VNFs
Minimum VF-C components supporting above functionalities:
NSLCM/Catalog/GVNFM/Vimproxy/EMS driver/vendor VNFM driver
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.
...
Sub-components are repositories and are consolidated in a single centralized place. Edit the Release Components name for your project in the centralized page.
...
TBD (add new R3 arch diagram with new components and interface)
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
...
| Area | Actual Level | Targeted Level for current Release | How, Evidences | Comments | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Performance | 0 | 11 |
|
| ||||||||||
| Stability | 1 | 2 | Need to do a 72 hours soak test for VF-C
|
| ||||||||||
| Resiliency | 2 | 2 | In Casablanca we will split all VF-C DBs into a single container, so plan to support Resiliency at the DB level
|
| ||||||||||
| Security | 1 | 1+ | Partial Need to know more clarification about the security level definitiion. There are still false positives and third party issues reported in NexusIQ; We will continute to solve critical issues first and then address medium issues.
|
| ||||||||||
| Scalability | 0 | 1 | Will split DBs from current VF-C components. So that VF-C components can scale in signle site
|
| ||||||||||
| Manageability | 1 | 1+ | Patial Need to know more clarification about manageablitilly level2 But we will update log format to compile log specification
|
| ||||||||||
| Usability | 1 | 1+ | APIs documentation update
|
|
...
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.
...
| 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
...