[Openstack] Multiple Physical Interfaces for Intra-Cloud Comunication - VXLAN

Martinx - ジェームズ thiagocmartinsc at gmail.com
Wed Apr 15 13:17:11 UTC 2015


Hey guys! Any ideas about how to load balance or split the VXLAN network
traffic?

On 10 April 2015 at 01:39, Martinx - ジェームズ <thiagocmartinsc at gmail.com>
wrote:

> Hello Remo, Erik,
>
>  Thanks for this fast reply!   :-)
>
>  Remo, I want to seg the communication between my Instances (i.e.,
> intra-vm communication), for example, I want to "scp from-instance-a
> to-instance-b" through "net-a" and simultaneously, "scp from instance-b
> to-instance-a" through "net-b", so, there will be no bottleneck. On this
> example, both Instances have two subnets attached but, I would like to use
> two VXLAN tunnels, one for "net-a" and another for "net-b"... And I'm not
> sure if this is even possible to achieve... Is it?
>
>  Evolving this scenario, I'll build something like this:
>
>  * Instance-A -> net-a -> "Instance-Bridge" -> net-b -> "Instance-Gateway"
> -> Internet
>
>  Here, the "Instance-bridge" will be connected at both "net-a" and
> "net-b", and will act as bridge. The gateway IP of "Instance-a" is
> allocated at "Instance-Gateway".
>
>  So, I'll need to, somehow, attach "net-a", to a VXLAN tunnel associated
> with "segment 1", and "net-b", to a VXLAN tunnel associated with "segment
> 2".
>
>  Erik, in fact, no, I don't need more bandwidth, I just need to make sure
> that the network traffic going in and out from "Instance-bridge /
> Instance-Gateway" will face no bottleneck. I'm thinking about the
> possibility to build a LACP BOND channel, using 4 ethernets, for just one
> VXLAN subnet. This way, I believe it will more dynamic and easy to
> build/manage... What do you think? Ah, and yes, I'm intending to segment
> the traffic in a specific way, as my above example.
>
>  Thanks again!
>
> Best,
> Thiago
>
> On 9 April 2015 at 23:32, Erik McCormick <emccormick at cirrusseven.com>
> wrote:
>
>> If your goal is to simply have more available bandwidth, I would think
>> you could bond the 4 interfaces into one and enable jumbo frames. Are you
>> intending to segment the traffic for some other purpose?
>> On Apr 9, 2015 7:20 PM, "Martinx - ジェームズ" <thiagocmartinsc at gmail.com>
>> wrote:
>>
>>> Hey guys!
>>>
>>>  I'm looking to build an OpenStack environment, where I have 4 physical
>>> interfaces that will be dedicated to the VXLAN tunnels but, how can I do
>>> that?
>>>
>>>  For example, I planning to create 4 "net / subnets" and each one of it
>>> will be associated with 1 VXLAN tunnel (of 4?)...
>>>
>>>  My need is that some traffic will come from one segment, pass through a
>>> Instance and goes out through another segment. So, in fact, I need to
>>> balance the network traffic, throughout more than one segment, to avoid
>>> bottlenecks.
>>>
>>>
>>>  Which approach better fits into my needs?
>>>
>>>  A- 1 VXLAN tunnel for each ethernet segment (4 tunnels) (is this even
>>> possible?)? or
>>>
>>>  B- 1 VXLAN on top of a BOND channel (here, the BOND channel will be
>>> built using 4 ethernet segments)?
>>>
>>>
>>>  I appreciate any tip!   :-)
>>>
>>>  Thanks in advance!
>>>
>>> Cheers!
>>> Thiago
>>>
>>> _______________________________________________
>>> Mailing list:
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>>> Post to     : openstack at lists.openstack.org
>>> Unsubscribe :
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>>>
>>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20150415/5db03785/attachment.html>


More information about the Openstack mailing list