Yo Jeff,
> I sounds like I should instruct lcg-info-dynamic-scheduler to do the right thing with this syntax; however we should also clarify what people can put into groups.conf and what YAIM can put into the dynamic-scheduler conf file.
>
> I have seen things like this:
>
> voname:group
> /voname:group
> /voname/*:group
>
> This is an overspecification and dealing with it in l-i-d-s means I have to choose some interpretation for the above, it is ambiguous.
In /opt/glite/yaim/examples/groups.conf.README there are these examples:
"/my-VO/ROLE=lcgadmin":::sgm:
"/my-VO/ROLE=production":::prd:
"/my-VO/foobar/ROLE=admin":::foobar_admin:
"/my-VO/foobar/*":::foobar_group:
"/my-VO/foobar":::foobar_group:
"/my-VO/*"::::
"/my-VO"::::
The idea is that a few special cases need to be dealt with explicitly
and wildcards are used where it is impractical to capture all the FQANs
that might be present in a proxy of a supported VO.
In particular, the penultimate line says: map any other subgroups or
roles the same way as default proxies for the VO (the last line).
The lcg-info-dynamic-scheduler configuration just needs to be compatible
with these notions, it does not need to have 1 line for every line that
appears in groups.conf.
Maybe a small change in config_gip_scheduler_plugin() would be enough
to avoid unnecessary complications in the configuration or in the code
of lcg-info-dynamic-scheduler?
|