Versions Compared

Old Version 9

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.

...

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

5.       ETSI Interface alignment(Depend on resource contribution)

...

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)

Image Added

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.

Image Added

Platform Maturity

...

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-953
  • 0 -- none
  • 1 – baseline performance criteria identified and measured
  • 2 & 3 – performance improvement plans created & implemented
Stability12

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 

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

  • 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-937


  • 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
Scalability01

Will split DBs from current VF-C components. So that VF-C components can scale in signle site

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


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

Patial

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-935

  • 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.

...

Risk identifiedMitigation PlanContingency Plan
To fill outTo fill outTo fill out

  • Resources

Fill out the Resources Committed to the Release centralized page.

  • Release Milestone

...