implementation of storage network industry association...

1© 2007 EMC Corporation. All rights reserved.

Implementation of Storage Network Industry Association (SNIA) SMI-S Standard for Symmetrix and CLARiiON

Richard RoscoeEMC Corporation


What is SMI-S?

SMI-S is the Storage Management Initiative Specification. It is an ISO and ANSI standard.

It is a set of object-oriented interfaces designed to make it easier forheterogeneous storage hardware and software from multiple vendors to work together under a controlled setof interoperable standards.

The Storage Network Industry Association (SNIA) Consortium is charted with Development, Acceptance, andCertification of the SMI-Specifications.

“Plug & Play”


Why use SMI-S?EMC view

– Common object modelSymmetrix, CLARiiON, Celerra, Invista, Centera, CDLBase classes have properties than can be shared

– Common managementSingle user interface possible for EMC devices

– Allows vendor extensionsEach EMC device can have extensions to the base classes

– Transport protocolOne transport protocol that can be both public and private

IT view– SMI-S delivers increased flexibility and freedom of choice

Management applications can configure and control multivendor environment (array, switch, HBA, tape library…)No need to purchase or operate different management apps for each device

– Reduces management costsReduces training requirements for multiple management appsReduced complexity and increased normalization in managing SAN


Web-Based Enterprise Management

WBEM is a DMTF standard that is defined by a set of standards that include:

• Common Information Model (CIM): A Data Description Standard that describes the resources to be managed.

• CIM-XML: A Communication Protocol Standard that defines an encoding and a transport protocol.

DMTF Board Members: Cisco, Dell Computer Corp., EMC, Hewlett-Packard Company, IBM, Intel Corporation, Microsoft Corporation, NEC Corporation, Novell, Oracle, Sun Microsystems, Inc., Symantec Corporation, VERITAS Software, WBEM Solutions

WHAT

HOW

Web-Based Enterprise Management (WBEM) is a platform- and resource-independent DMTF standard that defines both a common model (i.e., description) and protocol (i.e., interface) for monitoring and controlling resources from diverse sources (e.g., different types of platforms or different types of resources on the same platform).

DMTF Specifications and Schema are available at: http://www.dmtf.org

CIMData Description

TransportEncodingCIM-XML

Distributed Management Task Force, Inc.


What is CIM (Common Information Model)?

CIM is the object model for WBEMProvides a common definition of management information for systems, networks, applications, and services, and is composed of a Specification and a Schema

– CIM SpecificationDefines the integration details with other management models

– CIM SchemaIs specified by MOF and provides the actual model descriptionsThe latest version of the CIM Schema is V2.9/V2.10

CIM Schema is specified by MOF (Managed Object Format)Allows vendor extensions


WBEM Communication ProtocolCIM-XML is a DMTF WBEM Communication Protocol Standard that provides a formal description of the operations, protocol, and encoding used between the client and server and includes:

– Use of the CIM Specification & CIM Schema for the representation of managed resources.

– CIM Operations: A standard set of operations for monitoring and managing CIM Modeled resources.

– A CIM-XML Encoding: A standard for encoding CIM data and operations into XML.

– An HTTP Transport Protocol: The definition of a standard protocol for transporting CIM-XML encoded requests and responses over HTTP.

Service Location Protocol (SLP): A standard that provides a way for applications to identify and interact with WBEM management systems.


CIM Operation Solution Components

A CIM Server receives and processes CIM Operation requests and issues CIM Operation responses.

A CIM Client issues CIM Operation requests and receives and processes CIM Operation responses.

A CIM Provider translates CIM formatted requests into resource-specific operations and translates resource-specific responses into CIM formatted responses.

A Managed Resource is a manageable entity (e.g., memory, process, system, application, network) plus the resource-specific instrumentation capable of monitoring and controlling the resource.

Managed Node

Managed Resources

CIM Providers

Management Node

CIM Client

CIM Server

CIM

Schem

a

CIM Operations


The Client CIM OperationsAssociatorsAssociatorNamesReferencesReferenceNamesGetPropertySetPropertyGetQualifierSetQualifierInvokeMethod

GetClassGetInstanceDeleteClassDeleteInstanceCreateClassCreateInstanceModifyClassModifyInstanceEnumerateClassesEnumerateClassNamesEnumerateInstancesEnumerateInstanceNamesExecQuery


CIM Indication SolutionComponents

