...
Only once this done should we be able to trigger migrate.
Assumptions:
- Can we We assume that composition target is already primed?
- Only the participants can execute a Participants execute the effective pre-check.
- Is Pre-check is completely optional? . it will be executed before the migration, if . If it fail or the migration is not supported, can the migration be executed?
- User needs to receive receives the result of the precheck on the outProperties result.
Solution: create a new flow for migration-precheck
...
- User send migration-precheck action
- Acm-runtime set the instance in "MIGRATING-PRECHECK" deployState
- Acm-runtime sends migration-precheck message to participants (it will be AUTOMATION_COMPOSITION_MIGRATION message with Boolean flag "precheck" set to true)
- Participant receives migration-precheck message and executes the precheck and sends the result (it will be a new method "migratePrecheck()" that participant has to implement)
- It will add a new NOT_VALID state in stateChangeResult
- Acm-runtime receives precheck-result messages from all participants
- Acm-runtime shows this result into the stateChangeResult
- NO_ERROR: means the migration is supported (deployState will be in "DEPLOYED")
- NOT_VALID: means the migration is not supported (deployState will be in "DEPLOYED")
- FAILED: means something went wrong during the migration precheck (deployState will be in "MIGRATING-PRECHECK")
- It will be implemented migratePrecheck() in participant-simulator to test all scenarios.
...
| stateChangeResult | deployState | Allowed | Not Allowed Operation | NOT_VALID | DEPLOYED | UPDATE, UNDEPLOY, UNLOCK, MIGRATE_PRECHECK | DELETE, DEPLOY, MIGRATE, LOCK|
|---|---|---|---|---|---|---|---|
| FAILED | MIGRATING-PRECHECK | UNDEPLOY, MIGRATE_PRECHECK | UPDATE, DELETE, DEPLOY, MIGRATE, UNLOCK, LOCK | ||||
| TIMEOUT | MIGRATING-PRECHECK | UNDEPLOY, MIGRATE_PRECHECK | UPDATE, DELETE, DEPLOY, MIGRATE, UNLOCK, LOCK |
...