You are viewing a plain text version of this content. The canonical link for it is here.
Posted to marketing@cloudstack.apache.org by Toshiaki Hatano <to...@verio.net> on 2013/04/29 23:27:34 UTC

[Talk Idea][WIP] VXLAN support

Hello Marketing,

 

It’s my first time to post CloudStack mailing-list.

I’d like to ask question regarding CfP for the CloudStack Collaboration Conference.

 

I’m currently working on integration between Linux native VXLAN and CloudStack as my internship project.

I’d like to talk and discuss in Conference about VXLAN support on CloudStack.

 

Is that suitable topic for conference or not?

Please comment!

 

I already have working demo code, which simply replaces VLAN with VXLAN under cloud-agent level in KVM hypervisor.

 

 

##) Here is the detail.

 

1.     Background

VXLAN is one of emerging technologies to overcome VLAN scalability limitation, being standardized in IETF [1].

VXLAN enable Layer 2 tunneling over UDP/IP with VLAN-like encapsulation and allow 16M isolated networks in the domain.

CloudStack currently have the capability to use VLAN (or GRE) to isolate customer networks in advanced networking mode. 

But, due to the VLAN ID limitation (there’re only 4096 IDs), only 4K networks (= account) can be in a zone using VLAN.

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.

VXLAN will solve this 4K limitation.

OpenStack already started process[2] to support Linux native VXLAN. 

 

2.     Implementation

There’re three ways to use VXLAN in Linux, Open vSwitch and user land implementation and Linux kernel (3.7 or later) native support. 

We choose Linux native support because it’s the simplest way. As always, simple is the best.

As proof of concept, I’ve modified “modifyvlan.sh” 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. (I’m still testing)

 

3.     TODOs

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’s large ID space.

There’re difference in parameter between L2 encapsulation (VLAN) and L3 encapsulation (VXLAN) so it should be handled too.

(E.g. MTU, source IP address, multicast group)

I’d like to commit my code but I don’t know how to so I’d like some help to learn the process J

 

