...
- 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.
- Created epic https://jira.onap.org/browse/SDC-23782378
- We should add metadata in SDC Service metadata definition which indicates whether a service is CFS (public) or RFS (private)
Video showing service on-boarding and reuse in service definition ( in SDC local instance setup at Telstra) :
...