402a976820
This patch adds documentation for baremetal provisioning with ML2/OVN. This patch also splits the section about external ports to a different document so it can be shared between baremetal and SR-IOV as both features uses the same feature from core OVN. Change-Id: I48cbd73c3c0fcf0393e31356c081ab1561eecc79 Signed-off-by: Lucas Alvares Gomes <lucasagomes@gmail.com>
2.5 KiB
Baremetal provisioning guide for OVN
The purpose of this page is to describe how the baremetal provisioning can be configured with ML2/OVN.
Currently, baremetal provisioning with ML2/OVN can be achieved using the OVN's built-in DHCP server for IPv4 or using Neutron's DHCP agent for either IPv4 or IPv6.
How to configure it
Scheduling baremetal ports
The first thing to know is that when a port with VNIC
baremetal is created, ML2/OVN will create an OVN port of
the type external. These ports will be bound to nodes that
have external connectivity and are responsible to responding to the ARP
requests on behalf of the baremetal node.
For more information about external ports, its scheduling and
troubleshoot please check the External Ports guide
<ovn_external_ports>.
Metadata access
Different from ML2/OVS, ML2/OVN requires to have the
ovn-metadata-agent running on the node that the virtual
machines are running onto. Since baremetal requires an external port
that will be bound to another node, as explained Scheduling baremetal ports
section, it is required that the ovn-metadata-agent is also
deployed on the nodes marked with the enable-chassis-as-gw
option so it can serve metadata to the baremetal nodes booting off those
external ports.
Using OVN built-in DHCP for PXE booting
Currently, only IPv4 is supported for PXE booting a baremetal node using the OVN's built-in DHCP server. It's also required to have OVN running the version 22.06 or above.
The version of OVN used for baremetal provisioning should include the following commits [1] [2].
And last, make sure that configuration option
[ovn]/disable_ovn_dhcp_for_baremetal_ports is set to
False (the default).
Using Neutron DHCP Agent for PXE booting
If using the OVN built-in DHCP server is not desirable or if PXE
booting nodes off IPv6 is required, the operator will need to deploy
Neutron's DHCP agents on the controller nodes and also disable the OVN's
DHCP server for the baremetal ports by setting the
[ovn]/disable_ovn_dhcp_for_baremetal_ports configuration
option to True (defaults to False).