openstack/openstack-ansible
Code Issues Proposed changes

Document required repository hosts config info

Browse Source 
Installs must have either the repo-infra_hosts list, or the
openstack_repo_url defined. Otherwise, greenfield installations
following our installation docs will fail.

Change-Id: I116040302e846530895836dd8aab9d4136b110af
Closes-Bug: #1475000
(cherry picked from commit 6f0ba63dd1)
This commit is contained in:
Nolan Brubaker 2015-07-15 16:03:25 -04:00 committed by Jesse Pretorius
parent 1bf8902289
commit bd68726369
1 changed files with 66 additions and 36 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

102
doc/source/install-guide/configure-hostlist.rst
View File

@ -22,40 +22,40 @@ suitable short hostname for a compute host might be:
.. code-block:: yaml .. code-block:: yaml
infra_hosts: infra_hosts:
603975-infra01: 603975-infra01:
ip: INFRA01_IP_ADDRESS ip: INFRA01_IP_ADDRESS
603989-infra02: 603989-infra02:
ip: INFRA02_IP_ADDRESS ip: INFRA02_IP_ADDRESS
627116-infra03: 627116-infra03:
ip: INFRA03_IP_ADDRESS ip: INFRA03_IP_ADDRESS
628771-infra04: ... 628771-infra04: ...
Replace *``*_IP_ADDRESS``* with the IP address of the ``br-mgmt`` Replace ``*_IP_ADDRESS`` with the IP address of the ``br-mgmt``
container management bridge on each infrastructure target host. Use container management bridge on each infrastructure target host. Use
the same net block as bond0 on the nodes, for example: the same net block as bond0 on the nodes, for example:
.. code-block:: yaml .. code-block:: yaml
infra_hosts: infra_hosts:
603975-infra01: 603975-infra01:
ip: 10.240.0.80 ip: 10.240.0.80
603989-infra02: 603989-infra02:
ip: 10.240.0.81 ip: 10.240.0.81
627116-infra03: 627116-infra03:
ip: 10.240.0.184 ip: 10.240.0.184
#. Configure a list containing at least one network target host in the #. Configure a list containing at least one network target host in the
``network_hosts`` section: ``network_hosts`` section:
.. code-block:: yaml .. code-block:: yaml
network_hosts: network_hosts:
602117-network01: 602117-network01:
ip: NETWORK01_IP_ADDRESS ip: NETWORK01_IP_ADDRESS
602534-network02: ... 602534-network02: ...
Replace *``*_IP_ADDRESS``* with the IP address of the ``br-mgmt`` Replace ``*_IP_ADDRESS`` with the IP address of the ``br-mgmt``
container management bridge on each network target host. container management bridge on each network target host.
#. Configure a list containing at least one compute target host in the #. Configure a list containing at least one compute target host in the
@ -63,12 +63,12 @@ suitable short hostname for a compute host might be:
.. code-block:: yaml .. code-block:: yaml
compute_hosts: compute_hosts:
900089-compute001: 900089-compute001:
ip: COMPUTE001_IP_ADDRESS ip: COMPUTE001_IP_ADDRESS
900090-compute002: ... 900090-compute002: ...
Replace *``*_IP_ADDRESS``* with the IP address of the ``br-mgmt`` Replace ``*_IP_ADDRESS`` with the IP address of the ``br-mgmt``
container management bridge on each compute target host. container management bridge on each compute target host.
#. Configure a list containing at least one logging target host in the #. Configure a list containing at least one logging target host in the
@ -76,25 +76,55 @@ suitable short hostname for a compute host might be:
.. code-block:: yaml .. code-block:: yaml
log_hosts: log_hosts:
900088-logging01: 900088-logging01:
ip: LOGGER1_IP_ADDRESS ip: LOGGER1_IP_ADDRESS
903877-logging02: ... 903877-logging02: ...
Replace *``*_IP_ADDRESS``* with the IP address of the ``br-mgmt`` Replace ``*_IP_ADDRESS`` with the IP address of the ``br-mgmt``
container management bridge on each logging target host. container management bridge on each logging target host.
#. Configure a list containing at least one repository target host in the
``repo-infra_hosts`` section:
.. code-block:: yaml
repo-infra_hosts:
603975-repo01:
ip: REPO01_IP_ADDRESS
603989-repo02:
ip: REPO02_IP_ADDRESS
627116-repo03:
ip: REPO03_IP_ADDRESS
628771-repo04: ...
Replace ``*_IP_ADDRESS`` with the IP address of the ``br-mgmt``
container management bridge on each repository target host.
The repository typically resides on one or more infrastructure hosts.
Alternatively, specify a value for the ``openstack_repo_url`` variable
in the ``/etc/openstack_deploy/user_group_vars.yml`` file. The value should
contain a URL for a host with the appropriate repository layout. For
example:
.. code-block:: yaml
openstack_repo_url: "https://rpc-repo.rackspace.com/"
Using ``repo-infra_hosts`` configures a local repository with the
appropriate layout and sets ``openstack_repo_url`` for you.
#. Configure a list containing at least one optional storage host in the #. Configure a list containing at least one optional storage host in the
``storage_hosts`` section: ``storage_hosts`` section:
.. code-block:: yaml .. code-block:: yaml
storage_hosts: storage_hosts:
100338-storage01: 100338-storage01:
ip: STORAGE01_IP_ADDRESS ip: STORAGE01_IP_ADDRESS
100392-storage02: ... 100392-storage02: ...
Replace *``*_IP_ADDRESS``* with the IP address of the ``br-mgmt`` Replace ``*_IP_ADDRESS`` with the IP address of the ``br-mgmt``
container management bridge on each storage target host. Each storage container management bridge on each storage target host. Each storage
host also requires additional configuration to define the back end host also requires additional configuration to define the back end
driver. driver.