ETSI-Alignment Architecture - Honolulu

1- Brief Project Overview (brief as it should be known)

This use case intends to demonstrate the ETSI-Aligned modeling, package distribution, and orchestration by conforming to ETSI NFV. This use case shall support:

1. VNF modeling with minimum CNF enhancements from ETSI NFV 4.1.1, by conforming to the ETSI SOL004 Package and SOL001 Modeling standards
2. automated NSD and VNF/CNF package E2E distribution, by conforming to SOL005 and SOL003 Package Management APIs
3. NS and VNF Orchestration through a modular architecture and standards-based (ETSI NFV) interfaces, by conforming to SOL005 and SOL003 LCM standards

1.1 Overall Architecture

The following diagram depicts overall ETSI-Alignment Architecture for Honolulu.

• SDC supports SOL004 Package onboarding
• SDC supports SOL007 Design
  • SOL007 Onboarding is not yet supported in Honolulu
• ETSI Catalog Manager receives SDC Package notification
• ETSI Catalog Manager gets the original vendor ETSI NS and VNF packages and stores them into its database
• ETSI Catalog Manager sends the package onboarding notification to its subscribers (SO NFVO, SOL003 Adapter, in the future SOL005 Adapter)
• If the SOL004 VNF package embeds Container Images, ETSI Catalog Manager pushes the images to CIR via Docker Registry APIs
  • Currently, ETSI Catalog Manager defined this Container Image handling as a stretch goal 
  • If not (due to SDC 2MB Image file size limitation), ETSI Catalog Manager does not handle Container Images. In that case, the operator will upload Container Image(s) to the CIR component directly
  • SOL004 Package metadata will references Container Image file(s)
• CIR will be realized by Nexus with Docker Registry
  • CIR component can be delivered part of ONAP or the operator can leverage their CIR component(s)
  • Access APIs to CIR will be Docker Registry APIs
• K8S CISM will obtain information on Container Image(s) thru Docker Registry APIs
• K8S CIS will pull Container Image(s) thru Docker Registry APIs
• The Interface between VNFM and K8S CISM will follow K8S APIs
  • Interface between VNFM and CISM: use k8s APIs, potential to leverage an alignment with O2-DMS
  • Interface between MultiCloud K8s Plugin and CISM: use k8s APIs, potential to leverage alignment with O2-DMS
  • VNFM Enhancement (PoC) to invoke CISM on O-Cloud through O2-DMS
  • Note: support O2-DMS is a stretch goal; most likely use K8S APIs

1.2 ONAP SO CNF Orchestration Support

There are two tracks in ONAP for CNF support: ONAP ETSI-Alignment and Direct Path for CNF (Based on models, SO selects a proper path):

• ETSI-Alignment path
  • Following ETSI NFV IFA specifications for CNF
  • Leveraging and extending existing ONAP ETSI-Alignment Architecture
• Direct Path
  • Some think there is no need for the full VNFD for LCM, just Helm Charts and Images; delegate LCM to CISM; it may work for simple CNFs
  • Note: there are several cases where a more complete VNFD will be needed, such as 5G Core NFs.
• Collaboration Areas:
  • Unified Modeling, Packaging & Onboarding (SDC) – optional VNFD?
  • Package Distribution (SDC – ETSI Catalog Manager – CIR)
  • Common Components (e.g., CIR, A&AI, CDS)
• Note: CIR will be realized by Nexus with Docker Registry, and CIR access APIs will be based on Docker Registry APIs.

2- New component capabilities for Honolulu, i.e. the functional enhancements, if applicable

• SDC
  
  • Enhancements related to ETSI 3.3.1 SOL004 compliant VNF / CNF package onboarding and distribution
    • ETSI Package Management (SDC Enhancements) - Honolulu
    • ETSI Package Management (SDC Enhancements) - Honolulu#ETSIPackageManagementArchitecture
  • Supports ETSI 3.3.1 VNF with minimum CNF enhancements from 4.1.1
    • VNF/CNF Data Model Based on ETSI v3.3.1 SOL001 plus CNF Enhancements
    • CSAR Models: ETSI-Alignment VNFD and Example(s)
  • Enhancements related to ETSI 3.3.1 SOL007 compliant NSD package Design and Distribution
    • ETSI Package Management (SDC Enhancements) - Honolulu#NSOnboardingDesign: Design SOL007
    • ETSI Package Management (SDC Enhancements) - Honolulu#DesignNS: Design NS
  • Enhancements related to ETSI 3.3.1 SOL004 VNF and SOL007 NS package security
    
    • ETSI Package Management (SDC Enhancements) - Honolulu#SDCSOL004/SOL007VNFPackageSecurity
  • Architecture Diagram

• SO / SO NFVO
  • SO NFVO continues to support the same SOL005 APIs as Guilin: Create NS, Instantiate NS, Terminate NS, Delete NS and Get NS Operation Status.
    • In addition, It will support NSD subscription and notification
    • However, SO NFVO will upgraded ETSI v3.3.1 SOL005 LCM APIs from ETSI v2.7.1 SOL005 LCM APIs
    • SO NFVO and SOL003 Adapter CSIT will be supported
    • Epics and User Stories: ONAP SO Hierarchical Orchestration (SO NFVO) - Honolulu#EpicandUserStory
  • SO NFVO Honolulu Architecture Highlights
    • SO NFVO will be invoked by Curl Commands (as SO NFVO Client) since the SOL005 Adapter enhancements are out of scope
    • SO NFVO NS Workflow BPMNs and business logic will be packaged as a war file and deployed to ONAP SO Standalone/Clustered Camunda Engine
    • SO NFVO and SOL003 Adapter communications will be treated as an internal communication via HTTP
    • SO NFVO interacts with ETSI Catalog Manager thru MSB for NSD subscription and notification
  • Architecture Diagram: ONAP SO Hierarchical Orchestration (SO NFVO) - Honolulu#HonoluluSONFVOTesting

• ETSI Catalog Manager
  • Enhancements related to direct SDC Package distribution support thru SDCE-6
  • Enhancements related to NSD Subscription and Notification
  • Architectural Relationships and Interfaces support: ARC Modeling Component Description – Honolulu-R8
  • Architecture Diagram:

• AAI
  • No impacts since the SO NFVO does not support Scaling or Healing
  • AAI impacts will be analyzed for the Istanbul release

3- New or modified interfaces

• SDC ↔ ETSI Catalog Manager
• ETSI Catalog Manager ↔ SO NFVO

4- If they are modified, are they backwards compatible?

6- Interface naming (point to an example)

7- Consumed API from other projects

8- Published API

9- Reference to the interfaces.

(Reference to the the swagger.json file(s) whenever possible)

10- What are the system limits?

.

11- Involved use cases, architectural capabilities or functional requirements.

12- Listing of new or impacted models used by the project (for information only).

• Identify any High Level Information Model Requirements.   See: ONAP R8 Modeling High Level Requirements
  • Models based on information exchanges from Use Cases
  • Models documenting existing implementations
  • Forward looking models that may be implemented in future releases
• Describe how exposed APIs are mapped to information models

(list all the relevant Jira tickets)

13-Test plan/Testing Strategy

1. Unit Testing
2. Dev-to-Dev Testing  and
3. Integration
   

14- Any other details that are specific to this functional enhancement or UseCase.