[ClusterLabs] Pacemaker in Azure

Kristoffer Grönlund kgronlund at suse.com
Fri Aug 25 12:55:46 EDT 2017

Eric Robinson <eric.robinson at psmnv.com> writes:

> 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.

I meant the agents that are in resource-agents already:


You'll probably also be interested in fencing: There are agents for
fencing both on AWS and Azure in the fence-agents repository.


> --
> Eric Robinson
> -----Original Message-----
> From: Kristoffer Grönlund [mailto:kgronlund at suse.com] 
> Sent: Friday, August 25, 2017 3:16 AM
> To: Eric Robinson <eric.robinson at psmnv.com>; Cluster Labs - All topics related to open-source clustering welcomed <users at clusterlabs.org>
> Subject: Re: [ClusterLabs] Pacemaker in Azure
> Eric Robinson <eric.robinson at psmnv.com> 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: Users at clusterlabs.org 
>> 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
> // kgronlund at suse.com

// Kristoffer Grönlund
// kgronlund at suse.com

More information about the Users mailing list