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 NameAmsterdam
Project Lifecycle StateIncubation
Participating Company China Mobile ,ZTE, Huawei,Nokia ,VMware,Boco,Jio,raisecom,Accenture.

Scope

What is this release trying to address?

Describe the problem being solved by this release

Realizing full life cycle management and FCAPS of VNF and NS.

Features and Functionality for First Release:

  1. Full life cycle management for NS
  2. Full life cycle management and FCAPS for VNFs
  3. Providing specifications for NSD and VNFD
  4. Providing the integration specifications for Policy/SO/DCAE/Use case Portal/VID/Vendor VNFM/EMS/A&AI/Mutil-VIM
    Note: The end2end service orchestration is out of scope for VF-C, VF-C will take part in end2end service orchestration by working with SO.

Use Cases

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

Use Case: VoLTE(approved)

Minimum Viable Product

Describe the MVP for this release.

Basic LCM for NS

Basic LCM and FCAPS for VNFs 

Modeling specification for NSD

Modeling specification for VNFD

Integration specification for other componets

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.

Functionality Name

In or Out

Priority

Stretch

NS LCM

IN

H

NS instance creation, NS instance termination

VNF LCM(GVNFM)

IN

H

VNF deployment, termination according to the VNF information model

VNF FCAPS

IN

M

Collection fcaps data from the EMS

Resource Granting

IN

H

Grant the resources requested from VNFMs

VNFM Integration

IN

H

Integration with specific VNFMs of vendors to deploy commercial VNFs

VNF Integration(GVNFM)

IN

H

Integration with the VNF

NS LCM

IN

M

NS instance healing

NS LCM

OUT

M

NS instance scaling

Resource Granting

OUT

M

Intelligent monitoring, allocation and reservation resources based on the requirement of VNFs

Interface provided

IN

H

Provide restful interfaces  to Policy/SO/VID/portal

Integration with other projects(VF-C will consume the interfaces these projects provided ):

Functionality Name

In or Out

Priority

Stretch

VIM Integration

IN

H

Integration with multi VIMs via Multi-VIM.

A&AI Integration

In

M

Integration with A&AI

SDC Integration

In

M

Integration with SDC

DCAE IntegrationInHIntegration with DACE to push vnf fcaps data to DACE



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.

Improve NS LCM operations 

Nested NSs.

Improve VNF LCM operations

Release Deliverables

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

Deliverable Name

Deliverable Description

NS LCM

NS lifecycle management

VNF FCAPS Collection

Collect FCAPS data from the EMS

NS Resource Management

NS Visualize resources and instantiations resources management

VNFM Drivers

VNFM drivers, including specific VNFM drivers

VNF LCM(GVNFM)

VNF lifecycle management and init configuration management

VNF Resource Management(GVNFM)

VNF Virtual Resource Management

Sub-Components

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

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

ONAP Dependencies

List the other ONAP projects your depends on.

Policy

DCAE

SO

Use case Portal

VID

Multi-VIM

A&AI

SDC

Modeling

MSB

OOM

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.

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.


API Incoming Dependencies

List the API this release is expecting from other releases.
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




API Outgoing Dependencies

API this release is delivering to other releases.

API Name

API Description

API Definition Date

API Delivery date

API Definition link (i.e.swagger)

NSLCM API Definition

Network services lifecycle management APIs



Link toward the detailed API description

VNFM Driver API Definition

VNFM Driver component northbound APIs




VNF LCM API Definition

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


Name

Description

Version

WSO2

Workflow execution engine


Parser

TOSCA Parser provided by modeling project

TBD

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.(to be updated)

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 Plan
To fill outTo fill outTo 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.

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
July 7ModelingNSD and VNFD
July 7ModelingParser API requirements
July 21Policy/SO/Usecase portalNS/VNF LCM API

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

6 Comments

  1. Adityakar Jha

    1. Since the functionality of NS LCM (Instantiation, Termination, Healing, Scaling) is covered in the scope of VFC and also Nested NSs has been covered under "long term roadmap" of VFC, can we have more clarity on the use case of SO-VFC integration, covered in point 3 under scope? 
    2. Under "API Incoming Dependencies" parser API is listed. Are we assuming that parser will be an external module? As per my understanding both parser and workflow engine shall be intrinsic to VFC. It is fine to list these under "Third Party Product Dependencies" as VFC project is dependent on WSO2/Aria.
    3. It will give us more clarity if In/Out APIs of VFC is listed per (inter-dependent) ONAP module interfacing with VFC along with API Description/Purpose. It will also help us not only clearly define the dependencies but also reconcile requirements from other ONAP projects. Further deliberation of these APIs may be done at design time. Suggesting a sample below,
    ModuleIN/OUTAPI NameAPI Description
    PortalINInstantiateNS/TerminateNSAPI to Instantiate/Terminate Network Service
    SDCINReadCatalogueAPIs to read NS/VNF Catalogues
    PolicyINReadPolicyAPIs to read policies pertaining to resource allocation, High Availability, Access Restriction, Scaling etc.
    PolicyOUTManageLCMAPIs to manage LCM of NS/VNF based on trigger condition
    A&AIINupdateInventoryAPIs to update NFV Instance Inventory



    1. Yan Yang

      Thanks for your comments

      1?Added a note to clarify that VF-C will take part in part in E2E Service Orchestration initiated by SO.
      2, We will be using the parser provided by modeling project.
      3, All the APIs are captured in the "Incoming API Dependencies" section, except for the third one, would you clarify that? We believe it is contained as contraints in NSD/VNFD, not in separate policies.

  2. Cheng (Ian) Liu

    On the architecture diagram as well as in the current seed code, I see an SFC driver to interface with SDN controller to set up SFC.   May I know if this driver is in the scope of Release 1? If not, any plan to use this driver in the future releases? Can current SDN-C in ONAP support this driver? Thanks!

    1. Yan Yang

      The SFC driver is not in the scope of Release 1,but we have the seed code from Open-O.Currently,we have no plan to use this driver,but we may use it to set up SFC in some senariao in the future release.

      1. Cheng (Ian) Liu

        Thanks a lot. May I know if current ONAP SDN-C can support this SFC Driver?

        1. Bertrand Low

          Hi there, I'm also interested in the current state of SFC implementation in ONAP - can anyone shed some light on this? thanks.