Migrating to Jetstream2 from Jetstream1

Jetstream 2 will support and encourages the migration of research from Jetstream1 (JS1) to the superior capabilities of Jetstream2 (JS2). In this section, we document information relative to that migration.

Jetstream 1 & 2 availability

Jetstream1 will remain online through the end of July 2022. We are no longer accepting any new allocations on Jetstream1 as Jetstream2 has entered operations phase.

There will be no extension beyond July 31 for Jetstream1. All allocations will be disabled and denied access at that time.

We strongly recommend users migrate to JS2 as soon as possible. VMs on JS1 will continue running as long as you have a valid allocation there BUT only until it is decommissioned. The TACC cloud of JS1 will likely be taken down in stages prior to the IU cloud.

What Researchers should know before migrating

Researchers on JS1 wishing to migrate to JS2 should take note of:

  1. Critical differences between JS2 and JS1 for:

  2. How to migrate from JS1 to JS2

Critical differences JS2 and JS1

Architecture

We highly recommend that you read about the key differences between the architecture of JS2 and JS1.

The biggest difference is that Jetstream2 will consist of one primary cloud (hosted at Indiana University) and multiple regional clouds, each with unique features and resources.

For Atmosphere users, you will be pleased to find that IP addresses are persistent, though we do ask you to return IP addresses to the pool whenever they are no longer needed, as they are a finite resource.

The JS1 IP pool and IP addresses ARE NOT transferable to JS2 at this time.

User Interfaces (UI)

Application Credentials

One important differences to note for our existing users is that we’ve enhanced our security profile and are using Application Credentials for our interfaces. Each user interface above has similar, but slightly different ways to access those Application Credentials, so please be aware, and carefully follow the instructions.

Important note for CLI users

Jetstream2 use of Application Credentials has expanded to include CLI access. This means CLI users well also authenticate using XSEDE credentials. Please see Setting up the openrc.sh for the Jetstream2 CLI for instructions generating application credentials and an openrc for Jetstream2.

Jetstream2 Software Collection

Rather than pack each and every virtual machine with research software, Jetstream2 has created a shared directory of packages that you can load and unload as desired using the LMOD system.

The use of the JS2 Software Collection is described here:
https://docs.jetstream-cloud.org/general/usingsoftware/#using-the-jetstream2-software-collection