From 246a5b78eaec3d6f1fad5a4231da74adaa1c7d66 Mon Sep 17 00:00:00 2001
From: Clark Boylan <clark.boylan@gmail.com>
Date: Mon, 9 Jan 2017 08:23:10 -0800
Subject: [PATCH] More bifrost details for infracloud
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
---
doc/source/infra-cloud.rst | 9 +++++++--
1 file changed, 7 insertions(+), 2 deletions(-)
diff --git a/doc/source/infra-cloud.rst b/doc/source/infra-cloud.rst
index 1e09123c3c..e45bca3ae6 100644
--- a/doc/source/infra-cloud.rst
+++ b/doc/source/infra-cloud.rst
@@ -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