• Event. The occurrence of a phenomenon of interest. For example, an event can denote the occurrence of a disk write error, a failed authentication attempt, or even a mouse click.

• Indication. The representation of the occurrence of an event.

• Indication Subscription. The process of registering to receive indications.

• Indication Delivery. The process of transporting one or more indications to a designated destination. The intended protocol and destination are specified as part of the subscription definition.

• Subscription Client. A CIM Client application that creates subscriptions.

Managed Resources

CIM Indication Providers

Managed Node

Management Node

CIM ClientSubscriber

CIM Server

Indication Consumer

ManagementNode

CIM Listener

Indication Receipt & Consumption

Indication Generation& Delivery

Indication Subscription

IndicationDelivery

Event Detection &Indication Generation

IndicationSubscription

SubscriptionClient


Conceptual WBEM DMTF Server Architecture

Authentication Server

WBEM Server

CIMOM (Pegasus)Provider Protocol Adapters: CMPI, Java/C++

Client Protocol Adapters

CIM-XML

Indication Handlers

CIM-XML

WBEM Mgmt Clients WBEM Event Listeners

Repository

ManagedElements

ProvidersProvidersProviders


SMI-S: Services for Management

CIM-XML &WS-Management

Storage Management Applications SMI-S Clients

Disk Arrays FC HBAsTape Libraries

FC Switches

Management ServicesObject Oriented, Platform Independent, Automated Discovery,

Security, Configuration, Provisioning Operations, etc.

Individual Device Properties

EDUCATION2005, 2006, 2007 Storage Networking Industry Association. All Rights Reserved.

SMI-S Providers


WBEM DiscoveryService Location ProtocolService Location Protocol (SLP) is a protocol for service discovery.

It allows clients to locate servers and other services on the network.

User Agent(UA)

User Agent(UA)

User Agent(UA)

Service Agent(SA)

Service Agent(SA)

Directory Agent(DA)

CIM-Clients

CIM-Servers


Summary of WBEM BenefitsClient developers benefits:

– Common definition of data– Standard mechanism to access management data– Degree of isolation from hardware and software changes– Reduced cost of developing multivendor, multiplatform, secure

solutions

Provider developers benefits:– Common definition of data– Potential for low-cost, tight integration with a wealth of applications

and systems– Reduced cost of developing multivendor, multiplatform, secure

solutions

WBEM simplifies adoption by:– Advocating evolution not revolution– Relying on existing, pervasive standards and technologies


Modeling LUN Provisioning in an Array

Primordial Storage Pool

Raw disks are aggregated into a primordial pool of storage from which concrete pools can be allocated.

Concrete Storage Pool

Volumes are created from concrete pools. For each, a setting is created that specifies performance and availability (QoS).

Volumes

LUN Masking and Mapping of a volume is applied to one or more host HBA Fibre Channel or iSCSI ports.

One or more concrete pools is created from the primordial pool from which volumes can be created.


Storage Pools


testsmiprovider (Client Test Program)C:\Program Files\EMC\SYMCLI\storbin>testsmiproviderHost [localhost]:Connection Type (ssl,no_ssl) [no_ssl]:Port [5988]:Username []: providerPassword []: ############Connecting to localhost:5988Using user account 'provider' with password ‘xxxxxxxxx'########################################################################## #### EMC SMI Provider Tester #### This program is unsupported and intended for use by EMC Support #### personnel only. At any time and without warning this program may #### be revised without regard to backwards compatibility or be #### removed entirely from the EMC SMI-S Provider kit. ##########################################################################cn - Connect dc - Disconnectei - EnumerateInstances ein - EnumerateInstanceNames a - Associators an - AssociatorNamesr - References rn - ReferenceNames

gi - GetInstance gc - GetClass dv - Display version info ns - NameSpace q - Quit h - Help(other commands exist but omitted for readability and not need for this presentation)########################################################################repeat count: 1(localhost:5988) ?


EnumerateInstanceNames

(localhost:5988) ? einClass: emc_storagesystem++++ Testing EnumerationInstanceNames: emc_storagesystem ++++Enumerate 1 instance names; repeat count 1; Instance 0:Symm_StorageSystem.CreationClassName="Symm_StorageSystem",Name="SYMMETRIX+000000005231"


GetInstance

