Feature Request: Ability to add custom labels to Google VMs

WDL Forums discussion

In #3233 the ability to customize GCS VM labels was removed. My understanding was that this was to lift Google’s restrictions on VM labels from the workflow labels. However, I would benefit greatly from the ability to optionally supply labels to each VM.

Specifically, I’m operating my own fork of the cromwell_on_google tool which I use to spin up large batches of VMs to execute workflows. However, it’s hard to pick out individual VMs from the compute api console, especially when running multiple unrelated submissions.

My tool creates one Cromwell VM for each submission, which then (via the Google JES backend) starts new VMs for each workflow. To distinguish and filter the VMs in the console, I want to attach two labels to every vm:

• execution-role : A label to distinguish between Cromwell VMs and worker VMs
• submission-id : A label with submission IDs generated by my tool to distinguish between VMs working on different submissions

The cromwell-workflow-id label is helpful, but not convenient if I wish to operate on all VMs working on a single submission en masse.

The Google genomics API allows me to set execution-role=Cromwell and submission-id={ID} labels on the Cromwell VMs. However, without Cromwell support, I can’t set execution-role=Worker and submission-id={ID} labels on the workers at creation time.

I’m currently pursuing a workaround to manually set these labels after creation, but having control via Cromwell would be preferable.

Thanks!

[agraubert]

Can you shuffle the labels again, please? Just so that I know this still isn’t being worked on

[agraubert]

Scala is very much not in my wheelhouse, so unfortunately this is not a task I’d be comfortable taking on. But I really do appreciate the status update