2b0242f645
This commit switching tasks resolution approach to the tags based one. Tag - minimal unit what's necessary only for task resolution and can be mapped to the node through the role interface only. Each role provides set of tags in its 'tags' field and may be modified via role API. Tag may be created separately via tag API, but, this tag can not be used unless it's stuck to the role. Change-Id: Icd78fd124997c8aafb07964eeb8e0f7dbb1b1cd2 Implements: blueprint role-decomposition |
||
---|---|---|
bin | ||
debian | ||
docs | ||
nailgun | ||
specs | ||
systemd | ||
.gitignore | ||
.gitreview | ||
LICENSE | ||
MAINTAINERS | ||
README.md | ||
build_docs.sh | ||
run_tests.sh | ||
tox.ini |
README.md
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