Running in Google Compute Engine (GCE)

Toil supports a provisioner with Google, and a Google Job Store. To get started, follow instructions for Preparing your Google environment.

Preparing your Google environment

Toil supports using the Google Cloud Platform. Setting this up is easy!

  1. Make sure that the google extra (Installing Toil with Extra Features) is installed

  2. Follow Google’s Instructions to download credentials and set the GOOGLE_APPLICATION_CREDENTIALS environment variable

  3. Create a new ssh key with the proper format. To create a new ssh key run the command

    $ ssh-keygen -t rsa -f ~/.ssh/id_rsa -C [USERNAME]

    where [USERNAME] is something like Make sure to leave your password blank.


    This command could overwrite an old ssh key you may be using. If you have an existing ssh key you would like to use, it will need to be called id_rsa and it needs to have no password set.

    Make sure only you can read the SSH keys:

    $ chmod 400 ~/.ssh/id_rsa ~/.ssh/
  4. Add your newly formated public key to Google. To do this, log into your Google Cloud account and go to metadata section under the Compute tab.


    Near the top of the screen click on ‘SSH Keys’, then edit, add item, and paste the key. Then save:


For more details look at Google’s instructions for adding SSH keys.

Google Job Store

To use the Google Job Store you will need to set the GOOGLE_APPLICATION_CREDENTIALS environment variable by following Google’s instructions.

Then to run the sort example with the Google job store you would type

$ python google:my-project-id:my-google-sort-jobstore

Running a Workflow with Autoscaling


Google Autoscaling is in beta!

The steps to run a GCE workflow are similar to those of AWS (Running a Workflow with Autoscaling), except you will need to explicitly specify the --provisioner gce option which otherwise defaults to aws.

  1. Download

  2. Launch the leader node in GCE using the Launch-Cluster Command command:

    (venv) $ toil launch-cluster <CLUSTER-NAME> --provisioner gce --leaderNodeType n1-standard-1 --keyPairName <SSH-KEYNAME> --zone us-west1-a

    Where <SSH-KEYNAME> is the first part of [USERNAME] used when setting up your ssh key. For example if [USERNAME] was, <SSH-KEYNAME> should be jane.

    The --keyPairName option is for an SSH key that was added to the Google account. If your ssh key [USERNAME] was, then your key pair name will be just jane.

  3. Upload the sort example and ssh into the leader:

    (venv) $ toil rsync-cluster --provisioner gce <CLUSTER-NAME> :/root
    (venv) $ toil ssh-cluster --provisioner gce <CLUSTER-NAME>
  4. Run the workflow:

    $ python /root/  google:<PROJECT-ID>:<JOBSTORE-NAME> --provisioner gce --batchSystem mesos --nodeTypes n1-standard-2 --maxNodes 2
  5. Clean up:

    $ exit  # this exits the ssh from the leader node
    (venv) $ toil destroy-cluster --provisioner gce <CLUSTER-NAME>