Bug 1351772 - Outdated storage domain limitations in the Technical Reference
Summary: Outdated storage domain limitations in the Technical Reference
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: Documentation
Version: 4.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ovirt-4.0.1
: ---
Assignee: Byron Gravenorst
QA Contact: Tahlia Richardson
URL:
Whiteboard:
Depends On:
Blocks: 1343898
TreeView+ depends on / blocked
 
Reported: 2016-06-30 19:20 UTC by Allon Mureinik
Modified: 2016-08-15 23:48 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-08-15 23:48:05 UTC
oVirt Team: Docs
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Allon Mureinik 2016-06-30 19:20:18 UTC
Description of problem:
Chapter 10.4 (Storage Domain Limitations) lists several limitations that are no longer true, and should be amended:

"Legacy FCP or iSCSI export storage domains from Red Hat Enterprise Virtualization 2.2 environments can be attached to data centers in Red Hat Enterprise Virtualization 3.0."
While this was true for RHEV 3.0, the support for these legacy domains was removed back in RHEV 3.1. This sentence should either be updated to something like "Legacy FCP or iSCSI export storage domains from Red Hat Enterprise Virtualization 2.2 environments are no longer supported", or just removed completely - up to the documentation stakeholders to decide what to do with this sentence exactly.

"New ISO and export storage domains in Red Hat Enterprise Virtualization 3.6 must be provided by NFS."
This sentence is not accurate. ISO and export domains may be provided by any file-based storage (NFS, Posix or GlusterFS).

Comment 1 Lucy Bopf 2016-07-13 06:22:56 UTC
Assigning to Byron for review.

Comment 3 Tahlia Richardson 2016-08-03 01:27:25 UTC
Merged. Updated revision history for 3.6.


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