(localhost:5988) ? giObjectPath: Symm_StorageSystem.CreationClassName="Symm_StorageSystem",Name="SYMMETRIX+000000005231"LocalOnly [false]:IncludeQualifiers [false]:Property to include ('-' for all)? [-]: elementnameProperty to include ('-' for all)? [-]: operationalstatusProperty to include ('-' for all)? [-]: statusdescriptionsProperty to include ('-' for all)? [-]:repeat count 1 in 0 seconds

<INSTANCE CLASSNAME="Symm_StorageSystem" ><PROPERTY NAME="ElementName" TYPE="string"><VALUE>000000005231</VALUE></PROPERTY><PROPERTY.ARRAY NAME="StatusDescriptions" TYPE="string" ARRAYSIZE="2"><VALUE.ARRAY><VALUE>OK</VALUE><VALUE>ONLINE</VALUE></VALUE.ARRAY></PROPERTY.ARRAY><PROPERTY.ARRAY NAME="OperationalStatus" TYPE="uint16" ARRAYSIZE="2"><VALUE.ARRAY><VALUE>2</VALUE><VALUE>32769</VALUE></VALUE.ARRAY></PROPERTY.ARRAY></INSTANCE>


Storage Pools


AssociatorNames of TopLevel StorageSystem

(localhost:5988) ? anObjectPath: Symm_StorageSystem.CreationClassName="Symm_StorageSystem",Name="SYMMETRIX+000000005231"Assoc Class []: cim_hostedstoragepoolResult Class []: cim_storagepoolRole []:Result Role []:++++ Testing AssociatorNames: Symm_StorageSystem.CreationClassName="Symm_StorageSystem",Name="SYMMETRIX+000000005231" ++++AssociatorNames: 5 associators; repeat count 1; in 0.015625 secondsAssociator Name 0://api155/root/emc:Symm_DeviceStoragePool.InstanceID="SYMMETRIX+000000005231+C+0000"Associator Name 1://api155/root/emc:Symm_PrimordialStoragePool.InstanceID="SYMMETRIX+000000005231+P+Primordial"Associator Name 2://api155/root/emc:Symm_SpareStoragePool.InstanceID="SYMMETRIX+000000005231+E+AVAILABLE_FOR_FAILOVER"Associator Name 3://api155/root/emc:Symm_SpareStoragePool.InstanceID="SYMMETRIX+000000005231+E+FAILED-REPLACED_BY_SPARE"Associator Name 4://api155/root/emc:Symm_SpareStoragePool.InstanceID="SYMMETRIX+000000005231+E+FAILED-NOT_REPLACED_BY_SPARE"

In 0.046875 Seconds


EnuermateInstanceNames of CIM_StoragePool(localhost:5988) ? einClass: cim_storagepool++++ Testing EnumerationInstanceNames: cim_storagepool ++++Enumerate 5 instance names; repeat count 1; in 0.093750 secondsInstance 0:Symm_DeviceStoragePool.InstanceID="SYMMETRIX+000000005231+C+0000"Instance 1:Symm_PrimordialStoragePool.InstanceID="SYMMETRIX+000000005231+P+Primordial"Instance 2:Symm_SpareStoragePool.InstanceID="SYMMETRIX+000000005231+E+AVAILABLE_FOR_FAILOVER"Instance 3:Symm_SpareStoragePool.InstanceID="SYMMETRIX+000000005231+E+FAILED-REPLACED_BY_SPARE"Instance 4:Symm_SpareStoragePool.InstanceID="SYMMETRIX+000000005231+E+FAILED-NOT_REPLACED_BY_SPARE"


Storage Pools


EnuermateInstanceNames of CIM_StorageVolume

(localhost:5988) ? einClass: cim_storagevolume++++ Testing EnumerationInstanceNames: cim_storagevolume ++++Enumerate 65 instance names; repeat count 1; in 0.031250 secondsInstance 0:Symm_StorageVolume.CreationClassName="Symm_StorageVolume",DeviceID="0000",SystemCreationClassName="Symm_StorageSystem",SystemName="SYMMETRIX+000000005231"Instance 1:Symm_StorageVolume.CreationClassName="Symm_StorageVolume",DeviceID="0001",SystemCreationClassName="Symm_StorageSystem",SystemName="SYMMETRIX+000000005231……….Instance 62:Symm_StorageVolume.CreationClassName="Symm_StorageVolume",DeviceID="0045",SystemCreationClassName="Symm_StorageSystem",SystemName="SYMMETRIX+000000005231"Instance 63:Symm_StorageVolume.CreationClassName="Symm_StorageVolume",DeviceID="0046",SystemCreationClassName="Symm_StorageSystem",SystemName="SYMMETRIX+000000005231"Instance 64:Symm_StorageVolume.CreationClassName="Symm_StorageVolume",DeviceID="0047",SystemCreationClassName="Symm_StorageSystem",SystemName="SYMMETRIX+000000005231"


