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

Bug 1609651

Summary: [Docs][Planning] Self-hosted engine networking recommendations
Product: Red Hat Enterprise Virtualization Manager Reporter: Tahlia Richardson <trichard>
Component: DocumentationAssignee: Donna DaCosta <ddacosta>
Status: CLOSED CURRENTRELEASE QA Contact: rhev-docs <rhev-docs>
Severity: medium Docs Contact:
Priority: high    
Version: 4.2.5CC: amusil, ctomasko, danken, dholler, emarcus, germano, gveitmic, lsurette, mperina, pelauter, srevivo
Target Milestone: ovirt-4.4.6Keywords: Documentation, NoDocsQEReview, Task
Target Release: 4.3.0   
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: 2021-06-02 15:15:22 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Network RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1497925    
Bug Blocks:    

Description Tahlia Richardson 2018-07-30 06:16:20 UTC
From https://bugzilla.redhat.com/show_bug.cgi?id=1497925#c5

"Forth to our latest conversation with Yaniv and as we agreed, I'm providing my recommendations:
IMHO

We should recommend to have stable network infrastructure and storage environment, properly designed by network professionals, with properly configured DNS and DHCP records, prior to any SHE deployments.

For HA to work properly, LAG/Bond/Ether-channel should be used for layer two (L2) link failures and network congestions, for redundancy customers should use pair of NICs on hosts, such design will eliminate single NIC failure on host's level.

Storage connectivity should use either multiple dedicated NICs to work in separate network as multi-path or at least to operate in multiple storage-dedicated VLANs over shared or dedicated Bond/LAG/Ether-channel, if Bond will be shared with other network traffic, then proper QOS is required for storage and other network traffic. FC should have either two HBAs or at least one dual HBA for L2 link fail over protection.

Ether-channel/Bond/LAG is meant for link failure protection at L2 level only and for providing greater throughput, while single physical link is insufficient and aggregation of multiple physical links in to one logical link is required.

On storage side we should also recommend to have either several Ethernet connections or single/multiple ether-channels, for redundancy and greater throughput."

Comment 2 Sandro Bonazzola 2019-01-28 09:41:42 UTC
This bug has not been marked as blocker for oVirt 4.3.0.
Since we are releasing it tomorrow, January 29th, this bug has been re-targeted to 4.3.1.

Comment 8 Ales Musil 2021-05-11 06:32:09 UTC
Looks good, thanks

Comment 9 Germano Veit Michel 2021-05-15 01:42:03 UTC
Looks good with the 2 items we discussed by email.