openstack
/
charm-deployment-guide
Code Issues Proposed changes

Mention hardware addresses for OVN Chassis 

It is common for users to not have the same
network interface name available across all MAAS
nodes for ovn-chassis units. This PR outlines the
use of hardware addresses.

Change-Id: I84cc572441f55c5e38f4bb99613be2514bddd86a
This commit is contained in:
Peter Matulis 2022-06-29 21:05:56 -04:00
parent 5920c9ffab
commit acce3eae2a
2 changed files with 21 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
deploy-guide/source/install-maas.rst
View File

@ -232,6 +232,13 @@ The mapping of bridge to interface ('br-ex:enp1s0') will be used in the
:ref:`Neutron networking <neutron_networking>` section on the :doc:`Install
OpenStack <install-openstack>` page.
.. important::
Identically-named interfaces on the cloud nodes is not a strict requirement
as an individual interface can also be denoted by its hardware (MAC)
address. In such a case, make note of the MAC address of each node's
interface.
Node summary
------------

14
deploy-guide/source/install-openstack.rst
View File

@ -259,6 +259,20 @@ a mapping of OVS bridge to network interface. As described in the :ref:`Create
OVS bridge <ovs_bridge>` section on the :doc:`Install MAAS <install-maas>`
page, it is 'br-ex:enp1s0'.
.. note::
To use hardware addresses (as opposed to an interface name common to all
four nodes) the ``bridge-interface-mappings`` option can be expressed in
this way (substitute in your own values):
.. code-block:: yaml
bridge-interface-mappings: >-
br-ex:52:54:00:03:01:01
br-ex:52:54:00:03:01:02
br-ex:52:54:00:03:01:03
br-ex:52:54:00:03:01:04
The ``flat-network-providers`` setting enables the Neutron flat network
provider used in this example scenario and gives it the name of 'physnet1'. The
flat network provider and its name will be referenced when we :ref:`Set up