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
pub:hpc:mill [2025/01/15 18:27] – [DOI] jonesjoshpub:hpc:mill [2025/12/22 16:05] (current) – [SSH Keys] dbwkp
Line 1: Line 1:
 ====== The Mill ====== ====== The Mill ======
 ===== Request an account ===== ===== Request an account =====
-You can request an account on the Mill by filling out the form found at https://missouri.qualtrics.com/jfe/form/SV_e5n4I8cvzo77jr8+You can request an account on the Mill by filling out the account request form at help.mst.edu in the HPC Cluster category:[[https://tdx.umsystem.edu/TDClient/48/Portal/Requests/TicketRequests/NewForm?ID=PEUIinShX0k_&RequestorType=Service|help.mst.edu]] 
 + 
 + 
 +===== SSH Keys ===== 
 + 
 +If you want to connect using SSH keys, either to avoid having to type in your password, or are wanting to connect from off campus without a VPN, you can add your SSH public key to Mill. 
 + 
 +For Windows users, we recommend using MobaXterm https://mobaxterm.mobatek.net. Powershell, git bash, and putty are some other available options. Mac and Linux users can use the default terminal. 
 +Generating an SSH Key 
 + 
 +You can generate a new SSH key on your local machine. After you generate the key, you can add the public key to your account on Mill. 
 + 
 +    Open terminal 
 +    Paste the text below, replacing the email used in the example with your University email address. 
 + 
 +ssh-keygen -t ed25519 -C "sso@example.com
 + 
 +    Note: If you are using a legacy system that doesn't support the Ed25519 algorithm, use: 
 + 
 +    ssh-keygen -t rsa -b 4096 -C "sso@example.com" 
 + 
 +This creates a new SSH key, using the provided email as a label. 
 + 
 +Generating public/private ALGORITHM key pair. 
 + 
 +When you're prompted to “Enter a file in which to save the key”, you can press Enter to accept the default file location. Please note that if you created SSH keys previously, ssh-keygen may ask you to rewrite another key, in which case we recommend creating a custom-named SSH key. To do so, type the default file location and replace id_ALGORITHM with your custom key name. 
 + 
 +# Windows 
 +Enter file in which to save the key (/c/Users/USERNAME/.ssh/id_ALGORITHM):[Press enter] 
 +# Mac 
 +Enter a file in which to save the key (/Users/USERNAME/.ssh/id_ALGORITHM): [Press enter] 
 +# Linux 
 +Enter a file in which to save the key (/home/USERNAME/.ssh/id_ALGORITHM):[Press enter] 
 + 
 +    At the prompt, type a secure passphrase. 
 + 
 +Enter passphrase (empty for no passphrase): [Type a passphrase] 
 +Enter same passphrase again: [Type passphrase again] 
 + 
 +Adding your SSH key 
 + 
 +You may add your own SSH public key to your Mill account. You can also send the key to tdx.umsystem.edu  and we can add it to your Mill account. 
 + 
 +    Copy the contents of your SSH public key, which is written to the file created in the Generating an SSH Key step. 
 + 
 +# Windows 
 +Your public key has been saved in /c/Users/USERNAME/.ssh/id_ALGORITHM.pub 
 +# Mac 
 +Your public key has been saved in /Users/USERNAME/.ssh/id_ALGORITHM.pub 
 +# Linux 
 +Your public key has been saved in /home/USERNAME/.ssh/id_ALGORITHM.pub 
 +# Windows 
 + 
 +    The id_ALGORITHM.pub file contents should look similar to the ones below. 
 + 
 +# ed25519 
 +ssh-ed25519 AAAAB3NzaC1yc2EAAAABIwAAAQEAklOUpkDHrfHY17SbrmTIpNLTGK9Tjom/BWDSUGP truman@example.com 
 + 
 +# rsa 
 +ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEAklOUpkDHrfHY17SbrmTIpNLTGK9Tjom/BWDSUGPl+nafzlHDTYW7hdI4yZ5ew18JH4JW9jbhUFrviQzM7xlELEVf4h9lFX5QVkbPppSwg0cda3Pbv7kOdJ/MTyBlWXFCR+HAo3FXRitBqxiX1nKhXpHAZsMciLq8V6RjsNAQwdsdMFvSlVK/7XAt3FaoJoAsncM1Q9x5+3V0Ww68/eIFmb1zuUFljQJKprrX88XypNDvjYNby6vw/Pb0rwert/EnmZ+AW4OZPnTPI89ZPmVMLuayrD2cE86Z/il8b+gw3r3+1nKatmIkjn2so1d01QraTlMqVSsbxNrRFi9wrf+M7Q== truman@example.com 
 + 
 +    Add your public key to your account by appending it to your authorized_keys file on Mill 
 + 
 +[sso@mill-login ~]$ vim /home/sso/.ssh/authorized_keys 
 + 
 +    OR send us your public key. 
 + 
 ===== System Information ===== ===== System Information =====
