Page Comparison

Table of Contents

Use Case

...

SOL003 VNFM Adapter Architecture for Frankfurt

...

1. VNFM Adapter SOL003 Adapter continues to be an SO microservice component, and exposes its NBI to any VNFM SOL003 Adapter client in ONAPVNFM
2. SOL003 Adapter continues to be a SO microservice componentis registered to MSB.
3. VNFM Adapter will be registered to MSB.
4. a VNFM Adapter client (e.g., GNFC) will locate the VNFM Adapter through MSB.
Interfaces are refactored to be
5. generic (accessed by other ONAP/External components) - TBDthe VNFM Adapter Operator registers VNFM and VIM to ESR in AAI.
6. SOL003 Adapter exposes its NBI to any SOL003 Adapter client in ONAP (not for Frankfurt)
   1. Interfaces will be refactored to be generic to allow access by other ONAP components.
   2. The NBI will be enhanced for additional SOL003 operation support.
7. SDC CSAR including the SDC internal model and the vendor original SOL004 package is supported
8. SO leverages ONAP-ETSI Catalog microservice for ETSI-based NS, VNF and PNF
9. VNFM distributes SDC packages including the vendor original SOL004 (VNF and PNF) and SOL007 (NS) packages – SOL007 is not for Frankfurts
10. SO (SDC Controller) passes the SDC CSAR ID to ETSI Catalog Manager to invoke storage
11. ETSI Catalog Manager queries for SDC CSAR with the SDC CSAR id & store SOL004/SOL007 package.
12. SO (BPMN) and the SOL003 Adapter client locates SOL003 Adapter.
13. SO (BPMN) and the SOL003 Adapter client invokes SOL003 Adapter.
14. SOL003 Adapter retrieves VNF package from Catalog Manager.
15. VNFM Adapter Client uses MSB to locate the VNFM Adapter
16. VNFM Adapter locates a VNFM SOL003 Adapter gets available VNFM locations (endpoints) and gets VIM and VNF Info.
17. SOL003 Adapter selects a VNFM, based on a better VNFM locating mechanism.
18. VNFM SOL003 Adapter and SVNFM support additional SOL003 operations, possibly including modification for configurationVNFM supports SOL003 VNF LCM, granting and package management operations.
19. SOL003 Adapter supports HPA-based Granting, leveraging OOF.
20. SOL003 Adapter updates vServer, status and VNF association in AAI
21. SOL003 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
22. VNFM Adapter interfaces with OOF to support HPA-support granting (see the Granting enhancement section)
23. For the (AAF, and vendor AA mechanism) – partially for Frankfurt.
24. For integration testing, the VNFM Simulator in the CSIT container will be is used.

SOL003 Operations

The following SOL003 operations will be supported:

...

• Reading VNFD of an on-boarded VNF package (VNFM → SOL003 Adapter → ETSI Catalog Manager)

  • SOL003 Adapter Package Management - Read VNFD

    • SOL003 Adapter provides the SOL003 Reading VNFD service to SVNFM.
    • SVNFM requests for a VNFD for the given vnfd to SOL003 Adapter
      • GET .../vnf_packages/{vnfpkgid}/vnfd
    • SOL003 Adapter requests for a VNFD for the given vnfd to ETSI Catalog Manager
      • GET /api/vnfpkgm/v1/vnf_packages/{vnfPkgId}/vnfd
    • ETSI Catalog Manager returns a zip file of VNF package including vnfdModel JSONDefinition directory to SOL003 Adapter
    • SOL003 Adapter returns a Vnfd with the vnfdModel JSON zip file of VNF package Definition directory to SVNFM

    
    

    Precondition: The VNF package is onboarded to the ONAP-ETSI Catalog Manager

    Postcondition: SVNFM receives Vnfda Vnf package definition zip file

• Fetching an on-boarded VNF package (VNFM → SOL003 Adapter)
  • SOL003 Adapter supports the whole package content fetch only..
    • Support of the package_contents partial is a stretch goal in Frankfurt. The ETSI Catalog Manager supports fetching package_contents partial by setting the HTTP_RANGE in the request headers when the SOL003 Adapter wants to obtain a single range of bytes from the VNF package file. 
  • SVNFM sends a GET request for the VNF package content resource to the SOL003 Adapter.
    • GET .../vnf_packages/{vnfPkgId}/package_content
  • SOL003 Adapter sends a GET request for the VNF package content resource to the ETSI Catalog Manager
    • GET /api/vnfpkgm/v1/vnf_packages/{vnfPkgId}/package_content
  • ETSI Catalog Manager returns a copy of the VNF package file in the payload body to SOL003 Adapter.
  • SOL003 Adapter returns with a copy of the VNF package file in the payload body to SVNFM.

...

                           SVNFM gets package subscription (PkgmSubscription)subscription (PkgmSubscription)

<Sequence Diagram SVNFM → SOL003 Adapter>

<Sequence Diagram SOL003 Adapter → ETSI_Catalog_Manager>

• Query Subscription Info
  • SVNFM re-synchronizes all or selected subscriptions after some errors in SVNFM or some exception handling.
  • SVNFM sends a Query Subscription Info request to the SOL003 Adapter.
    • GET .../subscriptions  // for all subscriptions
  • SOL003 Adapter returns package subscription lists in the form of PkgmSubscription[] in the payload
  • or
  • SVNFM sends a Query Subscription Info request for a selected subscription to the SOL003 Adapter 
    • GET .../subscriptions/{subscriptionId}
  • SOL003 Adapter returns a selected package subscription to SVNFM.

...

Postcondition: SVNFM receives a notification

• Receiving notifications for the package management (ETSI Catalog Manager → SOL003 Adapter)
  • The ETSI Catalog Manager team is working on the Notification API.
  • Once the notification api is settled, the subscribed SOL003 Adapter will receive package notifications from the ETSI Catalog Manager.
• <Sequence Diagram: TBD>

Grant Request with Synchronous Response with HPA (VNFM → SOL003 Adapter)

...

There are two methods to support HPA in SO:. In the Frankfurt release, only the Method 1 will be supported.

• Method 1: 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
  • See the following diagram for the component interaction.

...

• Method 2: 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.
  • Note: current, OOF does NOT support the VNF Level Homing request. OOF API enhancement is under discussion. Otherwise, the method 1 (Service Level Homing) is used for Frankfurt. TBD.Frankfurt - Out of Frankfurt Release scope
  • 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)
• SOL003 Adapter Homing Request to OOF
  • <describe the homing request API and contract here>

...