This section contains the cumulative release notes for Cloud Cruiser version 3.4.x. The current release is version 3.4.0.
All documentation articles updated for this release have the tag version_3.4. List these articles.
The following features are new or enhanced in Cloud Cruiser version 3.4.0.
Cloud Cruiser can now collect Microsoft Windows Azure Pack data supplied by GridPro, a new service provider to Windows Azure Pack.
If you are upgrading from a previous version, to collect GridPro data you must do the following:
<install_dir>/job_samples/azure_pack_daily_load.xml, customizing as necessary.
The OpenStack Ceilometer Collector can now collect from systems that don't use the default name for either the Service project (tenant) or the Admin project. You specify the names of these projects in an OpenStack data source.
For instructions, see Creating a data source.
The AWS Collector collects unblended charges by default, which provides the most reliable results on a daily basis. With this release you can now collect blended charges, which include discounts from pricing tiers and reserved instances. For the best results, collect unblended charges daily and then after you have a final report for a given month, unload that month's data from Cloud Cruiser and collect blended charges.
You specify which type of rates and charges to collect using the
useBlendedValues property of the
AWSFeedConfig feed configuration bean. For instructions, see the procedure in Amazon Web Services.
You can now deploy Cloud Cruiser with a two-server architecture that provides report-only access to clients located outside your network while keeping data secure behind your firewall.
Install one instance of Cloud Cruiser behind your firewall and use it as normal for any tasks. Install a second instance in your DMZ, pointing to the same database, and set the new
reportOnly profile to active in the system properties file. Your customers or other users from the Internet can log in to this instance to view reports, but the instance is unable to run batch jobs, preventing it from modifying data if it were compromised.
For instructions, see Deploying an external reporting server.
You can now include more information in exception records, making their cause easier to determine, by setting two new properties on the
exceptionIncludeTransform: When true, exception records include the identifier
@transform. This identifier is set to a number representing the transform processor that generated the exception, in processing order within its transform step.
exceptionIncludeMessage: When true, exception records include the identifier
@exception. This identifier contains a message stating what caused the exception.
These properties are optional, and default to false. For more information, see the Javadoc for
You can now create an identifier that holds the name of the rate plan associated to the customer responsible for the usage in a CC Record. The new transform processor
CreateRatePlanIdentifier looks up the rate plan for an account ID you specify and returns its name as the value of an identifier. If no customer record exists for the account, the processor returns the
default rate plan.
For instructions, see CreateRatePlanIdentifier.
The following bugs have been fixed since the Cloud Cruiser 3.3 release:
|Upgrading from version 2.3.1 failed with the message ||2950|
|Collection from Microsoft Windows Azure failed with the error message ||3689|
An empty Windows Azure Pack plan name caused collection to fail.
Subscriptions associated with such a plan are now associated to the default Cloud Cruiser rate plan, allowing their usage charges to be loaded.
Microsoft intends to populate plan names again starting with Windows Azure Pack Update 2, which would assign names to plans for which you have previously collected usage data. In this case a corresponding rate plan is created in Cloud Cruiser the next time you load Windows Azure Pack data. However, you must manually associate the appropriate subscriptions with it. You can quickly find these customers by scanning the list for customers at the Subscription level that have no description. Other customers have a description matching their Windows Azure Pack plan name.
Windows Azure Pack usage from a service provider not recognized by Cloud Cruiser prevented data from being loaded into the Cloud Cruiser database.
This usage is now written to records that do not contain a resource so that it is auditable even though it can't be loaded into Cloud Cruiser.
If you are upgrading from a previous version, to pick up this fix you must replace your Windows Azure Pack load job with the new sample job
When the input file specified for a charge step is not found, the job fails with the following error:
The Resource Invoice and Resource Invoice Summary reports displayed incorrect account IDs when run using an Account Structure other than the default structure.
This fix is not applied when upgrading from a previous version. You must uninstall Cloud Cruiser, leaving your database intact, and then install version 3.4.
|When specifying parameters for a standard report, sometimes the Account Level menu displayed duplicate items.||None|
You should also install Cloud Cruiser Analytics Desktop on this computer.
The 64-bit version of Java Standard Edition 7 (JDK or JRE) is required. Version 8 is not supported.
You can download Java at http://www.java.com/getjava. The navigation of this site changes often, so you might need to look carefully to find version 7 in 64 bits.
One of the following operating systems:
A database server is not included with the Cloud Cruiser installation. You must provide one of the following database servers:
For hardware and operating system requirements for this computer, see the documentation for your database server. Storage needs will grow as Cloud Cruiser accumulates data over time.
One of the following browsers:
As of the last update to this article, Cloud Cruiser has been tested with Firefox 32 and Chrome 37, and we continue to test with new, automated version updates of these browsers. The application should continue to function with such versions. However, some issues could arise that can only be resolved with subsequent patches to Cloud Cruiser or by reverting the browser update.
The following programming documentation for Cloud Cruiser is provided in the