In case people don't follow Cyril's link below, you can adjust the scope of the downtime announcements you receive. Look at 'Downtime Notification' in the CIC Portal. You can limit it to one service from one site if you wish.
We need something similar for the core services too.
Now Cyril will tell me that it already exists:-)
John
> -----Original Message-----
> From: LHC Computer Grid - Rollout
> [mailto:[log in to unmask]] On Behalf Of Cyril L'Orphelin
> Sent: 08 May 2008 08:09
> To: [log in to unmask]
> Subject: Re: [LCG-ROLLOUT] GOC DB problem
>
> Hi al,
> I will try to explain some points :
> - for the normal broadcasts : targets are selected by user
> and it is under his responsibility to select the "good" values
> - for the downtime announcement : it is an automatic
> selection described in this document :
> http://cic.gridops.org/index.php?section=home&page=SDprocedure
>
> I will be really happy to find a solution to avoid "spaming"
> people but it is not so obvious .
> We need to inform some "mandatory" people and as soon as you
> are a site admin or a vo manager you belong to "mandatory" people !!!
> If you have any idea don't hesitate to contact CIC portal
> team at [log in to unmask] .
>
> NB : since one week we are not authorized to send any mail to
> CERN mailing lists via broadcast tool ( including roc
> manager mailing list) .
> I've opened a ticket and I'm waiting some solutions .
>
> Regards,
>
> --
> Cyril L'Orphelin
> Grid computing - EGEE/LCG team - CIC Portal Team
>
>
>
>
> Steve Traylen a écrit :
> > 2008/5/7 Burke, S (Stephen) <[log in to unmask]>:
> >
> >> LHC Computer Grid - Rollout
> >> > [mailto:[log in to unmask]] On Behalf Of
> Debreczeni Gergely
> >> said:
> >>
> >>
> >>> I hope you are joking ... you cannot 'advise; it to 500
> site admins...
> >>>
> >> > A correct solution on the other side is needed.
> >>
> >> One of the basic rules of grid computing is that a quick
> solution always
> >> beats a good solution :(
> >>
> >>
> >
> > Looking for suggestions there are various ideas floating around for
> > what can be one.
> >
> > 1) Junking the email and rely on people or things to
> subscribe to what
> > they are interested in
> > via RSS or whatever.
> > 2) Providing ICAL feeds of downtimes at some resolution.
> > 3) Batching up annouces in a daily report, containing.
> > a) Things happening today.
> > b) Things happening in the next week.
> > c) ....
> > The vast majority of items are not needed now,
> > the next morning would be fine.
> >
> > The above three are probably all useful.
> >
> >
> >
> >
> >
> >> > (you know: distributed, scalable, no SPF, etc.....)
> >>
> >> Apart from the GOCDB, R-GMA registry,
> freedom-of-choice(?), WMS, L&B,
> >> APEL, LFC, FTS, voms servers, ... (and any SE with unique
> data, and
> >> probably lots of VO-specific services)
> >>
> >> Stephen
> >>
> >>
> >
> >
> >
> >
>
|