Re: [ClusterLabs] iSCSI on ZFS on DRBD

The way that Pacemaker interacts with services is using resource agents. These resource agents are bash scripts that you can modify to your heart’s content to do the things you want to do. Having worked with the ocf:heartbeat:iSCSITarget and ocf:heartbeat:iSCSILogicalUnit quite a lot in the

Re: [ClusterLabs] OS Patching Process

_to_every_cluster_node_first -> now_add_device_the_volume_group_on_every_cluster_node -> now_resize_the_volume_on_every_cluster_node : now you have every cluster with the same logical volume size, now you can resize drbd and filesystem on the active node 2016-11-22 17:35 GMT+01:00 Jason A Ramsey <ja...@era

[ClusterLabs] OS Patching Process

Can anyone recommend a bulletproof process for OS patching a pacemaker cluster that manages a drbd mirror (with LVM on top of the drbd and luns defined for an iscsi target cluster if that matters)? Any time I’ve tried to mess with the cluster, it seems like I manage to corrupt my drbd

Re: [ClusterLabs] DRBD Insufficient Privileges Error

Did you install the drbd-pacemaker package? That’s the package that contains the resource agent. -- [ jR ] there is no path to greatness; greatness is the path From: Jasim Alam Reply-To: Cluster Labs - All topics related to open-source clustering welcomed

[ClusterLabs] ocf:linbit:drbd Deprecated?

I note from http://linux-ha.org/doc/man-pages/re-ra-drbd.html that this resource agent is deprecated…? What’s the alternative? I wouldn’t care except I just had to build a whole mess of stuff from source so I could get an iSCSI target on RHEL6 that supports SCSI-3 persistent reservations and

[ClusterLabs] (ELI5) Physical disk XXXXXXX does not have the inquiry data (SCSI page 83h VPD descriptor) that is required by failover clustering

Anyone that follows this mailing list at all has probably noticed that I’m creating a 2-node HA iSCSI Target on RHEL 6 using Pacemaker/Corosync (and CMAN, I guess) and the available tgt scsi tools to use as shared file system for some Windows Server Failover Cluster nodes. After a great deal of

[ClusterLabs] Node Fencing and STONITH in Amazon Web Services

If you don’t mind, please allow me to walk through my architecture just a bit. I know that I am far from an expert on this stuff, but I feel like I have a firm grasp on how this all works conceptually. That said, I welcome your insights and advice on how to approach this problem—and any

Re: [ClusterLabs] Error When Creating LVM Resource

labs.org> Subject: Re: [ClusterLabs] Error When Creating LVM Resource On Fri, Aug 26, 2016 at 9:32 AM, Jason A Ramsey <ja...@eramsey.org<mailto:ja...@eramsey.org>> wrote: Failed Actions: * gctvanas-lvm_start_0 on node1 'not running' (7): call=42, status=complete, exitreason='LVM: targetfs did

[ClusterLabs] Error When Creating LVM Resource

So, I’m setting up a two node cluster that will eventually (hopefully) serve as an HA iSCSI Target (Active/Passive) on RHEL 6. I’m using the [incredibly poorly written] guide I found on Linbit’s website (“Highly available iSCSI storage with DRBD and Pacemaker”). I have somehow gotten pretty far

Re: [ClusterLabs] pcs cluster auth returns authentication error

? -- [ jR ] @: ja...@eramsey.org there is no path to greatness; greatness is the path On 8/25/16, 9:50 PM, "Jason A Ramsey" <ja...@eramsey.org> wrote: Still stuck, but here’s the output of the command with --debug turned on: Error: node1: Username and/or password is inc

Re: [ClusterLabs] pcs cluster auth returns authentication error

read config 'cluster.conf' from '/etc/cluster/cluster.conf': No such file\n", "W, [2016-08-25T21:46:40.850609 #4825] WARN -- : Cannot read config 'cluster.conf' from '/etc/cluster/cluster.conf': No such file or directory - /etc/cluster/cluster.conf\n", "I, [2

Re: [ClusterLabs] pcs cluster auth returns authentication error

ot; <kgail...@redhat.com> wrote: On 08/25/2016 03:04 PM, Jason A Ramsey wrote: > Please help. Just getting this thing stood up on a new set of servers > and getting stymied right out the gate: > > > > # pcs cluster auth node1 node

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

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

korný" <jpoko...@redhat.com> wrote: 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 su

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

te: 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'

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

ts patches that fixes it) * for RHEL6 you might want to use our branch 'RHEL6' that have to work with python2.6. Maybe you won't get latest features but it should be enough for most of the installations. m, On Tue, Aug 9, 2016 at 10:20 PM, Jason A Ramsey <ja...@eramsey.org<mailto:ja...@e

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

Oyvind accepts patches that fixes it) * for RHEL6 you might want to use our branch 'RHEL6' that have to work with python2.6. Maybe you won't get latest features but it should be enough for most of the installations. m, On Tue, Aug 9, 2016 at 10:20 PM, Jason A Ramsey <ja...@eramsey.org<mailto

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

