Configuring VMware vRealize Automation image flavors

Flavors represent the capacity of images, including memory, storage space, and processor capacity. You must configure a set of flavors for VMware vRealize Automation Enterprise.

Configure the cloud discovery service. See Setting up images, regions, and flavors for the cloud discovery service and engine.

After you configure flavors, you can select a flavor at provisioning time to specify the size of the environment.

Open the cloud discovery service configuration file.
If you do not have a cloud discovery service configuration file, see Setting up images, regions, and flavors for the cloud discovery service and engine.

In the section of this file that is labeled vra, add flavors.

Each flavor has the following parameters:

flavor: The name of the flavor. This name appears in the list of flavors when you provision the environment.
memory: The amount of memory in megabytes.
disk: The size of the storage in gigabytes.
vcpu: The number of virtual CPUs.

For example, the following code creates six flavors:

"vra": {
    "flavors": [
        {
            "flavor": "default",
            "memory": 0,
            "disk": 0,
            "vcpu": 0
        },
        {
            "flavor": "m1.tiny",
            "memory": 512,
            "disk": 20,
            "vcpu": 1
        },
        {
            "flavor": "m1.small",
            "memory": 2048,
            "disk": 20,
            "vcpu": 2
        },
        {
            "flavor": "m1.medium",
            "memory": 4096,
            "disk": 40,
            "vcpu": 2
        },
        {
            "flavor": "m1.large",
            "memory": 8192,
            "disk": 80,
            "vcpu": 4
        },
        {
            "flavor": "m1.xlarge",
            "memory": 16384,
            "disk": 100,
            "vcpu": 8
        }
    ]
}

Save the file and restart the cloud discovery service.
To restart the cloud discovery service, see Starting the blueprint designer, cloud discovery service, and engine and Stopping the blueprint designer, cloud discovery service, and engine.
On the system that hosts the engine, open the /usr/lib/heat/ibm-cloud-ext/resources/ibm-cloud-discovery.conf file.

In this file, add the same flavors to the [vra] section.

For example, the following code contains six flavors that match the flavors in the previous example:

[vra]
flavors: [
    {
        "flavor": "default",
        "memory": 0,
        "disk": 0,
        "vcpu": 0
    }, {
        "flavor": "m1.tiny",
        "memory": 512,
        "disk": 20,
        "vcpu": 1
    }, {
        "flavor": "m1.small",
        "memory": 2048,
        "disk": 20,
        "vcpu": 2
    }, {
        "flavor": "m1.medium",
        "memory": 4096,
        "disk": 40,
        "vcpu": 2
    }, {
        "flavor": "m1.large",
        "memory": 8192,
        "disk": 80,
        "vcpu": 4
    }, {
        "flavor": "m1.xlarge",
        "memory": 16384,
        "disk": 100,
        "vcpu": 8
    }]

Save the file and restart the engine.

Now when you provision environments, the flavors are listed in the Flavor list under Image Parameters.