...
- Still valid the startPhase definition for backward compatibility;
- Using startPhase and stepPhase in a composition definition is not valid;
- stepPhase is configured in composition definition element;
- Any composition definition element could have different sptePhase for each operation: for example the order for deploy could different for migrate;
- Any instance element could be executed more then one time;
- All instance elements whit same stepPhase are executed at same time in parallel;
- stepPhase has not reversal order.
Example of composition definition element stepPhase property:
| Code Block | ||
|---|---|---|
| ||
properties:
stepPhase:
- deploy: [0,1]
- migrate: [0,2]
- undeploy: [01]
- delete: [1] |
All not defined operations will be set to 0.
The table below shows the stepPhase for each Composition Definition Element
| Composition Definition Element | stepPhase |
|---|---|
| A1 | 0, 2 |
| A2 | 0, 2 |
| B | 1 |
When an instance element has completed a step, not means that the full implementation is completed (DEPLOYED state).
During the execution of the operation how the user is able to see the steps executed by the instance element? Same issue for monitoring, it needs new filed into Instance Element to store what step is executed.