> -----Original Message-----
> From: Testbed Support for GridPP member institutes [mailto:TB-
> [log in to unmask]] On Behalf Of David Meredith
> Sent: 16 January 2013 15:37
>
> If you mean Service Groups in GOCDB, then these are explained in the user
> docs at:
> https://wiki.egi.eu/wiki/GOCDB/Input_System_User_Documentation#Service_Groups
>
Thanks, that's rather useful. In short, that says that:
A service group is an arbitrary grouping of existing service endpoints
that can be distributed across different physical sites (previously
known as 'Virtual Sites'):
- Each service endpoint that appears in a group must already be a member
of one hosting physical site (a service group cannot own its own services).
- A service group role does not extend any permissions over its child services.
This means that you cannot declare a downtime on the services that you group
together or modify the service attributes.
- Currently, any GOCDB user can create their own service groups (everything is
logged, including who created the service group). Service groups are typically
used for monitoring a particular collection of services using the GOCDB
get_service_group PI method.
Which sounds pretty much ideal for this, unless we have any particular reason
to want to avoid associating services with their hosting sites, which I don't
think we do (do we?).
And we could probably use the gridpp-ops list as the contact address, and we're
done.
No doom.
Ewan
|