Chargeback integration
IBM® Cloud Infrastructure Center is able to integrate with cloud management solutions that provide OpenStack integration points or plug-ins to provide the allocation model and consumption model for both z/VM hypervisor and KVM hypervisor chargeback support.
Allocation model
The allocation model is charged based on VM sizing, like CPU cores, memory and storage that are allocated to the VM instances.
Consumption model
The consumption model is charged based on VM consumption, like CPU time, memory and storage that are consumed to the VM instances.
Turn on the monitoring data collection
You need to turn on the monitoring data collection for collecting the metering. Refer to Enabling and disabling monitoring services for details.
Integrate with upper layers cloud management solutions via OpenStack API
You are able to generate the chargeback report from the overlying layers of the cloud management tools by the OpenStack API. For example, IBM Cloud Pak for Watson AIOps.
The IBM Cloud Pak for Watson AIOps is an IT operations management solution that allows IT operators to place AI at the core of their ITOps toolchain. It contains Infrastructure automation that consists of the infrastructure management component from the IBM Cloud Pak for Watson AIOps. The IBM® Cloud Infrastructure Center is able to integrate with the infrastructure management to provide the allocation model chargeback support.
Here are the general steps to produce the chargeback report from infrastructure management.
step 1. Create the IBM Cloud Infrastructure Center Cloud Provider
IBM® Cloud Infrastructure Center can be connected via the Keystone V3 API.
step 2. Enable the Application Setting of C & U Collection of the Region.
In infrastructure management, in the left menu bar, click Settings > Application Settings, then select C & U Collection tab. Select Yes for Collect for All Cluster and Collect for All data stores.
step 3. Enable Server Roles of the Server.
In infrastructure management, in the left menu bar, click Settings > Application Settings. Under Settings > XXX Region: Region 0\[0\] > Zones > Zone: Default Zone (current) > "EVM \[1\]" (current) , select Server tab. In the Server Control section, enable these Server Roles:
Capacity & Utilization Coordinator
Capacity & Utilization Data Collector
Capacity & Utilization Data Processor
step 4. Create the chargeback rate for the allocation model or consumption model
To use the allocation model, you need to set the rates for the Allocated CPU Count
, Allocated Memory
, Allocated Disk Storage
. For the Allocated CPU Count
, Allocated Memory
and Allocated Disk Storage
that is rated, they must not be set to zero.
To use the consumption model, you need to set the rates for CPU Used
, Memory Used
, Storage Used
(Used Disk Storage) and Network I/O
. For the CPU Used
, Memory Used
, Storage Used
and Network I/O
that is rated, they must not be set as zero.
step 5. Assign the chargeback rate to the specific projects
You can assign different chargeback rates to different projects.
step 6. Create the chargeback report from the report templates
For example, chargeback for vms. You can customize the report columns, formatting and filters. Note, that from the filter tab, you can select the specific Openstack based cloud provider as the data source for generating the chargeback report. You can also set the chargeback interval from daily to monthly.
step 7. Select the chargeback report and click the queue button to generate the chargeback report.
For further information, refer to IBM Cloud Pak for Watson AIOps Chargeback
Note: To get into the infrastructure management in IBM Cloud Pak for Watson AIOps, follow these steps. Login to IBM Cloud Pak for Watson AIOps, browse to Menu and click automate infrastructure > infrastructure management.
Steps on infrastructure management to produce the chargeback report are similar to ManageIQ.
Here are the general steps to produce the chargeback report on infrastructure management in IBM Cloud Pak for Watson AIOps.
step 1. Create the Openstack based Cloud Provider
The IBM® Cloud Infrastructure Center can be connected via the Keystone V3 API.
step 2. Enable the Application Setting of C & U Collection of the Region.
In infrastructure management, in the left menu bar, click Settings > Application Settings, then select C & U Collection tab. Select Yes for Collect for All Cluster and Collect for All data stores.
step 3. Enable Server Roles of the Server. In infrastructure management, in the left menu bar, click Settings > Application Settings. Under Settings > CP4MCM:IM Region: Region 0\[0\] > Zones > Zone: Default Zone (current) > "EVM \[1\]" (current) , select Server tab. In the Server Control section, enable these Server Roles: - Capacity & Utilization Coordinator - Capacity & Utilization Data Collector - Capacity & Utilization Data Processor
step 4. Create the chargeback rate for the allocation model or consumption model
To use the allocation model, you need to set the rates for the Allocated CPU Count
, Allocated Memory
, Allocated Disk Storage
. For the Allocated CPU Count
, Allocated Memory
and Allocated Disk Storage
that is rated, they must not be set to zero.
To use the consumption model, you need to set the rates for CPU Used
, Memory Used
, Storage Used
(Used Disk Storage) and Network I/O
. For the CPU Used
, Memory Used
, Storage Used
and Network I/O
that is rated, they must not be set as zero.
step 5. Assign the chargeback rate to the specific projects
You can assign different chargeback rates to different projects.
step 6. Create the chargeback report from the report templates
For example, chargeback for VMs. You can customize the report columns, formatting and filters. Note, that from the filter tab, you can select the specific Openstack based cloud provider as the data source for generating the chargeback report. You can also set the chargeback interval from daily to monthly.
step 7. Select the chargeback report and click the queue button to generate the chargeback report.
For other cloud management solutions steps are similar.
Support metrics for chargeback support with Allocation model and Consumption model
Following are supported metrics with chargeback report based on allocation model.
Chargeback metrics from Infrastructure Management | Origin metrics from ICIC | Support for z/VM Hypervisor | Support for KVM Hypervisor |
---|---|---|---|
vCPUs Allocated Rate | * | Yes | Yes |
vCPUs Allocated over Time Period | vcpus | Yes | Yes |
vCPUs Allocated Cost | * | Yes | Yes |
CPU Total Cost | * | Yes | Yes |
Memory Allocated Rate | * | Yes | Yes |
Memory Allocated Cost | * | Yes | Yes |
Memory Allocated over Time Period | memory.usage | Yes | Yes |
Memory Total Cost | * | Yes | Yes |
Storage Allocated | disk.root.size | Yes | Yes |
Storage Allocated Rate | * | Yes | Yes |
Storage Allocated Cost | * | Yes | Yes |
Storage Total Cost | * | Yes | Yes |
Note
The '*' in the table indicates the specific metric can be defined or calculated by Infrastructure Management directly.
Origin metric in ICIC indicates the resources metric provided by Cloud Infrastructure Center.
Following are supported metrics with chargeback report based on consumption model.
Chargeback metrics from Infrastructure Management | Origin metrics from ICIC | Support for z/VM Hypervisor | Support for KVM Hypervisor |
---|---|---|---|
CPU Used | cpu_util | Yes | Yes |
CPU Used Rate | * | Yes | Yes |
CPU Used Cost | * | Yes | Yes |
CPU Total Cost | * | Yes | Yes |
Memory Used | mem_util | Yes | Yes |
Memory Used Rate | * | Yes | Yes |
Memory Used Cost | * | Yes | Yes |
Memory Total Cost | * | Yes | Yes |
Network I/O Used | network.incoming.bytes / network.outgoing.bytes | No | Yes |
Network I/O Used Rate | * | Yes | Yes |
Network I/O Used Cost | * | Yes | Yes |
Storage Used | disk.device.usage | Yes | Yes |
Storage Used Rate | * | Yes | Yes |
Storage Total Cost | * | Yes | Yes |
Disk I/O Used | disk.device.read.bytes / disk.device.write.bytes | No | No |
Disk I/O Used Rate | * | Yes | Yes |
Disk I/O Used Cost | * | Yes | Yes |
Note
The '*' in the table indicates the specific metric can be defined or calculated by Infrastructure Management directly.
Origin metric in ICIC indicates the resources metric provided by Cloud Infrastructure Center.