Re: [ClusterLabs] Pacemaker in Azure

bin...@psmnv.com>; Cluster Labs - All topics related to open-source clustering welcomed <users@clusterlabs.org> Subject: RE: [ClusterLabs] Pacemaker in Azure Eric Robinson <eric.robin...@psmnv.com> writes: > Hi Kristoffer -- > > If you would be willing to share your AWS i

Re: [ClusterLabs] Pacemaker in Azure

com] > Sent: Friday, August 25, 2017 3:16 AM > To: Eric Robinson <eric.robin...@psmnv.com>; Cluster Labs - All topics > related to open-source clustering welcomed <users@clusterlabs.org> > Subject: Re: [ClusterLabs] Pacemaker in Azure > > Eric Robinson <eric.robin.

Re: [ClusterLabs] Pacemaker in Azure

Eric Robinson 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

Re: [ClusterLabs] Pacemaker in Azure

there. -- Eric Robinson > -Original Message- > From: Oyvind Albrigtsen [mailto:oalbr...@redhat.com] > Sent: Friday, August 25, 2017 12:17 AM > To: Cluster Labs - All topics related to open-source clustering welcomed > <users@clusterlabs.org> > Subject: Re: [Cluster

Re: [ClusterLabs] Pacemaker in Azure

There's the awsvip agent that can handle secondary private IP addresses this way (to be used with order/colocation constraints with IPaddr2). https://github.com/ClusterLabs/resource-agents/blob/master/heartbeat/awsvip There's also the awseip for Elastic IPs that can assign your Elastic IP to

Re: [ClusterLabs] Pacemaker in Azure

ail...@redhat.com> Sent: Thursday, August 24, 2017 4:45:32 PM To: Cluster Labs - All topics related to open-source clustering welcomed Subject: Re: [ClusterLabs] Pacemaker in Azure That would definitely be of wider interest. I could see modifying the IPaddr2 RA to take some new arguments for AWS

Re: [ClusterLabs] Pacemaker in Azure

Unfortunately I can't post the full resource agent here. In our search for solutions we did find a resource agent for managing AWS Elastic IPs: https://github.com/moomindani/aws-eip-resource-agent/blob/master/eip. This was not what we wanted, but it will give you an idea of how it can work. Our

Re: [ClusterLabs] Pacemaker in Azure

ed to open-source clustering > welcomed <users@clusterlabs.org> > Subject: Re: [ClusterLabs] Pacemaker in Azure > > > > That's what we did in AWS. The IPaddr2 resource agent does an arp > broadcast after changing the local IP but this does not work in AWS > (probably f

Re: [ClusterLabs] Pacemaker in Azure

That's what we did in AWS. The IPaddr2 resource agent does an arp broadcast after changing the local IP but this does not work in AWS (probably for the same reasons as Azure). We created our own OCF resource agent that uses the Amazon APIs to move the IP in AWS land and made that dependent on

Re: [ClusterLabs] Pacemaker in Azure

> Don't use Azure? ;) That would be my preference. But since I'm stuck with Azure (management decision) I need to come up with something. It appears there is an Azure API to make changes on-the-fly from a Linux box. Maybe I'll write a resource agent to change Azure and make IPaddr2 dependent

Re: [ClusterLabs] Pacemaker in Azure

On 2017-08-24 03:56 PM, Eric Robinson wrote: > 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

[ClusterLabs] Pacemaker in Azure

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