openstack/kolla-ansible
Code Issues Proposed changes

Add missing steps to Vagrant instructions

Browse Source 
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
This commit is contained in:
Doug Szumski 2018-11-19 18:18:13 +00:00
parent 2e629ea866
commit 205df6949c
1 changed files with 14 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
doc/source/contributor/vagrant-dev-env.rst
View File

@ -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** It builds Docker images and pushes them to the local registry if the **push**
option is enabled (in Vagrant this is the default behaviour). 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 Deploying OpenStack with Kolla
------------------------------ ------------------------------
@ -217,7 +226,11 @@ To deploy **all-in-one**:
sudo kolla-ansible deploy 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: For Centos 7: