glue-wg-bounces@ogf.org
[mailto:glue-wg-bounces@ogf.org] On Behalf Of owen.synge@desy.de said: In other words why does the Glue schema have a service entity which is mapped 1:1 with physical instance and not an VO-service entity?
As a minimum it saves publishing the same information many times over. Also some services are not VO-specific (e.g. BDII). Services do have the information on who is authorised to use them via the AccessPolicy, so there's nothing stopping you publishing separate services per VO, and indeed for most sites that's exactly what happens with the CE, i.e. there is one CE (queue) per VO - but it isn't very satisfactory because you end up with a huge number of queues. Also intrinsically a VO is just one level in a UserDomain hierarchy, you can have groupings of VOs (all WLCG VOs, all GridPP VOs) and subgroups within VOs. On a more abstract level you could say that the publishing should be aligned with who "owns" the information. Services are run by sites, not VOs, so it makes sense for a site to publish information about all the services it runs, including who is authorised to use them (which may change from time to time). Stephen