Bug 1252592 - [Director] Document the OVS bonding modes in the official documentation
[Director] Document the OVS bonding modes in the official documentation
Status: CLOSED CURRENTRELEASE
Product: Red Hat OpenStack
Classification: Red Hat
Component: documentation (Show other bugs)
7.0 (Kilo)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: 7.0 (Kilo)
Assigned To: Martin Lopes
Dan Macpherson
: Documentation, ZStream
Depends On:
Blocks: 1191185 1243520 1277361
  Show dependency treegraph
 
Reported: 2015-08-11 16:21 EDT by Dan Sneddon
Modified: 2016-01-11 05:11 EST (History)
7 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2016-01-11 05:11:34 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Dan Sneddon 2015-08-11 16:21:59 EDT
Description of problem:
The OVS bonding modes are different from the Linux Bonding modes. We should document the OVS bonding modes, how to set them properly, and the fine-tuning knobs that exist for the bonds. The docs should also compare Linux Bond modes to OVS bonding modes.

Version-Release number of selected component (if applicable):
OSP 7 GA


Actual results:
Confusion and chaos

Expected results:
Proper documentation

Additional info:

Bond Mode 1, 2, and 4 are concepts that apply to Linux Bonds only. OVS bonds, on the other hand, have the following modes:

active-backup (only one link is used at a time)
balance-slb (MAC address-based load balancing, LACP optional)
balance-tcp (layer 2-4 intelligent load balancing, LACP required)

The active-backup mode is equivalent to Linux mode 1 bonds, and does not require switch support or configuration.

The balance-slb mode is compatible with "static" bonds, which means that the switch is always configured to send traffic down all bond members. This is roughly equivalent to Linux Bonding in mode 2. LACP support on the switch is not required, however one does not get the protection against unidirectional link failure or link error detection that LACP provides.

The balance-tcp mode requires LACP, but provides robust link failure detection, additional link data at the switch level, and has better load balancing characteristics. This is roughly equivalent to Linux mode 4 bonds. LACP support and configuration is required on the switch.

The default bonding options will configure the host to send LACP packets to the switch. If an LACP link cannot be established (for instance if the switch is not configured for LACP), then the link will fall back to active-backup mode. This makes the default options safe to deploy on switches that aren't yet configured for LACP bonds. If LACP is later configured on the switches, then the bonds will automatically switch from active-backup to active-active LACP bonds.
Comment 3 Deon Ballard 2015-08-11 18:39:08 EDT
Reassigning to the doc writer.
Comment 9 Andrew Dahms 2016-01-11 05:11:34 EST
This content is live on the Customer Portal.

Closing.

Note You need to log in before you can comment on or make changes to this bug.