small update.
I could enforce changes using -F option so that I could get rid of " Do you
still want to commit?"
On Wed, Dec 11, 2013 at 11:04 AM, ESWAR RAO wrote:
> Hi All,
>
> When I ran below configuration on a 3 node HB+pacemaker setup I am getting
> WARNING: Resources cluster-ip,nvp_vip vi
why you have cluster-ip and nvp_vip primitivies with same ip address and
after that you cloned nvp_vip, what would you archive?
2013/12/11 ESWAR RAO
> small update.
> I could enforce changes using -F option so that I could get rid of " Do
> you still want to commit?"
>
>
> On Wed, Dec 11, 2013
Hi Emmanuel,
I have IPVS running on node3 which does tcp load balancing.
The IPVS is configured with direct routing so the same VIP address should
be present in loopback interfaces of other two nodes which are real backend
servers for IPVS.
Thanks
Eswar
On Wed, Dec 11, 2013 at 8:04 PM, emmanue
read this
http://www.sebastien-han.fr/blog/2012/09/16/pacemaker-load-balancing-with-clone/
2013/12/11 ESWAR RAO
> Hi Emmanuel,
>
> I have IPVS running on node3 which does tcp load balancing.
> The IPVS is configured with direct routing so the same VIP address should
> be present in loopback int
- Original Message -
> From: "Andrew Beekhof"
> To: "The Pacemaker cluster resource manager"
> Sent: Wednesday, November 20, 2013 9:02:40 PM
> Subject: [Pacemaker] Time to get ready for 1.1.11
>
> With over 400 updates since the release of 1.1.10, its time to start
> thinking about a new
