Manage Instance Types
CloudCenter only displays application VM instance types that were selected by your administrator during the iprocess:
CloudCenter 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.
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, IBM Cloud, Azure, AzureRM, Google, and DimensionData.
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 by the CloudCenter platform:
Add Instance Types
To add an instance type, follow this procedure:
Click the Admin link displayed in the CCM UI main menu.
Click the Cloud Configurations tab in the side panel to display the Cloud Configurations page.
Click the Configure link (Actions column) for the required cloud.
Scroll down to the Cloud Regions section and click the Configure link for the required region.
Scroll down to the Configure Image Mappings section and click Add Mapping for the required image.
Click Add Instance Type to add a newmapping or override an existing mapping.
Click Save to save any newly added instance types
Repeat this process for other images as applicable for your deployment.
Billing Cycle and Summary
The feature is only available for AWS environments with valid credentials.
The currency displayed in the invoice is always in US Dollars (USD), irrespective of your currency preference configuration for the tenant.
You may see a minor difference in price between the invoice displayed in CloudCenter and the bill displayed in the AWS console:
The invoice data for the current month to date will not match the actual AWS bill summary (as seen in the AWS console) as the usage data reported via the API has update delays.
The CloudCenter invoices are at service-level whereas the AWS invoices are consolidated
The CloudCenter platform provide support for the following tasks to administrators and users with manage and modify privileges for an AWS cloud account:
View invoices and the current month to date usage rates for a particular AWS cloud account. The Invoice is broken down into each individual AWS service consumed by the account and its price across regions (per service and per region).
If you see the Billing Data Not Found error, it is possible that the billing data is not available for the selected month or period. The billing period dropdown is based on the client's browser time but AWS servers list this information in UTC time. Based on when you request the information, you may see this error.
View the usage summary of unblended rates for all linked accounts (user accounts that are under the a tenant as par of consolidated billing option):
The current month (month-to-date summary)
The previous month (invoice)
Two months before the current period (invoice)
Three months before the current period (invoice)
Refer to the AWS documentation for additional information about unblended rates.
To view the invoice/summary, navigate to Admin > Clouds > Configure Cloud. The Cloud Accounts page displays a column called Estimated Month to Date Cost as displayed in the following screenshot.
When you click the View Invoice link, the corresponding popup displays the usage summary for the Current Month to Date and you can change the display to reflect the desired period:
The Start date = the starting date for the month
The End date = the starting date of the next month
For example, if you need a billing period of March 2018, then the start date should be 01/03/2018 and the end date should be 01/04/2018 respectively.
The Last Billing Cycle column in the summary/invoice is visible only if you :
Configured the CCO on an AWS cloud.
For a cloud account with is shared view permissions the Last Billing Cycle column remains empty.
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 manage an instance type, follow this procedure:
Navigate to Admin > Clouds, then click Configure Cloud for the required cloud.
Click Manage Instance Type for the required cloud account.
Select the relevant region in the area highlighted in the following screenshot to display the Cloud Instance Types for this 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)
To perform this manual procedure, you must have access to the Package Store.
Administrators have the ability to sync instance type and price information from the. This feature allows administrators to sync information when they see a change in cloud provider instance type definitions and price information.
To sync instance types, follow this process:
Configure the cloud region as specified in the Configure Cloud(s) page.
When the CCO (Orchestrator) Configuration section displays the Running status as displayed in the following screenshot – click Sync Instance Types.
This feature is available in some clouds:
The Cloud Regions page updates to display the synced status displayed in the following screenshot.
Auto-Sync Instance Types
This feature is only available for AWS cloud configurations.
A scheduled background task automatically syncs instance types and their corresponding costs in the database and also displays the Last Synced interval as displayed in the following screenshot.
If the AWS account is wrongly configured, for example, the right account ID is configured with a wrong access/secret key, then the CloudCenter platform issues an error about a missing Cloud Image mapping. This results in last synced time not being displayed for the cloud. Try restarting the CCM server to solve this issue.
Can continue to manually sync instance types and costs
Cannot edit the details of the instance or delete it from the list.
Cannot add any instance types manually – this button is removed and no longer available for AWS.
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.