Bug 1463790 - [Docs][NFV] Clarify the use of bridges vs bonded interfaces in NFV Configuration Guide
[Docs][NFV] Clarify the use of bridges vs bonded interfaces in NFV Configurat...
Status: CLOSED CURRENTRELEASE
Product: Red Hat OpenStack
Classification: Red Hat
Component: documentation (Show other bugs)
11.0 (Ocata)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Sandra McCann
RHOS Documentation Team
: Triaged
Depends On:
Blocks: 1463778
  Show dependency treegraph
 
Reported: 2017-06-21 14:44 EDT by Sandra McCann
Modified: 2017-07-18 11:04 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-07-18 11:04:50 EDT
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 Sandra McCann 2017-06-21 14:44:22 EDT
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

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