Mailing-List: contact dev-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Received-SPF: pass (nike.apache.org: local policy)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="utf-8"
Importance: normal
Priority: normal
Content-Transfer-Encoding: quoted-printable
Subject: [PROPOSAL] [CLOUDSTACK-2328] Linux native VXLAN support on KVM
 hypervisor
Date: Fri, 17 May 2013 19:49:22 -0400
Message-ID: 
 <2F06164F2E8ECE4A97106FC49A25C3B2046DDC0E@IAD-WPRD-XCHB03.corp.verio.net>
Thread-Topic: [PROPOSAL] [CLOUDSTACK-2328] Linux native VXLAN support on KVM
 hypervisor
Thread-Index: Ac5TWIDhjOCoa7s3SfmGlj5l61Gf0Q==
From: "Toshiaki Hatano" <toshiaki.hatano@verio.net>
To: <dev@cloudstack.apache.org>

Hi all,

I've done initial draft of FS.
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Feature+Proposal+-=
+Linux+native+VXLAN+support+on+KVM+hypervisor

Please review it and provide your comment and feedback.
And let me know if there're something unclear or missing, I'll update as =
soon as possible.

I'd like to assign Jira ticket to me but it looks I don't have =
permission to do so.
https://issues.apache.org/jira/browse/CLOUDSTACK-2328
Could anyone kindly assign the ticket to me?

Thanks,
--
Toshiaki

> -----Original Message-----
> From: Toshiaki Hatano [mailto:toshiaki.hatano@verio.net]
> Sent: Friday, May 03, 2013 3:50 PM
> To: dev@cloudstack.apache.org; users@cloudstack.apache.org
> Subject: RE: [DISCUSS] Linux native VXLAN support on KVM hypervisor
>=20
> Thank you all for your comment and approval!
>=20
> I agree with Justin's proposal.
> And yesterday, Open vSwitch released v1.10.0 with VXLAN support.
> http://openvswitch.org/pipermail/announce/2013-May/000052.html
>=20
>=20
> I've created Jira ticket and start writing design doc.
> https://issues.apache.org/jira/browse/CLOUDSTACK-2328
>=20
> Once I've done design doc, I'll submit it to dev list.
>=20
> Sincerely,
> --
> Toshiaki
>=20
> > -----Original Message-----
> > From: Justin Grudzien [mailto:grudzien@gmail.com]
> > Sent: Thursday, May 02, 2013 5:35 PM
> > To: dev@cloudstack.apache.org
> > Cc: dev@cloudstack.apache.org
> > Subject: Re: [DISCUSS] Linux native VXLAN support on KVM hypervisor
> >
> > I will +1 this. I spoke with Cisco a few weeks ago and they =
certainly
> > see VXLANS as being the future for cloud infrastructures. In =
addition
> > to Linux support we should look at the Cisco 1000v and open vSwitch =
support
> a well.
> > Cisco said they already have VMWare support today on the 1000v with
> > KVM coming soon.
> >
> > Justin
> >
> > Sent from my iPhone
> >
> > On May 2, 2013, at 3:31 PM, Chip Childers =
<chip.childers@sungard.com>
> wrote:
> >
> > > On Wed, May 01, 2013 at 04:58:12PM -0400, Toshiaki Hatano wrote:
> > >> Hi all,
> > >>
> > >> I=E2=80=99d like to add Linux native VXLAN support on KVM =
hypervisor.
> > >>
> > >> Currently, advanced zone with VLAN isolation can hold only 4k
> > >> networks
> > (=3D accounts) in a zone due to the VLAN ID limitation.
> > >> 4k accounts per zone is not enough for IaaS provider like us.
> > >> Furthermore, VPC will allow single account to consume multiple
> networks.
> > >>
> > >> Linux kernel 3.7 or later supports VXLAN as part of its ordinal
> > >> networking
> > function.
> > >> VXLAN enable Layer 2 tunneling over UDP/IP with VLAN-like
> > >> encapsulation
> > and allow 16M isolated networks in the domain.
> > >> So, by using linux native VXLAN support, we can extend network
> > >> limits
> > without introducing unnecessary complexity.
> > >> (But in other words, it=E2=80=99s not as flexible as Open =
vSwitch. Only
> > >> thing Linux native VXLAN provides is multipoint L2 tunneling.)
> > >>
> > >> Any thoughts about this?
> > >>
> > >>
> > >> P.S.
> > >>
> > >> I=E2=80=99m currently working on this as my internship project.
> > >> As proof of concept, I=E2=80=99ve modified =
=E2=80=9Cmodifyvlan.sh=E2=80=9D script which is
> > >> actual
> > VLAN create/delete manipulation script called from cloud-agent, to
> > create and to use VXLAN interface instead of VLAN interface.
> > >> Modified script is tested with CloudStack 4.0.1 and 3 KVM
> > >> hypervisors
> > based on CentOS 6.4 + 3.8.6 kernel.
> > >> And it looks working. (But I=E2=80=99m still testing)
> > >>
> > >>
> > >> P.S.2.
> > >>
> > >> FYI: OpenStack already started process [1] to support Linux =
native
> VXLAN.
> > >> [1] https://review.openstack.org/#/c/26516/
> > >>
> > >>
> > >> Best Regards,
> > >> --
> > >> Toshiaki Hatano
> > >
> > > I note that no one has replied to this thread yet, but I'll give =
you
> > > my general +1 on the idea.
> > >
> > > Can some of the network-centric folks on the dev list please speak
> > > up on the proposal?
> > >
> > > -chip
>=20
>=20
> This email message is intended for the use of the person to whom it =
has
> been sent, and may contain information that is confidential or legally
> protected. If you are not the intended recipient or have received this
> message in error, you are not authorized to copy, distribute, or =
otherwise
> use this message or its attachments. Please notify the sender =
immediately
> by return e-mail and permanently delete this message and any =
attachments.
> Verio Inc. makes no warranty that this email is error or virus free.  =
Thank
> you.


This email message is intended for the use of the person to whom it has =
been sent, and may contain information that is confidential or legally =
protected. If you are not the intended recipient or have received this =
message in error, you are not authorized to copy, distribute, or =
otherwise use this message or its attachments. Please notify the sender =
immediately by return e-mail and permanently delete this message and any =
attachments. Verio Inc. makes no warranty that this email is error or =
virus free.  Thank you.