[openstack-dev] [Neutron][IPAM] Uniqueness of subnets within a tenant

Kevin Benton blak111 at gmail.com
Fri Mar 20 21:16:01 UTC 2015

To clarify a bit, we obviously divide lots of things by tenant (quotas,
network listing, etc). The difference is that we have nothing right now
that has to be unique within a tenant. Are there objects that are uniquely
scoped to a tenant in Nova/Glance/etc?

On Fri, Mar 20, 2015 at 12:50 PM, Jay Pipes <jaypipes at gmail.com> wrote:

> On 03/20/2015 03:37 PM, Carl Baldwin wrote:
>> On Fri, Mar 20, 2015 at 12:31 PM, Jay Pipes <jaypipes at gmail.com> wrote:
>>> This is a question purely out of curiousity. Why is Neutron averse to the
>>> concept of using tenants as natural ways of dividing up the cloud --
>>> which
>>> at its core means "multi-tenant", on-demand computing and networking?
>>  From what I've heard others say both in this thread and privately to
>> me, there are already a lot of cases where a tenant will use the same
>> address range to stamp out identical topologies.  It occurred to me
>> that we might even being doing this with our own gate infrastructure
>> but I don't know for sure.
>>  Is this just due to a lack of traditional use of the term in networking
>>> literature? Or is this something more deep-grained (architecturally) than
>>> that?
>> We already have NAT serving as the natural divider between them and so
>> there is no reason to create another artificial way of dividing them
>> up which will force them to change their practices.  I've come to
>> terms with this since my earlier replies to this thread.
> OK, thanks for the info, Carl, appreciated.
> Best,
> -jay
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Kevin Benton
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150320/b775710e/attachment.html>

More information about the OpenStack-dev mailing list