...
| Project Name | Enter the name of the project |
|---|---|
| Target Release Name | CasablancaDublin |
| Project Lifecycle State | Incubation |
| Participating Company | China Mobile ,ZTE, Huawei, Nokia ,VMware, Boco, Jio, raisecom, Intel, Intel verizon |
What is this release trying to address?
The VF-C Casablanca release C Dublin release has following primary objectives:
...
2. Supporting use cases identified by ONAP and integration: VoLTE, vCPE, CCVPN
3. Supporting Functional Requirements identified: HPA, Centralized Representation and Consistent Identification of Cloud Regions In ONAP
4. Enhancement to VF-C existing features:
Integration with OOF, AAF(Strech goal)OOF integration improvement
ETSI Interface alignment(Including SOL005 and SOL003, how much alignment depends on resource contribution)
VF-C workflow optimization
NS instance model mapping to A&AI
R4 R3 tosca data model alignment
5. External Cooperation
ETSI Interface alignment Cooperate with Integration team to add tosca-based VNF deployment functional tests.(Depend on the commit resource contribution )
Participate in Generic tosca parser requirment analysis and API design
Use Cases
Describe the use case this release is targeted for (better if reference to customer use case).
Use Case: VoLTEResidential Broadband vCPE (approvedApproved)
CCVPN Use Case : Residential Broadband vCPE (ApprovedDublin)
Functional Requirements:
Hardware Platform Enablement In ONAP
...
Minimum VF-C components supporting above functionalities:
NSLCM/Catalog/GVNFM/Workflow/Vimproxy/EMS driver/vendor VNFM driver
...
| Jira | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
...
| Jira | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
...
Sub-components are repositories and are consolidated in a single centralized place. Edit the Release Components name for your project in the centralized page.
...
| Area | Actual Level | Targeted Level for current Release | How, Evidences | Comments | |||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Performance | 01 | 1 |
|
| |||||||||||||||||||||||||||
| Stability | 1 | 21 | Need to do a 72 hours soak test for VF-C
|
| Resiliency | 2 | 2 |
And also plan to add VF-C to CI/CD （stretch goal）In Casablanca we will split all VF-C DBs into a single container, so plan to support Resiliency at the DB level
|
| ||||||||||||||||||||||
| Resiliency | 2 | 2 | Depend on K8s supporting,no more work to do |
| |||||||||||||||||||||||||||
| 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 | 01 | 1 | Will split DBs from current Migrate VF-C components. So that VF-C components can scale in signle sitemysql db to mariadb galera cluster
|
| |||||||||||||||||||||||||||
| Manageability | 1 | 1+ | PatialPartial Need to know more clarification about manageablitilly level2 But we will update log format to compile log specification
|
| |||||||||||||||||||||||||||
| Usability | 1 | 1 | APIs documentation update
|
|
...
| API Name | API Description | API Definition Date | API Delivery date | API Definition link (i.e.swagger) |
|---|---|---|---|---|
NSLCM API Definition | Network services lifecycle management APIs, including scaling API | Link toward the detailed API description | ||
VNFM Driver API Definition | VNFM Driver component northbound APIs, including scaling API | |||
| VNF LCM API Definition | provide VNF lifecycle management APIs | |||
| Catalog API | NS/VNF package management APIs |
Third Party Products Dependencies
...
| 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
...