This section contains the cumulative release notes for Cloud Cruiser version 4.3.x. The current release is version 4.3.8.
All documentation articles updated for this release have the tag version_4.3. List these articles.
Cloud Cruiser can now connect to HP Cloud Service Automation using Transport Layer Security (TLS) versions up to 1.3. Previously, only TLS 1.0 was supported.
HP Cloud Service Automation Subscription data sources now have an SSL Negotiation setting. When you select Full, Cloud Cruiser will request a TLS v1.3 connection and negotiate down from there.
The following features are new or enhanced in Cloud Cruiser version 4.3.7.
There is now the ability to import both data sources and schedules as well as to export both datasources and schedules to a CSV file. New menu options are now available in Data > Setup > Sources and Data > Processing > Scheduling tab respectively.
The following bug is fixed in the Cloud Cruiser 4.3.7 release:
|When a user is running the help menu in the command line; datasourceSetup -s is being shown, which is not supported. Also in the command line, Updates and Duplicates were being shown in the command line output while running Import commands..||MAINT-386|
See Bugs fixed in 4.3.7 for information about the bugs fixed in this release.
The following features are new or enhanced in Cloud Cruiser version 4.3.5.
By default, clicking the main logo in the upper-left corner of the Cloud Cruiser interface opens the Cloud Cruiser website in a new browser window. You can now change the URL to open a different page, such as a page on your corporate intranet. For more information, see Rebranding the user interface.
See Bugs fixed in 4.3.5 for information about the bugs fixed in this release.
The following feature is enhanced in Cloud Cruiser version 4.3.4.
For individual jobs, you can now override the global setting for enabling/disabling the charge step. Cloud Cruiser includes a global setting that enables you to disable the charge step for all jobs. This enables you to test your Cloud Cruiser implementation as you are working, without generating charge records that would otherwise need to be removed each time you run an ETL workbook.
If you want to override that global setting for any specific job, open your job's XML file and set the
ignoreChargeEnabledFlag parameter to
true. For more information, see Disabling and enabling the charge step in jobs.
Cloud Cruiser 4.3.3 fixes bugs, several of which improve the reliability and accuracy of charge jobs. For the full list see Bugs fixed in 4.3.3.
The following features are new or enhanced in Cloud Cruiser version 4.3.0.
Cloud Cruiser now includes the CloudSmart-Now packaged offering, enabling you to collect, process, and publish billing and usage data faster than with the standard collection methods available in earlier versions of Cloud Cruiser.
CloudSmart-Now solutions work out-of-the-box with minimal configuration for the following public and private clouds:
As part of the CloudSmart-Now packaged offering, Cloud Cruiser includes services for private cloud data sources to handle common chargeback use cases, and automatically matches usage to these services. Additionally, Cloud Cruiser includes baseline rates to speed implementation time. These are based on a sampling of actual service-provider rates to provide a realistic starting point for your needs.
To get started with CloudSmart-Now, see CloudSmart-Now.
Cloud Cruiser has expanded its What-If capabilities with the ability to help you decide which workloads provide the necessary services at the best cost. To do this, build scenarios that compare the estimated costs for different groups of services. For example, you might compare services offered from a single provider to see which is the best value from that provider. You might then compare that workload against a similar workload from a different provider to help you make an informed business decision about the services you purchase. For more information, see What-If for new workloads.
What-If functionality in Cloud Cruiser requires a special license. If you do not see What-If available in the Cloud Cruiser navigation pane, contact Cloud Cruiser.
The following bugs are fixed in the Cloud Cruiser 4.3.5 release:
|Cloud Cruiser allowed 2 batch, workbook or reporting jobs to run at the same time. The duplicate job would fail without warning. You now see a warning in the scheduler when times for same schedule overlap.||N/A|
|When loading data, Cloud Cruiser truncated passthrough costs to 2 decimal places, propagating a charge of 0 to the charge job in the rare event that the charge could not be rounded to at least 0.01. (For example, 0.003456).||N/A|
The following bug is fixed in the Cloud Cruiser 4.3.4 release:
|While you could disable the automatic charge step for all jobs, you could not manually run the charge step when charge is disabled.||MAINT-293|
The following bugs are fixed in the Cloud Cruiser 4.3.3 release:
|After loading data for a range of dates, if you later re-ran the charge for an early date in that range, Cloud Cruiser was missing some data that was previously there.||MAINT-282|
|For charges allocated hourly, Cloud Cruiser did not report charges accurately.||MAINT-277|
|Cloud Cruiser was incorrectly reading ampersand characters in Jasper report filters as an escape character instead of a literal character.||MAINT-276|
When running a charge job, Cloud Cruiser produced the following error:
|When running Windows Azure Pack collection from a workbook, Cloud Cruiser would stop collecting data when it encountered a resource with an ||MAINT-149|
|When using a Min Commit value for a service with the Basic Rate Type, Cloud Cruiser sometimes generated incorrect charges.||MAINT-146|
|When using a Min Commit value for a service with the Basic Rate Type, Cloud Cruiser generated two charge records for the service.||MAINT-142|
The following are the minimum hardware and software requirements for Cloud Cruiser and its components.
Cloud Cruiser recommends that you install Cloud Cruiser, Cloud Cruiser Analytics Server, and your database server on separate computers. These system requirements apply to that architecture.
You should also install Cloud Cruiser Analytics Desktop on this computer.
You must use the 64-bit version of one of the following operating systems:
The Server Core installation option of Windows is not supported. The Cloud Cruiser installer requires a graphical user interface and cannot be run within a command window.
Using the X Window System requires that the
DISPLAY variable be set. After you restart Cloud Cruiser, this variable can cause Cloud Cruiser reports to render improperly. To work around this issue, complete one of the following actions:
CATALINA_OPTSsection of the
The 64-bit version of Java Standard Edition 8 (JDK or JRE) is required. Versions earlier than 8 are 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 8 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 44, 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 documentation for Cloud Cruiser 4.x is located at Cloud Cruiser 4.
In addition to the documentation available on this site, version 4 has more help within the Cloud Cruiser Portal. This includes help for windows, dialogs, and the functions and parameters in Data > Workbooks.