Offline Fileserver

For users who demand additional storage space for analysis, so called XXL volumes of size up to 30GB per user can be provided. The Offline Fileserver is setup in AFS and can be found in AFS underneath the toplevel path /afs/desy.de/group/hasylab/pool. In general it can be accessed by DESY Photon Science staff (i.e. with accounts belonging to the AFS group 'hasylab' - Beamtime accounts fs****** are NOT member of this group). Below the path given above, the data is organized in different subdirectories for different purposes. The brief structure is as follows:

.1 /afs/desy.de/group/hasylab/pool. .2 group. .3 $<$ProjectName$>$. .2 public. .3 p3seismo. .2 temp. .3 $<$SomeName$>$. .2 usr. .3 $<$Username1$>$. .3 $<$Username2$>$.
Inside the folder 'usr' one can find user specific XXL folders. They are available on request to FS-EC and by default, they have a quota of 30GB and volume permissions are set similar to a users home directory.

The folder 'public' contains folders/data which can be read by entire Photon Science staff. It shares common data or might be used to provide information having small file sizes. In particular it offers the subdirectory p3seismo which provides regularly updated data deduced from the seismometers at PETRA III which can be accessed by the TANGO seismometer server.
User accounts having the group membership 'hasylab' is granted write permission to the public folder and read permission to folder p3seismo.

The folder 'group' contains project related storage space, i.e. a single folder is dedicated to a specific project. Such storage has a quota of 100GB and can be requested by a project responsible via FS-EC. The project responsible will be granted access rights similar to a users home directory and has to maintain ACLs by her-/his self.

The folder 'temp' can be used as (short term) temporary storage space for Photon Science staff. Users may store amounts of data in here which overcome their quota limit in their home/XXL folder for analysis purposes. This temp folder does not have any backup mechanism nor does it provide specific security measures concerning data access. Users are recommended to create a subdirectory for her-/his self in here and not to store data directly inside the temp folder itself. Moreover they are admonished to delete the data as soon as possible.

To be discussed / Notes here:

* Shall users have write permission to temp by default? Then usg:hasylab write
would imply that they can create/delete data among themself (?)

* I wanted to set a quota of 4TB or 6TB for temp which is not possible (not even
  with the newer AFS version which was supposed to do so)
  => currently no quota set

* Do we want to delete this folder automatically, i.e. once a moth or so

* Do we want to limit XXL volumes to DESY staff? By now? in common?

* Volumes are created via UCO or afs.service by request FSEC-IT

* Quotas can be changed via UCO or afs.service  by request FSEC-IT, in future
  hopefully via 'Delegationstool' by FSEC-IT

* Default rights? We can define as long as in agreement with RSR-Statements

## Note AR:
##  according http://rechnersicherheit.desy.de/e8/e84/e93/index_ger.html
##  for AFS
##  AFS: Zugriffsrechte für Verzeichnisse und Dateien
##
##  RSR Statement 1999/6
##
##  <SNIP>
##  Directory     Who     Rights
##   ~/*          User    lrwidka
##                Admin   lrwidka
##         system:anyuser
##                Others  as needed
##
##  ==> * whoever reqests/gets storage space is considered as User with ACL 'all'
##        for the specific mount point (and subdirs) 
##      * system:administrators -> all
##      * usg:fsec-it -> all
##      * additional groups or desy-accounts get read (or write), if needed and
##        known in advance/neddeed
##      * the User takes care on further right management according to rules
##        and recommendations given by RSR (Rechnersicherheitsrat)