From 205df6949c80576a5320513fd4f1cca5e62d4dbb Mon Sep 17 00:00:00 2001
From: Doug Szumski <doug@stackhpc.com>
Date: Mon, 19 Nov 2018 18:18:13 +0000
Subject: [PATCH] Add missing steps to Vagrant instructions
Add a couple of missing steps to complete a Vagrant deployment. In
the case of the multi-node deployment we could go one step further
and ensure that the supplied inventory matches the default set of
nodes created by Vagrant.
Change-Id: Iee878e26989e92e4de06c071704a6794011b6e58
---
doc/source/contributor/vagrant-dev-env.rst | 15 ++++++++++++++-
1 file changed, 14 insertions(+), 1 deletion(-)
diff --git a/doc/source/contributor/vagrant-dev-env.rst b/doc/source/contributor/vagrant-dev-env.rst
index 2d70f6c1f7..156f3215bb 100644
--- a/doc/source/contributor/vagrant-dev-env.rst
+++ b/doc/source/contributor/vagrant-dev-env.rst
@@ -208,6 +208,15 @@ Once logged on the **operator** VM call the ``kolla-build`` utility:
It builds Docker images and pushes them to the local registry if the **push**
option is enabled (in Vagrant this is the default behaviour).
+Generating passwords
+--------------------
+
+Before proceeding with the deployment you must generate the service passwords:
+
+.. code-block:: console
+
+ kolla-genpwd
+
Deploying OpenStack with Kolla
------------------------------
@@ -217,7 +226,11 @@ To deploy **all-in-one**:
sudo kolla-ansible deploy
-To deploy multinode:
+To deploy **multinode**:
+
+Ensure that the nodes deployed by Vagrant match those specified in the
+inventory file:
+``/usr/share/kolla-ansible/ansible/inventory/multinode``.
For Centos 7:
--
GitLab