Hi Stephen,
On 30/07/2012 11:22, Stephen Jones wrote:
> Hi all, I need some help.
>
> I'm looking at parts of the system that have been "swept
> under the carpet", so to speak. The first thing I looked at
> was documentation on the GridPP wiki about the "GridPP
> Approved VOs". There is a process now to keep it up to
> date (with a tool called "VomsSnooper").
>
> Anyway, the point of this message is this: while finding
> a way to keep the "GridPP Approved VOs" synchronized to
> the CIC Portal, it came out that several pieces of odd VO data
> were not disseminated via the CIC Portal.
>
> The fields like this that I know about are:
>
> VO_VONAME_SW_DIR=blah blah blah
> VO_VONAME_DEFAULT_SE=blah blah blah
> VO_VONAME_RBS=blah blah blah
> VO_VONAME_STORAGE_DIR=blah blah blah
> VO_VONAME_VOMS_EXTRA_MAPS=blah blah blah
> VO_VONAME_VOMS_POOL_PATH=blah blah blah
> VO_VONAME_SGM=blah blah blah
> VO_VONAME_USERS=blah blah blah
>
The RBS has been replaced by the WMS 5 years ago. I think SGM, USERS,
VOMS_EXTRA_MAPS and VOMS_POOL_PATH are also all obsolete.
SW_DIR, DEFAULT_SE, STORAGE_DIR are site specific and therefore should
not be decided by the VO.
cheers
alessandra
There may be others. As far as I know, these variables are not
> derived form the CIC portal. This then begs the question: how
> is this information disseminated? (It would also be good to know
> what it's for!)
>
> If you have any knowledge about this, I'd be grateful if you could
> discuss it here.
>
> BTW: The VO_VONAME_SW_DIR almost always points to some
> standard mount point, appended with the name of the VO. Only
> VOs that use CVMFS break that convention.
>
> I need similar rules, sources or conventions for all the variables.
> Can anyone throw any light on this?
>
> Cheers,
>
>
> Steve
>
>
--
Facts aren't facts if they come from the wrong people. (Paul Krugman)
|