...
1 – External Third party domain exports it service catalog details to Telstra. Telstra orchestrator ONAP exposes TMF Open API 633 Service Catalog API via ONAP Ext API component. Third Party Domain leverages the API 633 to POST the Service Catalog payload.
POST nbi/api/v3v2/serviceSpecification
Request body –ONAP compatible Service CSAR / (json ??)CSAR – TMF 633 Service Catalog compatible payload
Payload contents:
RFSS for Partner Domain Service
...
- Expose POST functionality of SDC Onboarding API as an external API within ONAP
- Reuse sdc-dao to update the Cassandra database and store the new service in SDC catalog
- Reuse SDC distribution functionality to distribute the new service to registered ONAP components (no change )
- Existing UUID creation logic will be used
- Last mile access service from 3rd party will be used for detailed analysis and reference implementation
- TOSCA based onboarding in work in progress in SDC, it supports heat based only. The TOSCA based work is ongoing separately in Modeling project. This dependency on Modeling project need to be looked into.
- SDC UI Impact analysis is in-progress to identify how to segregate the Third Party services from other services which will have more VF level details associated with them.
Video showing service on-boarding and reuse in service definition ( in SDC local instance setup at Telstra) :
Attached video takes us through the service creation journey, from creation to distribution-approved, in SDC with the help of the API and SDC UI
View file name onap-sdc-servicecreation.mp4 height 250
Below video shows an example of how the imported service definition can be used to create a composite service
View file name onapdemo-composite-service.mp4 height 250
Possible Approaches for 3rd Party Catalog Sync Entity
...
- Onboard the service in ONAP SDC as a Service, will require updates to Service onboarding API (proposed)
Possible Approaches for 3rd Party Catalog payload Option
...
- Leveraging existing approach for Ext API / NBI
- ExtAPI / NBI will need to convert JSON to YAML for SDC Consumptionsend the JSON in SDC compatible format for its Consumption in v1/catalog/services
Payload Option 1: CSAR
- Potential reuse from TOSCA onboarding Project in SDC
- This might alter existing Ext API / NBI approach
- There would be additional implementation at Third Party end to generate higher level TOSCA
...