The Daily Bulletin

May 23, 2019

CISL has released a pre-production implementation of the popular JupyterHub platform on the Cheyenne system. It is accessible at jupyterhub.ucar.edu with a valid Cheyenne user ID and YubiKey or Duo authentication.

As it is a pre-production offering, no documentation is available at this time for the installation, and CISL cannot guarantee its availability, robustness, or reliability. This JupyterHub instance will remain in a pre-production state for the lifetime of the Cheyenne cluster. A fully supported instance is expected to be available on the Cheyenne system’s successor, which is scheduled to be deployed in 2021.

After coming online earlier this year, NCAR's JupyterHub portal has been leveraged by several workshops, tutorials, and users with varying degrees of success. If you plan to employ JupyterHub in a workshop or tutorial, please notify CISL at cislhelp@ucar.edu at least one week in advance so we can provide the best possible experience and minimize potential issues.

May 17, 2019

A major Cheyenne operating system update has been scheduled for the last week of June while routine maintenance times scheduled for June 4, July 2, and August 6 have been canceled. The Cheyenne system will be unavailable from Monday, June 24, through Monday, July 1, as CISL staff update from SUSE Linux Enterprise Server (SLES) Service Pack 1 to SLES Service Pack 4. The update is required to bring the system up to current security and support levels and is expected to be the last operating system upgrade in Cheyenne’s lifetime.

During the update outage all of the Cheyenne cluster will be unavailable, including the system’s login nodes. The Casper cluster, GLADE file system, and HPSS will all be available through the recently deployed Casper login nodes. Users should also be aware that all cron services will be unavailable throughout the outage.

Most users’ programs and executables will need to be rebuilt following the update, as many system libraries will change. Most scripts should not require modifications but users are encouraged to thoroughly test their commonly used scripts after the system is returned to service.