Browse Prior Art Database

Dynamic Provider Layer Update Mechanism for CIM agents

IP.com Disclosure Number: IPCOM000185417D
Original Publication Date: 2009-Jul-24
Included in the Prior Art Database: 2009-Jul-24
Document File: 5 page(s) / 46K

Publishing Venue

IBM

Abstract

Mechanism for providers to dynamically choose and apply the most appropriate update technique to any set or subset of a CIM schema.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 52% of the total text.

Page 1 of 5

Dynamic Provider Layer Update Mechanism for CIM agents

The role of the DS8000/DS6000 CIM agent is to maintain a global space (or a set of spaces) of CIM data representing the configuration, capabilities, and services of the device. For example, Figure 1 represents what an example total dataset of CIM data might look like.

CIM Data Available

Volume 1

Volume 1 Statistics

  Array 1 Vol Creation

Volume 2

Volume 2 Statistics

  Array 2 Vol Creation

FCPort 1

Volume 3

Volume 3 Statistics

FCPort 2

Volume 4

Volume 4 Statistics

FCPort 3

Figure 1

What the CIM agent must do to generate the CIM data is make various calls to the device it is managing and then translate information received form the device into CIM data. The latencies of the device calls required to generate the CIM data are often long. This can be due to the inherent nature of storage devices (the management stack is often slow) or possibly the environment the CIM agent and storage devices are in (i.e., long distances between servers, intermittent networks). To compensate for the various types of latencies when querying the device, CIM agents can employ a variety of update techniques to generate the CIM data.

The CIM agent needs to know what data to update and how to keep it coherent. Here is where the problem arises, as the global space of CIM data is large and complex. The various areas of CIM data require different approaches to maintain coherency. For example:

Some pieces of CIM data may only be able to be generated from the device at some maximum interval. On DS8000 devices Statistical information for volume, FCPorts and pools can only be retrieved from the device at some maximum interval (i.e., once every 5 min).

Some pieces of CIM data may never change unless an event occurs. On DS8000 devices, once pool information is retrieved, it stays the same until a pool is added, deleted or modified. This may

1

Page 2 of 5

occur often, rarel

y

or even never after initial installation.

Because of the wide variety of CIM data available in the global space and the various methods to maintain coherency, a general update mechanism will not address all the requirements for all the CIM data.

Maintaining the space of CIM data requires more than update techniques. The CIM agent requires a mechanism that allows it to apply the best suited update method (be it with caching techniques, no-caching or other) at a level of granularity that allows different areas of the total CIM data space to be serviced as is best suited for that particular data.

Without this invention implementing, general update techniques becomes a daunting task as there is not a manageable way to apply an update technique to some part of the CIM data, updating everything is not acceptable, and updating portions does not have enough coverage of the CIM data. Developers going through the CIM data set and providing update solutions to different CIM data manually is also too daunting of a tas...