Description
Jetstream2 LM 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. This particular portion of the resource is allocated separately from the primary resource and contains 32 nodes of GPU-ready 1TB RAM compute nodes, AMD Milan 7713 CPUs with 128 cores per node connected by 100gbps ethernet to the spine.
RP Description
Jetstream2 LM is a cloud VM service consisting of on-demand high-memory virtual machines in two flavors, r3.large at 64 vCPUs and 500 GB RAM and r3.xl at 128 vCPUs and 1000 GB RAM. It is particularly well suited for workloads that need more RAM than a standard CPU flavor provides, and is often used for high-RAM analytics, genomics, graph processing, and in-memory databases. It includes whatever software you install, alongside the Jetstream2 software collection.
Login Text
Jetstream2 Large Memory is accessed primarily through the Exosphere web interface. Users do not create a separate Jetstream2-specific user account. They need an ACCESS account and must be the PI of, or be added to, an active allocation that includes Indiana Jetstream2 Large Memory. Access to Jetstream2 CPU does not automatically provide access to the Large Memory resource.
In Exosphere, select Add allocation, choose Add ACCESS Account, select ACCESS CI (XSEDE) as the CILogon identity provider, sign in with ACCESS credentials, and select the allocation containing the Large Memory resource. ACCESS uses Duo for multi-factor authentication. Users who need to enroll in Duo or manage their authentication devices should follow the ACCESS Duo MFA instructions.
Jetstream2 does not provide a shared SSH login node. Users must first create a Large Memory virtual machine in Exosphere. To create an SSH key pair on a local Linux, macOS, or Windows OpenSSH system, run ssh-keygen -o -a 100 -t ed25519 -C "descriptive-label" -f ~/.ssh/id_ed25519. During instance creation, open the advanced options and select or upload the generated public key, normally ~/.ssh/id_ed25519.pub. Only the public key should be uploaded; the private key must not be shared.
Assign the instance a public IP address when direct SSH access is required. Exosphere-created instances use the exouser account. Connect with ssh -i ~/.ssh/id_ed25519 exouser@<PUBLIC_IP>. Users may alternatively connect through Exosphere Web Shell or Web Desktop.
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 LM 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 r3.large or r3.xl flavor, create a VM, and connect through Web Shell, Web Desktop, or SSH. Only r3.* flavors should be used on this resource. Applications run directly inside the VM, and you install software with the operating system's package manager, Python environments, containers, or the Jetstream2 software collection.
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].