eResearch Doc

User Tools

Site Tools

You are here: start » hpc » access_the_hpc_clusters
hpc:access_the_hpc_clusters

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
hpc:access_the_hpc_clusters [2025/04/30 08:03] – Adrien Alberthpc:access_the_hpc_clusters [2025/12/17 15:06] (current) – [Inactivity Notice and Account Deletion Policy] Adrien Albert
Line 40: Line 40:
  
 **Key details:** **Key details:**
-  - Authentication is done via the SSH key (only) provided during the invitation process  +  - Authentication is done via the SSH Public Key (only) provided during the invitation process  (Authentication with password is disabled)
   - SSH key can be updated at any time: [[https://applicant.unige.ch/main/outsider-info/update|Update your SSH key]]     - SSH key can be updated at any time: [[https://applicant.unige.ch/main/outsider-info/update|Update your SSH key]]  
   - SSH key updates are applied daily at 1:30 PM and 5:00 AM via the UNIGE Active Directory   - SSH key updates are applied daily at 1:30 PM and 5:00 AM via the UNIGE Active Directory
Line 58: Line 58:
  
 Once invited, the future Outsider will receive an email with detailed instructions to finalize their registration.   Once invited, the future Outsider will receive an email with detailed instructions to finalize their registration.  
-(*Tip: read it carefully!*)+(**Tip: read it carefully!**)
  
 **To renew an expired Outsider account, a new invitation must be created.** **To renew an expired Outsider account, a new invitation must be created.**
Line 72: Line 72:
 Users will receive an email notification prior to the scheduled deletion of their account, giving them the opportunity to log in and keep their account active. If no response is received within one month, the account will be deleted, along with all associated data. Users will receive an email notification prior to the scheduled deletion of their account, giving them the opportunity to log in and keep their account active. If no response is received within one month, the account will be deleted, along with all associated data.
  
 +**Users no more at Unige:**
 +
 +In the middle of each month, an automated process is triggered to identify all accounts that are no longer listed in the University of Geneva (UNIGE) electronic directory.
 +An account that is no longer listed indicates that the individual has left UNIGE.
 +
 +These accounts are automatically flagged for deletion in the current end-of-month deletion batch.
 +At the end of the month, the account and all associated data are permanently deleted.
 +
 +__**Example:**__
 +
 +   * **15 January 2025**: Check Account 
 +      * Dark Vador is no longer listed in the UNIGE directory. => Tagged for deletion
 +
 +
 +   * **31 January 2025**: Batch deletion
 +      * Dark Vador’s account and associated data are removed.
 ===== Cluster connection ===== ===== Cluster connection =====
 Once you have received an email confirming the creation of you account, you have access to our clusters: Baobab and Yggdrasil. Once you have received an email confirming the creation of you account, you have access to our clusters: Baobab and Yggdrasil.
Line 110: Line 126:
  
 **Note**: Make sure you copy the public ssh key linked to the private key you're going to use. If you have regenerated your ssh key, you'll need to put your public key in [[https://my-account.unige.ch|my-account]] or [[https://applicant.unige.ch/main/outsider-info/update|applicant]] **Note**: Make sure you copy the public ssh key linked to the private key you're going to use. If you have regenerated your ssh key, you'll need to put your public key in [[https://my-account.unige.ch|my-account]] or [[https://applicant.unige.ch/main/outsider-info/update|applicant]]
 +
 +=== multiple ssh key ===
 +It is possible to register multiple SSH public keys on the authentication server. However, [[https://my-account.unige.ch/|my-account.unige.ch]] does not allow this at the moment (work in progress). In the meantime, please send your request to the LDAP team directly at dl-distic-windows-team@unige.ch.
 +
 +<WRAP center round important 60%>
 +After requesting an additional sshPublicKey, if you update it via my-account, all previous references will be overwritten.
 +</WRAP>
 +
  
  
Line 265: Line 289:
   (baobab)-[alberta@login1 ~]$ /usr/bin/sss_ssh_authorizedkeys $USER   (baobab)-[alberta@login1 ~]$ /usr/bin/sss_ssh_authorizedkeys $USER
   ssh-rsa  [...]   ssh-rsa  [...]
 +
 +Only for tunneling: Once the configured you MUST save this SSHpublicKey in your ssh_authorizedkeys on Cluster. 
 +
 +  $ ssh-copy-id <ssh.pub> <users>@login1.<cluster>.hpc.unige.ch
  
 **3.** On your local machine configure the proxyjump: **3.** On your local machine configure the proxyjump:
Line 342: Line 370:
 (baobab)-[alberta@cpu001 ~]$ (baobab)-[alberta@cpu001 ~]$
 </code> </code>
 +
 +===== Alternative to using ProxyJump =====
 +
 +ProxyJump doesn't work with host based authentication, this is the reason why you need to use a ssh key in the previous setup. The reason is because ProxyJump doesn't open a real ssh session and thus the ssh-keysign isn't run when you connect. Instead of using ProxyJump, you can proceed as follow:
 +
 +<code>
 +Host baobab
 +    HostName login1.baobab.hpc.unige.ch
 +    User <youruser>
 +    
 +Host cpu*
 +    HostName %h
 +    User <youruser>
 +    ProxyCommand ssh -tt baobab ssh %r@%h
 +</code>
 +
 +Usage: ssh cpu001
 +
  
 <note> <note>
 +
 +
 +
 More Information on HPC-community forum: More Information on HPC-community forum:
  
hpc/access_the_hpc_clusters.1746000233.txt.gz · Last modified: (external edit)