Discovery in the WBEM Architecture (Infrastructure Discovery)

Transcription

1 Discovery in the WBEM Architecture (Infrastructure Discovery) 3:15 pm- 4:05 pm Thursday Winston Bumpus, Novell, Inc. Director of Standards, Karl Schopmeyer, Open Group / Application WG Chair

2 The Problem Location of manageable resources in a WBEM environment Location of CIM Servers in a WBEM environment Isolation of manageable resources to those of interest to the client Determining the capabilities of the CIM Server to allow and define communication between the server and the client Doing all of this efficiently and dynamically

3 Some of the Major Alternatives Predetermined lists of servers Only in a stable, well-known environment Using network tools IP address queries, port scanning, etc. Yuck, interoperable but inefficient and limited discovery protocols Ex. SLP ( Location Protocol) Using DEN and directory services What about the future and WEB s

4 Status of Discovery Today DMTF has specified SLP* as a discovery mechanism. Initial specification in HTTP operations specification 1.3 (it will be) SLP service template specified in a separate specification *SLP Location Protocol, an IETF standard

5 Objectives of initial version Find CIM Servers efficiently based on an open protocol Creating a light-weight discovery environment that could be implemented easily Discovering CIM Servers and CIM Server capabilities The server, not the managed components.

6 Location Protocol IETF standard, RFC 2608 Designed specifically for discovery of the existence, location, and attributes of services such as CIM. Designed to work in all types of networked environments, from very small to very large publishes attributes, service type and service access point(s). Application queries for services over the network Published service information returned to application s described using URLs Attributes can be embedded in URL or described separately. s can be authenticated requests can include filters Only find Pegasus CIMOMs, for example Implementation can be as minimal as described up to now. DA is designed specifically to provide scalability registrations have limited lifetimes in order to avoid stale data DA s have special discovery characteristics in order to allow other SLP agents to find them. e.g., using DHCP options in restricted networks.

7 SLP Fundamentals Client Client Request: service:cimom.dmtf Reply: service:cimom.dmtf:\\ :4891;namespac e=standard,pegasus,ibm.eserver CIM Server CIM Server Repository Reply: service:cimom.dmtf:\\ :58710;namespac e=standard,pegasus,compaq, authorization=pegasus-strong CIM Server CIM Server Repository

8 SLP Directory Request: service:cimom.dmtf DA DA Client Client Reply: service:cimom.dmtf:\\ :4891;n amespace=standard,pegasus,ibm.eserve r service:cimom.dmtf:\\ :58710;n amespace=standard,pegasus,compaq, authorization=pegasus-strong Registration: service:cimom.dmtf:\\ :4891;namespac e=standard,pegasus,ibm.eserver Registration: service:cimom.dmtf:\\ :58710;namespac e=standard,pegasus,compaq, authorization=pegasus-strong CIM Server CIM Server Repository CIM Server CIM Server Repository

9 CIMOM SLP environment CIMOM CIMOM CIMOM CIMOM CIMOM CIMOM User User Advertisement Advertisement type type Attributes Attributes Access Access Point Point Client asks UA to request services info based on service temlate CIM CIM Client Client Template Template type type Attributes Attributes Access Point Access Point Info for Template from CIM Schemas

10 The Template Discovery is controlled by the service Template Type (WBEM) Separate us from all other services. Location Information so the client can talk directly to the service Attributes (optional and required) Refines information about the server Ex with printers, type, paper, things it might print) For WBEM More about the CIM server More about what this server manages.

11 Implementation of SLP in WBEM environment CIM Server Add component to advertise defined attributes from template Add functions to build attributes from CIM Schema (mapping defined in template spec) CIM Client Add User to make discovery requests and accept responses Add Interface to CIMClient interface so application can initiate requests and analyze responses. Directory Generic technology that is independent of any given template and is used for efficiency, not to add functionality Security We allocated security back to the CIM Server, not to discovery

12 CIMOM SLP environment CIMOM CIMOM CIMOM CIMOM CIMOM CIMOM User User Advertisement Advertisement type type Attributes Attributes Access Access Point Point Client asks UA to request services info based on service temlate CIM CIM Client Client Template Template type type Attributes Attributes Access Point Access Point Info for Template from CIM Schemas

13 The WBEM Template today Provides primarily CIM Server environment information Based completely on information in the CIM Schema Information includes: Server identification Server location Server capabilities Server authentication Namespaces The only required attribute is location Goal of V1 is validation of concept and implementation of protocols with simple template. NOTE: Discovery attributes are independent of the discovery mechanism. We did not base the concept of discovery on SLP, simply the implementation.

14 Next step in discovery What can this CIM Server do? Think V1 who and where V2, what Solution Profiles Profile groups a set of CIM classes into a manageability functionality that is semantically understandable to the client. Profiles are structured groupings of manageability functionality (profiles and subprofiles Effort in process today (See BOF tonight)

15 Profiles (cont) Profiles are defined as instance of a profile class Template extended to include profiles attribute Profiles information could be installed MOF directly compiled Part of provider registration

16 Schedule and Plan for Profiles Work in process now. Primarily changes to Define profile concepts Define profile classes in CIM_interop schema Extend Template to pass profile information

17 Web s Management Future Management Port Description Management Management Discovery Discovery Agencies Agencies Discovery Management Port Description Discovery Management Port Description Business Business Discovery Discovery Agencies Agencies Business Description Find Publish Publish Find Mgmt. Requester Client Environ Client Interact Env Mgmt Port Description Management Port Description Environment Business Description Interact Bus. Requester Client Environ Client

18 DEN Futures DEN V3 Web s Support, UDDI, DSML Part of WBEM not an Alternative WEB s Architecture Identify Locate Configure Secure

19 What should we do? Develop UDDI for Managed s Based on CIM Based on SLP Expand WBEM Architecture Web Based Registry & Location

20 Summary, Issues With HTTP 1.3 spec, WBEM environments will be discoverable SLP offers simply usable implementations Open source environments are implementing now SLP will be used (ex. SNIA) SLP is only one of several major alternatives Directory as discovery Web services discovery and Grid.