<div dir="ltr">In the Triple-O docs for unicast DHCP relay, it doesn't exactly say which IP address to target. Without deploying Triple-O, I'm not clear if the relay IP should be the bridge interface or the DHCP device. <div><br></div><div>The first method makes sense because the gateway for that subnet wouldn't be connected to the Ironic controller by layer 2 (unless we used VXLAN over the physical network). </div><div><br></div><div>As an experiment, I created a second subnet on my provisioning network. The original DHCP device port now has two IP addresses, one on each subnet. That makes the second method possible if I targeted its original IP address. </div><div><br></div><div>Thanks for the help and please let me know which method is correct. </div><div><br></div><div>Tom King</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, May 29, 2020 at 3:15 AM Dan Sneddon <<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"><div><div><div dir="auto">You probably want to enable Neutron segments and use the Neutron routed networks feature so you can use different subnets on different segments (layer 2 domains AKA VLANs) of the same network. You specify different values such as IP allocation pools and router address(es) for each subnet, and Ironic and Neutron will do the right thing. You need to enable segments in the Neutron configuration and restart the Neutron server. I don’t think you will have to recreate the network. Behind the scenes, dnsmasq will be configured with multiple subnets and address scopes within the Neutron DHCP agent and the Ironic Inspector agent. </div><div dir="auto"><br></div><div dir="auto">Each segment/subnet will be given a different VLAN ID. As Dmitry mentioned, TripleO uses that method for the provisioning network, so you can use that as an example. The provisioning network in TripleO is the one referred to as the “control plane” network. </div></div></div><div><div><div dir="auto"><br></div><div dir="auto">-Dan</div></div><div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, May 29, 2020 at 12:51 AM Dmitry Tantsur <<a href="mailto:dtantsur@redhat.com" target="_blank">dtantsur@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"><div dir="ltr"><div>Hi Tom,</div><div><br></div><div>I know for sure that people are using DHCP relay with ironic, I think the TripleO documentation may give you some hints (adjusted to your presumably non-TripleO environment): <a href="http://tripleo.org/install/advanced_deployment/routed_spine_leaf_network.html#dhcp-relay-configuration" target="_blank">http://tripleo.org/install/advanced_deployment/routed_spine_leaf_network.html#dhcp-relay-configuration</a></div></div><div dir="ltr"><div><br></div><div>Dmitry<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, May 28, 2020 at 11:06 PM Amy Marrich <<a href="mailto:amy@demarco.com" target="_blank">amy@demarco.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"><div dir="ltr"><div>Hey Tom,</div><div><br></div><div>Forwarding to the OpenStack discuss list where you might get more assistance.</div><div><br></div><div>Thanks,</div><div><br></div><div>Amy (spotz)<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, May 28, 2020 at 3:32 PM Thomas King <<a href="mailto:thomas.king@gmail.com" target="_blank">thomas.king@gmail.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"><div dir="ltr">Good day, <div><br></div><div>We have Ironic running and connected via VLANs to nearby machines. We want to extend this to other parts of our product development lab without extending VLANs. </div><div><br></div><div>Using DHCP relay, we would point to a single IP address to serve DHCP requests but I'm not entirely sure of the Neutron network/subnet configuration, nor which IP address should be used for the relay agent on the switch. </div><div><br></div><div>Is DHCP relay supported by Neutron? </div><div><br></div><div>My guess is to add a subnet in the provisioning network and point the relay agent to the linuxbridge interface's IP: </div><div>14: brq467f6775-be: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 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" 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></div><div><br></div><div>Thank you, </div><div>Tom King</div></div>
_______________________________________________<br>
openstack-mentoring mailing list<br>
<a href="mailto:openstack-mentoring@lists.openstack.org" target="_blank">openstack-mentoring@lists.openstack.org</a><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>
</blockquote></div>
</blockquote></div>
</blockquote></div></div>
</div>-- <br><div dir="ltr"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><font face="monospace, monospace">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" target="_blank">redhat.com/cloud</a><br>dsneddon:irc | @dxs:twitter</font><br></div></div></div></div></div></div>
</blockquote></div>