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.

...

Table of Contents
outlinetrue

Overview

Project NameEnter the name of the project
Target Release Name
Enter the name of the release you are targeting to deliver
Casablanca
Project Lifecycle State
Either
Incubation
, Core, Mature. Refer to ONAP Charter, section 3.3 Project Lifecycle for further information
Participating Company 
List the company participating in this release. At least 3-4 organizations, including an operator are recommended.

...

China Mobile ,ZTE, Huawei, Nokia ,VMware, Boco, Jio, raisecom, Intel 


What is this release trying to address?

The VF-C Casablanca release has following primary objectives:

1. Improving platform maturity:enhance scalability, manageability,security (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

4. Enhancement to VF-C existing features:

      Integration with OOF, AAF(Strech goal)

      R3 tosca data model alignment

      ETSI Interface alignment(Depend on resource contribution)Describe the problem being solved by this release

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)


Functional Requirements:

Hardware Platform Enablement In ONAP

Centralized Representation and Consistent Identification of Cloud Regions In ONAP

Auto Scaling - stretch goal 

Minimum Viable Product

...

VF-C will include the necessary subcomponents supporting the primary objectives: meeting platform maturity goals and supporting the use cases.

LCM(instantiate/terminate/heal/scaling) for NS and Vendor VNFs

FCAPS for vendor VNFs

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.

...

Jira
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues20
jqlQueryproject = sanbox and issuetype in (epic) VFC AND issuetype = Epic AND status = "To Do" AND resolution = Unresolved AND fixVersion = "Casablanca Release"
serverId425b2b0a-557c-3c0c-b515-579789cceedb

...

Jira
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues20
jqlQueryproject = sanbox and issuetype in (story) VFC AND issuetype = Story AND fixVersion = "Casablanca Release"
serverId425b2b0a-557c-3c0c-b515-579789cceedb

...

Indicate the outcome (Executable, Source Code, Library, API description, Tool, Documentation, Release Note...) of this release.

Deliverable Name

Deliverable Description

To fill outTo fill out

Source CodeSource code for all VF-C components
Maven ArtifactsMaven Artifacts for all VF-C components
Docker ContainersDocker container  associated with VF-C componets
DocumentationVF-C detailed documentation

Sub-Components

List all sub-components part of this release.
Activities related to sub-components must be in sync with the overall release.

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

...

Indicate where your project fit within the ONAP Archiecture diagram.

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

Refering to CII Badging Security Program and Platform Maturity Requirements, fill out the table below by indicating the actual level , the targeted level for the current release and the evidences on how you plan to achieve the targeted level.

AreaActual LevelTargeted Level for current ReleaseHow, EvidencesComments
Performance01


Jira
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId425b2b0a-557c-3c0c-b515-579789cceedb
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
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId425b2b0a-557c-3c0c-b515-579789cceedb
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
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId425b2b0a-557c-3c0c-b515-579789cceedb
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
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId425b2b0a-557c-3c0c-b515-579789cceedb
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
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId425b2b0a-557c-3c0c-b515-579789cceedb
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
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId425b2b0a-557c-3c0c-b515-579789cceedb
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
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyVFC-935

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


  • API Incoming Dependencies

...

Prior to the delivery date, it is a good practice to organize an API review with the API consumers.

API Name

API Description

API Definition Date

API Delivery date

API Definition link (i.e.swagger)

To fill outHigh level description of the APIDate for which the API is reviewed and agreedTo fill out

Catalog API (SDC)

API to read the NS and VNF Catalog




Parser API(Modeling)

API for parsering TOSCA file




Micro-services bus API

API for registration and use of micro-services bus




Multi-vim API

API to allocate resource to VIM




DCAE VES collector SB API

API to push vnf fcaps data to VES collector




A&AI API

API to store inventory




OOF APIAPI to chose VIM which is used to deploy VNF
Link toward the detailed API description



  • API Outgoing Dependencies

API this project is delivering to other projects.

API NameAPI DescriptionAPI Definition DateAPI Delivery dateAPI Definition link (i.e.swagger)
To fill outHigh level description of the APIDate for which the API is reviewed and agreedTo fill out

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


  • Third Party Products Dependencies

Third Party Products mean products that are mandatory to provide services for your components. Development of new functionality in third party product may or not be expected.
List the Third Party Products (OpenStack, ODL, RabbitMQ, ElasticSearch,Crystal Reports, ...).

NameDescriptionVersion
To fill outTo fill outTo fill out
activiti workflow engine

In case there are specific dependencies  (Centos 7 vs Ubuntu 16. Etc.) list them as well.

...

This section is used to document a limitation on a functionality or platform support. We are currently aware of this limitation and it will be delivered in a future Release.
List identified release gaps (if any), and its impact.

Gaps identifiedImpact
To fill outTo fill out

  • Known Defects and Issues

Provide a link toward the list of all known project bugs.

Jira
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues20
jqlQueryproject = sanbox and VFC AND issuetype in (bug) AND fixVersion = "Casablanca Release"
serverId425b2b0a-557c-3c0c-b515-579789cceedb

...

List the risks identified for this release along with the plan to prevent the risk to occur (mitigation) and the plan of action in the case the risk would materialized (contingency).

Risk identifiedMitigation PlanContingency Plan
To fill outTo fill outTo fill out

  • Resources

Fill out the Resources Committed to the Release centralized page.

  • Release Milestone

...

It is not expected to have a detailed project plan.

DateProjectDeliverable
To fill outTo fill outTo fill out

  • Documentation, Training

  • Highlight the team contributions to the specific document related to he project (Config guide, installation guide...).
  • Highlight the team contributions to the overall Release Documentation and training asset
  • High level list of documentation, training and tutorials necessary to understand the release capabilities, configuration and operation.
  • Documentation includes items such as:
    • Installation instructions
    • Configuration instructions
    • Developer guide
    • End User guide
    • Admin guide
    • ...

...