Manage Instance Types

Overview

CloudCenter only displays application VM instance types that were selected by your administrator during the image mapping process:

  • CloudCenter filters the Instance Type dropdown to automatically list only those instances provided during the image mapping process.
  • CloudCenter does not display any instance type if the selected cloud does not have image mapping or if the image is not compatible with the selected cloud.
  • The instance types are dynamically configured for public clouds. Once you add the instance type(s) for your deployment, you see the Configure Instance Types section display the configured instance(s).
  • The administrator can edit mapped images to support additional Instance Types.
  • When adding an instance type to a cloud region, users can specify a zero disk size as local storage. If 0 (zero), then the disk in the image is used and no additional disks are deployed to the VM.

  • Support for instance type and image sync is available for AWS, SoftLayer, Azure, AzureRM, Google, and Dimension Data.

Sample Instance Types

Enter the instance type(s) for your enterprise. Here are sample instance types defined by the CloudCenter platform:

Add Instance Types

To add an instance type, follow this procedure:

  1. Click the Admin link displayed in the left pane.
  2. Click the Cloud Configurations tab in the side panel to display the Cloud Configurations page.
  3. Click the Configure link (Actions column) for the required cloud.
  4. Scroll down to the Cloud Regions section and click the Configure link for the required region.
  5. Scroll down to the Configure Image Mappings section and click Add Mapping for the required image.
  6. Click Add Instance Type to add a new Instance Type mapping or override an existing mapping.
  7. Click Save to save any newly added instance types
  8. Repeat this process for other images as applicable for your deployment.

Sync Instance Types

To perform this procedure, you must have access to the Package Store.

Administrators have the ability to sync instance type and price information from the Package Store. This feature allows administrators to sync information when they see a change in cloud provider instance type definitions and price information (see Tenant Billing for additional billing information).

To sync instance types, follow this process:

  1. Configure the cloud region as specified in the Configure Cloud(s) page.
  2. Register the CCO with the CCM.

  3. When the CCO (Orchestrator) Configuration section displays the Running status, click Sync Instance Types.

  4. The Cloud Regions page updates to display the synced status.


Billing Control

See Tenant Billing > Granular Billing Control for additional context on billing users.

Scratch Disk Storage (Local Storage)

Typically, the root disk is controlled by the cloud image and is never resized by the CloudCenter platform. Most clouds do not have an automated resize option. The root disk of the application VM is always the same size as the image that is used for deployment.

The CloudCenter platform provides an additional (secondary) size in the instance type and regardless of the cloud image root disk size. This size is for an ADDITIONAL disk that is added to the VM (Install Base OS Image) for extra storage.

This local storage is added as a second hard drive, in addition to the drive found on the image template.

The additional disk size that is assigned by the CloudCenter platform to the VM at deployment time has its own requirement. If a user adds a disk volume size beyond what is supported by the instance type, the deployment fails with a corresponding error message from the associated cloud.

The storage size setting in the instance type definition is for user to understand what hardware spec they are getting when they select an instance type (just for display purposes). For public clouds like Azure and AWS, the instance types and their hardware specs are all pre-defined by the cloud. Changing this setting to 2000GB does not create a 2000GB ephemeral disk.

Root Disk Size

The root disk size behavior depends on the cloud as identified in the following table:

CloudCloud Image Disk Size Nuances

AWS

The instance type disk size is for ephemeral (temporary scratch) disk, the root disk size is what specified in the VM image. Some instance types may have multiple ephemeral disks.

Azure

The behavior is similar to AWS, the instance type disk size is for ephemeral disk, the root disk size is what specified in the VM image. Depends on the instance type, there might be a max root disk size limit.

The Azure instance type storage size refers to the ephemeral (temp) disk size – if you select A4\ExtraLarge, the ephemeral disk is 650GB.

OpenStack

The instance type disk size is for the root disk size – If an instance type specifies 40GB disk, and the base image has a root disk size of 20GB, when a VM is launched using this image and instance type, the root disk is auto resized to 40GB. However, if the base image has a root disk of 80GB, the VM launch would fail if user choose the same instance type that specifies 40GB disk size. 

VMware

VMware has no concept of instance type. In the CloudCenter platform's definition, the instance type disk size is for the ephemeral disk. If it is specified in an instance type, the CloudCenter platform attaches another disk with specified size to the VM when launching a VM using this instance type. See VMware Configurations > Resize VM Root Disk for additional context.

Instance Types Not Visible?

Instance types are not specific to each region. Be aware that some instances may not be available in some regions.

If the available instance types are not visible in the Instance Type dropdown for a given Base OS Image, verify the following settings:

  • Base image mapping – Verify the following information when mapping the images (see Map Images):
    • The service is using the required Base OS Image and that you have defined your image mapping .
    • When you select the instance types for an image (either when you Add Cloud Mapping or Edit Cloud Mapping), make sure that the required instance types are mapped.

  • Hardware specifications: Verify that your specifications are lower than the targeted instance type settings. See the Sample Instance Type sections above for some examples.