...
PNF/VNF : Preference will be to use Fixed Broadband Access Service and associated network functions as reference for this use case. Clearwater IMS will be the backup option
Product Modeling and Distribution:
Work Flows:
The use case is being divided into sub use cases in order to limit the scope of changes for F release.
Import Service Catalog
Submit Order
Interaction Flow
...
...
This sequence diagram depicts external catalog sync into SDC followed by order request from BSS
...
- SDC
- In order to import the Service Catalog, Service load will have to be sent to SDC from Ext API.
- JSON representation of the Service load needs to be identified and agreed with SDC team
SDC Impact analysis:
- 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.
Possible Approaches for 3rd Party Catalog Sync Entity
Entity Option 1 - Resource
- Onboard the resource in ONAP SDC as a VSP, will require updates to VSP onboarding API
Entity Option 2 - Service
- Onboard the service in ONAP SDC as a Service, will require updates to Service onboarding API
Possible Approaches for 3rd Party Catalog payload Option
Payload Option 1: JSON (Proposed)
- Leveraging existing approach for Ext API / NBI
- ExtAPI / NBI will need to convert JSON to YAML for SDC Consumption
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
- (VLM to be manually created and any service coming from 3rd Party domain this should be attached to specific VLM)
Ext API (yet to be analyzed in detail and scoped)
- Introduce POST for TMF API 633 – Service Catalog API
- Realization of POST operation in Ext API will depend on decisions taken during SDC implementation.
- Ext API changes to be planned for future release
Work Commitment:
Telstra team will work on SDC. We welcome partner contributions into this usecase.
...