Disable a Compute Environment
evaluating
C
Coral reef Lamprey
When modifying a compute environment, we need to create a new one, migrate the pipelines to it, and delete the old one. However, the compute environment needs to be idle before it can be deleted. Users will often relaunch jobs without updating the compute environment, which can make it tedious to delete a compute environment.
Adding an option to Disable a compute environment - in other words, to mark it so no new jobs can be started - would make this much easier. We could then create the new environment, migrate the pipelines, mark the old one as disabled, and just wait a day or two for existing jobs to finish.
Rob Newman
Coral reef Lamprey - would this existing feature request - making compute environments editable - resolve this for you?
C
Continuous Squid
Another use case: we create compute environemnts to give access to the researchers to VMs and workstations when they are available. When the VM/WS is needed for other scopes, we need to disable the compute environment. Exemple: our workstations used for CryoEM come with several GPUs, when no CryoEM data has to be processed, the facility gives access to the WS (with seqera) to the WS.
Rob Newman
evaluating
Rob Newman
Coral reef Lamprey: Would this also be resolved if we made Compute Environment parameters/options editable post-creation?
C
Continuous Squid
Rob Newman in our case we would still like a disable/enable environment option
Rob Newman
acknowledged