Page History

...

• Deliver points of interoperability between ONAP and External Systems
• Focus on ONAP External APIs to BSS/OSS (i.e., MEF Legato)
  • Service Catalog
    • Add notification for serviceCatalog API
      
      • Description:
        
        • Allow BSS catalog function to receive service catalog notification as serviceSpec status change or characteristic change (new value in an enum list for example). Could be interesting to track these serviceSpec update to update accordingly productSpec
      • Relevance:
      • Complexity: Moderate - need to subscribe to authenticated topic
      • Prerequisites: It requires to have a notification from SDC via DMaaP
      • Resources: Adrian O'Sullivan
  • Service Ordering
    
    • Add Support for serviceOrder API for Service Instantiation via macro mode
      
      • Description: 

        • With Dublin, a new mode is available in SO to instantiate a service : the "macro" mode.

          In SDC, a service can be declared with an instantiationType equal to "A-la-carte" or equal to "Macro". This information is then available in the Tosca service definition file.

          When "Macro" mode is choosen for a service, the SO will use different kind of BPMN workflow.

          This "macro" mode need to be managed by NBI.

          NBI needs to look at service definition in Tosca file, select the mode, build the "macro" request toward SO  when service instantiationType is "Macro". 

          REQUEST 1 : NBI have to send a request to SO with the parameter "aLaCarte": false when instantiationType is Macro in service definition file

          In macro mode, the SO request may also contain, in the "userParams" section, all needed information about VNFs and VF-module(s) to be instantiated.

          All those necessary information are in the Tosca service definition file generated by SDC.

          If NBI do not fill those information, the serviceOrder sent to NBI will have to provide those informations (that means an external system will have to do the job)

          REQUEST 2 : NBI to look at VNF, VF-module and Network in the Tosca service definition file in order to build the full "macro" request toward SO.

      • Relevance:
      • Complexity: High
      • Prerequisites: 
      • Resources: Romain and Rene
    • Update serviceOrder API to use GR_API
      
      • Description: 

        • SO can use two kind of API with SDNC : Generic-Resource API (GR_API) or VNF_API

          .It seems that it is better to indicate to SO to use GR_API now.

          It is the value of the field "testApi" that need to be modified in SO request to instantiate service object.

          Can be an environment variable.

      • Relevance:
      • Complexity: Easy
      • Prerequisites: 
      • Resources: Romain
    • Update ServiceOrder to accommodate Service Characteristics of "object" type
      
      • Description: 

        • Need to handle service orders which use "object" type in the serviceCharacteristics, i.e. utiizing the new specificationInputSchema  

          also update the object to be stored as "object" v "Object" in the service catalog response.

      • Relevance:
      • Complexity: Easy
      • Prerequisites: 
      • Resources: Adrian O'Sullivan
  • Performance Management (specification focus) (stretch goal: implementation associated with Network Slicing KPI reporting)
  • Integration 
    • Integrate External API/NBI within ONAP DMaap for authenticated topics ( Adrian )
    • Integrate External API/NBI with AAF for security enhancement  ( Matthieu )

...

The existing use cases are still going to be supported and additional use cases will be supported for the Frankfurt Release (as defined by the Control loop sub committee and TSC). Network Slicing Use case is a new use case which have plans to use External API Service Order APIs.

Minimum Viable Product

• Documentation of User Stories; Use Cases and Interactions (e.g., swagger ); Data Models (e.g., JSON); Interface Profiles and Functional Definition; 
• ONAP Component Mapping and Functional Analysis; 
• Code contribution for External API Agent functionality.

Functionalities

List the functionalities that this release is committing to deliver by providing a link to JIRA Epics and Stories. In the JIRA Priority field, specify the priority (either High, Medium, Low). The priority will be used in case de-scoping is required. Don't assign High priority to all functionalities.

...