Requirements concerning VF-C C release
NF: Non-functional requirement
F: Functional requirement
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) 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 | High | VF-C | |
| NF1.2 | S3P-scalability | 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 | High | VF-C, OOM | |
| NF1.3 | Remaining issue during Integration Testing-configuration | 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. | High | VF-C, OOM | |
| NF1.4 | Documentation | Improve VF-C documentation and make the user/developer to more easy to try to use VF-C | High | VF-C, Doc | |
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 | SOL005 interface alignment | VF-C Northbound interfaces align with SOL005 | High | VF-C, SO, UUI | |
F2 | |||||
F3 | |||||
UC1 | |||||
UC2 | |||||
| O1 | |||||
| O2 | |||||
| O3 | |||||
| O4 | |||||
O5 | |||||
O6 | |||||
O7 | |||||
| O8 | |||||
| O9 |