Re: [openstack-dev] [Fuel] How much do we rely on dnsmasq?
6to4 is a whole different story. I'd prefer to avoid it unless there are seriously compelling reasons to support it. I think dual stack is the way to implement IPv6 support in Fuel. -- Sean M. Collins __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Fuel] How much do we rely on dnsmasq?
My biggest concern is about 4to6 translations. I would prefer to avoid them as longer as it possible. >From my point of view pure ipv6 is easier to implement than dual stack. I see it like when you install Fuel node you decide once and forever what IP version you are go with. We will have two implementations of Fuel - v4 and v6 - and then will try to merge them together. Another option may be if PXE, management, and storage networks are still v4, but OSt API endpoints and Neutron are configured to use IPv6. But some problems may hide there. On Fri, Aug 28, 2015 at 9:07 PM, Sean M. Collins wrote: > On Thu, Aug 27, 2015 at 08:27:24PM EDT, Andrey Danin wrote: > > Hi, Sean, > > > > Dnsmasq is managed by Cobbler. Cobbler may also manage isc-dhcpd + BIND > > [0]. > > Great - thanks for the link. > > > So, switching from dnsmasq requires 2 more services been installed. I > > think it's not a big deal to a update Cobbler container. The most work > will > > be in adding ipv6 support into everything: fuelmenu, Nailgun/UI, a lot of > > Puppet modules, especially L23network module, OSTF. Also, it doubles QA > > efforts. > > Thanks - I agree there is a lot of places we'll have to cover. > > > Other questions come up. Do we want to support dual stack too? When a > user > > will choose an IP version: once during master node installation or it'll > be > > allowed to switch over in any moment? > > I think probably in the first iteration it'll be dualstack, since we'll > mostly just be working on enabling IPv6 in all the components. Stretch > goal will be for Fuel to not require IPv4 at all so that in the future > we can deploy it in IPv6 only environments. > > -- > Sean M. Collins > > __ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > -- Andrey Danin ada...@mirantis.com skype: gcon.monolake __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Fuel] How much do we rely on dnsmasq?
On Thu, Aug 27, 2015 at 08:27:24PM EDT, Andrey Danin wrote: > Hi, Sean, > > Dnsmasq is managed by Cobbler. Cobbler may also manage isc-dhcpd + BIND > [0]. Great - thanks for the link. > So, switching from dnsmasq requires 2 more services been installed. I > think it's not a big deal to a update Cobbler container. The most work will > be in adding ipv6 support into everything: fuelmenu, Nailgun/UI, a lot of > Puppet modules, especially L23network module, OSTF. Also, it doubles QA > efforts. Thanks - I agree there is a lot of places we'll have to cover. > Other questions come up. Do we want to support dual stack too? When a user > will choose an IP version: once during master node installation or it'll be > allowed to switch over in any moment? I think probably in the first iteration it'll be dualstack, since we'll mostly just be working on enabling IPv6 in all the components. Stretch goal will be for Fuel to not require IPv4 at all so that in the future we can deploy it in IPv6 only environments. -- Sean M. Collins __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Fuel] How much do we rely on dnsmasq?
Hi, Sean, Dnsmasq is managed by Cobbler. Cobbler may also manage isc-dhcpd + BIND [0]. So, switching from dnsmasq requires 2 more services been installed. I think it's not a big deal to a update Cobbler container. The most work will be in adding ipv6 support into everything: fuelmenu, Nailgun/UI, a lot of Puppet modules, especially L23network module, OSTF. Also, it doubles QA efforts. Other questions come up. Do we want to support dual stack too? When a user will choose an IP version: once during master node installation or it'll be allowed to switch over in any moment? [0] http://cobbler.github.io/manuals/2.6.0/3/4/2_-_Managing_DNS.html On Thu, Aug 27, 2015 at 10:06 PM, Sean M. Collins wrote: > Hi, > > I wanted to ask if we have any opinions on dnsmasq, since I am doing > some hacking on adding IPv6 support to fuel, for the provisioning stage. > > https://review.openstack.org/#/c/216787/ > > Depending on if dnsmasq supports DHCPv6 options for PXE booting, we may > need to investigate replacing it with isc-dhcpd. Which is no small task, > I can imagine. > > The spec review has links to a post I made on the dnsmasq mailing list > to see if there is anyone there that can answer my question. > > -- > Sean M. Collins > > __ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > -- Andrey Danin ada...@mirantis.com skype: gcon.monolake __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [Fuel] How much do we rely on dnsmasq?
Hi, I wanted to ask if we have any opinions on dnsmasq, since I am doing some hacking on adding IPv6 support to fuel, for the provisioning stage. https://review.openstack.org/#/c/216787/ Depending on if dnsmasq supports DHCPv6 options for PXE booting, we may need to investigate replacing it with isc-dhcpd. Which is no small task, I can imagine. The spec review has links to a post I made on the dnsmasq mailing list to see if there is anyone there that can answer my question. -- Sean M. Collins __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev