Requirements concerning VF-C F 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 |
| F1 | Catalog Enhancement to support ETSI Catalog | Now we receive SO ETSI catalog requirements as follows: API for the original vendor package; API for storing original vendor package into the Catalog DB Catalog need enhancement to support their specific requirements and this can be a good step to make catalog to be a common service | High | VF-C, SDC | |
| F2 | Dmaap python library | There is no python library for Dmaap, if can provide a python library , the csar package can distribute to VF-C from SDC directly not need to through UUI | Medium | VF-C, SDC | |
| F3 | LCM Operation rollback | Once NS/VNF LCM is abnormal, should Support NS and VNF rollback | Medium | VF-C | |
| F4 | SFC supporting | In CCVPN , they have the SFC requirements, for VF-C , need to consider to support VNFFG/NFP | High | VF-C | |
| F5 | K8S Integration | Plan to support CNF according to integrate with K8S Need to align with the K8S plugin which implemented in multicloud and to see the status and solution | VF-C, multicloud | ||
| F6 | Workflow Optimization | In F release, we would like to perform different workflow branches through flexible configuration. And increase the capabilities that workflow microservices can provide, such as monitoring …and the other related capabilities. | Medium | VF-C | |
| UC1 | CCVPN Edge NS Deployment | In CCVPN ,the AI applications as the value-add service can be provided by service provider, these AI applications are usually deployed in a distributed fashion to the edge DCs. So the requirements for VF-C is to instantiate the edge NS which include the AI application in enterprise branch | High | VF-C, Multicloud | |
| UC2 | vCPE | ||||
NF1.1 | S3P-security | ||||
| NF1.3 | configuration | ||||
NF1.4 | |||||
| NF1.5 | |||||
| NF1.6 | |||||
| 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. | Medium | 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 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 | High | VF-C, SO, UUI | need confirm the test plan with SO and verizon guys . |
O6 | |||||
O7 | |||||
| O8 | |||||
| O9 |