Handling sequence of lifecycle operations
Registered by
Ton Ngo
A TOSCA node can specify any number of lifecycle operations. When the node is deployed, they are executed in a specific sequence, for instance ['create', 'start', 'configure']. This sequence is currently implicit and the knowledge is hard-coded in the translator (hot_resource.py). This sequencing needs to be generalized to allow for different order of execution, or new type of lifecycle operation.
Blueprint information
- Status:
- Not started
- Approver:
- Sahdev Zala
- Priority:
- High
- Drafter:
- Ton Ngo
- Direction:
- Approved
- Assignee:
- Yaoguo Jiang
- Definition:
- Approved
- Series goal:
- None
- Implementation:
-
Not started
- Milestone target:
- None
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
Thomas has created a diagram for it. Matt will email..
Gerrit topic: https:/
Addressed by: https:/
Change lifecycle sequence define
(?)
