Hi Alessandra,
On 19/01/2012 11:09, "Alessandra Forti" <[log in to unmask]> wrote:
>> If every service had a list of configuration files and a list of
>>possible
>> entries in those files, I'd be a much happier bunny.
>
>indeed you can do that with YAIM. There is an
>/opt/glite/yaim/examples/services directory you can use. Even before
>that I had split site-info.def at service level and just source them
>where needed.
That's the YAIM configuration files and I am aware of that, what I want is
that, for example, the glite-ce-cream rpm includes a (fully annotated)
/etc/glite-ce-cream/cream-config.xml file. That's probably not a good
example because at least the EMI cream CE comes with a
cream-comfig.xml.template file, though it isn't annotated and I agree with
whoever it was that said that "XML is file format that is neither easily
human or machine readable." it is at least something.
There seems to be an feeling from the developers that grid services are
especially complex and they need to protect us poor sysadmins from that
complexity, we're not end users we are used to deploying complex systems.
YAIM is a great starting point and I don't want to see it go away but
quite rightly it's not going to support all the possible setups of a grid
site, but it certainly appears to me to be used by the developers as an
excuse to not do proper packaging. YAIMing a node after an update should
be a rare exception when they are introducing major new functionality not
the norm is seems to be now to fix file permissions that really should be
done in the rpm and replacing config files that got needlessly removed by
the upgrade.
Just my 2p worth, I don't expect any of this to get fixed.
Yours,
Chris.
|