Hi John/Alessandra
I completely agree with your replies. The ROC is supposed to summarise
the issues of sites and reduce the repetitive nature of some aspects -
like raising tickets for the same problem - and escalate. I passed on
the request since it was directed at all ROCs, but I think the intention
was to see if this really a wider problem (I think it is already
demonstrated) by invoking a response from additional sites/ROCs. Often
problems are reported from the UKI region, no other ROC/site comments at
the ops meeting and then a few months later the problem comes back again
driven by another region.
I'll ask for clarification.
Jeremy
-----Original Message-----
From: Testbed Support for GridPP member institutes
[mailto:[log in to unmask]] On Behalf Of John Walsh
Sent: 01 December 2008 16:01
To: [log in to unmask]
Subject: Re: Please raise ticket if your site experiences a problem with
biomed
Hi Jeremy,
Why are more GGUS tickets required? The problem was reported initially
to GGUS
(by Glasgow?) and then also discussed via TB-SUPPORT. It was clear from
the
discussion that this was not just a single site problem.
Since you raised this as a problem seen in UK/I today at the Ops
meeting, then it should
have been accepted as an EGEE-wide problem. Indeed, a ticket was raised
by one of
the Greek sites about this, see:
https://gus.fzk.de/ws/ticket_info.php?ticket=44044&from=search
The number of tickets should not be an indication of the severity of a
problem. It also
replicates the amount of work that the COD must do in handling these
individual tickets
as they may need to find "related tickets" and associate them as such.
Many of us did not submit tickets as it was already reported. Can we may
add a comment
to the original ticket voicing that our site was also affected?
cheers,
j.
--
Scanned by iCritical.
|