All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Teigland <teigland@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] unfencing
Date: Mon, 23 Feb 2009 13:27:02 -0600	[thread overview]
Message-ID: <20090223192702.GE12791@redhat.com> (raw)
In-Reply-To: <20090223192226.GA14849@redhat.com>

On Mon, Feb 23, 2009 at 01:22:26PM -0600, Ryan O'Hara wrote:
> On Mon, Feb 23, 2009 at 01:09:58PM -0600, David Teigland wrote:
> > On Mon, Feb 23, 2009 at 07:52:55PM +0100, Fabio M. Di Nitto wrote:
> > > > A node unfences *itself* when it boots up.  As such, power-unfencing doesn't
> > > > make sense; unfencing is only meant to reverse storage fencing.
> > > 
> > > What can stop a user to run fence_node -U from another node to do remote
> > > (un)fencing?
> > 
> > It would work.  Users can do anything they like, that's beside the point.
> > 
> > The point is to make storage fencing more practical by automating storage
> > unfencing.  Otherwise, users have to invent ad hoc methods of doing it
> > themselves, often manually.  And, we end up solving the problem in painful,
> > one-off cases like scsi_reserve/fence_scsi, which cry out for a better
> > approach.
> 
> I was going to ask about this. From the sounds of it, we could
> elimiate the need for scsi_reserve completly. At least I can't think
> of any reason that it could not me eliminated at this point.

Yep, that's the idea.



  reply	other threads:[~2009-02-23 19:27 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-20 21:44 [Cluster-devel] unfencing David Teigland
2009-02-23  6:27 ` Fabio M. Di Nitto
2009-02-23 18:15   ` David Teigland
2009-02-23 18:31     ` Fabio M. Di Nitto
2009-02-23 18:40       ` David Teigland
2009-02-23 18:52         ` Fabio M. Di Nitto
2009-02-23 19:09           ` David Teigland
2009-02-23 19:22             ` Ryan O'Hara
2009-02-23 19:27               ` David Teigland [this message]
2009-02-23 20:24             ` Ryan O'Hara
2009-02-23 20:28               ` David Teigland
2009-02-26  6:51             ` Fabio M. Di Nitto
2009-02-26 14:33               ` David Teigland
2009-02-26 18:06                 ` [Cluster-devel] unfencing (cman startup) Fabio M. Di Nitto
2009-02-27 12:54                   ` Chrissie Caulfield
2009-02-27 15:52                     ` David Teigland
2009-02-27 16:27                       ` Chrissie Caulfield
2009-02-27 17:46                       ` Fabio M. Di Nitto
2009-03-02  7:59                         ` Chrissie Caulfield
2009-02-23 19:36 ` [Cluster-devel] unfencing Ryan O'Hara
2009-02-23 19:44   ` David Teigland
2009-02-26 21:35 ` David Teigland
2009-02-27  7:04   ` Fabio M. Di Nitto

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=20090223192702.GE12791@redhat.com \
    --to=teigland@redhat.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.