Bug 1310612 - [Docs] [RHEV integration] Replica 3 is not recommended, but a requirement
Summary: [Docs] [RHEV integration] Replica 3 is not recommended, but a requirement
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: doc-Configuring_Red_Hat_Enterprise_Virtualization_with_RHGS
Version: rhgs-3.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: RHGS 3.1.3
Assignee: Laura Bailey
QA Contact: SATHEESARAN
URL:
Whiteboard:
Depends On:
Blocks: 1311847
TreeView+ depends on / blocked
 
Reported: 2016-02-22 11:01 UTC by Yaniv Kaul
Modified: 2016-06-29 14:22 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-06-29 14:22:08 UTC
Target Upstream Version:


Attachments (Terms of Use)
optimizing the volume tab (38.23 KB, image/png)
2016-05-12 07:19 UTC, SATHEESARAN
no flags Details

Description Yaniv Kaul 2016-02-22 11:01:06 UTC
Description of problem:
https://access.redhat.com/documentation/en-US/Red_Hat_Storage/3.1/html/Configuring_Red_Hat_Enterprise_Virtualization_with_Red_Hat_Gluster_Storage/chap-Recommended_Best_Practices_and_Troubleshooting.html recommends having replica 3. In fact, we must have replica 3 (I think this is enforced from 3.6).

Comment 2 Laura Bailey 2016-05-10 00:30:44 UTC
Sas, can you confirm that replica 3 is a requirement rather than a recommendation when using RHGS to work with RHEV 3.6 and onward?

Comment 3 SATHEESARAN 2016-05-12 07:18:04 UTC
(In reply to Laura Bailey from comment #2)
> Sas, can you confirm that replica 3 is a requirement rather than a
> recommendation when using RHGS to work with RHEV 3.6 and onward?

Laura,

Still I see that replica 3 volume only as a recommendation.

I tried setting up a distributed gluster volume for the backend of RHEV data domain with RHEV 3.6.5, and that works too.

Only when optimising the volume for virt store it throws a suggestion to use replica 3 volume.

As far as I can observe, the resstriction to use replica 3 volume is still not enforced

Attaching the screenshot too

Comment 4 SATHEESARAN 2016-05-12 07:19:17 UTC
Created attachment 1156486 [details]
optimizing the volume tab

optimizing the volume for virt store suggests using replica 3 volume and doesn't enforces it

Comment 5 Laura Bailey 2016-05-12 12:17:15 UTC
Yaniv, it looks like this is still a recommendation. Can you confirm so that we can close this NOTABUG, or provide more information?

Comment 6 Yaniv Kaul 2016-05-12 20:37:28 UTC
It should be a requirement,  period. The fact we are enforcing it in the product is a bug by itself. 
Y.

Comment 7 Laura Bailey 2016-05-12 23:52:11 UTC
Whether it should be a requirement is another question altogether, I'm afraid. I've raised the question with product management; you should be on CC, Yaniv. :)

For now, closing this NOTABUG.

Comment 8 Laura Bailey 2016-05-13 00:44:57 UTC
Re-opening after confirmation from Sayan that replica 3 is required for support.

Waiting on further information re. whether RHEV enforces this.

Comment 10 Laura Bailey 2016-05-20 02:10:21 UTC
Yaniv, can you confirm that the changes in comment 9 solve the problem?

Comment 11 Yaniv Kaul 2016-05-20 17:45:28 UTC
Sahina, anyone from the Gluster team can take a look at this?

Comment 12 Sahina Bose 2016-05-23 12:48:31 UTC
Procedure 3.1 Please change note " Red Hat Gluster Storage recommends that you use Replicate or Distributed Replicate volume type for hosting virtual machine disk images. " - to indicate replica 3 requirements

Procedure 4.1 Note about quorum - sas, can you recheck this section

Comment 13 SATHEESARAN 2016-05-23 16:37:18 UTC
(In reply to Sahina Bose from comment #12)
> Procedure 3.1 Please change note " Red Hat Gluster Storage recommends that
> you use Replicate or Distributed Replicate volume type for hosting virtual
> machine disk images. " - to indicate replica 3 requirements
> 
> Procedure 4.1 Note about quorum - sas, can you recheck this section

The section - Section 4.1 - looks valid

Comment 16 SATHEESARAN 2016-05-24 16:38:33 UTC
The doc content looks good


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