You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 11 Next »

The CLAMP Automation Composition Runtime Lifecycle Management uses the following system-level dialogues. These dialogues enable the CLAMP runtime capabilities described in Section 2 of TOSCA Defined Automation Compositions: Architecture and Design. Design Time dialogues will be described in future releases of the system.

1 Dialogues on Participants

1.1 Participant Registration

Participant Registration is performed by a Participant when it starts up. It registers its ID and type with the ACM runtime. Participant Participant ACM_Runtime ACM_RuntimeACM_Database ACM_Database Register Create or Update Participant Registration Registration Accepted loop[over all Automation Composition Types] alt[This Automation Composition Type has the Participant Type of this Participant] Trigger Priming of this Automation Composition Type

1.2 Participant Deregistration

Participant Registration is performed by a Participant when it shuts down. It deregisters its ID and type with the ACM runtime. The ACM runtime reprimes any Automation Composition Types that use the participant type of the removed participant because the participants available to the Automation Composition Type  have changed. It also triggers supervision of any AC instances using this particular participant so that the instance can be moved to another participant or can be marked as errored. Participant Participant ACM_Runtime ACM_RuntimeACM_Database ACM_Database Deregister Delete Participant Registration Deregistration Accepted loop[over all Automation Composition Type Definitions] alt[This Automation Composition Type has the Participant Type of this Participant] Trigger Priming of this Automation Composition Type loop[over all Automation Composition Instances] alt[This Automation Composition Instance uses this Participant] Trigger supervision of this Automation Composition Instance

2 Dialogues on Automation Composition Type Definitions

Commissioning dialogues are used to commission and decommission Automation Composition Type definitions and to set the values of Common Parameters.

Commissioning an Automation Composition Type is a three-step process

  1. The Automation Composition Type must be created, that is the Automation Composition Type definition must be loaded and stored in the database. This step may be carried out over the REST interface or using SDC distribution.
  2. The Common Properties of the Automation Composition type must be assigned values and those values must be stored in the database. This step is optional only if all mandatory common properties have default values. The Common Property values may be set and amended over and over again in multiple sessions until the Automation Composition Type is primed.
  3. The Automation Composition Type Definition and the Common Property values must be primed, which is sent to the concerned participants. Once an Automation Composition Type is primed, its Common Property values can no longer be changed. To change Common Properties on a primed Automation Composition Type, all instances of the Automation Composition Type must be removed and the Automation Composition Type must be de-primed.

2.1 Commissioning an Automation Composition Type Definition using the ACM REST Interface

PlantUML 1.2023.12 <b>This version of PlantUML is 301 days old, so you should<b>consider upgrading from https://plantuml.com/download [From string (line 5) ] @startumlparticipant RESTparticipant ACM_Runtimedatabase ACM_Database  REST -> ACM_Runtime: Commission Automation Composition Type DefinitionSyntax Error?

2.2 Commissioning an Automation Composition Type Definition using SDC

SDC SDC Policy_Distribution Policy_Distribution ACM_Runtime ACM_Runtime [DMaaP] CSAR containing Automation Composition Type Definition Commission Automation Composition Type Definition(See Commissioning Sequence Diagram) Result of commissioning [DMaaP] Return result of Deployment

2.3 Deleting an Automation Composition Type Definition

CLAMP_GUI CLAMP_GUI CLAMP_Runtime CLAMP_Runtime Participant ParticipantACM_Database ACM_Database [REST] Read Automation Composition Type Definitions Read Automation Composition Type Definitions [REST] Type Definitions returned Select Automation Composition Type Definition for Parameterization [REST] Fetch GUI fields for Common Parameter Definitions alt[Automation Composition Type Definition not Commissioned on Participants] Read Automation Composition Type Definition Generate fields for Common Parameters for GUI [REST] Return GUI fields Common Parameter Definitions Render UI for Common Parameters Get values for Common Parameters from user [REST] Set values for Common Parameters Store values for Common Parameters [REST] Common Parameter values stored [Automation Composition Type Definition already Commissioned on Participants] [REST] Cannot set Common Parameters onAutomation Composition Type Definition that hasbeen commissioned on participants

2.4 Priming an Automation Composition Type Definition on Participants

