VMs: Standardization on single template sizes

Up until now we provided different variations of each operating system image template, one per available disk size. Starting February 28th we will only provide a single template for each operating system on Exoscale.

Having a single template still gives you the ability to perform standard actions, such as:

• Deploying VM instances with arbitrary disk sizes
• Restoring VM instances with arbitrary disk sizes

If you’re relying on larger templates you will need to look into the rootdisksize parameter of the relevant API calls:

• deployVirtualMachine
• restoreVirtualMachine

We’ve done the work on updating most published automation tooling support to this new behavior, but should you run on an oddity, let us know through the standard support channels.

As a reminder we keep a published list of all available VM templates on our template page.