8306fa17eb
* This patch removes the approach with DB polling needed to
determine if a "join" task is ready to run. Instead of running
a periodic scheduled job, each task completion now runs the
algorithm that finds all potentially affected join tasks
and schedules just one job (instead of a periodic job) to check
their readiness.
This solves a problem of system cascaded overloading in case of
having many very large joins (when a workflow has many joins with
many dependencies each). Previously, in such case Mistral created
too many periodic jobs that just didn't let the workflow progress
well, i.e. most CPU was used by scheduler to run those periodic
jobs that very rarely switched "join" tasks to the RUNNING state.
Change-Id: I5ebc44c7a3f95c868d653689dc5cea689c788cd0
Closes-Bug: #1799356
(cherry picked from commit
|
||
---|---|---|
api-ref/source | ||
devstack | ||
doc | ||
etc | ||
functionaltests | ||
mistral | ||
playbooks | ||
rally-jobs | ||
releasenotes | ||
tools | ||
.coveragerc | ||
.dockerignore | ||
.gitignore | ||
.gitreview | ||
.stestr.conf | ||
.zuul.yaml | ||
CONTRIBUTING.rst | ||
HACKING.rst | ||
LICENSE | ||
README.rst | ||
lower-constraints.txt | ||
requirements.txt | ||
run_functional_tests.sh | ||
run_tests.sh | ||
setup.cfg | ||
setup.py | ||
test-requirements.txt | ||
tox.ini |
README.rst
Team and repository tags
Mistral
Workflow Service for OpenStack cloud. This project aims to provide a mechanism to define tasks and workflows without writing code, manage and execute them in the cloud environment.
Project Resources
Mistral Official Documentation
Project status, bugs, and blueprints are tracked on Launchpad
CloudFlow: visualization tool for workflow executions on https://github.com/nokia/CloudFlow
Additional resources are linked from the project Wiki page
Apache License Version 2.0 http://www.apache.org/licenses/LICENSE-2.0
Release notes for the project can be found at: https://docs.openstack.org/releasenotes/mistral/