[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/> 

[2] https://review.openstack.org/#/c/26516/

 

Best Regards,

--  

Toshiaki Hatano

Technical Account Manager I

Verio, an NTT Communications company 
E-mail:   toshiaki.hatano@verio.net

AIM:     toshiaki.hatano@verio.net

Phone:  (801)437-7482  Office

        (801)960-6410  Cellular

 



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.

RE: [Talk Idea][WIP] VXLAN support

Posted by Toshiaki Hatano <to...@verio.net>.
Hi Sebastian and Chip,

Thank you for you advices!
I'll submit the proposal to CfP and check dev mail-list.

--
Toshiaki

> -----Original Message-----
> From: Chip Childers [mailto:chip.childers@sungard.com]
> Sent: Tuesday, April 30, 2013 8:34 AM
> To: marketing@cloudstack.apache.org
> Subject: Re: [Talk Idea][WIP] VXLAN support
> 
> On Mon, Apr 29, 2013 at 05:27:34PM -0400, Toshiaki Hatano wrote:
> > Hello Marketing,
> >
> > It’s my first time to post CloudStack mailing-list.
> 
> Welcome!
> 
> >
> > I’d like to ask question regarding CfP for the CloudStack Collaboration
> Conference.
> >
> > I’m currently working on integration between Linux native VXLAN and
> CloudStack as my internship project.
> >
> > I’d like to talk and discuss in Conference about VXLAN support on
> CloudStack.
> >
> >
> >
> > Is that suitable topic for conference or not?
> 
> Absolutely!  Please submit this as a talk proposal.
> 
> >
> > Please comment!
> >
> >
> >
> > I already have working demo code, which simply replaces VLAN with VXLAN
> under cloud-agent level in KVM hypervisor.
> >
> 
> Sebastien already gave you pointers for joining the
> dev@cloudstack.apache.org list and for how to propose your patch...  but
> I'll add to that by saying that this looks very interesting!  Please do
> propose it on the dev list.


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.

Re: [Talk Idea][WIP] VXLAN support

Posted by Chip Childers <ch...@sungard.com>.
On Mon, Apr 29, 2013 at 05:27:34PM -0400, Toshiaki Hatano wrote:
> Hello Marketing,
> 
> It’s my first time to post CloudStack mailing-list.

Welcome!

> 
> I’d like to ask question regarding CfP for the CloudStack Collaboration Conference.
> 
> I’m currently working on integration between Linux native VXLAN and CloudStack as my internship project.
> 
> I’d like to talk and discuss in Conference about VXLAN support on CloudStack.
> 
>  
> 
> Is that suitable topic for conference or not?

Absolutely!  Please submit this as a talk proposal.

> 
> Please comment!
> 
>  
> 
> I already have working demo code, which simply replaces VLAN with VXLAN under cloud-agent level in KVM hypervisor.
> 

Sebastien already gave you pointers for joining the
dev@cloudstack.apache.org list and for how to propose your patch...  but
I'll add to that by saying that this looks very interesting!  Please do
propose it on the dev list.

Re: [Talk Idea][WIP] VXLAN support

Posted by Sebastien Goasguen <ru...@gmail.com>.
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" <to...@verio.net> wrote:

> Hello Marketing,
> 
> 
> 
> It’s my first time to post CloudStack mailing-list.
> 
> I’d like to ask question regarding CfP for the CloudStack Collaboration Conference.
> 
> 
> 
> I’m currently working on integration between Linux native VXLAN and CloudStack as my internship project.
> 
> I’d like to talk and discuss in Conference about VXLAN support on CloudStack.
> 
> 
> 
> Is that suitable topic for conference or not?
> 
> Please comment!
> 
> 
> 
> I already have working demo code, which simply replaces VLAN with VXLAN under cloud-agent level in KVM hypervisor.
> 
> 
> 
> 
> 
> ##) Here is the detail.
> 
> 
> 
> 1.     Background
> 
> VXLAN is one of emerging technologies to overcome VLAN scalability limitation, being standardized in IETF [1].
> 
> VXLAN enable Layer 2 tunneling over UDP/IP with VLAN-like encapsulation and allow 16M isolated networks in the domain.
> 
> CloudStack currently have the capability to use VLAN (or GRE) to isolate customer networks in advanced networking mode. 
> 
> But, due to the VLAN ID limitation (there’re only 4096 IDs), only 4K networks (= account) can be in a zone using VLAN.
> 
> 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.
> 
> VXLAN will solve this 4K limitation.
> 
> OpenStack already started process[2] to support Linux native VXLAN. 
> 
> 
> 
> 2.     Implementation
> 
> There’re three ways to use VXLAN in Linux, Open vSwitch and user land implementation and Linux kernel (3.7 or later) native support. 
> 
> We choose Linux native support because it’s the simplest way. As always, simple is the best.
> 
> As proof of concept, I’ve modified “modifyvlan.sh” 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. (I’m still testing)
> 
> 
> 
> 3.     TODOs
> 
> 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’s large ID space.
> 
> There’re difference in parameter between L2 encapsulation (VLAN) and L3 encapsulation (VXLAN) so it should be handled too.
> 
> (E.g. MTU, source IP address, multicast group)
> 
> I’d like to commit my code but I don’t know how to so I’d like some help to learn the process J
> 
> 
> 
> [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/> 
> 
> [2] https://review.openstack.org/#/c/26516/
> 
> 
> 
> Best Regards,
> 
> --  
> 
> Toshiaki Hatano
> 
> Technical Account Manager I
> 
> Verio, an NTT Communications company 
> E-mail:   toshiaki.hatano@verio.net
> 
> AIM:     toshiaki.hatano@verio.net
> 
> Phone:  (801)437-7482  Office
> 
>        (801)960-6410  Cellular
> 
> 
> 
> 
> 
> 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.