Re: [Pacemaker] Pacemaker Digest, Vol 59, Issue 59

2012-10-25 Thread vishal kumar

 Hi Dejan,


I tried with  lrmadmin -M lsb httpd NULL and was able to get the meta-data.

I was able to add a resource from lrmadmin but i cannot see that resource
in crm shell.

Many Thanks
Vishal

Message: 1
 Date: Tue, 23 Oct 2012 13:48:24 +0200
 From: Dejan Muhamedagic deja...@fastmail.fm
 To: The Pacemaker cluster resource manager
 pacemaker@oss.clusterlabs.org
 Subject: Re: [Pacemaker] Pacemaker Digest, Vol 59, Issue 57
 Message-ID: 20121023114823.GA19526@walrus.homenet
 Content-Type: text/plain; charset=us-ascii

 Hi,

 On Tue, Oct 23, 2012 at 10:18:36AM +0530, vishal kumar wrote:
  Hello Florian,
 
  Thanks for the help.
 
  I tried with  crm ra meta sshd lsb but it gave me the same meta-data
 error.
 
  The problem is while trying to add a lsb resource from crm shell, like
  httpd as i am using rhel it gives the following error
  ERROR: lsb:httpd: could not parse meta-data:
  ERROR: lsb:httpd: no such resource agent
 
  the httpd package is installed and i have a httpd file /etc/init.d
  directory. I am unable to add any resource which in /etc/init.d
 directory.

 Do you have cluster-glue installed? And is pacemaker running?
 lrmadmin (part of cluster-glue) gets the meta-data from lrmd. You
 can try it by hand like this:

 lrmadmin -M lsb httpd NULL

 Thanks,

 Dejan

  Many thanks
   Vishal
 
 
  Message: 1
   Date: Mon, 22 Oct 2012 17:53:23 +0530
   From: vishal kumar vishal.kanoj...@gmail.com
   To: pacemaker@oss.clusterlabs.org
   Subject: [Pacemaker] lsb: could not parse meta-data
   Message-ID:
   CANz=
   rdksq4t-sbbf+kbnwob2fgr7xu7g6mrugbpfzasbvnp...@mail.gmail.com
   Content-Type: text/plain; charset=iso-8859-1
  
   Hi
  
   I am trying to configure pacemaker with corosync on RHEL 6.
  
   While trying to add lsb resources i get  could not parse meta-data.
  
   The pacemaker version is 1.1.7 . Below is the error what i get when i
 check
   for metadata in crm shell.
  
   *crm(live)ra# list lsb*
   *abrt-ccpp   abrt-oops   abrtd
 acpid   atd*
   *auditd  autofs  certmonger
cgconfigcgred*
   *corosynccorosync-notifydcpuspeed
crond   cups*
   *haldaemon   haltheartbeat
 httpd   ip6tables*
   *iptablesirqbalance  kdump
 killall ktune*
   *lvm2-lvmetadlvm2-monitor
  matahari-broker
 matahari-host   matahari-network*
   *matahari-rpcmatahari-service
  matahari-sysconfig
matahari-sysconfig-console  mcelogd*
   *mdmonitor   messagebus  netconsole
netfs   network*
   *nfs nfslock ntpd
