Versions Compared

Old Version 5

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.

...

Project NameEnter the name of the project
Target Release NameEnter the name of the release you are targeting to deliverAmsterdam
Project Lifecycle StatePlanningIncubation
Participating Company China Mobile ?,ZTE?, Huawei?,Nokia ?,VMware?,Boco?,Jio?,raisecom,Accenture.

Scope

What is this release trying to address?

...

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

...

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

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

...

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

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

...

Jira
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues20
jqlQueryproject=sanbox VFC and issuetype in (story)
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

NS LCM

NS lifecycle management

VNF

Fcaps

FCAPS Collection

Collect

fcaps

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

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.

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

...

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

Image Removed

Image Removed

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

Image Added


API Incoming Dependencies

...

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




...

Name

Description

Version

WSO2

Workflow execution engine


ARIAParser

TOSCA Parser provided by modeling project

Parser

Openstack Parser ???

TBD

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

...

Provide a link toward the list of all known project bugs.(to be updated)

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

...

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.

To fill out
DateProjectDeliverableTo fill outTo fill out
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
    • ...

...

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


Charter Compliance

The project team comply with the ONAP Charter.