Re: [Pacemaker] Multi-level ACLs for the CIB

Hi, Sorry for delaying this update so long because of some other works. The ACL implementation has been improved. As we discussed, two new functionalities has been added: * The access control on attributes of elements * xpath based ACL. The schema and the corresponding codes has been simplified:

Re: [Pacemaker] Master/Slave Confusion

OK - it seems I've achieved what I want via the following configuration: node testvm1 node testvm2 node testvm3 primitive LDAP lsb:ldap \ op monitor interval="40s" \ op monitor interval="41s" role="Master" primitive LDAP-IP ocf:heartbeat:IPaddr2 \ params ip="10.1.1.80" cid

Re: [Pacemaker] Master/Slave Confusion

if you make the LDAP daemon listen on all available interfaces, it will accept connections on the on-demand activated floating-ip. Well, I'm trying to get this to work and running into a wall... I've got 3 servers, I want LDAP to run on testvm2 and testvm3. I've configured LDAP on those 2 s

Re: [Pacemaker] Master/Slave Confusion

Thanks! This will be helpful... Rafał Kupka wrote: On Sun, Jan 31, 2010 at 06:39:28PM -0800, Erich Weiler wrote: Hi, However, it seems that when LDAP starts, the IP needs to be live on each node for the LDAP server to bind on that IP. Is that how the master/slave setup works in pacemaker?

[Pacemaker] Announce: Final Release of Heartbeat 3.0.2, Cluster-Glue 1.0.2, and Resource-Agents 1.0.2

This is to announce that we now have released version 1.0.2 Cluster Glue and the Resource Agents package, and version 3.0.2 for Heartbeat. This is the STABLE series of Heartbeat, intended for use with the Pacemaker cluster resource manager. 3.0.2 is the first "official" 3.0 release. We chose 3.0

Re: [Pacemaker] Master/Slave Confusion

On Sun, Jan 31, 2010 at 06:39:28PM -0800, Erich Weiler wrote: Hi, > However, it seems that when LDAP starts, the IP needs to be live on each > node for the LDAP server to bind on that IP. Is that how the > master/slave setup works in pacemaker? Does it use iptables or > something to block

Re: [Pacemaker] Corosync+Pacemaker multistate failed rule

Sorry but it is solved. The problem wasn't the rule. It was a bad configuration of a resource. I have an attribute bad written. Thank you! 2010/2/1 Adrian Chapela > Hello, > > I have this rules: > > > > value="correo2"/> > > > > > operation="eq" value="correo3"/>

Re: [Pacemaker] Master/Slave Confusion

Hi, if you make the LDAP daemon listen on all available interfaces, it will accept connections on the on-demand activated floating-ip. Or, if you really want to make the ldap daemon listen only on the floating-ip, you would have to write a resoure agent for ldap which will edit the ldap config

[Pacemaker] Corosync+Pacemaker multistate failed rule

Hello, I have this rules: DRBD-Samba and DRBD-Mail are two multi-state resources. Only one of node is Master. As I can read in the rules, I know that correo2 will be the Master of DRBD-Mail and cor