Re: [ClusterLabs] Unable to Build fence-agents from Source on RHEL6

Believe me, I would love to use a more modern dist, but RHEL6 is currently our standard image… -- [ jR ] M: +1 (703) 628-2621 @: ja...@eramsey.org there is no path to greatness; greatness is the path On 8/10/16, 2:50 PM, "Jan Pokorný" wrote: On 10/08/16

Re: [ClusterLabs] ocf:heartbeat:LVM or /etc/lvm/lvm.conf settings question

you described your problem, but didn't show any logs or cluster config. 2016-08-10 23:47 GMT+02:00 Darren Kinley : > The default lvm.conf's filter includes /dev/drbdX > > # By default we accept every block device except udev names, floppy and > cdrom drives: >

Re: [ClusterLabs] ocf:heartbeat:LVM or /etc/lvm/lvm.conf settings question

The default lvm.conf's filter includes /dev/drbdX # By default we accept every block device except udev names, floppy and cdrom drives: filter = [ "r|/dev/.*/by-path/.*|", "r|/dev/.*/by-id/.*|", "r|/dev/fd.*|", "r|/dev/cdrom|", "a/.*/" ] -Original Message- From: emmanuel

Re: [ClusterLabs] ocf:heartbeat:LVM or /etc/lvm/lvm.conf settings question

your lvm filter include the drbd devices /dev/drbdX ? 2016-08-10 21:38 GMT+02:00 Darren Kinley : > Hi, > > I have an LVM logical volume and used DRBD to replicate it to another > server. > The /dev/drbd0 has PV/VG/LVs which are mostly working. > I have colocation and

[ClusterLabs] Coming in 1.1.16: versioned resource parameters

Have you ever changed a resource agent in a backward-incompatible way, and found yourself wishing you could do a rolling upgrade? With a new feature in the current master branch, which will be part of the next Pacemaker release, you will be able to specify different resource parameters to be used

[ClusterLabs] ocf:heartbeat:LVM or /etc/lvm/lvm.conf settings question

Hi, I have an LVM logical volume and used DRBD to replicate it to another server. The /dev/drbd0 has PV/VG/LVs which are mostly working. I have colocation and order constraints that bring up a VIP, promote DRBD and start LVM plus file systems. The problem arises when I take the active node

Re: [ClusterLabs] Unable to Build fence-agents from Source on RHEL6

On 10/08/16 20:50 +0200, Jan Pokorný wrote: > On 10/08/16 16:52 +, Jason A Ramsey wrote: >> Installing the openwsman-python package doesn’t work. Configure’ing >> the fence-agents source tree fails because it still can’t find the >> pywsman module. I thought that it might be because it’s

Re: [ClusterLabs] Unable to Build fence-agents from Source on RHEL6

On 10/08/16 16:52 +, Jason A Ramsey wrote: > Installing the openwsman-python package doesn’t work. Configure’ing > the fence-agents source tree fails because it still can’t find the > pywsman module. I thought that it might be because it’s looking in > /usr/lib/python-x/site-packages rather

Re: [ClusterLabs] Unable to Build fence-agents from Source on RHEL6

Installing the openwsman-python package doesn’t work. Configure’ing the fence-agents source tree fails because it still can’t find the pywsman module. I thought that it might be because it’s looking in /usr/lib/python-x/site-packages rather than /usr/lib64/python-x/site-packages (or vice

Re: [ClusterLabs] Unable to Build fence-agents from Source on RHEL6

On 09/08/16 20:20 +, Jason A Ramsey wrote: > Here’s the output I now get out of pip install pywsman: > > < stupiderrormessage > > > # pip install pywsman > DEPRECATION: Python 2.6 is no longer supported by the Python core team, > please upgrade your Python. A future version of pip will drop

Re: [ClusterLabs] Unable to Build fence-agents from Source on RHEL6

On 2016-08-10 10:04, Jason A Ramsey wrote: Traceback (most recent call last): File "eps/fence_eps", line 14, in if sys.version_info.major > 2: AttributeError: 'tuple' object has no attribute 'major' Replace with sys.version_info[0] Dima ___

Re: [ClusterLabs] Unable to Build fence-agents from Source on RHEL6

Thanks! I actually just figured this out and was about to share my findings with the list. Lol. -- [ jR ] M: +1 (703) 628-2621 @: ja...@eramsey.org there is no path to greatness; greatness is the path On 8/10/16, 11:12 AM, "Dmitri Maziuk" wrote: On

Re: [ClusterLabs] Can Pacemaker monitor geographical separated servers

On 08/10/2016 04:43 PM, Jason A Ramsey wrote: > > I can’t answer all of this because I’m still working out how to do > fencing, but I’ve been setting up a Pacemaker cluster in Amazon Web > Services across two separate availability zones. Naturally, this means > that I have to bridge subnets, so

Re: [ClusterLabs] Unable to Build fence-agents from Source on RHEL6

Okay, so ripped apart the code and removed references to the fence_amt_ws module. Configure worked. Make got really close, but not quite:

Re: [ClusterLabs] Can Pacemaker monitor geographical separated servers

I can’t answer all of this because I’m still working out how to do fencing, but I’ve been setting up a Pacemaker cluster in Amazon Web Services across two separate availability zones. Naturally, this means that I have to bridge subnets, so I’ve battled through a good bit of this already.

Re: [ClusterLabs] Unable to Build fence-agents from Source on RHEL6

Unfortunately, I need the latest features in my use case… Thanks for the tip, though. -- [ jR ] M: +1 (703) 628-2621 @: ja...@eramsey.org there is no path to greatness; greatness is the path From: Marek Grac Reply-To: Cluster Labs - All

Re: [ClusterLabs] Can Pacemaker monitor geographical separated servers

On Tue, Aug 9, 2016 at 9:40 PM, bhargav M.P wrote: > Hi All, > I have deployment where we have two Linux servers that are geographically > separated and they are across different subnets . I want the server to work > in Active/Standby mode . I would like to use

[ClusterLabs] Can Pacemaker monitor geographical separated servers

Hi All, I have deployment where we have two Linux servers that are geographically separated and they are across different subnets . I want the server to work in Active/Standby mode . I would like to use pacemaker-corsync for performing switch over when active fails. My requirement: * would like

Re: [ClusterLabs] Unable to Build fence-agents from Source on RHEL6

Hi, * pywsman is required only for fence_amt_ws so if you don't need it, feel free to remove this dependency (and agent) * python2.6 (and RHEL6) is no longer a platform that we support at upstream. We aim for python 2.7 and 3.x currently. But it might work on python2.6 (and Oyvind accepts patches