hpc:access_the_hpc_clusters
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| hpc:access_the_hpc_clusters [2025/05/13 16:07] – [SSH tunnel and socks proxy] Yann Sagon | hpc: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 |
| - SSH key can be updated at any time: [[https:// | - SSH key can be updated at any time: [[https:// | ||
| - 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 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:// | **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:// | ||
| + | |||
| + | === multiple ssh key === | ||
| + | It is possible to register multiple SSH public keys on the authentication server. However, [[https:// | ||
| + | |||
| + | <WRAP center round important 60%> | ||
| + | After requesting an additional sshPublicKey, | ||
| + | </ | ||
| + | |||
| Line 346: | Line 370: | ||
| (baobab)-[alberta@cpu001 ~]$ | (baobab)-[alberta@cpu001 ~]$ | ||
| </ | </ | ||
| - | |||
| - | < | ||
| ===== Alternative to using ProxyJump ===== | ===== Alternative to using ProxyJump ===== | ||
| Line 365: | Line 387: | ||
| Usage: ssh cpu001 | Usage: ssh cpu001 | ||
| + | |||
| + | |||
| + | < | ||
| + | |||
| + | |||
| More Information on HPC-community forum: | More Information on HPC-community forum: | ||
hpc/access_the_hpc_clusters.1747152478.txt.gz · Last modified: (external edit)