Bug 1463790 - [Docs][NFV] Clarify the use of bridges vs bonded interfaces in NFV Configuration Guide
Summary: [Docs][NFV] Clarify the use of bridges vs bonded interfaces in NFV Configurat...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: documentation
Version: 11.0 (Ocata)
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Sandra McCann
QA Contact: RHOS Documentation Team
URL:
Whiteboard:
Depends On:
Blocks: 1463778
TreeView+ depends on / blocked
 
Reported: 2017-06-21 18:44 UTC by Sandra McCann
Modified: 2020-07-16 09:54 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-07-18 15:04:50 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

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


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