Select platform compute environment via nextflow config without retrieving the ID from the console
acknowledged
Adam Talbot
It's quite common to point a Nextflow process at a different compute environment than the one the platform submits to. E.g when we create a second compute environment called "myGpuComputeEnvironment", we can point a process at it with a config file like so:
process {
withLabel: "GPU" {
queue = "TowerForge-3d21D1WBJ80hWpvZ9x7ks1"
}
}
But you have to rummage around in the AWS/Azure/GCP console and find that unique ID which can be frustrating. Instead, it would be much better if we could use the compute environment names from Seqera Platform, like so:
process {
withLabel: "GPU" {
queue = "myGpuComputeEnvironment"
}
}
The platform performs a switch under the hood to point
myGpuComputeEnvironment
to TowerForge-3d21D1WBJ80hWpvZ9x7ks1
, but the user has a much easier interface for re-directing a process to a different queue. In addition, if I delete and re-make myGpuComputeEnvironment
it will automatically re-point to the right compute environment.This would enable more complex deployments of compute environments while still using the same interface.
Rob Newman
acknowledged