Skykomish A MOF-Based CIM-Development Environment. Michael T. Peterson Mazama Sofware LLC

Transcription

1 Skykomish A MOF-Based CIM-Development Environment Michael T. Peterson Mazama Sofware LLC

2 What is Skykomish? Skykomish is a set of tools designed for developers of management (e.g., system and network administration) applications. Excellent Management Applications are charactered as having: Common object model and data definitions E.g., Status: Red, Green, OK, 1, 0, Active, etc., CIM is a good example of a common object model designed for management operations of Computer-oriented stuff. Transparent, Interoperable components Interface Definition Languages permit developers to write applications that manage objects they ve never seen before. MOF is an especially rich and extensible IDL. Static and Dynamic Semantics Operations are determined statically (via pre-compiled MOF files) or dynamically by run-time compilation of policy specifications. DMTF 2002 Developers' Conference June 10-13, 2002 Page 2

3 Usage Model Skykomish completely hides the underlying framework (e.g., CIM, SNMP). For example: Device Vendor Develop MOF files for the object to managed (e.g., a device). Compile the MOF into Java/C++ provider source code stubs. Complete the stubs, test, debug, etc., When complete, publish/release the MOF Management Application Vendor Get MOF from device vendor Compile MOF into client objects. Write management application that uses the client objects. DMTF 2002 Developers' Conference June 10-13, 2002 Page 3

4 Components 1. Next Generation MOF Compiler, mzc Standalone, i.e., independent of CIM Server (aka cimom) Supports both SNIA and WBEMServices environments.\ Very strict Multipass (Syntax, Semantics, high-order rules) Code generators for Java, C++, and CORBA IDL Generates both Provider and Client source code CORBA IDL going away. Will generate CORBA clients and skeletons directly. 2. The Clerk Daemon The clerk Daemon (clerkd) resides on every host where a client application is installed. Location Broker / rpcd functionality Management Adapters (CIM, SNMP) Protocol Adapters (security, transactions, naming & discovery, events) DMTF 2002 Developers' Conference June 10-13, 2002 Page 4

5 3. Advanced Development Components (Cont d) Mazama will add cimxml over IIOP E.g., Object Name IIOP://<Stringified IOR>/root/cimv2/ Where IOR is an Interoperable Object Reference in string form Additional MOF semantics and/or Qualifiers Exception and Raises qualifiers Void return type DMTF 2002 Developers' Conference June 10-13, 2002 Page 5

6 The Compiler - MZC MOF-To-Java, MOF-To-C++, and MOF-To-IDL (CORBA) mappings. Full support for all [relevant] standard Qualifiers, including Values,ValueMap, MinValue, MaxValue, Abstract, Static, In, Out, etc. Description qualifier contents translated to javadoc format Two new [experimental] Qualifiers Exceptions (read-only properties) Qualifier Exception : boolean = false, Scope(class, association, indication), Flavor(DisableOverride, Restricted); Raises Qualifier Raises : string[], Scope(method), Flavor(Translatable); DMTF 2002 Developers' Conference June 10-13, 2002 Page 6

7 Exception Example MOF [Exception] Class MZC_CareerOverException : MZC_BaseException { [Override( MZC_BaseException.exceptionMsg )] string exceptionmsg = UhOh, Reciepts nowhere to be found! ; [key, Override( MZC_BaseException.exceptionValue ) ] uint32 exceptionvalue = 0x1BadBabe; }; class MZC_Foo : MZC_Base { [Raises( MZC_Exception )] uint16 takebusinesstrip( [in] uint32 val ); }; Java Uint16 Status takebusinesstrip( Uint32 val ) throws MZC_CareerOverException; DMTF 2002 Developers' Conference June 10-13, 2002 Page 7

8 The Mazama Object Factories Used for instantiation and removal of classes and instances. Programmers access the factories using static methods compiled into each class (by mzc). Makes use of the MOF model path, e.g. given the following declaration: class MZC_Person : MZC_Base { [key] string Name; [key] string CreationClassName; }; A model path might be MZC_Person.Name=\ J.Smith\,SSAN=\ \ DMTF 2002 Developers' Conference June 10-13, 2002 Page 8

9 Obtaining Instances Retrieve pre-existing instances using enumeration MZC_Person p = null; String cp = MZC_Person.getClassPath(); // static method Enumeration e = MZCInstanceFactory( cp ); while( e.hasmoreelements() == true ) { String modelpath = (String) e.nextelement(); p = MZC_Person.getInstance( modelpath) ; // static method } DMTF 2002 Developers' Conference June 10-13, 2002 Page 9

10 Obtaining Instances Create a new instance String modelpath = new String( MZC_Person.Name=\ J.Smith\,SSAN=\ \ ); try { MZC_Person p = new MZC_Person( modelpath ); } catch( MZCException ex ) { com.mazama.utils.trace.print( ex.getmessage() ); System.exit( MZCException.getValue() ); } DMTF 2002 Developers' Conference June 10-13, 2002 Page 10

11 Compiler Status Compiler Code Generation Java client and provider source generation is complete CIM Support SNIA Very Strict. Existing MOF files from DMTF WEB contain numerous bugs that prevent compilation. Steve Jerman, HP, has a set of V 2.7 MOF files that have been fixed and can be compiled without error by mzc. DMTF 2002 Developers' Conference June 10-13, 2002 Page 11

12 Clerkd Status Adapter support Management Adaptors CIM Protocol Adapters None Naming/Discovery partially complete, Security and Transactions are stubbed out. Not required to run compiler or software built from compiler generated sources. DMTF 2002 Developers' Conference June 10-13, 2002 Page 12

13 Release Schedule Beta I Release 30 June, 2002 Compiler only, no Clerk Daemon Java language binding Client-side and provider-side source code SNIA CIM Server only Beta II Release 30 September, 2002 Compiler only, no Clerk Daemon Support for WBEM Services CIM Server Beta III Release 31 January, 2003 Compiler (Same as Beta II) First Release of Clerk Daemon Security Adapter Discovery / Naming Services Adapter Instance Caching DMTF 2002 Developers' Conference June 10-13, 2002 Page 13

14 Schedule (Cont d) Beta IV Release April 30, 2003 Compiler (No change) Clerk Daemon Transaction Support Including distributed locking Nested Transactions Events Both Persistent and Transient Final Beta Release August 31, 2003 Functionally Complete DMTF 2002 Developers' Conference June 10-13, 2002 Page 14

15 Version 2 Version 2 will include a rewrite of most of the compiler s internals. The Clerk Daemon will be complete with the addition of dynamic policies. V2 Compiler C++ language binding for both client and provider developers Policy Compilation Better speed More informative error messaging Internationalization V2 Clerk Daemon Performance Enhancements (incorporate P2P) Policy Adapter and dynamic policies DMTF 2002 Developers' Conference June 10-13, 2002 Page 15