...
A call to the update endpoint for a Control Loop Instance follow the semantics described here: TOSCA Defined Control LoopLoops: Architecture and DesignDesign#4.1Upgrade.
Instantiation Control Loop Instance Lifecycle Management
This sub API is used to manage the life cycle of Control Loop Instances. A Control Loop Instance can be in the states described here: TOSCA Defined Control LoopLoops: Architecture and DesignDesign#2.1:ControlLoopInstanceStates. Managing the life cycle of a Control Loop Instance amounts to steering the Control Loop through its states.
The sub API allows upgrades and downgrades of Control Loop Instances to be pushed to participants following the semantics described here: TOSCA Defined Control LoopLoops: Architecture and DesignDesign#4.1Upgrade. When the API is used to update the participants on a Control Loop Instance, the new/upgraded/downgraded definition of the Control Loop is pushed to the participants. Note that the API asks the participants in a Control Loop Instance to perform the update, it is the responsibility of the participants to execute the update and report the result using the protocols described here: CLAMP Participants. The progress and result of an update can be monitored using the REST APIs for CLAMP Control Loops.
...
The Monitoring API allows the state and statistics of Participants, Control Loop Instances and their Control Loop Elements to be monitored. This API is used by the CLAMP GUI. The API provides filtering so that specific Participants and Control Loop Instances can be retrieved. In addition, the quantity of statistical information to be returned can be scoped.
...
Pass Through API
This API allows information to be passed to Control Loop Elements in a control loop.
...