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 the cloud provider as summarized in the table below.

ParameterAWSAzureRMGooglevCenterOpenStackKubernetes

Display name

x

x

x

x

x

x

Price per hour

x

x

x

x

x

x

Instance type ID

x

x

x

x

x

x

CPU

x

x

x

x

x

MilliCPUs

32- or 64-bit architecture

x

x

x

x

x


RAM (MB)

x

x

x

x

x

x

NICs

x

x

x

x

x


Instance storage (GB)

x

x

x


x


SSD support

x

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 the instance type.

FunctionAWSAzureRMGooglevCenterOpenStackKubernetes

Auto-populate and Auto-sync

x

x

x




Manual sync





x


Add




x

x

x

Edit


x

x

x

x

x

Auto-create




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 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. The Price column (highlighted in red in the above screenshot) displays the cost of an instance. 

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. For 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 the price per hour, which is used by Workload Manager and Cost Optimizer for deployment cost calculations.

Historical Price Management

Sometimes, you want to update the historical cost to correct or update cost computation. In such cases, the cost of the affected resources is computed from the date and time the price is updated. You can update the prices of the instances types for the preceding three months only.

To update the price, follow these steps:

  1. Click Edit Instance Type. The Edit Instance Types page appears.

  2. In the Price/Hour column, click the Pricing History icon. The Edit Price History dialog appears.

  3. Specify a date and time in the appropriate fields and enter the desired price in the Price/Hour field, enter the desired price.

  4. Click OK, followed by Done (in the Edit Instance Types page) to save the changes. 

After the price has been updated, the cost is recomputed for all resources (VMs and deployments, as applicable) affected by the price change. This could take a few minutes. When the recomputation is successful, you receive a notification that can be viewed in the Notification icon in the Cost Optimizer header (see Cost Optimizer Dashboard), as shown in the following sample screenshot. 

Simultaneously, the updated accrued cost of a VM is displayed on the Virtual Machines page and the updated deployment cost is displayed on the Deployment Details page.

  • No labels
Terms & Conditions Privacy Statement Cookies Trademarks