SDS@hd/SV Management - Revision history

H Schumacher: added instructions for role changes

2026-10-09T11:46:19Z

added instructions for role changes

← Older revision		Revision as of 13:46, 9 October 2026
Line 63:		Line 63:
	* ...add and remove Users from allocations except themselves or the PI.		* ...add and remove Users from allocations except themselves or the PI.
	* ...change the roles of Users on project and allocation level (Project: User <-> PM; SV: None <-> Guest).		* ...change the roles of Users on project and allocation level (Project: User <-> PM; SV: None <-> Guest).
			*: → Go to the Users table, click the action item for the selected user and change the role.

	* ...enable/disable notifications for other Users.		* ...enable/disable notifications for other Users.

H Schumacher: added information to storage place management

2026-10-09T09:16:39Z

added information to storage place management

← Older revision		Revision as of 11:16, 9 October 2026
Line 244:		Line 244:
	== Storage Space Management ==		== Storage Space Management ==

	At the ~~moment~~ you can't see how much storage space is left. ~~We are working on including this information.~~		At the acllocation page at bwServices-Management, you can see how much storage space is left.

	To keep the data hot, you should regularly check the following points:		To keep the data hot, you should regularly check the following points:
	* Make sure that temporary data gets removed.		* Make sure that temporary data gets removed:
			** Delete temporary files, for example in the .cache folder. Other folders starting with a dot might contain temporary files as well, for example .local/share/Trash.
