8e12d76f86
There is the possibility to change OpenStack config after deployment. Changes could be applied per role. And in the case of multiple roles on a node, many changes could pretend to be applied. I.e. if we have a config for the role 'compute', a config for the role 'cinder' and a node with role 'cinder+compute' we have to choose one of them. Previous decision was 'sort it in the lexicographical order', so it applies 'cinder' then --- 'compute'. It is contra intuitive. The best option is applying to a node the last related config, to new config overlaps old ones. Change-Id: I7db388ca3baeb351adc9fdb70c55b0be50fafe48 Closes-bug: #1671521 |
||
---|---|---|
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