VF-C requirements collection for E 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)

/wiki/spaces/SV/pages/16089212

The following repos still have security issue

java projects:

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 

python projects:

vfc-gvnfm-vnflcm

vfc-gvnfm-vnfmgr

vfc-gvnfm-vnfres

vfc-nfvo-catalog

vfc-nfvo-driver-vnfm-gvnfm

vfc-nfvo-driver-vnfm-svnfm-zte

vfc-nfvo-lcm

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

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

2. MSB registeration flag

The Service will  register to MSB automatically by code when service start , and when pod start, the service will also register to MSB via OOM. Need to consider how to deal with the  duplicate service endpoint 

MSB Issue need find effective solution 

xx

NF1.4

Including VF-C to daily building testing

Investigate how to add VF-C to the daily building test case if we can leverage the CLI work

During the integration testing, found some issue when use uwsgi to start the service.

If add the enable-thread, the new thread can start up in component, but when the pod start, we encounter the empty reply from service 

During vCPE testing, we will query the unstable reason 

Intel, ZTE, CMCC

During the integration testing, found the DB connection will be lost during some DB operation.

Need stable testing

During vCPE testing, we will query the unstable reason 

Intel, ZTE, CMCC

Python 2.7 will reach the end of its life on January 1st, 2020 and won't be maintained after that date. A future version of pip will drop support for Python 2.7. 0
So we need to upgrade the python version.

chose one component, such as gvnfmdriver to update and test, then if we have time and resource in E release, we can update the remaining components

ZTE

O1

SOL005 interface alignment

need use case to verify this

The NSLCM interface have aligned with SOL005

need use case to do the integration testing, especially for SO and  VF-C integration

O6

OVP MVP

In OVP  MVP， have added tosca validation ， VF-C will cooperate with OVP to provide the tosca-based VNF validation.

We suggest to leverage the VF-C existing feature , not to add new function

Intel, Huawei, ZTE, CMCC

VNFSDK will invoke VF-C NS APIs, when a VNF onboarding to SDC, CLI will invoke SDC internal API to design VNF to a NS, we need to make sure the NS  can be associated with VNF under artifact directory.

O7

Code refactoring

code style refactor, including good variable, function name,... etc

const refactor

test case refactor

We would like to optimize GVNFM driver to make it can integrate with multiple SOL003 VNFM. 

Need to see whether it can support now or need to do some enhancement