Hi Stephen
I see your point - poor wording. They will get the same time, and if
there are currently VOs enabled with 72hr wallclock limits then this
sets the maximum. If sites are moving this to 48hrs then 48hrs becomes
our reference point. But, we want the reference point the same across
sites to allow responsiveness (and actions taken) across sites to be
measured in a consistent way. My wording of "to give sites more time"
was also out of context as it is not possible for them to complete some
of the required tasks on too short a time scale. I'd rather have a
fuller discussion AFTER the security challenges otherwise we undermine
the whole point in running them!
Jeremy
-----Original Message-----
From: Testbed Support for GridPP member institutes
[mailto:[log in to unmask]] On Behalf Of Burke, S (Stephen)
Sent: 19 October 2008 16:16
To: [log in to unmask]
Subject: Re: Enabling the gridpp VO (and providing a 72hr queue)
Testbed Support for GridPP member institutes
> [mailto:[log in to unmask]] On Behalf Of Coles, J (Jeremy)
said:
> principal reason at the moment is to give sites more time to
> react under
> future security service challenges that we will run under the VO.
Err, why should sites get longer in a security challenge than they would
in a real incident?
Stephen
--
Scanned by iCritical for STFC.
--
Scanned by iCritical for STFC.
|