So, I’ve managed to wade through the majority of dependency hell issues I’ve encountered trying to get RPMs built of Pacemaker and its ancillary packages. That is, of course, with the exception of the fence-agents source tree (grabbed from github). Autogen.sh works great, but when it comes to

Re: [ClusterLabs] STONITH Fencing for Amazon EC2

Is there some other [updated] fencing module I can use in this use case? -- [ jR ] M: +1 (703) 628-2621 @: ja...@eramsey.org there is no path to greatness; greatness is the path On 8/2/16, 11:59 AM, "Digimer" <li...@alteeve.ca> wrote: On 02/08/16 10:02 AM, Jaso

[ClusterLabs] STONITH Fencing for Amazon EC2

I’ve found [oldish] references on the internet to a fencing module for Amazon EC2, but it doesn’t seem to be included in any the fencing yum packages for CentOS. Is this module not part of the canonical distribution? Is there something else I should be looking for? -- [ jR ] @:

[ClusterLabs] Pacemaker Resource Agent for iSCSILogicalUnit is Incomplete

Hi, everyone. You might’ve noticed a few emails from me in the last couple of weeks that chronicle my struggle to get an HA iSCSI Target configured in AWS. After stumbling through this setup (and struggling all the way), I think I’ve finally gotten to the point where I’m ready to create the

Re: [ClusterLabs] Resource Agent ocf:heartbeat:iSCSILogicalUnit

t; <arvidj...@gmail.com> wrote: 22.07.2016 18:29, Jason A Ramsey пишет: > From the command line parameters for the pcs resource create or is it > something internal (not exposed to the user)? If the former, what > parameter? > http://www

Re: [ClusterLabs] Resource Agent ocf:heartbeat:iSCSILogicalUnit

t; <arvidj...@gmail.com> wrote: 22.07.2016 17:43, Jason A Ramsey пишет: > Additionally (and this is just a failing on my part), I’m > unclear as to where the resource agent is fed the value for > “${OCF_RESOURCE_INSTANCE}” given the limited number of parameters one

[ClusterLabs] Resource Agent ocf:heartbeat:iSCSILogicalUnit

I’m struggling to understand how to fully exploit the capabilities of targetcli using the Pacemaker resource agent for iSCSILogicalUnit. From this block of code: lio-t) # For lio, we first have to create a target device, then # add it to the Target Portal Group as an LU.

Re: [ClusterLabs] Setup problem: couldn't find command: tcm_node

; greatness is the path On 7/21/16, 10:31 AM, "Andrei Borzenkov" <arvidj...@gmail.com> wrote: On Thu, Jul 21, 2016 at 5:18 PM, Jason A Ramsey <ja...@eramsey.org> wrote: > Thanks for the response, but as I indicated in a previous response, lio-utils is depreca

Re: [ClusterLabs] Setup problem: couldn't find command: tcm_node

tcm_node is in a package called lio-utils. If it is SUSE, you can try to zypper in lio-utils. Thanks, BR Zhu Lingsan On 07/20/2016 11:08 PM, Jason A Ramsey wrote: > I have been struggling getting a HA iSCSI Target cluster in place for literally weeks. I c

Re: [ClusterLabs] Setup problem: couldn't find command: tcm_node

20.07.2016 18:08, Jason A Ramsey пишет: > I have been struggling getting a HA iSCSI Target cluster in place for literally weeks. I cannot, for whatever reason, get pacemaker to create an iSCSILogicalUnit resource. The error message that I’m seeing leads me to believe that I’

[ClusterLabs] Setup problem: couldn't find command: tcm_node

I have been struggling getting a HA iSCSI Target cluster in place for literally weeks. I cannot, for whatever reason, get pacemaker to create an iSCSILogicalUnit resource. The error message that I’m seeing leads me to believe that I’m missing something on the systems (“tcm_node”). Here are my

Re: [ClusterLabs] HA iSCSITarget Using FileIO

-- [ jR ] M: +1 (703) 628-2621 @: ja...@eramsey.org<mailto:ja...@eramsey.org> there is no path to greatness; greatness is the path From: Jason Ramsey <ja...@eramsey.org> Reply-To: Cluster Labs - All topics related to open-source clustering welcomed <users@clusterlabs.o

[ClusterLabs] HA iSCSITarget Using FileIO

I’m having some difficulty setting up a PCS/Corosync HA iSCSI target. I’m able to create the iSCSI target resource (it spins up the target service properly when the pcs command is issued. However, when I attempt to create a LUN, I get nothing but error messages. This works: pcs resource create

Re: [ClusterLabs] HA iSCSI Target on Amazon Web Services (Multi-AZ)

Anyone have any clues on this? I’m rather a stumped person at present. Thank you! -- [ jR ] there is no path to greatness; greatness is the path From: Jason Ramsey <ja...@eramsey.org> Reply-To: Cluster Labs - All topics related to open-source clustering welcomed <users@cluste

[ClusterLabs] HA iSCSI Target on Amazon Web Services (Multi-AZ)

So, I've been struggling for about 2 weeks to cobble together the bits and bobs required to create a highly available iSCSI Target cluster in AWS. I have a Pacemaker/Corosync cluster in place using DRBD for block-level replication of the EBS volumes used as target storage between the nodes.