For the latest version (which might not fit your installation) see https://github.com/holgerBerger/hpc-workspace/blob/master/user-guide.md
workspaces are a concept allowing the operations team of an HPC resource to offload some tasks to the user, and allow the user to keep easier track of job directories. It also allows the operations team to manage and load balance several filesystems, and hiding this fact from the users.
A workspace is formost a directory created on behalf of the user with some properties
- it has an ID selected by the user
- it has a lifetime selected by the user, but limited by the operations team
- it has permissions the user can influence or change
The workspace is the place where big data remains during a job or during a job campaign. It is probably not the place to store source files, and it is not the place to archive data at.
Any workspace will be deleted at some point in time, so better keep track of them. But this property makes sure the nasty user from the other side of the floor does not use all the space for ages.
A workspace can be created with ws_allocate.
Example:
SCRDIR=$(ws_allocate MySpace 10)
will create a workspace with the ID MySpace existing for 10 days.
The command will return the path to that new directory into SCRDIR, and will print some more information on stderr.
The maximum lifetime for a workspace may be limited by the operations team. If you specify a longer lifetime, it will be capped to the maxium, and you will see a message that it was changed. If you do not specify a lifetime, a default lifetime will be used (typcially 1 day).
There might be several filesystems prepared by the operations team where a workspace
can be created, you can find out those filesystems with ws_list -l.
This will give a list of filesystems, and one of them might be marked with (default).
The default one will be chosen if you do not specify a filesystem. You can otherwise
choose the filesystem using ws_allocate -F <location> <ID> <DURATION>.
Important: Creating a workspace a second time with any of above lines is a no-operation, it always returns the same path, so it is safe and encourage to use such a line in batch jobs, which are part of a series of jobs working on the same data, no matter if the job was running before or not.
You can use ws_find <ID> instead as well, if you feel more comfortable.
See man ws_allocate for a description of all options.
ws_list will list all your owned workspaces. This has many options for verbosity
(-s only names, -t less than default, -v more than default) and sorting
(-N for name, -C date of creation, -R remaining time, -r reversed)
-l shows the available locations, and -F limits the locations of the listing.
See man ws_list for a description of all options.
ws_release <ID> releases a workspace.
Releasing means that the ID can be reused and the directory is not accessible any more,
but it does not delete the data immediately.
The data is probably kept for a while if there is enough space and can be recovered using
the ws_restore command as long as it is not finally deleted.
The real deletion will probably take place during the nighttime.
Please note: data in a released workspace can still account for the quota usage!
In case the data is limiting you, delete the data before releasing the workspace, or if already
released, restore it using ws_restore, delete it and release the workspace again.
As each workspace has an expiration date, its lifetime is limited.
The operations team can allow you a certain number of extensions of a workspace,
you can see the amount of available extensions with ws_list.
You can extend a workspace using ws_allocate -x <ID> <DAYS>,
each call will consume an extension, unless the new expiration date is shorter
than the previous one. You can also shorten the lifetime if no extensions
are available anymore.
To get a reminder email before the workspace expires, you can set a reminder alarm
using ws_allocate -m <mailaddress> -r <DAYS> <workspace> <duration>.
You can store default values for reminder and email in ~/.ws_user.conf (from version 1.4.0 on, before only for email). Defaults in file can be overruled with command line options.
You can change reminder and email address of an existing workspace using ws_allocate -r <days> -m <mail> -x <workspace> 0.
When a workspace is created with -g it gets a group workspace that is visible to others with ws_list -g (if in same group),
and is group readable.
When it is created with -G <groupname> the workspace gets writable as well, and gets group sticky bit. The group can be specified in
the ~/.ws_user.conf file as well.
With ws_share you can share workspaces with users outside your group, using ACLs (if supported by underlaying filesystem, since 1.3.7)
ws_share share <workspace> <user> gives read access to the specified user, ws_share unshare <workspace> <user> removes the access.
Those operations are applied to all files and directories in the workspace.
Some defaults can be set in ~/.ws_user.conf, so you do not have to give them on command line all the time.
The file is in YAML syntax, and can have the follwing keys: mail, duration, reminder and groupname.
Example:
mail: [email protected]
duration: 10
reminder: 3
groupname: abba