Use Cases

  • ETSI-Alignment SOL005 Adapter Use Case
    • Package Management for External NFVO
    • Security between the Adapters and External NFVOs
    • Additional operations will be determined

Feature Descriptions

Feature

Description

ETSI Catalog Manger - SOL005 AdaptersETSI Catalog Manager API support for SOL005 Adapters
SOL005 Adapters - External NFVOSOL005 Adapter package management support based on SOL005 APIs
Secured communication and authentication and authorization support

Secured communication and authentication and authorization support between SOL005 Adapter and External NFVO

  • HTTPS protocol
  • Authentication and Authorization support via AAF

Epic and User Story

Epic

User Story

Description

FrankfurtJIRA
SOL005 Adapter will support NS/VNF Package Management and NS LCM
SOL005 Adapter will support NS/VNF Package Management and NS LCMNo

SO-2435 - Getting issue details... STATUS


SOL005 Adapter Package Management for External NFVO by leveraging the ONAP-ETSI Catalog Manager

  • Access the ONAP-ETSI Catalog Manager to retrieve the NS packages
  • Access the ONAP-ETSI Catalog Manager to retrieve the VNF packages
  • Subscribe to the ONAP-ETSI Catalog Manager for package notifications from the Catalog Manager
  • Terminate the ONAP-ETSI Catalog Manager package notifications
  • provides APIs to the external NFVO for retrieving the NS packages
  • Provides APIs to the external NFVO for retrieving the VNF packages
SOL005 Adapter Package Management for External NFVO by leveraging the ONAP-ETSI Catalog ManagerNo

SO-2436 - Getting issue details... STATUS

SOL005 Adapter will support SOL005 NS Management

SO supports ETSI SOL005 Alignment of its interfaces with NFVO through SOL005

Yes

SO-1579 - Getting issue details... STATUS


SOL005 Adapter will support Create NSSOL005 Adapter will support Create NSYesunder SO-1579

SOL005 Adapter will support Instantiate NSSOL005 Adapter will support Instantiate NSYesunder SO-1579

SOL005 Adapter will support Terminate NSSOL005 Adapter will support Terminate NSYesunder SO-1579

SOL005 Adapter will support Delete NSSOL005 Adapter will support Delete NSYesunder SO-1579
SOL005 Adapter will support Communication Security

SOL005 Adapter will support Communication Security based on OAuth2 for APIs and OAuth2/HTTP Basic Authentication for notification

Yes

SO-2437 - Getting issue details... STATUS


Secured communication will be supported between SOL005 Adapter and external NFVOSecured communication between SOL005 Adapter and external NFVOYes

SO-2438 - Getting issue details... STATUS


Authentication and authorization will be supported between SOL005 Adapter and external NFVOAuthentication and authorization will be supported between SOL005 Adapter and external NFVOYes

SO-2439 - Getting issue details... STATUS

SOL005 Adapter Architecture

Support ETSI NFV-SOL 005 (Os-Ma-Nfvo ref point ) between SO & VF-C/NFVO

SOL005 Operations

The following SOL005 operations will be supported:

  • Package Management
  • TBD

SOL005-based Operation Sequence Flows

The following diagram depicts SOL005-based operation sequence flows.

SOL005 Adapter Operations


  • No labels

6 Comments

  1. Katsia Kazak

    Fernando OliveiraByung-Woo Jun I suggest to extract SOL005 Adapter from SO in Frankfurt. This will make possible direct communication SDC → SOL005 Adapter → NFVO for package management, skipping SO.

  2. Byung-Woo Jun

    Katsia Kazak are you suggesting we remove the SOL005 Adapter from SO? What is the rationale for this? 

    By looking at the current SOL005 Adapter architecture, the SOL005 Adapter is an extension of SO VFC adapter. If we extract the SOL005 Adapter, where do we put the Adapter? 

    The second question about the package management... It seems that you are suggesting the SOL005 Adapter gets the package from SDC, not from the runtime component.

    1. Fernando Oliveira

      Katsia Kazak Would exposing the SOL005 adapter's NBI satisfy your use case for having SDC directly pass packages to an external NFVO?  This would require that SDC develop a consumer of that NBI.

      We plan to enhance the SOL005 adapter beyond package management to support Network Service LCM, configuration, LCN, Fault Management and Performance Management so that SO can act as a OSS with an external NFVO.  While it is possible to extract the SOL005 Adapter from SO, much of the interface will be very intimate with the behavior of the SO which would make the NBI very complicated.

      1. Katsia Kazak

        Byung-Woo Jun It depends. I would like to see SOL005 adapter fully independent from SO component. Looking at your comment (last question) on the page ETSI Package Management , I assumed that you and community have the same vision. But now I see that its different (smile)

        1. Currently SOL005 adapter is dependant on Catalog DB and Request DB, what for are SO catalogues needed?
        2. Ok, I understand that you want to enhance SOL005 beyond management support. But why do you need SO for that?
        3. Which faults/performance/lifecycle notifications/metrics are you planning send to NFVO? Is it something more than can be found in Dmaap topics from VES events or AAI?


  3. Byung-Woo Jun

    Fernando Oliveira , I read the linked SOL005 Adapter architecture section. In the sequence diagram, there is a step, "store CSAR detail". I asked the author to elaborate the step to understand how the SOL005 Adapter handles ETSI packages. Could you share your insight?

  4. Byung-Woo Jun

    I created the above diagram which indicates where the SOL005 Adapter gets ETSI packages from the ONAP-ETSI Catalog Manager. The Catalog Manager will store NS/VNF (possibly PNF) and Software Images and provide APIs for the SOL005/SOL003 Adapters.