The following features are new or enhanced in Cloud Cruiser version 3.3.0.
This release adds a native collector for VMware vCloud Networking and Security, formerly known as VMware vShield. The collector collects configuration data about Edge Gateways from the vCloud Networking and Security REST API.
For information about using this collector, see VMware vCloud Networking and Security. Javadoc for the collector is available at
In this release, you no longer need to manually request usage reports from the Windows Azure Enterprise Portal. When you run the collector, it requests a report for the selection date, waits for the report to become available, and then downloads it. The procedure To set up regular collection and loading of data has been updated accordingly.
The following enhancements apply to Cloud Cruiser's batch processing language.
This release adds a set of new values to choose from when setting the select date in a job schedule or running a job from the command line. The new options, Current Day Minus 2 Days through Current Day Minus 14 Days, allow you to daily run an automated job with a select date more than one day in the past. This enables the automatic collection of Microsoft Azure data, which becomes available several days after usage is completed.
This release adds a new filter for conditional processing,
ResourceNameMatchesCondition. This filter matches the resource names in a record against a regular expression.
This release adds a new transform processor for batch jobs,
CreateException. This processor writes the current record to an exception file if it meets specified filter conditions. This enables you to remove bad data from a dataset with visibility, as opposed to simply dropping these records with DropRecord.
For reference information about this filter, see CreateException.
The aggregation tasklet,
CCRecordAggregationTasklet, can now aggregate separate chunks of records within a daily interval. When the
adjustUsageInterval property is set to false, the tasklet merges two records if there is one minute or less separating their usage timeframes. Previously it would merge all records from the same day into a single record regardless of how much time separated them.
For example, records with the following times will now aggregate into one record from 10:00:20 to 11:59:58 and another from 13:03:27 to 14:59:59:
|Start time||End time|
You can still merge all records from the same day into a single record by setting
adjustUsageInterval to true. In this case, the start time of the merged record is 0:00:00 and the end time is 23:59:59.
The ImportNewResources transform processor now has a new property,
resourceGroupIdentifier. When set, this property specifies an identifier whose value becomes the name of the resource group into which all resources in the current record are imported.