diff options
author | Harald Jensas <hjensas@redhat.com> | 2018-02-01 19:43:59 +0100 |
---|---|---|
committer | Harald Jensas <hjensas@redhat.com> | 2018-02-01 19:47:14 +0100 |
commit | 71021bb9d4e4cd3b02f5e4f7c9003b672441382c (patch) | |
tree | 905a844a8ba41bd9316dbfed7f91a0de158da83f | |
parent | f51909d378ce1bd710a221567ab10a0464fe5efc (diff) | |
download | ironic-71021bb9d4e4cd3b02f5e4f7c9003b672441382c.tar.gz |
Fix configure-networking docs
This patch address feedback in Ic9a5d1de959cbeedb0e56ab5447042ce29028a8d
Change-Id: I58543cc18745f8ec6876423fbe72fcca3a7cbdb6
-rw-r--r-- | doc/source/install/configure-networking.rst | 23 |
1 files changed, 18 insertions, 5 deletions
diff --git a/doc/source/install/configure-networking.rst b/doc/source/install/configure-networking.rst index 6904ffa73..8e834f50f 100644 --- a/doc/source/install/configure-networking.rst +++ b/doc/source/install/configure-networking.rst @@ -8,17 +8,30 @@ with the Networking service for DHCP, PXE boot and other requirements. This section covers configuring Networking for a single flat network for bare metal provisioning. -Baremetal service requires the baremetal mechanism driver to be installed and -enabled in the networking service for flat networks. Documentation regarding -installation and configuration of the baremetal mechanism driver is available -at `here <https://docs.openstack.org/networking-baremetal/latest/index.html>`_. +It is recommended to use the baremetal ML2 mechanism driver and L2 agent for +proper integration with the Networking service. Documentation regarding +installation and configuration of the baremetal mechanism driver and L2 agent +is available `here +<https://docs.openstack.org/networking-baremetal/latest/index.html>`_. + +For use with `routed networks +<https://docs.openstack.org/neutron/latest/admin/config-routed-networks>`_ +the baremetal ML2 components are required. + +.. Note:: When the baremetal ML2 components are *not* used, ports in the + Networking service will have status: ``DOWN``, and binding_vif_type: + ``binding_failed``. This was always the status for Bare Metal + service ``flat`` network interface ports prior to the introduction + of the baremetal ML2 integration. For a non-routed network, bare + metal servers can still be deployed and are functional, despite this + port binding state in the Networking service. You will also need to provide Bare Metal service with the MAC address(es) of each node that it is provisioning; Bare Metal service in turn will pass this information to Networking service for DHCP and PXE boot configuration. An example of this is shown in the :ref:`enrollment` section. -#. Install the networking-baremetal ml2 mechanism driver and l2 agent in the +#. Install the networking-baremetal ML2 mechanism driver and L2 agent in the Networking service. #. Edit ``/etc/neutron/plugins/ml2/ml2_conf.ini`` and modify these: |