John/All
My request was to follow the current procedure as I defined it in an
email earlier. Certainly if there is a better (automated) procedure we
should pursue it but that will take time. The conclusion is that for now
we have to go with the proposal (unless there is a significant reason to
oppose it - if there is a significant reason then we need to go back
with an alternative solution that can be implemented now).
Jeremy
-----Original Message-----
From: Testbed Support for GridPP member institutes
[mailto:[log in to unmask]] On Behalf Of Gordon, JC (John)
Sent: 11 October 2005 15:20
To: [log in to unmask]
Subject: Re: Procedure for scheduling downtime - applies to all sites!
Possible in theory but one more item on the long list of requested GOCDB
developments. I don't know if the CIC Portal method has an API that
GOCDB could use.
Can we follow this proposal for now?
John
> -----Original Message-----
> From: Testbed Support for GridPP member institutes
> [mailto:[log in to unmask]] On Behalf Of Coles, J (Jeremy)
> Sent: 11 October 2005 13:09
> To: [log in to unmask]
> Subject: Re: Procedure for scheduling downtime - applies to all sites!
>
> Hi Andrew
>
> Yes - I thought about this while writing the message earlier.
> I'll find
> out. It will work providing advance notice is not required before the
> GOCDB entry is placed.
>
> Jeremy
>
> -----Original Message-----
> From: Andrew Beresford [mailto:[log in to unmask]]
> Sent: 11 October 2005 12:09
> To: Coles, J (Jeremy)
> Cc: Testbed Support for GridPP member institutes
> Subject: Re: Procedure for scheduling downtime - applies to all sites!
>
> On Tue, 2005-10-11 at 11:00 +0100, Coles, J (Jeremy) wrote:
> > 2- Assuming no requests to delay downtime (in practice sites may not
> > wait to enter information in GOCDB, but will reschedule (if
> possible)
> if
> > a VO responds indicating that access is required at the
> proposed time)
> -
> > update GOCDB with details of scheduled downtime. Deselect monitoring
> for
> > the affected nodes.
>
> If this is the case, why doesn't GOCDB send the message out to all VO
> managers automatically? That saves us doing anything differently from
> what we do now and VO managers get the information they want.
> Win-win :)
>
> Cheers,
>
> Andrew
>
|