[openstack-dev] [neutron] Why is "network" and "subnet" modeled separately?

P Balaji-B37839 B37839 at freescale.com
Thu Aug 15 06:32:38 UTC 2013

Though we can add multiple subnets to the Network. We don't have an option to attach/select subnet to Network. It is observed that when all the IP Address are consumed from first subnet, then it starts using the next subnet available for the network.

More flexibility in selecting subnet to Network will be a good thing to have.

Any thoughts or use-case information for not giving an option to select subnet for a Network?


From: Lorin Hochstein [mailto:lorin at nimbisservices.com]
Sent: Thursday, August 15, 2013 1:43 AM
To: openstack-dev at lists.openstack.org
Subject: [openstack-dev] [neutron] Why is "network" and "subnet" modeled separately?

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 Hochstein
Lead Architect - Cloud Services
Nimbis Services, Inc.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20130815/981123c4/attachment.html>

More information about the OpenStack-dev mailing list