RC_Z

We are releasing RC_Z to FireCloud production on 2019-04-11.

This release includes the following Leo issues:
RC_Z_2019-04-11

• (#852) Fix leo automation test failures
  • Addresses some intermittent auto-test failures. Not user facing.
• (#838) Upgrade Hail to 2.11.
  • User facing. See Hail change log for release notes.
• (#831) "Permission denied" attempting to install JupyterLab extension
  • User facing. Fixes an error when trying to install JupyterLab extensions.
• (#824) Jupyter terminal times out after a couple of minutes
  • User facing. The terminal should no longer time out.
• (#806) Verify required permission for Leo SA
  • Not user facing. Verified the permissions needed for the Leo service account. See ticket for details.
• (#704) Have workspace bucket name available via an environment variable
  • User facing. Users can now access WORKSPACE_NAMESPACE, WORKSPACE_NAME, and WORKSPACE_BUCKET environment variables from within a notebook.

RC_W

We are releasing RC_W to FireCloud production on 2019-03-19.

This release includes the following Leo issues:
RC_W_2019-03-19

• #732: Enable NewRelic in Leonardo
  • Not user facing: enables NewRelic in production for improved monitoring.
• #771: Clusters with only RStudio on them get stuck in Starting status
  • Not user facing: RStudio bug fix
• #525: Add leo automation test to create and run a notebook in jupyterlab
  • Not user facing: add integration testing for JupyterLab

RC_U

We are releasing RC_U to FireCloud production on 2019-03-12.

This release includes the following Leo issues:
RC_U_2019-03-12

• #777 Update Hail to the latest
  • User facing: Upgrades Hail to 0.2.10. Requires a cluster rebuild to take effect.
• #768 Delete staging bucket after cluster is deleted
  • User facing: We now set a lifecycle policy on clusters' staging buckets after the cluster is deleted. This helps control storage costs in users' billing projects.
• #819 Upgrade jackson to 2.9.8 to address CVE reports
  • Not user facing: upgrades Jackson to close a security hole
• #801 Install python dev libs and pip by default in RStudio image
  • Not user facing: RStudio prep work
• #753 Update rstudio-docker-compose.yaml to create the volume at container start
  • Not user facing: RStudio prep work

RC_T

We are releasing RC_T to FireCloud production on 2019-03-06.

This release includes the following Leo issues:
RC_T_2019-03-06

• #797: User cannot import ggplot using python 2 kernel
  • User facing: Fixes ggplot using python 2 kernel.
• #788: Implement fix for Apache CPU hogging
  • Performance bugfix leading to apache hogging CPU
• RStudio prep work
  • Not yet exposed through public API

RC_S2

(Yes, we had 2 RC_S releases in a row.)

We are releasing RC_S to FireCloud production on 2019-02-27.

This release includes the following Leo issues:
RC_S_2019-02-27

• #770: Token refresh not working from JupyterLab
  • Fixes a bug where users' JupyterLab sessions would expire, forcing them to periodically refresh to reauthenticate.
• #742: JupyterLab Extension From Single File
  • Adds support for providing JupyterLab extensions as a single js or ts file. (This was an ask by Terra UI.)

RC_S

We are releasing RC_S to FireCloud production on 2019-02-19.

This release includes the following Leo issues:
RC_S_2019-02-19

• #774: Upgrade Docker version that we install on hosts and upgrade existing nodes
  • Patches a security vulnerability in the Docker that runs on users' clusters.
• #751: Install gcsfuse on clusters by default (install it on all of them)
  • Not user facing. Begins to lay some infrastructure for RStudio.
• #746: Horizontal scaling
  • User facing. Leo will now run on multiple machines, allowing for better performance and reliability.
• #745: Leo should recursively copy extensions
  • User facing. Allows callers to specify JupyterLab extensions as a GCS prefix instead of a tar file. (This was an AoU ask.)
• #776: More efficient database unmarshaling in Leo
  • User facing. Fixes a performance issue that led to high CPU on Leo machines, manifesting as slowness to the end user.

RC_R

We are releasing RC_R to FireCloud production on 2019-02-05.

This release includes the following Leo issues:
RC_R_2019-02-05

• #733: ClusterMonitor should not monitor clusters in Error status
  • User facing. Fixes a bug where certain types of Google errors could cause clusters to spin in Creating status indefinitely. Now the appropriate error message will be returned to the user.

RC_Q

We are releasing RC_Q to FireCloud production on 2019-01-29.

This release includes the following Leo issues:
RC_Q_2019-01-30

• #758: Python Dependency Issue
• #761: Build python 3.6 from source instead of pulling from debian testing repo
  • Fixes the method by which we install python 3.6.8 on the cluster. Not user facing.
• #762: Make dataproc zone configurable
  • Adds the ability to control the zone clusters are deployed in. Done to work around a Google issue with insufficient quota in certain zones. Not user facing.

More details about both in a post mortem to follow.

RC_P

We are releasing RC_P to FireCloud production on 2019-01-28.

This release includes the following Leo issues:
RC_P_2019-01-28

• #565: Deploy front/back Leos
• #743: Fix run-jupyter-local.sh

Neither is user facing.

RC_O

We are releasing RC_O to FireCloud production on 2019-01-22.

This release includes the following Leo issues:
https://github.com/DataBiosphere/leonardo/labels/RC_O_2018-01-22

• #595: Leo now supports JupyterLab extensions