...
1. Terminology
Control Loop Type: A set of executing elements on which Life Cycle Management (LCM) is executed collectively. For example, a set of microservices may be spawned and executed together to deliver a service. This collection of services is a control loop
Control Loop Element: A single executing entitity, with its Life Cycle being managed as part of the overall control loop. For example, a single microservice that is executing as one microservice in a service.
CLAMP Control Loop Runtime:The CLAMP server that holds Control Loop Type definitions and manages the life cycle of Control Loop Instances and their Control Loop Elements in cooperation with participants.
Participant: A system or framework that takes part in control loops by executing Control Loop Elements in cooperation with the CLAMP Control Loop Runtime. A participant chooses to partake in control loops, to manage Control Loop Elements for CLAMP, and to receive, send and act on LCM messages for the CLAMP runtime.
Control Loop Type: A definition of a Control Loop in the TOSCA language. This definition describes a certain type of a control loop. The life cycle of instances of a Control Loop Type are managed by CLAMP.
definition of a Control Loop in the TOSCA language. This definition describes a certain type of a control loop. The life cycle of instances of a Control Loop Type are managed by CLAMP.
Control Loop Instance: An instance of a Control Loop Type. The life cycle of a Control Loop Instance is managed by CLAMP. A Control Loop Instance is a set of executing elements on which Life Cycle Management (LCM) is executed collectively. For example, a set of microservices may be spawned and executed together to deliver a service. This collection of services is a control loop.
Control Loop Element Type: A definition of a Control Loop Element in the TOSCA language. This definition describes a certain type of Control Loop Element for a control loop in a Control Loop Type.
Control Loop Element Instance: A single entity executing on a participant, with its Life Cycle being managed as part of the overall control loop. For example, a single microservice that is executing as one microservice in a service.
CLAMP Control Loop Runtime: The CLAMP server that holds Control Loop Type definitions and manages the life cycle of Control Loop Instances and their Control Loop Elements in cooperation with participants.
Participant: A system or framework that takes part in control loops by executing Control Loop Elements in cooperation with the CLAMP Control Loop Runtime. A participant chooses to partake in control loops, to manage Control Loop Elements for CLAMP, and to receive, send and act on LCM messages for the CLAMP runtimeControl Loop Instance: An instance of a Control Loop Type. The life cycle of a Control Loop Instance is managed by CLAMP.
Property: Metadata defined in TOSCA that is associated with a Control Loop, a Control Loop Element, or a Participant.
...