Consumption Analytics Documentation

Home > Documentation for older versions > Cloud Cruiser 4 for HPE GreenLake Flex Capacity > Cloud Cruiser architecture and workflow > Cloud Cruiser architecture

Cloud Cruiser architecture

This topic provides an overview of the physical and logical architecture of Cloud Cruiser

Physical architecture

Cloud Cruiser is deployed across three environments:

  • DEV​
  • ITG
  • PROD 

Within each environment are four servers:

  • Database
  • Application Server
  • Analytics Server
  • Apache front-end

Database server

The database server performs the following tasks:

  • Hosts the Cloud Cruiser database, ccdb.
  • Stores the collected usage data and associated charges
  • Stores the configuration of services, rate plans, and customers
  • Stores the configuration of users and user groups
  • Provides data to the reporting engine and the analytics servers

The database can be Microsoft SQL Server 2012 or later, running on Microsoft Windows Server 2012 or a suitable cloud-based DBaSS.

Application server

The application server hosts the following aspects of the solution:

  • User Interface
    • Workbook editor
    • Services, rate plans, and customer administration and maintenance
    • Standard reporting
  • Batch jobs
    • Daily download process
    • Scheduled workbooks
    • All functionality involving the load and unload of data into the database
  • API functionality

All collected usage data resides on the filesystem of the application server. The application server is effectively a system service, and must be managed as such.

The application server must be running RHEL 6.

Analytics server

The Analytics server hosts the Tableau server (for Insights) and its database. The analytics server must be running Microsoft Windows Server 2012.

Apache front-end server

The front-end server is a dedicated instance of Apache that forwards web traffic to the back-end application server. This is a requirement of HP security policies.

Logical architecture

The following key logical elements comprise the FC metering and billing solution:

  • Remote metering scripts
  • Central upload mailbox
  • IMAP download to central server
  • Data processing, sorting, and dissemination
  • Workbook processing
  • Usage load
  • Reporting and analytics

The following diagram shows the flow of the logical architecture:logicalArchitecture.jpg

  1.  Metering scripts collect data from resources into usage files.
  2. Metering scripts mail usage files to the FC gmail account.
  3. The _DownloadUsage workbook receives usage files as email.
  4. The _DownloadUsage workbook does initial processing and puts usage files in the file system.
  5. The _ProcessUsage workbook does initial processing of usage files, and the customer-specific workbooks finish the processing.
  6. Customer-specific workbooks publish usage data to schemas.
  7. The publish step triggers the Charge Engine, which gets usage data from schema, service and rate plan data, and then creates charge records.
  8. Tableau creates nightly extracts of Cloud Cruiser data for use with Insights.
Last modified


This page has no custom tags.


This page has no classifications.

 (c) Copyright 2017-2020 Hewlett Packard Enterprise Development LP