Workspaces: Difference between revisions

From bwHPC Wiki
Jump to navigation Jump to search
 
(31 intermediate revisions by the same user not shown)
Line 1: Line 1:
{| style=" background:#FFD28A; width:100%;"
<div style="border: 3px solid #ffc107; padding: 15px; background-color: #fff3cd; margin: 10px 0;">
'''Note:''' This is the updated Workspaces guide. The old wiki: [[Workspace]].
| style="padding:8px; background:#FFC05C; font-size:120%; font-weight:bold; text-align:left" | New Workspace Page
</div>
|-
|
'''WARNING:''' This is a new Workspaces page, the old safe-to-use page can be found here: [[Workspace]].
|}


'''Workspace tools''' provide temporary storage spaces called '''workspaces''' for your calculations. They are meant for data that needs to persist longer than a single job, but not permanently.


== What are Workspaces? ==
'''Workspace tools''' provide temporary scratch space called '''workspaces''' for your calculations 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.

Workspaces give you access to the cluster's fast parallel filesystems (like Lustre or Weka). '''You cannot write directly to these parallel filesystems''' - workspaces provide your designated area.

'''Use workspaces for:'''
* Jobs generating intermediate data
* Data shared between multiple compute nodes
* Multi-step workflows
* Temporary scratch space during calculations

'''Don't use workspaces for:'''
* Permanent storage (use HOME or project directories)
* Single-node temporary files (use <tt>$TMPDIR</tt> instead)

== Important - Read First ==

