CloudCenter 4.8 has reached End of Life (EOL) as of November 14, 2018. See End of Support Notices for additional context.

Track Cloud Costs

UI Cloud Configuration

The Track Cloud Cost check box mentioned in the Configure Cloud(s) page allows you to track cloud cost for each cloud. When you deploy an application on a cloud, there is a cost for running the VM instance for this application on the cloud. The cost associated with this instance can be passed on to the tenant or user based on the deployment setup. You can manage this cost by checking this box in the CCM UI’s Cloud Configuration page.

If you do not check the Track Cloud Cost check box, the cloud cost is not calculated. If checked, you must wait for the next billing cycle (runs at the top of every hour) to view the cost and usage details. See Financial Overview for additional context.

Instance Type Pricing

Administrators can customize cloud instance type pricing. Consider a scenario where a company has a volume pricing agreement for a public cloud such that consumption is below list price or a private cloud that a central governing authority wants to pass on costs to a set of constituents. Using the administrative tools provided by the CCM, enterprises have the ability to control and override prices and address other similar situations.

Compute Cost and Storage Cost

In earlier CloudCenter releases, the compute costs and associated storage costs of VMs running in public clouds was updated on the top of the hour based and on an hourly billing cycle with round up for fractional hours used. In reality, various public cloud providers have different billing cycles for their compute instances as well as different billing cycles for attached storage. The CloudCenter platform now addresses these cloud provider nuances and offers more granular cost reporting customized for each provider. CloudCenter 4.9.1 offers more granular compute and storage cost calculations customized for the following cloud providers:

  • AWS

  • Google Cloud Platform

  • Microsoft Azure

The new cost reporting models for compute and storage for these public cloud providers are summarized in the following two tables.

Compute charges:

Cloud ProviderImage TypeBilling CycleMinimum DurationRounding
AWS

Amazon Linux, Ubuntu, Marketplace AMIs without hourly charge

1 second

60 seconds

None
AWS

Windows, RHEL, SLES, Marketplace AMIs with hourly charge

1 hour

1 hour

Round up
AzureAll

1 minute

1 minuteRound down
GCPAll

1 second

60 seconds

None


Storage charges:

Cloud ProviderBilling CycleMinimum DurationRounding
AWS

1 second

60 seconds

None
Azure

1 hour

NoneRound up
GCP

1 second

60 seconds

None


For these public clouds:

  • When a VM or deployment is suspended, compute charges cease to accumulate.

  • Storage charges continue to accumulate until the VM or deployment is terminated.

CloudCenter uses these billing models to calculate and update the cumulative cloud costs as follows:

  • For a deployment, it is displayed in the following list pages in the Deployments list page.

  • For a VM, it is displayed in the Virtual Machines list page.

The calculation considers all suspend and resume events for the VM or deployment since the last calculation. These updates occur at the top of the hour, when:

  • A VM or a deployment is manually suspended.

  • A deployment is automatically suspended due to a suspension policy. 

The storage cost is not calculated for Unmamaged VMs. 

AWS Cloud Nuance

For Unmanaged VMs imported from AWS, before the CloudCenter agent is installed, the OS is unknown; therefore the one hour billing cycle model is used in this situation.


For VMs on all other public and private clouds, the one hour billing cycle model is used.

Other References

  • No labels
© 2017-2019 Cisco Systems, Inc. All rights reserved