[openstack-dev] [Neutron] The Available Virtual Network Topology for a Tenant

Zirui Zhuang zr.zz.alp at gmail.com
Thu Sep 18 02:18:15 UTC 2014


Hello everyone.

>From what I can see in current neutron implementation, a tenant may
organize its own network in following topology,

External Network <-> Tenant Router <-> Tenant Networks <-> Tenant Subnets
<-> Tenant Instances

This is a quite simple but efficient topology that should be enough for
most common use in IaaS environment.

>From the Neutron Concept section (
http://docs.openstack.org/havana/install-guide/install/yum/content/install-neutron.html
, Chapter 9, Section 2), I see this statement,

*"Each router has one gateway that is connected to a network and many
interfaces that are connected to subnets. "*

And its similar to the idea of a physical router.

However, the current neutron restricts the gateway to a external network.
So if this is a compromise related to the development schedule or a
designed feature. If it's the latter, then by what reason we decided not to
give tenants the freedom to control more of its network available topology.

Thanks a lot.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140918/ff95969f/attachment.html>


More information about the OpenStack-dev mailing list