Re: [ClusterLabs] Pacemaker in Azure

2017-08-24 Thread Eric Robinson
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

Re: [ClusterLabs] Pacemaker in Azure

2017-08-24 Thread Leon Steffens
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

2017-08-24 Thread Ken Gaillot
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 +, Eric Robinson wrote: > Leon -- I will pay you one

Re: [ClusterLabs] Pacemaker in Azure

2017-08-24 Thread Leon Steffens
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

2017-08-24 Thread Eric Robinson
> 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] start one node only?

2017-08-24 Thread Ken Gaillot
On Thu, 2017-08-24 at 15:53 -0500, Dimitri Maziuk wrote: > On 08/24/2017 03:40 PM, Ken Gaillot wrote: > > > You could set wait_for_all to 0 in corosync.conf, then boot. The living > > node should try to fence the other one, and proceed if fencing succeeds. > > Didn't I just read a thread that

Re: [ClusterLabs] ClusterLabs.Org Documentation Problem?

2017-08-24 Thread Ken Gaillot
On Wed, 2017-08-23 at 23:33 +, Eric Robinson wrote: > I have a BIG correction. > > If you follow the instructions titled, "Pacemaker 1.1 for Corosync 2.x," and > NOT the ones entitled, "Pacemaker 1.1 for CMAN or Corosync 1.x," guess what? > It installs cman anyway, and you spend a couple of

Re: [ClusterLabs] start one node only?

2017-08-24 Thread Ken Gaillot
On Thu, 2017-08-24 at 15:10 -0500, Dimitri Maziuk wrote: > Hi everyone, > > I seem to remember seeing theis once before, but my google-fu is > failing: I've a 2-node active-passive cluster, when I power up one node > only, resources remain stopped. Is there a way to boot a cluster on one > node

Re: [ClusterLabs] start one node only?

2017-08-24 Thread Dimitri Maziuk
PS. centos 7.latest w/ the current pcs/corosync/pacemaker rpms as distributed by centos, resources are stonith:fence_scsi, IPaddr2, and ZFS. -- Dimitri Maziuk Programmer/sysadmin BioMagResBank, UW-Madison -- http://www.bmrb.wisc.edu signature.asc Description: OpenPGP digital signature

[ClusterLabs] start one node only?

2017-08-24 Thread Dimitri Maziuk
Hi everyone, I seem to remember seeing theis once before, but my google-fu is failing: I've a 2-node active-passive cluster, when I power up one node only, resources remain stopped. Is there a way to boot a cluster on one node only? -- Note that if I boot up the other node everything starts, and

Re: [ClusterLabs] Pacemaker in Azure

2017-08-24 Thread Digimer
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

2017-08-24 Thread Eric Robinson
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