[openstack-dev] [neutron] Re: [Blueprint vlan-aware-vms] VLAN aware VMs

Yi Sun beyounn at gmail.com
Wed Dec 18 03:40:24 UTC 2013



On 12/17/13, 6:36 AM, Erik Moe wrote:
>
> Hi,
>
> thanks for your comments.
>
> see answers below.
>
> Thanks,
> Erik
>
>
> On Tue, Dec 17, 2013 at 6:17 AM, Isaku Yamahata 
> <isaku.yamahata at gmail.com <mailto:isaku.yamahata at gmail.com>> wrote:
>
>     Added openstack-dev
>
>     The document is view-only. So I commented below.
>
>     - 2 Modeling proposal
>       What's the purpose of trunk network?
>       Can you please add a use case that trunk network can't be
>     optimized away?
>
>
> In some use cases the trunk network will trunk all VLANS from a VM, so 
> they can for example be 'tunneled' to another VM or externally. In the 
> use case where a VM wants to connect to multiple Neutron networks, the 
> trunk network is a logical connection between the VM trunk port and 
> the L2-gateways. From my point of view it looks a little strange for 
> this use case, but I think this is what we said during our meeting in 
> Hong Kong (Unless I misunderstood something...).
>
> I added use case where two VMs are connected through a trunk network. 
> This can not be optimized away. The network would have to be able to 
> trunk all VLANs between the VMs.
I see the case where admin user wants to have more than one L2 gateways 
to talk to the same VM trunk port. Also, these L2 gateways may connected 
to the untagged networks that belongs different tenants. The trunk 
network should belong to a single tenant though.
Yi

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20131217/9f58c0a3/attachment.html>


More information about the OpenStack-dev mailing list