[ClusterLabs] Pacemaker in Azure
eric.robinson at psmnv.com
Fri Aug 25 04:07:53 EDT 2017
Thanks. Leon sent me the same one earlier but I hadn't mentioned it yet (just got it a short while ago). I'll be able to use it as a template to build one for Azure. I have already installed the Azure CLI and it is working from my Linux cluster nodes, so I'm maybe a third of the way there.
> -----Original Message-----
> From: Oyvind Albrigtsen [mailto:oalbrigt at redhat.com]
> Sent: Friday, August 25, 2017 12:17 AM
> To: Cluster Labs - All topics related to open-source clustering welcomed
> <users at clusterlabs.org>
> Subject: 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).
> There's also the awseip for Elastic IPs that can assign your Elastic IP to hosts or
> secondary private IPs.
> On 25/08/17 10:13 +1000, Leon Steffens wrote:
> >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:
> >This was not what we wanted, but it will give you an idea of how it can
> >Our script manages secondary private IPs by using:
> >aws ec2 assign-private-ip-addresses
> >aws ec2 unassign-private-ip-addresses
> >aws ec2 describe-network-interfaces
> >There are a few things to consider:
> >* The AWS call to assign IPs to an EC2 instance is asynchronous (or it
> >was the last time I checked), so you have to wait a bit (or poll
> >AWS/Azure until the IP is ready).
> >* The IP change is slower than a normal VIP change on the machine, so
> >expect a slightly longer outage.
> >Users mailing list: Users at clusterlabs.org
> >Project Home: http://www.clusterlabs.org Getting started:
> >Bugs: http://bugs.clusterlabs.org
> Users mailing list: Users at clusterlabs.org
> Project Home: http://www.clusterlabs.org Getting started:
> Bugs: http://bugs.clusterlabs.org
More information about the Users