Description
Jetstream2 is a hybrid-cloud platform that provides flexible, on-demand, programmable cyberinfrastructure tools ranging from interactive virtual machine services to a variety of infrastructure and orchestration services for research and education. The primary resource is a standard CPU resource consisting of AMD Milan 7713 CPUs with 128 cores per node and 512gb RAM per node connected by 100gbps ethernet to the spine.
RP Description
Jetstream2 CPU is a cloud VM service consisting of on-demand virtual machines in flavors from m3.tiny at 1 vCPU and 3 GB RAM to m3.3xl at 128 vCPUs and 500 GB RAM. It is particularly well suited for interactive computing and long-running services rather than batch work, and is often used for software development, data analysis, custom research environments, and persistent hosted services. It includes whatever software you install - you manage the VM operating system, software stack, storage attachments, and runtime configuration yourself.
Login Text
Full instructions are in [Jetstream2 User Interfaces]. Jetstream2 CPU has no shared login node - you reach a machine by creating a virtual machine yourself. Exosphere is the recommended interface and the one these instructions assume; Jetstream2 also supports other OpenStack interfaces if you prefer one. Before your first sign-in:
- You need an ACCESS account, and you must be the PI of - or be added to - an active allocation that includes Indiana Jetstream2 CPU.
- There is no separate Jetstream2 account. Sign in with your ACCESS credentials, choosing ACCESS CI (XSEDE) as the CILogon identity provider.
- ACCESS uses Duo for multi-factor authentication. To enroll or manage your devices, see [Enroll in or manage ACCESS Duo MFA].
Instances created through Exosphere use the exouser account. Once an instance has a public IP address you can connect through Web Shell, Web Desktop, or SSH.
File Transfer Text
Jetstream2 does not use dedicated data transfer nodes. Files are transferred directly to and from VM instances or through web-based and managed transfer tools.
Common 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. See the [Jetstream2 File Transfer] for guidance.
Storage Text
Jetstream2 provides cloud storage associated with virtual machine instances rather than a traditional shared HPC filesystem. Instances may use ephemeral or volume-backed root disks. Data on an ephemeral root disk is permanently removed when the instance is deleted; retention of a volume-backed root disk depends on the instance's delete-volume setting.
Persistent storage options include block volumes, OpenStack Manila file shares, and S3-compatible object storage. Volumes can be attached to one instance at a time, Manila shares can be mounted by multiple instances, and object storage can be accessed through S3-compatible tools or HTTP. All Jetstream2 allocations receive 1 TB (1000 GB) of storage quota by default; additional storage can be requested through the Indiana Jetstream2 Storage resource.
Jobs Information
Jetstream2 CPU is a cloud virtual-machine resource, not a centrally scheduled Slurm cluster. There is no shared login node and no Slurm queue, partition, sbatch, srun, or squeue workflow. Slurm commands apply only if your project separately deploys and administers its own virtual cluster.
Select an m3.* CPU flavor, create a VM, and connect through Web Shell, Web Desktop, or SSH. Applications run directly inside the VM, and you install software with the operating system's own package manager. The m3.3xl flavor is not available by default and requires a justified request to Jetstream2 support.
Resource use is determined by the flavor you select and how long the instance stays active. An active instance consumes service units even when no application is running. Shelve an instance when you are not using it; a shelved instance consumes zero compute SUs.
See [Jetstream2 Instance Flavors] and [Jetstream2 Instance Management and SU Conservation].