Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 195 Next »




Table of Contents

ETSI MANO and ONAP ETSI Alignment Landscape 

As part of aligning ONAP to ETSI MANO, ONAP supports ETSI standards for packaging, operations and monitoring for managing VNF, PNF and NS.

  • For packaging, the SOL004 standard is used for VNF and PNF, the SOL007 standard is used for NS
  • Use of the SO007 standard for NS packages is under discussion. 
  • VNF, PNF and NS will be described by SOL001 standard.
  • For VNF LCM, Package Management, LCM operations and Monitoring, SOL003 standard is used.
  • For NS LCM and Package Management, LCM operations and Monitoring, SOL005 standard is used.
  • For EM triggered scenarios (LCM, Fault, Performance, Configuration), SOL002 standard is used.

The following diagram depicts the relationship between ETSI MANO and ONAP ETSI Alignment.


Requirements

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

  • External VNFM scenarios :
    • ONAP needs to ingest and save (without modification) a SOL004 CSAR package for later consumption by a SOL003 compliant VNF Manager (VNFSDK, SDC)
    • ONAP needs to ingest and interpret a SOL001 compliant VNF Descriptor in order to design an ONAP Service (VNFSDK, SDC)
    • ONAP needs to understand resource requirements in the VNF-D for each deployment and scaling level (SO, A&AI, OOF)
    • ONAP needs to have a SOL003 compliant SBI (VF-C, SO )
    • ONAP needs a mechanism for specifying that a VNF instance should be runtime managed by a particular VNFM type (design time)  and instance (run time) (SO, OOF, A&AI)
    • ONAP needs to have a way to inventory a VNF that was deployed using an external VNFM (SO, A&AI)
  • External NFVO scenarios :
    • ONAP needs to ingest and save (without modification) a SOL004 CSAR package for later consumption by a SOL003 compliant VNF Manager (VNFSDK, SDC)
    • ONAP needs to ingest and interpret a SOL001 compliant VNF Descriptor in order to design an ONAP Service (VNFSDK, SDC)
    • ONAP needs to be able to convert an ONAP Service into a SOL001 compliant Network Service Descriptor (SOL005 Adapter)
    • ONAP needs to have a SOL005 compliant SBI (SO, VF-C, External)
    • ONAP needs a mechanism for specifying that a Service should be runtime managed SO, VF-C or external NFVO (SDC, SO)
    • ONAP needs to 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 be able to design a Service that includes some VNFs and some hierarchy (nested) of Services (NSs) (SDC)
    • ONAP needs 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)

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


  • vCPE use cases plan to be used.

Detailed Use Case, Architecture and Design

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

Frankfurt Scope

FeatureDescription
ETSI (SOL004/SOL007) Package Management
  • SOL004/SOL007 Package onboarding and distribution thru SOL005/SOL003 Package Management APIs
    • SDC Onboarding 
    • Direct SO Onboarding (SOL004)
    • SOL001 VNF/PNF/NS Handling
  • Package Security Handling
ONAP ETSI Catalog Management
  • ONAP-ETSI Catalog Management
  • SO ETSI Catalog Management
  • SOL003/SOL005 Adapter ONAP-ETSI Catalog Access/Use 
SOL003 Adapter
  • SOL003 operation support
SOL005 Adapter
  • SOL005 operation support
SOL002 Adapter
  • SOL002 operation support
SOL001 Mapping to SDC AID DM Mapping to SDC AID DM
  • VNFD Mapping
  • PNFD Mapping
  • NSD Mapping
Communication Security
  • Security between ONAP and external SVNFM/NFVO



Overall ETSI-Alignment Architecture

The following diagram depicts the overall ETSI-Alignment architecture.

Common Function Use Case, Architecture, Design 

<describe common functions>


Open Issues

  • 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 slide deck is for the Antwerp event.



  • The following slide deck was presented at the LFN+DDF event.


  • No labels