Versions Compared

Old Version 2

changes.mady.by.user Yan Yang

Saved on

compared with

New Version Current

changes.mady.by.user Yan Yang

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Project NameEnter the name of the project
Target Release NameCasablancaDublin
Project Lifecycle StateIncubation
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)      R3 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 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 Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues20
jqlQueryproject = VFC AND issuetype = Epic AND status = "To Do" AND resolution = Unresolved Status = Open AND fixVersion = "Casablanca Dublin Release"
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176

...

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues20
jqlQueryproject = VFC AND issuetype = Story AND fixVersion = "Casablanca Dublin Release"
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176

...

Sub-components are repositories and are consolidated in a single centralized place. Edit the Release Components name for your project in the centralized page.

...

AreaActual LevelTargeted Level for current ReleaseHow, EvidencesComments
Performance011


Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyVFC-9531238
  • 0 -- none
  • 1 – baseline performance criteria identified and measured
  • 2 & 3 – performance improvement plans created & implemented
Stability121

Need to do a 72 hours soak test for VF-C

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyVFC-938

  • 0 – none
  • 1 – 72 hours component level soak w/random transactions
  • 2 – 72 hours platform level soak w/random transactions
  • 3 – 6 months track record of reduced defect rate
Resiliency22

In Casablanca we will split all VF-C DBs into a single container, so plan to support Resiliency at the DB level 

1240

And also plan to add VF-C to CI/CD （stretch goal）

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyVFC-9511208

  • 0 – none
  • 1 – 72 hours component level soak w/random transactions
  • 2 – 72 hours platform level soak w/random transactions
  • 3 – 6 months track record of reduced defect rate
Resiliency22

Depend on K8s supporting,no more work to do

  • 0 – none
  • 1 – manual failure and recovery (< 30 minutes)
  • 2 – automated detection and recovery (single site)
  • 3 – automated detection and recovery (geo redundancy)
Security11+

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.

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyVFC-9371201


  • 0 – none
  • 1 – CII Passing badge + 50% Test Coverage
  • 2 – CII Silver badge; internal communication encrypted; role-based access control and authorization for all calls
  • 3 – CII Gold
Scalability011

Will split DBs from current Migrate VF-C components. So that VF-C components can scale in signle sitemysql db to mariadb galera cluster

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyVFC-9521205


  • 0 – no ability to scale
  • 1 – single site horizontal scaling
  • 2 – geographic scaling
  • 3 – scaling across multiple ONAP instances
Manageability11+

PatialPartial

Need to know more clarification about manageablitilly level2

But we will update log format to compile log specification

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyVFC-933

  • 1 – single logging system across components; instantiation in < 1 hour
  • 2 – ability to upgrade a single component; tracing across components; externalized configuration management
Usability11

APIs documentation update

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyVFC-9351207

  • 1 – user guide; deployment documentation; API documentation
  • 2 – UI consistency; usability testing; tutorial documentation

...

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 NameAPI DescriptionAPI Definition DateAPI Delivery dateAPI 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 Definitionprovide VNF lifecycle management APIs


Catalog APINS/VNF package management APIs


  • Third Party Products Dependencies

...

Risk identifiedMitigation PlanContingency Plan
To fill outTo fill outTo fill out

  • Resources

Fill out the Resources Committed to the Release centralized page.

  • Release Milestone

...