Mapping data to Cloud Cruiser

Table of contents

The collector’s query to UCS Manager results in a list of XML elements of the specified class, so data mapping for the Cisco UCS Collector is based on data mapping for the XML Collector. To see the exact documents that are parsed for data mapping, set the printEntityXML property of the Cisco UCS collector to true and run collection from a command line using ccjob.

Feed configuration

Feed configuration for the com.cloudcruiser.batch.collect.cisco.UCSFeedConfig bean extends the basic XmlFeedConfig bean with the following properties:

classId: Specifies the Cisco UCS class to query.

hierarchical: A flag that when true increases the depth of the results to include config objects contained by the target class.

filter: Restricts results using the filter capability of the underlying UCS Manager XML API. See the API documentation for UCSPropertyFilter and UCSCompositeFilter for more information.

Time and date

All timestamps in the XML data collected from Cisco UCS are in UTC.

Identifiers

There is typically a relative name (rn) or a designated name (dn) for an entity in the model. These names are distinct and represent a path to the instance in the information tree. Other identifiers may include serial number, model, and UUID values.

The following identifiers are mapped from computeBlade entities in the sample job:

uuid

vendor

model

dn

assignedToDn

chassisId

operPower

Resources

Each instance of a given class of configuration item may be considered a resource. For example, each computeBlade node represents one blade.

The state of an item may affect pricing, in which case you should capture a state identifier or include a state indicator in resource names. For example, you can filter out a powered-off blade before loading charge data or else capture the power state to avoid charging the same amount as a powered on blade.

The following resources are mapped from computeBlade entities in the sample job: