Bug 1093217 - [RFE] Gluster module (purpleidea) to support HA installations using Pacemaker
Summary: [RFE] Gluster module (purpleidea) to support HA installations using Pacemaker
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: GlusterFS
Classification: Community
Component: puppet-gluster
Version: mainline
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
Assignee: bugs@gluster.org
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-05-01 01:28 UTC by Gilles Dubreuil
Modified: 2018-11-19 03:06 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-11-19 03:06:51 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:

Attachments (Terms of Use)

Description Gilles Dubreuil 2014-05-01 01:28:36 UTC 
To be able to deploy Gluster cluster (HA) using VIP through Pacemaker instead of keepalived.

The main justifications are, so far:

1. Pacemaker is fully supported on RHEL6+
2. Already used by Openstack Foreman installer
Comment 1 Gilles Dubreuil 2014-06-23 06:44:43 UTC 
Hi James,

Could you please provide some information about this one?

Thanks,
Gilles
Comment 2 James (purpleidea) 2014-06-23 19:23:36 UTC 
(In reply to Gilles Dubreuil from comment #1)
> Hi James,
> 
> Could you please provide some information about this one?
> 
> Thanks,
> Gilles

I'm busy working on other projects at the moment, so this isn't a priority right now. Sorry,

Cheers,
James
Comment 3 James (purpleidea) 2014-09-30 16:28:19 UTC 
Thanks to ndevos for volunteering to fix this bug ;)
Comment 4 Niels de Vos 2014-09-30 16:44:33 UTC 
(In reply to James (purpleidea) from comment #3)
> Thanks to ndevos for volunteering to fix this bug ;)

I think this is actually more something Kaleb is (or should be) interested in.
Comment 5 Niels de Vos 2014-11-27 14:45:20 UTC 
Feature requests make most sense against the 'mainline' release, there is no ETA for an implementation and requests might get forgotten when filed against a particular version.
Comment 6 Kaleb KEITHLEY 2014-12-01 13:09:30 UTC 
We already have a glusterfs-resource-agents subpackage which has a (pacemaker) glusterd heartbeat resource.

Although it looks like its resource file is installed in /usr/lib/ocf/resource.d/glusterfs/glusterd instead of /usr/lib/resource.d/heartbeat, where the heartbeat resources are usually installed.

What are we really asking for here?
Comment 7 James (purpleidea) 2014-12-01 13:15:23 UTC 
(In reply to Kaleb KEITHLEY from comment #6)
> We already have a glusterfs-resource-agents subpackage which has a
> (pacemaker) glusterd heartbeat resource.
> 
> Although it looks like its resource file is installed in
> /usr/lib/ocf/resource.d/glusterfs/glusterd instead of
> /usr/lib/resource.d/heartbeat, where the heartbeat resources are usually
> installed.
> 
> What are we really asking for here?

Actually his is a bit different...

I am using this technique:

https://ttboj.wordpress.com/2012/08/23/how-to-avoid-cluster-race-conditions-or-how-to-implement-a-distributed-lock-manager-in-puppet/

in my puppet module. It uses keepalived instead of pacemaker for the VIP it needs. This feature requests porting puppet-gluster to also use pacemaker.

Actually if GlusterFS or anything else provided an HA identifier, it could be ported to use that instead...

Does this answer the question?

Cheers!
Comment 8 Vijay Bellur 2018-11-19 03:06:51 UTC 
We are not actively maintaining puppet-gluster. Hence closing this enhancement request.
Note You need to log in before you can comment on or make changes to this bug.