Cloud Cruiser became HPE Consumption Analytics on Nov. 1st. You'll still see the old name in places while we update this site.

 

 

Consumption Analytics Documentation

Home > Cloud Cruiser 3 > Setting Up Collection > Native collectors > HP CloudSystem Matrix > Overview

Overview

Table of contents
No headers

When ordering a service, the user can enter an optional billing code that is associated with the service instance. This code can be included in the account structure thereby allowing the user to control how the service is accounted for. If certain conventions are followed, the billing code can represent a series of account codes such as department and project.

A service offering is defined as a service template. The template consists of one or more server groups (server types) that in turn contain virtual disks and network adaptors. Pricing can be defined in CSM for the service itself, for each server group, and pricing per disk and network.

For current service instances, service details can be collected from the HPIO API. This data provides good detail but requires polling at regular intervals to create snapshots that are then processed daily and loaded into the database.

Starting with CSM 7.1, historical usage data is available from a chargeback web service. However, this is summary level only and will not include resource details such as VM memory or CPU count. Because of this and the multiple HPIO API versions, several variations on collection are supported.

The following table shows the compatibility between the HPIO Web Service API versions and the versions of the CSM Collector:

API Version

HPIO v2

HPIO v3

HPIO v4

Meter v4

CSM v6.3

X

 

 

 

CSM v7.0

X

X

 

 

CSM v7.1

X

X

X

X

Last modified

Tags

This page has no custom tags.

Classifications

This page has no classifications.
© Copyright 2018 Hewlett Packard Enterprise Development LP