Linode types

Quake AI concept: Flavors

• Linode exposes flavors as account-level "types" returned by the List types API, which the docs say are used when creating or resizing Linodes. In OpenStack, flavors are also instance sizes, but Linode’s canonical API naming is "types" rather than a Nova flavor resource. (Akamai TechDocs)
• The Create a Linode endpoint requires a `type` field when provisioning, and the docs describe it as one of several Linode types with different sizes, processing potential, and cost. That is a predefined bundle model rather than an arbitrary per-instance resource shape chosen at launch time from OpenStack-style custom flavor extra specs. (Akamai TechDocs)
• Linode plans are tied to billing on creation and resizing: creating a Linode incurs a charge, and resizing is called out as a separate operation that uses the types list. The billing docs also say services accrue hourly charges up to a monthly cap, with some compute services continuing to offer both hourly and monthly pricing, which differs from OpenStack’s provider-defined billing model. (Akamai TechDocs, Akamai TechDocs)
• The docs explicitly present types as selectable during create and resize, and the account can switch between different Linode interface generations, but they do not describe any Nova-style flavor metadata, flavor access control, or flavor extra-spec customization. The public docs therefore show a fixed catalog of provider-defined plans rather than user-defined or tenant-scoped flavors. (Akamai TechDocs, Akamai TechDocs)