DRAFT PROPOSAL FOR COMMENTS

The content of this template is expected to be fill out for M1 Release Planning Milestone.

Info

Use the "Copy" and "Move" options (available under the ..., top right of this page) to duplicate this template into your project wiki.
Use the Wiki to document the release plan. Don't provide PowerPoint.
Use as much diagrams and flow charts as you need, directly in the wiki, to convey your message.


Overview

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?

Describe the problem being solved by this release.

The VF-C  Beijing release has two primary objectives: 1. improving platform maturity ; 2. supporting use cases.  

  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

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

Minimum Viable Product

Describe the MVP for this release.

LCM(instantiate/terminate/heal/scaling) for NS

LCM(instantiate/terminate/heal/scaling)  and FCAPS for vendor VNFs

LCM(instantiate/terminate) for open source VNFs

Integration specification for Logging/A&AI-Image Manager

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.


Epics

Key Summary T Created Updated Due Assignee Reporter P Status Resolution
Refresh

Stories

Key Summary T Created Updated Due Assignee Reporter P Status Resolution
Refresh

Longer term roadmap

Indicate at a high level the longer term roadmap. This is to put things into the big perspective.

Release Deliverables

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

Deliverable Name

Deliverable Description

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

New deliverables in this release: NS/VNF Scaling API,Optimized NS/LCM API,Multi-cloud Indirect mode proxy, GVNFM with improvement function.

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.

Architecture

High level architecture diagram

At that stage within the Release, the team is expected to provide more Architecture details describing how the functional modules are interacting.

Indicate where your project fit within the ONAP Archiecture diagram.

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.

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

Need to work with the benchmarking project and define the critera

VFC-663 - Getting issue details... STATUS

  • 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

VFC-662 - Getting issue details... STATUS

  • 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

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

VFC-661 - Getting issue details... STATUS

  • 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

VFC-660 - Getting issue details... STATUS


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

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

VFC-659 - Getting issue details... STATUS

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

VFC-639 - Getting issue details... STATUS .

  • 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

VFC-664 - Getting issue details... STATUS

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


  • API Incoming Dependencies

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 Name

API Description

API Definition Date

API Delivery date

API Definition link (i.e.swagger)

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




A&AI Image Manager APIAPI to get/store image


  • API Outgoing Dependencies

API this project is delivering to other projects.

API Name

API Description

API Definition Date

API Delivery date

API 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 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
activiti workflow engineworkflow execution engine

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

  • Testing and Integration Plans

Provide a description of the testing activities (unit test, functional test, automation,...) that will be performed by the team within the scope of this release.

Describe the plan to integrate and test the release deliverables within the overall ONAP system.
Confirm that resources have been allocated to perform such activities.

  • Gaps

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.

Key Summary T Created Updated Due Assignee Reporter P Status Resolution
Refresh

  • Risks

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

  • Team Internal Milestone

This section is optional and may be used to document internal milestones within a project team or multiple project teams. For instance, in the case the team has made agreement with other team to deliver some artifacts on a certain date that are not in the release milestone, it is erecommended to provide these agreements and dates in this section.

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

Note

The Documentation project will provide the Documentation Tool Chain to edit, configure, store and publish all Documentation asset.


Other Information

  • Vendor Neutral

If this project is coming from an existing proprietary codebase, ensure that all proprietary trademarks, logos, product names, etc. have been removed. All ONAP deliverables must comply with this rule and be agnostic of any proprietary symbols.

  • Free and Open Source Software

FOSS activities are critical to the delivery of the whole ONAP initiative. The information may not be fully available at Release Planning, however to avoid late refactoring, it is critical to accomplish this task as early as possible.
List all third party Free and Open Source Software used within the release and provide License type (BSD, MIT, Apache, GNU GPL,... ).
In the case non Apache License are found inform immediately the TSC and the Release Manager and document your reasoning on why you believe we can use a non Apache version 2 license.

Each project must edit its project table available at Project FOSS.


Charter Compliance

The project team comply with the ONAP Charter.

  • No labels