Bug 1567055 - [RFE] Add planning section to CONFIGURING RED HAT VIRTUALIZATION WITH RED HAT GLUSTER STORAGE
Summary: [RFE] Add planning section to CONFIGURING RED HAT VIRTUALIZATION WITH RED HAT...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: doc-Configuring_Red_Hat_Enterprise_Virtualization_with_RHGS
Version: rhgs-3.3
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: storage-doc
QA Contact: SATHEESARAN
URL:
Whiteboard:
Depends On:
Blocks: 1724792
TreeView+ depends on / blocked
 
Reported: 2018-04-13 11:07 UTC by Thom Carlin
Modified: 2023-11-25 05:04 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-11-24 02:55:58 UTC
Embargoed:


Attachments (Terms of Use)

Description Thom Carlin 2018-04-13 11:07:54 UTC
Description of enhancement:

https://access.redhat.com/documentation/en-us/red_hat_gluster_storage/3.3/html-single/configuring_red_hat_virtualization_with_red_hat_gluster_storage/#chap-Support_Requirements

Add Planning Section to help end-users understand the current integration and ho w it affects their Architecture and Implementation decisions.

Version-Release number of selected component (if applicable):

3.3

Additional info:

For example, they need to reserve space as raw devices on their storage servers.  This would need to be done during the initial OS install or would require additional storage be made available (since XFS filesystems cannot be shrunk).

Another example would be NFS-Ganesha and Samba (and Samba AD integration) are not used as part of these integration.

The intent is that many large organizations often have multiple independent groups responsible for portions of these architectures.  It would help them if we guided them through a series of questions to fill out a table summarizing the design decisions.  This way, the later questions in the related documents could be answered based on the answers given.


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