diff options
| author |   FrancescoFioraEst <francesco.fiora@est.tech> | 2023-09-28 11:00:38 +0100 |
|---|---|---|
| committer | FrancescoFioraEst <francesco.fiora@est.tech> | 2023-09-29 09:42:01 +0100 |
| commit | fa75c54798e1320c1f3e33eb177fb9bd2ec3ac47 (patch) | |
| tree | 8ed464ed80c655cead954655342633ba003e04c9 /docs/clamp/acm/api-protocol | |
| parent | 47d41204a962e150e479f858fbfbcc2ef838caac (diff) | |
Update Documentation for migration
Issue-ID: POLICY-4812
Change-Id: I8adbb39765bba68d0ca33d048c4b96c991129669
Signed-off-by: FrancescoFioraEst <francesco.fiora@est.tech>
Diffstat (limited to 'docs/clamp/acm/api-protocol')
| -rwxr-xr-x | docs/clamp/acm/api-protocol/system-level-dialogues.rst | 30 |
1 files changed, 22 insertions, 8 deletions
diff --git a/docs/clamp/acm/api-protocol/system-level-dialogues.rst b/docs/clamp/acm/api-protocol/system-level-dialogues.rst index 49521882..a2efdc36 100755 --- a/docs/clamp/acm/api-protocol/system-level-dialogues.rst +++ b/docs/clamp/acm/api-protocol/system-level-dialogues.rst @@ -154,7 +154,21 @@ The ACM Runtime receives and stores the responses. .. image:: ../images/system-dialogues/UpdateAcElementsResponse.png -3.5 Undeploy Automation Composition Instance +3.5 Migrate Automation Composition Instance +------------------------------------------- +The user requests the AC Instance to be migrated using a REST endpoint. The ACM Runtime orders the AC Instance to be migrated. + +.. image:: ../images/system-dialogues/MigrateAcInstance.png + +Each participant migrated its AC Element from the AC Instance + +.. image:: ../images/system-dialogues/MigrateAcElements.png + +The ACM Runtime receives and stores the responses. + +.. image:: ../images/system-dialogues/MigrateAcElementsResponse.png + +3.6 Undeploy Automation Composition Instance -------------------------------------------- The user requests the AC Instance to be undeployed using a REST endpoint. The ACM Runtime orders the AC Instance to be undeployed. @@ -168,12 +182,12 @@ The ACM Runtime receives and stores the responses. .. image:: ../images/system-dialogues/UndeployResponseStored.png -3.6 Read Automation Composition Instances +3.7 Read Automation Composition Instances ----------------------------------------- .. image:: ../images/system-dialogues/ReadAcInstances.png -3.7 Unlock Automation Composition Instance +3.8 Unlock Automation Composition Instance ------------------------------------------ The user requests the AC Instance to be unlocked using a REST endpoint. The ACM Runtime orders the AC Instance to be unlocked on Participants. @@ -187,7 +201,7 @@ The ACM Runtime receives and stores the responses. .. image:: ../images/system-dialogues/UnlockResponseStored.png -3.8 Lock Automation Composition Instance +3.9 Lock Automation Composition Instance ---------------------------------------- The user requests the AC Instance to be locked using a REST endpoint. The ACM Runtime orders the AC Instance to be locked on Participants. @@ -201,17 +215,17 @@ The ACM Runtime receives and stores the responses. .. image:: ../images/system-dialogues/LockResponseStored.png -3.9 Update Operational State on Automation Composition Instance ---------------------------------------------------------------- +3.10 Update Operational State on Automation Composition Instance +---------------------------------------------------------------- .. image:: ../images/system-dialogues/UpdateOperationalState.png -3.10 Update Usage State on Automation Composition Instance +3.11 Update Usage State on Automation Composition Instance ---------------------------------------------------------- .. image:: ../images/system-dialogues/UpdateUsageState.png -3.11 Failure handling in ACM +3.12 Failure handling in ACM ---------------------------- After any ACM operation is completed, one of the following result messages will be updated in the ACM. These result values are updated along with the overall state of the ACM instance. |