diff options
Diffstat (limited to 'docs/clamp/acm/design-impl')
| -rw-r--r-- | docs/clamp/acm/design-impl/clamp-runtime-acm.rst | 5 | ||||
| -rw-r--r-- | docs/clamp/acm/design-impl/participants/participant-intermediary.rst | 24 |
2 files changed, 20 insertions, 9 deletions
diff --git a/docs/clamp/acm/design-impl/clamp-runtime-acm.rst b/docs/clamp/acm/design-impl/clamp-runtime-acm.rst index ba5ffe33..dd6348c8 100644 --- a/docs/clamp/acm/design-impl/clamp-runtime-acm.rst +++ b/docs/clamp/acm/design-impl/clamp-runtime-acm.rst @@ -123,7 +123,9 @@ Delete of a Automation Composition Instance - GUI calls DELETE "/onap/policy/clamp/acm/v2/compositions/{compositionId}/instances/{instanceId}" endpoint - runtime-ACM receives the call by Rest-Api (InstantiationController) - It checks that AC Instance is in UNDEPLOYED deployState -- It deletes the AC Instance from DB +- It updates the AC Instance to DB with DELETING deployState +- It triggers the execution to send a broadcast AUTOMATION_COMPOSITION_STATE_CHANGE message +- the message is built by AutomationCompositionStateChangePublisher using Instance data. (with startPhase = last StartPhase) Depriming of a Automation Composition Definition Type +++++++++++++++++++++++++++++++++++++++++++++++++++++ @@ -242,6 +244,7 @@ Monitoring is designed to process the follow operations: - to determine the next startPhase in a AUTOMATION_COMPOSITION_DEPLOY message - to update AC deployState: in a scenario that "AutomationComposition.deployState" is in a kind of transitional state (example DEPLOYING), if all - AC elements are moved properly to the specific state, the "AutomationComposition.deployState" will be updated to that and saved to DB - to update AC lockState: in a scenario that "AutomationComposition.lockState" is in a kind of transitional state (example LOCKING), if all - AC elements are moved properly to the specific state, the "AutomationComposition.lockState" will be updated to that and saved to DB +- to delete AC Instance: in a scenario that "AutomationComposition.deployState" is in DELETING, if all - AC elements are moved properly to DELETED, the AC Instance will be deleted from DB - to retry AUTOMATION_COMPOSITION_DEPLOY/AUTOMATION_COMPOSITION_STATE_CHANGE messages. if there is a AC Element not in the proper state, it will retry a broadcast message The solution Design of retry, timeout, and reporting for all Participant message dialogues are implemented into the monitoring execution. diff --git a/docs/clamp/acm/design-impl/participants/participant-intermediary.rst b/docs/clamp/acm/design-impl/participants/participant-intermediary.rst index 6ebc76f9..53215389 100644 --- a/docs/clamp/acm/design-impl/participants/participant-intermediary.rst +++ b/docs/clamp/acm/design-impl/participants/participant-intermediary.rst @@ -64,31 +64,39 @@ DePrime of an Automation Composition Definition Type - the message is built by ParticipantPrimePublisher with an empty list of ParticipantDefinition - Participant-intermediary will receive a PARTICIPANT_PRIME message and deletes the Tosca Service Template data on ParticipantHandler -Design of "issues automation composition commands to automation compositions" - case UNDEPLOY to DEPLOY -------------------------------------------------------------------------------------------------------- +Design of "issues automation composition commands to automation compositions" - case UNDEPLOYED to DEPLOYED +----------------------------------------------------------------------------------------------------------- - AUTOMATION_COMPOSITION_DEPLOY message with instantiation details and DEPLOY order state is sent to participants - Participant-intermediary validates the current deployState change - Participant-intermediary will receive AUTOMATION_COMPOSITION_DEPLOY message and sends the details of AutomationCompositionElements to participants - Each participant performs its designated job of deployment by interacting with respective frameworks -Design of "issues automation composition commands to automation compositions" - case DEPLOY to UNDEPLOY -------------------------------------------------------------------------------------------------------- +Design of "issues automation composition commands to automation compositions" - case DEPLOYED to UNDEPLOYED +----------------------------------------------------------------------------------------------------------- - AUTOMATION_COMPOSITION_STATE_CHANGE message with instantiation details and UNDEPLOY order state is sent to participants - Participant-intermediary validates the current deployState change - Participant-intermediary will receive AUTOMATION_COMPOSITION_STATE_CHANGE message and sends AC-element details to participants - Each participant performs its designated job of undeployment by interacting with respective frameworks -Design of "issues automation composition commands to automation compositions" - case LOCK to UNLOCK ---------------------------------------------------------------------------------------------------- +Design of "issues automation composition commands to automation compositions" - case LOCKED to UNLOCKED +------------------------------------------------------------------------------------------------------- - AUTOMATION_COMPOSITION_STATE_CHANGE message with instantiation details and UNLOCK order state is sent to participants - Participant-intermediary validates the current lockState change - Participant-intermediary will receive AUTOMATION_COMPOSITION_STATE_CHANGE message -Design of "issues automation composition commands to automation compositions" - case UNLOCK to LOCK ---------------------------------------------------------------------------------------------------- +Design of "issues automation composition commands to automation compositions" - case UNLOCKED to LOCKED +------------------------------------------------------------------------------------------------------- - AUTOMATION_COMPOSITION_STATE_CHANGE message with instantiation details and LOCK order state is sent to participants - Participant-intermediary validates the current lockState change +Design of Delete - case UNDEPLOYED to DELETED +--------------------------------------------- +- AUTOMATION_COMPOSITION_STATE_CHANGE message with instantiation details and DELETE order state is sent to participants +- Participant-intermediary validates the current deployState change +- Participant-intermediary will receive AUTOMATION_COMPOSITION_STATE_CHANGE message and sends AC-element details to participants +- Each participant performs its designated job of removing instantiation data if not done in undeployment +- Participant-intermediary will remove instantiation data + Design of a PARTICIPANT_STATUS_REQ message ------------------------------------------ - AC-runtime triggers the execution to send a broadcast PARTICIPANT_STATUS_REQ message or to send it to a specific participant |