VVP Release Planning Template

Owned by Steven wright
Last updated: Mar 13, 2018
5 min read

DRAFT PROPOSAL FOR COMMENTS

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


Overview

Project Name

Enter the name of the project

Project Name

Enter the name of the project

Target Release Name

Beijing

Project Lifecycle State

Incubation. Refer to ONAP Charter, section 3.3 Project Lifecycle for further information

Participating Company 

Amdocs, AT&T, China Mobile, Huawei, Orange, Tech Mahindra,

Scope

What is this release trying to address?

For the Beijing release, the vvp project adds no new functionality, but the code delivered late in the Amsterdam release is integrated into the Beijing release plan. 

Use Cases

  1. We will not target any specific use case as the VNF Validation Program is focused on developing a mechanism for any VNF to obtain a ONAP Compatible Label

Minimum Viable Product

The MVP for Amsterdam will create the necessary framework and guidance to allow any 3rd party to acquire the ability to obtain an ONAP Compatible Label. The key here is to provide the necessary tracking and mechanisms to both carryout the validations and also to manage which 3rd parties have been approved to carry out such validations.

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.

For the Beijing release, the vvp project adds no new functionality, but the code delivered late in the Amsterdam release is integrated into the Beijing release plan. 

Epics

key summary type created updated due assignee reporter priority status resolution
Refresh

Stories

key summary type created updated due assignee reporter priority status resolution
Refresh



Longer term roadmap

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

The test scripts in vvp/test-scripts are used to validate compliance with VNF Requirments.  Currently these are focussed on VNFs packaged in HEAT templates. These need to expand in future releases to accommodate changes in VNF Requirments and  adoption of TOSCA formatted VNFs.

The other repos provide a tool for standalone validation of VNF packages. these same tests are likely to be also made available through VNF SDK and SDC projects in future. 

Release Deliverables

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

Deliverable Name

Deliverable Description

Deliverable Name

Deliverable Description

release notes

no new functionality beyond current code base expected

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.

Area

Actual Level

Targeted Level for current Release

How, Evidences

Comments

Area

Actual Level

Targeted Level for current Release

How, Evidences

Comments

Performance

NA

NA

vvp is a stand alone tool not a platform component

  • 0 -- none

  • 1 – baseline performance criteria identified and measured

  • 2 & 3 – performance improvement plans created & implemented

Stability

NA

NA

vvp is a stand alone tool not a platform component

  • 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

Resiliency

NA

NA

vvp is a stand alone tool not a platform component

  • 0 – none

  • 1 – manual failure and recovery (< 30 minutes)

  • 2 – automated detection and recovery (single site)

  • 3 – automated detection and recovery (geo redundancy)

Security

0

1

vvp is a stand alone tool not a platform component

  • 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

Scalability

NA

NA

vvp is a stand alone tool not a platform component

  • 0 – no ability to scale

  • 1 – single site horizontal scaling

  • 2 – geographic scaling

  • 3 – scaling across multiple ONAP instances

Manageability

NA

NA

vvp is a stand alone tool not a platform component

  • 1 – single logging system across components; instantiation in < 1 hour

  • 2 – ability to upgrade a single component; tracing across components; externalized configuration management

Usability

NA

NA

vvp is a stand alone tool not a platform component

  • 1 – user guide; deployment documentation; API documentation

  • 2 – UI consistency; usability testing; tutorial documentation





  • API Incoming Dependencies



VVP does not have APIs with other ONAP components.

  • API Outgoing Dependencies

VVP does not have APIs with other ONAP components.

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

Name

Description

Version

Name

Description

Version

Postgresql

object database

To fill out

git

repository



jenkins

Ci/CD tool



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

  • TESTING AND INTEGRATION PLANS

The vvp project has been developed as a containerized service for stand alone operation.

This is being integrated for instanciation by the OOM project

  • GAPS

  • KNOWN DEFECTS AND ISSUES

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

key summary type created updated due assignee reporter priority 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 identified

Mitigation Plan

Contingency Plan

Risk identified

Mitigation Plan

Contingency Plan

To fill out

To fill out

To fill out

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

11/16/18

M0

Kickoff

1/18/18

M1

Planning process Complete

2/12/18

M2

Functionality Freeze

3/8/18

M3

API/Data Model Freeze

3/29/18

M4

Code Freeze

4/19/18

RC0

Release Candidate 0

5/23/18

RC1

Release Candidiate 1

5/17/18

RC2

Release Candidiate 2

5/24/18

Release Delivery

Target Release Date

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

No additional functionality is expected in Beijing release.

Date

Project

Deliverable

Date

Project

Deliverable

To fill out

To fill out

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