Hi Jeff, John -
You're both absolutely correct; I munged my phrasing a bit in the
proposal. To state things more clearly, the OpenPegasus source will be
delivered via the network storage consolidation delivering into
OpenSolaris. The OpenSolaris project page for OpenPegasus will point
back to this NWS consolidation for that source, and as such the source
will be available from OpenSolaris. We will not provide any one-click
download of a source jar directly from the project page; however, the
project page *will* point back to the OpenPegasus site to get that type
of download instead.
Thanks guys for helping straighten me out. Let me know if my
paraphrase here makes sense.
-gh
Jeff Cheeney wrote:
John Forte wrote:
+1, although I do believe the source should be a part of the OpenSolaris
source base as well. I realize that we want to strive to maintain a
single source base and community around the project but there will
likely be instances where the binaries distributed via OpenSolaris and
the source maintained at openpegasus.org will differ with a binary only
approach.
Upon reflection I agree with John. To integrate with Solaris you will
need to have the source code placed into a consolidation's source tree.
Now it you want to keep a private source tree while the project is in
development, that is your choice, but you will need to deliver the code
into OpenSolaris.
I still support the project, I just think you will need to meet other
requirements for the ultimate integration.
--jc
- John
Gary Horton wrote:
OpenPegasus CIM Server Project
Purpose
Provides up-to-date WBEM service on OpenSolaris via a port of the OpenPegasus
CIM server.
Sponsoring Community Groups
Observability
Storage
Initial Project Team
Robert Harryman
Gary Horton
Project Description
The OpenPegasus CIM Server Project will integrate the OpenPegasus codebase into
OpenSolaris, providing modern SMI-S services for Solaris, with updates to the
supported JDK, CIM Schema and CIM/XML version, and use of a standardized
Provider API. This new CIM server will co-exist with existing WBEM Services on
Solaris, posing no disruption to that service, but providing up-to-date WBEM
support and acting as a migration/upgrade path for the existing clients and
providers to use that modernized support. This co-location of separate WBEM
products will be accomplished via clearly defined ownership of standard and
non-standard ports for each service.
Additional efforts beyond the scope of this project will likely be needed to
address removal of the legacy WBEM service from OpenSolaris. Meanwhile, the
proposed port configuration strategy will support the needs of any WBEM clients
and providers.
Distribution on OpenSolaris will be binary only, with pointers back to the
OpenPegasus community for access to the source. We are working closely with
that community, with agreement that the source code will always live in their
repository.
The following components are included that are essentially equivalent to the
corresponding component in the existing Solaris WBEM services:
* Common Information Model Object Manager (CIM Object Manager, aka CIMOM)
* CIM Repository
* MOF compiler
* Client APIs
* Provider APIs
* Sample source code
The following components are included in addition to existing Solaris WBEM
components:
* Indications API - provides supports for generation of, subscription to
and processing of events in the managed system
* Security infrastructure - authentication, authorization and
confidentiality/integrity support, including SSL and PAM
* SLP - support for automatic discovery of managed resources using the SLP
standard
* Operating System provider - supports generic information such as
operating system type, version, last boot-up time, local date and time, number
of users, swap space size, and free physical memory
* Basic operating system client - exercises the infrastructure by querying
for general information as provided by the OS provider, et. al.
* Computer System provider - supports computer system information such as
computer name, status, and administrator contact information
* Process Providers - support basic UNIX process information, such as name
of the executable image, process ID, priority, execution state, and various
process resource utilization statistics. Client applications can use these
Providers to give clients an understanding of the processes running on the
Managed System within the context of its operating system.
The initial port will be for OpenPegasus version 2.7.1. Full details around
this release can be found at these locations:
Feature Status: http://www.openpegasus.org/page.tpl?CALLER=index.tpl&ggid=799
External Interface:
http://www.openpegasus.org/pp/uploads/40/14874/PEP293_ExternalInterface2.7.htm
Release Notes: http://www.openpegasus.org/pp/uploads/40/14933/ReleaseNotes.htm
The service will be enhanced to take advantage of OpenSolaris security
features, e.g. SMF, PAM, RBAC and SSL, and will advertise itself as a WBEM
service using SLP.
No GUI or BUI is provided, but administration and management is supported by
the a collection of commands, scripts and tools delivered as part of the
OpenPegasus codebase.
Project Needs
OpenSolaris Project Page
SCM Management
Discussion List
Coordination with the OpenPegasus community
Thanks in advance for endorsements from the Storage and Observability
communities.
_______________________________________________
storage-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/storage-discuss
_______________________________________________
storage-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/storage-discuss
--
Gary Horton
Storage Platform Software Group
Sun Microsystems, Inc., Broomfield, CO
303-443-1518, x79140, 303-272-9140
http://blogs.sun.com/lokibear
http://www.linkedin.com/in/garyhorton
_______________________________________________
storage-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/storage-discuss
