2caa56fa6e
Doing this we avoid inclusion of task cache update statement into the next transaction which may cause different problems such as deadlocks. (update happens inside make_astute_message() function) Change-Id: I865b98beb621bee089cf79f1304498fd3637d64f Closes-Bug: #1618852 |
||
---|---|---|
bin | ||
debian | ||
docs | ||
nailgun | ||
specs | ||
systemd | ||
tools | ||
.gitignore | ||
.gitreview | ||
LICENSE | ||
MAINTAINERS | ||
README.md | ||
build_docs.sh | ||
run_tests.sh | ||
tox.ini |
README.md
Team and repository tags
fuel-web
fuel-web (nailgun) implements REST API and deployment data management. It manages disk volumes configuration data, networks configuration data and any other environment specific data which are necessary for successful deployment. It has required orchestration logic to build instructions for provisioning and deployment in a right order. Nailgun uses SQL database to store its data and AMQP service to interact with workers.
Project resources
Project status, bugs, and blueprints are tracked on Launchpad: https://launchpad.net/fuel
Development documentation is hosted here: https://docs.fuel-infra.org/fuel-dev
Any additional information can be found on the Fuel's project wiki https://wiki.openstack.org/wiki/Fuel
Anyone wishing to contribute to fuel-web should follow the general OpenStack process. A good reference for it can be found here: https://wiki.openstack.org/wiki/How_To_Contribute