This would have been assigned to NGI ops management today after the holiday if Jeremy hadn't picked it up in the night.
> -----Original Message-----
> From: Testbed Support for GridPP member institutes [mailto:TB-
> [log in to unmask]] On Behalf Of Jeremy Coles
> Sent: 10 April 2012 01:19
> To: [log in to unmask]
> Subject: Re: Ticket Summary for 10/4/2012 Ops meeting
>
> It was not assigned to the site yet but it should have been so the
> explanation can be added first hand. I can not find an NGI notifier for
> this ticket (or the performance tickets for March) and will look into
> that; in the meantime I've added Stuart's explanation and closed the
> ticket.
>
> Jeremy
>
>
>
>
> On 9 Apr 2012, at 23:54, Stuart Purdie wrote:
>
> > On 9 Apr 2012, at 23:11, Matt Doidge wrote:
> >
> >> GLASGOW
> >> https://ggus.eu/ws/ticket_info.php?ticket=80960
> >> The Availability/Reliability query for March. A gentle(ish) reminder
> >> that this needs to be done this week.
> >
> > Ah - strictly, this is _not_ a ticket against Glasgow.
> >
> > It is a ticket _about_ glasgow, but it's to the NGI. (That's why
> we've not spotted it on our reviews). This is the normal procedure for
> poor performing sites - COD ask NGI, on the grounds that in many case
> of poor site performance, the site itself is not in a position to
> respond. More importantly, the primary purpose of COD asking the NGI
> is to ensure that the NGI is aware of the case.
> >
> > In this instance, the root cause was extended downtime for
> replacement of our network and installation of new equipment. It is
> not expected to continue or repeat, and the benefits of the work should
> become apparent over the next month.
|