This section contains the cumulative release notes for Cloud Cruiser version 3.5.x. The current release is version 3.5.0.
All documentation articles updated for this release have the tag version_3.5. List these articles.
The following features are new or enhanced in Cloud Cruiser version 3.5.0.
The Cloud Cruiser REST API now includes methods for getting, deleting, importing, and exporting translation tables. The reference documentation for these methods is at Translation tables.
The following enhancements are made to collectors or tasklets that participate in collection in this release.
The following enhancements are made to the OpenStack Ceilometer Collector in this release:
includeMetaproperty to true.
<property name="dateTimeZone" value="UTC" />
<property name="dateTimePattern" value="yyyy-MM-dd'T'HH:mm:ss" />
<property name="datePattern" value="yyyy-MM-dd'T'HH:mm:ss" />
The following enhancements are made to the OpenStack AMQP Collector in this release:
AMQPConsumerTasklet, enables you to specify a list of event types, each with its own pattern.
<install_dir>/job_samples/nova_event_listener.xmlor the JavaBean Reference documentation at
The JSON Collector can now map data from lists of both objects and intrinsics using standard JSONPath expressions. For information about this, see Mapping data to Cloud Cruiser.
When importing customer records using
CustomerCCRecordCollector, you can now use a standard
filter property to specify which CC Records should be imported.
The following transform processors are added or enhanced in this release. For information about these processors, see the JavaBean Reference documentation at
There are two enhancements in this release:
syncDeleteEnabledtell the processor whether to trust the control feed over the records being processed. When
syncInsertEnabledis true, the processor creates a new CC Record when a record exists in the control feed without a corresponding record in the processed set. When
syncDeleteEnabled is true, the processor deletes a CC Record when no corresponding record exists in the control feed.
The new property
defaultToSourceOnException controls what happens when no match is found and exception processing is off. When true, the value of the source identifier is written to the target identifier, the previous behavior of the processor. When false, the processor does nothing to the record.
This new processor drops all identifiers except those specified.
This processor now creates an empty output file instead of no output file when no records are diverted.
This new processor subtracts one second from the end time. This is needed when data contains an exclusive end time because we expect inclusive end times.
This new processor modifies a record to have only an end time by dropping the start time. If no end time exists, the start time is copied to the end time before being dropped.
This new processor modifies a record to have only a start time by dropping the end time. If no start time exists, the end time is copied to the start time before being dropped.
The following batch tasklets are enhanced in this release.
The exception file for a transform step using
CCRecordTransformTasklet is now initialized before record processing begins. This ensures exceptions from a previous run are cleared out if the job is executed again for same date.
CCRecordSortTasklet compares timestamps to sort records where all other identifiers match, where both start and end times exist the comparison now uses the start time by default. Previously the end time was the default. You can compare end times by setting the new
preferEndTime property to true.
This change was to resolve issues with event correlation because true chronological order is expected there. For information about
CCRecordSortTasklet, see the JavaBean Reference documentation at
defaultFunction property of
CCRecordAggregationTasklet now accepts a value of
DISTINCT. This function combines only records where all resource values match. These values are untouched: aggregation only merges usage periods and mutable identifiers. You can also use
DISTINCT when using
AggregateResource to specify the aggregation function for an individual resource.
For information about
CCRecordAggregationTasklet, see the JavaBean Reference documentation at
All timestamps in the Job Monitoring window, including log messages, now include hours, minutes, and seconds.
The REST API method for running a report has a new element
extraParameters that enables you to pass job-specific parameters to the report engine.
The following bugs have been fixed since the Cloud Cruiser 3.4 release:
The Microsoft Azure collector failed with the error
Microsoft Azure displays this shorter date format on some usage reports requested during April 2014, regardless of the date range requested. When the collector now encounters such a report, it ignores the report (it needs exact dates) and continues scanning the list of available reports to find another one matching the selection date for the current run. If the dates for which you want to collect data are in a report listed with short-format dates, you must request a new report for the same date range.
The Microsoft Azure collector failed with the error
The collection job now completes without failing.
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 was released in version 3.4 but was not applied when upgrading an existing installation. Upgrading to version 3.5 does apply the fix.
|The Profit and Loss By Account report showed an incorrect GM% value of ||None|
|The Windows Azure Pack Collector failed when the hostname of a data source included the string ||3805|
|The sample job for the Windows Azure Pack Collector had a low exception limit for records with a ||None|
|After attempting to save a customer, transaction, discount, or surcharge with certain missing or incorrect information, the Save and Cancel buttons did not reappear even after editing the object to correct the error.||3354|
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