Pegasus Status Update April 2001 25 April 2001 Karl Schopmeyer.

Post on 29-Dec-2015

216 views 1 download

Tags:

transcript

Pegasus Status Update

April 2001

25 April 2001

Karl Schopmeyer

Agenda Items

Status Today Work Accomplished Plans

Pegasus Status Today

Project Code Users Events

Version 1.0 Release

Functions Complete except

Events, Query, WQL Includes

All CIM Operations Working Providers Client/services/provider interfaces Full CIM model in C++ Class and Instance Repository Sample clients and providers Compiler

Version 1.0 (cont)

Platforms Linux, Windows, AIX?, Compaq?

Compilers gcc, Visual C++

Documentation Combined user/developer manual

Availability Source Snapshots and CVS Binary Release for Windows/Linux

User Interest

Intel Compaq IBM Novell

Planned Events

Work Group Meeting about 14 May 2001

DMTF Interop Presentations at Interop (about 8 June 2001)

Open Group Members Meeting, July 2001 Week of 16 July Theme is Manageability

Accomplishments

Public Release WEB Site

www.opengroup.org/management/pegasus Open mailing list

Public discussion Events TOG Regional meetings

Plans

New Versions Platforms Working Together

Planned Major Enhancements

Security WQL Indications Non-Blocking Multiple Provider modes

Built in / DLL / Remote Discovery Interop Extensions

CIMOM Manageability

Connectors Architecture Services Extensions Provider Toolkit Better Clients Multiple Language

Support Modules Async Interface

Security

Status today No Security

Objectives DMTF Level authentication SSL encryption ACLs internally

WQL

State Today No ExecQuery Implementation

Objective Implement WQL Level 1

Plans CIM Operation May 2001 WQL – Summer 2001

Indications

State Today Nothing Today

Objective Implement in stages Stage 1

Listener, Indication Service Manager Stage 2

Provider extensions for indications

Provider Communications

State Today Dynamic Library Providers Simple Interface Minimal Toolkit

Objectives Multiple communication models Clarify Interface and move to Specification Create extensive toolkit

Interop Extensions

State Today TBD

Objectives Implement the changes being made by Interop

work Group to provide CIMOM and Provider capabilities, registration, etc.

Non-Blocking Operations

State Today All operations are blocked except for TCP

receive Objectives

Non-blocking operations on providers, services, repositories

Problems Portablity of the model across systems Must include locks also (repository and

provider)

Discovery

State Today Nothing

Objectives Use Well-known port (ASAP) Implement SLP as test Work with Interop to get SLP standardized

Services

State Today We are having problems defining the concept

Objective Define services concepts Refine with initial services

Service examples Indication Manager Indication Registration Manager Etc.

Clients

State Today Simple WEB based CGI Client

Objective Browser/Edit Graphic Client Demonstration clients for particular functions CLI client – Command Line Test Client Special demonstration clients. Scripting Client (ex. TCL)

Providers

State Today Simple Interface Couple of basic providers

Objectives Test Providers Provider Toolkit Working Providers to demonstrate concepts Scripting Provider

Connectors

Concept Separate communications from core CIMOM Provide pluggable communications Provide language conversion

Today We understand our concept No implementation

Objectives Create connector definition Create CIM classes to represent connectors Implement several connectors

Ex. Cim-xml, soap, toMOF, etc.

Async Interface

State Today None

Objectives Still trying to clarify requirements

Other areas for Discussion

Working as a Project Open questions

Open Questions Today

Licensing and the WBEMSource Creating a working test environment

We feature many unit tests Will initiate Client/server tests when server

becomes a daemon Need to add compiler test environment.

Additional help