openstack/openstack-ansible
Code Issues Proposed changes

Add documentation for Keystone identity_hosts configuration

Browse Source 
Added a section in configure-hostlist.rst for identity_hosts
Cleaned up documentation for consistency and removal of duplicity

Change-Id: Ib436dd54867d39b4ddfb11970f6bdb1fb485cb99
Closes-Bug: 1550040
This commit is contained in:
Amy Marrich 2016-03-07 14:11:26 -06:00
parent 4ebf7974ef
commit bd3b4bac84
1 changed files with 30 additions and 60 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -17,33 +17,22 @@ prevent length limitation issues with LXC and SSH. For example, a
suitable short hostname for a compute host might be: suitable short hostname for a compute host might be:
``123456-Compute001``. ``123456-Compute001``.
Unless otherwise stated, replace ``*_IP_ADDRESS`` with the IP address of
the ``br-mgmt`` container management bridge on each target host.
#. Configure a list containing at least three infrastructure target #. Configure a list containing at least three infrastructure target
hosts in the ``shared-infra_hosts`` section: hosts in the ``shared-infra_hosts`` section:
.. code-block:: yaml .. code-block:: yaml
shared-infra_hosts: shared-infra_hosts:
603975-infra01: infra01:
ip: INFRA01_IP_ADDRESS ip: INFRA01_IP_ADDRESS
603989-infra02: infra02:
ip: INFRA02_IP_ADDRESS ip: INFRA02_IP_ADDRESS
627116-infra03: infra03:
ip: INFRA03_IP_ADDRESS ip: INFRA03_IP_ADDRESS
628771-infra04: ... infra04: ...
Replace ``*_IP_ADDRESS`` with the IP address of the ``br-mgmt``
container management bridge on each infrastructure target host. Use
the same net block as bond0 on the nodes, for example:
.. code-block:: yaml
shared-infra_hosts:
603975-infra01:
ip: 10.240.0.80
603989-infra02:
ip: 10.240.0.81
627116-infra03:
ip: 10.240.0.184
#. Configure a list containing at least two infrastructure target #. Configure a list containing at least two infrastructure target
hosts in the ``os-infra_hosts`` section (you can reuse hosts in the ``os-infra_hosts`` section (you can reuse
@ -52,28 +41,23 @@ suitable short hostname for a compute host might be:
.. code-block:: yaml .. code-block:: yaml
os-infra_hosts: os-infra_hosts:
603975-infra01: infra01:
ip: INFRA01_IP_ADDRESS ip: INFRA01_IP_ADDRESS
603989-infra02: infra02:
ip: INFRA02_IP_ADDRESS ip: INFRA02_IP_ADDRESS
627116-infra03: infra03:
ip: INFRA03_IP_ADDRESS ip: INFRA03_IP_ADDRESS
628771-infra04: ... infra04: ...
Replace ``*_IP_ADDRESS`` with the IP address of the ``br-mgmt`` #. Configure a list of at least one keystone target host in the
container management bridge on each infrastructure target host. Use ``identity_hosts`` section:
the same net block as bond0 on the nodes, for example:
.. code-block:: yaml .. code-block:: yaml
os-infra_hosts: identity_hosts:
603975-infra01: infra1:
ip: 10.240.0.80 ip: IDENTITY01_IP_ADDRESS
603989-infra02: infra2: ...
ip: 10.240.0.81
627116-infra03:
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:
@ -81,12 +65,9 @@ suitable short hostname for a compute host might be:
.. code-block:: yaml .. code-block:: yaml
network_hosts: network_hosts:
602117-network01: network01:
ip: NETWORK01_IP_ADDRESS ip: NETWORK01_IP_ADDRESS
602534-network02: ... network02: ...
Replace ``*_IP_ADDRESS`` with the IP address of the ``br-mgmt``
container management bridge on each network target host.
Providing more than one network host in the ``network_hosts`` block will Providing more than one network host in the ``network_hosts`` block will
enable `L3HA support using VRRP`_ in the neutron-agent containers. enable `L3HA support using VRRP`_ in the neutron-agent containers.
@ -99,12 +80,9 @@ suitable short hostname for a compute host might be:
.. code-block:: yaml .. code-block:: yaml
compute_hosts: compute_hosts:
900089-compute001: compute001:
ip: COMPUTE001_IP_ADDRESS ip: COMPUTE001_IP_ADDRESS
900090-compute002: ... compute002: ...
Replace ``*_IP_ADDRESS`` with the IP address of the ``br-mgmt``
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
``log_hosts`` section: ``log_hosts`` section:
@ -112,12 +90,9 @@ suitable short hostname for a compute host might be:
.. code-block:: yaml .. code-block:: yaml
log_hosts: log_hosts:
900088-logging01: logging01:
ip: LOGGER1_IP_ADDRESS ip: LOGGER1_IP_ADDRESS
903877-logging02: ... logging02: ...
Replace ``*_IP_ADDRESS`` with the IP address of the ``br-mgmt``
container management bridge on each logging target host.
#. Configure a list containing at least one repository target host in the #. Configure a list containing at least one repository target host in the
``repo-infra_hosts`` section: ``repo-infra_hosts`` section:
@ -125,16 +100,13 @@ suitable short hostname for a compute host might be:
.. code-block:: yaml .. code-block:: yaml
repo-infra_hosts: repo-infra_hosts:
603975-repo01: repo01:
ip: REPO01_IP_ADDRESS ip: REPO01_IP_ADDRESS
603989-repo02: repo02:
ip: REPO02_IP_ADDRESS ip: REPO02_IP_ADDRESS
627116-repo03: repo03:
ip: REPO03_IP_ADDRESS ip: REPO03_IP_ADDRESS
628771-repo04: ... 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. The repository typically resides on one or more infrastructure hosts.
@ -161,13 +133,11 @@ suitable short hostname for a compute host might be:
.. code-block:: yaml .. code-block:: yaml
storage_hosts: storage_hosts:
100338-storage01: storage01:
ip: STORAGE01_IP_ADDRESS ip: STORAGE01_IP_ADDRESS
100392-storage02: ... storage02: ...
Replace ``*_IP_ADDRESS`` with the IP address of the ``br-mgmt`` Each storage host also requires additional configuration to define the back end
container management bridge on each storage target host. Each storage
host also requires additional configuration to define the back end
driver. driver.
The default configuration includes an optional storage host. To The default configuration includes an optional storage host. To