SNIA CIM Prototype and Demonstration

1. SNIA CIM Prototype and Demonstration John Tyrrell Mike Dutch October 21, 1999

2. Agenda • Storage Area Networks (SAN) • SAN Inhibitors • CIM Prototype • Demonstration • Conclusions

3. Why Do We have SAN Fever?

4. SAN As A Solution • Consolidation of storage • Data sharing • Improved backup/recovery • Disaster tolerance • Higher availability • Improved performance • Selection of “best in class” products • Easier migration to new technologies • Centralized, policy-based management

5. SAN Inhibitors ESRM SAN Highway

6. Total Cost of Storage $0.35 per MB, one time Hardware: $3.50 per MB, per year Management:

7. Enterprise StorageResource Management • Asset Management • Capacity Management • Configuration Management • Performance Management • Availability Management • Policy Management • etc.

8. Answer: It’s Acme-centric! DO single vendor shops exist? What’s wrong with this picture? Acme Storage SAN Portfolio

9. Answer: All fibre components don’t interoperate today! What’s wrong with this picture?

10. Answer: Can’t manage storage shared between different OS systems! What’s wrong with this picture?

11. Answer: No people to micro-manage storage by vendor! What’s wrong with this picture?

12. Answer: ESRM S/W vendors can’t keep up with unique vendor H/W What’s wrong with this picture?

14. Common Information Model (CIM) Core Model Application to all domains of management Common Models Applicable to a specific management domain but independent of any particular technology Extension Schema Technology-specific extensions of the Common Models

15. DMTF and WBEM

16. and XML • Standard Generalized Markup Language (SGML) is the “mother tongue” of all markup specification languages (ISO 8879) • HyperText Markup Language (HTML) is an application of SGML (RFC 1866) used on the WWW to describe how data is rendered • Extensible Markup Language (XML) is a simplified SGML used to describe what the data is… enabling application data exchange • Document Type Definition (DTD) files define XML vocabularies • Extensible Style Language (XSL) adds transformation rules • The World Wide Web Consortium (W3C) owns the XML recommendation but not the DTD vocabularies • DMTF owns the CIM XML Mapping and XML DTD The Acronym Factory

17. WBEM Implementation Vendor Specific Applications - ESRM - HTTP Access Data Description CIM Platform Specific <xmlCIM/>Transport Encoding Platform Neutral CIM Object Manager Object Providers Storage

18. Why Do a Prototype? • Verify CIM Object Manager plumbing(Sun and Microsoft) • Validate vendor CIM field instantiation • Understand CIM performance implications • Help size CIM-based products • Help develop subsequent white papers • Show good citizenship to our customers

19. Goals of the CIM Prototype • Build a representative mini-ESRM function • Encourage other vendor’s participation • Allow new vendors to join dynamically • Demonstrate viability of CIM model • Exercise existing CIM OM implementations • Test new CIM OM HTTP/XML interface • Build a SNIA “reference model”

20. Demonstrationhttp://208.200.29.2

21. Statistics Disk System Vendor Location Service Processor Capacity Planning Cache Host View I/O Disk Storage

22. MaintainDirectory InstalledCapacity PhysicalInventory GrowthCapacity Demonstrate Common Resource Management 129.63.16.188 extranet.stortek.com/snia-demo 206.124.19.2 know1.emcweb.com 208.200.29.3 192.208.35.85 208.208.57.154

23. Mini-ESRM Contributors • Functional Design • Prototype Architecture • Instantiation Details • Java CIMOM • Directory Add/Delete • Prototype Architecture • Java AQE • Functional Design • Prototype Architecture • Project Management • ESRM Server • WMI CIMOM • Style Sheets/XML • WMI AQE

24. CIM Prototype Providers

25. Directory Add/Delete Web Browser Web Browser • Physical Inventory • Physical Capacity Resource Manager HTML Perl Script Directory HTTPServer xxxxx xxxxx xxxxx xxxxx Web Pages Style Sheets 1 3 • Browser HTML form updates directory using Perl script • Browser script “discovers” WBEM Servers in directory, initiates statistics gathering, and requests inventory data • Statistics provider navigates CIM Schema to calculate summary statistics • Browser script aggregates summary statistics from discovered WBEM Servers WBEM Server XML HTTPServer CIM Object Manager Statistics Provider Disk Provider 2

26. Root/Hitachi AQE Updates Clone.exe Root/Hitachi/clone DirectAQE Modification Events Cloned Objects • Clone.exe uses • Event registration to detect changes • Updates to maintain AQE • Client is not aware of the difference

27. Maintain directory Click to download

28. Add <?xml version="1.0" ?>- <DIRECTORY> <ENTRYCIMOM="http://208.208.57.154/root/disk/hitachi" VENDOR="Hitachi Data Systems" LOCATION="Santa Clara ,California" LOGO_URL="http://208.200.29.2/cimdemo/snia/logos/hitachi.gif" WEBPAGE="http://www.hds.com" EMAIL="mike.dutch@hds.com" /> </DIRECTORY> Remove

29. Click to show inventory

30. Click to show installed capacity

31. Click to show growth capacity

32. Return to home

33. The Good News • Suicidal mission…. But we did it! • First Internet WBEM Implementation • Multi-Vendor, Cooperative, Proof of Concept • Validated two vendor CIM Object Managers • Extensible CIM Profile for Disk System • Tested WBEM plumbing • HTTP/XML, CIMOM, CIM 2.2 • SNIA Helps!

34. WBEM Higher Availability Performance Scalability Discovery Namespace Use Education And Support Model Complexity Standards/Consortium Collaboration Standardization Complete CIM Profile for Disk Systems Develop CIM Profiles for other Devices Common Disk Methods Drive Profiles to DMTF Adoption Further Work Required

35. Project Contacts

36. Thank You!