[Pacemaker] setting up NFS resources on systemd based Linux distributions

Dejan Muhamedagic dejanmm at fastmail.fm
Mon Oct 22 16:15:22 UTC 2012


Hi,

On Tue, Oct 16, 2012 at 07:59:26AM -0700, Lonni J Friedman wrote:
> On Mon, Oct 15, 2012 at 8:51 PM, Andrew Beekhof <andrew at beekhof.net> wrote:
> > On Tue, Oct 16, 2012 at 2:50 PM, Andrew Beekhof <andrew at beekhof.net> wrote:
> >> On Tue, Oct 16, 2012 at 9:24 AM, Lonni J Friedman <netllama at gmail.com> wrote:
> >>> On Thu, Sep 27, 2012 at 6:24 AM, David Vossel <dvossel at redhat.com> wrote:
> >>>> ----- Original Message -----
> >>>>> From: "Lonni J Friedman" <netllama at gmail.com>
> >>>>> To: pacemaker at oss.clusterlabs.org
> >>>>> Sent: Wednesday, September 26, 2012 9:44:21 PM
> >>>>> Subject: [Pacemaker] setting up NFS resources on systemd based Linux  distributions
> >>>>>
> >>>>> I'm trying to setup NFS resources on Fedora16, and its not working.
> >>>>> After googling, I stumbled across the following discussion from about
> >>>>> 8 months ago:
> >>>>> http://www.gossamer-threads.com/lists/linuxha/pacemaker/77404
> >>>>>
> >>>>> Has anything changed since then, or is systemd still not supported?
> >>>>
> >>>> Yes, systemd is now supported in the latest 1.1.8 release that came out a few days ago.  Use 'systemd' or 'service' as the resource class when defining the resource in the configuration and everything should just work.
> >>>
> >>> I finally got around to upgrading to pacemaker-1.1.8-2.fc16.x86_64
> >>> using a rebuilt
> >>> http://clusterlabs.org/rpm-next/fedora-17/src/pacemaker-1.1.8-2.fc17.src.rpm
> >>> .
> >>>
> >>> Unfortunately, this resource class is either not working, or I'm
> >>> misunderstanding how it needs to be specified.  I tried adding the
> >>> following:
> >>> primitive FS0_NFS systemd:nfs-server.service op monitor interval="10s"
> >>
> >> just "systemd:nfs-server" no ".service" suffix.
> >
> > Oh, you tried that.  Weird.  Logs?
> >
> > What does crm_resource --list-standards say?
> 
> Looks like it might have been a bug in crmsh-1.2.0.  I just updated to
> 1.2.1 and now it seems to work.  thanks

crmsh-1.2.0 doesn't know about new 1.1.8 LRM ways, so it
couldn't get the data anyway.

Thanks,

Dejan




More information about the Pacemaker mailing list