-====DOI====+====DOI and Citing the Mill====
 Please ensure you use The Mill's DOI on any publications in which The Mill's resources were utilized. The DOI is https://doi.org/10.71674/PH64-N397 Please ensure you use The Mill's DOI on any publications in which The Mill's resources were utilized. The DOI is https://doi.org/10.71674/PH64-N397
 +
 +Please also feel free to use these files with your citation manager to create formatted citations.
 +
 +BibTex Citation:
 +<file bib mill_cluster_citation.bib>
 +@Article{Gao2024,
 +  author    = {Gao, Stephen and Maurer, Jeremy and Information Technology Research Support Solutions },
 +  title     = {The Mill HPC Cluster},
 +  year      = {2024},
 +  doi       = {10.71674/PH64-N397},
 +  language  = {en},
 +  publisher = {Missouri University of Science and Technology},
 +  url       = {https://scholarsmine.mst.edu/the-mill/1/},
 +}
 +</file>
 +RIS Citation:
 +<file ris mill_cluster_citation.ris>
 +TY  - JOUR
 +AU  - Stephen, Gao
 +AU  - Jeremy, Maurer
 +AU  - Solutions, Information Technology Research Support
 +DO  - 10.71674/PH64-N397
 +LA  - en
 +PU  - Missouri University of Science and Technology
 +PY  - 2024
 +ST  - The Mill HPC Cluster
 +TI  - The Mill HPC Cluster
 +UR  - https://scholarsmine.mst.edu/the-mill/1/
 +ER  - 
 +</file>
 ==== Software ==== ==== Software ====
 The Mill was built and managed with Puppet. The underlying OS for the Mill is Alma 8.9. For resource management and scheduling we are using SLURM Workload manager version 22.05.2 The Mill was built and managed with Puppet. The underlying OS for the Mill is Alma 8.9. For resource management and scheduling we are using SLURM Workload manager version 22.05.2
Line 24: Line 121:
 | Model | CPU Cores | System Memory | Node Count |  | Model | CPU Cores | System Memory | Node Count | 
 | Dell R6525 | 128 | 512 GB | 25 |  | Dell R6525 | 128 | 512 GB | 25 | 
-| Dell C6525 | 64 | 256 GB | 159 |+| Dell C6525 | 64 | 256 GB | 160 |
 | Dell C6420 | 40 | 192 GB | 44 |  | Dell C6420 | 40 | 192 GB | 44 | 
  
Line 51: Line 148:
 The Mill home directory storage is available from an NFS share backed by our enterprise SAN, meaning your home directory is the same across the entire cluster. This storage will provide 10 TB of raw storage, limited to 50GB per user. **This volume is not backed up, we do not provide any data recovery guarantee in the event of a storage system failure.** System failures where data loss occurs are rare, but they do happen. All this to say, you ** should not ** be storing the only copy of your critical data on this system. Please contact us if you require more storage and we can provide you with the currently available options. The Mill home directory storage is available from an NFS share backed by our enterprise SAN, meaning your home directory is the same across the entire cluster. This storage will provide 10 TB of raw storage, limited to 50GB per user. **This volume is not backed up, we do not provide any data recovery guarantee in the event of a storage system failure.** System failures where data loss occurs are rare, but they do happen. All this to say, you ** should not ** be storing the only copy of your critical data on this system. Please contact us if you require more storage and we can provide you with the currently available options.
  
-==Scratch Directories==+==Scratch Directories== 
  
-High speed network scratch is not yet available at the time of writing+In addition to your 50GB home directory, you also have access to a high-performance network-mounted scratch storage space. This is meant for temporary storage of files that are currently being used for computations, not for anything resembling permanent or project storage. If there are intermediate results or files that you need to store between jobs that you will submit back-to-back, this is a good place to store such things. To change directory to this storage you can use the “cdsc” command which we have provided for ease of use. The path for this area is “/share/ceph/scratch/$USER” where $USER is the username you use to log in to the Mill. We may clean this space during maintenance and reserve the right to clean it immediately if that becomes necessary for continued quality of service, so make sure you are not storing anything there that you cannot afford to lose, or do not have backed up elsewhere
  
-There is always local scratch on each compute node for use during calculations in /local/scratch. On the Mill this is 1.5TB in size. There is no quota placed on this spaceand it is cleaned regularly as well, but things stored in this space will only be available to processes executing on the node in which they were created. Meaning if you create it in /local/scratch in a job, you won't be able to see it on the login node, and other processes won't be able to see it if they are on a different node than the process which created the file. +There is also local scratch on each compute node for use during calculations in /local/scratch. On the Mill this is 1.5TB in size. If you use this space we request that you add a cleanup command to your job to delete your files at the end of your job and make sure the space remains available for others. Things stored in this space will only be available to processes executing on the node in which they were created. Meaning if you create it in /local/scratch in a job, you won't be able to see it on the login node, and other processes won't be able to see it if they are on a different node than the process which created the file. 
  
 ==Leased Space== ==Leased Space==
  
-If home directory, and scratch space availability aren't enough for your storage needs we also lease out quantities of cluster attached space. If you are interested in leasing storage please contact us. Below is a cost model of our storage offerings:+If home directory, and scratch space availability aren't enough for your storage needs we also lease out quantities of cluster attached space. If you are interested in leasing storage please contact us. Additional information on the STRIDE storage allocations can be found here [[https://mailmissouri.sharepoint.com/:b:/s/MUandSTITRSS-Ogrp/EVgQcegipVtPgs4Rc9tcqAcBxWf2qEXeZawWYSrco7sKpQ|STRIDE storage model]].  
 +Below is a cost model of our storage offerings:
  
 Vast Storage Cluster: Vast Storage Cluster:
Line 96: Line 194:
 | general | 2 days | 800MB| | general | 2 days | 800MB|
 | gpu     | 2 days | 800MB| | gpu     | 2 days | 800MB|
 +| interactive | 4 hours | 800MB|
 +| rss-class | 4 hours | 2GB |
 | any priority partition | 28 days | varies by hardware| | any priority partition | 28 days | varies by hardware|