I agree completely. Are you offering to make those changes? Because they would expand the capability of resource angent and would be a welcome addition. Also, full disclosure, I need to have something in place by the weekend, lol. ________________________________ From: Ken Gaillot <kgail...@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/Azure parameters, and if those are configured, it would do the appropriate API requests. On Thu, 2017-08-24 at 23:27 +0000, Eric Robinson wrote: > Leon -- I will pay you one trillion samolians for that resource agent! > Any way we can get our hands on a copy? > > > > -- > Eric Robinson > > > > From: Leon Steffens [mailto:l...@steffensonline.com] > Sent: Thursday, August 24, 2017 3:48 PM > To: Cluster Labs - All topics related 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 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 the IPaddr2 > resource, and it worked fine. > > > > > > > > > Leon Steffens > > > > > On Fri, Aug 25, 2017 at 8:34 AM, Eric Robinson > <eric.robin...@psmnv.com> wrote: > > > 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 on it. That might work? > > -- > Eric Robinson > > > _______________________________________________ > Users mailing list: Users@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 > > > > > _______________________________________________ > Users mailing list: Users@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 -- Ken Gaillot <kgail...@redhat.com> _______________________________________________ Users mailing list: Users@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
_______________________________________________ Users mailing list: Users@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