Workspace

Workspace tools provide temporary scratch space so calles workspaces for your calculation on a central file storage. They are meant to keep data for a limited time – but usually longer than the time of a single job run.

No Backup

Workspaces are not meant for permanent storage, hence data in workspaces is not backed up and may be lost in case of problems on the storage system. Please copy/move important results to $HOME or some disks outside the cluster.

Create workspace

To create a workspace you need to state name of your workspace and lifetime in days. A maximum value for lifetime and a maximum number of renewals is defined on each cluster. Execution of:

  $ ws_allocate blah 30

e.g. returns:

  Workspace created. Duration is 720 hours. 
  Further extensions available: 3
  /work/workspace/scratch/username-blah-0

For more information read the program's help, i.e. $ ws_allocate -h.

List all your workspaces

To list all your workspaces, execute:

  $ ws_list

which will return:

• Workspace ID
• Workspace location
• available extensions
• creation date and remaining time

Find workspace location

Workspace location/path can be prompted for any workspace ID using ws_find, in case of workspace blah:

  $ ws_find blah

returns the one-liner:

  /work/workspace/scratch/username-blah-0

Extend lifetime of your workspace

Any workspace's lifetime can be only extended a cluster-specific number of times. There several commands to extend workspace lifetime

1. $ ws_extend blah 40

   which extends workspace ID blah by 40 days from now,

2. $ ws_extend blah

   which extends workspace ID blah by the number days used previously

3. $ ws_allocate -x blah 40

   which extends workspace ID blah by 40 days from now.

Setting Permissions for Sharing Files

The examples will assume you want to change the directory in $DIR. If you want to share a workspace, DIR could be set with DIR=$(ws_find my_workspace)

Regular Unix Permissions

Making workspaces world readable/writable using standard unix access rights with chmod is only feasible if you are in a research group and you and your co-workers share a common ("bwXXXXX") unix group. It is strongly discouraged to make files readable or even writable to everyone or to large common groups.

Command	Action
chgrp -R bw16e001 "$DIR" chmod -R g+rX "$DIR"	Set group ownership and grant read access to group for files in workspace via unix rights to the group "bw16e001" (has to be re-done if files are added)
chgrp -R bw16e001 "$DIR" chmod -R g+rswX "$DIR"	Set group ownership and grant read/write access to group for files in workspace via unix rights (has to be re-done if files are added). Group will be inherited by new files, but rights for the group will have to be re-set with chmod for every new file

Options used:

• -R: recursive
• g+rwx
  • g: group
  • + add permissions (- to remove)
  • rwx: read, write, execute

"ACL"s: Access Crontrol Lists

ACLs allow a much more detailed distribution of permissions but are a bit more complicated and not visible in detail via "ls". They have the additional advantage that you can set a "default" ACL for a directory, (with a -d flag or a d: prefix) which will cause all newly created files to inherit the ACLs from the directory. Regular unix permissions only have limited support (only group ownership, not access rights) for this via the suid bit.

Best practices with respect to ACL usage:

1. Take into account that ACL take precedence over standard unix access rights
2. The owner of a workspace is responsible for its content and management

Please note that ls (List directory contents) shows ACLs on directories and files only when run as ls -l as in long format, as "plus" sign after the standard unix access rights.

Examples with regard to "my_workspace":

Command	Action
getfacl "$DIR"	List access rights on $DIR
setfacl -Rm u:fr_xy1:rX,d:u:fr_xy1:rX "$DIR"	Grant user "fr_xy1" read-only access to $DIR
setfacl -Rm u:fr_me0000:rwX,d:u:fr_me0000:rwX "$DIR" setfacl -Rm u:fr_xy1:rwX,d:u:fr_xy1:rwX "$DIR"	Grant your own user "fr_me0000" and "fr_xy1" inheritable read and write access to $DIR, so you can also read/write files put into the workspace by a coworker
setfacl -Rm g:bw16e001:rX,d:g:bw16e001:rX "$DIR"	Grant group (Rechenvorhaben) "bw16e001" read-only access to $DIR
setfacl -Rb "$DIR"	Remove all ACL rights. Standard Unix access rights apply again.

Options used:

• -R: recursive
• -m: modify
• u:username:rwX u: next name is a user; rwX read, write, eXecute (only where execute is set for user)

Delete a Workspace

  $ ws_release blah # Manually erase your workspace blah

Note: workspaces are kept for some time after release. To immediately delete and free space e.g. for quota reasons, delete the files with rm before release

Restore an Expired Workspace

For a certain (varying) time after a workspace has expired, it is possible to restore a workspace using the following steps:

(1) Display restorable workspaces.

ws_restore -l

(2) Create a new workspace as the target for the restore:

ws_allocate restored 60

(3) Restore:

ws_restore full_name_from_ws-l restored

If the workspace is no visible/restorable, it has been permanently deleted and cannot be restored, not even by us. Please always remember, that workspaces are intended solely for temporary work data, and there is no backup of data in the workspaces.