Open Stack

I think the trunk port BP referenced below (and registered by myself) would likely solve this use case. There is no design summit session to discuss this, but I hope to have an unconference slot in Hong Kong to discuss this with folks who are interested.

Thanks,
Kyle

On Oct 28, 2013, at 4:34 PM, beyounn <beyounn at gmail.com> wrote:

> Hi Erik,
> While we were discussing about the service VM framework, the trunk port support was also mentioned.  I think people do see the needs for it.
> I have seen someone have mentioned another BP https://blueprints.launchpad.net/neutron/+spec/quantum-network-bundle-api in your BP already. Maybe it is same as what you are doing.
> And the trunk port use case can also impact how the zone being constructed in the fwaas context (when a firewall VM uses a trunk port to connect multiple networks). The basic question is how we should present a trunk port and the vlan on a trunk port to Neutron.
>  
> Yi
>  
> From: Erik Moe [mailto:emoe264 at gmail.com] 
> Sent: Monday, October 28, 2013 1:56 PM
> To: openstack-dev at lists.openstack.org
> Subject: [openstack-dev] [Neutron] VLAN aware VMs
>  
> Hi!
> 
> We are looking into how to make it possible for tenant VMs to use VLAN tagged traffic to connect to different Neutron networks.
>  
> The VID on frames sent/received will determine which Neutron network the frames are connected to.
> 
> https://blueprints.launchpad.net/neutron/+spec/vlan-aware-vms
> 
> I would like to find others that also see the need for this kind of functionality and would like to discuss this.
> 
> Regards,
> Erik
> 
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev