9dabe06369
This patch adds support to deploy Ironic with separate Neutron network for provisioning baremetal instances. * Add NetworkDeploymentSerializer100 as Ironic multitenancy is supported from Newton, and we will backport this till stable/newton. * Update network scheme generation to create 'vlan' baremetal network, assign IPs to Ironic conductors from this network, make them accessible from baremetal servers. * Add new checkbox at 'Openstack Settings/Additional components' tab which allows to define if separate provisioning network should be used during deployment. This is a trigger to switch ironic deployment to multitenancy case. If not selected old behaviour is kept, 'flat' network is used. The checkbox is shown only when Ironic component is enabled. Change-Id: I861a8b3b046202526d6a856c9f2dca2cfaddc887 Related-Bug: #1588380 |
||
---|---|---|
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