...
1. Participant State Change : This message handles states of a participant. Runtime can order participant for a state change.
ParticipantState can be set to one of the following
UNKNOWN : Control Loop execution is unknown.
PASSIVE : Control Loop execution is always rejected.
SAFE : Control Loop execution proceeds, but changes to domain state or context are not carried out.
The The participant returns an indication that it is running in SAFE mode together with the action it would
have have performed if it was operating in ACTIVE mode.
TEST : Control Loop execution proceeds and changes to domain and state are carried out in a test environment.
The The participant returns an indication that it is running in TEST mode together with the action it has performed
on on the test environment
ACTIVE : Control Loop execution is executed in the live environment by the participant.
TERMINATED : Control Loop execution is terminated and not available.
2. Control Loop Update: This message creates the control loop elements and brings them from UNINITIALISED UNINITIALIZED to PASSIVE state.
ControlLoopUpdate message contains full ToscaServiceTemplate describing all components participanting participating in a control loop.
This acts as a template for any control loop to be created according to the template.
When participant-intermediary receives this message, it triggers creation of policy-types and policies in Policy-Framework by Policy-Participant,
and deploys DCAE from DCAE-participant
3. Control Loop State change: This message is used to order a state change in control loop element.
Runtime can order one of the following ordered states.
UNINITIALISED UNINITIALIZED : The control loop or control loop element should become uninitialised uninitialized on participants, it should not exist on participants.
PASSIVE : The control loop or control loop element should initialised initialized on the participants and be passive, that is,
it it is not handling control loop messages yet.
RUNNING : The control loop or control loop element should running and is executing control loops. Once any of above states are ordered, then control loop element transitions into
UNINITIALISED UNINITIALIZED : The control loop or control loop element is not initialised initialized on participants, it does not exist on participants.
UNINITIALISED2PASSIVE UNINITIALIZED2PASSIVE : The control loop or control loop element is changing from unitialised uninitialized to passive,
it it is being initialised initialized onto participants.
PASSIVE : The control loop or control loop element is initialised initialized on the participants but is passive, that is, it is not
handling handling control loop messages yet.
PASSIVE2RUNNING : The control loop or control loop element is changing from passive to running,
the participants are preparing to execute control loops.
RUNNING : The control loop or control loop element is running and is executing control loops.
RUNNING2PASSIVE : The control loop or control loop element is completing execution of current control loops but
will not start running any more control loops and will become passive.
PASSIVE2UNINITIALISED PASSIVE2UNINITIALIZED : The control loop or control loop element is changing from passive to unitialiseduninitialized,
the control loop is being removed from participants
...
As a response to any of the above message participant returns a Participant Status message, holding respective message response.
Runtime recieved receives Participant Status message and stores relavent relevant information in database, Or performs respective actions.
4.2.2: Policy Participant Agent
Policy participant recieves receives messages through participant-intermediary common code, and handles them by invoking REST APIs towards policy-framework.
For example, When a ControlLoopUpdate message is recieved received by policy participant, it contains full ToscaServiceTemplate describing all components
participating in a control loop. When the control loop element state changed from UNINITIALISED UNINITIALIZED to PASSIVE, Policy-participant triggers creation
of policy-types and policies in Policy-Framework.
When the state changes from PASSIVE to UNINITIALISEDUNINITIALIZED, Policy-Participant deletes the policies, policy-types by invoking REST APIs towards policy-framework.
4.2.4: DCAE Participant Agent
DCAE participant recieves receives messages through participant-intermediary common code, and handles them by invoking CLAMP DCAE methods,
which internally work towards DCAE.
For example, When a ControlLoopUpdate message is recieved received by DCAE participant, it contains full ToscaServiceTemplate describing all components
participating in a control loop. When the control loop element state changed from UNINITIALISED UNINITIALIZED to PASSIVE, DCAE-participant triggers deploy
of DCAE.
When the state changes from PASSIVE to UNINITIALISEDUNINITIALIZED, DCAE-Participant undeployes un-deploys DCAE by invoking methods towards CLAMP.
4.2.5:
...
Kubernetes Participant Agent
Kubernates Kubernetes participant recieves receives messages through participant-intermediary common code, and handles them by invoking Kubernetes Open API.
For example, When a ControlLoopUpdate message is recieved received by Kubernates Kubernetes participant, When the control loop element state changed from UNINITIALISED UNINITIALIZED to PASSIVE, KubernatesKubernetes-participant triggers Kubernetes Open API and passes the HELM charts towards cluster.
...