Associatornames of CIM_StoragePool/CIM_StorageVolume

(localhost:5988) ? anObjectPath: Symm_DeviceStoragePool.InstanceID="SYMMETRIX+000000005231+C+0000"Assoc Class []: cim_allocatedfromstoragepoolResult Class []: cim_storagevolumeRole []:Result Role []:++++ Testing AssociatorNames: Symm_DeviceStoragePool.InstanceID="SYMMETRIX+000000005231+C+0000" ++++AssociatorNames: 65 associators; repeat count 1; in 0.031250 secondsAssociator Name 0://api155/root/emc:Symm_StorageVolume.CreationClassName="Symm_StorageVolume",DeviceID="0000",SystemCreationClassName="Symm_StorageSystem",SystemName="SYMMETRIX+000000005231"Associator Name 1://api155/root/emc:Symm_StorageVolume.CreationClassName="Symm_StorageVolume",DeviceID="0001",SystemCreationClassName="Symm_StorageSystem",SystemName="SYMMETRIX+000000005231"

-------

Associator Name 63://api155/root/emc:Symm_StorageVolume.CreationClassName="Symm_StorageVolume",DeviceID="0046",SystemCreationClassName="Symm_StorageSystem",SystemName="SYMMETRIX+000000005231"Associator Name 64://api155/root/emc:Symm_StorageVolume.CreationClassName="Symm_StorageVolume",DeviceID="0047",SystemCreationClassName="Symm_StorageSystem",SystemName="SYMMETRIX+000000005231"


Associators of CIM_StoragePool/CIM_StorageVolume

(localhost:5988) ? aObjectPath: Symm_DeviceStoragePool.InstanceID="SYMMETRIX+000000005231+C+0000"Assoc Class []: cim_allocatedfromstoragepoolResult Class []: cim_storagevolumeIncludeQualifiers [false]:IncludeClassOrigin [false]:Property to include ('-' for all)? [-]: deviceidProperty to include ('-' for all)? [-]: blocksizeProperty to include ('-' for all)? [-]: numberofblocksProperty to include ('-' for all)? [-]:++++ Testing Associators: Symm_DeviceStoragePool.InstanceID="SYMMETRIX+000000005231+C+0000" ++++Associators: 65 associators; repeat count 1; in 0.109375 secondsAssociator 0:Path = //api155/root/emc:Symm_StorageVolume.CreationClassName="Symm_StorageVolume",DeviceID="0000",SystemCreationClassName="Symm_StorageSystem",SystemName="SYMMETRIX+000000005231"DeviceID = 0000NumberOfBlocks = 2112000BlockSize = 512-----------------------------Associator 64:Path = //api155/root/emc:Symm_StorageVolume.CreationClassName="Symm_StorageVolume",DeviceID="0047",SystemCreationClassName="Symm_StorageSystem",SystemName="SYMMETRIX+000000005231"DeviceID = 0047NumberOfBlocks = 20972160BlockSize = 512


Storage Pools


Associators of CIM_StorageVolume/CIM_StorageSetting

(localhost:5988) ? aObjectPath: //api155/root/emc:Symm_StorageVolume.CreationClassName="Symm_StorageVolume",DeviceID="0000",SystemCreationClassName="Symm_StorageSystem",SystemName="SYMMETRIX+000000005231"Assoc Class []: cim_elementsettingdataResult Class []: cim_storagesettingncludeQualifiers [false]:IncludeClassOrigin [false]:Property to include ('-' for all)? [-]: extentstripelengthProperty to include ('-' for all)? [-]: packageredundancygoalProperty to include ('-' for all)? [-]:++++ Testing Associators: //api155/root/emc:Symm_StorageVolume.CreationClassName="Symm_StorageVolume",DeviceID="0000",SystemCreationClassName="Symm_StorageSystem",SystemName="SYMMETRIX+000000005231" ++++Associators: 1 associators; repeat count 1; in 0.000000 secondsAssociator 0:Path = //api155/root/emc:Symm_StorageVolumeSetting.InstanceID="SYMMETRIX+000000005231+0000"ExtentStripeLength = 1PackageRedundancyGoal = 0

