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

Stephen Gran stephen.gran at theguardian.com
Thu Aug 15 06:58:08 UTC 2013


Hi,

On 14/08/13 21:12, Lorin Hochstein 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)?

Different tenants might both use the same subnet range on different 
layer 2 networks.
One one layer 2 network, you might run dual stacked, ie, ipv4 and ipv6.

Supporting these use cases necessitates modeling them separately.

Cheers,
-- 
Stephen Gran
Senior Systems Integrator - theguardian.com
Please consider the environment before printing this email.
------------------------------------------------------------------
Visit theguardian.com   

On your mobile, download the Guardian iPhone app theguardian.com/iphone and our iPad edition theguardian.com/iPad   
Save up to 32% by subscribing to the Guardian and Observer - choose the papers you want and get full digital access.
Visit subscribe.theguardian.com

This e-mail and all attachments are confidential and may also
be privileged. If you are not the named recipient, please notify
the sender and delete the e-mail and all attachments immediately.
Do not disclose the contents to another person. You may not use
the information for any purpose, or store, or copy, it in any way.
 
Guardian News & Media Limited is not liable for any computer
viruses or other material transmitted with or as part of this
e-mail. You should employ virus checking software.
 
Guardian News & Media Limited
 
A member of Guardian Media Group plc
Registered Office
PO Box 68164
Kings Place
90 York Way
London
N1P 2AP
 
Registered in England Number 908396

--------------------------------------------------------------------------




More information about the OpenStack-dev mailing list