...
CPS-Core exposes REST endpoints for creating and querying CPS data which can be invoked by http participant with few limitations.
Limitations:
Creating Schema set
Creating schema set requires sending multipart file (yang model) in the REST request which is is not supported by ACM http participant.
POST: /v2/dataspaces/{dataspace-name}/schema-sets
Forwarding the queried CPS data to other components is not supported.
Http participant doesn't forward the response/result to other components. It only executes the request and prints the results.
- We may require to perform sequence of REST operations by creating dataspace, schemaset and anchors in CPS for a single microservice. This might increase the complexity of tosca template for http participant.
- Http participant doesn't support on-request REST call invocation in the ACM RUNNING state. It fires all the requests when initialized and doesn't take any further request during runtime. (Works based on Tosca template, no endpoints exposed)
CPS participant design considerations:
Require to support multiform data in REST request for creating schema set.
On-demand support for querying CPS data during runtime ?
Expose endpoints in CPS participant that are to be used by microservices in ACM ?
How to make the microservices in ACM talk to the CPS participant for sending CPS requests?