All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Mahoney <jeffm@suse.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [RFC] Fencing harness for OCFS2
Date: Tue, 30 May 2006 15:42:36 -0400	[thread overview]
Message-ID: <447CA02C.30308@suse.com> (raw)
In-Reply-To: <20060530193848.GP17040@marowsky-bree.de>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Lars Marowsky-Bree wrote:
> On 2006-05-25T20:31:33, Daniel Phillips <phillips@google.com> wrote:
> 
>> Goals:
>>     - Lightweight, kernel based fencing harness
>>     - Support pluggable fencing methods
>>     - Pluggable methods take policy out of kernel
>>     - No reinvented wheels, use kernel modules
>>     - Also accomodate user space fencing methods
>>     - Divide work appropriately between kernel and user space
>>     - Obey memory deadlock prevention rules
>>     - Obey safe module unload rules
>>     - Handle multiple clusters per node
> 
> Sorry we're chiming in so late, but with Jeff's user-space membership
> patches, we have user-space driven fencing working with heartbeat 2.

It works, but the "Obey memory deadlock prevention rules" line item is
still an issue.

- -Jeff

- --
Jeff Mahoney
SUSE Labs
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org

iD8DBQFEfKAsLPWxlyuTD7IRAqZwAJ0egEKtPZcLcBe+mgikTXIOqIC+ngCeIMfg
SyhZFMnEmajfx2ekomzRygk=
=MuXE
-----END PGP SIGNATURE-----

  reply	other threads:[~2006-05-30 19:42 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-26  3:31 [Ocfs2-devel] [RFC] Fencing harness for OCFS2 Daniel Phillips
2006-05-30 19:38 ` Lars Marowsky-Bree
2006-05-30 19:42   ` Jeff Mahoney [this message]
2006-05-30 20:15     ` Daniel Phillips
2006-05-31  0:19       ` Lars Marowsky-Bree
2006-05-31 18:38         ` Daniel Phillips
2006-05-31 23:03           ` Lars Marowsky-Bree
2006-06-01  0:57             ` Daniel Phillips
2006-06-01 10:13               ` Lars Marowsky-Bree
2006-06-01 18:57                 ` Daniel Phillips
2006-05-30 19:45   ` Daniel Phillips

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=447CA02C.30308@suse.com \
    --to=jeffm@suse.com \
    --cc=ocfs2-devel@oss.oracle.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.