ntpdate oddjobd*
   *pacemaker   portreserve postfix
 psacct  qpidd*
   *quota_nld   rdisc   restorecond
 rhnsd   rhsmcertd*
   *rngdrpcbind rpcgssd
 rpcidmapd   rpcsvcgssd*
   *rsyslog sandbox saslauthd
 single  smartd*
   *sshdsssdsysstat
 tuned   udev-post*
   *ypbind  *
   *crm(live)ra# meta lsb heartbeat*
   *ERROR: heartbeat:lsb: could not parse meta-data: *
   *crm(live)ra# meta lsb sshd*
   *ERROR: sshd:lsb: could not parse meta-data: *
   *crm(live)ra# meta lsb ntpd*
   *ERROR: ntpd:lsb: could not parse meta-data: *
   *crm(live)ra# meta lsb httpd*
   *ERROR: httpd:lsb: could not parse meta-data*
  
   Please do suggest me where am i going wrong.
   Thanks for the help.
  
   Thanks
   Vishal
   -- next part --
   An HTML attachment was scrubbed...
   URL: 
  
 http://oss.clusterlabs.org/pipermail/pacemaker/attachments/20121022/0ade914c/attachment-0001.html
   
  
   --
  
   Message: 2
   Date: Mon, 22 Oct 2012 14:48:31 +0200
   From: Florian Crouzat gen...@floriancrouzat.net
   To: pacemaker@oss.clusterlabs.org
   Subject: Re: [Pacemaker] lsb: could not parse meta-data
   Message-ID: 5085409f@floriancrouzat.net
   Content-Type: text/plain; charset=ISO-8859-1; format=flowed
  
   Le 22/10/2012 14:23, vishal kumar a ?crit :
Hi
  
Please do suggest me where am i going wrong.
Thanks for the help.
   
  
   See: crm ra help meta
   Then try something like: crm ra meta sshd lsb # parameters order matter
  
   Anyway, you won't learn anything out of meta-datas from a LSB
   initscript, because it's just a script

Re: [Pacemaker] Pacemaker Digest, Vol 59, Issue 57

2012-10-23 Thread vishal kumar
Hello Florian,

Thanks for the help.

I tried with  crm ra meta sshd lsb but it gave me the same meta-data error.

The problem is while trying to add a lsb resource from crm shell, like
httpd as i am using rhel it gives the following error
ERROR: lsb:httpd: could not parse meta-data:
ERROR: lsb:httpd: no such resource agent

the httpd package is installed and i have a httpd file /etc/init.d
directory. I am unable to add any resource which in /etc/init.d directory.


Many thanks
 Vishal


Message: 1
 Date: Mon, 22 Oct 2012 17:53:23 +0530
 From: vishal kumar vishal.kanoj...@gmail.com
 To: pacemaker@oss.clusterlabs.org
 Subject: [Pacemaker] lsb: could not parse meta-data
 Message-ID:
 CANz=
 rdksq4t-sbbf+kbnwob2fgr7xu7g6mrugbpfzasbvnp...@mail.gmail.com
 Content-Type: text/plain; charset=iso-8859-1

 Hi

 I am trying to configure pacemaker with corosync on RHEL 6.

 While trying to add lsb resources i get  could not parse meta-data.

 The pacemaker version is 1.1.7 . Below is the error what i get when i check
 for metadata in crm shell.

 *crm(live)ra# list lsb*
 *abrt-ccpp   abrt-oops   abrtd
   acpid   atd*
 *auditd  autofs  certmonger
  cgconfigcgred*
 *corosynccorosync-notifydcpuspeed
  crond   cups*
 *haldaemon   haltheartbeat
   httpd   ip6tables*
 *iptablesirqbalance  kdump
   killall ktune*
 *lvm2-lvmetadlvm2-monitormatahari-broker
   matahari-host   matahari-network*
 *matahari-rpcmatahari-servicematahari-sysconfig
  matahari-sysconfig-console  mcelogd*
 *mdmonitor   messagebus  netconsole
  netfs   network*
 *nfs nfslock ntpd
  ntpdate oddjobd*
 *pacemaker   portreserve postfix
   psacct  qpidd*
 *quota_nld   rdisc   restorecond
   rhnsd   rhsmcertd*
 *rngdrpcbind rpcgssd
   rpcidmapd   rpcsvcgssd*
 *rsyslog sandbox saslauthd
   single  smartd*
 *sshdsssdsysstat
   tuned   udev-post*
 *ypbind  *
 *crm(live)ra# meta lsb heartbeat*
 *ERROR: heartbeat:lsb: could not parse meta-data: *
 *crm(live)ra# meta lsb sshd*
 *ERROR: sshd:lsb: could not parse meta-data: *
 *crm(live)ra# meta lsb ntpd*
 *ERROR: ntpd:lsb: could not parse meta-data: *
 *crm(live)ra# meta lsb httpd*
 *ERROR: httpd:lsb: could not parse meta-data*

 Please do suggest me where am i going wrong.
 Thanks for the help.

 Thanks
 Vishal
 -- next part --
 An HTML attachment was scrubbed...
 URL: 
 http://oss.clusterlabs.org/pipermail/pacemaker/attachments/20121022/0ade914c/attachment-0001.html
 

 --

 Message: 2
 Date: Mon, 22 Oct 2012 14:48:31 +0200
 From: Florian Crouzat gen...@floriancrouzat.net
 To: pacemaker@oss.clusterlabs.org
 Subject: Re: [Pacemaker] lsb: could not parse meta-data
 Message-ID: 5085409f@floriancrouzat.net
 Content-Type: text/plain; charset=ISO-8859-1; format=flowed

 Le 22/10/2012 14:23, vishal kumar a ?crit :
  Hi

  Please do suggest me where am i going wrong.
  Thanks for the help.
 

 See: crm ra help meta
 Then try something like: crm ra meta sshd lsb # parameters order matter

 Anyway, you won't learn anything out of meta-datas from a LSB
 initscript, because it's just a script (not cluster oriented, not a real
 resource agent), it's not multistate, nothing like that, only
 start/stop/monitor and default mandatory settings.


 --
 Cheers,
 Florian Crouzat


