openstack/ironic
Code Issues Proposed changes

docs: note ipv6 is a good idea with neutron interface

Browse Source 
One caveat around dhcpv6 and network interfaces, is the binding logic
in the ``neutron`` network interface is able to generate multiple
dhcp addresses for use, where as the flat interface is not able to.

Change-Id: If89c618ec951f75b9b09d7218b8500fd43a0d381
This commit is contained in:
Julia Kreger 2024-12-03 07:48:04 -08:00
parent 3421bb614a
commit c980a6de4c
1 changed files with 10 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
doc/source/admin/networking.rst
View File

@ -96,7 +96,8 @@ the Ironic service:
support for the switches attached to the baremetal servers so they can be support for the switches attached to the baremetal servers so they can be
programmed. This interface generally requires use of ML2 plugins or other programmed. This interface generally requires use of ML2 plugins or other
Neutron SDN integrations to facilitate the port configuration actions in Neutron SDN integrations to facilitate the port configuration actions in
the network fabric. the network fabric. When using IPv6, use of the ``neutron`` interface
is preferred.
To use these interfaces, they need to be enabled in *ironic.conf* utilizing To use these interfaces, they need to be enabled in *ironic.conf* utilizing
the :oslo.config:option:`enabled_network_interfaces` setting. the :oslo.config:option:`enabled_network_interfaces` setting.
@ -389,6 +390,14 @@ physical top of rack switches for the bare metal servers. To do this an ML2
mechanism driver which supports the ``baremetal`` VNIC type for the make and mechanism driver which supports the ``baremetal`` VNIC type for the make and
model of top of rack switch in the environment must be installed and enabled. model of top of rack switch in the environment must be installed and enabled.
One case where you may wish to prefer the ``neutron`` network interface, even
when your architecture is statically configured interfaces similar to ``flat``
networks, is when your using IPv6. Various hardware, bootloader, and Operating
System DHCP clients utilize different techneaques for generating the host
identifier string which DHCP servers utilize to track IPv6 hosts. The
``neutron`` interface generates additional IPv6 DHCP entries to account for
situations such as this, where as the ``flat`` interface is unable to do so.
This is a list of known top of rack ML2 mechanism drivers which work with the This is a list of known top of rack ML2 mechanism drivers which work with the
``neutron`` network interface. ``neutron`` network interface.