...
ID | catalog | How VF-C is concerned | priority | Projects Impacted | Resource 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 | High | VF-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-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 | |||||||||||||||||||||||||||
| NF1.3 | Remaining 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 | High | VF-C, OOM | CMCC
| |||||||||||||||||||||||||||
NF1.4 | 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 thisif we can leverage the CLI work | High | VF-C, Integartion |
| |||||||||||||||||||||||||||
| NF1.5 | Duplicate Service registered in MSB | 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 | High | VF-C | NF1.6 | Start up way: uwsgi and runserver | During the integration testing, found some issue when use uwsgi to start the servieceservice. 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 | High | VF-C | |||||||||||||||||||||||
| NF1.76 | DB unstable | During the integration testing, found the DB connection will be lost during some DB operation. Need stable testing testing | High | VF-C | F3 | Scaling | Auto scaling | Low | DCAE/Holmes/Policy/VF-C | F4 | ||||||||||||||||||||||
| NF1.7 | upgrade 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. | High | VF-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 | UC1 | vCPE | VF-C integrates with opensource CPE VNFs via GVNFM in C Release | High | VF-C | UC2 | CCVPN | VF-C participates in CCVPN use case to support site vCPE instantiation in Dublin release and will plan to support SFC scenario in CCVPN E release | High | VF-C, SO, UUI | |||||||||||||||||
O1 | SOL005 interface alignment need use case to verify this | VF-C Northbound interfaces align with SOL005 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 | High | VF-C, SO, UUI | Create NS API : ZTE Delete NS API: ZTE Get NS API :ZTE Instantiate NS API: ZTE Scale NS API： CMCC Heal NS API: CMCC Update NS API : CMCC Terminate NS API :ZTE Delete NS API :ZTE NS LCM Operation Occurrences NSD PNFD VNF Package Management APIs : Verizon NSD Package Management APIs : Verizon
| The NSLCM interface have aligned with SOL005 need use case to do the integration testing, especially for SO and VF-C integration | O4 | NS instance model mapping to A&AI | The NetworkService and Service instance model will be merged together, A&AI will extend service instance to support NS instance information in Dublin release, VF-C will do the corresponding mapping to A&AI | High | VF-C, A&AI |
| ||||||||||||||||||||
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 | Medium | VF-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, VNFSDK | We suggest to leverage the VF-C existing feature , not to add new function | |||||||||||||||||||||||||||
O7 | ||||||||||||||||||||||||||||||||
| O8 | ||||||||||||||||||||||||||||||||
| O9 |