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, intelIntel

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: scaling, HPA

      3. Maturity enhancement to existing functionalities:  interface align ETSI, indirect mode support

Features and Functionality for this Release:

  1. Manual scaling
  2. HPA
  3. Integration with Logging/A&AI-Image Manager
  4. Multi-cloud Indirect mode
  5. Auto scaling- stretch goal

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/VNF Scaling

...

IN

...

H

...

NS/VNF scaling

...

VNF LCM (GVNFM)

...

IN

...

H

...

VNF instantiate, termination through GVNFM

...

VNF Integration(GVNFM)

...

IN

...

H

...

Integration with the open source VNF(HPA)

...


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 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 AND fixVersion = "Beijing 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.TBD

Architecture

High level architecture diagram

...

AreaActual LevelTargeted Level for current ReleaseHow, EvidencesComments
Performance01

Need to work with the benchmark benchmarking project and define the critera

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

  • 0 -- none
  • 1 – baseline performance criteria identified and measured
  • 2 & 3 – performance improvement plans created & implemented
Stability01

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

automated detection and recoveryNeed to work with OOM team to learn more about the mechanism they can provide.

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
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 Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
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(*)

lack resource*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 Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyVFC-659

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

support ONAP standard loggingNeed to work with Logging team to identify the logging guidline.

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

  • 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 Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyVFC-664

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

...