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

Feature Descriptions

Epic and User Story

SOL003 VNFM Adapter Architecture for Frankfurt

The diagram depicts SOL003 VNFM Adapter Architecture.

1. VNFM Adapter exposes its NBI to any VNFM Adapter client
   1. VNFM Adapter continues to be a SO microservice component.
   2. VNFM Adapter will be registered to MSB.
   3. a VNFM Adapter client (e.g., GNFC) will locate the VNFM Adapter through MSB.
2. Interfaces are refactored to be generic (accessed by other ONAP/External components) - TBD
   1. the VNFM Adapter NBI will be enhanced for additional SOL003 operation support.
3. SDC CSAR including the SDC internal model and the vendor original SOL004 package is supported
4. SO leverages ETSI Catalog microservice for ETSI-based NS, VNF and PNF
5. VNFM Adapter retrieves VNF package from Catalog Manager
6. VNFM Adapter Client uses MSB to locate the VNFM Adapter
7. VNFM Adapter locates a VNFM based on a better VNFM locating mechanism
8. VNFM Adapter and SVNFM support additional SOL003 operations, possibly including modification for configuration
9. VNFM Adapter and SVNFM support authentication and authorization
   1. AAF will be used for authentication and authorization
   2. But, vendor SVNFMs may use their own AA mechanism
10. VNFM Adapter interfaces with OOF to support HPA-support granting (see the Granting enhancement section)
11. For the integration testing, the VNFM Simulator in the CSIT container will be used.

SOL003 Operations

The following SOL003 operations will be supported:

• Package Management
• Grant enhancement
• Query of VNF
• Scaling (stretch goal)
• Modify
• Operation Status

SOL003-based Operation Sequence Flows

• Create / Instantiate VNF
  • It is supported in the Dublin release, and it will be enhanced to leverage the ETSI Catalog Manager.
• The following sequence flows depicts the SOL003 Create/Instantiate operations by leveraging the above architecture. 

• Terminate/Delete VNF
  • It is supported in the Dublin release, and it will be enhanced to leverage the ETSI Catalog Manager.
• The following sequence flows depicts the SOL003 Terminate/Delete operations by leveraging the above architecture. 

<Diagram : tbd>

• Query VNF
  • TBD

SOL003 Adapter - SVNFM Operations

The SOL003 Adapter supports the following SOL003-based operations.

Package Management

• Query/Reading VNF package information (VNFM → SOL003 Adapter)
  • The SOL003 Adapter provides the SOL003 Query/Reading VNF package services to the SVNFM.
  • The SVNFM can request for multiple VNF packages or an individual VNF package for the given vnfPkgId.
  • The SOL003 Adapter returns the VnfPkgInfo[] or VnfPkgInfo.

• Reading VNFD of an on-boarded VNF package (VNFM → SOL003 Adapter)
  • The SOL003 Adapter provides the SOL003 Reading VNFD service to the SVNFM.
  • The SVNFM can request for a VNFD for the given vnfd.
  • The SOL003 Adapter returns a copy of VNFD from the VNF package.

• Fetching an on-boarded VNF package (VNFM → SOL003 Adapter)
  • SOL003 Adapter supports the whole package content fetch only.
  • The SVNFM sends a GET request for the VNF package content resource.
  • The SOL003 Adapter returns with a copy of the VNF package file.

• Fetching a VNF package artifact (VNFM → SOL003 Adapter)
  • SOL003 Adapter supports the whole content of the artifact only.
  • The SVNFM sends a GET request for the Individual VNF package artifact. 
  • The SOL003 Adapter returns with a copy of the applicable artifact file from the VNF package.

• Creating subscriptions for the package management (VNFM → SOL003 Adapter)
  • The SVNFM sends a POST request for the Subscriptions resource including PkgSubscriptionRequest.
  • The SOL003 Adapter returns with a data structure of PkgmSubscription.

• Sending notifications for the package management (SOL003 Adapter → VNFM)
  • If an event occurs that matches the filtering criteria, the SOL003 Adapter generates a notification that includes information about the event, and sends it to the registered SVNFM.
  • The SVNFM acknowledges the successful delivery of the notification.

Grant Request with Synchronous Response with HPA

The SOL003 Adapter supports the Synchronous Grant operation. Hardware Platform capability requirements are downloaded as part of the VNFD data.

There are two methods to support HPA in SO:

• Use of Homing information that is made during the SO decompose processing.
  • During SO decompose processing, SO calls OOF for collecting homing information for the service (which includes the VNFs).
  • Call the OOF APIs to perform the optimize service/VNF homing and placement
  • Use the existing homing workflows to pass hardware platform capability requirements to OOF

• If the above processing does not work for the vendor VNF HPA, OOF will be called from the SOL003 Adapter per VNF. The following describes the interactions between SOL003 Adapter and OOF.
  
  • VNFM Adapter sends out homing requests to OOF (OSDF) containing resource info
  • OOF (OSDF) pulls all the related homing constraints from Policy
  • OOF (HAS) checks AAI database to pull region (flavor) information
  • OOF (HAS) communicates with Multi-Cloud to check cloud capacity (vims which fulfill the requirements)
  • OOF (OSDF) returns homing allocation solution to VNFM Adapter
  • OOF collects information as following:
  • Service and Resource Info, from: AAI
  • HPA Flavors/Capabilities/Capacity Info, from: AAI
  • Policy Models (Homing, PCI) from: Policy
  • Infrastructure Metrics Info (capacity), from: MultiCloud
  • Cloud Agnostic Intent Info, from: MultiCloud
  • PCI configuration data (not yet a part of SDC model)

Query VNF

The SOL003 Adapter requests the Query VNF to the VNFM.

Modify VNF

The SOL003 Adapter requests the Modify VNF to the VNFM.

Get Operation Status

The SOL003 Adapter requests the Get Operation Status operation. The following diagram depicts a sequence for obtaining the status of a VNF lifecycle management operation occurrence.

Authentication and Authorization for the VNFM Adapter and the VNFM

• Leverage AAF for authentication and authorization to secure communications among ONAP components and SVNFM and external NFVO (App-to-App AA). The following is input from AT&T. More to discuss…
  • OAuth2 is not yet used in ONAP. Start with HTTP Basic Authentication with HTTPS
  • Update an application pom file and add properties; i.e., no application code changes?
    • Remove Spring Security as well, as we cannot have both in place
  • There is no need to use the CADI Rest Client at all
  • The CADI filter can be configured to handle authorization; that is the method AT&T uses, or the application can enforce the authorization. It supports basic URI matching semantics
  • Generate certificates by AAF for HTTPS is the current gap.
• Authentication and Authorization on SOL003 and SOL005 APIs need to be supported.
  • HTTP Basic Authentication + TLS
  • OAuth2
  • Two-way TLS
• How does ONAP support vendor-specific SVNFM security (authentication/authorization)? It is under discussion.
  • Security between SOL003/SOL005 and SVNFM/NFVO
  • Each SVNFM can use their own security mechanism; i.e., non-AAF based
• Note:
  • Communications between SOL003/SOL005 Adapter and SVNFM/NFVO must be secured through HTTPS
  • SOL002 Adapter is facing the similar security requirements.