Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1370030 - [Docs][Admin][RFE] Document FCoE hook
[Docs][Admin][RFE] Document FCoE hook
Status: CLOSED CURRENTRELEASE
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: Documentation (Show other bugs)
4.0.0
Unspecified Unspecified
unspecified Severity unspecified
: ovirt-3.6.9
: ---
Assigned To: Tahlia Richardson
Byron Gravenorst
: FutureFeature
Depends On: 1334748
Blocks:
  Show dependency treegraph
 
Reported: 2016-08-25 02:22 EDT by Lucy Bopf
Modified: 2016-10-11 02:07 EDT (History)
9 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2016-10-11 02:07:34 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: Docs
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Lucy Bopf 2016-08-25 02:22:23 EDT
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.
Comment 1 Lucy Bopf 2016-08-30 21:01:00 EDT
Assigning to Tahlia for review.
Comment 4 Dan Kenigsberg 2016-09-26 09:30:54 EDT
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?
Comment 5 Elad 2016-09-27 09:59:08 EDT
(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

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