Re: [Pacemaker] Spreading the Cluster Accross Datacenters

2009/6/9 Димитър Бойн : > Thank you very much, Andrew! > > I am in stand by for the NOC to enable multicast between my subnets. > Two question though: > 1. Compatibility with PIM-SM RFC 2362 and IGMP Version 2 RFC 2236 ? I'm not familiar with those two > 2. Are there some tested threshold levels?

Re: [Pacemaker] failback

2009/6/9 Димитър Бойн : > Thanks Andrew! > > Why even allow "-INFINITY" then > Shouldn't we hard limit in the code the "stickiness" to ">=0" then ? -INFINITY makes more sense in other contexts, and is great for exercising the cluster :-) ___ Pacemaker m

Re: [Pacemaker] Spreading the Cluster Accross Datacenters

Thank you very much, Andrew! I am in stand by for the NOC to enable multicast between my subnets. Two question though: 1. Compatibility with PIM-SM RFC 2362 and IGMP Version 2 RFC 2236 ? 2. Are there some tested threshold levels? - low latency - not greater than ? - high throughput - not lesser th

Re: [Pacemaker] failback

Thanks Andrew! Why even allow "-INFINITY" then Shouldn't we hard limit in the code the "stickiness" to ">=0" then ? ./Dimitar -Original Message- From: Andrew Beekhof [mailto:and...@beekhof.net] Sent: Monday, June 08, 2009 3:14 PM To: pacema...@clusterlabs.org Cc: pacema...@clusterlabs.o

Re: [Pacemaker] failback

2009/6/8 Димитър Бойн : > Hi, > > Check if you have something like > > value="INFINITY"/> > > In your current > > Or similar setting by resources. > > > > The ability to set resource stickiness controls the "fail back on recovery". > > > > If you want your resources to failback on default set: >

Re: [Pacemaker] System Health backend patch part 1

You might find: + syslog (LOG_INFO, "Event id:"U64T"\n", event_id); + syslog (LOG_INFO, "Log timestamp: %s\n", ctime (&(event->time_logged))); + syslog (LOG_INFO, "Event timestamp: %s\n", ctime (&(event->time_event))); to be quite noisy. Perhaps LOG_DEBUG and/or com

Re: [Pacemaker] Spreading the Cluster Accross Datacenters

Pacemaker itself doesn't care. What you need to worry about is the requirements of the underlying cluster stack. Generally this involves low latency, high throughput and high reliability. If you have all three, you should be fine. 2009/6/8 Димитър Бойн : > Hi, > > Has anybody done a pacemaker/ope

Re: [Pacemaker] failback

Hi, Check if you have something like In your current Or similar setting by resources. The ability to set resource stickiness controls the "fail back on recovery". If you want your resources to failback on default set: In object crm_config Best Regards! Boyn, Dimitar G. Tech

[Pacemaker] failback

Hi, I configured a clone for 4 nodes with inside a group of 30 ipaddr2 resources. when I reboot a node the group resources are taken by another node but the once the rebooted node the failed node resources don't go back. What the settings to do it right ? THanks Franck Chionna -- This message h

[Pacemaker] System Health backend patch part 1

Okay, here is my first pass at the backend part needed for system health. Comments/suggestions? (See attached file: pacemaker.mark.patch) Mark Common Information Model/Web-Based Enterprise Management at http://www.openpegasus.org/ Take a look at the Linux Omni Printer Driver Framework at http:/

[Pacemaker] Spreading the Cluster Accross Datacenters

Hi, Has anybody done a pacemaker/openais deployment spreading the nodes between two or more different subnets? I would really appreciate any reference of what does pacemaker need to connect the nodes Thanks, as always! Boyn, Dimitar G. Technical Marketing Engineer db...@postpath

Re: [Pacemaker] [Debian-HA] Updates: Pacemaker 1.0.4, Pacemaker Management Client

Hi there, why does now with pacemaker v1.0.4 pingd logs a message every second (like below)? It didn't with 1.0.3. Is is possible to silence pingd info messages? I am using logd + /etc/logd.cf Jun 08 20:04:27 ariel pingd: [8826]: info: attrd_update: Sent update: pingd=100 for localhost Jun 08

Re: [Pacemaker] ipAddr2 OCF

On Sat, Jun 6, 2009 at 10:52 PM, Infos E-Blokos wrote: > Hi, > > is it possible to create in primitive ipAddr2 resource as Clone clusterip > an IP range (30 IPs) rather than create a primitive resource for eache IP ? Possible, yes. Implemented. no. ___

Re: [Pacemaker] cibadmin -R

On Sun, Jun 7, 2009 at 5:29 AM, Infos E-Blokos wrote: > Hi, > > after verify my new cib.xml > crm_verify -V -x newcib.xml > OK > and try to update > cibadmin -R -o cib -x cib.xml > it says > Call cib_replace failed (-47): Update does not conform to the configured > schema/DTD > > Any suggesti

Re: [Pacemaker] [Debian-HA] Updates: Pacemaker 1.0.4, (Offensive Word Found In Message) Pacemaker Management Client

On Mon, 2009-06-08 at 00:36 +0200, Martin Gerhard Loschwitz wrote: > Hi Folks, > > just another rounds of updates flying in as I am writing this. Pacemaker > 1.0.4 is now available for Debian in my repository (lenny for amd64/i386 > and sid for amd64), and there's another big thing. > > (Actually

Re: [Pacemaker] pacemaker-mgmt-client: broken dependency in CentOS 5 repo

Hi Dejan, On Tue, 2009-06-02 at 13:02 +0200, Dejan Muhamedagic wrote: > Hi Yan, > > On Mon, Jun 01, 2009 at 03:00:52PM +0800, Yan Gao wrote: > > On Wed, 2009-05-27 at 15:46 +0200, Andrew Beekhof wrote: > > > I'll have to defer to Yan Gao on this one. > > > I'm not familiar with the GUI's requireme