...
UC: Use-case
O: Other requirements
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) /wiki/spaces/SV/pages/16089212 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 | 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
| ||||||||||||||||||||
| NF1. |
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
| Jira Legacy | ||||||||
|---|---|---|---|---|---|---|---|---|
|
| 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 | High | VF-C, OOM | CMCC
| ||||||||||
NF1.4 |
Improve VF-C documentation and make the user/developer to more easy to try to use VF-C
https://onap.readthedocs.io/en/latest/submodules/vfc/nfvo/lcm.git/docs/platform/installation.html
CMCC
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 | High | VF-C, Integartion |
|
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
CMCC
| Jira Legacy | ||||||||
|---|---|---|---|---|---|---|---|---|
|
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
Intel / ZTE /CMCC
| Jira Legacy | ||||||||
|---|---|---|---|---|---|---|---|---|
|
F3 | Scaling | Auto scaling | Low | DCAE/Holmes/Policy/VF-C | |
F4 | |||||
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 |
| server | System Jira |
|---|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
| key | VFC-1237 |
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
|
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 VNFHeal VNF
Operation VNF
Scale VNF
LCM Notification
| Jira Legacy | ||||||||
|---|---|---|---|---|---|---|---|---|
|
Align R4 DM
| Jira Legacy | ||||||||
|---|---|---|---|---|---|---|---|---|
|
Operation VNF
Scale VNF
LCM Notification
| 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 |
| ||||||||||
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 | ||||||||
O7 | ||||||||||||
| O8 | ||||||||||||
| O9 |