* '''No Backup:''' Data is '''not backed up''' and will be '''automatically deleted''' after expiration
* '''Time-limited:''' Lifetime typically 30-100 days (cluster-specific). See [[Workspaces/Advanced_Features/Quotas#Cluster-Specific_Workspace_Limits|Cluster Limits]]
* '''Automatic Reminders:''' Email notifications before expiration
* '''Backup Important Data:''' Copy results to permanent storage before expiration

'''For advanced features and detailed options:''' [[Workspaces/Advanced Features]]

== Command Overview ==


Main commands:
== Important ==


* <tt>ws_allocate</tt> - Create or extend workspace
* '''No Backup:''' Data in workspaces is '''not backed up''' and will be '''automatically deleted''' after expiration
* <tt>ws_list</tt> - List your workspaces
* '''Time-limited:''' Every workspace has a limited lifetime (typically 30-100 days depending on cluster, see the [[Workspaces/Advanced_Features#Cluster-Specific_Workspace_Limits|Cluster-Specific Workspace Limits]])
* <tt>ws_find</tt> - Find workspace path (for scripts)
* '''Automatic Email Reminders:''' You will receive email notifications before expiration
* <tt>ws_extend</tt> - Extend workspace lifetime
* '''Backup Important Data:''' Copy important results to appropriate permanent storage before expiration (location depends on your cluster/site policies)
* <tt>ws_release</tt> - Release (delete) workspace
* <tt>ws_restore</tt> - Restore expired/released workspace
* <tt>ws_register</tt> - Create symbolic links


All commands support <tt>-h</tt> for help.
== Quick Start - Most Common Commands ==

== Quick Start ==


{| class="wikitable"
{| class="wikitable"
Line 23: Line 49:
!style="width:60%" | Command
!style="width:60%" | Command
|-
|-
|Create workspace for 30 days
|Create workspace (30 days)
|<tt>ws_allocate myWs 30</tt>
|<tt>ws_allocate myWs 30</tt>
|-
|-
|Create group-writable workspace
|Create group workspace
|<tt>ws_allocate -G groupname myWs 30</tt>
|<tt>ws_allocate -G groupname myWs 30</tt>
|-
|-
|List all your workspaces
|List all workspaces
|<tt>ws_list</tt>
|<tt>ws_list</tt>
|-
|-
|See what expires soon
|Find workspace path (for scripts)
|<tt>ws_list -Rr</tt> (<tt>-R</tt>=by time, <tt>-r</tt>=reverse)
|-
|Find path (for scripts)
|<tt>ws_find myWs</tt>
|<tt>ws_find myWs</tt>
|-
|-
|Extend by 30 days
|Check which expire soon
|<tt>ws_list -R</tt>
|-
|Extend workspace by 30 days
|<tt>ws_extend myWs 30</tt>
|<tt>ws_extend myWs 30</tt>
|-
|-
|Delete/release workspace
|Delete workspace
|<tt>ws_release myWs</tt>
|<tt>ws_release myWs</tt>
|-
|-
|Restore released workspace
|Restore workspace
|<tt>ws_restore -l</tt> then <tt>ws_restore oldname newname</tt>
|<tt>ws_restore -l</tt> then <tt>ws_restore oldname newname</tt>
|}
|}
Line 50: Line 76:
== Create Workspace ==
== Create Workspace ==


To create a workspace you need to specify a '''name''' and '''lifetime''' in days:
Create a workspace with a '''name''' and '''lifetime''' in days:


$ ws_allocate myWs 30
$ ws_allocate myWs 30 # Create for 30 days


Returns:
This returns:
Workspace created. Duration is 720 hours.
Workspace created. Duration is 720 hours.
Line 60: Line 86:
/work/workspace/scratch/username-myWs-0
/work/workspace/scratch/username-myWs-0


'''Common options:'''
'''Important:''' Creating a workspace a second time with the same command is safe - it always returns the same path.


$ ws_allocate -G groupname myWs 30 # Group-writable (for teams)
'''Capture the path in a variable:'''
$ ws_allocate -g myWs 30 # Group-readable
$ ws_allocate -F ffuc myWs 30 # bwUniCluster 3.0: Flash filesystem

'''Capture path in variable:'''


$ WORKSPACE=$(ws_allocate myWs 30)
$ WORKSPACE=$(ws_allocate myWs 30)
$ cd $WORKSPACE
$ cd "$WORKSPACE"

'''Important:''' Running the same command again is safe - returns the existing workspace path.


'''For all options and advanced usage,''' see the [[Workspaces/Advanced_Features#Detailed_ws_allocate_Options|Advanced Features guide]].
'''Details:''' [[Workspaces/Advanced_Features/ws_allocate|Advanced Features guide]]


== List Your Workspaces ==
== List Your Workspaces ==


$ ws_list # List all workspaces
To see all your workspaces:


Shows workspace ID, location, extensions, creation date, and remaining time.
$ ws_list


'''Common options:'''
Shows:
* Workspace ID
* Workspace location
* Available extensions
* Creation date and remaining time


$ ws_list -Rr # Sort by remaining time, reverse (last to expire first)
'''Useful options:'''
* <tt>ws_list -R</tt> - Sort by remaining time (see what expires soon)
$ ws_list -s # Short format (names only, for scripts)
$ ws_list -g # Show group workspaces
* <tt>ws_list -s</tt> - Short format (only names, good for scripts)


'''Note:''' To list expired workspaces for restore, use <tt>ws_restore -l</tt>. See [[#Restore_Workspace|Restore]].
== Find Workspace Path ==


'''Details:''' [[Workspaces/Advanced_Features/ws_list|Advanced Features guide]]
Get the path to a workspace for use in scripts:


== Extend Workspace Lifetime ==
$ ws_find myWs


Extend before workspace expires:
Returns:


$ ws_extend myWs 30 # Extend by 30 days from now
/work/workspace/scratch/username-myWs-0


'''In scripts:'''
'''Alternative:'''


$ ws_allocate -x myWs 30 # Same result
$ cd $(ws_find myWs)
$ WORKSPACE=$(ws_find myWs)


'''Note:''' Each extension consumes one available extension. See [[Workspaces/Advanced_Features/Quotas#Cluster-Specific_Workspace_Limits|Cluster Limits]].
== Extend Workspace Lifetime ==


'''Group workspaces:''' See [[#Extend_Group_Workspace|Extend Group Workspace]] for extending workspaces created by colleagues.
Extend a workspace before it expires:


'''Details:''' [[Workspaces/Advanced_Features/ws_extend|Advanced Features guide]]
$ ws_extend myWs 30 # Extend by 30 days from now

Or use:

$ ws_allocate -x myWs 30 # Alternative command

'''Note:''' Each extension consumes one of your available extensions (see the [[Workspaces/Advanced_Features#Cluster-Specific_Workspace_Limits|Cluster-Specific Workspace Limits]]).


== Release (Delete) Workspace ==
== Release (Delete) Workspace ==


When you no longer need a workspace:
When no longer needed:


$ ws_release myWs
$ ws_release myWs # Release workspace


'''What happens:'''
'''What happens:'''
* Workspace becomes inaccessible
* Workspace becomes inaccessible immediately
* Data is kept for a grace period (can be restored, see below)
* Data kept for short grace period (typically until next cleanup)
* Can be restored with <tt>ws_restore</tt> during grace period
* Real deletion happens later (typically during nighttime)
* May still count toward quota until final deletion


'''Details:''' [[Workspaces/Advanced_Features/ws_release|Advanced Features guide]]
'''To free quota immediately:'''

$ ws_release --delete-data myWs # Immediate deletion (WARNING: cannot be recovered!)

Or with older workspace tools:

$ WSDIR=$(ws_find myWs) && [ -n "$WSDIR" ] && rm -rf "$WSDIR" # Delete data first (with safety check)
$ ws_release myWs # Then release


== Restore Workspace ==
== Restore Workspace ==


{| class="wikitable"
If you released a workspace by accident or need to recover an expired one, you can restore it within a grace period:
|-
!style="width:40%" | Works on cluster
!style="width:10%" | bwUC 3.0
!style="width:10%" | BinAC2
!style="width:10%" | Helix
!style="width:10%" | JUSTUS 2
!style="width:10%" | NEMO2
|-
|<tt>ws_restore</tt>
|style="background-color:#90EE90; text-align:center;" | ✓
|style="background-color:#90EE90; text-align:center;" | ✓
|style="background-color:#90EE90; text-align:center;" | ✓
|style="background-color:#90EE90; text-align:center;" | ✓
|style="background-color:#90EE90; text-align:center;" | ✓
|}


'''(1) List restorable workspaces:'''
Recover expired or released workspaces within grace period:


'''Restore procedure:'''
$ ws_restore -l


$ ws_restore -l # (1) List restorable workspaces
'''(2) Create a new target workspace:'''
$ ws_allocate restored 60 # (2) Create target workspace
$ ws_restore username-myWs-0 restored # (3) Restore


'''Important:''' Use the '''full name''' from <tt>ws_restore -l</tt> (with username and timestamp), not the short name.
$ ws_allocate restored 60


'''Details:''' [[Workspaces/Advanced_Features/ws_restore|Advanced Features guide]]
'''(3) Restore the expired workspace:'''


== Work with Groups (Share Workspaces) ==
$ ws_restore username-myWs-0 restored


{| class="wikitable"
'''Note:''' Use the '''full name''' from <tt>ws_restore -l</tt> (including username and timestamp), not the short name from <tt>ws_list</tt>.
|-
!style="width:40%" | Works on cluster
!style="width:10%" | bwUC 3.0
!style="width:10%" | BinAC2
!style="width:10%" | Helix
!style="width:10%" | JUSTUS 2
!style="width:10%" | NEMO2
|-
|<tt>-g</tt> (group-readable)
| style="text-align:center;" |
| style="text-align:center;" |
| style="text-align:center;" |
| style="text-align:center;" |
|style="background-color:#90EE90; text-align:center;" | ✓
|-
|<tt>-G</tt> (group-writable)
| style="text-align:center;" |
| style="text-align:center;" |
| style="text-align:center;" |
| style="text-align:center;" |
|style="background-color:#90EE90; text-align:center;" | ✓
|}


Simple team collaboration with group workspaces:
'''For detailed restore options,''' see the [[Workspaces/Advanced_Features#Restore_an_Expired_Workspace|Advanced Features guide]].


== Share Workspace ==
=== Create Group Workspace ===


'''Group-readable (read-only):'''
You can share workspaces with team members:

'''Important:''' Not all sharing options are available on all clusters. ACL-based methods like <tt>ws_share</tt> require filesystem support and may not work everywhere. If one method doesn't work, try an alternative approach.

'''Group-readable workspace''' (read-only for group):


$ ws_allocate -g myWs 30
$ ws_allocate -g myWs 30


'''Group-writable workspace''' (read-write for group, recommended):
'''Group-writable (recommended):'''


$ ws_allocate -G projectgroup myWs 30
$ ws_allocate -G projectgroup myWs 30 # Replace 'projectgroup' with your group


'''Tip:''' Set default in <tt>~/.ws_user.conf</tt>:
'''Recommended approach:'''
* Use <tt>-g</tt> or <tt>-G</tt> flags during workspace creation
* For read-only sharing: use <tt>-g</tt>
* For collaborative work (read-write): use <tt>-G groupname</tt>
* Set <tt>groupname</tt> in <tt>~/.ws_user.conf</tt> if you always work with the same group

'''For advanced sharing options''' (ACL-based, read-only, less common), see the [[Workspaces/Advanced_Features#Cooperative_Usage_.28Group_Workspaces_and_Sharing.29|Advanced Features guide]].

== Command Overview ==

The workspace tools consist of several commands:

* <tt>ws_allocate</tt> - Create or extend a workspace
* <tt>ws_list</tt> - List all your workspaces
* <tt>ws_find</tt> - Find the path to a workspace
* <tt>ws_extend</tt> - Extend the lifetime of a workspace
* <tt>ws_release</tt> - Release (delete) a workspace
* <tt>ws_restore</tt> - Restore an expired or released workspace
* <tt>ws_register</tt> - Create symbolic links to workspaces

All commands support <tt>-h</tt> or <tt>--help</tt> to show detailed usage information.

== Using Workspaces in Batch Jobs ==

'''Recommended approach:''' Create your workspace manually before submitting jobs, then reference it in your job scripts using <tt>ws_find</tt>.

'''(1) Create workspace once (on login node):'''

$ ws_allocate myProject 60

'''(2) Use in job scripts with ws_find:'''


<pre>
<pre>
groupname: projectgroup
#!/bin/bash
#SBATCH --job-name=my_job
#SBATCH --time=24:00:00

# Find existing workspace
WORKSPACE=$(ws_find myProject)

# Change to workspace
cd $WORKSPACE

# Your computation here
./my_program --input input.dat --output results.dat
</pre>
</pre>


Then simply: <tt>ws_allocate myWs 30</tt>
'''Warning:''' Avoid using <tt>ws_allocate</tt> directly in job scripts that run frequently. While <tt>ws_allocate</tt> is safe to call multiple times on the same workspace name (it returns the existing workspace), you should not create too many workspaces unnecessarily. Create workspaces manually when needed, then use <tt>ws_find</tt> in your job scripts to locate them.

== Advanced Features ==

For detailed information about advanced workspace features, configuration options, and less frequently used commands, see the separate [[Workspaces/Advanced_Features]] guide.

Topics covered in the advanced guide include:
* Complete command reference with all options
* Multiple filesystem locations
* Detailed options for ws_allocate, ws_list, ws_find, ws_extend
* Email and calendar reminders configuration
* Group workspaces and cooperative usage
* Advanced sharing with ws_share (ACL-based, read-only)
* Setting permissions (ACLs and Unix permissions)
* Deleting and restoring workspaces in detail
* Cluster-specific limits and quotas
* Checking workspace quotas
* Registering workspace links

== Best Practices and Recommendations ==

=== For All Users ===

# '''Set up ~/.ws_user.conf''' - Configure default reminder timing, duration, and groupname to avoid typing them repeatedly (see [[Workspaces/Advanced_Features#Example_.7E.2F.ws_user.conf_Configuration|example configuration]])
# '''Email reminders are automatic''' - Notifications are sent automatically using your identity provider email; only use <tt>-r</tt> to customize reminder timing if needed
# '''Custom email only if needed''' - Only use <tt>-m</tt> option to override the email address from your identity provider
# '''Use ws_register''' - Create symbolic links to your workspaces in a convenient directory: <tt>ws_register ~/workspaces</tt>
# '''Create workspaces manually''' - Create workspaces on the login node before submitting jobs, then use <tt>ws_find</tt> in your job scripts
# '''Track your workspaces''' - Regularly run <tt>ws_list -R</tt> to see which workspaces will expire soon
# '''Backup important data''' - Workspaces are temporary and not backed up - copy results to appropriate permanent storage (check your cluster/site policies for backup locations)
# '''Clean up regularly''' - Release workspaces you no longer need to keep filesystems organized


=== For Short-term Jobs (hours to days) ===
=== List Group Workspaces ===


$ ws_list -g # Show all group workspaces
# Use default or short durations (1-7 days)
# Consider using a single workspace for a series of related jobs
# Use <tt>ws_find</tt> in job scripts to locate the workspace


=== Extend Group Workspace ===
=== For Long-term Campaigns (weeks to months) ===


Anyone in the group can extend group-writable workspaces (<tt>-G</tt>):
# Request maximum allowed duration
# Email reminders are sent automatically; optionally customize reminder timing with <tt>-r</tt> option
# Use <tt>ws_list -R</tt> regularly to monitor remaining time
# Plan data archival to appropriate permanent storage before expiration (check cluster/site policies)


$ ws_extend myWs 30 # If you created it
=== For Collaborative Work ===
$ ws_allocate -x -u alice myWs 30 # If colleague created it


=== Manage Reminders ===
# Use <tt>ws_allocate -G groupname</tt> for shared write access (recommended)
# Set <tt>groupname</tt> in <tt>~/.ws_user.conf</tt> if you always work with the same group
# Use <tt>ws_allocate -g</tt> for read-only sharing within group
# Document the workspace location for your team members
# For advanced sharing scenarios, see the [[Workspaces/Advanced_Features#Cooperative_Usage_.28Group_Workspaces_and_Sharing.29|Advanced Features guide]]


Take over reminder responsibility:
=== For Managing Multiple Filesystems ===


$ ws_allocate -r 7 -u alice -x myWs 0 # Update timing and take over reminders
# '''Note:''' Most clusters have only one default filesystem - the <tt>-F</tt> option is rarely needed
# Use <tt>ws_list -l</tt> first to check if multiple filesystems are available on your cluster
# Use <tt>-F</tt> option only if you need specific filesystem for performance or capacity needs (see [[Workspaces/Advanced_Features#Multiple_Filesystem_Locations|filesystem options]])
# '''bwUniCluster 3.0 filesystems:'''
#* '''Default Lustre filesystem:''' Standard workspace location, best for large files and sequential I/O
#* '''Flash filesystem (ffuc):''' SSD-based storage for KIT/HoreKa users, shared between bwUniCluster 3.0 and HoreKa
#* Use flash filesystem for workloads with many small files, random I/O, AI/ML training, or compilation
#* Balance load: use <tt>-F ffuc</tt> when appropriate to reduce load on default filesystem
# '''General guidelines:'''
#* Flash-based filesystems (SSD/NVMe): Use for many small files, low-latency requirements, random I/O
#* Standard Lustre/parallel filesystems: Best for large files and sequential I/O patterns


Changes reminder to 7 days before expiration and redirects emails to you.
=== For Different Data Types ===


=== Why Use Group Workspaces? ===
# '''Large sequential I/O:''' Use standard workspace filesystem (Lustre best for very large files, Weka excellent for both large and small)
# '''Many small files or random access:''' Use flash-based workspace filesystem like Weka (NEMO2) or bwUniCluster ffuc, or stage to <tt>$TMPDIR</tt>
# '''Data read multiple times on single node:''' Copy to <tt>$TMPDIR</tt> at job start for best performance
# '''Temporary data for single node:''' Always use <tt>$TMPDIR</tt>, not workspaces
# '''Multi-node temporary data:''' Use workspaces (not suitable for <tt>$TMPDIR</tt>)
# '''AI/ML training data:''' Use Weka (NEMO2) or flash filesystems for best performance, or stage to <tt>$TMPDIR</tt> for repeated access
# '''Compilation/build directories:''' Use flash-based filesystems (Weka, ffuc) or <tt>$TMPDIR</tt> for better performance


* Simple collaboration - everyone accesses same data
=== For Quota Management ===
* No permission problems - automatic group permissions
* Independent extensions - team can extend without creator
* Easy discovery - <tt>ws_list -g</tt> shows all team workspaces


'''Advanced sharing:''' [[Workspaces/Advanced_Features/Sharing|Sharing guide]] for ACLs and ws_share
# Delete data before releasing if you need immediate quota relief: <tt>WSDIR=$(ws_find workspace) && [ -n "$WSDIR" ] && rm -rf "$WSDIR"</tt> then <tt>ws_release workspace</tt>
# Use <tt>ws_release --delete-data</tt> (newer versions) for immediate deletion
# Remember: released workspaces may still count toward quota during grace period

Latest revision as of 17:18, 2 December 2025

Note: This is the updated Workspaces guide. The old wiki: Workspace.

Workspace tools provide temporary storage spaces called workspaces for your calculations. They are meant for data that needs to persist longer than a single job, but not permanently.

What are Workspaces?

Workspaces give you access to the cluster's fast parallel filesystems (like Lustre or Weka). You cannot write directly to these parallel filesystems - workspaces provide your designated area.

Use workspaces for:

  • Jobs generating intermediate data
  • Data shared between multiple compute nodes
  • Multi-step workflows
  • Temporary scratch space during calculations

Don't use workspaces for:

  • Permanent storage (use HOME or project directories)
  • Single-node temporary files (use $TMPDIR instead)

Important - Read First

  • No Backup: Data is not backed up and will be automatically deleted after expiration
  • Time-limited: Lifetime typically 30-100 days (cluster-specific). See Cluster Limits
  • Automatic Reminders: Email notifications before expiration
  • Backup Important Data: Copy results to permanent storage before expiration

For advanced features and detailed options: Workspaces/Advanced Features

Command Overview

Main commands:

  • ws_allocate - Create or extend workspace
  • ws_list - List your workspaces
  • ws_find - Find workspace path (for scripts)
  • ws_extend - Extend workspace lifetime
  • ws_release - Release (delete) workspace
  • ws_restore - Restore expired/released workspace
  • ws_register - Create symbolic links

All commands support -h for help.

Quick Start

Task Command
Create workspace (30 days) ws_allocate myWs 30
Create group workspace ws_allocate -G groupname myWs 30
List all workspaces ws_list
See what expires soon ws_list -Rr (-R=by time, -r=reverse)
Find path (for scripts) ws_find myWs
Extend by 30 days ws_extend myWs 30
Delete workspace ws_release myWs
Restore workspace ws_restore -l then ws_restore oldname newname

Create Workspace

Create a workspace with a name and lifetime in days:

  $ ws_allocate myWs 30                    # Create for 30 days

Returns:

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

Common options:

  $ ws_allocate -G groupname myWs 30       # Group-writable (for teams)
  $ ws_allocate -g myWs 30                 # Group-readable
  $ ws_allocate -F ffuc myWs 30            # bwUniCluster 3.0: Flash filesystem

Capture path in variable:

  $ WORKSPACE=$(ws_allocate myWs 30)
  $ cd "$WORKSPACE"

Important: Running the same command again is safe - returns the existing workspace path.

Details: Advanced Features guide

List Your Workspaces

  $ ws_list                                # List all workspaces

Shows workspace ID, location, extensions, creation date, and remaining time.

Common options:

  $ ws_list -Rr                            # Sort by remaining time, reverse (last to expire first)
  $ ws_list -s                             # Short format (names only, for scripts)
  $ ws_list -g                             # Show group workspaces

Note: To list expired workspaces for restore, use ws_restore -l. See Restore.

Details: Advanced Features guide

Extend Workspace Lifetime

Extend before workspace expires:

  $ ws_extend myWs 30                      # Extend by 30 days from now

Alternative:

  $ ws_allocate -x myWs 30                 # Same result

Note: Each extension consumes one available extension. See Cluster Limits.

Group workspaces: See Extend Group Workspace for extending workspaces created by colleagues.

Details: Advanced Features guide

Release (Delete) Workspace

When no longer needed:

  $ ws_release myWs                        # Release workspace

What happens:

  • Workspace becomes inaccessible immediately
  • Data kept for short grace period (typically until next cleanup)
  • Can be restored with ws_restore during grace period
  • May still count toward quota until final deletion

Details: Advanced Features guide

Restore Workspace

Works on cluster bwUC 3.0 BinAC2 Helix JUSTUS 2 NEMO2
ws_restore

Recover expired or released workspaces within grace period:

Restore procedure:

  $ ws_restore -l                          # (1) List restorable workspaces
  $ ws_allocate restored 60                # (2) Create target workspace
  $ ws_restore username-myWs-0 restored    # (3) Restore

Important: Use the full name from ws_restore -l (with username and timestamp), not the short name.

Details: Advanced Features guide

Work with Groups (Share Workspaces)

Works on cluster bwUC 3.0 BinAC2 Helix JUSTUS 2 NEMO2
-g (group-readable)
-G (group-writable)

Simple team collaboration with group workspaces:

Create Group Workspace

Group-readable (read-only):

  $ ws_allocate -g myWs 30

Group-writable (recommended):

  $ ws_allocate -G projectgroup myWs 30    # Replace 'projectgroup' with your group

Tip: Set default in ~/.ws_user.conf:

groupname: projectgroup

Then simply: ws_allocate myWs 30

List Group Workspaces

  $ ws_list -g                             # Show all group workspaces

Extend Group Workspace

Anyone in the group can extend group-writable workspaces (-G):

  $ ws_extend myWs 30                      # If you created it
  $ ws_allocate -x -u alice myWs 30        # If colleague created it

Manage Reminders

Take over reminder responsibility:

  $ ws_allocate -r 7 -u alice -x myWs 0    # Update timing and take over reminders

Changes reminder to 7 days before expiration and redirects emails to you.

Why Use Group Workspaces?

  • Simple collaboration - everyone accesses same data
  • No permission problems - automatic group permissions
  • Independent extensions - team can extend without creator
  • Easy discovery - ws_list -g shows all team workspaces

Advanced sharing: Sharing guide for ACLs and ws_share