This requirement is for 3rd Party Operational Domain Manager use case. There is a need for Ext API to introduce POST in TMF 633 API in order to automatically upload the 3rd Party's Service Definition into ONAP SDC.

Only the consumers defined in ONAP will have access to post service specification via POST of TMF 633. Refer guiding principles on use case wiki (Controlled access to ONAP SDC Catalog) 

As part of the 3rd Party use case, we propose enhancements to SDC to expose the Service Onboarding API as an external API. That work is planned as part of SDC-2378. Once that is available, NBI will be able to consume it to upload the service definition into SDC. 

The work involves

Introducing POST for TMF 633 API. Currently Ext API only exposes GET.

Translation of the payload from TMF633 format to the SDC format

Consuming the SDC API to create the service definition in SDC.

Sample payloads to ONAP and payload to SDC are attached.

Assumption- For POST to SDC, NBI will send partner service category, as that is the only category for POST.