network is layer 2 and subnet is layer 3. A common use case would be that one tenant creates a network with a 10.1.1.0/24 subnet. Another tenant wants to use that same network, so they create a new network and can also create the 10.1.1.0/24 subnet. On Wed, Aug 14, 2013 at 1:12 PM, Lorin Hochstein <lorin at nimbisservices.com>wrote: > Here's a neutron implementation question: why does neutron model "network" > and "subnet" as separate entities? > > Or, to ask another way, are there are any practical use cases where you > would *not* have a one-to-one relationship between neutron networks and > neutron subnets in an OpenStack deployment? (e.g. one neutron network > associated with multiple neutron subnets, or one neutron network associated > with zero neutron subnets)? > > Lorin > -- > Lorin Hochstein > Lead Architect - Cloud Services > Nimbis Services, Inc. > www.nimbisservices.com > > _______________________________________________ > OpenStack-dev mailing list > OpenStack-dev at lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20130814/e75bc138/attachment.html>