Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1463790

Summary: [Docs][NFV] Clarify the use of bridges vs bonded interfaces in NFV Configuration Guide
Product: Red Hat OpenStack Reporter: Sandra McCann <samccann>
Component: documentationAssignee: Sandra McCann <samccann>
Status: CLOSED CURRENTRELEASE QA Contact: RHOS Documentation Team <rhos-docs>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 11.0 (Ocata)CC: srevivo
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-07-18 15:04:50 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1463778    

Description Sandra McCann 2017-06-21 18:44:22 UTC
Description of problem:

Currently in RHOSP11 NFV Configuration Guide, there is little guidance on why some interfaces are bonded and some go to bridges:


The DPDK documentation states that in compute./yaml all node bridges should be type "ovs_user_bridge" and that "ovs_bridge" can no longer be used in the  compute.yaml file when deploying DPDK. However in /usr/share/openstack-tripleo-heat-templates/network/config/bond-with-vlans/compute-dpdk.yaml we see both types of bridges "ovs_bridge" and "ovs_user_bridge" in the same file. 

In the compute.yaml examples, non dpdk enabled user bridges are no longer being configured as bridges at all, rather they have been migrated to linux_bonds with tagged interfaces, no bridging required. However, the migration or use of linux_bonds is not mentioned in the doc outside of the configuration examples, adding further confusion