Manage Instance Types
The Workload Manager only displays application VM instance types that were selected by your administrator during the iprocess:
The Workload Manager filters the Instance Type dropdown to automatically list only those instances provided during the image mapping process. Even within the displayed list, the administrator has the option to select the instance types that should be displayed to end-users. By default, all available instances are selected as displayed in the following image.
The Workload Manager 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, AzureRM, and Google.
The Instance Type reflects MilliCPUs for a Kubernetes container and (Virtual) CPUs for all other clouds.
The Instance Type Storage field is reflected in the Instance Type card cloud as applicable for each cloud.
The storage label for instance types differs based on cloud as listed in the following table:
Cloud Additional Storage Label in the Instance Type Card
TEMP STORAGE (Temporary Storage)
2GB TEMP STORAGE
OpenStack ROOT DISK
2GB ROOT DISK
Other Clouds This field is not displayed
Sample Instance Types
Enter the instance type(s) for your enterprise. The following screenshot displays some sample instance types defined in Workload Manager :
Add Instance Types
The Add instance Type feature is only supported for vCenter and OpenStack clouds.
To add an instance type, follow this procedure:
Click the Admin link displayed in the Workload Manager UI main menu.
Click the Clouds tab in the side panel to display the Cloud list page.
Click the Configure link for the required cloud.
For OpenStack clouds, select the Regions tab and then the required region. For vCenter clouds, select the Details tab.
Scroll down to the Instance Types section and click Add Instance Type to add a new.
Complete the required fields and click Save.
Administrators can perform the following actions for the selected cloud account and region:
Set a Price Adjustment value, which will change the custom price for all the instance types. So, users don’t have to change it individually for all the instance types.
Enable/disable instance types functionality.
To set custom instance type pricing for an account/region combination, follow this procedure:
Navigate to Admin > Clouds, then click Configure Cloud for the required cloud.
Select the Accounts tab.
In the Actions column for the required cloud account, click the dropdown icon an then click Manage Instance Types.
If your cloud has only one region configured, you are brought directly the Cloud Instance Type dialog box, as shown in the screenshot below. If you have multiple regions configured, you must first select the required region from the Select Region dialog box, and then the Cloud Instance Type dialog box is displayed for that region.
Configure the Price Adjustment Value. By default, the value defaults to 100%, which indicates that the custom prices across all instance types available in the selected region will be the same as the default price. Change the Price adjustment value as required. The custom price field for all the instance types shown in the grid updates accordingly.
The custom price of an instance = Price Adjustment value * Default price of instance/100
Price adjustment value = 10, the custom prices for all instance types will be 10% of Default price of instance type.
Price adjustment value = 200, the custom prices for all instance types will be 200% of Default price of instance type.
Valid values for Price adjustment are between (0-1000 both excluded, using up to 2 decimal places).
Click OK to save the Price Adjustment value.
Review the enable/disable state of each instance type and toggle the ON/OFF switch to change any instance type.
Repeat this process for other regions as applicable for your deployment.
Sync Instance Types (Manual)
This feature is supported for OpenStack Clouds only. Administrators have the ability to import all instance flavors defined in OpenStack as CloudCenter Suite instance types by clicking the Sync Instance Types link in the upper right of the instance types section of the Regions tab.
Auto-Sync Instance Types
This feature is only available for public VM cloud providers.
A scheduled background task automatically syncs instance types and their corresponding costs once every 24 hours.
For public VM-based clouds, administrators:
Cannot edit the details of the instance (except for price for AzureRM and Google) or delete it from the list.
Cannot add any instance types manually.
This Add Instance Type feature (custom addition) was allowed for OpenStack environments in case users do not want to sync all instance types. In such cases, users can manually add the instance type using the same name that was defined in your OpenStack environment.
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 Images Page):
The service is using the required OOB Logical Images 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.
For existing, private clouds (VMware and OpenStack) created prior to CloudCenter Suite 5.1, a user would need to click Edit Instance Type and save it again without modifying any fields. This step is required if you want to deploy a Windows application. For new cloud environments (VMware and OpenStack) added as part of CloudCenter Suite 5.1, this step is not needed.
- No labels