ManDevCon

ManDevCon 2006 will take place December 4-7, 2006, at the Santa Clara Marriott, Santa Clara, California.

This work area is to faciliatate the coordiation of OpenPegasus presentations to try and get a balanced coverage avoiding duplication and ensuring that essential topics are addressed.

If you are planning a presentation, please add an entry based on the following template:

1. Title - Presenter(s) - Status (For discussion here / Submitted / Accepted / Withdrawn)

Brief description

If you have any questions, for instance you are loking for a co-presenter, add them to the description.

Reviewers - please add (helpful) comments below the description.

1. “Overview of Pegasus Technology and Project Status and Plans” - K. Schopmeyer - Submitted
   • This is a general update and introduction to Pegasus. Similar to what was done last year. Planned for one hour
2. “Using the CIMPLE Provider development Enviroment” - M. Brasher & K. Schopmeyer - To be Submitted today
   • Overview of CIMPLE, what it is, how to use it, why it is helpful, etc. Planned for one hour.
   • Abstract: CIMPLE is a CIM provider engine. It offers a complete environment for developing and deploying providers into development and production environments. CIMPLE is used to a) build providers that work with a variety of provider interfaces (CMPI, Pegasus C++, etc.) and CIMServers, b) proivde a foundation for implementing CIM-based standards such as WBEM, SMASH, WS-Managmenent, WSDM. CIMPLE has three major advantages over conventional provider technologies: a) it reduces provider development time through the use of first class objects, b) it allows developing providers that can be used with a variety of servers without any rewriting the providers. c) it produces very efficient and small providers. CIMPLE developed providers integrate directly into OpenPegasus. This presentation will introduce CIMPLE, compare it with other provider development technologies, demonstrate how to write providers with it and provide examples of a variety of provider types written in CIMPLE.
3. “Using Pegasus in resource Limited Environments” - Proposal submitted to ManDevCon by K. Schopmeyer
   • This presentation would be based on the work of the peglite group and the peps it is producing to further define a) pegasus resource usage, b) resuource limits, c) options that can be used, etc. to help users in resource limited environments (i.e. embedded systems) with working with pegasus. Right now this proposal only and we have not committed to doing the presentation. The peglite group was positive about it.
   • Abstract: OpenPegasus was originally as a Server based CIMServer. However,it has found wide usage in embedded environments where resources are strongly limited. The OpenPegasus project has created a work group specifically to work on issue that affect this user community. This presentation defines the characteristics, of OpenPegasus that have a direct impact on resource limited environments and the alternatives and options within Pegasus for working within these enviroments.
4. “The CIM Data Model and its Representation in OpenPegasus” - Roger Kumpf - Submitted
   • Abstract: This session defines and describes the CIM data types and model components. Each aspect of the model is distilled to a set of subcomponents, clearly indicating the relationships between components. The concepts are exemplified via a mapping of the components to their representational counterparts in the OpenPegasus object model.
5. “How To Engage” in the OpenPegasus Project - Denise Eckstein - Planned for Submittal
   • This presentation describes how individuals can engage in the OpenPegasus Project from a variety of perspectives. Topics include: How to submit requirements? How to plan releases? How to build the software? How to configure the software? How to report defects? How to contribute?
6. “The CIM-API: a new way of using CIM” - presenter is Andre Asselin - Submitted
   • Abstract: CIM-API is an effort through the Open Group to develop an industry standard API whose key feature is access to CIM infrastructure in-process or out-or-process. The use cases for such a facility include embedded environments, access to remote CIM data via alternate network protocols (e.g. SMASH CLP, web services, etc.), and hierarchical structuring of CIM-based management solutions. This session will show the main use cases with code examples, explain the CIM-API design and key implementation decisions, and summarize the implementation design for OpenPegasus. Overall, we will show why the use of CIM-API will be an important enabler of CIM technology in general, and will expand the range of its applicability.
7. “Security Overview for the CIM Server Administrator” - Dave Sudlik/Heather Sterling - Submitted
   • Abstract: This presentation will use examples from OpenPegasus to discuss all aspects of setting up and managing a secure environment for your CIM Server. Topics include commands and configuration options related to authorization and authentication, what they do, and how they fit together. Discussion will also include information on using OpenSSL to create and manage certificates, truststores, CRLs, and more.
8. “A CIM Operations Tutorial” - Muni Reddy - Submitted
   • Abstract: This demonstration aims at providing an understanding of the CIM Operations using the OpenPegasus Command Line Interface (CLI). Examples using CLI will show all of the CIM Operations, valid and invalid options for each CIM Operation, and various supported and unsupported CIM datatypes. (Additional note for conference organizers: We’d like to present this as a lab exercise where attendees can try the examples concurrently.)
9. “Pegasus and the SNIA SMI-s Implementations” - Submitted by K. Schopmeyer to ManDevCon as presentation Proposal -
   • Abstract: This presentation will focus on the use of OpenPegasus in the SNIA SMI-s environment. It will present the capabilities of the OpenPegasus environment and features of Pegasus that have been and are being implemented to support this environment. It will specifically include definition of the incroporation of profiles as defined in the SNIA environment into OpenPegasus and SLP. This proposal is aimed at present and current users of OpenPegasus as client and providers in the SMI-s environment. NOTE: Right now this is a proposal and before we really complete it we will need concurrence with at least some of the current SMI-s users and we hope to get input from SMI-s Pegasus users to help with the development of the presentation..
10. “The Common Manageability Programming Interface (CMPI)” - Robert Kieninger - Submitted (by D Sudlik)
    • Abstract: The Common Manageability Programming Interface (CMPI) is a standard interface for CIM providers published by The Open Group. It is supported by many popular CIM Servers such as OpenPegasus, OpenWBEM and SBLIM Small Footprint CIM Broker (sfcb). CMPI is a binary compatible provider interface that makes the development of CIM providers independent from a particular CIM Server implementation. The session covers the concepts of CMPI and shows the CMPI Provider Interface by the means of code examples, including updates based on the 2.0 version of the standard.
11. “OpenPegasus BoF” - Martin Kirk - Submitted
    • Abstract: This session will be an open panel discussion allowing users and potential users of OpenPegasus to have a free discussion with the OpenPegasus developer’s team. The panel will be drawn from as many of the OpenPegasus team as are attending the conference. Ideally this would be scheduled as a evening session.