___
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org


[Pacemaker] lsb: could not parse meta-data

2012-10-22 Thread vishal kumar
Hi

I am trying to configure pacemaker with corosync on RHEL 6.

While trying to add lsb resources i get  could not parse meta-data.

The pacemaker version is 1.1.7 . Below is the error what i get when i check
for metadata in crm shell.

*crm(live)ra# list lsb*
*abrt-ccpp   abrt-oops   abrtd
  acpid   atd*
*auditd  autofs  certmonger
 cgconfigcgred*
*corosynccorosync-notifydcpuspeed
 crond   cups*
*haldaemon   haltheartbeat
  httpd   ip6tables*
*iptablesirqbalance  kdump
  killall ktune*
*lvm2-lvmetadlvm2-monitormatahari-broker
  matahari-host   matahari-network*
*matahari-rpcmatahari-servicematahari-sysconfig
 matahari-sysconfig-console  mcelogd*
*mdmonitor   messagebus  netconsole
 netfs   network*
*nfs nfslock ntpd
 ntpdate oddjobd*
*pacemaker   portreserve postfix
  psacct  qpidd*
*quota_nld   rdisc   restorecond
  rhnsd   rhsmcertd*
*rngdrpcbind rpcgssd
  rpcidmapd   rpcsvcgssd*
*rsyslog sandbox saslauthd
  single  smartd*
*sshdsssdsysstat
  tuned   udev-post*
*ypbind  *
*crm(live)ra# meta lsb heartbeat*
*ERROR: heartbeat:lsb: could not parse meta-data: *
*crm(live)ra# meta lsb sshd*
*ERROR: sshd:lsb: could not parse meta-data: *
*crm(live)ra# meta lsb ntpd*
*ERROR: ntpd:lsb: could not parse meta-data: *
*crm(live)ra# meta lsb httpd*
*ERROR: httpd:lsb: could not parse meta-data*

Please do suggest me where am i going wrong.
Thanks for the help.

Thanks
Vishal
___
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org


Re: [Pacemaker] order constraint based on any one of many

2010-08-23 Thread Vishal
From what I have read and understood a clone will run simultaneously  
on all the nodes specified in the config . I donot see how a clone  
will run once a resource group is started . You can alternatively add  
the clone to each group and ensure when either group starts , the  
clone runs with it.


On Aug 23, 2010, at 11:50 AM, Patrick Irvine p...@cybersites.ca wrote:


Hi,

