- Preface
- New and Changed Information for this Release
- Overview
- Managing Users and Groups
- Setting Up the End User Portal
- Managing System Administration Settings
- Managing Integration Settings
- Managing a Physical Infrastructure
- Managing a Virtual Infrastructure
- Managing Policies
- Managing Virtual Data Centers
- Managing Resource Groups
- Managing Catalogs
- Using Self-Service Provisioning
- Multiple Disk VM Provisioning
- Using the Chargeback Module
- System Monitoring and Reporting
- Managing Lifecycles
- Managing CloudSense Analytics
- About Chargeback Features
- Budget Policies
- Cost Models
- Modifying a VDC to Include a Cost Model
- Package-Based Cost Models
- Storage Tier Cost Models
- About Assigning a Datastore to Tiers
- Chargeback Reports
- Viewing the Current Month Summary
- Viewing the Previous Month’s Summary
- Viewing Monthly Resource Accounting Information
- Viewing the VM Level Resource Accounting Details
- Viewing the VM Level Chargeback Details
- Exporting the Monthly Resource Accounting Details
- Exporting VM Level Resource Accounting Details
- Exporting VM Level Chargeback Details
- About Change Records
- Chargeback Calculations
Using the Chargeback
Module
This chapter contains the following sections:
- About Chargeback Features
- Budget Policies
- Cost Models
- Modifying a VDC to Include a Cost Model
- Package-Based Cost Models
- Storage Tier Cost Models
- About Assigning a Datastore to Tiers
- Chargeback Reports
- About Change Records
- Chargeback Calculations
About Chargeback Features
The chargeback module in Cisco UCS Director offers in-depth visibility into the costs of the virtual infrastructure. It allows the definition of cost models and their assignment to policies within departments and organizations. Virtual machine (VM) metering data is collected at frequent intervals to ensure accurate calculation of resource costs.
The chargeback module is supported only for physical servers that are within an application container.
Following are the features of the chargeback module:
-
Flexibility—Provides fixed costs, one-time costs, allocation costs, usage costs, and a combination of these costs, based on the organizational requirements.
-
Reusable Cost Models—Assigns cost models to VMs using standardized cost models or templates. These templates apply cost models to new environments quickly.
-
Reporting—Generates various summary and comparison reports of costs and resource usage for the virtual infrastructure. These reports are exported to PDF, CSV, and XLS formats and allow you to view them with a web browser.
-
Top Five Reports—Monitors the top five reports for organizations or groups with the highest VM cost, CPU, memory, storage, and network costs.
-
Dashboard—Monitors and analyzes VM metering information and chargeback in real time with the built-in dashboard and an extensive set of graphical widgets.
Budget Policies
Overall resources are accounted for by the chargeback module. In addition to chargeback, individual groups or organizations must be associated with a budget policy where you can enable or disable the budget watch and over budget.
Configuring a Budget Policy
Creating a Tag-Based Cost Model
The tag-based cost model capability is supported on all VMs that have been provisioned through a container.
Step 1 | Choose . | ||||||||||
Step 2 | On the Service Delivery page, click Tag Based Cost Model. | ||||||||||
Step 3 | Click Add to create a new cost model. | ||||||||||
Step 4 | In the
Add Tag
Based Cost Model screen, complete the required fields, including the
following:
| ||||||||||
Step 5 | Click + sign to add tag costs to the cost model. | ||||||||||
Step 6 | In the
Add Entry
to Tag Costs screen, complete the required fields, including the
following:
| ||||||||||
Step 7 | Click Submit. | ||||||||||
Step 8 | In the Add Tag Based Cost Model screen, click Submit. | ||||||||||
Step 9 | Click OK. |
Cost Models
A cost model is used to define the unit-level costs of virtual resources, and physical resources. These costs are used for chargeback calculations of VMs within the virtual infrastructure as well as physical resources. Cost models offer a definition of costs in a linear model.
The cost of a particular resource is calculated on how many units are assigned to that resource in the VM or physical resource. For example, the cost of 1 GB of RAM is defined within the cost model. This unit cost is used to determine the cost of RAM for a particular VM.
You can define one-time provisioning costs, active or inactive VM costs, and provisioned, reserved, or used costs for resources, such as CPU, and memory. These values are used to calculate VM costs based on usage.
In addition, you can also create a cost model for bare metal servers within the physical infrastructure.
![]() Note | You can map a cost model to a VDC or to an application container. For more information on mapping a cost model to an application container, see the Cisco UCS Director Application Container Guide available at the following link: |
Creating a Cost Model
Step 1 | Choose . | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Step 2 | On the Service Delivery page, click Cost Model. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Step 3 | Click Add. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Step 4 | In the
Add Cost
Model screen, complete the required fields, including the following:
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Step 5 | Click Add. |
Creating a Bare Metal Cost Model
Step 1 | Choose . | ||||||||||||||||||||||||
Step 2 | On the Bare Metal Servers page, click Bare Metal Cost Model. | ||||||||||||||||||||||||
Step 3 | Click Add. | ||||||||||||||||||||||||
Step 4 | In the
Add Bare
Metal Cost Model screen, complete the required fields, including the
following:
| ||||||||||||||||||||||||
Step 5 | Click Submit. |
What to Do Next
You can choose this cost model when you create a Bare Metal Server provisioning policy.
Modifying a VDC to Include a Cost Model
You can add or edit an existing VDC to assign a newly created cost model. You can edit an existing VDC, or create a new VDC and assign a cost model to it.
After the cost model is assigned to a VDC, all VMs within the VDC are charged based on the advanced cost model. Any VMs within VDCs that have the standard type of cost model are still charged according to the standard cost model.
Adding a Cost Model to a VDC
Step 1 | Choose . | ||||||||||||||||||||||||||||||||||||||||||||||||||||
Step 2 | On the Virtual Data Centers page, click vDC. | ||||||||||||||||||||||||||||||||||||||||||||||||||||
Step 3 | Choose the VDC to which you want to add the cost model. | ||||||||||||||||||||||||||||||||||||||||||||||||||||
Step 4 | Click Add. | ||||||||||||||||||||||||||||||||||||||||||||||||||||
Step 5 | In the Add vDC screen, select the account type, and click Submit. | ||||||||||||||||||||||||||||||||||||||||||||||||||||
Step 6 | In the
Add
VDC screen, complete the required fields, including the following:
| ||||||||||||||||||||||||||||||||||||||||||||||||||||
Step 7 | Click Add. |
Editing a VDC to Include a Cost Model
Step 1 | Choose . |
Step 2 | On the Virtual Data Centers page, click VDC. |
Step 3 | Choose the VDC to add to the cost model. |
Step 4 | Click Manage Categories. |
Step 5 | Choose the category to edit. |
Step 6 | Click Edit. |
Step 7 | In the Edit App Category screen, in the drop-down list, choose a Cost Model and a Deploy Policy. |
Step 8 | Click Save. |
Package-Based Cost Models
A package-based cost model enables you to define the costs for the system resources as packages instead of as individual definitions. There are different packages to choose from based on your requirements. This type of cost model is suitable for nonlinear models.
![]() Note | Cisco UCS Director supports definitions of CPU memory (server) packages. |
In this type of cost model, the definition is based on the available resource packages. The model is in the following format:
C – M:X.
C is the number of CPU cores.
M is the memory in GB.
X is the combined monthly cost of C and M.
For example, a package with an entry of 2-4:200 implies CPU cores = 2, memory = 4 GB, and the cost of this package is $200 per month.
You can define multiple packages using the following format: C1-M1:X1,C2-M2:X2,......,CN-MN:XN.
For example, 1-1:50,1-2:70,1-4:90,2-4:150,2-6:170,2-8:190,4-8:350,4-12:380,4-16:400. The first entry 1-1:50 is a package of 1 core CPU and 1 GB memory that costs $50 per month.
![]() Note | These entries can be edited at any time to suit the cost package requirements. |
Creating a Package-Based Cost Model
Step 1 | Choose . | ||
Step 2 | On the Service Delivery page, click Cost Model. | ||
Step 3 | Click Add. | ||
Step 4 | In the Add Cost Model screen, enter a cost model name and description. | ||
Step 5 | For the Cost Model Type field, choose Advanced. | ||
Step 6 | Paste the script
provided in the
Advanced
Cost Model field.
/********************************/ var CPU_MEMORY_COST = "1-2:81,1-4:95,1-8:109,2-4:162,2-6:176,2-8:189,2-16:378,4-12:352,4-16:378"; var oneTimeCost = 150; /********************************/ /* define cost packages as shown above. The cost packages can be defined in the following format: C-M:X. C is the number of CPU cores. M is the memory in GB. X is the combined monthly cost of C and M. For example, 2-4:162 means CPU cores = 2, memory = 4 GB and the cost of this package is $162 per month. */ /* When defining multiple packages, define it in the following format: C1-M1:X1,C2-M2:X2, ...........,CN-MN:XN The standard packages are defined at the top of the script using the variable CPU_MEMORY_COST. This variable can be edited to suit the cost package requirement. */ /* For reference, the storage cost to use is based on the storage tier cost model definition. */ /* do not edit any script below */ computeChargeback(data); function computeChargeback(data) { var map = chargeBackAPI.getCPUMemCostModelMap(CPU_MEMORY_COST); var cpuCores = data.getVmMeter().getCpuCores(); var memory = data.getVmMeter().getAllocMemGB(); var serverCost = chargeBackAPI.getCostForItem(map,cpuCores, memory); serverCost = serverCost / (24 * 30); var storageTierCost = chargeBackAPI.getStorageCostForItem(data.getVmMeter().getVmId()); var storageGB = (data.getVmMeter().getCommittedDiskGB()) + (data.getVmMeter().getUncommittedDiskGB()); var committedDiskGBCost = (data.getVmMeter().getCommittedDiskGB()) * storageTierCost; var unCommittedDiskGBCost = (data.getVmMeter().getUncommittedDiskGB()) * storageTierCost; var storageCost = (storageGB * storageTierCost) / (24 * 30); var totalVMCost = serverCost + storageCost; var cb = data.getCbSummary(); cb.setCpuCores(cpuCores); cb.setMemory(memory); cb.setServerCost(serverCost); cb.setCommittedDiskGB(data.getVmMeter().getCommittedDiskGB()); cb.setCommittedDiskGBCost(committedDiskGBCost); cb.setUncommittedDiskGB(data.getVmMeter().getUncommittedDiskGB()); cb.setUncommittedDiskGBCost(unCommittedDiskGBCost); cb.setTotalCost(totalVMCost); } /********************************/ | ||
Step 7 | Click
Add.
|
Storage Tier Cost Models
You can use a storage tier cost model to define multiple costs for storage using the tier format. Current storage types include but not limited to local storage, NFS, SAN, and NAS. Each storage cost could vary. You can incorporate this variation while calculating costs for storage usage.
You can use this model to define different costs for different tiers and then assign existing datastores to these tiers. You can group similar datastore types by cost wise using the tier cost model.
Each tier must be assigned a cost, at a per-GB, per-month value. For example, when assigning $0.50 to a tier, all datastores within this tier are charged at $0.50 per GB per month. By default, four tiers are already created, so you must assign the costs to them.
Assigning a Cost to a Tier
About Assigning a Datastore to Tiers
You can assign a datastore to a tier so that the cost defined in the tier is used to calculate the cost of storage within that particular datastore.
When calculating the chargeback for VMs within a datastore, the cost is determined by which tier the datastore was assigned to. If no tier is assigned to a datastore, the storage cost for that datastore is not considered when using the advanced (script-based) cost model.
With a regular cost model, you define resource costs in a form. Storage tier costs are taken into consideration if tier costs are assigned and datastores are assigned to those tiers. However, if no tier is assigned to a datastore, the storage cost for VMs under that datastore is removed from the storage cost entry of the cost model form.
![]() Note | Assigning a datastore to a tier applies only to the regular cost model. |
Assigning a Datastore to a Tier
Step 1 | Choose . |
Step 2 | On the Storage page, choose the cloud. |
Step 3 | On the Storage page, click Datastore Capacity Report. |
Step 4 | Choose the datastore to assign to a tier. |
Step 5 | Click
Assign
Tier and the
Storage
Tier screen appears.
Currently, the tier-based cost is supported only on VMware cloud accounts. |
Step 6 | From the drop-down list, choose a tier. |
Step 7 | Click Submit. |
Chargeback Reports
Chargeback provides information about how much your organization may be paying for resources, even unused resources. This feature allows you to optimize resource consumption and costs. System resources accounting can be based on monthly usage. Resources, such as CPU and memory usage, are monitored and measured.
Chargeback reports are based on the cost model type. Chargeback is calculated and shown in the user interface in the form of tabular reports, summaries, graphical reports, and widgets.
Chargeback summary data is stored only at a daily and monthly interval. So, you cannot generate daily and hourly trend cost reports using the Chargeback menu option. You can generate trend reports only for weekly and monthly duration. You can generate these trend reports, in addition to several other trend reports, using the Report Builder menu available under CloudSense. For more information on using the Report Builder option, see Report Builder for Custom Report Templates.
While generating trend reports for a month, the data is caculated from the first day of the month till the current date. For example, if you are generating a trend report on 5th March, this report includes data from March 1st, to March 5th.
![]() Note | For VMs that are provisioned through a container, you can associate a tag-based cost model and include those costs in the regular chargeback calculations and subsequent reports. |
Following are the report types that are available:
-
Viewing
-
Current month summary—The current month summary cost report (VM, CPU, storage costs, and so on).
-
Previous month summary—The previous month summary cost report (VM, CPU, storage costs, and so on).
-
Monthly resource accounting details—The resource accounting details (CPU and memory usage statistics) on a monthly basis.
-
VM level resource accounting details—The resource accounting details at the VM level.
-
VM level chargeback details—The charges that are applicable for VM usage calculated with the chargeback feature.
-
-
Export
You can generate these reports for a group, or for a specific virtual data center (VDC). These reports include information on virtual resources as well as on physical servers.
- Viewing the Current Month Summary
- Viewing the Previous Month’s Summary
- Viewing Monthly Resource Accounting Information
- Viewing the VM Level Resource Accounting Details
- Viewing the VM Level Chargeback Details
- Exporting the Monthly Resource Accounting Details
- Exporting VM Level Resource Accounting Details
- Exporting VM Level Chargeback Details
Viewing the Current Month Summary
Using the Current Month Summary tab, you can view the month’s chargeback details for all VMs and physical servers that belong to the group.
Viewing the Previous Month’s Summary
Using the Previous Month Summary tab, you can view the previous month’s chargeback details for all VMs and physical servers that belong to the group.
Viewing Monthly Resource Accounting Information
Viewing the VM Level Resource Accounting Details
Using the Resource Accounting Details tab, you can view the individual VM's resource usage details.
Viewing the VM Level Chargeback Details
Using the Chargeback tab, you can view the chargeback report for the selected group or VDC.
If you indicated that the tag-based cost model must be included in the regular VM chargeback calculations, then you will see the Fixed Costs column in the report. This column retrieves the cost that you indicated in the tag-based cost model.
Exporting the Monthly Resource Accounting Details
Step 1 | Choose . |
Step 2 | On the Chargeback page, click Resource Accounting. |
Step 3 | Click the Export Report icon. |
Step 4 | In the
Export Report screen, choose a format.
It can be one of the following options: |
Step 5 | Click
Generate
Report.
After the report is generated, the Download option appears. |
Step 6 | Click
Download to open the report in another browser.
After the report opens in another browser, you can save it on your system. |
Exporting VM Level Resource Accounting Details
Step 1 | Choose . |
Step 2 | On the Chargeback page, click Resource Accounting Details. |
Step 3 | Click the Export Report icon. |
Step 4 | In the
Export Report screen, choose a format.
It can be one of the following options: |
Step 5 | Click
Generate
Report.
After the report is generated, the Download option appears. |
Step 6 | Click
Download to open the report in another browser.
After the report opens in another browser, you can save it on your system. |
Exporting VM Level Chargeback Details
Step 1 | Choose . |
Step 2 | On the Chargeback page, click Chargeback. |
Step 3 | On the right side of the toolbar, click the Export Report icon. |
Step 4 | In the
Export Report screen, choose a format.
It can be one of the following options: |
Step 5 | Click
Generate
Report.
After the report is generated, the Download option appears. |
Step 6 | Click
Download to open the report in another browser.
After the report opens in another browser, you can save it on your system. |
About Change Records
You can use change records within the Change Management Database (CMDB) to track and manage changes in the system. These records typically display ADD, DELETE, and MODIFY types of events on any resource, such as a VM, service request, or group.
Change records display information about the resource type (VM), including the resource name, change type, change time, and description. When a VM is resized, the change records display information on the resources that were resized. This includes information on the original resource size and the resized values. You can view this information from the Change Records tab.
Accessing Change Records
Chargeback Calculations
The total cost calculated for a VM includes the following:
Total cost = active VM cost or inactive VM cost + one-time cost + CPU cost + memory cost + disk cost + CPU reserved cost + memory reserved cost + CPU used cost + CPU core cost + memory used cost + network received used cost + network transmitted used cost + application cost.
If a VM is associated with a tag, and has a cost model and a tag-based cost model associated with the vDCs, then the chargeback calculation is derived as follows:
-
When the Include VM in Regular Chargeback check box is not checked, only the tag-based cost is calculated.
Total Cost - Fixed Cost + One-Time Cost
-
When the Include VM in Regular Chargeback check box is checked, the total cost is calculated including the tag-based cost and the regular chargeback computation.
Total Cost = active VM cost or inactive VM cost + one-time cost + CPU cost + memory cost + disk cost + CPU reserved cost + memory reserved cost + CPU used cost + CPU core cost + memory used cost + network received used cost + network transmitted used cost + application cost + Fixed Cost
![]() Note | The one-time cost for the VM is determined from the cost specified in the tag-based cost model. If you have not specified a one time cost in the tag-based cost model, then this cost is derived from the regular cost model. |
The total cost calculated for a physical server includes the following:
Total cost = one time cost + CPU cost + memory cost + memory used cost + committed disk cost + CPU core cost + full blade cost + half blade cost.
The VM cost calculation is done only on an hourly basis. There is no other option available to calculate the VM cost. The cost for each resource is calculated based on the values that are defined in the cost model. The cost calculations are based as follows:
Cost | Cost Description |
---|---|
Active VM Cost |
The value defined in the cost model for the active VM cost. |
Inactive VM Cost |
The value defined in the cost model for the inactive VM cost. |
One Time Cost |
The value defined in the cost model for the one-time cost. |
CPU Cost |
CPU usage (provisioned) × cost that is defined in the cost model for the provisioned CPU cost. The CPU charge unit is GHz. |
Memory Cost |
Memory usage (provisioned) × cost that is defined in the cost model for the provisioned memory cost. The memory charge unit is GB. |
Disk Cost |
The committed storage × committed storage cost that is defined in the cost model + uncommitted storage × uncommitted storage cost that is defined in the cost model. The storage charge unit is GB. |
CPU Reserved Cost |
The reserved CPU × cost that is defined in the cost model for the reserved CPU cost.1. |
Memory Reserved Cost |
The reserved memory × cost that is defined in the cost model for the reserved memory cost.2. |
CPU Used Cost |
The used CPU × cost that is defined in the cost model for the used CPU cost.1. |
CPU Core Cost |
The used CPU core × cost that is defined in the cost model for the CPU core cost. The CPU charge unit is per core. |
Memory Used Cost |
The used memory × cost that is defined in the cost model for the used memory cost.2. |
Network Received Used Cost |
The network received usage in KB / (1024.0 × 1024.0) × cost that is defined in the cost model for the received network data cost. The network charge unit is GB. |
Network Transferred Used Cost |
The network transmitted usage in KB / (1024.0 × 1024.0) × cost that is defined in the cost model for the transmitted network data cost.5. |
Application Cost |
The active VM hours × cost that is defined in a catalog for active VM application cost + inactive VM hours × cost that is defined in a catalog for the inactive VM application cost. |
Full-length Blade Cost |
The cost of full-length blade servers per-hour. This cost is applicable only for physical servers. This is applicable only for physical servers that are part of an application container. |
Half-Length Blade Cost |
The cost of half-length blade servers per-hour. This cost is applicable only for physical servers. This is applicable only for physical servers that are part of an application container. |
Fixed Cost USD |
The fixed cost, per-hour, determined for the VM. This is applicable only if you have indicated that the tag-based cost model should be included with the regular cost model for the VM. |