VFC R 2 Feature Planning Implementation Yang yangyanyjchinamobile
VF-C R 2 Feature Planning & Implementation Yang yangyanyj@chinamobile. com December 11, 2017
VF-C Amsterdam Release Retrospect Functionalities delivered in Amsterdam release • VF-C supports NS/VNF lifecycle management and VF-C FCAPS management • VF-C supports integration with multi VNFMs and EMS via drivers • VF-C supports integration with VNFs via generic VNFM. Components delivered in Amsterdam release • NFVO LCM, Catalog, Res. Mgr, Ems. Driver, SVNFM Driver(3), GVNFM Driver • GVNFM LCM, Res, Mgr • Wf. Engine,activiti 2
VF-C R 2 Feature Planning Focus • Use Case Requirements - R 2 functional requirement from different use cases • Carrier Grade Requirements(S 3 P) - Address S 3 P requirements in R 2 • VF-C R 1 function enhancement - Address and enhance the issues discovered in R 1 VF-C functionalities can be divided into two categories in R 2 - Functionality enhancement to existing use cases - Maturity enhancement to existing functionalities 3
Functionality Enhancement to Existing Use Cases - NS/VNF Scaling - Support NS/VNF level scaling - Support auto & manual scaling - EPA - Support EPA features - VF-C Dummy case for developer - VF-C v. FW and v. LB case - Virtual Resource Management in indirect mode - VF-C R 1 supports direct mode - In R 2, VF-C will work with Multi-cloud to implement indirect mode - Support VNFs as containers– stretch goal - Automatic configuration management – stretch goal 4
Functionality enhancement—NS/VNF Scaling • NS/VNF Manual scaling: Manual scaling provides the capability of NS/VNF scale in/out triggered by operators Portal SO VF-C 3 rd VNFM VIM/NFVI 3 rd EMS/VNF 1. Manually trigger scaling operation 2. Scaling in/out 3. Operate scaling in/out 2’. Scaling in/out 3’. Operate scaling in/out 5
Functionality Enhancement —NS/VNF Scaling Auto-scaling close loop Onset DCAE Clear DMaa. P ③ ④ TCA PDP DMaa. P VES Collector Rest ⑦ Scaling VNF KPI EMS VNF VF-C Host Action Execution Adapter ① Guest ⑤ ② Multi-Cloud VF-C VM KPI ⑥ 6
Functionality Enhancement—NS/VNF Scaling • NS/VNF Auto-Scaling workflow based on policies 7
Functionality Enhancement—EPA • EPA Features support VNF Suppliers VNF Packages (CSAR Files) VNF packages are ingested and onboarded SDC CLAMP Catalog POLICY DB Contain hardware platform requirements Parse hardware platform capabilities in tosca model Discovery of hardware platform capabilities EPA-centric policies for VNF placement and operation DB SO DCAE VF-C A&AI DB Discovered hardware capabilities are stored in the inventory DB Multi-VIM Abstraction Layer Open. Stack Wind. River VMware VIO 8
Functionality Enhancement—EPA • VF-C EPA Features Support Project Requirement Modeling Adding the EPA description in VNFD model EPA features SDC Handling of EPA requirements during on-boarding and service design SO/VF-C Orchestration of service and VNF instantiation based on EPA requirements; Use of hardware platform requirements as constraints for VNF instance operation and remediation. Multi. VIM Discovery of VIM compute resources, discovery of hardware platform capabilities, persistence of compute resource capability data AAI Modeling and persistence of hardware platform capabilities as part of the inventory information. Other …… SR-IOV, NUMA, …. . GVNFM VNFD VNF Simple VNF, Clearwater 9
Functionality Enhancement -Dummy Case for Developer • R 1 focuses on integration with related modules to support Vo. LTE use case, such as SDC, A&AI, SO, Policy, etc. • In R 2, use VF-C to demo dummy case for developer, such as v. FW, v. LB SDC A&AI SO MSB UUI Policy NBI Adaptor NFVO GVNFM v. FW Adaptor Multi-VIMl v. LB VNF Open source VNF VIMs • Work with Integration team to define -Tosca Model - Test cases 10
Functionality Enhancement to Existing Use Cases—Indirect Mode • VNF related resource management done by VNFM • VNF related resource management done by NFVO 11
Functionality Enhancement to Existing Use Cases—Indirect Mode • Shield direct interaction between VNFM and VIM • Unified virtual resources management entrance VF-C is participating in the discussion and formulation of indirect mode solutions. Design Principles model requirements VF-C / vendor VNFM Seamless switch to the multi-vim proxy module Multi-cloud Provide a consistent interface with VIM to avoid VNFM changes 12
Functionality Enhancement to Existing Use Cases—Stretch goal • Two stretch goal - Support VNFs as containers in addition to VNFs as VMs Ø Container technical advantages Ø VNFs as container is needed for ONAP R 2+ use cases, such as 5 G-RAN and v. CPE - Automatic configuration management – stretch goal Ø Object: Service configuration unified entrance and automatic service configuration delivery Ø Current situation: No reference standard, big difference among vendors 13
Maturity Enhancement to Existing Functionalities • VF-C module maturity enhancement - Continue to align interface with the ETSI • ONAP system maturity enhancement - Image Management - Package Management - Resource Management - Deployment Management - Operation and maintenance management 14
VF-C Module Maturity Enhancement- Align interface with the ETSI • Alignment analysis of current VF-C interface with ETSI standard Interface Features Alignment analysis NSLCM NBI NS Package Align with the SDC interface, not ETSI LCM Most of interfaces have aligned with ETSI, only a few URLs and parameters need to be aligned Notification Not align with ETSI VNF Package VFC provides query and fetch VNF package interface. In addition to the above interface , ETSI provides package subscribe and notification interface. LCM • VF-C only provides instantiate interface; ETSI provides create and instantiate interface; • VF-C only provides terminate interface; ETSI provides terminate and delete interface; • Other functions are almost aligned,need to align URLs and parameter. Notification Not align with ETSI LCM/ VNF package/Notification LCM interfaces are aligned with ETSI, the Package and notification interfaces can refer the Driver’s analysis Interface between NSLCM and Driver GVNFM NBI 15
VF-C Module Maturity Enhancement- Align interface with the ETSI ONAP Interface NSLCM NBI NSLCM and Driver API Interface ETSI Interface api/nslcm/v 1/ns SOL 005 api/nslcm/v 1/ns/{ns. Instance. Id}/instantiate SOL 005 api/nslcm/v 1/ns/{ns. Instance. Id}/scale SOL 005 api/nslcm/v 1/ns/{ns. Instance. Id}/heal SOL 005 api/nslcm/v 1/ns/{ns. Instance. Id}/terminate SOL 005 api/nslcm/v 1/jobs/{job_id} SOL 005 /{vnfmtype}/v 1/{vnfmid}/vnfs SOL 003 /{vnfmtype}/v 1/{vnfmid}/vnfs/{vnf. Instance. Id}/scale SOL 003 /{vnfmtype}/v 1/{vnfmid}/vnfs/{vnf. Instance. Id}/heal SOL 003 /{vnfmtype}/v 1/{vnfmid}/vnfs/{vnf. Instance. Id}/terminate SOL 003 /{vnfmtype}/v 1/{vnfmid}/vnfs/{vnf. Instance. Id} SOL 003 /{vnfmid}/jobs/{jobid} SOL 003 /catalog/v 1/vnfpackages/{csar. Id} SOL 003 /nslcm/v 1/ns/grantvnf SOL 003 /nslcm/v 1/ns/{vnfmid}/vnfs/{vnf. Instance. Id}/Notify SOL 003 16
ONAP System Maturity Enhancement • Cooperate with other projects to enhance ONAP system maturity Enhance Function Related Project Function Description R 1 Implementation Image Management IM VF-C cooperates with IM to complete the image upload to the specified VIM in the running time Image manually upload to VIM Package Management RT Catalog VF-C cooperates with RT catalog to VF-C has one catalog complete the package management component to manage in running time packages in running time Resource Management A&AI VF-C synchronize all virtual resource instances to A & AI Only NS/VNF/VL/VM resource stored in A&AI Deployment Management OOM Use OOM to deploy VF-C deployment with heat VF-C integrates with Logging to implement log centralized management and operation and maintenance. VF-C didn’t integrate with Logging Operation and Logging Maintenance Management 17
s Thanks
- Slides: 18