![]() |
Consumption Analytics Documentation |
Cloud Cruiser’s HP Cloud Service Automation (CSA) collector is based on the REST API provided by CSA. The REST API for CSA is designed to support the end user portal and as a result the importers and collector iterate through the valid CSA users and collect data visible to each user while avoiding duplicate requests where they might occur (for example, Service Offerings). Cloud Cruiser supports CSA API version 4.1. Compatibility with later versions is unknown.
Specific batch processing components for CSA are provided that support collecting subscription data, importing organizations and importing service offering catalogs.
Service offerings are contained in one or more catalogs and organized by category. Each offering can have one or more options. These offerings must be imported to establish a resource model to support reporting. The default solution imports the offerings as a passthrough resource with its rates defined within the source system. Cloud Cruiser does not maintain the rate value.
To collect, transform, and publish set up HP CSA data
https://<serverName>:8444/csa/rest
.Convert to Start Event
and Convert to End Event
transformation steps to fill in missing usage start or usage end dates, depending on configuration.The account structure for a CSA solution typically includes the organization, person, and subscription. For example, CSA could have an account structure like the following:
Account ID | Name | Description |
---|---|---|
| Organization | Customer record |
| Person | End user requesting services |
| Subscription | Services consumed by the customer |
In this example, Subscription is the lowest account level. It provides an account to map in provider specific resource consumption, such as Matrix Operating Environment (MOE) or vCenter resources. You can configure the account as a default to meet your needs. For more information, see Working with account structures.
CSA Organizations contain persons, who are essentially the end users requesting services. Importing person records is optional and creates a customer record for accounts at the person level when activated.
Organizational data in CSA can be imported to establish a customer record per organization. Having a customer record simplifies scoping reports, and makes it easier to define budgets and set alerts. For more information, see Managing customers.
You must configure the organization importer to construct an account identifier for the organization that will match the account codes created when loading subscription data. Both organization import and data loading should align with the account structure defined for your solution.
Subscriptions represent the consumption of services and service infrastructure by the user, and are the source of data for all charges and historical reporting. In CSA, a subscription can be flexed, meaning that the underlying service or service options can change. To accurately track subscription state and load the proper data, subscription data must be polled at regular intervals or the history of service requests that affect subscription state can be mined for data. The sample solution does the latter and does not require polling. This means that collection can be performed for previous dates and will remain accurate.
CSA pricing allows for both an initial fixed price and a recurring price. To support this, separate resources are created: one for the initial price and another for the recurring rate.
To accommodate options pricing, Cloud Cruiser creates distinct resources for each configured option and treats them as separate resources. Options can have both initial and recurring costs.
Each item having a price and quantity is considered a consumable resource and requires a unique identifier and description. An Offering represents a resource by itself. Each option of an Offering is considered a separate passthrough resource.
In both CSA and Cloud Cruiser, services/resources are managed using a 32-digit hex UUID. The UUID is imported by Cloud Cruiser and used as the resource name. The resource’s description is the title of the service, as defined in CSA. For example, a 32-digit hex UUID of 8a83d19e3803d463013805a8ab4816fe
can be defined as a resource called Physical Server Request in Cloud Cruiser.
An identifier is anything in the file you can associate with the resource. Everything in the subscription name value pair are identifiers.
The following are the fixed identifier names that are used in the CC Record files created when running CSA jobs:
Identifier | Description |
---|---|
| User ID of the organization |
| Name of the organization |
| Organization display name. If the display name is not specified, |
| Person user ID |
| Person name |
| Person display name. If the display name is not specified, |
A sequence of calls gathers pertinent information into a single document for data mapping. For each subscription, the subscription detail document provided by CSA is used as the base input document for collection. Each Service Offering is mapped into multiple resources for the initial and recurring prices of the base offering, as well as each option. This provides resource costs as part of the resulting CC Record data by using standard data mapping capabilities controlled by the feed configuration for a CSA collection.
Subscription data is collected by making a series of REST calls to gather data on the subscription itself, as well as all related requests and service instances.
You can map collected dtaa to Cloud Cruiser using XPath expressions and standard output field mapping. This works the same as does mapping output from the XML Collector. For more information, see Advanced configuration for the XML collector.
Each request contains all the current pricing and options selected along with a start time. It is Cloud Cruiser’s task to figure out the end time for each. Another request (modification) on the same subscription, or a cancelation request, will terminate a previous request. Otherwise, the request is assumed to still be in effect.
Use Convert to Start Event
and Convert to End Event
transformation steps to fill in missing usage start or usage end dates, depending on configuration.
(c) Copyright 2017-2020 Hewlett Packard Enterprise Development LP