@@ -32,23 +32,25 @@ at [1]_.
32
32
can announce host routes for both floating and fixed IP addresses. These
33
33
functions are not supported in OVN.
34
34
35
- * Baremetal provisioning with iPXE
35
+ * Baremetal provisioning with iPXE without Neutron DHCP agent for IPv6
36
36
37
- The core OVN DHCP server implementation does not have support for
38
- sending different boot options based on the ``gpxe `` DHCP Option
39
- (no. 175). Also, Ironic uses dnsmasq syntax when configuring the DHCP
40
- options for Neutron [2 ]_ which is not understood by the OVN driver.
37
+ The core OVN built-in DHCP server implementation does not
38
+ yet support PXE booting for IPv6. This can be achieved at
39
+ the moment if used with the Neutron DHCP agent by deploying it
40
+ on OVN gateway nodes and disabling the OVN DHCP by setting the
41
+ ``[ovn]/disable_ovn_dhcp_for_baremetal_ports `` configuration option
42
+ to True.
41
43
42
44
* QoS minimum bandwidth allocation in Placement API
43
45
44
46
ML2/OVN integration with the Nova placement API to provide guaranteed
45
- minimum bandwidth for ports [3 ]_.
47
+ minimum bandwidth for ports [4 ]_. Work in progress, see [ 5 ]_
46
48
47
49
* IPv6 Prefix Delegation
48
50
49
51
Currently ML2/OVN doesn't implement IPv6 prefix delegation. OVN logical
50
- routers have this capability implemented in [4 ]_ and we have an open RFE to
51
- fill this gap [5 ]_.
52
+ routers have this capability implemented in [6 ]_ and we have an open RFE to
53
+ fill this gap [7 ]_.
52
54
53
55
* East/West Fragmentation
54
56
@@ -62,11 +64,12 @@ at [1]_.
62
64
from instances to reach the DHCP agent. For OVN this traffic has to be explicitly
63
65
allowed by security group rules attached to the instance. Note that the default
64
66
security group does allow all outgoing traffic, so this only becomes relevant
65
- when using custom security groups [6 ]_.
67
+ when using custom security groups [8 ]_. Proposed patch is [9 ]_ but it
68
+ needs to be revived and updated.
66
69
67
70
* DNS resolution for instances
68
71
69
- OVN cannot use the host's networking for DNS resolution, so Case 2b in [7 ]_ can
72
+ OVN cannot use the host's networking for DNS resolution, so Case 2b in [10 ]_ can
70
73
only be used when additional DHCP agents are deployed. For Case 2a a different
71
74
configuration option has to be used in ``ml2_conf.ini ``::
72
75
@@ -82,11 +85,12 @@ References
82
85
----------
83
86
84
87
.. [1 ] https://github.com/ovn-org/ovn/blob/master/TODO.rst
85
- .. [2 ] https://github.com/openstack/ironic/blob/123cb22c731f93d0c608d791b41e05884fe18c04/ironic/common/pxe_utils.py#L447-L462>
86
- .. [3 ] https://specs.openstack.org/openstack/neutron-specs/specs/rocky/minimum-bandwidth-allocation-placement-api.html
87
- .. [4 ] https://patchwork.ozlabs.org/project/openvswitch/patch/6aec0fb280f610a2083fbb6c61e251b1d237b21f.1576840560.git.lorenzo.bianconi@redhat.com/
88
- .. [5 ] https://bugs.launchpad.net/neutron/+bug/1895972
89
- .. [6 ] https://bugs.launchpad.net/neutron/+bug/1926515
90
- .. [7 ] https://docs.openstack.org/neutron/latest/admin/config-dns-res.html
91
- .. [8 ] https://bugs.launchpad.net/neutron/+bug/1951816
92
- .. [9 ] https://bugs.launchpad.net/neutron/+bug/1950686
88
+ .. [2 ] https://bugzilla.redhat.com/show_bug.cgi?id=2060310
89
+ .. [3 ] https://review.opendev.org/c/openstack/neutron/+/842292
90
+ .. [4 ] https://specs.openstack.org/openstack/neutron-specs/specs/rocky/minimum-bandwidth-allocation-placement-api.html
91
+ .. [5 ] https://review.opendev.org/c/openstack/neutron/+/786478
92
+ .. [6 ] https://patchwork.ozlabs.org/project/openvswitch/patch/6aec0fb280f610a2083fbb6c61e251b1d237b21f.1576840560.git.lorenzo.bianconi@redhat.com/
93
+ .. [7 ] https://bugs.launchpad.net/neutron/+bug/1895972
94
+ .. [8 ] https://bugs.launchpad.net/neutron/+bug/1926515
95
+ .. [9 ] https://review.opendev.org/c/openstack/neutron/+/788594
96
+ .. [10 ] https://docs.openstack.org/neutron/latest/admin/config-dns-res.html
0 commit comments