Home > Cloud Cruiser 4 > Collecting, transforming, and publishing > Microsoft Windows Azure Pack

Microsoft Windows Azure Pack

Windows Azure Pack orchestrates several resource providers to manage a private cloud. These providers post usage data for services such as databases, websites, and VMs to Windows Azure Pack's usage database. Cloud Cruiser's Microsoft Windows Azure Pack solution queries the Windows Azure Pack Usage API for this usage data, as well as data about subscription events. You will see charges for usage related to:

  • Various sizes of virtual machines
  • VM storage allocated
  • VM storage used (optional)
  • SQL Server database access and space
  • MySQL Server access and space
  • Webspaces allocated
  • Incoming and outgoing network traffic (for a website)

By default, Cloud Cruiser charges for VM storage allocated. If you would rather charge by VM storage used, on the Services page show inactive services, activate the WAP VM Storage Used service, and then deactivate the WAP VM Storage Allocated service.

The costs you see in the Cloud Cruiser portal and Windows Azure Pack portals are not real-time information. Every night, Cloud Cruiser collects subscription and usage data for the previous day from the Windows Azure Pack Usage API. Therefore, if a VM is created on Monday you will see costs for that VM Tuesday morning.

For more information about Windows Azure Pack collection, see the following topics:

CloudSmart-Now prerequisites

If you want to use the CloudSmart-Now solution for Windows Azure Pack, you must complete the following tasks:

Before you begin

Cloud Cruiser uses the Usage REST API of Windows Azure Pack to retrieve subscription and usage data. Because the user account it connects with, UsageClient , has a randomly-generated password by default, you must set a new password that you can provide to the Cloud Cruiser data source. If you did not set this password as part of the Cloud Cruiser installation process, do so now.

To set the Usage REST API password

  1. On the Microsoft Windows Azure Pack Admin Site machine, open a Windows PowerShell window.
  2. Execute the following command:
    Set-MgmtSvcSetting -Namespace UsageService -Name Password -Value '<newPassword>' -Encode
  3. Note the new password you created so that you can provide it in the Cloud Cruiser data source.

Configuring Cloud Cruiser to collect, transform, and publish Windows Azure Pack data

To collect, transform, and publish Windows Azure Pack data

  1. Modify the WAP data source named WAP1 to work with your Windows Azure Pack account:
    1. Navigate to Data > Setup > Sources.
    2. Click the WAP1 data source.
    3. In the Endpoint field, enter the URL for the Microsoft Windows Azure Pack Enterprise Portal, formatted as https://<adminSite>:30022, where <adminSite> is the hostname or IP address of your Windows Azure Pack Admin Site machine.
    4. In the Username field, enter the username to your Windows Azure Pack Admin Site machine. The user name is UsageClient unless you changed this name with a Set-MgmtSvcSetting command.
    5. In the Password field, enter the API password to your Windows Azure Pack Admin Site machine.
      WAPDataSource.jpg
    6. Click Save.
  2. Create a Windows Azure Pack workbook:
    1. Navigate to Data > Workbooks.
    2. In the list of workbooks, right-click and select Add New Workbook.
    3. Enter a Workbook Name and (optionally) a Workbook Description.
    4. Check the Create Workbook from Template box, and then select the Microsoft Windows Azure Pack template.
    5. Click OK.
      A new workbook opens, already containing the necessary collections and workflow.
    6. Click Save to save the workbook.
  3. Test your workbook:
    1. In the Workbook ribbon, click Run.
      The Run Workbook dialog box opens.
    2. In the Select Date field, enter the previous day's date.
    3. Select all of the collections and flows, and then click Run.
    4. After the run finishes, click View Log at the bottom left of the dialog box to open the Monitoring window, where you can view the log for any specific collection or flow.
    5. If your workbook test run did not complete successfully, or if it did not provide the data you need, edit the workbook and then run another test. For more assistance, see Troubleshooting Windows Azure Pack collection.
  4. When you are done editing your workbook delete any test data loads:
    1. Navigate to Data > Processing > Published Loads.
    2. Select one or more entry rows and click Delete Load(s) at the top of the page.
    3. Click Yes to confirm the deletion.
  5. When you are ready to put your workbook into production, start the next procedure, Scheduling regular collection.

Scheduling regular collection

After configuring Cloud Cruiser to collect, transform, and publish your Windows Azure Pack data, create a schedule that defines when and how often to run those processes.

To schedule regular collection

  1. Go to Data > Processing > Scheduling.
  2. In the Schedules section, click New.
    The New Schedule dialog box appears.
  3. In the Job Type field, select Workbook.
  4. In the Name field, enter WAP.
  5. (Optional) In the Description field, enter a description for this schedule, such as Daily schedule for WAP data.
  6. Set Enabled to Yes so that the schedule will run.
  7. In the Frequency section, set the Start Date to the first date that you want the schedule to run, usually today's date.
  8. In the Recurrence field, select Daily.
  9. In the Start Time field enter the time of day the schedule will run, 02:15.
  10. In the Workbook field, select WAP.
  11. In the Workbook Components section, select all of the components and flows.
  12. Click OK.
    The new schedule is added to the list.
Last modified

Tags

Classifications

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