Use taskflow library for building and executing action plans

Registered by Taylor Peoples on 2015-12-04

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.).

[1] https://wiki.openstack.org/wiki/TaskFlow

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:
milestone icon mitaka-2
Started by
Jean-Emile DARTOIS on 2016-01-13
Completed by
Antoine Cabot on 2016-01-25

Related branches

Sprints

Whiteboard

Gerrit topic: https://review.openstack.org/#q,topic:bp/use-taskflow,n,z

Addressed by: https://review.openstack.org/264142
    Provide a more dynamic Actions management solution

Addressed by: https://review.openstack.org/270642
    WiP Add Schema validator

(?)

Work Items

Dependency tree

* Blueprints in grey have been implemented.

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.