Re: [ClusterLabs] Cluster monitoring

2015-10-21 Thread Ken Gaillot
On 10/21/2015 08:24 AM, Michael Schwartzkopff wrote: > Am Mittwoch, 21. Oktober 2015, 18:50:15 schrieb Arjun Pandey: >> Hi folks >> >> I had a question on monitoring of cluster events. Based on the >> documentation it seems that cluster monitor is the only method >> of monitoring the cluster

Re: [ClusterLabs] difference between OCF return codes for monitor action

2015-10-21 Thread Vallevand, Mark K
In my resource agent, I use OCF_NOT_RUNNING to indicate that the managed resource is literally ‘not running’. I use OCF_ERR_GENERIC to indicate that the managed resource is running, but has entered an error state. It is potentially recoverable if it is restarted. I use OCF_ERR_PERM to

Re: [ClusterLabs] difference between OCF return codes for monitor action

2015-10-21 Thread Ken Gaillot
On 10/21/2015 07:44 AM, Kostiantyn Ponomarenko wrote: > Hi, > > What is the difference between "OCF_ERR_GENERIC" and "OCF_NOT_RUNNING" > return codes in "monitor" action from the Pacemaker's point of view? > > I was looking here >

[ClusterLabs] Cluster monitoring

2015-10-21 Thread Arjun Pandey
Hi folks I had a question on monitoring of cluster events. Based on the documentation it seems that cluster monitor is the only method of monitoring the cluster events. Also since it seems to poll based on the interval configured it might miss some events. Is that the case ? Is their any other

Re: [ClusterLabs] about the configuration for a iSCSITarget resource using the crm(8) shell.

2015-10-21 Thread Dejan Muhamedagic
Hi, On Wed, Oct 21, 2015 at 12:17:15PM +, Shilu wrote: > Hi,everyone! > The following is an example configuration for a iSCSITarget resource using > the crm(8) shell: > primitive tgt ocf:heartbeat:iSCSITarget \ > params implementation="tgt" iqn="foo" tid="1" \ > op monitor interval="1s"

Re: [ClusterLabs] Cluster monitoring

2015-10-21 Thread Michael Schwartzkopff
Am Mittwoch, 21. Oktober 2015, 18:50:15 schrieb Arjun Pandey: > Hi folks > > I had a question on monitoring of cluster events. Based on the > documentation it seems that cluster monitor is the only method of > monitoring the cluster events. Also since it seems to poll based on the > interval

[ClusterLabs] [ANNOUNCE] [HA] [Pacemaker] new, maintained openstack-resource-agents repository

2015-10-21 Thread Adam Spiers
[cross-posting to openstack-dev and pacemaker user lists; please consider trimming the recipients list if your reply is not relevant to both communities] Hi all, Back in June I proposed moving the well-used but no longer maintained https://github.com/madkiss/openstack-resource-agents/ repository

Re: [ClusterLabs] Cluster node loss detection.

2015-10-21 Thread Jan Pokorný
On 16/10/15 12:51 -0400, Digimer wrote: > On 16/10/15 12:37 PM, Vallevand, Mark K wrote: >> So, it looks like setting the corosync parameters in cluster.conf >> has some effect. Cman seems to pass them to corosync. > > Yes, never configure corosync directly when using cman, only use >

[ClusterLabs] difference between OCF return codes for monitor action

2015-10-21 Thread Kostiantyn Ponomarenko
Hi, What is the difference between "OCF_ERR_GENERIC" and "OCF_NOT_RUNNING" return codes in "monitor" action from the Pacemaker's point of view? I was looking here http://clusterlabs.org/doc/en-US/Pacemaker/1.1/html/Pacemaker_Explained/s-ocf-return-codes.html , but I still don't see the

Re: [ClusterLabs] difference between OCF return codes for monitor action

2015-10-21 Thread Michael Schwartzkopff
Am Mittwoch, 21. Oktober 2015, 15:44:17 schrieb Kostiantyn Ponomarenko: > Hi, > > What is the difference between "OCF_ERR_GENERIC" and "OCF_NOT_RUNNING" > return codes in "monitor" action from the Pacemaker's point of view? > > I was looking here >