1 - Invoke External Service Creation API with the payload for Partner Service Definition
POST URL - /sdc/v1/catalog/services
Pre-requisites -
- Input headers same as the ones used by NBI for GET /sdc/v1/catalog/services
- Input payload for Partner Domain Service
- SDC master/frankfurt build containing changes for tickets SDC-2382, SDC-2383 and SDC-2385
Expected Response - 201 Created
The Postman collection for the tests has been uploaded to the ticket SDC-2385
Note - Once the proposed change in EXTAPI-351 is complete, this SDC API can be tested by invoking it from ONAP External API. Meanwhile it can be tested using Postman by invoking the SDC API.
Screenshot of SDC UI showing Partner/3rd party service created using the API in 'Ready for Testing' state
2 - Submit the Service Definition for Testing, Certification and Distribution
Once the service is created via the API, it can be submitted for verification and distribution.
This can be done by logging into the SDC portal or by invoking the SDC internal APIs.
Once the Service is Distributed, it can be used as a component within a composite service.
A Partner Service is a unitary service and it cannot add other services as its components. It can only be added as a component of other composite services or it can be instantiated as a single service
Refer - Sample Internet Service - Service Specifications on Third-party Operational Domain Manager for an example of Partner Domain Service