Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The VF-C Frankfurt release has following primary objectives:

1.

...

2. LCM Operation rollback

3. SFC supporting

4. K8S Integration 

5. Workflow Optimization 

6.Upgrade from python2 to python3

...

Improving platform maturity : Mariadb-Galera DB Consolidation for EI Alto,security (i.e., S3P items)

2. Supporting use cases identified by ONAP and integration:  vCPE

3. Supporting Functional Requirements identified:

      ETSI Alignment : migrate VF-C catalog to modeling etsicatalog

      E2E Network Slicing: (supporting NSSMF,Stretch goal depend on the commit resource )

4. VF-C enhancement and new  features:

      Python upgrade from python2 to python3

      JDK upgrade evaluate and migrate (Depend on the commit resource)

      VF-C integrate with CLI to improve VF-C Usability

      Provide python-based Dmaap library

      Supporting LCM Operation rollback(Stretch goal)

      Add VF-C related use case vCPE on daily CI chains 

Use Cases

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

Use Case: Residential Broadband vCPE (Approved)

Requirements

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

ETSI Alignment Support

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyREQ-101

E2E Network Slicing 

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyREQ-146
  
Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyREQ-158

Minimum Viable Product

VF-C will include the necessary sub-components supporting the primary objectives: meeting platform maturity goals and supporting the use cases.

...

Minimum VF-C components supporting above functionalities:

NSLCM/Catalog/GVNFM/Workflow/Vimproxy/EMS driver/vendor VNFM driver

...

Catalog API (SDCAPI to read the NS and VNF Catalog
API NameAPI DescriptionAPI Definition DateAPI Delivery dateAPI Definition link (i.e.swagger))

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




OOF APIAPI to chose VIM which is used to deploy VNF


...

API NameAPI DescriptionAPI Definition DateAPI Delivery dateAPI 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 Definitionprovide VNF lifecycle management APIsCatalog APINS/VNF package management APIs


  • Third Party Products Dependencies

...