From 4.1, RHV can consume FCoE block storage. An 'fcoe' hook is available on hosts (confirm whether it is available by default or must be installed). This hook and its functionality must be documented. 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 enable FCoE on a NIC, attach a network to it, and set the "fcoe" network custom property to enable=yes[,dcb=yes][,auto_vlan=yes] in the Administration Portal.
Assigning to Tahlia for review.
It is not: the user should run engine-config -s UserDefinedNetworkCustomProperties='fcoe=^((enable|dcb|auto_vlan)=(yes|no),?)*$' to allow the right values. I suggest users to start with `engine-config -g UserDefinedNetworkCustomProperties` which checks whether there's a previously defined user custom property, so they don't blindly override it with the new value. Also, we should document that on RHEL-H hosts, users are responsible to install vdsm-hook-fcoe on each host, as it is not deployed by default. Elad, have I missed something?
(In reply to Dan Kenigsberg from comment #4) > Elad, have I missed something? No, neither the documentation. The described procedure is correct for both RHVM FCoE configuration and fcoe custom property in networks setup
Now published at https://access.redhat.com/documentation/en/red-hat-virtualization/4.0/single/administration-guide/#How_to_Set_Up_RHVM_to_Use_FCoE