Computerworld - Without a way to put together multivendor storage components and manage them effectively, much of the value proposition of storage-area networks (SAN) is moot. Users are either shackled to one seller's technology or face an expensive, laborious process in order to jury-rig management applications that work across all components of their SANs.
But now, slowly swimming through the murky waters of the standards adoption process, comes Bluefin, a storage management protocol drafted by a group of 16 vendors and presented for review in May to the Storage Networking Industry Association (SNIA) in Mountain View, Calif. Late last month, the SNIA launched its Storage Management Initiative (SMI) aimed at fostering the full development and adoption of Bluefin and related specifications.
According to the SNIA, Bluefin will provide the key to making disparate storage hardware and software work together and thereby revolutionize networked data storage. Talk of revolution may be premature, however, since Bluefin is a consolidation of and an incremental step beyond two existing standards: the Common Information Model (CIM) and the Web-Based Enterprise Management interface.
CIM is central to Bluefin, providing an object model—a standardized way to describe the physical and logical components of the storage network. Each component has its own CIM profile, whether it's a disk array, a Fibre Channel fabric device or any other part of the network. If CIM provides the vocabulary of SAN management, Bluefin gives that vocabulary grammatical structure. That is, it standardizes the way the components communicate with one another and perform key functions.
Bluefin provides rules for three crucial services: device discovery (when a Bluefin-compliant product is plugged into a SAN, it announces itself and its capabilities to other SAN components); security against unauthorized reconfiguration of the SAN; and locking, which keeps various management applications from interfering with one another.
A key feature of Bluefin is its two deployment models. In the first, a Bluefin agent is embedded into a Bluefin-compliant storage device. In the second, the agent sits on a proxy server that intermediates between a management application and a storage device that doesn't support Bluefin. The second model is crucial because it allows Bluefin to support legacy storage installations.
Free Insider GuideCopyright © 1994 - 2012 Computerworld Inc. All rights reserved. Reproduction in whole or in part in any form or medium without express written permission of Computerworld Inc. is prohibited. Computerworld and Computerworld.com and the respective logos are trademarks of International Data Group Inc.
