[Openstack] Multiple Physical Interfaces for Intra-Cloud Comunication - VXLAN
Erik McCormick
emccormick at cirrusseven.com
Fri Apr 10 02:32:31 UTC 2015
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/20150409/c6fd6fce/attachment.html>
More information about the Openstack
mailing list