On 09/12/2016 04:33 PM, Gareth Roy wrote:
> If I understand this correctly, then I’m a little concerned with this approach as it adds rather than removes something the site has to do. If any VOMS information is updated, we now need to:
>
> 1) Yum –y update
> 2) Locally Run the script to generate a new set of information
No. The script in my prototype just runs on install, as part of the RPM
post-script, or something like that.
But I agree about the life-cycle benefits. I would have to put in an
uninstall script, which is daft.
So I'll put the files directly in the rpm, as you suggest, which is
easier. I'll also deliver the XML snippet so you can adapt the RPM to
other baselines that do not use vomsdir/vomses, or which put them in
another place. That's the best way.
> An additional thought is the Perl XML SAX parser part of the default Perl install
I think it is. Or was on my system. But we won't use it. I'll bury the
files in the rpm, as you suggest, mainly for the life-cycle benefit. I
like the idea of giving the data out in an independent XML format - new
services could read that directly, and not use these derived files, as
they are pointless. So we'll do both.
Cheers,
Ste
--
Steve Jones [log in to unmask]
Grid System Administrator office: 220
High Energy Physics Division tel (int): 43396
Oliver Lodge Laboratory tel (ext): +44 (0)151 794 3396
University of Liverpool http://www.liv.ac.uk/physics/hep/
|