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 > Microsoft Windows Azure Pack > Process overview

Process overview

Table of contents
No headers

The following are the high-level steps required to set up regular collection and loading of Microsoft Windows Azure Pack data.

  1. If you have not yet set a password for the Windows Azure Pack Usage REST API user, do so.
    This step was part of the installation process. For more information, see Setting the Windows Azure Pack API password.
  2. Ensure that resources for Windows Azure Pack exist in Cloud Cruiser.
    These resources will be in the groups Azure Pack DatabaseAzure Pack Website, and Azure Pack Virtual Machine. For more information, see Resources.
  3. Ensure that you have the two provided Windows Azure Pack sample jobs saved as production jobs.
    If you selected the Windows Azure Pack collector when installing Cloud Cruiser, the installer created the production jobsazure_pack_collect and azure_pack_daily_load for you and you can skip to the next step. Otherwise you must create these by saving sample jobs as production jobs. For information about the sample jobs, see Sample jobs.
  4. Ensure that you have a data source with a working connection.
    If you selected the Windows Azure Pack collector when installing Cloud Cruiser and the installation completed with no errors, skip to the next step. Otherwise configure a data source as described in Data source configuration.
  5. Edit your load job XML to perform the following tasks:
    • Edit the process_subscriptions step so that it creates account identifiers that match your account structure, then edit the transform step to match.
    • Edit the extract_subscribers step to set the correct accountLength for your account identifiers.
    • Edit the transform step to perform the desired transformation of identifiers and resources.
  6. For each resource for which you will charge, set the desired rate.
    If you want to charge for a resource at multiple rates, clone it to the appropriate Windows Azure Pack rate plans. For more information, see Setting alternative rates with rate plans.
  7. Ensure that your collection has been bootstrapped.
    This collects and loads all usage, plan, and subscription data up through yesterday, preparing Cloud Cruiser for the incremental collection and loading done by the daily jobs:
    • If you selected the Windows Azure Pack collector when installing Cloud Cruiser and the installation completed with no errors, the installer performed bootstrapping and you can skip to the next step.
    • If you selected the Windows Azure Pack collector and clicked past a Credentials are invalid message in the installer, or if you did not select this collector, perform the procedure in Resetting data to enable daily collection.
  8. Schedule both jobs to run daily against the previous day, with the load job starting thirty minutes after the collection job.
    If you selected the Windows Azure Pack collector when installing Cloud Cruiser, the installer created these schedules for you.

What to do next

Consider installing the Cloud Cruiser extensions to Windows Azure Pack to enable administrators and users to view costs from within the Windows Azure Pack management portals. For instructions, see Displaying costs in Windows Azure Pack and Allowing tenants to view their costs.

Last modified

Tags

This page has no custom tags.

Classifications

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