From: Christine Caulfield <ccaulfie@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH] STABLE3: enhance cman_tool to validate and distribute configuration files
Date: Mon, 28 Sep 2009 15:40:34 +0100 [thread overview]
Message-ID: <4AC0CAE2.1020508@redhat.com> (raw)
In-Reply-To: <1253724532.2727.12.camel@daitarn-fedora.int.fabbione.net>
On 23/09/09 17:48, Fabio M. Di Nitto wrote:
> Hi Chrissie,
>
> On Wed, 2009-09-23 at 15:41 +0100, Christine Caulfield wrote:
>> This patch adds significant functionality to 'cman_tool version'. If -r0
>> is specified, then the configuration file is validated (using
>> ccs_config_validate), distributed around the cluster (if necessary,
>> using ccs_sync) and activated. This provides a single command to update
>> a configuration ... something people have been asking for for ages.
>
> wooooo
>
>>
>> I'm not 100% happy about bundling it into cman_tool version, but neither
>> am I convinced that this warrants another cman_tool sub-command ... so
>> if anyone has any better ideas please speak up.
>
> No more subcommands.. I think this is enough.
>
> The patch looks good but I think we need to add a few more details here
> and there...
>
> We agreed to have validation to work with 3 config options: off (-D),
> warning and fail hard. So I think -D could just take an option to
> none,warn,fail or something like that.
>
> I'd like to see an option to disable sync too. Even if we have ccs_sync,
> not everybody might be using conga/luci and can at least allow them to
> do it gently.
>
> I don't recall exactly why we needed to propagate COROSYNC_CONFIG_IFACE
> from cman_tool invokation. I am sure there was a very good reason for
> that. If so we might have to propagate also other COROSYNC_ envvars
> including LDAP bits.. because they will need to be available to
> ccs_config_validator and I'll also need to make the validator a bit less
> picky about overriding the environment if the environment is already
> loaded (this is my task of course).
Here's a revised patch that adds fail,warn & none to the -D switch and
also adds it to cman_tool join
Chrissie
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: validate.patch
URL: <http://listman.redhat.com/archives/cluster-devel/attachments/20090928/4473014a/attachment.ksh>
prev parent reply other threads:[~2009-09-28 14:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-23 14:41 [Cluster-devel] [PATCH] STABLE3: enhance cman_tool to validate and distribute configuration files Christine Caulfield
2009-09-23 16:48 ` Fabio M. Di Nitto
2009-09-24 9:05 ` Christine Caulfield
2009-09-24 17:18 ` Fabio M. Di Nitto
2009-09-28 14:40 ` Christine Caulfield [this message]
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=4AC0CAE2.1020508@redhat.com \
--to=ccaulfie@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).