The Priming operation sends Automation Composition Type definitions and common property values to participants. Once an Automation Composition Type definition is primed, its property values can on longer be changed until it is de-primed. CLAMP_GUI CLAMP_GUI CLAMP_Runtime CLAMP_Runtime Participant ParticipantACM_Database ACM_Database Participants Participants [REST] Read Automation Composition Type Definitions Read Automation Composition Type Definitions [REST] Type Definitions returned Select Automation Composition Type Definition for Priming on Participants [REST] Prime Automation Composition Type Definition on Participants alt[Automation Composition Type Definition not Primed on Participants] Read Automation Composition Type Definition Read Common Parameter Values for Automation Composition Type Definition alt[Common Parameter values set for Automation Composition Type Definition] [DMaaP] Update Participants with Automation Composition Type Definition and values for Common Parameters [REST] Automation Composition Type Definition priming ordered on participants [Automation Composition Type Definition already primed on Participants] [REST] Common Parameters not seton Automation Composition Type Definition [Automation Composition Type Definition already primed on Participants] [REST] Cannot set Common Parameters onAutomation Composition Type Definition that hasbeen primed on participants Participant Responses [DMaaP] Result of Update with Automation Composition Type Definition and values for Common Parameters Store result of Automation Composition Type Definition Update on Participant Supervision loop[forever] Read Automation Composition Type Definitions loop[over each Automation Composition Type Definition] alt[Automation Composition Type Definition Participant priming underway] read result of Automation Composition Type Definition Updates from participants alt[Updates completed on all participants] set Automation Composition Type Definition as primed on Participants [Updates not completed] alt[Priming of Automation Composition Type Definition on participants timed out] set Automation Composition Type Definition priming as timed out on Participants Log error [Wait for updates to complete] [Automation Composition Type Definition Participant priming not underway]

2.5 De-Prime an Automation Composition Type Definition on Participants

This dialogue allows an Automation Composition Type Definition to be de-primed so that it can be deleted or its common parameter values can be altered.


PlantUML 1.2023.12 <b>This version of PlantUML is 301 days old, so you should<b>consider upgrading from https://plantuml.com/download [From string (line 6) ] @startumlparticipant CLAMP_GUIparticipant CLAMP_Runtimeparticipant Participantdatabase ACM_Database  CLAMP_GUI -> CLAMP_Runtime: [REST] Read Automation Composition Type DefinitionsSyntax Error?

2.6 Decommissioning an Automation Composition Type Definition in CLAMP

PlantUML 1.2023.12 <b>This version of PlantUML is 301 days old, so you should<b>consider upgrading from https://plantuml.com/download [From string (line 5) ] @startumlparticipant CLAMP_GUIparticipant CLAMP_Runtimedatabase ACM_Database  CLAMP_GUI -> CLAMP_Runtime: [REST] Read Automation Composition Type DefinitionsSyntax Error?

2.7 Reading Commissioned Automation Composition Type Definitions

PlantUML 1.2023.12 <b>This version of PlantUML is 301 days old, so you should<b>consider upgrading from https://plantuml.com/download [From string (line 5) ] @startumlparticipant CLAMP_GUIparticipant CLAMP_Runtimedatabase ACM_Database  CLAMP_GUI -> CLAMP_Runtime: [REST] Read Automation Composition Type DefinitionsSyntax Error?

3. Instantiation Dialogues

Instantiation dialogues are used to create, set parameters on, instantiate, update, and remove Automation Composition instances.

Assume a suitable Automation Composition Definition exists in the Commissioned Automation Composition Inventory. To get an Automation Composition instance running one would, for example, execute dialogues 2.1, 2.3, and 2.4.

3.1 Creating an Automation Composition Instance

PlantUML 1.2023.12 <b>This version of PlantUML is 301 days old, so you should<b>consider upgrading from https://plantuml.com/download [From string (line 5) ] @startumlparticipant CLAMP_GUIparticipant CLAMP_Runtimedatabase ACM_Database database ACM_Database  CLAMP_GUI -> CLAMP_Runtime: [REST] Read Automation Composition Type Definit ...Syntax Error?

Note that this dialogue creates the Automation Composition Instance in the Instantiated Automation Composition Inventory. The instance is sent to the participants using the process described in the dialogue in Section 2.3.

3.2 Updating Instance Specific Parameters on an Automation Composition Instance

PlantUML 1.2023.12 <b>This version of PlantUML is 301 days old, so you should<b>consider upgrading from https://plantuml.com/download [From string (line 5) ] @startumlparticipant CLAMP_GUIparticipant CLAMP_Runtimedatabase ACM_Database  CLAMP_GUI -> CLAMP_Runtime: [REST] Read Automation Composition InstancesSyntax Error?

3.3 Updating an Automation Composition Instance with a Configuration on Participants

