Yo,
As part of putting together my answer to Arnau, I looked at our own dynamic scheduler (remind me to tell you about Templon's Law next time I see you) and found that we are not publishing any FQAN-based VOViews at all right now. Which was to me a surprise, my guess is that something changed in the bowels of YAIM so that our local work-around-the-standard-yaimology-for-groups-and-roles script no longer works. Anyway, nobody at all complained, our conclusion from this was that nobody (no users) care about what is in the VOViews. As long as the ACBRs are ok ... which they are.
JT
On Feb 15, 2012, at 10:44 , Stephen Burke wrote:
> LHC Computer Grid - Rollout [mailto:[log in to unmask]]
>> On Behalf Of Jeff Templon said:
>> If "VO:atlas" appears in the static LDIF file, and "atlas" is the name
>> of a unix group, then some lines about atlas should be printed by the
>> dynamic scheduler program. I *think* that if /atlas is listed in the
>> static LDIF file, but not "VO:atlas", that it also by default prints
>> for /atlas. But maybe not.
>
> In the past pic had a problem with publishing whole-VO FQANs, i.e. things like VOMS:/atlas, which led to this request for yaim to flag a warning:
>
> https://savannah.cern.ch/bugs/?func=detailitem&item_id=54755
>
> At a quick look it does now have the normal VO:atlas etc, plus FQANs for a load of roles and groups which looks a bit strange - and it hence has lots of VOViews including DENY rules. Is there a good reason for configuring it like that?
>
> Stephen
|