Hi Kristoffer -- If you would be willing to share your AWS ip control agent(s), I think those would be very helpful to us and the community at large. I'll be happy to share whatever we come up with in terms of an Azure agent when we're all done.
-- Eric Robinson -----Original Message----- From: Kristoffer Grönlund [mailto:[email protected]] Sent: Friday, August 25, 2017 3:16 AM To: Eric Robinson <[email protected]>; Cluster Labs - All topics related to open-source clustering welcomed <[email protected]> Subject: Re: [ClusterLabs] Pacemaker in Azure Eric Robinson <[email protected]> writes: > I deployed a couple of cluster nodes in Azure and found out right away that > floating a virtual IP address between nodes does not work because Azure does > not honor IP changes made from within the VMs. IP changes must be made to > virtual NICs in the Azure portal itself. Anybody know of an easy way around > this limitation? You will need a custom IP control agent for Azure. We have a series of agents for controlling IP addresses and domain names in AWS, but there is no agent for Azure IP control yet. (At least as far as I am aware). Cheers, Kristoffer > > -- > Eric Robinson > > _______________________________________________ > Users mailing list: [email protected] > http://lists.clusterlabs.org/mailman/listinfo/users > > Project Home: http://www.clusterlabs.org Getting started: > http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf > Bugs: http://bugs.clusterlabs.org -- // Kristoffer Grönlund // [email protected] _______________________________________________ Users mailing list: [email protected] http://lists.clusterlabs.org/mailman/listinfo/users Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
