Re: [Nfs-ganesha-devel] NFS-Ganesha HA

2017-07-05 Thread Daniel Gryniewicz
There are currently no changes in the Ceph side. Daniel On 07/05/2017 09:56 AM, Supriti Singh wrote: So at the moment the direction is more to use pacemaker/corosync and each FSAL its own way to handle the client state in shared storage. Looking at storhaug, it seems like the plan is to use the

Re: [Nfs-ganesha-devel] NFS-Ganesha HA

2017-07-05 Thread Supriti Singh
So at the moment the direction is more to use pacemaker/corosync and each FSAL its own way to handle the client state in shared storage. Looking at storhaug, it seems like the plan is to use the same resource agent for both gluster and ceph (cephfs and rgw) backend. We need to point to different

Re: [Nfs-ganesha-devel] NFS-Ganesha HA

2017-07-05 Thread Frank Filz
> CMAL is dead. There wasn't enough interest in it, and the majority of it's > features are provided by whatever clustered filesystem is backing Ganesha. CMAL is dead, long live CMAL! What came out of the CMAL effort was a couple things: 1. The dBus interface we have for clustering (takeip, rel

Re: [Nfs-ganesha-devel] NFS-Ganesha HA

2017-07-05 Thread Daniel Gryniewicz
Hi, Supriti. CMAL is dead. There wasn't enough interest in it, and the majority of it's features are provided by whatever clustered filesystem is backing Ganesha. There are plans underway to extend the FSAL APIs to support more features required by HA. It's unlikely that we'll ever be able

Re: [Nfs-ganesha-devel] NFS-Ganesha HA

2017-07-05 Thread Supriti Singh
Hi Mark, I have looked into storhaug. I was trying to use the resource agents, "ganesha" and "ganesha_trigger". But just for active-passive configuration, I used systemd resource agent for now. Thanks, Supriti -- Supriti Singh��SUSE Linux GmbH, GF: Felix Imend��rffer, Jane Smithard, Gra