Instance Types Settings
An instance type is a performance category of a VM for VM-based clouds, or a performance category of a container for container-based clouds. The parameters for an instance type vary by cloud provider as summarized in the table below.
|Price per hour||x||x||x||x||x||x|
|Instance type ID||x||x||x||x||x||x|
|32 or 64 bit architecture||x||x||x||x||x|
|Instance stortage (GB)||x||x||x||x|
You can sync, edit and add instance types depending on the cloud provider as summarized in the table below. In addition, CloudCenter Suite will auto-create instance types for vCenter clouds based on observing the VM parameters of instances executing in vCenter. This is to facilitate cost calculations for vCenter clouds based on instance type.
|Auto-populate and Auto-sync||x||x||x|
For public clouds, CloudCenter Suite auto-populates the instance types in the Instance Types section from the cloud provider. CloudCenter Suite auto-syncs this information from the cloud provider once per 24 hours. For these clouds, you cannot force a sync on demand. For OpenStack clouds, you can sync all instance types (flavors) defined in OpenStack to CloudCenter Suite on demand. To manually sync OpenStack instance types, click the Sync Instance Types link in the upper left for the instances types section as shown in the figure below.
You can add new instance types for vCenter, OpenStack, and Kubernetes clouds (by clicking the Add Instance Types link in the upper right of the section) and these instance types will control the parameters of the corresponding VMs or containers launched as part of your application. If you add an instance type within CloudCenter Suite for OpenStack, you must make sure the instance type is already defined in OpenStack, and the instance ID you enter in CloudCenter Suite must exactly match the corresponding flavor ID in OpenStack. Furthermore, during application deployment, the CPU, RAM and storage parameters defined in the OpenStack flavor will override any of the corresponding parameters defined in CloudCenter Suite. There is no concept of instance type native to vCenter or Kubernetes, therefore the instance ID of the instance types you create in CloudCenter Suite can be arbitrary and the CPU and RAM parameters you specified in CloudCenter Suite will be used in the deployment.
You must specify the price details in the Price field for vCenter, OpenStack, and Kubernetes clouds when adding instance types. The price is used to compute resource costs, which is displayed as invoice costs in the Cost Optimizer Dashboard.
For all cloud providers except AWS, you can edit the fields of an instance type (except instance type ID) by clicking the Edit link in the Actions column in the list of instance types. For vCenter and Kubernetes clouds changing the values of parameters such as CPU and RAM will impact the properties of the VMs or containers deployed in those clouds. However, for all other clouds, edits to these parameters are ignored during application deployment. The only parameter that will impact CloudCenter Suite behavior for public clouds and OpenStack is price per hour, which is used by Workload Manager and Cost Optimizer for deployment cost calculations.
- No labels