...
Below sequence diagrams are depicting the Catalog Sync functionality in more detail:
High level flow of the activities for importing an external Service Catalog into ONAP with Payload Detail
Steps 1 to 3 on previous slide - which are part of new functionality - are explained here.
Steps 4 onward depict existing functionality reused
1 – Invoke TMF 633 Service Catalog API
3rd Party Domain’s Payload to be submitted as a JSON –
Expected format - Service Specification payload specified by TMF 633
2- Ext API to invoke SDC onboarding API to updated ONAP SDC catalog
Invoke ServiceServlet - createService() – JSON payload
Currently on-boarding API is invoked when Create Service button is clicked in SDC UI
Ext API needs to be added as a consumer of the API
Existing logic to be reused:
UUID creation in validateServiceBeforeCreate
Logic to add default TOSCA components
2a – Persist the service in SDC database
3-Ext API will Notify 3rd Party after SDC catalog update
Register for Distribution: Ext API will register itself with SDC.
Ext API will receive distribution notification from SDC after service catalog creation in SDC
Ext API notifies 3rd Party Domain
Project Impact:
Projects impacted as part of sub use case 1
...