How startPhase is currently implemented
Example using the Demo. The table below shows the startPhase for each Composition Definition Element
| Composition Definition Element | startPhase |
|---|---|
| onap.policy.clamp.ac.element.Policy_AutomationCompositionElement | 0 |
| onap.policy.clamp.ac.element.K8S_StarterAutomationCompositionElement | 0 |
| onap.policy.clamp.ac.element.K8S_BridgeAutomationCompositionElement | 0 |
| onap.policy.clamp.ac.element.K8S_SinkAutomationCompositionElement | 0 |
| onap.policy.clamp.ac.element.Http_StarterAutomationCompositionElement | 1 |
| onap.policy.clamp.ac.element.Http_BridgeAutomationCompositionElement | 1 |
| onap.policy.clamp.ac.element.Http_SinkAutomationCompositionElement | 1 |
The diagram below shows the flow of messages:Note:
- startPhase is configured in composition definition element and defines the order of execution of instance elements;
- Any instance element is executed only once;
- All instance elements whit same startPhase are executed at same time in parallel;
- startPhase is used by deploy and unlock; startPhase in reverse order is used by lock, undeploy and delete;
Alternative flow with stepPhase
To maintain the backward compatibility, we are introducing a new property stepPhase.
- 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;
Example of composition definition element stepPhase property:
properties:
stepPhase:
- deploy: [1]
- migrate: [1,2]
- undeploy: [2]
- delete: [2]
During the execution of the operation how the user is able to see the steps executed by the instance element?