Trace: • iscinventory

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
infra:howto:runjob [2025/03/11 17:06] – [Cleaning] remiinfra:howto:runjob [2026/03/11 10:25] (current) – [Quotas] marc
Line 10: Line 10:
  
  
 +===== Connection =====
 +Currently, you have to SSH directly on one of the compute node, either server [[infra:chacha|Chacha]] or [[infra:disco|Disco]] :
 +
 +  $ ssh firstname.lastname@disco.hevs.ch
 +  $ ssh firstname.lastname@chacha.hevs.ch
 +  
 +** NOTE : Please note you have to connect from the school network or the HEVS VPN to be able to connect on those servers **
 +
 +TODO : Change doc when the jump host will be ready
  
 ===== Environment ===== ===== Environment =====
  
-On either server [[infra:chacha|Chacha]] or [[infra:disco|Disco]], you have a symlink **datasets** in your home directory that is linked to the local storage of the server : its purpose is to give you a proper space to put all the data you will be working on.+ 1. On either server [[infra:chacha|Chacha]] or [[infra:disco|Disco]], you have a symlink **datasets** in your home directory that is linked to the local storage of the server : its purpose is to give you a proper space to put all the data you will be working on.
  
-You have also another symlink **shared_dataset** for jobs that needs to be run on several nodes : this filesystem is shared between nodes.+ 2. You have also another symlink **shared_dataset** for jobs that needs to be run on several nodes : this filesystem is shared between nodes.
  
 + 3. Your .bashrc / .zshrc contains by default the variable **APPTAINER_TMPDIR** set to **/home/user.name/.apptainer/** : this allows you to build containers without using the system /tmp that is restricted with a low quota, and use your larger dataset quota instead.
  
-NOTE : By default, you are the only one seeing your data : If you are working as a team on these data, **please ask for a group creation** so we can add members in it and apply suitable permissions.+ 4. By default, you are the only one seeing your data : If you are working as a team on these data, **please ask for a group creation** so we can add members in it and apply suitable permissions.
  
  
Line 37: Line 47:
  
  
 +
 +More information on our **[[infra:compute:slurmconfig|SLURM cluster]]**
 ===== Storage considerations ===== ===== Storage considerations =====
  
Line 70: Line 82:
 ==== Quotas ==== ==== Quotas ====
   - The root filesystem (/, including /home) for every researchers is 20GB for convenience. For students, this quota is lowered to 10GB to encourage proper infrastructure usage / coding with a lower threshold.   - The root filesystem (/, including /home) for every researchers is 20GB for convenience. For students, this quota is lowered to 10GB to encourage proper infrastructure usage / coding with a lower threshold.
-  - On local and shared datasets, quota is set accordingly to what was requested during the access creation : either the direct value from the [[https://forms.office.com/e/zRkBFAbKD7|Access Form]] or it can be a lower quota depending on our current capacity. +  - On local and shared datasets, quota will be set on a case by case basis
  
 ==== Cleaning ==== ==== Cleaning ====
Line 88: Line 100:
    * [[https://learn.microsoft.com/en-us/answers/questions/1221136/visual-studio-2022-clear-local-caches]]    * [[https://learn.microsoft.com/en-us/answers/questions/1221136/visual-studio-2022-clear-local-caches]]
   - Currently your vscode caches are automatically removed from our servers.   - Currently your vscode caches are automatically removed from our servers.
 +
 +==== Automation ====
 +
 +If you need to use Cron to schedule something, you need to ask for your user to be added to the /etc/cron.allow whitelist.
Back to top