---------


Storage Pools


SMI-S V1.2 Profile BlockStorageViewsVolumeView

– CIM_StoragePool data (SP, volume was allocated from)– CIM_StorageVolume (SV)– CIM_StorageSetting (SS, redundancy characteristics, raid level)– Physical Package (PP, vendor information for the disk)– AllocatedFromStoragePool (AFSP)

DiskDriveView– CIM_StorageExtent (SE, primordial extent for the disk)– CIM_SoftwareIdentity (SI, Disk Firmware)– CIM_DiskDrive (DD)– Physical Package (PP, vendor information for the disk)


SMI-S V1.2 Profile BlockStorageViews (Cont)ExposedView

– CIM_SCSIProtocolController (SPC)– CIM_ProtocolEndpoint (PEP)– CIM_ProtocolControllerForUnit (PCFU)– AssociationInstance, shortcut for masking/mapping view– relationship between volume/front end protocol endpoint

(port)/storagehardwareid

MaskingMappingView– CIM_SCSIProtocolController (SPC)– CIM_ProtocolEndpoint (PEP)– CIM_SCSIProtocolEndpoint (SPEP)– CIM_StorageHardwareID (SHID)– CIM_AuthorizedPrivilege(AP)– AssociationInstance, shortcut for masking/mapping view


Profile BlockStorageViews (VolumeView)

(localhost:5988) ? einClass: snia_volumeview++++ Testing EnumerationInstanceNames: snia_volumeview ++++Enumerate 65 instance names; repeat count 1; in 0.046875 secondsInstance 0:Symm_VolumeView.SPInstanceID="SYMMETRIX+000000005231+C+0000",SVCreationClassName="Symm_StorageVolume",SVDeviceID="0000",SVSystemCreationClassName="Symm_StorageSystem",SVSystemName="SYMMETRIX+000000005231"Instance 1:Symm_VolumeView.SPInstanceID="SYMMETRIX+000000005231+C+0000",SVCreationClassName="Symm_StorageVolume",SVDeviceID="0001",SVSystemCreationClassName="Symm_StorageSystem",SVSystemName="SYMMETRIX+000000005231"Instance 2:

-----------------------

Instance 64:Symm_VolumeView.SPInstanceID="SYMMETRIX+000000005231+C+0000",SVCreationClassName="Symm_StorageVolume",SVDeviceID="0047",SVSystemCreationClassName="Symm_StorageSystem",SVSystemName="SYMMETRIX+000000005231"


Profile BlockStorageViews (VolumeView)(localhost:5988) ? anObjectPath:Symm_StorageSystem.CreationClassName="Symm_StorageSystem",Name="SYMMETRIX+000000005231"Assoc Class []: snia_systemdeviceviewResult Class []: snia_volumeview++++ Testing AssociatorNames: Symm_StorageSystem.CreationClassName="Symm_StorageSystem",Name="SYMMETRIX+000000005231" ++++AssociatorNames: 65 associators; repeat count 1; in 0.031250 secondsAssociator Name 0://api155/root/emc:Symm_VolumeView.SPInstanceID="SYMMETRIX+000000005231+C+0000",SVCreationClassName="Symm_StorageVolume",SVDeviceID="0000",SVSystemCreationClassName="Symm_StorageSystem",SVSystemName="SYMMETRIX+000000005231"Associator Name 1://api155/root/emc:Symm_VolumeView.SPInstanceID="SYMMETRIX+000000005231+C+0000",SVCreationClassName="Symm_StorageVolume",SVDeviceID="0001",SVSystemCreationClassName="Symm_StorageSystem",SVSystemName="SYMMETRIX+000000005231“--------------------Associator Name 64://api155/root/emc:Symm_VolumeView.SPInstanceID="SYMMETRIX+000000005231+C+0000",SVCreationClassName="Symm_StorageVolume",SVDeviceID="0047",SVSystemCreationClassName="Symm_StorageSystem",SVSystemName="SYMMETRIX+000000005231"


Profile BlockStorageViews (VolumeView)(localhost:5988) ? aObjectPath:Symm_StorageVolume.CreationClassName="Symm_StorageVolume",DeviceID="0044",SystemCreationClassName="Symm_StorageSystem",SystemName="SYMMETRIX+000000005231"Assoc Class []: SNIA_BaseInstanceResult Class []: SNIA_VolumeView

