NEMO2/Workspaces/Advanced Features/ws extend - Revision history

M Janczyk: M Janczyk moved page Workspaces/Advanced Features/ws extend to NEMO2/Workspaces/Advanced Features/ws extend

2026-03-02T19:39:30Z

M Janczyk moved page Workspaces/Advanced Features/ws extend to NEMO2/Workspaces/Advanced Features/ws extend

← Older revision	Revision as of 21:39, 2 March 2026
(No difference)

M Janczyk at 14:58, 2 December 2025

2025-12-02T14:58:03Z

@@ Line 1: / Line 1: @@
 = ws_extend - Extend Workspace Lifetime =
 == Basic Usage ==
@@ Line 12: / Line 14: @@
 == Extend Group Workspace ==
 Group members can extend group-writable workspaces (created with <tt>-G</tt>):
@@ Line 34: / Line 19: @@
    $ ws_allocate -x -u alice projectWs 30   # Extend Alice's workspace by 30 days
-Useful when the workspace owner is unavailable.
+Useful when the workspace owner is unavailable. May not work on all clusters.
 == Options ==

M Janczyk at 14:40, 2 December 2025

2025-12-02T14:40:04Z

← Older revision		Revision as of 16:40, 2 December 2025
Line 1:		Line 1:
	= ws_extend - Extend Workspace Lifetime =		= ws_extend - Extend Workspace Lifetime =

			== Basic Usage ==
	Beyond the basic extension shown in the main [[Workspaces/Extend\|Extend guide]]:

			$ ws_extend myWs 30 # Extend by 30 days from now
	== Options ==

			'''Alternative:'''
⚫	* <tt>-F filesystem</tt> - Extend workspace on specific filesystem
	* <tt>ws_allocate -x</tt> - Alternative command for extension
	* You can shorten workspace lifetime even if no extensions are available

			$ ws_allocate -x myWs 30 # Same result
⚫	== Group Workspace ~~Extensions~~ ==

		⚫	'''Important:''' Each extension consumes one of your available extensions. See [[Workspaces/Advanced_Features/Quotas\|Cluster-Specific Workspace Limits]].
⚫	Group members can extend group-writable workspaces (~~requires~~ ~~group write access~~ <tt>~~ws_allocate~~ -G</tt>):

		⚫	== Extend Group Workspace ==
	$ ws_allocate -x -u <username> <workspace_id> <days>

			{\| class="wikitable"
	Replace <tt><username></tt> with the workspace owner's username. This is useful when the workspace owner is unavailable and the workspace needs to be extended.
			\|-
			!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_allocate -x -u</tt> (extend other user's workspace)
			\| style="text-align:center;" \|
			\| style="text-align:center;" \|
			\| style="text-align:center;" \|
			\| style="text-align:center;" \|
			\|style="background-color:#90EE90; text-align:center;" \| ✓
			\|}

		⚫	Group members can extend group-writable workspaces (created with <tt>-G</tt>):
	'''Example:'''

	$ ws_allocate -x -u alice projectWs 30		$ ws_allocate -x -u alice projectWs 30 # Extend Alice's workspace by 30 days

	~~This~~ ~~extends~~ ~~Alice's~~ workspace ~~<tt>projectWs</tt>~~ by ~~30 days~~.		Useful when the workspace owner is unavailable.

	== ~~Notes~~ ==		== Options ==

		⚫	* <tt>-F <filesystem></tt> - Extend workspace on specific filesystem
⚫	* Each extension consumes one of your available extensions ~~(see~~ [[Workspaces/Advanced_Features/Quotas\|Cluster-Specific Workspace Limits]])
	* The <tt>-u</tt> option is only available on some clusters (see cluster compatibility table in advanced [[Workspaces/Advanced_Features/ws_allocate\|ws_allocate guide]])

	For more information: <tt>$ ws_extend -h</tt> or <tt>man ws_extend</tt>		For more information: <tt>ws_extend -h</tt> or <tt>man ws_extend</tt>

M Janczyk: Created page with "= ws_extend - Extend Workspace Lifetime = Beyond the basic extension shown in the main Extend guide: == Options == * `-F filesystem` - Extend workspace on specific filesystem * `ws_allocate -x` - Alternative command for extension * You can shorten workspace lifetime even if no extensions are available == Group Workspace Extensions == Group members can extend group-writable workspaces (requires group write access `ws_allocate -G..."`

2025-12-02T13:31:53Z Created page with "= ws_extend - Extend Workspace Lifetime = Beyond the basic extension shown in the main Extend guide: == Options == * <tt>-F filesystem</tt> - Extend workspace on specific filesystem * <tt>ws_allocate -x</tt> - Alternative command for extension * You can shorten workspace lifetime even if no extensions are available == Group Workspace Extensions == Group members can extend group-writable workspaces (requires group write access <tt>ws_allocate -G..." New page = ws_extend - Extend Workspace Lifetime = Beyond the basic extension shown in the main [[Workspaces/Extend|Extend guide]]: == Options == * <tt>-F filesystem</tt> - Extend workspace on specific filesystem * <tt>ws_allocate -x</tt> - Alternative command for extension * You can shorten workspace lifetime even if no extensions are available == Group Workspace Extensions == Group members can extend group-writable workspaces (requires group write access <tt>ws_allocate -G</tt>): $ ws_allocate -x -u <username> <workspace_id> <days> Replace <tt><username></tt> with the workspace owner's username. This is useful when the workspace owner is unavailable and the workspace needs to be extended. '''Example:''' $ ws_allocate -x -u alice projectWs 30 This extends Alice's workspace <tt>projectWs</tt> by 30 days. == Notes == * Each extension consumes one of your available extensions (see [[Workspaces/Advanced_Features/Quotas|Cluster-Specific Workspace Limits]]) * The <tt>-u</tt> option is only available on some clusters (see cluster compatibility table in advanced [[Workspaces/Advanced_Features/ws_allocate|ws_allocate guide]]) For more information: <tt>$ ws_extend -h</tt> or <tt>man ws_extend</tt>