This section contains the cumulative release notes for Cloud Cruiser Express version 3.4.x. This includes the new and updated features, bug fixes since v3.2.1, and the system requirements. The current release is Cloud Cruiser Express 3.4.0. The full documentation for this release is available at Cloud Cruiser Express v3 for Windows Azure Pack.
This release contains all of the enhancements in Cloud Cruiser 3.4.0. The following enhancements affect Cloud Cruiser Express users. The remaining enhancements and fixes in this release are instantly unlocked when you purchase an upgrade to Cloud Cruiser.
Cloud Cruiser Express 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 import the Windows Azure Pack resources in
You can now deploy Cloud Cruiser Express 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 Express 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.
This release contains all of the bug fixes in Cloud Cruiser 3.4.0. The following fixes affect Cloud Cruiser Express users. The remaining fixes in this release are instantly unlocked when you purchase an upgrade to Cloud Cruiser.
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
|The Resource Invoice and Resource Invoice Summary reports displayed incorrect account IDs when run using an Account Structure other than the default structure.||3693|
|When specifying parameters for a standard report, sometimes the Account Level menu displayed duplicate items.||None|
The following are the minimum hardware and software requirements for Cloud Cruiser Express and its components.
Cloud Cruiser recommends that you install Cloud Cruiser Express, your database server, and Windows Azure Pack on separate computers. These system requirements apply to that architecture.
You must use the 64-bit version of Microsoft Windows Server 2008, 2012, or 2012 R2.
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.
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.
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.