On 2 July 2010 14:57, Ewan MacMahon <[log in to unmask]> wrote:
>> -----Original Message-----
>> From: GRIDPP2: Deployment and support of SRM and local storage
>>
>> Then there is the question if we want something in weeks rather than
>> months we have to have 2 schema changes rather than one (the other
>> being when quotas is introduced).
>>
> Which of user banning and fast drain needs a schema change, and why?
>
User banning will need a schema change.
Originally, it was planned to make this schema change at the same time
as the schema change for quotas, but if people wanted user banning
"early", this would add one to the schema changes needed.
AFAIK, the change is simply to extend the current dpns user table with
a column for "is the dn mapped to this banned" or similar.
Incidentally, re: ARGUS - any "early" user banning implementation
would be a by-hand administered system. The originally planned
user-banning system would, instead, be integrated into ARGUS support
as you desire.
So, the choice is really:
fast dpm-drain (and ARGUS-integrated user banning with a single schema
change later)
manual user banning (and fast dpm-drain later)
Sam
> Ewan
>
|