What is the Globus preview environment?

Globus uses a separate environment, preview, for any new and upcoming changes in the Globus services that we would like users to test before it is released in production. Typically the services on preview are the same as the production system, but as needed updates and changes will be deployed for user testing. When such changes are made available on preview, an announcement is sent to developer-discuss.

The preview environment is completely isolated and separate from the Globus production service. Accounts and registered applications are not shared between production and preview. You will need to create and maintain separate accounts and registered applications for this environment.

Preview environment is available at https://preview.globus.org and other server information is below:

Web             https://preview.globus.org
Auth            auth.preview.globus.org
Transfer API    transfer.api.preview.globus.org
Globus ID       globusid.preview.globus.org
Developers      auth.preview.globus.org/developers

Cloning a production endpoint for use on preview

Below are the steps to clone a Globus Connect Server (GCS) endpoint that already exists in the production environment into the preview environment. Please note that only GCS host endpoints can be cloned - not shares or Globus Connect Personal endpoints.

  1. It is a prerequisite that the endpoint to be cloned already exist in the production environment and be functional there.

  2. Start by logging into the preview environment at the following URL: https://preview.globus.org

  3. After logging in, create a new endpoint definition in the preview environment via the following link: https://preview.globus.org/app/endpoints/create

  4. We recommend choosing a value for "Display Name" that clearly identifies which endpoint from production you are cloning, and that also makes clear that this endpoint definition is a clone - e.g. "Geosciences preview clone"

  5. Under the "Identity Provider" section you must copy verbatim what you see in the production environment in the Globus web interface Manage Endpoints "Servers" tab / "Identity Provider" section for the endpoint you are cloning.

  6. Under the "Servers" section you must copy verbatim what you see in the production environment in the Globus web interface Manage Endpoints "Servers" tab / "Servers" section for the endpoint you are cloning.

  7. Once you’ve created the endpoint clone, try using it to verify that it works.

Preview TCP Ports

Since preview hosts will be connecting to your endpoint, some ports must be open. Note that this is in addition to the normal GCS firewall policy requirements as noted here.

Port 2811 inbound from 107.20.144.193

  • Used for GridFTP control channel traffic.

Port 7512 inbound from 107.20.144.193

  • Used for MyProxy traffic.

  • Is needed only if your server is using a MyProxy service.

Using the CLI with the preview environment

To use the CLI with the preview environment you must set the GLOBUS_SDK_ENVIRONMENT environment variable to the value "preview". This tells the SDK the CLI is built on to make all API calls to the preview environment rather than defaulting to the production environment.

You will need to log in again to use the CLI on preview, but the CLI manages tokens per environment, so you can unset the the GLOBUS_SDK_ENVIRONMENT variable or use a separate terminal to go back to using the production environment without having to log in again.

Similarly, if you log out of one environment it will not log you out of the other, so make sure to log out of both environments separately when you are done.

For example, if you are using a bash shell you could log into the preview environment with these commands

$ export GLOBUS_SDK_ENVIRONMENT=preview
$ globus login

And then logout of each environment separately

$ globus logout
$ unset GLOBUS_SDK_ENVIRONMENT
$ globus logout