RETIRED, Fuel UI
Go to file
Alexey Shtokolov b0e9d4f1aa Revert "Restrict usage of controller and osd role on single host"
This reverts commit b433ee89f0.

Change-Id: I3cae65e2f54be550656c79c918a72ea60c3b0ac4
Closes-Bug: 1631878
2016-10-10 14:07:41 +00:00
bin Remove downloading debian-installer components 2016-04-18 10:18:20 +00:00
debian Remove lbound for ohai 2016-06-15 19:50:45 +03:00
docs Move network API handlers to extension 2016-04-27 14:43:42 -07:00
nailgun Revert "Restrict usage of controller and osd role on single host" 2016-10-10 14:07:41 +00:00
specs Remove version cap for python-networkx-core 2016-09-15 20:47:46 +03:00
systemd Systemd support for nailgun services 2015-11-30 13:47:32 +00:00
.gitignore Remove Fuel UI 2016-03-03 12:09:54 +00:00
.gitreview Update .gitreview for new namespace 2015-10-17 22:27:24 +00:00
LICENSE LICENCE added 2014-06-11 17:19:02 +04:00
MAINTAINERS Remove Evgeny from maintainers list for volume_manager 2016-06-23 14:54:54 +00:00
README.md Update README.md 2016-05-23 18:07:36 +03:00
build_docs.sh Deprecate shotgun directory 2015-10-27 13:09:34 +03:00
run_tests.sh Move UI-related testing logic to a separate file 2016-02-25 10:53:19 +00:00
tox.ini run extensions tests in 4 threads 2016-09-05 10:44:45 +00:00

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

http://docs.openstack.org/infra/manual/developers.html