<div dir="ltr">Well, I'm using a flat network (i.e., access mode switchport), not a tagged switchport. The remote nodes will be on their own subnet and VLAN/segment that will <i>not </i>be attached to the controller. <div><br></div><div>"In that case, DHCP requests from all segments that are not attached to the controller(s) need to be forwarded to the controllers via DHCP relay." Agreed. The question is which DHCP agent IP address? </div><div><br></div><div>DHCP agent IP #1 = <a href="http://10.10.1.1/16">10.10.1.1/16</a>, corresponds to an attached segment/subnet. </div><div>DHCP agent IP #2 = <a href="http://10.100.1.1/16">10.100.1.1/16</a>, corresponds to a subnet in a completely separate rack with no direct connection to the controller. </div><div><br></div><div>Even if I separate IP #2 onto a different segment with its own DHCP agent port, am I sending DHCP relay to IP #1 or #2? I'm assuming #1. </div><div><br></div><div>Tom</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Jun 1, 2020 at 6:40 PM <<a href="mailto:dsneddon@redhat.com">dsneddon@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">The use case for routed networks is when you have multiple distinct<br>
subnets which are not connected at layer 2 and only have connectivity<br>
to one another via the router gateways on each network. A segment can<br>
be thought of as a VLAN, although depending on topology a different<br>
VLAN ID is not always used. The key is that there is no layer 2<br>
connectivity between segments, traffic has to be routed between them.<br>
<br>
The situation where you would use DHCP relay is when you are not<br>
assigning DHCP agents to the compute nodes, and you have compute nodes<br>
on segments that the controllers are not attached to. In that case,<br>
DHCP requests from all segments that are not attached to the<br>
controller(s) need to be forwarded to the controllers via DHCP relay.<br>
<br>
If you have a flat network, then you have no need for DHCP relay, the<br>
DHCP agents can receive and respond to requests over layer 2. This<br>
applies even if you have multiple subnets on the same segment.<br>
<br>
On Mon, 2020-06-01 at 18:02 -0600, Thomas King wrote:<br>
> We do have the Ironic inspector enabled but mainly use out-of-band<br>
> such as iDRAC. <br>
> <br>
> I am indeed not using segments. I'll need to research that a bit<br>
> more. <br>
> <br>
> One important note, we are only using provider networks with no<br>
> Neutron routers. All routing is done on the physical network which<br>
> aligns with the docs for segments. The provisioning subnet is on<br>
> <a href="http://10.10.0.0/16" rel="noreferrer" target="_blank">10.10.0.0/16</a> for the directly attached nodes. As a test, I created a<br>
> second subnet, <a href="http://10.100.0.0/16" rel="noreferrer" target="_blank">10.100.0.0/16</a>, on the same Neutron network with DHCP<br>
> enabled, so now I have two subnets on the same network and Neutron<br>
> DHCP port. However, if DHCP relay requires different segments per<br>
> remote network...<br>
> > The Networking service defines a segment using the following<br>
> > components:<br>
> > <br>
> > Unique physical network name <br>
> > Segmentation type<br>
> > Segmentation ID<br>
> <br>
> Does having unique physical network names also mean unique physical<br>
> interfaces? <br>
> Does this mean no flat network for segments? <br>
> If I create <a href="http://10.100.0.0/16" rel="noreferrer" target="_blank">10.100.0.0/16</a> in rack A1 and the controller is in D30, am<br>
> I pointing the DHCP relay to the DHCP agent's <a href="http://10.10.0.0/16" rel="noreferrer" target="_blank">10.10.0.0/16</a> IP<br>
> address?<br>
> <br>
> <br>
> +--------------------+-------+---------------------------+<br>
> | Agent Type | Alive | Binary |<br>
> +--------------------+-------+---------------------------+<br>
> | Baremetal Node | :-) | ironic-neutron-agent |<br>
> | Baremetal Node | :-) | ironic-neutron-agent |<br>
> | Baremetal Node | :-) | ironic-neutron-agent |<br>
> | Baremetal Node | :-) | ironic-neutron-agent |<br>
> | Linux bridge agent | :-) | neutron-linuxbridge-agent |<br>
> | Baremetal Node | :-) | ironic-neutron-agent |<br>
> | Metering agent | :-) | neutron-metering-agent |<br>
> | Baremetal Node | :-) | ironic-neutron-agent |<br>
> | Baremetal Node | :-) | ironic-neutron-agent |<br>
> | Baremetal Node | :-) | ironic-neutron-agent |<br>
> | DHCP agent | :-) | neutron-dhcp-agent |<br>
> | L3 agent | :-) | neutron-l3-agent |<br>
> | Baremetal Node | :-) | ironic-neutron-agent |<br>
> | Baremetal Node | :-) | ironic-neutron-agent |<br>
> | Metadata agent | :-) | neutron-metadata-agent |<br>
> | Baremetal Node | :-) | ironic-neutron-agent |<br>
> | Baremetal Node | :-) | ironic-neutron-agent |<br>
> | Baremetal Node | :-) | ironic-neutron-agent |<br>
> +--------------------+-------+---------------------------+<br>
> <br>
> On Mon, Jun 1, 2020 at 4:34 PM <<a href="mailto:dsneddon@redhat.com" target="_blank">dsneddon@redhat.com</a>> wrote:<br>
> > You will have to target two IP addresses with DHCP relay if you are<br>
> > using Ironic Inspector. The first is the IP where Ironic Inspector<br>
> > is<br>
> > listening with dnsmasq, usually the IP of the host itself. I know<br>
> > this<br>
> > doesn't lend itself to HA scenarios, but you might also be able to<br>
> > forward to the broadcast IP of the subnet where the Ironic<br>
> > Inspector<br>
> > will be running (I haven't tested this, but it is a common use case<br>
> > for<br>
> > DHCP relay).<br>
> > <br>
> > The second IP address is that of the Neutron DHCP agent, and that<br>
> > will<br>
> > be used for deploying bare metal nodes. IIRC, this IP is shared<br>
> > with<br>
> > the Neutron router for the network if you are using the L3 agent as<br>
> > well.<br>
> > <br>
> > If you are not running Ironic Inspector (and manually entering in<br>
> > baremetal host details instead), then you can forward DHCP relay<br>
> > only<br>
> > to the Neutron DHCP agent.<br>
> > <br>
> > Both of these IP addresses will be on the "root" subnet which is<br>
> > associated with the segment with the controller node(s).<br>
> > <br>
> > It sounds like you created a second subnet, but I'm not sure if you<br>
> > created the second subnet on a different segment from the first<br>
> > subnet.<br>
> > In Neutron routed networking, the segments determine whether a<br>
> > subnet<br>
> > is local or remote to the controller node(s). Typically the first<br>
> > segment would be the one local to the controller(s). Are you sure<br>
> > you<br>
> > enabled the segments plugin and created your second subnet on a new<br>
> > segment?<br>
> > <br>
> > Another approach which does not involve DHCP relay is to deploy<br>
> > DHCP<br>
> > agents locally on compute nodes local to each segment. This way all<br>
> > DHCP will be done within the same L2 domain, and you will not have<br>
> > to<br>
> > configure DHCP relay on your router serving each segment/subnet.<br>
> > <br>
> > See the docs for more info:<br>
> > <a href="https://docs.openstack.org/newton/networking-guide/config-routed-networks.html" rel="noreferrer" target="_blank">https://docs.openstack.org/newton/networking-guide/config-routed-networks.html</a><br>
> > <br>
> > -Dan<br>
> > <br>
> > On Fri, 2020-05-29 at 10:47 -0600, Thomas King wrote:<br>
> > > In the Triple-O docs for unicast DHCP relay, it doesn't exactly<br>
> > say<br>
> > > which IP address to target. Without deploying Triple-O, I'm not<br>
> > clear<br>
> > > if the relay IP should be the bridge interface or the DHCP<br>
> > device. <br>
> > > <br>
> > > The first method makes sense because the gateway for that subnet<br>
> > > wouldn't be connected to the Ironic controller by layer 2 (unless<br>
> > we<br>
> > > used VXLAN over the physical network). <br>
> > > <br>
> > > As an experiment, I created a second subnet on my provisioning<br>
> > > network. The original DHCP device port now has two IP addresses,<br>
> > one<br>
> > > on each subnet. That makes the second method possible if I<br>
> > targeted<br>
> > > its original IP address. <br>
> > > <br>
> > > Thanks for the help and please let me know which method is<br>
> > correct. <br>
> > > <br>
> > > Tom King<br>
> > > <br>
> > > On Fri, May 29, 2020 at 3:15 AM Dan Sneddon <<a href="mailto:dsneddon@redhat.com" target="_blank">dsneddon@redhat.com</a>><br>
> > > wrote:<br>
> > > > You probably want to enable Neutron segments and use the<br>
> > Neutron<br>
> > > > routed networks feature so you can use different subnets on<br>
> > > > different segments (layer 2 domains AKA VLANs) of the same<br>
> > network.<br>
> > > > You specify different values such as IP allocation pools and<br>
> > router<br>
> > > > address(es) for each subnet, and Ironic and Neutron will do the<br>
> > > > right thing. You need to enable segments in the Neutron<br>
> > > > configuration and restart the Neutron server. I don’t think<br>
> > you<br>
> > > > will have to recreate the network. Behind the scenes, dnsmasq<br>
> > will<br>
> > > > be configured with multiple subnets and address scopes within<br>
> > the<br>
> > > > Neutron DHCP agent and the Ironic Inspector agent. <br>
> > > > <br>
> > > > Each segment/subnet will be given a different VLAN ID. As<br>
> > Dmitry<br>
> > > > mentioned, TripleO uses that method for the provisioning<br>
> > network,<br>
> > > > so you can use that as an example. The provisioning network in<br>
> > > > TripleO is the one referred to as the “control plane” network. <br>
> > > > <br>
> > > > -Dan<br>
> > > > <br>
> > > > On Fri, May 29, 2020 at 12:51 AM Dmitry Tantsur <<br>
> > > > <a href="mailto:dtantsur@redhat.com" target="_blank">dtantsur@redhat.com</a>> wrote:<br>
> > > > > Hi Tom,<br>
> > > > > <br>
> > > > > I know for sure that people are using DHCP relay with ironic,<br>
> > I<br>
> > > > > think the TripleO documentation may give you some hints<br>
> > (adjusted<br>
> > > > > to your presumably non-TripleO environment): <br>
> > > > > <br>
> > <a href="http://tripleo.org/install/advanced_deployment/routed_spine_leaf_network.html#dhcp-relay-configuration" rel="noreferrer" target="_blank">http://tripleo.org/install/advanced_deployment/routed_spine_leaf_network.html#dhcp-relay-configuration</a><br>
> > > > > <br>
> > > > > Dmitry<br>
> > > > > <br>
> > > > > On Thu, May 28, 2020 at 11:06 PM Amy Marrich <<a href="mailto:amy@demarco.com" target="_blank">amy@demarco.com</a><br>
> > ><br>
> > > > > wrote:<br>
> > > > > > Hey Tom,<br>
> > > > > > <br>
> > > > > > Forwarding to the OpenStack discuss list where you might<br>
> > get<br>
> > > > > > more assistance.<br>
> > > > > > <br>
> > > > > > Thanks,<br>
> > > > > > <br>
> > > > > > Amy (spotz)<br>
> > > > > > <br>
> > > > > > On Thu, May 28, 2020 at 3:32 PM Thomas King <<br>
> > > > > > <a href="mailto:thomas.king@gmail.com" target="_blank">thomas.king@gmail.com</a>> wrote:<br>
> > > > > > > Good day, <br>
> > > > > > > <br>
> > > > > > > We have Ironic running and connected via VLANs to nearby<br>
> > > > > > > machines. We want to extend this to other parts of our<br>
> > > > > > > product development lab without extending VLANs. <br>
> > > > > > > <br>
> > > > > > > Using DHCP relay, we would point to a single IP address<br>
> > to<br>
> > > > > > > serve DHCP requests but I'm not entirely sure of the<br>
> > Neutron<br>
> > > > > > > network/subnet configuration, nor which IP address should<br>
> > be<br>
> > > > > > > used for the relay agent on the switch. <br>
> > > > > > > <br>
> > > > > > > Is DHCP relay supported by Neutron? <br>
> > > > > > > <br>
> > > > > > > My guess is to add a subnet in the provisioning network<br>
> > and<br>
> > > > > > > point the relay agent to the linuxbridge interface's IP: <br>
> > > > > > > 14: brq467f6775-be: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu<br>
> > > > > > > 1500 qdisc noqueue state UP group default qlen 1000<br>
> > > > > > > link/ether e2:e9:09:7f:89:0b brd ff:ff:ff:ff:ff:ff<br>
> > > > > > > inet <a href="http://10.10.0.1/16" rel="noreferrer" target="_blank">10.10.0.1/16</a> scope global brq467f6775-be<br>
> > > > > > > valid_lft forever preferred_lft forever<br>
> > > > > > > inet6 fe80::5400:52ff:fe85:d33d/64 scope link <br>
> > > > > > > valid_lft forever preferred_lft forever<br>
> > > > > > > <br>
> > > > > > > Thank you, <br>
> > > > > > > Tom King<br>
> > > > > > > _______________________________________________<br>
> > > > > > > openstack-mentoring mailing list<br>
> > > > > > > <a href="mailto:openstack-mentoring@lists.openstack.org" target="_blank">openstack-mentoring@lists.openstack.org</a><br>
> > > > > > > <br>
> > <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-mentoring" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-mentoring</a><br>
> > > > <br>
> > > > -- <br>
> > > > Dan Sneddon | Senior Principal Software Engineer<br>
> > > > <a href="mailto:dsneddon@redhat.com" target="_blank">dsneddon@redhat.com</a> | <a href="http://redhat.com/cloud" rel="noreferrer" target="_blank">redhat.com/cloud</a><br>
> > > > dsneddon:irc | @dxs:twitter<br>
-- <br>
Dan Sneddon | Senior Principal Software Engineer<br>
<a href="mailto:dsneddon@redhat.com" target="_blank">dsneddon@redhat.com</a> | <a href="http://redhat.com/cloud" rel="noreferrer" target="_blank">redhat.com/cloud</a><br>
dsneddon:irc | @dxs:twitter<br>
<br>
</blockquote></div>