opendev/system-config
Code Issues Proposed changes

More bifrost details for infracloud

Browse Source 
Clarify that we only have a single baremetal controller, not one per
site. Also add detail on how one can interact with the bifrost ironic
server.

Change-Id: I1a86ccfe5d6c87894ac040760e43d8fed31340d7
This commit is contained in:
Clark Boylan 2017-01-09 08:23:10 -08:00
parent c15b312e1a
commit 246a5b78ea
1 changed files with 7 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
doc/source/infra-cloud.rst
View File

@ -88,14 +88,19 @@ possible. In the future the cloud may be continuously deployed.
Management
----------
* A "Ironic Controller" machine is installed by hand into each site. That
machine is enrolled into the puppet/ansible infrastructure.
* Currently a single "Ironic Controller" is installed by hand and used by both
sites. That machine is enrolled into the puppet/ansible infrastructure and
can be reached at baremetal00.vanilla.ic.openstack.org.
* The "Ironic Controller" will have bifrost installed on it. All of the
other machines in that site will be enrolled in the Ironic that bifrost
manages. bifrost will be responsible for booting base OS with IP address
and ssh key for each machine.
* You can interact with the Bifrost Ironic installation by sourcing
``/opt/stack/bifrost/env-vars`` then running the ironic cli client (for
example: ``ironic node-list``).
* The machines will all be added to a manual ansible inventory file adjacent
to the dynamic inventory that ansible currently uses to run puppet. Any
metadata that the ansible infrastructure for running puppet needs that