Versions Compared

Key

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

...

Project NameEnter the name of the project
Target Release NameBeijing
Project Lifecycle StateIncubation
Participating Company China Mobile ,ZTE, Huawei, Nokia ,VMware, Boco, Jio, raisecom., Intel

Scope

What is this release trying to address?

...

  1. System maturity enhancement: integration with Logging/A&AI-Image Manager, enhance stability,performance,security etc.

      2. Functionality enhancement to existing use cases: NS/VNF scaling, indirect mode supportHPA

      3. Maturity enhancement to existing functionalities:  interface align ETSI? integration with open source VNF

Features and Functionality for this Release:

...

indirect mode support

Use Cases

Describe the use case this release is targeted for (better if reference to customer use case).

Use Case: VoLTE(approved)

Use Case: Residential Broadband vCPE (Approved)

Enterprise vCPE - stretch goal

...

LCM(instantiate/terminate/heal/scaling)  and FCAPS for vendor VNFs which included in VoLTE use case

LCM(instantiate/terminate) for open source VNFs

...

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.

...

Functionality Name

...

In or Out

...

Priority

...

Stretch

...

NS Scaling

...

IN

...

H

...

NS scaling

...

VNF Scaling

...

IN

...

H

...

VNF Scaling

...

VNF LCM (GVNFM)

...

IN

...

H

...

VNF instantiate, termination through GVNFM

...

VNF Integration(GVNFM)

...

IN

...

H

...

Integration with the open source VNF

Integration with other projects:

...

Functionality Name

...

In or Out

...

Priority

...

Stretch

...

...

A&AI -Image Manager Integration

...

In

...

M

...

Integration with A&AI- Image Manager


Epics

Jira
serverONAP 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 AND fixVersion = "Beijing Release"
serverId425b2b0a-557c-3c0c-b515-579789cceedb

...

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

Architecture

High level architecture diagram

...

Indicate where your project fit within the ONAP Archiecture diagram.

Image RemovedImage Added

Block and sequence diagrams showing relation within the project as well as relation with external components are expected.

...

AreaActual LevelTargeted Level for current ReleaseHow, EvidencesComments
Performance01Awaiting guidance from Benchmark subcommittee

Need to work with the benchmarking project and define the critera

Jira
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyVFC-663

  • 0 -- none
  • 1 – baseline performance criteria identified and measured
  • 2 & 3 – performance improvement plans created & implemented
Stability01We assume that integration team will

Need to do a 72

hour ONAP soak which includes VF-C.

hours soak test for VF-C

Jira
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyVFC-662

  • 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
Resiliency12automated detection and recovery

Need to work with OOM team to learn more about the mechanism they can provide.

Jira
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyVFC-661

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

increase test coverage to 50% and need help with CII badging

Jira
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyVFC-660


  • 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
Scalability001(*)

*NOTE - due to lack of resources, VF-C may not achieve level 1 for all components in this release.

and It is "Low" priority per Jason's slides from TSC 1/4/2018.

Jira
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyVFC-659

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

Need to work with Logging team to identify the logging guidline.

Jira
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyVFC-639

support ONAP standard logging

.

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

documentation is already in onap.readthedocs.io, will continue to improve

Jira
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyVFC-664

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

...

EPA modeling haven't been definded yet
Risk identifiedMitigation PlanContingency PlanRisk DescriptionHPA support

Move to the next release

Move to the next release
Logging integrationContinue the current form of logging or writting log in accordance with the clear part of loging requirementContinue the current form of logging or writting log in accordance with the clear part of loging requirementCurrently there is no explicit requirement about how to log
  • Resources

Fill out the Resources Committed to the Release centralized page.

  • Release Milestone

The milestones are defined at the Release Level and all the supporting project agreed to comply with these dates.

...