Versions Compared

Old Version 2

changes.mady.by.user Yan Yang

Saved on

compared with

New Version 3

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 NameEnter the name of the release you are targeting to deliver
Project Lifecycle State
Either Incubation, Core, Mature. Refer to ONAP Charter, section 3.3 Project Lifecycle for further information
Planning
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.

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 the integration specifications for Policy/SO/DCAE/Use case Portal/VID/Vendor VNFM/EMS/A&AI/Mutil-VIM

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 

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

Interface provided

IN

H

Provide restful interfaces  to Policy/SO/VID/portal

NS LCM

IN

M

NS instance healing

VIM Integration

IN

H

 Integration with multi VIMs via Multi-VIM.

NS LCM

OUT

M

NS instance scaling

Resource Granting

OUT

M

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

A&AI Integration

In

M

Integration with A&AI

SDC Integration

In

M

Integration with SDC

...

Epics&Stories(draft)

NS Package Management

      NS Package Onboard

      Delete NS Package

      Show NS Package

      NS package management integration with SDC

VNF Package Management

      VNF Package Onboard

      Delete VNF Package

      Show VNF Package

      VNF package management integration with SDC

NS Deployment

      NS instantiation workflow

      NS Instantiation integration with parser

      NS Instantiation via ONAP Model

      NS Instantiation integration with SO

      NS Instantiation integration with Usecases Portal

      NS Instantiation integration with A&AI

      NS Instantiation integration with S-VNFM

      NS Instantiation integration with G-VNFM

      NS Instantiation integration with multi-VIM

NS Termination

      NS Termination workflow

      NS Termination integration with Usecases Portal

      NS Instantiation integration with SO

      NS Termination integration with A&AI

      NS Termination integration with S-VNFM

      NS Termination integration with G-VNFM

      NS Termination integration with multi-VIM

VNF Deployment

      VNF instantiation workflow

      VNF Instantiation integration with parser

      VNF Instantiation via ONAP Model

      VNF Instantiation integration with A&AI

      VNF Instantiation integration with multi-VIM

      VNF Instantiation integration with S-VNFM

      VNF Instantiation integration with VNF

      VNF Resource Granting for VNF Instantiation

VNF Termination

      VNF Termination workflow

      VNF Termination integration with A&AI

      VNF Termination integration with multi-VIM

      VNF Termination integration with S-VNFM

      VNF Resource Granting for VNF Termination

NS Autohealing

      NS Healing

      Integration with S-VNFM

      Integration with Policy

Fault

      Fault collect

      Integration with DCAE

Epics

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

...

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.

To fill out

Deliverable Name

Deliverable Description

To fill out

NS LCM

NS lifecycle management

VNF Fcaps

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

VNF Resource Management?GVNFM?

VNF Virtual Resource Management

VNF Init Configuration(GVNFM)

VNF Init Configuration and Management

Sub-Components

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

...

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

...

Anyone reading this section should have a good understanding of all the interacting modules.

Image Added


Image Added

The color coding is as following:

  • Green color of FBs (NFVO, G-VNFM/S-VNFM and EM) and interfaces (IFA013/SOL005, IFA007/SOL003, IFA008/SOL002, IFA006/OpenStack) implies full compliancy with ETSI NFV Release-2 specifications.
  • Blue color of interface (3GPP Itf-N – northbound of EM) implies full compliancy with 3GPP SA5 specifications
  • Yellow color of FBs (AA&I, MSO, DCAE and Policy) and interfaces (ECOMP message bus) implies un-changed ONAP message bus (same as used by APP-C)
  • White color of interfaces implies that this particular interface is typically not standardized and remains proprietary
  • Pink color of FB (ONAP Adaptor) shows the actual scope of the VF-C open source development effort

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)

Catalog API (SDC)

API to read the NS and VNF Catalog




Parser API

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

To fill outHigh level description of the APIDate for which the API is reviewed and agreedTo fill outLink toward the detailed API description




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)

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



Link toward the detailed API description

VNFM Driver API Definition

VNFM Driver component southbound 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


ARIA

TOSCA Parser


Parser

Openstack Parser ???

To fill outTo fill outTo fill out


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.

...

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.

...

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

...