Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
habrok:advanced_job_management:special_partitions [2025/08/22 06:34] – [GELIFES account] fokkehabrok:advanced_job_management:special_partitions [2025/08/22 15:09] (current) – [Group specific nodes] Formatting pedro
Line 11: Line 11:
 This sounds a bit complicated, but the main thing to take home is: This sounds a bit complicated, but the main thing to take home is:
  
-- Submit to the dedicated partition to get to the group specific nodes.\\ +  *Submit to the dedicated partition to get to the group specific nodes.\\ 
-- Usage (and priorities) of these nodes are handled separately from the usage and priorities of the rest of the cluster.+  *Usage (and priorities) of these nodes are handled separately from the usage and priorities of the rest of the cluster.
  
 ===== Account coordinator instructions ===== ===== Account coordinator instructions =====
  
-Users with the coordinator role in one of the special accounts can add users to the account using the following command:+Users with the coordinator role in one of the special accounts can add users to the account using the following command, which should be run on one of the login/interactive nodes of the cluster:
  
 <code> <code>
-sacctmgr add user USERNAME account=ACCOUNT fairshare=1+sacctmgr add user <username> account=<account> fairshare=1
 </code> </code>
-Where USERNAME should be changed into the userid that is to be added to the account ACCOUNT. ACCOUNT must be changed into the name of the account, e.g. gelifes, digitallab, caos. The fairshare should be by default set to 1.+Where <username> should be changed into the userid that is to be added to the account <account>. <account> must be changed into the name of the account, e.g. gelifes, digitallab, caos. The fairshare should be by default set to 1.
  
 In order to verify/check if a user has already been added to the account, the column “Account” in the output of the following command should show a row with “users” and one with the special account: In order to verify/check if a user has already been added to the account, the column “Account” in the output of the following command should show a row with “users” and one with the special account:
  
 <code> <code>
-sacctmgr show -s user USERNAME+sacctmgr show -s user <username>
 </code> </code>
 +
 +A full list of users in the account can be obtained using:
 +<code>
 +sacctmgr show -s account <account>
 +</code>
 +Note that CIT site administrators can also be members of these special accounts, as they need access for testing node performance and running software installations.
  
 Coordinators can be added to the special accounts using: Coordinators can be added to the special accounts using:
  
 <code> <code>
-sacctmgr add coordinator name=USERNAME account=ACCOUNT+sacctmgr add coordinator name=<username> account=<account>
 </code> </code>
 In order to modify an existing user the following can be used: In order to modify an existing user the following can be used:
  
 <code> <code>
-sacctmgr modify user name=USERNAME account=ACCOUNT set fairshare=1+sacctmgr modify user name=<username> account=<account> set fairshare=10
 </code> </code>
 +This will modify the fairshare for the user.
  
 +A user can be removed from the account using:
 +<code>
 +sacctmgr -i delete user <username> account=<account_name>
 +</code>
  
-==== GELIFES nodes ====+===== GELIFES nodes =====
  
 The node themselves are 64 core AMD EPYC 7601 nodes, running at 2.2 GHz, with 512GB of memory. These should be suitable for most of the GELIFES workloads. There is also quite a lot (16 TB) of **temporary** local scratch space per node, available for jobs through the use $TMPDIR in the jobs scripts. The node themselves are 64 core AMD EPYC 7601 nodes, running at 2.2 GHz, with 512GB of memory. These should be suitable for most of the GELIFES workloads. There is also quite a lot (16 TB) of **temporary** local scratch space per node, available for jobs through the use $TMPDIR in the jobs scripts.