Consumption Analytics Documentation

Home > Documentation for older versions > Cloud Cruiser 3 > Administering > Managing resources > Working with allocated resources

Working with allocated resources

When creating a resource, you can select an option to make the resource allocated .


An allocated resource is one that is charged on an amount that is available to a customer rather than the actual amount that the customer consumed . For example, you would use an allocated resource to charge for the number of CPUs in a virtual machine. By contrast, charging for CPU time used would be done with a non-allocated resource.

The variable rate for an allocated resource includes a time interval against which to apply the collected amount of the resource. This interval can be Hourly , Daily , Weekly , Monthly , or Yearly . For example, you might charge for CPUs at a variable rate of 15 USD per month.

Prorating allocated resources

By default, variable charges for an allocated resource are prorated, allowing you to charge fairly for access to that resource that doesn’t coincide with its defined time interval. To continue the previous example, imagine that Customer X created a VM with 4 CPUs at the beginning of April 16th and deleted that VM at the end of June 10th. Their charges for your CPU allocated resource would be:






4 CPU x $15 x 15/30 month



4 CPU x $15 x 1 month



4 CPU x $15 x 10/30 month

You can disable proration for an hourly, daily, or monthly resource or set of resources by editing the charge step of your batch job. For more information, see the API documentation for the enableProration property of com.cloudcruiser.batch.charge.ResourceFamily .

Applying rate tiers at a higher account level

In some cases, resource usage is collected against a level of your account structure that is lower than the level at which you bill. For example, you are a cloud service provider who collects usage for each department within each of your customers, but you send a monthly bill to each customer for the combined usage of its departments.

In such cases, if you are using tiered pricing you want your rate tiers to apply to that combined customer-level usage rather than the usage for individual departments. You can do this for allocated resources by editing the charge step of your batch job. This places the charges at the higher level of your account structure that you specify but leaves usage associated to the level at which it was collected so that you can drill down in reports. For more information, see the API documentation for the applyTierPerAccount and targetLevel properties of com.cloudcruiser.batch.charge.ResourceFamily .

Last modified


This page has no custom tags.


This page has no classifications.

 (c) Copyright 2017-2020 Hewlett Packard Enterprise Development LP