PlantUML 1.2023.12 <b>This version of PlantUML is 301 days old, so you should<b>consider upgrading from https://plantuml.com/download [From string (line 6) ] @startumlparticipant CLAMP_GUIparticipant CLAMP_Runtimeparticipant Participantdatabase ACM_Database  CLAMP_GUI -> CLAMP_Runtime: [REST] Read all configuration versions of Automation Composition Inst ...Syntax Error?

3.4 Changing the state of an Automation Composition Instance on Participants

PlantUML 1.2023.12 <b>This version of PlantUML is 301 days old, so you should<b>consider upgrading from https://plantuml.com/download [From string (line 6) ] @startumlparticipant CLAMP_GUIparticipant CLAMP_Runtimeparticipant Participantdatabase ACM_Database  CLAMP_GUI -> CLAMP_Runtime: [REST] Read all Instantiated Automation Composition InstancesSyntax Error?

3.5 De-instantiating an Automation Composition Instance from Participants

PlantUML 1.2023.12 <b>This version of PlantUML is 301 days old, so you should<b>consider upgrading from https://plantuml.com/download [From string (line 6) ] @startumlparticipant CLAMP_GUIparticipant CLAMP_Runtimeparticipant Participantdatabase ACM_Database  CLAMP_GUI -> CLAMP_Runtime: [REST] Read all Instantiated Automation Composition InstancesSyntax Error?

3.6 Deleting an Automation Composition Instance

PlantUML 1.2023.12 <b>This version of PlantUML is 301 days old, so you should<b>consider upgrading from https://plantuml.com/download [From string (line 5) ] @startumlparticipant CLAMP_GUIparticipant CLAMP_Runtimedatabase ACM_Database  CLAMP_GUI -> CLAMP_Runtime: [REST] Read all Automation Composition InstancesSyntax Error?

3.7 Reading Automation Composition Instances

PlantUML 1.2023.12 <b>This version of PlantUML is 301 days old, so you should<b>consider upgrading from https://plantuml.com/download [From string (line 5) ] @startumlparticipant CLAMP_GUIparticipant CLAMP_Runtimedatabase ACM_Database  CLAMP_GUI -> CLAMP_Runtime: [REST] Read all Automation Composition InstancesSyntax Error?

3. Monitoring Dialogues

Monitoring dialogues are used to monitor and read statistics on Automation Composition Instances.

3.1 Reporting of Monitoring Information and Statistics by Participants

PlantUML 1.2023.12 <b>This version of PlantUML is 301 days old, so you should<b>consider upgrading from https://plantuml.com/download [From string (line 5) ] @startumlparticipant CLAMP_Runtimeparticipant Participantdatabase ACM_Database  Participant -> CLAMP_Runtime: [DMaaP] Participant and Automation Composition Element Monitoring a ...Syntax Error?

3.2 Viewing of Monitoring Information

PlantUML 1.2023.12 <b>This version of PlantUML is 301 days old, so you should<b>consider upgrading from https://plantuml.com/download [From string (line 5) ] @startumlparticipant CLAMP_GUIparticipant CLAMP_Runtimedatabase ACM_Database  == Overview of all Automation Composition Instances ==Syntax Error?

3.2 Viewing of Statistics

PlantUML 1.2023.12 <b>This version of PlantUML is 301 days old, so you should<b>consider upgrading from https://plantuml.com/download [From string (line 5) ] @startumlparticipant CLAMP_GUIparticipant CLAMP_Runtimedatabase ACM_Database  == Statistics of all Automation Composition Instances ==Syntax Error?

3.3 Statistics Housekeeping

PlantUML 1.2023.12 <b>This version of PlantUML is 301 days old, so you should<b>consider upgrading from https://plantuml.com/download [From string (line 4) ] @startumlparticipant CLAMP_Runtimedatabase ACM_Database  == Automation Composition Instance Statistics ==Syntax Error?

4. Supervision Dialogues

Supervision dialogues are used to check the state of Automation Composition Instances and Participants.

4.1 Supervise Participants

PlantUML 1.2023.12 <b>This version of PlantUML is 301 days old, so you should<b>consider upgrading from https://plantuml.com/download [From string (line 4) ] @startumlparticipant CLAMP_Runtimedatabase ACM_Database  loop foreverSyntax Error?

4.2 Supervise Automation Compositions

PlantUML 1.2023.12 <b>This version of PlantUML is 301 days old, so you should<b>consider upgrading from https://plantuml.com/download [From string (line 4) ] @startumlparticipant CLAMP_Runtimedatabase ACM_Database  loop foreverSyntax Error?

  • No labels