On Nov 23, 2012, at 11:05 AM, Steve Jones wrote:
> Hi Chris,
>
>> For a whole host of reasons, it would be nice to just deploy the rpms
>> and config files, rather than rerunning yaim every time a package is
>> upgraded.
>
> We use both approaches. If the scope of the upgrade is very neat and
> clear, we just "do up" the changed bits. We surf the yaim scripts to find
> out what yaim would do if we ran it, then do by hand what yaim would have
> done.
>
> Else we just run yaim. Over time, I have come to know more about yaim, so
> we use it most of the time now.
>
>> I've had a quick look using installwatch - and get the following
>> (rather long) list of files that have been written to (or at least
>> touched) by yaim:
>
> Looking at your list: Taking out log files, rpmdb files, vomses and
> grid-security files, that leaves 6 conf files, 7 environment setting
> files, a couple of cron jobs and log rotate jobs, and the fetch-crl
> subsystem. If you look at it like that, it's not too bad.
>
> PS: re: grid security: VomsSnooper (which is now an RPM) can make your LSC
> files directly from the XML. It also has an (experimental!) feature to
> make the groups.conf file that yaim uses when setting up users.
>
For another method https://github.com/cernops/puppet-voms will create LSC
files if you are puppet inclined.
VomsSnopper scrapes form cic portal?
>
> Steve
|