What is Armis2?
Armis2 is an ARC-managed HPC cluster available for researchers who work with Protected Health Information (HIPAA). All computational work is scheduled via the Slurm resource manager and task scheduler, while data is kept on Turbo Research Storage. To request an allocation please contact email@example.com.
Who can use Armis2?
Armis2 is available for researchers at the University of Michigan who require HIPAA-compliant high performance computing. If you do not work with HIPAA data, your needs may be met by other ARC services (i.e., Great Lakes or Lighthouse).
- The Principal Investigator (PI) needs to email firstname.lastname@example.org for an account, specifying users that can access the account and payment details.
- Each user given access to the account must request a user login. Please refer to the Armis2 User Guide for additional steps and usage information.
Currently, there is no charge for using Armis2. Armis2 has an on-demand job model, paying for the resources your job uses, and there will be a rate applied on January 6th, 2020. For current prices, see the HPC rates page.
Principal Investigators can request that CPU, GPU, memory, billing units, and walltime be limited per user or group of users on their account. For more information, see the Armis2 policy documentation.
Limits must be requested by emailing email@example.com.
If you are a PI that hasn’t used Armis2 before, you are eligible for a limited trial account. This account will have $150 worth of cluster time (see the rates page) and will be unable to run jobs after 1 month. If interested, please contact firstname.lastname@example.org specifying that you’d like a trial account with lists of users and admins.
If you wish to pre-populate your SSH client configuration with the publicly available keys for Armis 2, they are as follows:
armis2.arc-ts.umich.edu,armis2-login?.arc-ts.umich.edu,188.8.131.52,184.108.40.206 ecdsa-sha2-nistp256 AAAAE2VjZHNhLXNoYTItbmlzdHAyNTYAAAAIbmlzdHAyNTYAAABBBHWel/rAXqIJYxexVzMSlgy/fICWukn8DaOGMPpAomH1E5AhCjrH2zMMTJHtXYsRA+brm/sTbn21Zw+pgpgJSYA=
armis2.arc-ts.umich.edu,armis2-login?.arc-ts.umich.edu,220.127.116.11,18.104.22.168 ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAICwaAq9LI48vVO4qbt35Xfz1pi+RE1Krq1iIeJQqoFEw
armis2.arc-ts.umich.edu,armis2-login?.arc-ts.umich.edu,22.214.171.124,126.96.36.199 ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAIEA16eDiBWF3SgPQXEeJsH8dsxO8x3o5KkdqWMg/lK57Kpwf4QGXJNvYy0jxSAuKTRim/ob6+nDRH8zIOwnl9tlyEw+8VN3WR8nqBqxX6Km2yzTOMO8Lh7fLuMTZHOdEz0uOn6tBP8LTMtHN9h/fANjKFVl8N+jsejMXrPf0w7jGjc=
On a Mac or Linux machine you’ll add the keys to your known_hosts file.
On a Mac this file is: /Users/<username>/.ssh/known_hosts.
On Linux: /home/<username>/.ssh/known_hosts.
The known_hosts file should have 644 (i.e. -rw-r--r--) permissions.
If you are using an SSH client that is not part of your operating system (e.g. Windows using PuTTY), please see the client documentation referring to host key verification.
A good start for PuTTY users can be found here (section A.2.9 “Is there an option to turn off the annoying host key prompts?)”
Any refunds (if any) are at the discretion of ARC and will only only be enacted during system-wide preventable issues. This does not include hardware failure, power failures, job failures, or similar issues. For more information, see the Armis2 policies.
If you have questions, please send email to email@example.com.