Public bug reported: This is a RFE request. The goal is to implement in Neutron the functionality provided by OVN since [1] (v24.09.0).
The DHCP relay routes the DHCP messages (discover, request) to an external DHCP server instead of replying using the builtin OVN DHCP server. How it works: * A new OVN NB table is created, "DHCP_Relay". Each entry can store one or several IP addresses of the DHCP servers. * A network (OVN Logical_Switch) is connected to a router (via a Logical_Router_Port). The Logical_Switch.options dictionary receives a new entry, "dhcp_relay_port", that is the Logical_Router_Port of this network connected to the router. * The Logical_Router_Port has a new field, "dhcp_relay". This value should have the UUID of the "DHCP_Relay" register. All ports (Logical_Switch_Ports) connected to this network (Logical_Switch), will have the DHCP messages routed to the IP address defined in the "DHCP_Relay" register. NOTE: * The OVN project provides information to implement a testing environment [2]. * With Neutron, I was able to create two private networks connected to a router. The first one will have a client VM (request DHCP). The second one will have a VM with a dhcpd/dnsmasq server. The server VM port will have no port security, the client VM port have the default SG rules plus (1) the egress UDP 67 and (2) ingress UDP 68. [1]https://github.com/ovn-org/ovn/commit/683a3a36d7c28f104b644d9b944187f70956dbb0 [2]https://github.com/ovn-org/ovn/blob/c92e19aa0331ad90bb891633c5dc4cbe847bc2cc/tests/system-ovn.at#L12960-L13106 ** Affects: neutron Importance: Undecided Assignee: Rodolfo Alonso (rodolfo-alonso-hernandez) Status: New ** Changed in: neutron Assignee: (unassigned) => Rodolfo Alonso (rodolfo-alonso-hernandez) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/2119647 Title: [RFE] OVN DHCP relay Status in neutron: New Bug description: This is a RFE request. The goal is to implement in Neutron the functionality provided by OVN since [1] (v24.09.0). The DHCP relay routes the DHCP messages (discover, request) to an external DHCP server instead of replying using the builtin OVN DHCP server. How it works: * A new OVN NB table is created, "DHCP_Relay". Each entry can store one or several IP addresses of the DHCP servers. * A network (OVN Logical_Switch) is connected to a router (via a Logical_Router_Port). The Logical_Switch.options dictionary receives a new entry, "dhcp_relay_port", that is the Logical_Router_Port of this network connected to the router. * The Logical_Router_Port has a new field, "dhcp_relay". This value should have the UUID of the "DHCP_Relay" register. All ports (Logical_Switch_Ports) connected to this network (Logical_Switch), will have the DHCP messages routed to the IP address defined in the "DHCP_Relay" register. NOTE: * The OVN project provides information to implement a testing environment [2]. * With Neutron, I was able to create two private networks connected to a router. The first one will have a client VM (request DHCP). The second one will have a VM with a dhcpd/dnsmasq server. The server VM port will have no port security, the client VM port have the default SG rules plus (1) the egress UDP 67 and (2) ingress UDP 68. [1]https://github.com/ovn-org/ovn/commit/683a3a36d7c28f104b644d9b944187f70956dbb0 [2]https://github.com/ovn-org/ovn/blob/c92e19aa0331ad90bb891633c5dc4cbe847bc2cc/tests/system-ovn.at#L12960-L13106 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/2119647/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
