8a73da20fd
* Fix get task properties, get task in DSL * Evaluating task on success/error/finish properties in engine: - evaluate YAQL conditions - schedule tasks * Unit tests for handling success/error/finish * For real work with context there is need to store it somewhere Implements: blueprint schedule-tasks-after-completion Change-Id: Ia9c34e755055ff0273dcd79a314858dbfbcc2fa9 |
||
---|---|---|
doc/source | ||
etc | ||
mistral | ||
scripts | ||
tools | ||
.gitignore | ||
.gitreview | ||
.pylintrc | ||
AUTHORS | ||
LICENSE | ||
openstack-common.conf | ||
README.rst | ||
requirements.txt | ||
setup.cfg | ||
setup.py | ||
test-requirements.txt | ||
tox.ini |
Mistral
Task Orchestration and Scheduling service for OpenStack cloud
Running in development mode
### Installation First of all, in a shell run:
tox
This will install necessary virtual environments and run all the project tests. Installing virtual environments may take significant time (~10-15 mins).
### Running Mistral API server To run Mistral API server perform the following command in a shell:
tox -evenv -- python mistral/cmd/api.py --config-file path_to_config
Note that an example configuration file can be found in etc/mistral.conf.example.
### Running Mistral Task Executors To run Mistral Task Executor instance perform the following command in a shell:
tox -evenv -- python mistral/cmd/task_executor.py --config-file path_to_config
Note that at least one Executor instance should be running so that workflow tasks are processed by Mistral.