Re: [openstack-dev] [Neutron] Deprecating the use_namespaces option - Now's the time to speak up!
+1 for deprecation if people don’t have use cases / good reasons to keep it, I don’t know and I can’t think of any, but that doesn’t mean they don’t exist. Miguel Ángel Ajo On Monday, 23 de March de 2015 at 2:34, shihanzhang wrote: > +1 to deprecate this option > > At 2015-03-21 02:57:09, "Assaf Muller" wrote: >Hello > everyone, > >The use_namespaces option in the L3 and DHCP Neutron agents > controls if you >can create multiple routers and DHCP networks managed by a > single L3/DHCP agent, >or if the agent manages only a single resource. > >Are > the setups out there *not* using the use_namespaces option? I'm curious as > >to why, and if it would be difficult to migrate such a setup to use > namespaces. > >I'm asking because use_namespaces complicates Neutron code for > what I gather >is an option that has not been relevant for years. I'd like to > deprecate the option >for Kilo and remove it in Liberty. > > >Assaf Muller, > Cloud Networking Engineer >Red Hat > > >__ > >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 Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > (mailto:openstack-dev-requ...@lists.openstack.org?subject:unsubscribe) > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > __ 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] [Neutron] Deprecating the use_namespaces option - Now's the time to speak up!
+1 to deprecate this option At 2015-03-21 02:57:09, "Assaf Muller" wrote: >Hello everyone, > >The use_namespaces option in the L3 and DHCP Neutron agents controls if you >can create multiple routers and DHCP networks managed by a single L3/DHCP >agent, >or if the agent manages only a single resource. > >Are the setups out there *not* using the use_namespaces option? I'm curious as >to why, and if it would be difficult to migrate such a setup to use namespaces. > >I'm asking because use_namespaces complicates Neutron code for what I gather >is an option that has not been relevant for years. I'd like to deprecate the >option >for Kilo and remove it in Liberty. > > >Assaf Muller, Cloud Networking Engineer >Red Hat > >__ >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 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] [Neutron] Deprecating the use_namespaces option - Now's the time to speak up!
I did hear of one use case.[1] :-) In all seriousness, it seems like our abstraction over executing processes must be leaking quite a bit if we can't handle a no-namespace deployment. It seems like running a command without "ip netns" in front of it shouldn't be that much harder. Or am I misunderstanding where the special-casing issues are? 1. http://lists.openstack.org/pipermail/openstack-dev/2015-March/059538.html On Fri, Mar 20, 2015 at 3:26 PM, Assaf Muller wrote: > > > - Original Message - > > Tempest tests fail when not using namespaces, so I'm not sure how well > we're > > even testing that codepath anymore. > > Hrmph, I meant to mention that the code path is basically untested but > forgot > to do that when I sent the email. > > > > > doug > > > > > > > On Mar 20, 2015, at 3:19 PM, Brian Haley wrote: > > > > > > On 03/20/2015 02:57 PM, Assaf Muller wrote: > > >> Hello everyone, > > >> > > >> The use_namespaces option in the L3 and DHCP Neutron agents controls > if > > >> you > > >> can create multiple routers and DHCP networks managed by a single > L3/DHCP > > >> agent, > > >> or if the agent manages only a single resource. > > >> > > >> Are the setups out there *not* using the use_namespaces option? I'm > > >> curious as > > >> to why, and if it would be difficult to migrate such a setup to use > > >> namespaces. > > > > > > This is a recent Neutron bug where someone is not using namespaces, so > they > > > exist: > > > > > > https://bugs.launchpad.net/neutron/+bug/1428007 > > > > > >> I'm asking because use_namespaces complicates Neutron code for what I > > >> gather > > >> is an option that has not been relevant for years. I'd like to > deprecate > > >> the option > > >> for Kilo and remove it in Liberty. > > > > > > +1 from me for deprecation. > > > > > > -Brian > > > > > > > > > > __ > > > 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 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 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 > -- Kevin Benton __ 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] [Neutron] Deprecating the use_namespaces option - Now's the time to speak up!
- Original Message - > Tempest tests fail when not using namespaces, so I'm not sure how well we're > even testing that codepath anymore. Hrmph, I meant to mention that the code path is basically untested but forgot to do that when I sent the email. > > doug > > > > On Mar 20, 2015, at 3:19 PM, Brian Haley wrote: > > > > On 03/20/2015 02:57 PM, Assaf Muller wrote: > >> Hello everyone, > >> > >> The use_namespaces option in the L3 and DHCP Neutron agents controls if > >> you > >> can create multiple routers and DHCP networks managed by a single L3/DHCP > >> agent, > >> or if the agent manages only a single resource. > >> > >> Are the setups out there *not* using the use_namespaces option? I'm > >> curious as > >> to why, and if it would be difficult to migrate such a setup to use > >> namespaces. > > > > This is a recent Neutron bug where someone is not using namespaces, so they > > exist: > > > > https://bugs.launchpad.net/neutron/+bug/1428007 > > > >> I'm asking because use_namespaces complicates Neutron code for what I > >> gather > >> is an option that has not been relevant for years. I'd like to deprecate > >> the option > >> for Kilo and remove it in Liberty. > > > > +1 from me for deprecation. > > > > -Brian > > > > > > __ > > 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 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 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] [Neutron] Deprecating the use_namespaces option - Now's the time to speak up!
They blow up because they assume you can have overlapping IPs, right? On Fri, Mar 20, 2015 at 2:26 PM, Doug Wiegley wrote: > Tempest tests fail when not using namespaces, so I'm not sure how well > we're even testing that codepath anymore. > > doug > > > > On Mar 20, 2015, at 3:19 PM, Brian Haley wrote: > > > > On 03/20/2015 02:57 PM, Assaf Muller wrote: > >> Hello everyone, > >> > >> The use_namespaces option in the L3 and DHCP Neutron agents controls if > you > >> can create multiple routers and DHCP networks managed by a single > L3/DHCP agent, > >> or if the agent manages only a single resource. > >> > >> Are the setups out there *not* using the use_namespaces option? I'm > curious as > >> to why, and if it would be difficult to migrate such a setup to use > namespaces. > > > > This is a recent Neutron bug where someone is not using namespaces, so > they exist: > > > > https://bugs.launchpad.net/neutron/+bug/1428007 > > > >> I'm asking because use_namespaces complicates Neutron code for what I > gather > >> is an option that has not been relevant for years. I'd like to > deprecate the option > >> for Kilo and remove it in Liberty. > > > > +1 from me for deprecation. > > > > -Brian > > > > > > > __ > > 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 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 > -- Kevin Benton __ 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] [Neutron] Deprecating the use_namespaces option - Now's the time to speak up!
Tempest tests fail when not using namespaces, so I'm not sure how well we're even testing that codepath anymore. doug > On Mar 20, 2015, at 3:19 PM, Brian Haley wrote: > > On 03/20/2015 02:57 PM, Assaf Muller wrote: >> Hello everyone, >> >> The use_namespaces option in the L3 and DHCP Neutron agents controls if you >> can create multiple routers and DHCP networks managed by a single L3/DHCP >> agent, >> or if the agent manages only a single resource. >> >> Are the setups out there *not* using the use_namespaces option? I'm curious >> as >> to why, and if it would be difficult to migrate such a setup to use >> namespaces. > > This is a recent Neutron bug where someone is not using namespaces, so they > exist: > > https://bugs.launchpad.net/neutron/+bug/1428007 > >> I'm asking because use_namespaces complicates Neutron code for what I gather >> is an option that has not been relevant for years. I'd like to deprecate the >> option >> for Kilo and remove it in Liberty. > > +1 from me for deprecation. > > -Brian > > > __ > 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 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] [Neutron] Deprecating the use_namespaces option - Now's the time to speak up!
On 03/20/2015 02:57 PM, Assaf Muller wrote: > Hello everyone, > > The use_namespaces option in the L3 and DHCP Neutron agents controls if you > can create multiple routers and DHCP networks managed by a single L3/DHCP > agent, > or if the agent manages only a single resource. > > Are the setups out there *not* using the use_namespaces option? I'm curious as > to why, and if it would be difficult to migrate such a setup to use > namespaces. This is a recent Neutron bug where someone is not using namespaces, so they exist: https://bugs.launchpad.net/neutron/+bug/1428007 > I'm asking because use_namespaces complicates Neutron code for what I gather > is an option that has not been relevant for years. I'd like to deprecate the > option > for Kilo and remove it in Liberty. +1 from me for deprecation. -Brian __ 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] [Neutron] Deprecating the use_namespaces option - Now's the time to speak up!
Assaf Muller writes: > Hello everyone, Hi Assaf, > The use_namespaces option in the L3 and DHCP Neutron agents controls if you > can create multiple routers and DHCP networks managed by a single L3/DHCP > agent, > or if the agent manages only a single resource. > > Are the setups out there *not* using the use_namespaces option? I'm curious as > to why, and if it would be difficult to migrate such a setup to use > namespaces. > > I'm asking because use_namespaces complicates Neutron code for what I gather > is an option that has not been relevant for years. I'd like to deprecate the > option > for Kilo and remove it in Liberty. I'm not clear what you're proposing. After the option is removed, will the code always behave as it used to when use_namespaces was False, or as when it was True? FWIW, my project Calico [1] uses a modified Neutron DHCP agent, where the behaviour for use_namespaces = False is closer to what we need. So we effectively arrange to ignore the use_namespaces setting, and behave as though it was False [2]. However, that isn't the only change we need, and it's also not clear that patching the Neutron DHCP agent in this way (or looking at upstreaming such a patch) will be our long term approach. Hence this case probably shouldn't be a significant one for deciding on your proposal. Regards, Neil [1] http://www.projectcalico.org/ [2] https://github.com/Metaswitch/calico-neutron/commit/af2f613368239e2a86b6312bae6e5e70a53d1396 __ 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] [Neutron] Deprecating the use_namespaces option - Now's the time to speak up!
- Original Message - > Assaf Muller writes: > > > Hello everyone, > > Hi Assaf, > > > The use_namespaces option in the L3 and DHCP Neutron agents controls if you > > can create multiple routers and DHCP networks managed by a single L3/DHCP > > agent, > > or if the agent manages only a single resource. > > > > Are the setups out there *not* using the use_namespaces option? I'm curious > > as > > to why, and if it would be difficult to migrate such a setup to use > > namespaces. > > > > I'm asking because use_namespaces complicates Neutron code for what I > > gather > > is an option that has not been relevant for years. I'd like to deprecate > > the option > > for Kilo and remove it in Liberty. > > I'm not clear what you're proposing. After the option is removed, will > the code always behave as it used to when use_namespaces was False, or > as when it was True? I'm sorry, I should have specified: I propose to remove the option and keep the default behavior, which is True. > > FWIW, my project Calico [1] uses a modified Neutron DHCP agent, where > the behaviour for use_namespaces = False is closer to what we need. So > we effectively arrange to ignore the use_namespaces setting, and behave > as though it was False [2]. > > However, that isn't the only change we need, and it's also not clear > that patching the Neutron DHCP agent in this way (or looking at > upstreaming such a patch) will be our long term approach. Hence this > case probably shouldn't be a significant one for deciding on your > proposal. > > Regards, > Neil > > [1] http://www.projectcalico.org/ > [2] > https://github.com/Metaswitch/calico-neutron/commit/af2f613368239e2a86b6312bae6e5e70a53d1396 > __ 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] [Neutron] Deprecating the use_namespaces option - Now's the time to speak up!
Assaf Muller writes: > Hello everyone, Hi Assaf, > The use_namespaces option in the L3 and DHCP Neutron agents controls if you > can create multiple routers and DHCP networks managed by a single L3/DHCP > agent, > or if the agent manages only a single resource. > > Are the setups out there *not* using the use_namespaces option? I'm curious as > to why, and if it would be difficult to migrate such a setup to use > namespaces. > > I'm asking because use_namespaces complicates Neutron code for what I gather > is an option that has not been relevant for years. I'd like to deprecate the > option > for Kilo and remove it in Liberty. I'm not clear what you're proposing. After the option is removed, will the code always behave as it used to when use_namespaces was False, or as when it was True? FWIW, my project Calico [1] uses a modified Neutron DHCP agent, where the behaviour for use_namespaces = False is closer to what we need. So we effectively arrange to ignore the use_namespaces setting, and behave as though it was False [2]. However, that isn't the only change we need, and it's also not clear that patching the Neutron DHCP agent in this way (or looking at upstreaming such a patch) will be our long term approach. Hence this case probably shouldn't be a significant one for deciding on your proposal. Regards, Neil [1] http://www.projectcalico.org/ [2] https://github.com/Metaswitch/calico-neutron/commit/af2f613368239e2a86b6312bae6e5e70a53d1396 __ 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] [Neutron] Deprecating the use_namespaces option - Now's the time to speak up!
+1 Would like to hear feedback hoping that deprecation is viable. Carl On Fri, Mar 20, 2015 at 12:57 PM, Assaf Muller wrote: > Hello everyone, > > The use_namespaces option in the L3 and DHCP Neutron agents controls if you > can create multiple routers and DHCP networks managed by a single L3/DHCP > agent, > or if the agent manages only a single resource. > > Are the setups out there *not* using the use_namespaces option? I'm curious as > to why, and if it would be difficult to migrate such a setup to use > namespaces. > > I'm asking because use_namespaces complicates Neutron code for what I gather > is an option that has not been relevant for years. I'd like to deprecate the > option > for Kilo and remove it in Liberty. > > > Assaf Muller, Cloud Networking Engineer > Red Hat > > __ > 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 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] [Neutron] Deprecating the use_namespaces option - Now's the time to speak up!
Hello everyone, The use_namespaces option in the L3 and DHCP Neutron agents controls if you can create multiple routers and DHCP networks managed by a single L3/DHCP agent, or if the agent manages only a single resource. Are the setups out there *not* using the use_namespaces option? I'm curious as to why, and if it would be difficult to migrate such a setup to use namespaces. I'm asking because use_namespaces complicates Neutron code for what I gather is an option that has not been relevant for years. I'd like to deprecate the option for Kilo and remove it in Liberty. Assaf Muller, Cloud Networking Engineer Red Hat __ 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
