# What is a Flavor

A PMO **Flavor** is a specification of the number of virtual CPUs, RAM and disk size that can be allocated to a virtual machine.

PMO comes out of box with a set of predefined flavors. Administrators can delete these and/or create more custom flavors.

Administrators can also define the visibility of a Flavor by making it a public or a private flavor. Public flavors are accessible to all users across all tenants in your PMO cloud. Private flavors are restricted to specific tenants and are accessible only to users within the tenants to which the administrator has given access to this flavor.

## Predefined Flavors

PMO provides five predefined flavors out of box. These are public flavors by default. The following table describes the predefined flavors:

| **Flavor Name** | **No. of virtual CPUs (vCPUs)** | **RAM** | **Disk Space** |
| --------------- | ------------------------------- | ------- | -------------- |
| Tiny            | 1                               | 512 MB  | 1 GB           |
| Small           | 1                               | 2 GB    | 20 GB          |
| Medium          | 2                               | 4 GB    | 40 GB          |
| Large           | 4                               | 8 GB    | 80 GB          |
| xLarge          | 8                               | 16 GB   | 160 GB         |

## Custom Flavors

PMO Administrators have full flexibility to delete all pre-defined flavors and /or create additional custom flavor that better suite the requirements of their PMO cloud.

## Zero Disk Size Flavor

When a virtual machine is deployed using an image by applying a flavor to it, PMO tries to deploy the virtual machine with the disk size that is specified by the flavor.

However, if the disk size specified by the flavor does not match the minimum disk size required by the image, the virtual machine deployment will fail.

To simplify this, PMO supports creation of zero disk-size flavors.

When a virtual machine is created by using a zero disk-size flavor, PMO configures disk size of the virtual machine to be the virtual disk size specified in the image from which the instance is being created.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.platform9.com/managed-openstack/5.8/flavour/flavors-flavors.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.