Skip to end of metadata
Go to start of metadata

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

Compare with Current View Page History

« Previous Version 3 Next »




Requirements & Use Cases

The following requirements are defined in the Honolulu release - functional requirements proposed list.

Support for ETSI SOL005 v3.3.1 Os-Ma-nfvo Interface between ONAP SO and NFVO

  • Executive Summary- Provide an interface adapter from ONAP Service Orchestrator tp NFVO(s) using an ETSI SOL005 v3.3.1 compliant Interface 
    • Support for Create, Upload, Update, Query, Delete of an ETSI NS Descriptor using an ETSI v3.3.1 SOL005 compliant NFVO
    • Support for Create, Instantiate, Terminate of a ETSI NS using an ETSI compliant NFVO
    • Support for receiving NS Notifications (LCN) from an NFVO
    • Support for ModifyVnfInfo operation.
  • Business Impact- Enables operators and service providers to use vendor provided or internally developed ETSI compliant NFVO(s).  Industry compatibility.
  • Business Markets- All operators and service providers that are using ETSI SOL005 compliant NFVOs
  • Funding/Financial Impacts- Reduction in operations expense from using industry standard Interfaces.
  • Organization Mgmt, Sales Strategies-There is no additional organizational management or sales strategies for this requirement outside of a service providers "normal" ONAP deployment and its attendant organizational resources from a service provider.

Feature Descriptions

Feature

Description







Epic and User Story

Epic

User Story

Description

Honolulu Plan?

JIRA

Support for ETSI SOL005 v3.3.1 Os-Ma-nfvo Interface between ONAP SO and NFVO


  • Executive Summary- Provide an interface adapter from ONAP Service Orchestrator tp NFVO(s) using an ETSI SOL005 v3.3.1 compliant Interface 
    • Support for Create, Upload, Update, Query, Delete of an ETSI NS Descriptor using an ETSI v3.3.1 SOL005 compliant NFVO
    • Support for Create, Instantiate, Terminate and Delete of a ETSI NS using an ETSI compliant NFVO
    • Support for receiving NS Notifications (LCN) from an NFVO
    • Support for ModifyVnfInfo operation.
  • Business Impact- Enables operators and service providers to use vendor provided or internally developed ETSI compliant NFVO(s).  Industry compatibility.
  • Business Markets- All operators and service providers that are using ETSI SOL005 compliant NFVOs
  • Funding/Financial Impacts- Reduction in operations expense from using industry standard Interfaces.
  • Organization Mgmt, Sales Strategies-There is no additional organizational management or sales strategies for this requirement outside of a service providers "normal" ONAP deployment and its attendant organizational resources from a service provider.
Yes



Support for Create, Upload, Update, Query, Delete of an ETSI NS Descriptor using an ETSI v3.3.1 SOL005 compliant NFVO

SOL005 Adapter needs to support Create, upload, Update, Query, Delete of and ETSI NS Descriptor using an ETSI v3.3.1 SOL005 compliant NFVO

Fernando Oliveira I don't think SOL005 Adapter support this package management because we have ETSI Catalog Manager. We can discuss this more

Yes ? 

Support for Create, Instantiate, Terminate and Delete of an ETSI NS using an ETSI compliant NFVO

SOL005 Adapter needs to support 3.3.1 Create, Instantiate, Terminate and Delete of an ETSI NS using an ETSI compliant NFVO

  • SOL005 Adapter need to choose a proper NFVO based on the model (SO NFVO, VFC, External NFVO)
  • SOL005 Adapter needs to receive the Create, Instantiate, Terminate and Delete NS LCM requests from ONAP SO. Its interfaces are not necessarily SOL005 APIs
  • SOL005 Adapter needs to send the Create, Instantiate, Terminate and Delete NS LCM requests to the selected NFVO via SOL005 LCM APIs
  • SOL005 Adapter should be able to support v2.7.1 SOL005 LCM APIs - one level backward compatibility is supported 
Yes

Support for receiving NS Notifications (LCN) from an NFVO

SOL005 Adapter needs to support NS Notification (LCN) from an NFVO

  • SOL005 Adapter needs to subscribe to NFVO for subscription with subscription filters, by using SOL005 APIs
  • SOL005 Adapter needs to receive NS notifications from the registered NFVOs
Yes

Support for ModifyVnfInfo operation.

SOL005 Adapter needs to support ModifyVnfInfo operation APIs

  • SOL005 Adapter needs to receive the ModifyVnfInfo. requests from ONAP SO through its NBI, which is not necessarily SOL005 APIs
  • SOL005 Adapter needs to send the ModifyVnfInfo requests to the selected NFVO via SOL005 APIs
Yes

Support for Queries for VNF/PNF/NS package management

SOL005 Adapter needs to query ETSI Catalog manager for VNF/PNF/NS packages

  • Note: for Honolulu, PNF packages will not supported from the SOL005 Adapter
Yes

Enhance NFVO invocation sequences from UUI to SOL005 Adapter to make ONAP SO SOL005 compliant

SOL005 Adapter supports interfaces to/from ONAP SO NFVO

  • Using UUI / CLI, the E2E request will be sent to SO. Make SO handles the E2E request
    • from UUI, selects NFVO
    • If CLI is used, pass the selected NFVO in the request
  • Make/enhance SO Workflows to extract NSDs from the E2E
  • For each NSD, make SO to invoke the SOL005 Adapter
  • SOL005 Adapter sends SOL005 requests to the ONAP SO NFVO, as one of the choices (SO NFVO, VFC, External NFVO)
    • Chooses the SO NFVO based on the selected NFVO in the request 
    • SOL005 Adapter sends CRUD SOL005-compliant NS requests which include multiple VNFs and VLs.
  • SOL005 Adapter subscribes (CREATE and DELETE) to ONAP SO NFVO for notifications
  • SOL005 Adapter provides notification endpoint(s) to receive notifications (P1)
  • Swagger will be provided to the SOL005 Adapter development
Yes

SO-2857 - Getting issue details... STATUS






SOL005 Adapter Architecture for Honolulu

The diagram depicts SOL005 Adapter Architecture.


 



 


SOL005 Adapter Operations

The following SOL005 Adapter operations will be supported:

  • Create NS
  • Instantiate NS
  • Terminate NS
  • Delete NS
  • Query of NS
  • Modify
  • Operation Status
  • No labels