e1ef04492e
Instead of having a ad-hoc state-machine being used to perform the various runtime actions (performed when a engine is ran) we can gain a much more explict execution model by translating that ad-hoc state machine to an explicit one instead... This commit does just that, it adds a new fsm type that can be used to create, define and run state-machines that respond to various events (internal or external) and uses it in the runner action engine module to run the previously ad-hc/implicit state-machine. Implements blueprint runner-state-machine Change-Id: Id35633a9de707f3ffb1a4b7e9619af1be009317f
23 lines
680 B
Plaintext
23 lines
680 B
Plaintext
# The order of packages is significant, because pip processes them in the order
|
|
# of appearance. Changing the order has an impact on the overall integration
|
|
# process, which may cause wedges in the gate later.
|
|
|
|
# Packages needed for using this library.
|
|
anyjson>=0.3.3
|
|
iso8601>=0.1.9
|
|
# Only needed on python 2.6
|
|
ordereddict
|
|
# Python 2->3 compatibility library.
|
|
six>=1.7.0
|
|
# Very nice graph library
|
|
networkx>=1.8
|
|
Babel>=1.3
|
|
# Used for backend storage engine loading.
|
|
stevedore>=0.14
|
|
# Backport for concurrent.futures which exists in 3.2+
|
|
futures>=2.1.6
|
|
# Used for structured input validation
|
|
jsonschema>=2.0.0,<3.0.0
|
|
# For pretty printing state-machine tables
|
|
PrettyTable>=0.7,<0.8
|