Use taskflow library for building and executing action plans
Action Plans are the equivalent of taskflow's "flows" and individual actions are the equivalent of taskflow's "tasks". The taskflow project [1] has gained significant traction in the past year and is being heavily used across many core projects. We should be using it instead of trying to re-implement only a small subset of what it provides.
This will also create a well-defined interface by the very nature of taskflow (execute, revert, update_progress, etc.) that exploiters can use to define their own implementations of actions (e.g., how to power off a host, add/remove mobile resources, alter fan speed, etc.).
Blueprint information
- Status:
- Complete
- Approver:
- Antoine Cabot
- Priority:
- High
- Drafter:
- Taylor Peoples
- Direction:
- Approved
- Assignee:
- Jean-Emile DARTOIS
- Definition:
- Approved
- Series goal:
- Accepted for mitaka
- Implementation:
-
Implemented
- Milestone target:
-
mitaka-2
- Started by
- Jean-Emile DARTOIS
- Completed by
- Antoine Cabot
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Provide a more dynamic Actions management solution
Addressed by: https:/
WiP Add Schema validator
Work Items
Dependency tree
* Blueprints in grey have been implemented.
