Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The body of the create and update end points is a TOSCA Service/Topology template that defines the new or changed Control Loop Type. The update and delete endpoints take a reference to the Control Loop Type. The incoming TOSCA is verified and checked for referential integrity. On delete requests, a check is made to ensure that no Control Loop Instances exist for the Control Loop Type to be deleted.

Image RemovedImage Added

Instantiation API

...

A call to the update endpoint for a Control Loop Instance follow the semantics described here: TOSCA Defined Control Loops: Architecture and Design#4.1Upgrade.

Image RemovedImage Added

Instantiation Control Loop Instance Lifecycle Management

...

The sub API allows upgrades and downgrades of Control Loop Instances to be pushed to participants following the semantics described here: TOSCA Defined Control Loops: Architecture and Design#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 103418132.

The sub API also allows a state change of a Control Loop Instance to be ordered. The required state of the Control Loop Instance is pushed to participants in a Control Loop Instance using the API. Note that the API asks the participants in a Control Loop Instance to perform the state change, it is the responsibility of the participants to execute the state change and report the result using the protocols described here: CLAMP Participants. The progress and result of a state change can be monitored using the REST APIs for CLAMP Control Loops 103418132.

Note

The Swagger for the Instantiation Lifecycle Management API will appear here.

...

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.

Image RemovedImage Added

Pass Through API

...

Sirisha Manchikanti please expand this description.

...


Image Added