Serge Dubrouski writes:
> On Mon, Jun 27, 2011 at 3:33 PM, veghead studyblue.com> wrote:
> If I remove the co-location, won't the elastic_ip resource just stay where it
> is? Regardless of what happens to LDAP?
>
> Right. That's why I think that you don't rea
Sorry for the questions. Some days my brain is just slow. :)
Serge Dubrouski writes:
> If you want to make your LDAP independent from IP just remove your
> collocation:colocation ldap-with-eip inf: elastic_ip ldap-clone
Is that really what I want to do? I mean, I need the elastic ip assigned to
veghead writes:
> Pair of LDAP servers running 389 (formerly Fedora DS) in
> high availability using Pacemaker with a floating IP.
> In addition, 389 supports multi-master replication,
> where all changes on one node are automatically
> replicated on one or more other nodes.
I&
Dejan Muhamedagic writes:
> lsb:dirsrv doesn't understand master/slave. That's OK, none of
> LSB agents do. You can only try to use clones (clone ldap-clone
> ldap ...).
That worked perfectly. I was getting master/slave and basic
clone stuff mixed up. Thanks!
I'm trying to setup a pair of LDAP servers running 389 (formerly Fedora DS) in
high availability using Pacemaker with a floating IP. In addition, 389 supports
multi-master replication, where all changes on one node are automatically
replicated on one or more other nodes.
I'm fairly close to hav
Dejan Muhamedagic writes:
> On Fri, May 27, 2011 at 08:21:08PM +0000, veghead wrote:
> > 1) Is there a way to force crm to accept my configuration request
> > ~before~ starting the second node?
>
> No before the DC is elected. There are two settings: dc-deadtime
> and s
veghead writes:
> Todd Nine writes:
> Wow. The example pacemaker config and the trick of starting
> heartbeat before
Bah. So close. But I still don't have it completely automated.
If I start heatbeat on the first node and then run:
crm configure < myconfigure.txt
That
Todd Nine writes:
> I have a setup nearly working. Would you be willing to share recipes?
...
> It's not quite working yet, but it's close. Since you've managed to get
> this working, you may be able to finish these off. I have everything
> working except the init start/stop hooks for pacema
Does anyone have any links to documentation on automating Pacemaker setup with
tools like Chef or Puppet?
I have a working two node cluster for HAProxy on EC2, but I'd like to fully
automate the setup process for future nodes. Specifically so I can spin up a
new
instance w/out any manual inter
