[openstack-dev] [Neutron] VLAN aware VMs
Isaku Yamahata
isaku.yamahata at gmail.com
Tue Nov 5 07:42:47 UTC 2013
I'm fine with 14:00 on Thursday.
On Tue, Nov 05, 2013 at 07:59:55AM +0100,
Erik Moe <emoe264 at gmail.com> wrote:
> Ok, 2PM Thursday is fine with me.
>
>
>
> On Tue, Nov 5, 2013 at 6:49 AM, Kyle Mestery (kmestery)
> <kmestery at cisco.com>wrote:
>
> > How about if we do a developers lounge chat at 2PM Thursday?
> >
> > On Nov 4, 2013, at 10:20 PM, Yi Sun <beyounn at gmail.com>
> > wrote:
> >
> > > Guys,
> > > I just checked the schedule of unconference sessions. There are no free
> > slots anymore.
> > >
> > > Yi
> > >
> > > On Tuesday, October 29, 2013, Isaku Yamahata wrote:
> > > Hi Erik and Li.
> > > Unconference at the next summit?
> > >
> > > On Mon, Oct 28, 2013 at 02:34:28PM -0700,
> > > 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-apiin
> > > > 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
> > >
> > >
> > > --
> > > Isaku Yamahata <isaku.yamahata at gmail.com>
> > >
> > > _______________________________________________
> > > OpenStack-dev mailing list
> > > OpenStack-dev at lists.openstack.org
> > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> > >
> > >
> > > --
> > > Android-x86
> > > http://www.android-x86.org
> > > _______________________________________________
> > > OpenStack-dev mailing list
> > > OpenStack-dev at lists.openstack.org
> > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >
> >
> > _______________________________________________
> > OpenStack-dev mailing list
> > OpenStack-dev at lists.openstack.org
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >
--
Isaku Yamahata <isaku.yamahata at gmail.com>
More information about the OpenStack-dev
mailing list