You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Next »

Requirements concerning VF-C E release

NF: Non-functional requirement

F: Functional requirement

UC: Use-case

O: Other requirements

ID

catalog

How VF-C is concerned

priorityProjects ImpactedResource commitment

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

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

HighVF-C

Security communication:


security Issue:

Components owner

vfc/nfvo/driver/vnfm/svnfm/huawei: Huawei

vfc/nfvo/driver/vnfm/gvnfm: Huawei

vfc-nfvo-multivimproxy: Huawei

vfc-nfvo-resmanagement :Huawei

vfc-nfvo-driver-ems : Boco

vfc-nfvo-driver-svnfm-nokiav2 : nokia

VFC-1203 - Getting issue details... STATUS

VFC-1204 - Getting issue details... STATUS

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

For python components,  chose one component to upgrade and test ,and then update the remaining components

ZTE

NF1.3Remaining issue during Integration Testing-configuration

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 


HighVF-C, OOM

CMCC

VFC-1206 - Getting issue details... STATUS

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


HighVF-C, Integartion

VFC-1208 - Getting issue details... STATUS

NF1.5Start up way: uwsgi and runserver 

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 

HighVF-C
NF1.6DB unstable 

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

Need stable testing

High VF-C
NF1.7upgrade from python2 to python3

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.

HighVF-C

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

HighVF-C, SO, UUI

need confirm the test plan with SO and verizon guys .

O6

OVP MVP

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

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

O7

Code refactoring

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

const refactor

test case refactor

middleVF-CZTE
O8






O9






  • No labels