Bug 1071487 - Always default to cluster.server-quorum-type server?
Summary: Always default to cluster.server-quorum-type server?
Keywords:
Status: CLOSED EOL
Alias: None
Product: GlusterFS
Classification: Community
Component: glusterd
Version: pre-release
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: bugs@gluster.org
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-02-28 22:38 UTC by josh@wrale.com
Modified: 2015-10-22 15:40 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-10-22 15:40:20 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description josh@wrale.com 2014-02-28 22:38:27 UTC
I'm using 3.5b3 and I'd like to set a policy for all volumes created in the future to by default enable server quorum with a default value of >50%.  Is this already implemented anywhere?  I know I can do so at the time of each volume creation or post-volume creation.  Can I pre-emptively say I always want quorum?

Today, I'm trying to set up an oVirt 3.4.0rc H/A w/hosted engine + GlusterFS 3.5b3 + Fedora 19 + btrfs (boot and bricks) cluster (converged hardware).  And that is why I'm asking. :)

Also, any help with this Gluster + oVirt issue would be much appreciated: 

http://www.mail-archive.com/users@ovirt.org/msg15678.html

Thanks,
Joshua

Comment 1 Kaleb KEITHLEY 2015-10-22 15:40:20 UTC
pre-release version is ambiguous and about to be removed as a choice.

If you believe this is still a bug, please change the status back to NEW and choose the appropriate, applicable version for it.


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