RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1258793 - [DOC]-SBRvirt request - Storage pool documentation needs to be re-tweaked
Summary: [DOC]-SBRvirt request - Storage pool documentation needs to be re-tweaked
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: doc-Virtualization_Deployment_and_Administration_Guide
Version: 7.2
Hardware: Unspecified
OS: Unspecified
medium
unspecified
Target Milestone: rc
: ---
Assignee: Yehuda Zimmerman
QA Contact: Jaroslav Suchanek
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-09-01 10:09 UTC by Laura Novich
Modified: 2019-03-06 02:06 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-09-04 12:45:36 UTC
Target Upstream Version:
Embargoed:
yzimmerm: needinfo+

Attachments (Terms of Use)

Description Laura Novich 2015-09-01 10:09:06 UTC 
Document URL: 
https://documentation-devel.engineering.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Virtualization_Deployment_and_Administration_Guide/chap-Storage_pools.html
Section Number and Name: Storage Pools chapter 13

Describe the issue:  
 Storage pool documentation needs to be re-tweaked - need to address the concept of a storage pool. Storage pools are not required - we have nothing to say whether you do or don’t need a storage pool
It is possible to create image from the defaults. Placing image files anywhere as an option is also not stated - need to tweak SELinux for this.
Fix includes: 
*Rewriting the ENTIRE storage chapter
*Put in section that dictates which hardware solution yields which storage pool
*Clearer understanding for what a storage pool volume and solution are and how and when to use them
*CLEARLY state that a storage pool is not required
*Also important is to Explain difference between the types of storage pool
*How to choose the storage pool that matches what you want to do, why to use one type or another.
*There are many ways to use storage. ie. if they have Fibre Channel -- put on LUNs or put on LVM
Customers should/usually understand what base system they have - will know if they have:
NFS
iSCSI
FC
Based on this they choose which storage pool type to configure. However, they don’t know which instructions apply to them.

Suggestions for improvement: 

Additional information:
Comment 6 John Ferlan 2018-03-08 13:31:05 UTC 
Unclear why there's 2 bugs tracking exactly the same thing (bz 1470018 points at the same link above). If one or the other is preferred for updates let me know; otherwise, I'll assume the latter is preferred. I'll work section by section - never quite sure how long it'll take to finish, but I am working on it now and will provide some feedback shortly.
Note You need to log in before you can comment on or make changes to this bug.