ONAP VNF Descriptor Data Modeling Collaborative Proposal for
ONAP VNF Descriptor Data Modeling Collaborative Proposal for Casablanca
ONAP R 3 VNF Descriptor (VNFD) Data Model (DM): Principles • ONAP needs an internal VNFD DM to permit its components to work predictably, consistently, and interoperate. • VNF Providers need a common form for delivery to multiple orchestration platforms including ONAP • ONAP needs to consider multiple alternatives for VNF On-boarding, both now (e. g. , HEAT, TOSCA), and in the future (e. g. , YANG, etc. ) • Internal ONAP DM will provide an ONAP optimized representation • The ONAP R 3 VNFD DM will be guided by ETSI SOL 001 VNFD and the ONAP R 2+ Resource Information Model - Semantics of on-boarded VNFD requirements need to be preserved - VNF On-boarding package need to be preserved within ONAP (both VNFD & CSAR) • ONAP will have well defined intra-platform/inter-component integration points based on its internal data model - Engage impacted ONAP Components to understand the aspects of the VNFD DM that are applied. • ONAP will document touch-points to define the relationship between its internal model and the industry standard models where appropriate at specific integration points.
Collaborative Recommendation for ONAP R 3 VNFD DM • SOL 004/SOL 001 v 2. 5. 1 and HEAT-based packages for on-boarding of VNFs into ONAP for Casablanca • On-boarding VNF package will be preserved and accessible within ONAP to support ONAP-ETSI points of interoperability and adaptor mediation • Document an Internal ONAP R 3 Resource Data Model for Design-Time and Run-Time by M 3 - Guided by ETSI SOL 001 VNFD, ONAP R 2+ Design-Time Resource DM clean version, and the ONAP R 3 Resource Information Model - Maintain mapping of Internal ONAP Data Model with ETSI SOL 001 and ONAP IM - Feed ONAP extensions back to ETSI for consideration • Document VNFD DM touch-points for ONAP components that are consuming VNFD and which part.
Next Steps • Provide VNF On-boarding model for ONAP R 3 (SOL 001) by M 2 Model Freeze, finalize by M 3. - Engage SDC Project to provide capability to preserve and make accessible the On -boarding VNF package within ONAP - Create SOL 001 on-boarding TOSCA supporting the v. CPE Use Case • Provide the Internal ONAP R 3 Resource Data Model for Design-Time and Run-Time by M 2 Model Freeze, finalize by M 3. - Engage impacted ONAP Components to understand the VNFD aspects of the Internal ONAP R 3 Resource Data Model that are applied - Create mapping of Internal ONAP Data Model with ETSI SOL 001 and ONAP Information Model
Backup Material
Features of ONAP VNFD DM for Casablanca and Beyond • VNFD association to the VNF used within the Service context • VNF Topology: describes VNF Components / Deployment Units, Connection Points (internal and external), Virtual Links (connectivity). • VNF Deployment Aspects: Deployment Flavors (DFs), configurable parameters, instantiation level, placement constraints, deployment groups, number of VDU instances, scaling. • VNF LCM Operations: LCM operations, input parameters, and artifacts.
Extra: VNF Design-time / run-time model relationships • VNFD is not just about on-boarding. Aspects are also used during the design-time and run-time stages the VNF. - Need to maintain touch-points to the on-boarded VNFD DM (properties, input parameters, VNF LCM operations) and CSAR packages. VNF Provider: • Design • Develop • Test (certify) • Integrate • Deliver Service Provider VNF Design-time: • Select • Order • Enrichment & Design • Validate & Certify • On-board • VNF Package (with VNFD) • End of Life Service Provider VNF Run-time: • Assemble • Assign • Service Configure • Deploy (instantiate, rebuild) • Operate (stop, restart, etc. ) • Modify / Query • Monitor • Test & Heal • Scale • Terminate
Extra: ONAP Needs Beyond ETSI-MANO • ONAP speed and agility vs longer release cycles of a standardization organization • ONAP services may not all have VNFs • ONAP services may be customer facing or infrastructure • ONAP supports allotted resources (using part of service B as a resource in service A) • ONAP will support abstract resolution at runtime (e. g. , a Firewall might be a PNF, VNF, or Allotted NF) • ONAP will manage the service lifecycle (where service != ETSI network service but instead is a service in support of a customer facing product)
Extra: ONAP as a Black Box VNF Provider ETSI SOL 004/SOL 001 On-Board & Refinement Service Designer enriches on-boarded VNFDs; Artifacts preserved Service Designer Creates Service Descriptor ONAP YANG, SOL 004/SOL 006 Open. Stack HEAT • ONAP has a broader functional scope than ETSI MANO (i. e. Service Orchestration and full Lifecycle Management), therefore the ETSI Data Model is not sufficient to drive ONAP behavior • ONAP needs to be agile and move quickly • ONAP as a Black Box supports Standards at the edges (e. g. , ETSI, TM Forum, MEF, HEAT) and preserves on-boarding artifacts BSS/OSS Service Creation and Lifecycle Management MEF LSO TM Forum Cross Domain VNFM Adaptor * Adaptors apply SOL 003 artifacts ETSI Compliant 3 rd Party VNFM * Use of VNFM Adaptor is only one use case
Extra: Standards on the Outside, ONAP DM on the Inside ETSI – one standardization organization Goal – creation of a standard… … supported by all vendors … providing comprehensive VNF description … compatible with multiple platforms (not only ONAP) … promotes its own architectural vision ONAP – a software development collaboration Goal – creation of a software product… … able to run in commercial environments … open to multiple input standards (not only ETSI) … cost-effective in creation, and operation of services - by being model-driven, by freedom of architectural decisions SDC Vendor Package VNF Onboarding Refinement Service And VNF Modeling e. g. , SOL 001 -> ONAP DM ETSI SOL 001, others ETSI VNFDs (SOL 001): one onboarding format, a solid base for extensions in ONAP, vendors should not have to deal with divergence Distribution To Runtime Components ONAP DM + original Artifacts ONAP model: drives the platform, higher velocity of change, multiple onboarded formats Lossless Transformation: preservation of the vendor-provided information as a requirement; The vendor provided VNF Package (including VNFD) remain available across ONAP DM Vendor Package
- Slides: 10