Bug 1334745
Summary: | [RFE] Add hook to handle FCOE storages | |||
---|---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Yaniv Lavi <ylavi> | |
Component: | RFEs | Assignee: | Pavel Zhukov <pzhukov> | |
Status: | CLOSED ERRATA | QA Contact: | Elad <ebenahar> | |
Severity: | medium | Docs Contact: | ||
Priority: | urgent | |||
Version: | 3.5.1 | CC: | amureini, cwu, danken, ebenahar, fdeutsch, frolland, gklein, lpeer, lsurette, melewis, mkalinin, pzhukov, rbalakri, sherold, srevivo, trichard, ycui, ykaul, ylavi | |
Target Milestone: | ovirt-4.0.0-beta | Keywords: | FutureFeature | |
Target Release: | 4.0.0 | Flags: | acanan:
testing_plan_complete-
|
|
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
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].
|
Story Points: | --- | |
Clone Of: | RHEV_FCOE | |||
: | 1334748 (view as bug list) | Environment: | ||
Last Closed: | 2016-08-23 20:38:41 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: | 1237212, 1266157, 1319873, 1334748, 1338795 | |||
Bug Blocks: | 1239122, 1317452, 1386533 |
Comment 2
Elad
2016-07-10 14:13:15 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 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. |