From: David Teigland <teigland@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] ccs_config_dump / ccs_config_validate
Date: Tue, 8 Sep 2009 11:01:21 -0500 [thread overview]
Message-ID: <20090908160121.GA11641@redhat.com> (raw)
In-Reply-To: <4AA4AB5E.5090300@redhat.com>
On Mon, Sep 07, 2009 at 07:42:38AM +0100, Christine Caulfield wrote:
> >- it can be confusing to users to see pipes and some shell magic
> >commands happening. After all we don't print all the calls we do
> >everywhere because the user doesn't really need to know all the internal
> >magic.
My whole point is that it's the plain "ccs_config_validate" that's confusing
to users, and printing more detail makes it *less* confusing!
> I agree. Just because it's a script that does the work doesn't mean it
> should automatically show its working. If the user wants to do that then
> there are -v or -x switches to the shell itself. If the whole operation
> was written in C you wouldn't get it to print its source code out before
> running ... would you ?
Setting aside absurdities :-), I'm not convinced either of you took enough
time to consider the real issue behind the unusual idea. Please try to forget
everything you know about ccs/confdb/xmlconfig/ldapconfig/cmanpreconfig and
put yourself the position of a user trying to debug/diagnose/understand what's
happening with their cluster. These tools are for them, not for cman_tool to
use, despite how they began.
My motivation is that a plain ccs_config_validate is a "magical" command; a
user has no clue what it's doing, which is the first key step in understanding
what to make of the result. As such, I think we should encourage the use of
explicit commands whenever possible, like:
ccs_config_validate --test-file /etc/cluster/cluster.conf
ccs_config_validate --test-load /etc/cluster/cluster.conf
Echoing one of those for a plain ccs_config_validate is probably not the best
way to communicate helpful info the user. So let's put some thought into
something *better* and less magical.
How about using -v (verbose) like,
ccs_config_validate --test-file new.conf
ok
ccs_config_validate -v --test-file new.conf
test file new.conf
ok
ccs_config_validate --test-file /etc/cluster/cluster.conf
ok
ccs_config_validate -v --test-file /etc/cluster/cluster.conf
test file /etc/cluster/cluster.conf
ok
ccs_config_validate --test-load /etc/cluster/cluster.conf
ok
ccs_config_validate -v --test-load /etc/cluster/cluster.conf
test load /etc/cluster/cluster.conf
ok
ccs_config_validate --test-load
ok
ccs_config_validate -v --test-load
test load /etc/cluster/cluster.conf
ok
ccs_config_validate
ok
ccs_config_validate -v
test load /etc/cluster/cluster.conf
ok
ccs_config_validate --test-load
ok
ccs_config_validate -v --test-load
test load ldap://...
ok
ccs_config_validate
ok
ccs_config_validate -v
test load ldap://...
ok
Dave
next prev parent reply other threads:[~2009-09-08 16:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-03 19:22 [Cluster-devel] ccs_config_dump / ccs_config_validate David Teigland
2009-09-04 6:16 ` Fabio M. Di Nitto
2009-09-04 15:37 ` David Teigland
2009-09-04 17:44 ` Fabio M. Di Nitto
2009-09-04 18:06 ` David Teigland
2009-09-05 6:12 ` Fabio M. Di Nitto
2009-09-07 6:42 ` Christine Caulfield
2009-09-08 16:01 ` David Teigland [this message]
2009-09-08 16:49 ` Fabio M. Di Nitto
2009-09-08 18:34 ` David Teigland
2009-09-08 20:47 ` Fabio M. Di Nitto
2009-09-08 20:50 ` Fabio M. Di Nitto
2009-09-09 15:42 ` David Teigland
2009-09-09 17:24 ` Fabio M. Di Nitto
2009-09-09 18:09 ` David Teigland
2009-09-09 18:37 ` Fabio M. Di Nitto
2009-09-10 8:22 ` Christine Caulfield
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=20090908160121.GA11641@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).