Bug 1334745 - [RFE] Add hook to handle FCOE storages
Summary: [RFE] Add hook to handle FCOE storages
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: RFEs
Version: 3.5.1
Hardware: Unspecified
OS: Unspecified
urgent
medium
Target Milestone: ovirt-4.0.0-beta
: 4.0.0
Assignee: Pavel Zhukov
QA Contact: Elad
URL:
Whiteboard:
Depends On: 1237212 1266157 1319873 1334748 1338795
Blocks: RHEV_FCOE oVirt_FCoE_support RHV_FCoE_support
TreeView+ depends on / blocked
 
Reported: 2016-05-10 12:43 UTC by Yaniv Lavi
Modified: 2020-08-13 08:28 UTC (History)
19 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
With this update, Red Hat Virtualization can now handle FCoE block storage. Depending on the FCoE card on the hosts, special configuration may be needed as described in https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Storage_Administration_Guide/fcoe-config.html To configure FCoE block storage, run engine-config -s UserDefinedNetworkCustomProperties='fcoe=^((enable|dcb|auto_vlan)=(yes|no),?)*$' on the Red Hat Virtualization Manager then restart the Manager. Ensure that the required host has vdsm-hook-fcoe installed then enable FCoE on a NIC. To enable FCoE on a NIC, attach a network then set the FCoE network custom property to enable=yes[,dcb=yes][,auto_vlan=yes].
Clone Of: RHEV_FCOE
: 1334748 (view as bug list)
Environment:
Last Closed: 2016-08-23 20:38:41 UTC
oVirt Team: Network
Target Upstream Version:
acanan: testing_plan_complete-

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 1268183 0 None None None 2016-10-28 16:08:52 UTC
Red Hat Product Errata RHEA-2016:1743 0 normal SHIPPED_LIVE Red Hat Virtualization Manager 4.0 GA Enhancement (ovirt-engine) 2016-09-02 21:54:01 UTC
oVirt gerrit 55029 0 master MERGED hooks: Add fcoe hook 2016-05-16 07:43:27 UTC
oVirt gerrit 57553 0 ovirt-3.6 MERGED hooks: Add fcoe hook 2016-05-23 07:41:04 UTC
oVirt gerrit 58446 0 ovirt-3.6 MERGED hooks: Fix typo in fcoe hook properties 2016-06-01 14:22:59 UTC
oVirt gerrit 58449 0 ovirt-4.0 MERGED hooks: Fix typo in fcoe hook properties 2016-06-01 14:22:53 UTC

Comment 2 Elad 2016-07-10 14:13:15 UTC 
Executed storage tier1 automation and manual negative using the hook.
Note that for FCoE, we used servers with Broadcom BCM57800 Ethernet multi function controllers which require DCB to be disabled (BZ #1353659). 

One more issue, fcoe and lldpad services are not enabled by the hook to start on boot (BZ #1353456).

Verified using:
Red Hat Enterprise Linux Server release 7.2 (Maipo)
Kernel: 3.10.0-327.28.2.el7.x86_64
vdsm-4.18.5.1-1.el7ev.x86_64
vdsm-hook-fcoe-4.18.5.1-1.el7ev.noarch
libvirt-daemon-1.2.17-13.el7_2.5.x86_64
qemu-kvm-rhev-2.3.0-31.el7_2.17.x86_64
selinux-policy-3.13.1-60.el7.noarch
sanlock-3.2.4-2.el7_2.x86_64
python-2.7.5-34.el7.x86_64

rhevm-4.0.2-0.2.rc1.el7ev.noarch


Hardware:
2 hosts connected to a Dell S5000 switch via 2 10G Ethernet ports [1] each (8G configured to be allocated for FC on each switchport)
XtremIO connected to the Dell S5000 switch via 2 8G FC ports.
Dell S5000 switch convert FC communication from XtremIO to FCoE communication to the hosts and vice versa.
6 LUNs exposed to the hosts from the storage server.


[1] 01:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM57800 1/10 Gigabit Ethernet Multi Function (rev 10)
Comment 4 errata-xmlrpc 2016-08-23 20:38:41 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHEA-2016-1743.html
Comment 12 Marina Kalinin 2016-10-28 16:08:53 UTC 
I have this kcs:
https://access.redhat.com/solutions/1268183

But I am looking for official documentation in either 3.6 or 4.0 docs please.
Note You need to log in before you can comment on or make changes to this bug.