Mailing-List: contact marketing-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: marketing@cloudstack.apache.org
Received-SPF: pass (athena.apache.org: domain of runseb@gmail.com designates
 74.125.82.171 as permitted sender)
Content-Type: text/plain; charset=iso-2022-jp
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: [Talk Idea][WIP] VXLAN support
From: Sebastien Goasguen <runseb@gmail.com>
In-Reply-To: 
 <2F06164F2E8ECE4A97106FC49A25C3B2045D8B98@IAD-WPRD-XCHB03.corp.verio.net>
Date: Tue, 30 Apr 2013 03:57:44 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <72C41905-13D4-4629-8C92-B276BA621B4B@gmail.com>
References: 
 <2F06164F2E8ECE4A97106FC49A25C3B2045D8B98@IAD-WPRD-XCHB03.corp.verio.net>
To: marketing@cloudstack.apache.org

Hi Toshiaki,

This is perfectly suitable.
you can submit your proposal at:
http://www.cloudstackcollab.com/CfP/

To submit your patch you can check:
http://www.slideshare.net/sebastiengoasguen/git-101-for-cloudstack

or
http://cloudstack.apache.org/develop/non-committer.html

If you have any questions regarding your patch please email =
dev@cloudstack.apache.org

thank you,

-Sebastien


On Apr 29, 2013, at 5:27 PM, "Toshiaki Hatano" =
<toshiaki.hatano@verio.net> wrote:

> Hello Marketing,
>=20
>=20
>=20
> It=1B$B!G=1B(Bs my first time to post CloudStack mailing-list.
>=20
> I=1B$B!G=1B(Bd like to ask question regarding CfP for the CloudStack =
Collaboration Conference.
>=20
>=20
>=20
> I=1B$B!G=1B(Bm currently working on integration between Linux native =
VXLAN and CloudStack as my internship project.
>=20
> I=1B$B!G=1B(Bd like to talk and discuss in Conference about VXLAN =
support on CloudStack.
>=20
>=20
>=20
> Is that suitable topic for conference or not?
>=20
> Please comment!
>=20
>=20
>=20
> I already have working demo code, which simply replaces VLAN with =
VXLAN under cloud-agent level in KVM hypervisor.
>=20
>=20
>=20
>=20
>=20
> ##) Here is the detail.
>=20
>=20
>=20
> 1.     Background
>=20
> VXLAN is one of emerging technologies to overcome VLAN scalability =
limitation, being standardized in IETF [1].
>=20
> VXLAN enable Layer 2 tunneling over UDP/IP with VLAN-like =
encapsulation and allow 16M isolated networks in the domain.
>=20
> CloudStack currently have the capability to use VLAN (or GRE) to =
isolate customer networks in advanced networking mode.=20
>=20
> But, due to the VLAN ID limitation (there=1B$B!G=1B(Bre only 4096 =
IDs), only 4K networks (=3D account) can be in a zone using VLAN.
>=20
> 4K is not enough for IaaS provider like us, we already allocated much =
IDs in our DCs and VPC must be going to accelerate consumption rate.
>=20
> VXLAN will solve this 4K limitation.
>=20
> OpenStack already started process[2] to support Linux native VXLAN.=20
>=20
>=20
>=20
> 2.     Implementation
>=20
> There=1B$B!G=1B(Bre three ways to use VXLAN in Linux, Open vSwitch and =
user land implementation and Linux kernel (3.7 or later) native support.=20=

>=20
> We choose Linux native support because it=1B$B!G=1B(Bs the simplest =
way. As always, simple is the best.
>=20
> As proof of concept, I=1B$B!G=1B(Bve modified =
=1B$B!H=1B(Bmodifyvlan.sh=1B$B!I=1B(B script which is actual VLAN =
create/delete manipulation script called from cloud-agent, to create and =
to use VXLAN interface instead of VLAN interface.
>=20
> Modified script is tested with CloudStack 4.0.1 and 3 KVM hypervisors =
based on CentOS 6.4 + 3.8.6 kernel.
>=20
> And it looks working. (I=1B$B!G=1B(Bm still testing)
>=20
>=20
>=20
> 3.     TODOs
>=20
> To receive merit from VXLAN, cloud-agent and cloud-server code should =
be modified to recognize VXLAN and to allocate VXLAN IDs (VNI) from =
VXLAN=1B$B!G=1B(Bs large ID space.
>=20
> There=1B$B!G=1B(Bre difference in parameter between L2 encapsulation =
(VLAN) and L3 encapsulation (VXLAN) so it should be handled too.
>=20
> (E.g. MTU, source IP address, multicast group)
>=20
> I=1B$B!G=1B(Bd like to commit my code but I don=1B$B!G=1B(Bt know how =
to so I=1B$B!G=1B(Bd like some help to learn the process J
>=20
>=20
>=20
> [1] http://datatracker.ietf.org/doc/draft-mahalingam-dutt-dcops-vxlan =
<http://datatracker.ietf.org/doc/draft-mahalingam-dutt-dcops-vxlan/> / =
<http://datatracker.ietf.org/doc/draft-mahalingam-dutt-dcops-vxlan/>=20
>=20
> [2] https://review.openstack.org/#/c/26516/
>=20
>=20
>=20
> Best Regards,
>=20
> -- =20
>=20
> Toshiaki Hatano
>=20
> Technical Account Manager I
>=20
> Verio, an NTT Communications company=20
> E-mail:   toshiaki.hatano@verio.net
>=20
> AIM:     toshiaki.hatano@verio.net
>=20
> Phone:  (801)437-7482  Office
>=20
>        (801)960-6410  Cellular
>=20
>=20
>=20
>=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.