28dd1ff3a1
Added new API handler /extensions/ which returns a list of available extensions. Co-Authored-By: Sylwester Brzeczkowski <sbrzeczkowski@mirantis.com> Change-Id: I072f3e4d9cd8f71498a20312af7c2016e951456d Implements: blueprint extensions-management Partial-Bug: #1614526 |
||
---|---|---|
bin | ||
debian | ||
docs | ||
nailgun | ||
specs | ||
systemd | ||
.gitignore | ||
.gitreview | ||
build_docs.sh | ||
LICENSE | ||
MAINTAINERS | ||
README.md | ||
run_tests.sh | ||
tox.ini |
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