typedef void (*cpg_totem_confchg_fn_t) (
cpg_handle_t handle,
struct cpg_ring_id ring_id,
uint32_t member_list_entries,
const uint32_t *member_list);
Should "struct cpg_ring_id ring_id" be "struct cpg_ring_id *ring_id"?
Regards,
Dashi Cao
"pacemaker+corosync"! Am I wrong?
Thanks a lot!
Dashi Cao
________________
From: Da Shi Cao <dscao...@hotmail.com>
Sent: Thursday, July 21, 2016 9:31:51 PM
To: Cluster Labs - All topics related to open-source clustering welcomed
Subject: Re: [ClusterLabs] agent oc
management, then the resource will show up and stay well!
Another question is what's the difference of dlm_controld and gfs_controld?
Must they both be present if a cluster gfs file system is mounted?
Thanks a lot!
Dashi Cao
From: Da Shi Cao <dscao...@hotmail.
dlm_controld is very tightly coupled with cman. I have built a cluster purely
with pacemaker+corosync+fence_sanlock. But if agent ocf:pacemaker:controld is
desired, dlm_controld must exist! I can only find it in cman.
Can the command dlm_controld be obtained without bringing in cman?
Best
Hello everybody,
After some try and error, fence_sanlock can be used as a stonith resource in
pacemaker+corosync.
1. Add a "monitor" action, which is exactly the same action as "status".
2. Make "status" action return "false" if a resource belongs to a host is
acquired and owned by another host.
Subject: Re: [ClusterLabs] pacemaker and fence_sanlock
On 05/11/2016 09:14 PM, Da Shi Cao wrote:
> Dear all,
>
> I'm just beginning to use pacemaker+corosync as our HA solution on
> Linux, but I got stuck at the stage of configuring fencing.
>
> Pacemaker 1.1.15, Cor
Dear all,
I'm just beginning to use pacemaker+corosync as our HA solution on Linux, but I
got stuck at the stage of configuring fencing.
Pacemaker 1.1.15, Corosync Cluster Engine, version '2.3.5.46-d245', and
sanlock 3.3.0 (built May 10 2016 05:13:12)
I have the following questions:
1.
