Description of problem: IMO it is too much human effort to follow EL* development and to extract parts from official EL* storage mgmt guides and too keep them up-to-date in specific related products which could work with storage service provided on such EL* machines. ie. IMO it is enough to keep a "link" to offical docs related to iSCSI as it is in 2nd paragraph under '7.5.2. Adding iSCSI Storage' and it seems to me better to drop whole '7.5.1' section about setting up iSCSI on EL6 only. Why? Either we should have 'Preparing iSCSI Storage' sections for both major versions (EL6, EL7) included or just drop the steps themselves and refer to official EL* docs. I would go for the latter. (Those little notes in '7.5.1' cannot be considered exhausted steps for iSCSI storage preparation and in some cases just following the steps [ie. changing already existing iSCSI target] can be harmful to already established initiators' connections.) Version-Release number of selected component (if applicable): https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Virtualization/3.6/html/Administration_Guide/sect-Preparing_and_Adding_Block_Storage.html How reproducible: 100% Steps to Reproduce: 1. see if 7.5.1 talks only about EL6 2. 3. Actual results: 7.5.1 talks only about EL6 and the steps only assume clean iscsi target Expected results: do not document details about iscsi storage preparation in RHEVM docs, just refer to official EL* storage mgmt guides Additional info:
*** Bug 1311799 has been marked as a duplicate of this bug. ***
RHEV doesn't have any special support matrix here - if the underlying RHEL(7) supports connecting to server X, so will RHEL, regardless of whether X is targetcli from RHEL 7, tgtd from RHEL 6, an EMC-VNX machine or whathaveyou. Chapter 7.5.1 isn't really part of RHEV - it's about one [not particularly useful] configuring the iSCSI **server** RHEV can connect to. I tend to agree with Jiri here. This chapter can be reduced to a link in the spirit of "RHEV can connect to any iSCSI server RHEL supports. For example, you can use a different RHEL server as a storage server, see guide X, section Y for details".
The updated content for this bug is now available: 3.6 https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Virtualization/3.6/html/Administration_Guide/chap-Storage.html 4.0 https://access.redhat.com/documentation/en/red-hat-virtualization/4.0/single/administration-guide/#chap-Storage