I am setting up a Pacemaker/Corosync/Glusterfs HA cluster set.

Pacemaker ver. 1.0.9.1

With Glusterfs I have 4 nodes serving replicated (RAID1) storage  
back-ends and up to 5 servers mounting the store.  With out getting  
into the specifics of how Gluster works, simply put, as long as any  
one of the 4 backed nodes are running, all of the 5 servers will be  
able to mount the store.


I have started setting up a testing cluster and have the following:  
(crm configure show output)


node test1
node test2
node test3
node test4
primitive glfs ocf:cybersites:glusterfs \
  params volfile=repstore.vol mount_dir=/home \
  op monitor interval=10s timeout=30
primitive glfsd-1 ocf:cybersites:glusterfsd \
  params volfile=glfs.vol \
  op monitor interval=10s timeout=30 \
  meta target-role=Started
primitive glfsd-1-IP ocf:heartbeat:IPaddr2 \
  params ip=192.168.5.221 nic=eth1 cidr_netmask=24 \
  op monitor interval=5s
primitive glfsd-2 ocf:cybersites:glusterfsd \
  params volfile=glfs.vol \
  op monitor interval=10s timeout=30 \
  meta target-role=Started
primitive glfsd-2-IP ocf:heartbeat:IPaddr2 \
  params ip=192.168.5.222 nic=eth1 cidr_netmask=24 \
  op monitor interval=5s \
  meta target-role=Started
primitive glfsd-3 ocf:cybersites:glusterfsd \
  params volfile=glfs.vol \
  op monitor interval=10s timeout=30 \
  meta target-role=Started
primitive glfsd-3-IP ocf:heartbeat:IPaddr2 \
  params ip=192.168.5.223 nic=eth1 cidr_netmask=24 \
  op monitor interval=5s
primitive glfsd-4 ocf:cybersites:glusterfsd \
  params volfile=glfs.vol \
  op monitor interval=10s timeout=30 \
  meta target-role=Started
primitive glfsd-4-IP ocf:heartbeat:IPaddr2 \
  params ip=192.168.5.224 nic=eth1 cidr_netmask=24 \
  op monitor interval=5s
group glfsd-1-GROUP glfsd-1-IP glfsd-1
group glfsd-2-GROUP glfsd-2-IP glfsd-2
group glfsd-3-GROUP glfsd-3-IP glfsd-3
group glfsd-4-GROUP glfsd-4-IP glfsd-4
clone clone-glfs glfs \
  meta clone-max=4 clone-node-max=1 target-role=Started
location block-glfsd-1-GROUP-test2 glfsd-1-GROUP -inf: test2
location block-glfsd-1-GROUP-test3 glfsd-1-GROUP -inf: test3
location block-glfsd-1-GROUP-test4 glfsd-1-GROUP -inf: test4
location block-glfsd-2-GROUP-test1 glfsd-2-GROUP -inf: test1
location block-glfsd-2-GROUP-test3 glfsd-2-GROUP -inf: test3
location block-glfsd-2-GROUP-test4 glfsd-2-GROUP -inf: test4
location block-glfsd-3-GROUP-test1 glfsd-3-GROUP -inf: test1
location block-glfsd-3-GROUP-test2 glfsd-3-GROUP -inf: test2
location block-glfsd-3-GROUP-test4 glfsd-3-GROUP -inf: test4
location block-glfsd-4-GROUP-test1 glfsd-4-GROUP -inf: test1
location block-glfsd-4-GROUP-test2 glfsd-4-GROUP -inf: test2
location block-glfsd-4-GROUP-test3 glfsd-4-GROUP -inf: test3


now I need a way of saying that clone-glfs can start once any of  
glfsd-1, glfsd-2,glfsd-3 or glfsd-4 have started.


Any ideas.  I have read the crm cli document, as well of many  
iterations of the clusters from scratch, etc.


I just can't seem to find an answer.  can it be done?

Pat.

___
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker



___
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker