VF-C requirements collection for Dublin release

ID

catalog

How VF-C is concerned

NF1.1

S3P-security

CII Silver badge(Including no critical and high known vulnerabilities > 60 days old and other requirements),plus

"All communication shall be able to be encrypted and have common rolebased access control and authorization. "( not committed)

R3 VF-C Security/Vulnerability - Full Content

The following repos still have security issue

vfc/nfvo/driver/vnfm/svnfm/huawei

vfc/nfvo/driver/vnfm/gvnfm

vfc-nfvo-multivimproxy

vfc-nfvo-resmanagement 

vfc-nfvo-driver-ems

vfc-nfvo-driver-svnfm-nokiav2 

For DB components, would like to see how to meet S3P through OOM.

Know from OOM team that MariaDB Galera Cluster can be used to meet S3P HA requirements.

For other components, we should to do some test to see whether the components can work properly based on OOM replicas

Investigate all VF-C configuration can be automatically injected through oom.

During the integration testing, such as SDC URL and user/pwd should be updated manually to Catalog configuration, Before that, need to turn off the livenessprobe of k8s.

Improve VF-C documentation and make the user/developer to more easy to try to use VF-C

VF-C R3 operation guide

https://onap.readthedocs.io/en/latest/submodules/vfc/nfvo/lcm.git/docs/platform/installation.html

NF1.5

Including VF-C to daily building testing

Investigate how to add VF-C to the daily building test case

Need work with Integration team to do this

F1

Centralized Representation and Consistent ID of Cloud Regions

ONAP need centralized representation and consistent ID of cloud regions to enable multiple cloud/VIM orchestration, and multicloud is the consumer of the ID

F2

HPA

Changes to VF-C will be required in order to incorporate use of HPA into instantiation and related operation.

Although VF-C have integrated with OOF , but haven't used the VIM decision which got from OOF, still using the VIM passed by UUI

F3

Scaling

Auto scaling

F4

UC1

vCPE

VF-C integrates with opensource CPE VNFs via GVNFM in C Release

UC2

CCVPN

O1

SOL005 interface alignment

VF-C Northbound interfaces align with SOL005

SOL005_support_In_VFC.ods

Create NS API

Delete NS API

Get NS API

Instantiate NS API

Scale NS API

Heal NS API

Update NS API

Terminate NS API

Delete NS API

NS LCM Operation Occurrences

Subscribe /Notify/ Query / Terminate - NSD Package

NSD

PNFD

Subscribe / Notify / Query / Terminate / Fetch - VNF Package

O2

SOL003 interface alignment

The interface have been supported now :

Create VNF Identifier

Query VNF           

Query Multiple VNFs

Delete VNF Identifier    

Instantiate VNF

Terminate VNF

Notify about VNF lifecycle endpoint

Heal VNF only support restart one vm

Operate VNF haven't been tested

GET VNF LCM Operation occurrences

Individual VNF LCM operation occurrence

Subscribe to VNF lifecycle change notification

Interface that will continue to implement are as follows :

Heal VNF

Operation VNF

Scale VNF

LCM Notification

Align R4 DM

O5

VF-C workflow Optimization

The build-in workflow is executed by default in current VF-C code. In Dublin release, plan to perform different workflow branches through flexible configuration. At least, support activity workflow and build-in workflow at D release.

The main work include:

a. Activity workflow edit and writing

b. Activity workflow integration testing

O6

O7