cluster-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: David Teigland <teigland@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] spectator setting in cluster.conf
Date: Tue, 23 Oct 2007 08:45:07 -0500	[thread overview]
Message-ID: <20071023134507.GA23832@redhat.com> (raw)
In-Reply-To: <471D85B3.5020405@ubuntu.com>

On Tue, Oct 23, 2007 at 07:25:07AM +0200, Fabio Massimo Di Nitto wrote:
> <clusternode name="node1" nodeid="1" votes="1">
>  <spectator/>
> </clusternode>
> 
> seems to be the sanest one and the query would look like:

agree

> I have a test patch for it if the assumption is that:
> 
> - spectator is more important than votes (spectator will override votes
> settings)
> - spectator setting cannot be changed by anything other than the cluster.conf
> (read below)

great

> > In each case, the existence of the lower-level setting would override the
> > effect of the abstract spectator setting.
> 
> What kind of lower-level settings are you thinking about? env vars?

A "ro" or "rw" (or "nospectator"?) option in /etc/fstab would override the
addition of "spectator" to the mount options implied by <spectator/>.

We'd add a variable to /etc/sysconfig/cman that would tell the init script
to run fence_tool join.  If this was set, it would override the skipping
of that step implied by <spectator/>.

An explicit votes= setting for a node would override the 0 votes implied
by <spectator/>.

Dave



  reply	other threads:[~2007-10-23 13:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-22 15:12 [Cluster-devel] spectator setting in cluster.conf David Teigland
2007-10-23  5:25 ` Fabio Massimo Di Nitto
2007-10-23 13:45   ` David Teigland [this message]
2007-10-23 16:58     ` Fabio Massimo Di Nitto
2007-10-23 18:15       ` David Teigland
2007-10-23 21:07         ` Fabio Massimo Di Nitto
2007-10-24  3:37     ` Fabio Massimo Di Nitto
2007-10-24  6:36       ` Fabio Massimo 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=20071023134507.GA23832@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).