Google Life Sciences
This guide assumes you have an existing Google Cloud Account. Sign-up for a free account here.
Tower provides integration to Google Cloud via the Cloud Life Sciences API.
The guide is split into two parts:
How to configure your Google Cloud account to use the Cloud Life Sciences API.
How to create a Google Life Sciences compute environment in Tower.
Configure Google Cloud#
Create a project#
Navigate to the Google Project Selector page and either select an existing project or select Create project.
Enter a name for your new project, e.g "tower-nf".
If you are part of an organization, the location will default to your organization.
In the navigation menu (≡), select Billing. You can follow these instructions to enable billing.
Use this link to enable the following APIs for your project:
- Cloud Life Sciences API
- Compute Engine API
- Cloud Storage API
Select your project from the dropdown menu and select Enable.
Alternatively, you can enable each API manually by selecting your project in the nav bar and visiting each API page:
Create service account key#
In the navigation menu, select IAM & Admin and then Service Accounts.
Select the email address of the Compute Engine default service account.
Select Keys, then Add key, then Create new key.
Select JSON as the key type.
A JSON file will be downloaded to your computer. This file contains the credential that will be used by Tower. You will need it to configure the compute environment in Tower.
You can manage your key from the Service Accounts page.
Create a Cloud Storage bucket#
In the navigation menu (≡), select Cloud Storage and then Create bucket.
Enter a name for your bucket. You will reference this name when creating the compute environment in Tower.
Do not use underscores (
_) in your bucket name. Use hyphens (
Select Region for the Location type and select the Location for your bucket. You will reference this location when creating the compute environment in Tower.
Select Standard for the default storage class.
Select Uniform for the Access control.
The Cloud Life Sciences API is available in a limited number of locations. However, these locations are only used to store metadata about the pipeline operations. The storage bucket and compute resources can be in any region.
Once the bucket is created, you will be redirected to the Bucket details page.
Select Permissions, then + Add.
Copy the email address of the Compute Engine default service account into New principals.
Select the following roles:
- Storage Admin
- Storage Legacy Bucket Owner
- Storage Legacy Object Owner
- Storage Object Creator
The following guide to configure Tower assumes you have (1) a service account key for a Google Cloud account and (2) the name and location of a Cloud Storage bucket.
To create a new compute environment for Google Cloud in Tower:
In a workspace, select Compute Environments and then New Environment.
Enter a descriptive name for this environment, e.g. "Google Life Sciences (europe-west2)".
Select Google Life Sciences as the target platform.
From the Credentials drop-down, select existing Google Cloud credentials, or add new credentials by selecting the + button. If you select to use existing credentials, skip to step 7.
Enter a name for the credentials, e.g. "Google Cloud Credentials".
Enter the Service account key for your Google Cloud account. This key was created in the previous section.
You can create multiple credentials in your Tower workspace.
Container registry credentials
From version 22.3, Tower supports the use of credentials for container registry services. These credentials can be created from the Credentials tab.
Select the Region and Zones where you'd like to execute pipelines.
You can leave the Location empty and the Cloud Life Sciences API will use the closest available location.
Enter your bucket URL for the Pipeline work directory. The URL is the name of your bucket with the
This bucket should be accessible in the region selected in the previous step.
You can enable Preemptible to use preemptible instances, which have significantly reduced cost compared to on-demand instances.
You can use a Filestore file system to automatically mount a Google Filestore volume in your pipelines.
You can use the Environment variables option to specify custom environment variables for the Head job and/or Compute jobs.
Configure any advanced options described below, as needed.
Select Create to finalize the compute environment setup.
Jump to the documentation for Launching Pipelines.
You can enable Use Private Address to ensure that your Google Cloud VMs aren't accessible to the public internet.
You can use Boot disk size to control the boot disk size of VMs.
You can use Head Job CPUs and Head Job Memory to specify the CPUs and memory allocated for head jobs.