[Bodington-developers] Quotas Implementation

[Matthew B. <mat...@ou...>]

Request for Comment.

I'm currently looking at implementing basic quotas for Bodington as we 
are hoping to allow everyone in Bodington to be able to create their own 
resources and this needs some management.

It would be difficult to follow the traditional model of file system 
quotas where each file has a principal owner and quotas are placed on 
users. The reason being that Bodington doesn't have an idea of one owner 
and implementing this isn't trivial or maybe right.

The route I am probably going to take is allowing for a quota to be 
placed on a resource and it applies to all child resources unless a 
child has its own quota defined.

I am going to initially only allow quotas to be set on a resource at 
creation time although later on quotas should be able to be applied 
after creation.

Quotas will be able to be adjusted after they have been initially set.

Sysadmin will be exempt from quotas.

Quotas will apply to resources (eg you can create a total of 20 
resource) and uploaded files (eg you can only upload 5MB of files).

No hard/soft quotas in version 1 they may come at a later date.

To see the quotas you need manage permission. If you have create 
permission you can see the resource quota. If you have upload permission 
you can see the uploaded file quota.

Exceeding quota will throw a BuildingServerException subclass. Nice 
error handling will be done at most places.

-- 
  -- Matthew Buckett, VLE Developer
  -- Learning Technologies Group, Oxford University Computing Services
  -- Tel: +44 (0)1865 283660 http://www.oucs.ox.ac.uk/ltg/