Predefined hardware-optimized series (e.g., D-family general purpose) with complex naming (e.g., Standard_D4as_v5), not user-defined vCPU/RAM like OpenStack flavors.
Sizes listed via API /providers/Microsoft.Compute/locations/{location}/vmSizes, region-specific availability.
Includes accelerator features (GPU, FPGA) baked into sizes, unavailable in basic OpenStack flavors without extensions.
Cannot create custom sizes; selection from catalog, limiting flexibility vs OpenStack flavor creation.
A Droplet must select a predefined “size” bundle (RAM/vCPU/disk/transfer) rather than choosing from an OpenStack flavor catalog that many clouds let you customize/extend at the project level.
The size object exposes explicit monthly pricing (price_monthly) and per-hour pricing (price_hourly) in the API response, whereas OpenStack clouds typically separate pricing from the Nova flavor definition.
DigitalOcean sizes embed transfer allowance and region availability directly in the size metadata, while OpenStack flavors generally describe compute resources and rely on separate networking/quotas/policies for bandwidth and availability.
DigitalOcean size classes are described in the API as categories like Basic, General Purpose, CPU-Optimized, Memory-Optimized, and Storage-Optimized rather than OpenStack’s provider-defined flavor naming/extra-specs approach.
This page indexes the OpenStack CLI surface for Quake AI Compute. For curated commands with Quake AI-specific context, use the Compute CLI reference. For the full command set on a single resource, use the per-resource pages below. For upstream command syntax, see the OpenStackClient Compute v2 command reference.
The OpenStack CLI authenticates against the same project credentials you use for the API. Each per-resource page lists its commands, required arguments, and the columns each command returns.
Flavors CLI reference: list and inspect the predefined flavors. Flavor creation and deletion are admin operations; end-user credentials receive a 403 Forbidden response.