Description of problem: os-net-config only supports OVS bonds and VLAN interfaces. This introduces extra complexity (one or more extra bridges), and a packet-processing path that is potentially less performant. Version-Release number of selected component (if applicable): OSP 7 GA How reproducible: 100% Steps to Reproduce: 1. Deploy OSP 7 2. 3. Actual results: All overcloud instances are using OVS for the bonds and VLAN interfaces in addition to the bridges. Expected results: We used to use Linux bonds and VLAN interfaces in OSP 5 & 6. A lot of people had an expectation that we would be continuing to use, or at least support, Linux bonds and bridges in OSP 7. The networking in OSP 7 is harder for people to grasp since they are used to Linux bonds and VLAN interfaces. OVS has a reputation for delivering less performance in bridging than Linux. It is likely that there is at least some performance impact when using OVS for bonds and VLAN interfaces as well. Additional info: We don't actually know if there is a performance impact from using OVS bonds and VLAN interfaces, but it's something that we should test. If there is a performance gap, it may be good to switch the default in an async release. In addition, some advanced networking architectures that use 3rd-party plugins require Linux bridge support. We may have issues integrating with SDN or NFV solutions if we only support OVS bonds and VLANs (speculation, actual impact unknown). Linux bonds support additional modes for bonding, so there may be a preference to use Linux bonds.
Nir, can you provide some feedback on whether this is something the field is going to need implemented, and an idea of how important it is that we get this working?
Is this going to be supported in 8.0 Director or we could expect in 7.0 as well.
(In reply to Salman Khan from comment #10) > Is this going to be supported in 8.0 Director or we could expect in 7.0 as > well. These features will be in the final point release of OSP 7/OSP-Director 7.2. The change is in beta testing now.
*** Bug 1276708 has been marked as a duplicate of this bug. ***
Couple of questions: 1. does this affect non - OVS bonding, i.e. kernel? 2. How does this affect ha-proxy and pacemaker?
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2015:2651
Created attachment 1146051 [details] original controller.yaml using ovs bonds
Created attachment 1146052 [details] controller.yaml with linux bonds example
Created attachment 1146053 [details] compute.yaml with linux bonds example
Created attachment 1146054 [details] ceph-storage.yaml with linux bonds example
Added examples of linux bond templates