Jetstream2 CPU provides virtual machines running on AMD Milan 7713 CPU hosts. The physical CPU nodes provide 128 cores and 512 GiB RAM per node, connected by 100 Gbps Ethernet. Users create and manage their own virtual machines, making Jetstream2 suitable for interactive computing, software development, data analysis, custom research environments, and persistent services that do not fit traditional batch-scheduled HPC workflows.
Jetstream2 is particularly useful for researchers who need flexible control over their software stack, web-accessible services, cloud-style infrastructure, or always-on computing environments.
Jobs
Jetstream2 does not use a centralized job scheduler like Slurm. Instead, users run workloads directly on virtual machines that they create and manage.
Jobs are executed interactively or through scripts within the VM environment. For example:
python script.pyIf batch scheduling is required, users can deploy their own scheduler (e.g., Slurm, HTCondor, or Kubernetes) inside a virtual cluster.
Resources are allocated based on the size and runtime of virtual machine instances rather than queued jobs.
Jetstream2 CPU usage is charged based on the selected VM flavor and runtime. Larger flavors consume service units at a higher rate, and running instances continue to consume allocation SUs until they are shelved, stopped, or deleted.
Queue specifications
| Name | Purpose | CPUs | GPUs | RAM | Jobs
30 days
|
Wait Time
30-day trend
|
Wall Time
30-day trend
|
|---|---|---|---|---|---|---|---|
| Indiana Jetstream2 CPU | CPU-only virtual machine instances for interactive computing, software development, data analysis, custom research environments, and always-on services. | Physical hosts: 2 × AMD Milan 7713, 128 cores per node. VM flavors provide 1–128 vCPUs | Physical hosts: 512 GB per node. CPU VM flavors provide 3–500 GB RAM. | — | — | — |
Storage
File System
| Directory | Path | Quota | Purge | Backup | Notes |
|---|
External Storage
Storage Filesystems
Jetstream2 does not use traditional shared HPC file systems. Storage is associated with virtual machines and cloud storage services.
Instance Storage
- Local/root disk associated with the VM instance
- Useful for operating system files, installed software, temporary data, and runtime files
- Not a substitute for persistent project storage
Persistent Volumes
- Block storage that can be attached to a VM
- Can be detached and reattached to instances
- Generally attached to one active instance at a time
- Useful for persistent datasets, software environments, and project data
Typical Exosphere mount path: /media/volume/<volume-name>
File Shares
- Shared networked storage using OpenStack Manila
- Can be mounted by multiple instances
- Useful for collaborative datasets and multi-instance workflows
- In Exosphere, file shares are currently presented as an experimental feature
Typical Exosphere mount path: /media/share/<share-name>
Object Store
- S3-compatible object storage
- Useful for web applications, public data hosting, and cloud-native workflows
- Accessible without mounting a traditional filesystem
File Transfer
Jetstream2 does not use dedicated data transfer nodes. File transfers are typically performed directly between the user’s local machine and a Jetstream2 virtual machine, or through web-based transfer tools.
Common transfer methods include the Exosphere web shell/web desktop file-transfer interface, SCP/SFTP to a VM with a public IP address, and Globus for larger or managed transfers. The best method depends on file size, whether the VM has a public IP address, and whether the user is transferring data from a local machine, another endpoint, or another digital resource.
| Supported Methods | Data Transfer Node | URL |
|---|---|---|
| GLOBUS | RECOMMENDED | https://www.globus.org/data-transfer | |
| SCP | ||
| SFTP |
Login to Jetstream2 CPU
Jetstream2 is primarily accessed through the Exosphere web interface. Users log in with ACCESS credentials through CILogon, select the appropriate ACCESS allocation, and then create and manage virtual machine instances.
ACCESS login through CILogon may require multi-factor authentication. Users must have an active Jetstream2 allocation before creating or using Jetstream2 resources.
After logging in, users can launch virtual machines, manage storage volumes and shares, view instance IP addresses, access web shells or web desktops, and configure SSH access to their instances.