From thomas.king at gmail.com Thu May 28 20:32:01 2020 From: thomas.king at gmail.com (Thomas King) Date: Thu, 28 May 2020 14:32:01 -0600 Subject: [Openstack-mentoring] Neutron subnet with DHCP relay Message-ID: Good day, 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. 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. Is DHCP relay supported by Neutron? My guess is to add a subnet in the provisioning network and point the relay agent to the linuxbridge interface's IP: 14: brq467f6775-be: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether e2:e9:09:7f:89:0b brd ff:ff:ff:ff:ff:ff inet 10.10.0.1/16 scope global brq467f6775-be valid_lft forever preferred_lft forever inet6 fe80::5400:52ff:fe85:d33d/64 scope link valid_lft forever preferred_lft forever Thank you, Tom King -------------- next part -------------- An HTML attachment was scrubbed... URL: From amy at demarco.com Thu May 28 21:04:04 2020 From: amy at demarco.com (Amy Marrich) Date: Thu, 28 May 2020 16:04:04 -0500 Subject: [Openstack-mentoring] Neutron subnet with DHCP relay In-Reply-To: References: Message-ID: Hey Tom, Forwarding to the OpenStack discuss list where you might get more assistance. Thanks, Amy (spotz) On Thu, May 28, 2020 at 3:32 PM Thomas King wrote: > Good day, > > 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. > > 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. > > Is DHCP relay supported by Neutron? > > My guess is to add a subnet in the provisioning network and point the > relay agent to the linuxbridge interface's IP: > 14: brq467f6775-be: mtu 1500 qdisc > noqueue state UP group default qlen 1000 > link/ether e2:e9:09:7f:89:0b brd ff:ff:ff:ff:ff:ff > inet 10.10.0.1/16 scope global brq467f6775-be > valid_lft forever preferred_lft forever > inet6 fe80::5400:52ff:fe85:d33d/64 scope link > valid_lft forever preferred_lft forever > > Thank you, > Tom King > _______________________________________________ > openstack-mentoring mailing list > openstack-mentoring at lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-mentoring > -------------- next part -------------- An HTML attachment was scrubbed... URL: From thomas.king at gmail.com Thu May 28 21:08:23 2020 From: thomas.king at gmail.com (Thomas King) Date: Thu, 28 May 2020 15:08:23 -0600 Subject: [Openstack-mentoring] Neutron subnet with DHCP relay In-Reply-To: References: Message-ID: Thanks, that'd be great. Tom King On Thu, May 28, 2020 at 3:04 PM Amy Marrich wrote: > Hey Tom, > > Forwarding to the OpenStack discuss list where you might get more > assistance. > > Thanks, > > Amy (spotz) > > On Thu, May 28, 2020 at 3:32 PM Thomas King wrote: > >> Good day, >> >> 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. >> >> 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. >> >> Is DHCP relay supported by Neutron? >> >> My guess is to add a subnet in the provisioning network and point the >> relay agent to the linuxbridge interface's IP: >> 14: brq467f6775-be: mtu 1500 qdisc >> noqueue state UP group default qlen 1000 >> link/ether e2:e9:09:7f:89:0b brd ff:ff:ff:ff:ff:ff >> inet 10.10.0.1/16 scope global brq467f6775-be >> valid_lft forever preferred_lft forever >> inet6 fe80::5400:52ff:fe85:d33d/64 scope link >> valid_lft forever preferred_lft forever >> >> Thank you, >> Tom King >> _______________________________________________ >> openstack-mentoring mailing list >> openstack-mentoring at lists.openstack.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-mentoring >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From thomas.king at gmail.com Fri May 29 16:47:11 2020 From: thomas.king at gmail.com (Thomas King) Date: Fri, 29 May 2020 10:47:11 -0600 Subject: [Openstack-mentoring] Neutron subnet with DHCP relay In-Reply-To: References: Message-ID: 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. 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). 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. Thanks for the help and please let me know which method is correct. Tom King On Fri, May 29, 2020 at 3:15 AM Dan Sneddon wrote: > 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. > > 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. > > -Dan > > On Fri, May 29, 2020 at 12:51 AM Dmitry Tantsur > wrote: > >> Hi Tom, >> >> 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): >> http://tripleo.org/install/advanced_deployment/routed_spine_leaf_network.html#dhcp-relay-configuration >> >> Dmitry >> >> On Thu, May 28, 2020 at 11:06 PM Amy Marrich wrote: >> >>> Hey Tom, >>> >>> Forwarding to the OpenStack discuss list where you might get more >>> assistance. >>> >>> Thanks, >>> >>> Amy (spotz) >>> >>> On Thu, May 28, 2020 at 3:32 PM Thomas King >>> wrote: >>> >>>> Good day, >>>> >>>> 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. >>>> >>>> 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. >>>> >>>> Is DHCP relay supported by Neutron? >>>> >>>> My guess is to add a subnet in the provisioning network and point the >>>> relay agent to the linuxbridge interface's IP: >>>> 14: brq467f6775-be: mtu 1500 qdisc >>>> noqueue state UP group default qlen 1000 >>>> link/ether e2:e9:09:7f:89:0b brd ff:ff:ff:ff:ff:ff >>>> inet 10.10.0.1/16 scope global brq467f6775-be >>>> valid_lft forever preferred_lft forever >>>> inet6 fe80::5400:52ff:fe85:d33d/64 scope link >>>> valid_lft forever preferred_lft forever >>>> >>>> Thank you, >>>> Tom King >>>> _______________________________________________ >>>> openstack-mentoring mailing list >>>> openstack-mentoring at lists.openstack.org >>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-mentoring >>>> >>> -- > Dan Sneddon | Senior Principal Software Engineer > dsneddon at redhat.com | redhat.com/cloud > dsneddon:irc | @dxs:twitter > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dtantsur at redhat.com Fri May 29 07:49:30 2020 From: dtantsur at redhat.com (Dmitry Tantsur) Date: Fri, 29 May 2020 09:49:30 +0200 Subject: [Openstack-mentoring] Neutron subnet with DHCP relay In-Reply-To: References: Message-ID: Hi Tom, 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): http://tripleo.org/install/advanced_deployment/routed_spine_leaf_network.html#dhcp-relay-configuration Dmitry On Thu, May 28, 2020 at 11:06 PM Amy Marrich wrote: > Hey Tom, > > Forwarding to the OpenStack discuss list where you might get more > assistance. > > Thanks, > > Amy (spotz) > > On Thu, May 28, 2020 at 3:32 PM Thomas King wrote: > >> Good day, >> >> 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. >> >> 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. >> >> Is DHCP relay supported by Neutron? >> >> My guess is to add a subnet in the provisioning network and point the >> relay agent to the linuxbridge interface's IP: >> 14: brq467f6775-be: mtu 1500 qdisc >> noqueue state UP group default qlen 1000 >> link/ether e2:e9:09:7f:89:0b brd ff:ff:ff:ff:ff:ff >> inet 10.10.0.1/16 scope global brq467f6775-be >> valid_lft forever preferred_lft forever >> inet6 fe80::5400:52ff:fe85:d33d/64 scope link >> valid_lft forever preferred_lft forever >> >> Thank you, >> Tom King >> _______________________________________________ >> openstack-mentoring mailing list >> openstack-mentoring at lists.openstack.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-mentoring >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dsneddon at redhat.com Fri May 29 09:14:51 2020 From: dsneddon at redhat.com (Dan Sneddon) Date: Fri, 29 May 2020 02:14:51 -0700 Subject: [Openstack-mentoring] Neutron subnet with DHCP relay In-Reply-To: References: Message-ID: 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. 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. -Dan On Fri, May 29, 2020 at 12:51 AM Dmitry Tantsur wrote: > Hi Tom, > > 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): > http://tripleo.org/install/advanced_deployment/routed_spine_leaf_network.html#dhcp-relay-configuration > > Dmitry > > On Thu, May 28, 2020 at 11:06 PM Amy Marrich wrote: > >> Hey Tom, >> >> Forwarding to the OpenStack discuss list where you might get more >> assistance. >> >> Thanks, >> >> Amy (spotz) >> >> On Thu, May 28, 2020 at 3:32 PM Thomas King >> wrote: >> >>> Good day, >>> >>> 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. >>> >>> 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. >>> >>> Is DHCP relay supported by Neutron? >>> >>> My guess is to add a subnet in the provisioning network and point the >>> relay agent to the linuxbridge interface's IP: >>> 14: brq467f6775-be: mtu 1500 qdisc >>> noqueue state UP group default qlen 1000 >>> link/ether e2:e9:09:7f:89:0b brd ff:ff:ff:ff:ff:ff >>> inet 10.10.0.1/16 scope global brq467f6775-be >>> valid_lft forever preferred_lft forever >>> inet6 fe80::5400:52ff:fe85:d33d/64 scope link >>> valid_lft forever preferred_lft forever >>> >>> Thank you, >>> Tom King >>> _______________________________________________ >>> openstack-mentoring mailing list >>> openstack-mentoring at lists.openstack.org >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-mentoring >>> >> -- Dan Sneddon | Senior Principal Software Engineer dsneddon at redhat.com | redhat.com/cloud dsneddon:irc | @dxs:twitter -------------- next part -------------- An HTML attachment was scrubbed... URL: From amy at demarco.com Fri May 29 20:37:43 2020 From: amy at demarco.com (Amy Marrich) Date: Fri, 29 May 2020 15:37:43 -0500 Subject: [Openstack-mentoring] [Diversity] [PTG] Diversity WG at PTG Message-ID: The Diversity and Inclusion WG will be having a session at 16:00 UTC on Monday at https://meetpad.opendev.org/PTGDiversityAndInclusion As a WG reporting to the OSF Board we would like to invite all OSF projects to come and learn what the WG can do for their project. The WG oversees the Diversity and Inclusion surveys as well as the OpenStack mentoring program. Hope to see new faces on Monday! Amy Marrich (spotz) -------------- next part -------------- An HTML attachment was scrubbed... URL: