Content Comparison

...

• Resource commitment:
  • Ericsson: primary contact Byung-Woo Jun
  • CMCC: primary contact Yan Yang Yuanhong Deng
  • Verizon: primary contact Former user (Deleted)
  • Samsung: primary contact k.kazak Pawel Slowikowski 
  • Nokia: under discussion
  • Intel: under discussion
• Usecase:
  • Ericsson: primary contact Byung-Woo Jun
  • CMCC: primary contact Yan Yang Yuanhong Deng
  • Verizon: primary contact Former user (Deleted)
  • Samsung: primary contact k.kazak Pawel Slowikowski 
• TSC Contact:
  • Ericsson: primary contact Stephen terrill
• Participating ONAP Projects:
  • SDC: Ericsson and others
  • SO, : Ericsson and others
  • SOL003 Adapter, : Ericsson and others
  • SOL005 Adapter, : Verizon
  • SOL002 Adapter
  • SDC
  • AAI
  • SDNC: Samsung
  • ETSI Catalog Manager: CMCC
  • AAI (as needed)

Table of Contents

...

Requirements

For ONAP ETSI MANO alignment, the following scenarios need to be fulfilled.

• ONAP shall support ETSI standards for packaging, distribution, LCM operations, security and monitoring for managing VNF, PNF and NS.
  • ONAP shall support SOL004 and SOL007 package onboarding and distribution (VNFSDK, SDC, SO, VFC and others)
  • ONAP shall support ETSI Package security and validation (VNFSDK, SDC, SVNFM, VFC, External NFVO)
  • ONAP shall support ETSI package catalog in runtime (SO, ONAP-ETSI Catalog Manager)
• External VNFM scenarios :
  • ONAP needs to shall ingest and save (without modification) a SOL004 CSAR package for later consumption by a SOL003 compliant VNF Manager VNFM/NFVO (VNFSDK, SDC, ONAP-ETSI Catalog Manager)
  • ONAP needs to shall ingest and interpret a SOL001 compliant VNF Descriptor VNFD in order to design an ONAP Service (VNFSDK, SDC)
  • ONAP needs to shall understand resource requirements in the VNF-D VNFD for each deployment and scaling level (SO, SOL003 Adapter, A&AI, OOF)
  • ONAP needs to have shall support a SOL003 compliant SBI to plug in external VNFM (SO, SOL003 Adapter, VF-C, SO )
  • ONAP needs shall have a mechanism for specifying that a VNF instance should be runtime managed by a particular VNFM type (design time)  and instance (run time) (SO, SOL003 Adapter, OOF, A&AI)
  • ONAP needs to shall have a way to inventory a VNF that was deployed using an external VNFM (SO, A&AI)
• External NFVO scenarios :
  ONAP needs to
  • ONAP shall ingest and save (without modification) a SOL007 Network Service Package. (VNFSDK, SDC) for later consumption by a SOL005 compliant NFVO
  • ONAP shall ingest and interpret a SOL001 compliant NSD (SDC)
  • ONAP shall ingest and save (without modification) a SOL004 CSAR package for later consumption by a SOL003 compliant VNF Manager NFVO (VNFSDK, SDC, ONAP-ETSI Catalog Manager)
  • ONAP needs to shall ingest and interpret a SOL001 compliant VNF Descriptor NSD/PNFD in order to design an ONAP Service (VNFSDK, SDC)
  • ONAP needs to shall be able to convert an ONAP Service into a SOL001 compliant Network Service Descriptor NSD (SOL005 Adapter)
  • ONAP needs to shall have a SOL005 compliant SBI (SO, SOL005 Adapter, VF-C,External External NFVO)
  • ONAP needs shall have a mechanism for specifying that a Service should be runtime managed SO, VF-C or external NFVO (SDC, SO)
  • ONAP needs to shall have a way to inventory a Service that was deployed as a Network Service using an external NFVO (SO, A&AI)
  • ONAP needs a way to ingest and save (without modification) a SOL007 Network Service Package. (VNFSDK, SDC)
  • ONAP needs to ingest and interpret a SOL001 Network Service  Descriptor (SDC)
  • ONAP needs to shall be able to design a Service that includes some VNFs and some hierarchy (nested) of Services (NSs) (SDC)
  • ONAP needs shall have a way to Deploy and Life Cycle Manage a Service that includes some VNFs and some hierarchy of Services (NSs) (SO, A&AI, SND-C, SOL003 & SOL005 Adapters)
• ONAP shall support: 1) VNFM-triggered VNF Configuration, 2) EM-triggered VNF/VNFC LCM and 3) VNF Indicator Interface, based on SOL002 standard (SOL002 Adapter, APPC, DCAE, Policy)

Overall Use Cases

• ETSI Package Management Use Case
  • SOL004/SOL007 VNF/PNF/NS Package includes SOL001 VNFD/PNFD/NSD with the original vendor package
  • SOL004/SOL007 VNF/PNF/NS Package Security
• ONAP-ETSI Catalog Management Use Case
  • ONAP-ETSI Catalog API Management
  • ONAP-ETSI Catalog Database
  • SO ETSI Catalog DB enhancement, by leveraging ONAP-ETSI Catalog Management Microservices
• ETSI-Alignment SOL003 Adapter Use Case
  • Package Management for SVNFM
  • Granting Enhancement with HPA
  • Query
  • Modify (TBD)
  • Policy-based Scaling (Stretch goal)
  • Security between the Adapter and VNFMs
  • Additional operations will be determined
• ETSI-Alignment SOL005 Adapter Use Case
  • Package Management for External NFVO
  • Security between the Adapters and External NFVOs
  • Additional operations will be determined
• ETSI-Alignment SOL002 Adapter Use Case
  
  • Security between the Adapters and VNFM
  • SOL002 operations

...

The following sub-sections describe the detailed use case, architecture and design for ETSI Alignment. 

• ETSI Package Management
• ETSI Catalog Management
• SOL003 Adapter 
• SOL005 Adapter
• SOL002 Adapter
• SOL001 Mapping to SDC AID DM
• Communication Security

Frankfurt Scope

...

Common Function Use Case, Architecture, Design 

...

• Mapping between SOL001 VNFD to SDC AID DM, including ScalingAspect+Delta and VF-Module - Not all VNFD needs to be transformed to the SDC AID DM
• How does ONAP support vendor-specific SVNFM security (authentication/authorization)?
• SOL007 (NS package) support is under discussion
• Certificate generation and distribution by AAF
• SOL005 Adapter requirements for the ONAP-ETSI Catalog Manager
• Where (SOL003 Adapter, or SO NFVO) do we support VNF software image transfer to VIM?
  • ONAP-ETSI Catalog Manager stores the software image and forwards it to VIM through the Adapter and VNFM.

Presentation Slide Deck

• The following deck presentation for the ETSI NFV workshop: https://nfvwiki.etsi.org/index.php?title=ONAP-ETSI_Alignment_Workshop_-_18_February_2020.

• The following deck will be presented to the ETSI SOL WG on Feb 18 (8am ET)

• The following slide deck is for the Antwerp event.

...