Skip to content
Documentation
View as Markdown

How to resize a Quake AI VM to a dedicated-CPU plan

How-to · Updated Sep 2026

Coming from another cloud?

▸AWS·EC2 Maintenance

This Quake AI feature maps to AWS’s EC2 Maintenance.

▸Azure·VM Maintenance

This Quake AI feature maps to Azure’s VM Maintenance.

▸DigitalOcean·Droplet Resize

This Quake AI feature maps to DigitalOcean’s Droplet Resize.

▸Google Cloud·Instance Maintenance

This Quake AI feature maps to Google Cloud’s Instance Maintenance.

Before this
Instances

How to resize a Quake AI VM to a dedicated-CPU plan

Move a VM from a shared vCPU flavor (the Developer plan's starting point) to a dedicated vCPU flavor (Basic and custom dedicated packs). A flavor resize keeps the instance ID, boot volume, attached volumes, and disk contents. The target flavor sets the new vCPU count, RAM, and network cap.

Prerequisites

Windows: CLI examples use bash. Set up a Linux CLI environment on Windows before proceeding.

  • A running instance on a shared vCPU flavor (for example s1a.micro)
  • Sufficient dedicated vCPU quota on the project for the target flavor
  • A maintenance window that tolerates a brief restart during the resize

Upgrade your resource tier#

Dedicated vCPU flavors draw from your project's dedicated vCPU quota. If your project is still on the Developer plan, add dedicated vCPUs, RAM, and any storage you need before you resize the instance.

Follow Upgrade or downgrade resource tiers to add dedicated vCPUs to your project through the portal checkout flow. This step is billing only; it does not touch the running instance.

Pick the target flavor#

Quake AI groups dedicated flavors into three families, each tuned for a different vCPU-to-RAM ratio: General Purpose (m2a) for balanced web and API workloads, Compute Optimized (c2a) for CPU-bound jobs, and Memory Optimized (r2a) for caches and in-memory workloads. See Flavors for the full comparison and the specification table.

Available sizes vary by flavor family and region. List the flavors available to your project, then copy the exact target flavor name from the output:

bash
openstack flavor list --long

For example, select m2a.large only when that exact name appears in the list. Confirm that your resource tier has enough dedicated vCPUs and RAM for the selected flavor before continuing.

Snapshot before you resize#

Take a snapshot so you have a rollback point if the new flavor misbehaves:

Follow How to create an instance snapshot.

Resize the instance#

Record the instance ID and current flavor before you start, so you can confirm the resize did not rebuild the instance.

bash
openstack server show INSTANCE_NAME -c id -c flavor

See How to maintain a Quake AI VM over its lifetime for the general resize reference, including notes on volume-backed instances.

Verify the instance was not rebuilt#

bash
openstack server show INSTANCE_NAME -c id -c flavor -c status

The id value matches the value you recorded before the resize, flavor shows the new dedicated flavor, and status is ACTIVE.

Move to production networking (optional)#

If the instance still runs on the PublicEphemeral network from the Developer-plan quickstart, its public address remains tied to the instance. Deleting the instance releases that address.

The resize leaves the network configuration unchanged. For a private network behind a router and a floating IP that persists independently of the instance, follow How to create a VM on a private network and How to allocate floating IP addresses.

Usage Guidelines

The sample code, software libraries, command line tools, proofs of concept, templates, and other related technology on this page (including any of the foregoing that is provided by Quake AI personnel) is provided to you as Quake AI Content under the Quake AI Customer Agreement, or the relevant written agreement between you and Quake AI (whichever applies). Do not use this Quake AI Content in your production accounts, or on production or other critical data. You are responsible for testing, securing, and optimizing the Quake AI Content (such as sample code) as appropriate for production grade use based on your specific quality control practices and standards. Deploying Quake AI Content may incur Quake AI charges for creating or using Quake AI chargeable resources, such as running Compute instances or storing data in Object Storage. Your use is also subject to the Acceptable Use Policy.

For the full policy, see Usage Guidelines.

Last validated: 01.09.2026

Quick answers

See all Compute FAQs

See Also

Flavors

Shares: Vcpu, Flavors

→

Instances

Prerequisite

→

Manage cloud projects

Shares: Resource Tiers

→

How to customize a template's image and flavor

Shares: Flavors, Instances

→

How to maintain a Quake AI VM over its lifetime

Shares: Flavors, Instances

→
Was this page helpful?