I have updated the Use Case document with all the comments that I have received. http://forge.gridforum.org/sf/go/doc14621 The Glossary and Reference still needs to be done but I will do that when the document is finalized. Laurence
Hi Laurence, I'll get back to you shortly with the usecases endorsed by the NGS, and any other feedback I receive. Usecase 5.4 Service Downtime. Is this a functional requirement for downtime information to be made available directly from resources, i.e. not via a separate component such as the GOCDB? Matt -----Original Message----- From: glue-wg-bounces@ogf.org [mailto:glue-wg-bounces@ogf.org] On Behalf Of Laurence Sent: 18 January 2008 15:03 To: glue-wg@ogf.org Subject: [glue-wg] Updated Use Case Document I have updated the Use Case document with all the comments that I have received. http://forge.gridforum.org/sf/go/doc14621 The Glossary and Reference still needs to be done but I will do that when the document is finalized. Laurence _______________________________________________ glue-wg mailing list glue-wg@ogf.org http://www.ogf.org/mailman/listinfo/glue-wg
glue-wg-bounces@ogf.org
[mailto:glue-wg-bounces@ogf.org] On Behalf Of Viljoen, MJ (Matthew) said: Usecase 5.4 Service Downtime. Is this a functional requirement for downtime information to be made available directly from resources, i.e. not via a separate component such as the GOCDB?
Glue per se doesn't have any requirements on what people actually publish, or where the information comes from. However, it may have some implications for how the schema implementations are defined. When we discussed this my comment was that EGEE/LCG probably wouldn't publish this at all, because as you say we use the GOCDB. However, if we ever did publish it it would probably be done by having a single publisher on the GOCDB rather than having each resource publish their own downtimes, and we should therefore ensure that the information structure is free-standing, linked by the service ID, rather than being embedded in the service information. Of course that doesn't preclude services from publishing their own downtimes if that's more convenient. Stephen
participants (3)
-
Burke, S (Stephen) -
Laurence -
Viljoen, MJ (Matthew)