Setup Azure batch compute environments#
Based on our discussion and the documentation and FAQ
Setup Permissions#
Here are the key points with setting up Azure Infrastructure using a Managed Identity and Batch Pool.
On Azure#
Create a service principal
Create a managed identity
Assign roles to the service principal and managed identity
Increase quota for the Azure Batch Account
Create Azure Batch pools in the Batch account
Attach nodes to the virtual network in the right subnet
Whitelist internet access on the subnet.
On Seqera Platform within a workspace:#
Admin permissions to add credentials, compute environment(s) and pipelines to a workspace
On VMs as nodes in a pool#
Nodes in a pool are described based on the VM naming convention:
See also Azure Batch documentation.
Local storage of a VM is one-to-one in line with the number of CPUs. See the
Local Storage
tab for a machine in a series to find out more. See for example the Ddsv4 sizes series.