do we apply similar rule for other sites which are mainly atlas sites?
I mean if site has nearly 100% availability for atlas and has problem with ops test should the site availability be determined by atlas?
Elena
On 21 Feb 2012, at 12:05, Sam Skipsey wrote:
>
>
> On 21 February 2012 11:45, Stephen Burke <[log in to unmask]> wrote:
> Testbed Support for GridPP member institutes [mailto:TB-
> > [log in to unmask]] On Behalf Of John Gordon said:
> > If this has been a long-standing DPM issue then I will ask to have this
> > test (SRMput ?) removed from the SRMV2 set of tests so that it isn't
> > included in availability.
>
> Even if there really was no free space for ops, does that make the SE unavailable? Any VO may fill up its space, that doesn't mean the site is broken. Probably the intention is that the test is just supposed to verify the functionality and no-one has considered the possibility of it being full. (CE tests are similar if the queues are full - there I think most sites do have an explicit reservation just to let the ops tests run.)
>
>
> This is a valid point, and what I was getting at with my nagios test comment: the test doesn't test if the storage is available, it tests if ops can write to the storage. (Now, obviously, there's a point at which you have to consider that a test has to test *something*...). ATLAS, meanwhile, can happily write to the storage; and even ops tests are happy talking to the storage, and it is responding in a reasonable and sane way.
>
> I note that Manchester is an almost entirely ATLAS site. It seems reasonable that their availability be determined by their being available for the entities that they are supposed to be supporting in the main, surely?
>
> Sam
>
> Stephen
>
__________________________________________________
Dr Elena Korolkova
Email: [log in to unmask]
Tel.: +44 (0)114 2223553
Fax: +44 (0)114 2223555
Department of Physics and Astronomy
University of Sheffield
Sheffield, S3 7RH, United Kingdom
|