⚫	* Make sure that no data from finished projects is stored. You might want to archive those with one of the archiving services listed on the [https://wiki.bwhpc.de/e/Main_Page Main Page].
			** Use the cleaning commands by your used software (e.g. conda).
			** Delete folders with temporary data created by your used software (e.g. nextflow).
		⚫	* Make sure that no data from finished projects is stored. You might want to archive those with one of the archiving services listed at the [https://wiki.bwhpc.de/e/Main_Page Main Page].
	* If someone has left the storage project, make sure that the PI has access to the data and the data is still hot.		* If someone has left the storage project, make sure that the PI has access to the data and the data is still hot.

H Schumacher: improved instructions

2026-10-07T08:42:16Z

improved instructions

← Older revision		Revision as of 10:42, 7 October 2026
Line 76:		Line 76:

	==== Adding users ====		==== Adding users ====
	PMs can add users to their projects and to any allocation within the project~~. To provide a user with access to an allocation, both of the following steps must be followed~~.		PMs can add users to their projects and to any allocation within the project.

			{\|style="background:#deffee; width:70%;"
			\|style="padding:5px; background:#cef2e0; text-align:left"\|
			[[Image:Attention.svg\|center\|25px]]
			\|style="padding:5px; background:#cef2e0; text-align:left"\|
			To provide a user with access to an allocation, <ins>'''both of the following steps must be followed'''</ins>.
			\|}
	<u>'''1.''' Adding users to a project:</u>		<u>'''1.''' Adding users to a project:</u>
	# On the project's page either the button on the top or next to the users list can be used for adding users.		# On the project's page either the button on the top or next to the users list can be used for adding users.
Line 93:		Line 99:

	An allocation can have multiple users. To add a new user:		An allocation can have multiple users. To add a new user:
	# Go to the page of the ~~allocation~~		# Go to the page of the project.
	# Go to the section ~~"Users~~ in ~~Allocation"~~ ~~and~~ ~~click "Add Users"~~		# Go to the section with the allocations table.
			# Go to the page of the allocation by clicking on the folder symbol under "Actions".
			# Go to the section "Users in Allocation" and click "Add Users".
	# Choose the users that shall be added from the list of project members.		# Choose the users that shall be added from the list of project members.
	#: If you don't see the user here, please make sure that you've added them to the project first.		#: If you don't see the user here, please make sure that you've added them to the project first.

	==== Yearly Project Extension ====		==== Yearly Project Extension ====

H Schumacher: improved change request description and FAQ

2026-10-05T12:07:20Z

improved change request description and FAQ

← Older revision		Revision as of 14:07, 5 October 2026
Line 140:		Line 140:
	==== Adjust SV Attributes ====		==== Adjust SV Attributes ====

	To change the properties of your SV, you can hand in a Change Request.		To change the properties of your SV, you can hand in a ''Change Request''. You can find this option at the page of your SV at bwServices-Management.

	When you request a quota expansion for your SV at the SDS@hd service in order to store hot scientific data, we kindly ask you to answer the questions in the justification textfield for reasoning the extension. The questions are:		When you request a quota expansion for your SV at the SDS@hd service in order to store hot scientific data, we kindly ask you to answer the questions in the justification textfield for reasoning the extension. The questions are:
	<syntaxhighlight lang="text">Q1: Please explain why additional storage is needed.		<syntaxhighlight lang="text">Q1: Please explain why additional storage is needed.
Line 166:		Line 167:
	== FAQ ==		== FAQ ==

			* How can I ask for increased quota?
			*: Please do it via a change request as described in the section [[#Adjust_SV_Attributes \| Adjust SV Attributes]].
	* I changed a user's role in bwServices-Management but the user still has the previous access rights.		* I changed a user's role in bwServices-Management but the user still has the previous access rights.
	*: After 30 minutes the adjustment should be synced to all systems. If not, it helps when the member with the role change logs in to bwServices once to trigger an automatic update and then waits for 30 minutes.		*: After 30 minutes the adjustment should be synced to all systems. If not, it helps when the member with the role change logs in to bwServices once to trigger an automatic update and then waits for 30 minutes.
Line 175:		Line 178:
	*: Please [mailto:sds-hd-support@urz.uni-heidelberg.de submit a Ticket]		*: Please [mailto:sds-hd-support@urz.uni-heidelberg.de submit a Ticket]
	* How can the PI of a project be changed?		* How can the PI of a project be changed?
	*: This is currently not possible but will be possible in the future.		*: This is currently not possible but will be possible in the future. If it is really necessary to do it before the feature is officially implemented, you can contact the SDS@hd support.
			* My SV status is "approved". When does it get "active"?
			*: When the first SV member finishes the [[SDS@hd/Registration \| registration]] for SDS@hd.

H Schumacher: moved section for adding users, added instructions

2026-09-28T14:11:18Z

moved section for adding users, added instructions

@@ Line 41: / Line 41: @@
 In bwServices-Management the top level entity is a project. On this page ''project'' always refers to this ''bwServices-Project''. Every bwIDM member with employee status can create a project by going to the ''Projects'' page (Home -> Projects) and then clicking on the "Add a project" button. A project can have multiple users. For specifics regarding the different roles in a project see the [[#Roles_in_a_Project| Roles]] section.
 [[File:bwServices_Management_home.png|300px|thumb|right|The start page lists recent projects and allocations. The titles link to the complete lists.]]
 Here is an overview of the most important pages and what you can find there:
@@ Line 76: / Line 60: @@
 === Project Manager (PM) ===
 Additionally to the abilities of a User, a PM can...
-* ...add and remove Users from the project.
+* ...add and remove Users from the project except themselves or the PI.
-* ...add and remove Users from allocations.
+* ...add and remove Users from allocations except themselves or the PI.
 * ...change the roles of Users on project and allocation level (Project: User <-> PM; SV: None <-> Guest).
@@ Line 90: / Line 74: @@
 * ...extend allocation lifetime.
 * ...can archive (~ delete) the project.
 ==== Yearly Project Extension ====
@@ Line 115: / Line 122: @@
 * ...view the status of the SV (active/expired, end date)
 Notifications regarding the SVs that they are a member of can be:
-** information about having been added to an allocation
+* information about having been added to an allocation
-** information about accepted or denied change requests (without the concrete content of the request)
+* information about accepted or denied change requests (without the concrete content of the request)
-** information about an allocation being activated or denied
+* information about an allocation being activated or denied
 === Guests ===
@@ Line 135: / Line 142: @@
 To change the properties of your SV, you can hand in a Change Request.
 When you request a quota expansion for your SV at the SDS@hd service in order to store hot scientific data, we kindly ask you to answer the questions in the justification textfield for reasoning the extension. The questions are:
-<syntaxhighlight>Q1: Please explain why additional storage is needed.
+<syntaxhighlight lang="text">Q1: Please explain why additional storage is needed.
 Q2: What is the potential for deleting or archiving data?</syntaxhighlight>

H Schumacher: added more information about chmod

2026-09-02T14:30:53Z

added more information about chmod

← Older revision		Revision as of 16:30, 2 September 2026
Line 177:		Line 177:

	* In the main space of an SV everyone has read and write access.		* In the main space of an SV everyone has read and write access.
	* The person who creates a file or folder is the owner. The owner can adjust the rights via [[Workspace#Regular_Unix_Permissions \| chmod]].		* The person who creates a file or folder is the owner. The owner can adjust the rights via [[Workspace#Regular_Unix_Permissions \| chmod]] when using one of the following connection methods: sftp/sshfs, nfs, bwVisu, bwForCluster Helix. On Windows the rights can be set with a right click on the file/folder and using the properties menu.
	* The SV responsible has full control over the access rights by being able to take [[#Taking_Ownership_of_Files \| ownership of files]].		* The SV responsible has full control over the access rights by being able to take [[#Taking_Ownership_of_Files \| ownership of files]].
	* The SDS@hd support can help with defining access rules for your specific use case. Optimally, this is discussed before the SV gets filled with data. Examples:		* The SDS@hd support can help with defining access rules for your specific use case. Optimally, this is discussed before the SV gets filled with data. Examples:

H Schumacher: fixed link

2026-09-02T14:25:56Z

fixed link

← Older revision		Revision as of 16:25, 2 September 2026
Line 177:		Line 177:

	* In the main space of an SV everyone has read and write access.		* In the main space of an SV everyone has read and write access.
	* The person who creates a file or folder is the owner. The owner can adjust the rights via [[Workspace#Regular_Unix_Permissions \| chmod].		* The person who creates a file or folder is the owner. The owner can adjust the rights via [[Workspace#Regular_Unix_Permissions \| chmod]].
	* The SV responsible has full control over the access rights by being able to take [[#Taking_Ownership_of_Files \| ownership of files]].		* The SV responsible has full control over the access rights by being able to take [[#Taking_Ownership_of_Files \| ownership of files]].
	* The SDS@hd support can help with defining access rules for your specific use case. Optimally, this is discussed before the SV gets filled with data. Examples:		* The SDS@hd support can help with defining access rules for your specific use case. Optimally, this is discussed before the SV gets filled with data. Examples:
Line 191:		Line 191:
	<ins>Hint:</ins> If needed, the SDS@hd support can create custom access rules for specific top level folders.		<ins>Hint:</ins> If needed, the SDS@hd support can create custom access rules for specific top level folders.

	The SV scheme on the right visualizes how the orange full member experiences the access when working in the SV. The full member has free read and write access to everything except the personal folder of the blue user.		The SV scheme on the right visualizes how the orange full member experiences the access when working in the SV. The full member has free read and write access to everything except the personal folder of the blue user.

	== Guest Folder ==		== Guest Folder ==

H Schumacher: fixed link

2026-09-02T10:39:53Z

fixed link

← Older revision		Revision as of 12:39, 2 September 2026
Line 52:		Line 52:
	# The added person gets an email notification regarding their new project membership.		# The added person gets an email notification regarding their new project membership.

	A project can have multiple allocations. Having an allocation means that you can allocate a resource like SDS@hd for your project. An allocation comes with its own form to fill in and its own terms to agree to. You can find detailed instructions under [[SDS@hd/~~Registration_New~~#b)_Apply_for_new_SV \| Registration/Apply for new SV]].		A project can have multiple allocations. Having an allocation means that you can allocate a resource like SDS@hd for your project. An allocation comes with its own form to fill in and its own terms to agree to. You can find detailed instructions under [[SDS@hd/Registration#b)_Apply_for_new_SV \| Registration/Apply for new SV]].

	'''Adding users to an allocation:'''		'''Adding users to an allocation:'''

H Schumacher: update to bwServices-Management

2026-09-01T15:14:18Z

update to bwServices-Management

Show changes

H Schumacher: added hint regarding ORCiD users

2026-07-24T12:52:53Z

added hint regarding ORCiD users

← Older revision		Revision as of 14:52, 24 July 2026
Line 14:		Line 14:
	*# Provide them with the SV password. The SV responsible received the initial password via email. <u>Caution</u>: Make sure to share the SV password. Do not share your personal service password which you set in registration step B at bwServices.		*# Provide them with the SV password. The SV responsible received the initial password via email. <u>Caution</u>: Make sure to share the SV password. Do not share your personal service password which you set in registration step B at bwServices.
	*# Afterwards, they can join by following the [[SDS@hd/Registration \| registration steps]].		*# Afterwards, they can join by following the [[SDS@hd/Registration \| registration steps]].
	* ...change the status of SV members (active/inactive)		* ...change the status of SV members (active/inactive). Make sure to especially manage the access of those members that joined with their ORCiD account. Otherwise, they'll have access forever.

	=== SV Responsible (SVV) ===		=== SV Responsible (SVV) ===