openstack/openstack-ansible-os_neutron
Code Issues Proposed changes

Update OVN northd group documentation

Browse Source 
Existing docs are missing mention of network-northd_hosts, which
is a required grouping for a successful OVN deployment. This patch
addresses that.

Change-Id: Ie532573cc04722d18915996c5148eecb180ee7ec
This commit is contained in:
James Denton 2023-01-11 10:09:58 -06:00
parent d4cbd2d7ad
commit 0d6ca7f07f
1 changed files with 26 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

32
doc/source/app-ovn.rst
View File

@ -80,12 +80,32 @@ OpenStack-Ansible supports the following common deployment scenarios:
- Collapsed Compute/Gateway Nodes
- Standalone Gateway Nodes
In an OpenStack-Ansible deployment, members of the ``network_hosts`` group are
considered members of the ``neutron_ovn_northd`` group and run OVN northd-related
services, while members of the ``compute_hosts`` group are considered members of
the ``neutron_ovn_controller`` group and run OVN controller-related services. It is
up to the deployer to dictate which nodes are considered "OVN Gateway Chassis" nodes
by using the ``network-gateway_hosts`` inventory group in ``openstack_user_config.yml``.
In an OpenStack-Ansible deployment, infrastructure hosts are intended to run
OVN northd-related services, while compute hosts are intended to run
OVN controller-related services.
In ``openstack_user_config.yml``, specify the hosts or aliases that will run the
``ovn-northd`` service(s), like so:
.. code-block:: yaml
network-northd_hosts:
infra01:
ip: 172.25.1.11
infra02:
ip: 172.25.1.12
infra03:
ip: 172.25.1.13
Alternatively, an alias can be specified, like so:
.. code-block:: yaml
network-northd_hosts: *infrastructure_hosts
It is up to the deployer to dictate which nodes are considered
"OVN Gateway Chassis" nodes by using the ``network-gateway_hosts``
inventory group in ``openstack_user_config.yml``.
In ``openstack_user_config.yml``, specify the hosts or aliases that will run the
``ovn-controller`` service and act as an OVN Gateway Chassis, like so: