From mboxrd@z Thu Jan  1 00:00:00 1970
From: David Teigland <teigland@redhat.com>
Date: Wed, 9 Sep 2009 13:09:10 -0500
Subject: [Cluster-devel] ccs_config_dump / ccs_config_validate
In-Reply-To: <1252517093.16393.116.camel@cerberus.int.fabbione.net>
References: <1252086256.6387.25.camel@cerberus.int.fabbione.net>
	<20090904180612.GB26463@redhat.com>
	<1252131148.6387.30.camel@cerberus.int.fabbione.net>
	<4AA4AB5E.5090300@redhat.com> <20090908160121.GA11641@redhat.com>
	<1252428569.16393.11.camel@cerberus.int.fabbione.net>
	<20090908183451.GB11641@redhat.com>
	<1252443046.16393.34.camel@cerberus.int.fabbione.net>
	<20090909154248.GA9771@redhat.com>
	<1252517093.16393.116.camel@cerberus.int.fabbione.net>
Message-ID: <20090909180910.GB9771@redhat.com>
List-Id: <cluster-devel.redhat.com>
To: cluster-devel.redhat.com
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit

On Wed, Sep 09, 2009 at 07:24:53PM +0200, Fabio M. Di Nitto wrote:
> The other problem is that we don't want to special case too much on the
> command line because it means keeping the tool constantly up to date
> with all possible loaders and custom loaders that users could/might
> write.

Hm, ok, I'm not sure how to respond to alternate universes arguments in this
context :-)

> The whole point of reading the configuration from sysconfig/cman is that
> once the user sets it to a custom loader, ccs_config_validate picks it
> up automatically without effort that would otherwise require both coding
> on our side and extra parameters from the user to validate.

Yes, I understand the point of sysconfig/cman.  If it were me, everything
everywhere would assume /etc/cluster/cluster.conf, the code would be simpler
and more robust, the tools likewise, and 99.9% of users would be very happy.
To the .1%, sorry.

That puts us at opposite ends of the spectrum, and I suspect the ccs tools are
now somewhere in the middle, so I'm fine with them.

Dave