Patent Application
20140237485
Common Information Model (“CIM”) is a standard set forth by the Distributed Management Task Force (“DMTF”) that allows for a common model of providing information regardless of hardware or operating system (“OS”) platform. CIM provides a common definition of management information for systems, networks, applications and services and allows for vendor extensions thereto. CIM is a vendor-agnostic industry management standard. A CIM object manager (“CIMOM”) is essentially a server for servicing CIM requestsA Common Information Model (“CIM”) provider provides on a CIM platform data representing a single entity. In the case of hardware, there will theoretically be an instance of a CIM object representing each component, including, for example, each processor, video card, etc. Hardware data is derived from multiple sources, including, but not limited to, Intelligent Platform Management Interface (“IPMI”), Hardware Abstraction Layer (“HAL”), System Management BIOS (“SMBIOS”), sysfs, and proprietary third party sources. Each of these sources has its own interface, some of which are very complex. There could be a representation of each component in only one, many, or all of the available data sources.
CIM promises a single interface to obtain the information about such components; however, the CIM provider requires a component profile provider to aggregate all of the data sources into a single CIM instance. This would traditionally require that for each component entity type (CIM provider), a profile provider would have to know how to interface with each of the data sources and aggregate that data into a single object.
In response to these and other problems, in one embodiment, a method is provided for aggregating data regarding a system component from multiple data sources to provide a single aggregated Common Information Model (“CIM”) object. The method comprises requesting data regarding a system component from a first one of the data sources; upon receipt of the requested system component data from the first one of the data sources, updating an aggregate CIM object for the system component using the received system component data in accordance with a priority of the first one of the data sources relative to the remaining data sources; and repeating the requesting and updating in connection with each of the remaining data sources in accordance with a relative priority of the remaining data source.
In another embodiment, the system comprises, for each of the data sources, means associated with the data source for responding to a request for a CIM object for a system component; and an aggregation module connected to each of the means for responding; wherein responsive to a request from a client application for a CIM object for a particular system component, the aggregation module receives a CIM object for the particular system component from each of the data sources and combines the received CIM objects into a single aggregated CIM object for the particular system component.
In still another embodiment, the system comprises means for requesting data regarding a system component from a first one of the data sources; and means responsive to receipt of the requested system component data from the first one of the data sources for updating an aggregate CIM object for the system component using the received system component data in accordance with a priority of the first one of the data sources relative to the remaining data sources; wherein the requesting and updating are repeated in connection with each of the remaining data sources in accordance with a relative priority of the remaining data source.
This disclosure relates generally to CIM objects and, more specifically, to a system and method for aggregating data from multiple CIM objects regarding a system component to provide a single aggregated CIM object to a client application. It is understood, however, that the following disclosure provides many different embodiments or examples. Specific examples of components and arrangements are described below to simplify the present disclosure. These are, of course, merely examples and are not intended to be limiting. In addition, the present disclosure may repeat reference numerals and/or letters in the various examples. This repetition is for the purpose of simplicity and clarity and does not in itself dictate a relationship between the various embodiments and/or configurations discussed.
Referring to
For each of the data sources 12a-12c, a separate CIM provider, comprising a CIMOM plug-in module, is provided for publishing the data it knows about the various types of system components into its own CIM namespace. In particular, one or more IPMI providers, represented in
A composite data provider 18 includes an aggregation module 20, the function of which is to provide awareness of all of the namespaces 16a-16c and to aggregate information from those namespaces. The aggregation module 20 uses configuration settings, which may be specified in a configuration file 21, to know which namespaces to aggregate, as well as for configuration settings for precedence rules, such as which namespace is deemed more accurate than others if there is conflicting data. Additionally, the aggregation module 20 uses “deviceIDs” that contain both an entity type and an instance number to identify which devices from each namespace are common and should be aggregated. Finally, the aggregation module 20 publishes one common instance for each instance that exists in at least one of the namespaces 16a-16c. This single instance provides all known information with regard to a single system component without regard to the origin of that information.
In operation, and as more fully described below, a client application 22 makes a request to a System Management Architecture for Server Hardware (“SMASH”) namespace 24 for data regarding a system component. In accordance with features of one embodiment, the response from the SMASH namespace 24 to this request comprises an aggregated CIM object.
Referring now to
The data returned to the aggregation module 20 from each of the namespaces 16a, 16b, 16c, comprises a CIM object. Each of the CIM objects is populated differently, depending on the data source from which it was derived. In one embodiment, as will be described in detail below, the aggregation module 20 aggregates the CIM objects received from the namespaces 16a, 16b, 16c, in a manner specified by the configuration file 21, which indicates, among other things, an order of precedence among the data sources 12a, 12b, 12c. The aggregated CIM object is returned to the SMASH namespace 24, as represented by an arrow 56. The SMASH namespace 24 provides the aggregated CIM object to the client application 22, as represented by an arrow 58.
In step 64, a determination is made whether the requested object exists in the data source; that is, whether the object has been returned from the data source. If so, in step 66, all data from the returned object is copied into an aggregated object for the component of interest. In performing step 66, any existing data in the aggregated object is overwritten with data included in the returned object. As previously noted, the data sources are processed in reverse order of priority, thus ensuring that the data provided by the data source with the highest order of priority is included in the aggregated object. If a negative determination is made in step 64, execution proceeds directly to step 68. In step 68, a determination is made whether there are more data sources in the list of data sources from which to request CIM objects. If so, in step 70, the CIM object for the component of interest is requested from next data source and steps 64-70 are repeated for each of the remaining data sources. If a negative determination is made in step 68, execution proceeds to step 72. In step 72, the aggregation is complete and the aggregated object is returned to the client application, as described with reference to
It will be recognized that, as opposed to being sorted in reverse order of priority, the list of aggregate data sources obtained in step 60 may be sorted in order of priority, in which case, in step 66, the only data that will be copied from the returned object into the aggregated object will be data that does not already exist in the aggregated object.
While the preceding description shows and describes one or more embodiments, it will be understood by those skilled in the art that various changes in form and detail may be made therein without departing from the spirit and scope of the present disclosure. For example, various steps of the described methods may be executed in a different order or executed sequentially, combined, further divided, replaced with alternate steps, or removed entirely. In addition, various functions illustrated in the methods or described elsewhere in the disclosure may be combined to provide additional and/or alternate functions. Therefore, the claims should be interpreted in a broad manner, consistent with the present disclosure.
This application is a continuation of U.S. patent application Ser. No. 11/376,907, filed Mar. 16, 2006, now allowed, which is incorporated by reference herein for all purposes.
| Number | Date | Country | |
|---|---|---|---|
| Parent | 11376907 | Mar 2006 | US |
| Child | 14263890 | US |
