The project registers automatically the two Resource Specifications (RSpecs) and we added handler functions for create, update and delete.
So when you create CFSs services using these (RSpecs) the Service Orchestrator will call these functions via the queue
\ No newline at end of file
So when you create CFSs services using these (RSpecs) the Service Orchestrator will call these functions via the queue
See BootstrapService that registers the two RSpecs as LogicalResourceSpecifications
The two classes has function to transform to TMF RSpecs, as well as to save back to OpenSlice their Resource Instances (thus they will go to the inventory)
The ResourceRepoService class has method calls for the handling of the messages from the orchestrator.
Useful metadata are included in some headers of the message:
- important header org.etsi.osl.resourceId is the UUID of the related resource that was created in OpenSlice and reflects the resource that this controller will handle. NOTE: you need to UPDATE this resource back in TMFAPI and set the status at least ResourceStatusType.AVAILABLE or TERMINATED if there are errors, etc
- header org.etsi.osl.serviceOrderId is the UUID of the related service order
- header org.etsi.osl.serviceId is the UUID of the related services
