[openstack-dev] [Neutron] Deprecating the use_namespaces option - Now's the time to speak up!
Neil Jerram
neil.jerram at metaswitch.com
Fri Mar 20 20:06:30 UTC 2015
Assaf Muller <amuller at redhat.com> 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
More information about the OpenStack-dev
mailing list