Open Stack

Yes and, I prefer mode=4 MLAG bond/team.  On Cent we had to use
xmit_hash_policy layer2+3 because layer3+4 caused kernel panics @ Cent
7.1.1503

Cheers
Wade


On Fri, Dec 18, 2015 at 12:17 PM Serguei Bezverkhi (sbezverk) <
sbezverk at cisco.com> wrote:

> Hello team,
>
>
>
> I would appreciate if you could share approach you use for OpenStack node
> redundancy from network failure perspective. Example in case of a failure
> of an upstream switch and if a node does not have redundant link to a
> second upstream switch, it gets isolated. I understand that OpenStack will
> deal with this situation by removing this node, but in my case there is a
> strict requirement to be able to prevent a single switch failure.
>
>
>
> Here is the solution I came up with, it is nothing new but appreciate your
> critic/comments/suggestions.
>
>
>
> Redundant OpenStack is connected to two upstream switches, interfaces are
> teamed into group and bound to respective OpenStack bridges. So br-int
> would have physical link interface team0 and not eth0 or eth1 connected. In
> this case if one of the upstream links fails, the connectivity would be
> preserved.
>
>
>
> Thank you
>
>
>
> Serguei
>
>
>
>
>
>
>
>
> _______________________________________________
> OpenStack-operators mailing list
> OpenStack-operators at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20151219/4c774e1c/attachment.html>