VM sizing guidelines for CloudSmart-Now

Lookup tables for public cloud providers

For public cloud providers (AWS and Microsoft Azure), Cloud Cruiser uses lookup tables to set the initial VM configurations before using the VM sizing tables described in Lookup tables for all providers.

• For AWS, Cloud Cruiser uses the AWS_Size2VMInfo lookup table to set the initial VM configurations based on the VM type indicated in the collected data. For example, an m3.xlarge VM has 4 CPUs, 15 GB of memory, and 80 GB of disk space.
• For Microsoft Azure, Cloud Cruiser uses the Azure_VMType2VMInfo lookup table to set the initial VM configurations based on the VM type indicated in the collected data. For example, a Basic.A3 VM has 4 CPUs, 7 GB of memory, and 120 GB of disk space. Data in this table is based on sizing data provided by Microsoft at http://azure.microsoft.com/en-us/pricing/details/virtual-machines.

Lookup tables for all providers

Cloud Cruiser uses the VM Sizes By Memory lookup table to determine initial VM sizes according to the memory allocated to the VM. The amount of memory is an upper range, so a VM with 6GB of memory is considered a Large VM.

After determining the initial size of the VM, Cloud Cruiser uses the Standard VM Size Definitions lookup table to determine whether the VM is standard or non-standard, using the combination of CPUs and memory as a guide:

Any combination of CPUs and memory that differs from that VM's standard configuration is considered non-standard. For example, a VM with 8 GB of memory and 4 CPUs is a standard Large VM. A VM with 4 CPUs and 12GB of memory is a non-standard Extra Large VM. If you want to use different definitions for VM sizes, modify the memory and CPU values in the VM Sizes By Memory and Standard VM Size Definitions lookup tables.