Bug 1045655

Summary: Network topology figures lack consistency and precision
Product: Red Hat Enterprise Virtualization Manager Reporter: Dan Kenigsberg <danken>
Component: DocumentationAssignee: Jodi Biddle <jbiddle>
Status: CLOSED WONTFIX QA Contact: ecs-bugs
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 3.5.0CC: acathrow, sfolkwil, yeylon
Target Milestone: ---   
Target Release: 3.4.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Instance Name: Not Defined Build: CSProcessor Builder Version 1.8 Build Name: 9026, Technical Reference Guide-3.2-null Build Date: 13-05-2013 13:48:47
Last Closed: 2014-07-16 01:09:23 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:

Description Dan Kenigsberg 2013-12-20 23:46:31 UTC 
Title: VLAN Configuration

Describe the issue:
The host networking devices in Figure 4.4 are wrong. The "VLAN A" device should stand between the NIC and the Bridge.

Suggestions for improvement:
The NIC block should sit at the border of a host container, as in Figure 4.6.

Additional information:

Glitches and inconsistency appear in other figures, too:
2. the bond device is better represented in the same way, both in Figure 4.5. Bridge, Bond, and NIC configuration and in Figure 4.7. Multiple Bridge, Multiple VLAN, and Multiple NIC with Bond connection.

3. "VNIC A" and "VNIC B" blocks should be dropped from Figure 4.7

4. It would be nice if Figure 4.7 shows a guest that's connect to two bridges, just to stress that it's possible.
Comment 1 Dan Kenigsberg 2014-05-21 13:36:04 UTC 
https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Virtualization/3.0/html/Technical_Reference_Guide/sect-Technical_Reference_Guide-Network_Architecture-Networking_in_Hosts_and_Virtual_Machines.html
Comment 2 Jodi Biddle 2014-07-16 01:09:23 UTC 
Unfortunately we don't have the resources to update the 3.0 documentation - we can only backport by one previous release, unless there's a critical customer need. Closing as wontfix.