-
Notifications
You must be signed in to change notification settings - Fork 3
Strategy for managing groups
samuell edited this page Dec 29, 2011
·
1 revision
- Projects as groups and collections (one group and one collection per project)
- Zones can't be used since one can only have one local zone configured. Also creating a new zone per project becomes impractical.
- One resource group per project does not create enough boundaries in terms of access rights. It is then possible for anyone to write to another resource group, possibly using all that project's quota.
- New policy for UPPNEX projects. Only one project per research project.
- Multiple data deliveries per UPPNEX project (sllu_001, slls_001 etc)
- irods/in and irods/out folders in each proj folder on Panasas, being symlinks to a special iRODS volume with separate folders for each collection/group.
- Cron script to automatically set the access rights of those folders to rwxrwx--- and owner to [irods_user]:[uppnex_projid]