Okay, so assuming the VIP travels with the active server, one idea would be to
have an iptables rule on each server that does a local redirect:
On the 8081 machine:
iptables -t nat -I PREROUTING --source 0/0 --destination 0/0 -p tcp --dport
8080 -j REDIRECT --to-ports 8081
And on the 8082 mach
Are you wanting to move all the resources back or just that one resource?
I'm still learning, but one simple way I move all resources back from nodeb to
nodea is like this:
# on nodeb
sudo crm node standby
# now services migrate to nodea
# still on nodeb
sudo crm node online
This may be a naive
ager"
> Sent: Friday, February 25, 2011 10:53:34 AM
> Subject: Re: [Pacemaker] Validate strategy for RA on DRBD standby node
> On Thu, Feb 24, 2011 at 10:49:27AM -0500, David McCurley wrote:
> > Thanks for the quick reply and especially the link. It was much
> > better and m
on DRBD standby node
>
> Why are you trying to start LDAP on a node where you don't have your
> DRBD resource mounted. Having LDAP up on both nodes would make sense
> if you were building an active/active LDAP cluster with syncrepl or
> any other replication mechanism. In that cas
Thanks for the quick reply and especially the link. It was much better and
more thorough in testing than the other shell ra ldap link I found.
> That would be the first python RA. BTW, there was recently posted
> slapd RA (implemented in shell), which I should review, but
> haven't done that yet
Pacemaker and list newbie here :)
I'm writing a resource adapter in python for the newer release of OpenLDAP but
I need some pointers on a strategy for the validate function in a certain case.
(In python because the more advanced shell scripting hurts my head :). Here
is the situation:
The c
