Use a explicit state machine when running workflows

Registered by Joshua Harlow

The current action engine runner uses an implicit state machine, this makes it difficult to read and understand. It would benefit from a explicit state machine with well defined transitions. This also is a good starting point to introduce a state machine type that can be used more extensively in taskflow (and elsewhere) as the concept/code gets flushed out (we have to start somewhere to get somewhere else, so this baby step seems like a good starting point, and one that is key to how taskflow runs workflows).

Blueprint information

Status:
Complete
Approver:
None
Priority:
Medium
Drafter:
Joshua Harlow
Direction:
Approved
Assignee:
Joshua Harlow
Definition:
Approved
Series goal:
Accepted for 0.4
Implementation:
Implemented
Milestone target:
None
Started by
Joshua Harlow
Completed by
Joshua Harlow

Related branches

Sprints

Whiteboard

Gerrit topic: https://review.openstack.org/#q,topic:fsm,n,z

Addressed by: https://review.openstack.org/106535
    Translate engine runner into a well defined state-machine

Gerrit topic: https://review.openstack.org/#q,topic:bp/runner-state-machine,n,z

Addressed by: https://review.openstack.org/107479
    Ensure state machine can be frozen

Addressed by: https://review.openstack.org/116544
    Tweak engine iteration 'close-up shop' runtime path

Addressed by: https://review.openstack.org/117406
    Move parts of action engine tests to a subdirectory

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.