Getting Started Overview
This section covers everything you need to get started with the Odin HPC cluster.
Prerequisites
Before you can access the Odin cluster, you’ll need:
- VPN connection (if required by your AWS environment)
- SSH key pair (your private key matching the public key in
users.yaml) - User account configured in
odin/terraform/users.yaml
Quick Start
- Set up your SSH key - Ensure your private key is in
~/.ssh/with proper permissions - Configure SSH - Add the cluster hosts to your
~/.ssh/config - Connect - SSH to the jump host, then to login nodes
Infrastructure Overview
| Component | Hostname | Purpose |
|---|---|---|
| Jump Host | jump.odin.navify.com |
Secure gateway (bastion) |
| Login Node 1 | login1.odin.cluster.local |
Interactive sessions, job submission |
| Login Node 2 | login2.odin.cluster.local |
Interactive sessions, job submission |
| Data Manager (Linux) | data-manager-linux.odin.cluster.local |
GxP data management, Samba gateway |
| Data Manager (Windows) | data-manager-windows.odin.cluster.local |
Windows data management |
Key Concepts
Login Nodes vs Head Node
⚠️ Important: Always use login nodes for interactive work, job submission, and VS Code Remote sessions. The head node is reserved for SLURM scheduler operations only and has limited memory (4GB).
User Accounts
Odin uses per-user accounts managed through users.yaml:
- Each user has their own UNIX account
- SSH public keys are deployed to all instances
- Users can access login nodes, data managers, and submit jobs
Storage Mounts
All login nodes and compute nodes have access to:
/mnt/odin- 12TB FSx Lustre (legacy data)/mnt/qcs- 1.2TB FSx Lustre (Navify data)/mnt/shared- EBS shared storage/home- EFS home directories
Next Steps
- SSH Setup - Configure your SSH client
- User Management - How user accounts work
- Cluster Access - Connect to the cluster