SRI Demo

Ulrich KurzIBM LTC Böblingen

(07//11/2002)

SBLIM Reference Implementation (SRI)

What is SRI? SRI...

page 2 of 31

What Is SRI? SRI...

...stands for "SBLIM Reference Implementation",

page 3 of 31

What Is SRI? SRI...

...stands for "SBLIM Reference Implementation",

...originally was a tool to test our own CIM/CIMOM development activities (the "providers"),

page 4 of 31

What Is SRI? SRI...

...stands for "SBLIM Reference Implementation",

...originally was a tool to test our own CIM/CIMOM development activities (our "providers"),

...is now a client application and framework for CIM based Linux systems management,

page 5 of 31

page 1 of

"Framework" means: Each CIM class that is contained in the remote CIMOM (and that contains "providers" to supply instance data) can easily be displayed via mere modification of SRI's setup-xml.The location in the SRI console tree (with "computer system management objects") and the way how CIM instances are displayed (as list, as table) and the contents of the context-menu (with actions to perform on a selected CIM instance) are set via sri.xml setup file. And: refinements of SRI's display classes can be achieved via sub-classing.And: SRI is extendable. It allows to invoke any JAVA class (SRI and non-SRI) via console (the class nameonly must be specified in sri.xml's <displayclass> tag.And: SRI has various xml-samples to setup the console's node hierarchy.Example: Instances of CIM class "Linux_LVMVolumeGroup" are displayed as list (responsible SRI display class:"DList". Contextmenu "LVM_Task2b" specified for node and used instead of default context menu)

page 6 of 31

What Is SRI? SRI...

...stands for "SBLIM Reference Implementation",

...originally was a tool to test our own CIM/CIMOM development activities (our "providers"),

...is now a client application and framework for CIM based Linux systems management,

...runs on Linux (and Windows),

page 7 of 31

What Is SRI? SRI...

...stands for "SBLIM Reference Implementation",

...originally was a tool to test our own CIM/CIMOM development activities (our "providers"),

...is now a client application and framework for Linux systems management,

...runs on Linux (and Windows),

...is written in JAVA Swing,

page 8 of 31

What Is SRI? SRI...

...stands for "SBLIM Reference Implementation",

...originally was a tool to test our own CIM/CIMOM development activities (our "providers"),

...is now a client application and framework for Linux systems management,

...runs on Linux (and Windows),

...is written in JAVA Swing,

...is Open Source and downloadable by everyone from http://www-124.ibm.com/developerworks/projects/sblim

page 9 of 31

How does the SRI console look? The SRI console has 2 parts:

the left part includes an easily configuable hierarchy of objects making up a computer ("nodes"), the right part allows to manage computer-objects available in a CIMOM ("cimnodes").

page 10 of 31

(Parts of) the xml making up (previous) console

3 entries are necessary to operate on a CIM object via the SRI console: <cimnode> defines the text (and implicitely the position) of the CIM object, <displayclass> defines how the data should be presented (SRI provides a set of display classes to select from), <cimclass> specifies what CIM class should be displayed. (Other entries, like <contextmenu> to define what operations should be possible on a selected CIM object, aren't mandatory).

page 11 of 31

Where stands SRI? And where is CIM and CIMOM?

page 12 of 31

System Management via CIM/CIMOM: the Providers

Software (RPM-packages), Data Storage:

Local File Systems,NFS File Systems, Logical Disks, Storage Volumes, LVM management (LVM Physical Volumes, LVM Volume Groups, LVM Logical Volumes),Directories,

Command Processing,Processes (and Services), Kernel parameters.

The system-management capabilities of SRI depend on the number of objects, providers and methods in the remote CIMOM. The SBLIM-team has written providers to display and/or manage

page 13 of 31

The "demo":

page 14 of 31

Step 1: Start SRI on Linux or Windows (the CIMOMs on remote machines must be running)...

page 15 of 31

Step 1: ...and the SRI console appears:

page 16 of 31

page 17 of 31

Step 2: Navigate through the object hierarchy to list all RPM packages on the remote machine...

page 18 of 31

Step 2: ...and a table which shows selected object attributes (index=0,1,14,15) in specified order(0,3,1,2) and specified headings ("Name...) is displayed:

Background: SRI has 3 display classes for lists (DList, DListUnordDup, DListOrdNodup) and 4 display classes for tables (DTable, DTableAll, DTableKey and DTableSel, which was invoked here).Each of this classes can easily be invoked via SRI's setup XML (name: "sri.xml") to display CIM instances in a different form.

page 19 of 31

Step 3: Navigate through the object hierarchy to list all services on the remote Red Hat machine (only RedHat supports the concept of "services")...

Step 3: ...and a list of services appears. Services can be started, stopped, associated processes can be listed, and details of a service can be displayed:

page 20 of 31

page 21 of 31

SRI... ...also supports LVM ("Logical Volume Management"):

page 21 of 30

SRI... ...allows to display kernel parameters and its values:

page 22 of 31

SRI also has a command console (e.g. to stop the remote machine)

page 23 of 31

Last not least: each of the display classes can be called individually from a console to test CIM providers:

page 24 of 31

What is SRI? SRI is not...

page 25 of 31

What Is SRI? SRI is not...

...a systems management application, but...

page 26 of 31

What Is SRI? SRI is not......a systems management application, but it can be used for systems management purposes by anybody:

page 27 of 30

More Details...

page 28 of 31

The 3 parts that manage SRI: Console (Invocation) - Display Class (Output) - XML File (Setup). Example 1: CIM Instances displayed as a list. Upper left screenshot shows the invocation point in the console ("Task2b..."), lower right screenshot the part in the xml-file that is responsible for console and display class invocation (invoked: display class "DList" on CIM class "Linux_LVMVolumeGroup" with context menu "LVM_Task2b"), lower left screenshots shows output of the invoked generic display class (with context menu) page 29 of 31

The 3 parts that...Example 2: CIM Instances displayed as a table (selected attributes only). Upper left screenshot shows the invocation point in the console ("Task2c..."), lower left screenshot shows the part in the xml-file that is responsible for console and display class invocation (invoked: display class "DTableSel" with display parameters - first parm selects the displayed attributes, second parm selects the display order, third parm defines the column headings - ; related CIM class is "Linux_LVMVolumeGroup", responsible context menu is "LVM_Task2c"), upper right screenshots shows output of the invoked generic display class (with context menu), lower right screenshots shows Volume Group definition panel if "Create New" has been selected in context menu, page 30 of 31

3.1 Service Mgt3

Business Mgt

2Operations Mgt

1Administrative Mgt

3.2 Asset Mgt

3.3. Accounting Mgt

3.4 Policy Mgt

3.5 User Mgt

1.1 Configuration Mgt

1.2 Change Mgt

1.3 Security Mgt

1.4 Software Admin

2.1 Operations Mgt

2.2 Problem Mgt

2.3 Performance Mgt

1.1.1 InventoryMgt

2.2.2 Bypass & Recovery

2.2.1 Determination

2.2.3 Assignment

1.1.2 Topology Mgt

1.3.1 LicenseMgt

2.1.1 Event Mgt

2.1.4 Data Mgt

2.1.3 Operations Mgt

2.1.2 Workload Mgt

2.3.1Control & Monitor

2.3.2 Execute & Measure

The CIM System Management Topology

page 31 of 31