...

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

7. Add VF-C to daily buildingImproving platform maturity : Mariadb-Galera DB Consolidation ,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

      Improve GVNFM Driver as SOL003 adapter

      Provide python-based Dmaap library

      Supporting LCM Operation rollback(Stretch goal)

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

5. Document current upgrade component strategy(TSC must have) 

6. SECCOM Perform Software Composition Analysis - Vulnerability tables(TSC must have) - plan to solve the most of the security issues, but also depends on the commit resource 

7. SECCOM Password removal from OOM HELM charts(TSC must have) 

8. SECCOM HTTPS communication vs. HTTP(TSC must have) - Based on the resource contribution 

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).CCVPN Use Case in Frankfurt Release

ETSI Alignment Support

E2E Network Slicing 

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

...

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

...

Please fill out the centralized wiki page: Frankfurt Release Platform Maturity v1

• API Incoming Dependencies

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

...

• Third Party Products Dependencies

...

Please update any risk on the centralized wiki page - Frankfurt Risks

• Resources

Fill out the Resources Committed to the Release centralized page.

• Release Milestone

...