From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Teigland Date: Tue, 23 Oct 2007 08:45:07 -0500 Subject: [Cluster-devel] spectator setting in cluster.conf In-Reply-To: <471D85B3.5020405@ubuntu.com> References: <20071022151200.GA26370@redhat.com> <471D85B3.5020405@ubuntu.com> Message-ID: <20071023134507.GA23832@redhat.com> List-Id: To: cluster-devel.redhat.com MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit On Tue, Oct 23, 2007 at 07:25:07AM +0200, Fabio Massimo Di Nitto wrote: > > > > > 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 . 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 . An explicit votes= setting for a node would override the 0 votes implied by . Dave