-----------------------Not all properties shown below-----------------------SPInstanceID = SYMMETRIX+000000005231+C+0000SVDeviceID = 0044SVCreationClassName = Symm_StorageVolumeSVSystemName = SYMMETRIX+000000005231SVSystemCreationClassName = Symm_StorageSystemSSUserDataStripeDepthMax = 0SSUserDataStripeDepthMin = 0SSUserDataStripeDepth = 0SSParityLayout = 0SPPoolID = 0000AFSPSpaceConsumed = 10737745920SSChangeableType = 0SSPackageRedundancyGoal = 1


CLARiiON / Symmetrix V3.2 Provider – Q2 2007Specifications

SMI-S V1.2 CIM Schema V2.14 OpenPegasus V2.6 Additional EMC-specific extensionsBackwards compatible with SMI-S V1.1CTP certification pending

SMI V1.1 Profiles/SubprofilesPackages:

– Health Fault Management– Block Services– Physical– Software

Profiles:– Array– Server

Array Subprofiles:– Job Control, Disk Drive Lite, Disk Drive– FC Initiator Ports, Multiple Computer

System– FC, iSCSI and SPI Target Ports – Access Points, Location, Software– Masking and Mapping– Block Server Performance– Extent Composition– Copy Services (local replication)

SMI V1.2 Profiles/SubprofilesArray Profiles:

– Volume Composition– Storage Server Asymmetry– Block Storage Views

Server Profiles:– Profile Registration


Symmetrix/CLARiiON Provider Install Prereqs– Provider Install guide spells out prerequisites (highlights below)– 32-bit systems only supported at this point– http://www.snia.org/ctp/conformingproviders/emc lists CLARiiON and

Symmetrix storage arrays supported by the provider Linux, (Red Hat, SLES 9)Solaris 2.8 or later Windows 2000, 2003On Windows 2000, WindowsInstaller-KB893803-v2-x86.exe must be installed prior to installing kit

– Symmetrix At least one gatekeeper visible to the host

– CLARiiONOne CLARiiON LUN visible to host or host can be discovered out of band syminq –v –clariion (shows IP addresses of the CLARiiON, if locally attached)symcfg auth add for each CLARiiON SP to be discovered (in-band only) CLARiiON must be running release 19 or laterCLARiiON CLIs not needed on provider host

http://www.snia.org/ctp/conformingproviders/emc


Symmetrix/CLARiiON Provider Install Prereqs (continued)Native installer kits for each of the platforms

– Linux – rpm kits– Solaris – package add– Windows – Microsoft installer

Pointer to partner alliance page for access to provider– http://www.emc.com/partnersalliances/developers/api_cli.jsp

http://www.emc.com/partnersalliances/developers/api_cli.jsp


ReferencesSNIA

– http://www.snia.org– http://www.snia.org/ctp (CTP Certified products) – http://www.snia.org/ctp/conformingproviders/emc (EMC Certified Providers)

– http://www.snia.org/ctp/smi_conform/smi_client_emc (EMC Certified Clients)

– http://www.snia.org/smi/tech_activities/smilab (SMI-LAB Overview)– http://www.snia.org/members/smis/ (SMI-S Central)

DMTF CIM Schema– http://www.dmtf.org/standards/cim

DMTF WBEM Standards– http://www.dmtf.org/standards/wbem

OpenPegasus– http://www.openpegasus.org/

http://www.snia.org/

http://www.snia.org/ctp

http://www.snia.org/ctp/conformingproviders/emc

http://www.snia.org/ctp/smi_conform/smi_client_emc

http://www.snia.org/smi/tech_activities/smilab

http://www.snia.org/members/smis/

http://www.dmtf.org/standards/cim

http://www.dmtf.org/standards/wbem

http://www.openpegasus.org/


SDC General Sessions – Keynote with Mark Lewis, Chief Development Officer, EMC

Wed May 23, 8:30-9:45 AM– ‘Meet the Experts’ Tues May 22, 4:15-5:45 PM– ‘Developer Challenge’ Wed May 23, 5:00-6:15 PM

Join the EMC Developer Network (EDN) to receive a cool gift and be automatically entered in a Developer Challenge drawing. Register for the EDN either in the SDC Lounge or the EDN booth in the Solutions Pavilion.

implementation of storage network industry association...

Documents