Hi Florian,
Dejan told me that you're the maintainer for the iSCSI pieces, so I'm
sending you this patch.
Please apply, thank you very much!
Regards,
Phil
--
: Ing. Philipp Marek
: LINBIT | Your Way to High Availability
: DRBD/HA support and consulting
On 10/06/2012 08:45 AM, Kevin F. La Barre wrote:
I'm trying to get the fence_ec2 agent (link below) working and a bit
confused on how it should be configured. I have modified the agent with
the EC2 key and cert, region, etc. The part of confused about is the
port argument and how it's
El 28/09/2012 20:42, Nicolás escribió:
Hi all!
I'm new to this list, I've been looking to get some info about this but
I haven't seen anything, so I'm trying this way.
I've successfully configured a 2-node cluster with DRBD + Heartbeat +
Pacemaker. It works as expected.
The problem comes
On 10/08/2012 09:42 PM, Nicolás wrote:
El 28/09/2012 20:42, Nicolás escribió:
Hi all!
I'm new to this list, I've been looking to get some info about this but
I haven't seen anything, so I'm trying this way.
I've successfully configured a 2-node cluster with DRBD + Heartbeat +
Pacemaker. It
Thank you Andreas, your input does further my understanding of how this is
supposed to work; however, I'm still unclear about your statement where
the nodenames are sent as port parameter. Specifically, how is the port
parameter passed from Pacemaker to the fencing script? Should port be
On 10/08/2012 10:44 PM, Kevin F. La Barre wrote:
Thank you Andreas, your input does further my understanding of how this is
supposed to work; however, I'm still unclear about your statement where
the nodenames are sent as port parameter. Specifically, how is the port
parameter passed from
Andreas,
Pacemaker also sends the cluster node name to fence to the stonith
agent, that is interpreted as port. I am sure you read the description
about how to use this agent and how it tries to find the correct EC2
instance name to fence, using the node name.
Yes, I read and believe I
