version 1.1, 2003/11/13 16:02:37
|
version 1.7, 2004/10/18 18:20:06
|
|
|
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> |
<html> | <html> |
|
|
<head> | <head> |
<meta name="GENERATOR" content="Microsoft FrontPage 5.0"> | <meta name="GENERATOR" content="Microsoft FrontPage 5.0"> |
<meta name="ProgId" content="FrontPage.Editor.Document"> | <meta name="ProgId" content="FrontPage.Editor.Document"> |
<meta http-equiv="Content-Type" content="text/html; charset=windows-1252"> |
<meta http-equiv="Content-Type" |
|
content="text/html; charset=windows-1252"> |
<title>OpenPegasus</title> | <title>OpenPegasus</title> |
</head> | </head> |
|
|
<body> | <body> |
|
|
<p align="center"><b><font size="4">Pegasus Enhancement Proposal (PEP)</font></b></p> | <p align="center"><b><font size="4">Pegasus Enhancement Proposal (PEP)</font></b></p> |
<p style="margin-top: 0; margin-bottom: 0"><b>PEP #:</b> 103</p> |
<p style="margin-top: 0pt; margin-bottom: 0pt;"><b>PEP #:</b> 175</p> |
<p style="margin-top: 0; margin-bottom: 0"><b>Title: </b>OpenPegasus Version 2.3 |
<p style="margin-top: 0pt; margin-bottom: 0pt;"><b>Title: </b>OpenPegasus |
Release Readme file</p> |
Version 2.4 Release Readme file</p> |
<p style="margin-top: 0; margin-bottom: 0"><b>Version: </b>1.0</p> |
<p style="margin-top: 0pt; margin-bottom: 0pt;"><b>Version: </b><span |
<p style="margin-top: 0; margin-bottom: 0"><b>Created:</b> 12 November 2003</p> |
style="color: rgb(0, 0, 0);">1.4</span></p> |
<p style="margin-top: 0; margin-bottom: 0"><b>Authors: </b>Karl Schopmeyer</p> |
<p style="margin-top: 0pt; margin-bottom: 0pt;"><b>Created:</b> 24 June |
<p style="margin-top: 0; margin-bottom: 0"><b>Status: </b>draft</p> |
2004</p> |
<p style="margin-top: 0; margin-bottom: 0"><b>Version History:</b></p> |
<p style="margin-top: 0pt; margin-bottom: 0pt;"><b>Authors: </b>Warren |
<table border="1" cellspacing="1" bordercolordark="#666666" |
Grunbok, Mike Harris<br> |
bordercolorlight="#CCCCCC" width=100% |
</p> |
style='font-size=10.0pt;font-family:Arial'> |
<p style="margin-top: 0pt; margin-bottom: 0pt;"><b>Status: </b>draft</p> |
<tr> |
<p style="margin-top: 0pt; margin-bottom: 0pt;"><b>Version History:</b></p> |
<th bgcolor="#CAE6CA">Version</th> |
<table bordercolordark="#666666" bordercolorlight="#cccccc" |
<th bgcolor="#CAE6CA">Date</th> |
style="font-family: Arial;" border="1" cellspacing="1" width="100%"> |
<th bgcolor="#CAE6CA">Author</th> |
<tbody> |
<th bgcolor="#CAE6CA">Change Description</th> |
<tr> |
|
<th bgcolor="#cae6ca">Version</th> |
|
<th bgcolor="#cae6ca">Date</th> |
|
<th bgcolor="#cae6ca">Author</th> |
|
<th bgcolor="#cae6ca">Change Description</th> |
</tr> | </tr> |
<tr> | <tr> |
<td align="center">1.0</td> | <td align="center">1.0</td> |
<td align="center">12 Novemberl 2003</td> |
<td align="center">24, June 2004</td> |
<td align="center">Karl Schopmeyer</td> |
<td align="center">Warren Grunbok<br> |
<td>Update from 2.2 Release notes. Converted to HTML</td> |
</td> |
</tr> |
<td>Initial draft<br> |
<tr> |
</td> |
<td align="center"> </td> |
</tr> |
<td align="center"> </td> |
<tr> |
<td align="center"> </td> |
<td align="center"> 1.1</td> |
<td> </td> |
<td align="center">24,August 2004 <br> |
|
</td> |
|
<td align="center">Warren Grunbok <br> |
|
</td> |
|
<td>Mostly spelling changes, adds to very last paragraph <br> |
|
</td> |
|
</tr> |
|
<tr> |
|
<td style="vertical-align: top;">1.2<br> |
|
</td> |
|
<td style="vertical-align: top;">31, August 2004<br> |
|
</td> |
|
<td style="vertical-align: top;">Warren Grunbok<br> |
|
</td> |
|
<td style="vertical-align: top;">Changes based on architecture |
|
review. Removed /Directory structure section and placed |
|
into seperate document.<br> |
|
<br> |
|
</td> |
|
</tr> |
|
<tr> |
|
<td style="vertical-align: top;">1.3<br> |
|
</td> |
|
<td style="vertical-align: top;">???<br> |
|
</td> |
|
<td style="vertical-align: top;">Warren Grunbok<br> |
|
</td> |
|
<td style="vertical-align: top;">Removed Pegasus Directory |
|
structure and placed in PEP 191, Added Copyright and End of Doc marker.<br> |
|
</td> |
|
</tr> |
|
<tr> |
|
<td style="vertical-align: top; color: rgb(0, 0, 0);">1.4<br> |
|
</td> |
|
<td style="vertical-align: top; color: rgb(0, 0, 0);">27, |
|
Sept 2004<br> |
|
</td> |
|
<td style="vertical-align: top; color: rgb(0, 0, 0);">Warren |
|
Grunbok<br> |
|
</td> |
|
<td style="vertical-align: top; color: rgb(0, 0, 0);">Corrected |
|
Security changes as per Sterling.<br> |
|
</td> |
</tr> | </tr> |
|
</tbody> |
</table> | </table> |
<hr> | <hr> |
<p><b>Abstract:</b> Installation, build, operation information on the |
<p><b>Abstract:</b> Installation, build, operation information on |
Pegasus Platform Version 2.3 Release. Note that if this readme conflicts with |
the Pegasus Platform Version 2.4.0 Release. Note that if this readme |
the documentation in the release notes or interface defintion documents for a |
conflicts with the documentation in the release notes or interface |
particular release, those documents should be considered authorative. This is a |
definition documents for a particular release, those documents should |
simplified overview to act as an introduction to Pegasus.</p> |
be considered authorative. This is a simplified overview to act as an |
|
introduction to Pegasus.</p> |
<hr> | <hr> |
|
<p align="center"><b><font size="5">OpenPegasus - A Manageability |
<p align="Center"><b><font size="5">OpenPegasus - A Manageability Services Broker |
Services Broker for the DMTF CIM/WBEM Standards |
for the DMTF CIM/WBEM Standards |
</font></b></p> |
</font> |
<p align="left"><b>Tagline:</b> OpenPegasus is an object manager for |
</b> |
DMTF CIM objects written in C++ |
|
|
<p align="left"> |
|
<b>Tagline:</b> OpenPegasus is an object manager for DMTF CIM objects written in C++ |
|
and supported by The Open Group </p> | and supported by The Open Group </p> |
|
|
<p align="left"> | <p align="left"> |
|
<b>STATUS:</b> Revised Sept 2004 for Pegasus release version |
<b>STATUS:</b> Revised October 2003 for Pegasus release version 2.3. |
2.4.0 |
</p> |
- Approved<br> |
|
</p> |
<p align="center"> |
<a href="#Overview">Overview</a> |
<b><font size="4">Table of Contents</font></b><p align="left" style="margin-top: 0; margin-bottom: 0"> |
<blockquote style="margin-top: 0pt; margin-bottom: 0pt;"> <a |
<a href="#Overview"> Overview</a> |
href="#avail_of_peg">Availability of Pegasus</a><br> |
|
<a href="#peg_maj_comp">Pegasus Major Components</a><br> |
<p align="left" style="margin-top: 0; margin-bottom: 0"> |
<a href="#avail_of_peg">Availability of Pegasus</a><br> |
<a href="#Availability of Pegasus">Availability of Pegasus</a><p align="left" style="margin-top: 0; margin-bottom: 0"> |
<a href="#peg_sup_plat">Pegasus Supported Platforms</a><br> |
<a href="#Pegasus Major Components">Pegasus Major Components</a><p align="left" style="margin-top: 0; margin-bottom: 0"> |
<a href="#peg_dep">Pegasus Dependencies</a><br> |
<a href="#Pegasus Supported Platforms">Pegasus Supported Platforms</a><p align="left" style="margin-top: 0; margin-bottom: 0"> |
<a href="#peg_dir_struc">The Pegasus Directory Structure</a><br> |
<a href="#Pegasus Dependencies">Pegasus Dependencies </a> |
<a href="#dev_with_peg">Development with Pegasus and Pegasus Tools</a><br> |
|
<a href="#cmnd">Commands</a><br> |
<p align="left" style="margin-top: 0; margin-bottom: 0"> |
<a href="#docs">Documentation</a><br> |
<a href="#The Pegasus Directory Structure">The Pegasus Directory Structure</a> |
<a href="#part">Participate</a><br> |
|
</blockquote> |
<p align="left" style="margin-top: 0; margin-bottom: 0"> |
<a href="#inst_peg">Install Pegasus</a> |
<a href="#Pegasus Installation">Installation</a> |
<blockquote style="margin-top: 0pt; margin-bottom: 0pt;"><a |
|
href="#download">Download or checkout Pegasus</a><br> |
<p align="left" style="margin-top: 0; margin-bottom: 0"> |
<a href="#vfy_req_sw">Verify that you have the required |
<a href="#Building Pegasus">Building Pegasus </a> |
software</a><br> |
|
<a href="#set_envt_var">Set the environment variables</a><br> |
<p align="left" style="margin-top: 0; margin-bottom: 0"> |
<a href="#bld">Build the Pegasus runtime, test files, test clients, |
<a href="#Populate the Repository">Populate the Repository</a> |
and repository</a><br> |
|
<a href="#pop_peg_rep">Populate the Pegasus repository</a><br> |
<p align="left" style="margin-top: 0; margin-bottom: 0"> |
<a href="#reg_prov">Register providers in the Pegasus environment</a><br> |
<a href="#Registering Providers in the Pegasus Environment">Registering |
<a href="#bld_rpms">Build an RPM for Pegasus</a><br> |
Providers</a><p align="left" style="margin-top: 0; margin-bottom: 0"> |
<a href="#note_bld_peg_lnx">Notes |
<a href="#The MU Utility">The MU Utility</a> |
about Building Pegasus on Linux</a><br> |
|
<a href="#note_bld_peg_ssl">Notes on building Pegasus with SSL</a><br> |
|
<blockquote style="margin-top: 0pt; margin-bottom: 0pt;"> <a |
<p align="left" style="margin-top: 0; margin-bottom: 0"> |
href="#crt_ssl_cert">Creating SSL |
<a href="#Notes about Building Pegasus on Linux">Notes about Building Pegasus on Linux</a> |
certifications</a><br> |
|
</blockquote> |
<p align="left" style="margin-top: 0; margin-bottom: 0"> |
<a href="#bld_peg_win">Building |
<a href="#Notes about Building Pegasus with SSL">Notes on building Pegasus with SSL</a> |
Pegasus on Windows 2000 or Windows XP With Microsoft Visual C++</a><br> |
|
<blockquote style="margin-top: 0pt; margin-bottom: 0pt;"> <a |
<p align="left" style="margin-top: 0; margin-bottom: 0"> |
href="#mu_utility">The MU Utility</a><br> |
<a href="#Building Pegasus on Windows 2000 or Windows XP With Microsoft Visual C++">Building Pegasus on Windows 2000 or Windows XP With Microsoft Visual C++</a><p align="left" style="margin-top: 0; margin-bottom: 0"> |
</blockquote> |
<a href="#Installing the Pegasus HTML Test Client">Installing the Pegasus HTML Test Client |
</blockquote> |
</a> |
<a href="#test">Test the Pegasus installation</a><br> |
|
<blockquote style="margin-top: 0pt; margin-bottom: 0pt;"> <a |
<p align="left" style="margin-top: 0; margin-bottom: 0"> |
href="#inst_peg_html"> Installing the Pegasus HTML Test Client</a><br> |
<a href="#Development with Pegasus and Pegasus Tools">Development with Pegasus and Pegasus Tools</a> |
<a href="#test_icu">Testing with ICU enabled</a><br> |
|
</blockquote> |
<p align="left" style="margin-top: 0; margin-bottom: 0"> |
<hr> |
<a href="#Commands">Commands</a> |
|
|
|
<p align="left" style="margin-top: 0; margin-bottom: 0"> |
|
<a href="#Creating SSL certifications">Creating SSL certifications</a>. |
|
|
|
<p align="left" style="margin-top: 0; margin-bottom: 0"> |
|
<a href="#Testing with ICU enabled">Testing with ICU enabled </a> |
|
|
|
<p align="left" style="margin-top: 0; margin-bottom: 0"> |
|
<a href="#Pegasus Documentation">Documentation</a> |
|
|
|
<p align="left" style="margin-top: 0; margin-bottom: 0"> |
|
<a href="#Participate!">Participate</a> |
|
|
|
<h1><a name="Overview">Overview</a> </h1> | <h1><a name="Overview">Overview</a> </h1> |
|
<p><b>OpenPegasus (also referred to as Pegasus):</b> |
<p>OpenPegasus (also referred to as Pegasus): |
Pegasus is an open-source CIM Server for DMTF CIM objects. It is |
|
written |
Pegasus is an open-source object manager (CIMOM) for DMTF CIM objects. It is written |
in C++ and includes the Object manager (CIMOM), a set of defined |
in C++ and includes the Object manager, a set of defined interfaces, and |
interfaces, an implemenation of the CIMOperations over HTTP operations |
Interface libraries |
and their cimxml HTTP encodings, and Interface libraries |
for both client and providers. It is maintained | for both client and providers. It is maintained |
consistent with the DMTF CIM and WBEM specifications except for exceptions |
consistent with the DMTF CIM and WBEM specifications except for |
|
exceptions |
noted in the documentation. | noted in the documentation. |
<P> |
</p> |
Pegasus is open source and is covered under the MIT open-source license. |
<p>Pegasus is open source and is covered under the MIT open-source |
<P> |
license.</p> |
Pegasus is being developed and maintained under the auspices of The Open |
<p>Pegasus is being developed and maintained under the auspices of The |
Group. Pegasus is maintained under the license defined in the doc directory |
Open |
(LICENSE) of this release. This licensing is intended to support as wide a |
Group. Pegasus is maintained under the license defined in the doc |
|
directory |
|
(LICENSE) of this release. This licensing is intended to support as |
|
wide a |
distribution as possible with minimal demands on the users. | distribution as possible with minimal demands on the users. |
<P> |
</p> |
More information on this project, access to the CVS, and documentation on |
<p>More information on this project, access to the CVS, and |
|
documentation on |
Pegasus are available from the OpenGroup WEB site. | Pegasus are available from the OpenGroup WEB site. |
<P> |
</p> |
<a href="http://www.opengroup.org">http://www.openpegaus.org</a><p> |
<p> <a target="blank" |
There are separate documents |
href="http://www.openpegasus.org">http://www.openpegasus.org</a></p> |
|
<p>There are a number of separate documents representing the status and |
|
each release of Pegasus |
|
</p> |
<ul> | <ul> |
<li>What's new for this release - WHATSNEW and the release notes for each |
<li>What's new for this release - See the PEPs (Pegasus Enhancement |
release.<li>What's Broken - BUGS - See the ReleaseNotes for this release in the CVS and |
Procedures) release notes on the Pegasus web site and duplicated in the |
the web site as a Pegasus PEP.<li>Release Notes for each released version</ul> |
source top level directory </li> |
|
<li>What's Broken - BUGS - See the ReleaseNotes for this release in |
|
the CVS and the web site as a Pegasus PEP.</li> |
<p>The release notes are available on the WEB site as Pegasus PEP documents and |
</ul> |
in the CVS for each release.</p> |
<p>The release notes are available on the WEB site as Pegasus PEP |
<table border="1" cellspacing="1" width="31%" id="AutoNumber3"> |
documents and in the CVS for each release.</p> |
|
<table id="AutoNumber3" border="1" cellspacing="1" width="31%"> |
|
<tbody> |
<tr> | <tr> |
<td width="42%">Release</td> |
<td width="42%"><b>Release</b></td> |
<td width="58%">Release Notes PEP</td> |
<td width="58%"><b>Release Notes PEP</b></td> |
</tr> | </tr> |
<tr> | <tr> |
<td width="42%">2.0</td> | <td width="42%">2.0</td> |
|
|
<td width="42%">2.3</td> | <td width="42%">2.3</td> |
<td width="58%">PEP 98</td> | <td width="58%">PEP 98</td> |
</tr> | </tr> |
|
<tr> |
|
<td style="vertical-align: top;">2.4<br> |
|
</td> |
|
<td style="vertical-align: top;">PEP 185<br> |
|
</td> |
|
</tr> |
|
</tbody> |
</table> | </table> |
|
<h2><a name="avail_of_peg">Availability of Pegasus</a></h2> |
|
<p>Pegasus is distributed as open source under the MIT open-source |
<h1><a name="Availability of Pegasus">Availability of Pegasus</a></h1> |
license. The distribution is available via CVS and snapshot images in |
|
tar and zip file formats on the web site. |
<p>Pegasus is distributed as open source under the MIT open-source license. The distribution is available via |
The source code from CVS can be found at the following Open Group CVS |
CVS and snapshot images in tar and zip file formats. |
server; |
The source code from CVS can be found at the following Open Group CVS server; |
</p> |
<p> |
<p><font face="Courier New"> |
<font face="Courier New"> |
cvs.opengroup.org:/cvs/MSB </font> </p> |
cvs.opengroup.org:/cvs/MSB </font> |
<p>using the password authenticating server option (pserve). |
<p> |
</p> |
using the password authenticating server option (pserve). |
<p>Anonymous access for read is with the name and password "anon" as |
<p> |
follows: |
Anonymous access for read is with the name and password "anon" as follows: |
</p> |
<blockquote> | <blockquote> |
<p style="margin-top: 0; margin-bottom: 0"> |
<p style="margin-top: 0pt; margin-bottom: 0pt;"><font |
<font face="Courier New">%export CVSROOT=:pserver:anon@cvs.opengroup.org:/cvs/MSB |
face="Courier New">%export |
</font> |
CVSROOT=:pserver:anon@cvs.opengroup.org:/cvs/MSB </font></p> |
<p style="margin-top: 0; margin-bottom: 0"><font face="Courier New">%cvs login |
<p style="margin-top: 0pt; margin-bottom: 0pt;"><font |
</font> |
face="Courier New">%cvs login </font></p> |
</blockquote> | </blockquote> |
<p> | <p> |
When requested, enter the password "anon". |
When requested, enter the password "anon". |
The source tree is in the directory pegasus. To check out the complete Pegasus |
The source tree is in the directory pegasus. To check out the complete |
|
Pegasus |
source tree just type: | source tree just type: |
<p> |
</p> |
<font face="Courier New"> |
<p><font face="Courier New"> |
cvs co pegasus </font> | cvs co pegasus </font> |
<p> |
</p> |
A Pegasus directory will be created under the current directory and populated |
<p>A Pegasus directory will be created under the current directory and |
with the complete source tree and documentation. To get the latest updates |
populated |
after a checkout just type this from Pegasus root: |
with the complete source tree and documentation. To get the latest |
<p> |
updates after a checkout just type this from Pegasus root: |
<font face="Courier New"> |
</p> |
|
<p><font face="Courier New"> |
cvs update -d </font> | cvs update -d </font> |
|
</p> |
<p> |
<p>Active contributors to Pegasus have write access to the CVS |
Active contributors to Pegasus have write access to the CVS repository. |
repository. |
If you are interested in contributing back to the Pegasus project, | If you are interested in contributing back to the Pegasus project, |
(i.e. write (checkin) access to CVS) please request access from either | (i.e. write (checkin) access to CVS) please request access from either |
Martin Kirk (m.kirk@opengroup.org) or Karl Schopmeyer |
Martin Kirk (<a href="mailto:%28k.m.kirk@opengroup.org">m.kirk@opengroup.org</a>) |
<a href="mailto:(k.schopmeyer@opengroup.org">(k.schopmeyer@opengroup.org</a>). |
or Karl Schopmeyer <a href="mailto:%28k.schopmeyer@opengroup.org">k.schopmeyer@opengroup.org</a>. |
|
</p> |
<h1> |
<h2><a name="peg_maj_comp">Pegasus Major Components</a></h2> |
<a name="Pegasus Major Components">Pegasus Major Components</a></h1> |
|
|
|
<p>The major components of Pegasus are: | <p>The major components of Pegasus are: |
|
</p> |
<ul> | <ul> |
<li><b>Pegasus Server</b> - WBEM/CIM Server with interfaces for providers and clients |
<li><b>Pegasus Server</b> - WBEM/CIM Server with interfaces for |
</li> |
providers and clients </li> |
<li><b>Pegasus Repositories</b> - Today Pegasus provides a defined class repository |
<li><b>Pegasus Repositories</b> - Today Pegasus provides a defined |
interface and a simple file based class repository. It also includes |
class repository interface and a simple file based class repository. It |
an instance repository. Note that these repository were created for |
also includes an instance repository. Note that these repository were |
functionality, not efficieny. It is expected that they will be replaced |
created for functionality, not efficieny. It is expected that they will |
with other implementations of the respository function as the need arises. |
be replaced with other implementations of the respository function as |
</li> |
the need arises. </li> |
<li><b>Pegasus Client Library</b> - Tools for building Pegasus clients based on the Pegasus |
<li><b>Pegasus Client Library</b> - Tools for building Pegasus |
C++ interfaces and using the WBEM HTTP/XML protocols or directly |
clients based on the Pegasus C++ interfaces and using the WBEM HTTP/XML |
interfacing with Pegasus. |
protocols or directly interfacing with Pegasus. </li> |
</li> |
<li><b>Pegasus Test Clients</b> - Simple test clients being developed |
<li><b>Pegasus Test Clients</b> - Simple test clients being developed as part of the |
as part of the Pegasus development process. These can be seen in the |
Pegasus development process |
src/Clients directory and its subdirectories </li> |
</li> |
<li><b>Pegasus HTML Test Client</b> - To aid in testing we created a |
<li><b>Pegasus HTML Test Client</b> - To aid in testing we created a test client for |
test client for Pegasus that uses a WEB server (ex. Apache) with a set |
Pegasus that uses a WEB server (ex. Apache) with a set of CGI modules and |
of CGI modules and HTML to allow the entry of Pegasus operations from a |
HTML to allow the entry of Pegasus operations from a WEB browser as forms |
WEB browser as forms and the receipt of the response as WEB pages. This |
and the receipt of the response as WEB pages. This has proven useful as a |
has proven useful as a test tool and can be used for a wide variety of |
test tool and can be used for a wide variety of demonstrations. |
demonstrations. </li> |
</li> |
<li><b>Pegasus Provider Library</b> - Tools for building Pegasus |
<li><b>Pegasus Provider Library</b> - Tools for building Pegasus providers using the Pegasus |
providers using the Pegasus C++ interfaces. </li> |
C++ interfaces. |
<li><b>Pegasus Providers</b> - Providers to illustrate the use of |
</li> |
Pegasus services including providers for test and demonstration. </li> |
<li><b>Pegasus Providers</b> - Providers to illustrate the use of Pegasus services |
<li><b>Pegasus Control Providers</b> - Common services for use by |
including providers for test and demonstration. |
other Pegasus components to extend Pegasus capabilites. </li> |
</li> |
<li><b>Pegasus MOF Compiler </b>- There standalone compiler |
<li><b>Pegasus Control Providers</b> - Common services for use by other Pegasus |
(cimmofl) for MOF files that can be used |
components to extend Pegasus capabilites. |
to install MOF into the Pegasus schema repository and also to check |
</li> |
syntax. There is also a compiler that operates as a Pegasus |
<li><b>Pegasus MOF Compiler </b>- There standalone compiler (cimmofl) for MOF files that can be used |
client(cimmof) There is also a tool to extract the MOF from the |
to install MOF into the Pegasus schema repository and also to check syntax. |
repository. </li> |
There is also a compiler that operates as a Pegasus client(cimmof) |
|
There is also a tool to extract the MOF from the repository. |
|
|
|
</li> |
|
</ul> | </ul> |
|
<h2> |
<h1> |
<a name="peg_sup_plat">Pegasus Supported Platforms</a></h2> |
<a name="Pegasus Supported Platforms">Pegasus Supported Platforms</a></h1> |
|
|
|
<p> | <p> |
Pegasus is regularly tested against a variety of platforms by the development |
Pegasus is regularly tested against a variety of platforms by the |
group. The set of platforms and exact set of compilers for any given |
development group. The set of platforms and exact set of |
release is documented in the Release notes for that release (see the CVS source |
compilers for any given release is documented in the Release notes for |
tree root directory or the Pegasus PEP defining the ReleaseNotes for any |
that release (see the CVS source tree root directory or the Pegasus PEP |
particular release).</p> |
defining the ReleaseNotes for any particular release).</p> |
|
<p> |
<p> |
Pegasus is supported on a variety of platforms. The list of |
Generally Pegasus is supported on the following Platforms and Compilers.</p> |
platforms can be found in the release notes associated with this |
<table border="1" cellspacing="1" id="AutoNumber2" width="728"> |
release.<br> |
<tr> |
</p> |
<td width="169" bgcolor="#99FF99"><b>Platform and OS</b></td> |
<br> |
<td width="556" bgcolor="#99FF99"><b>Compilers</b></td> |
<h2><a name="peg_dep">Pegasus Dependencies</a></h2> |
</tr> |
|
<tr> |
|
<td width="169">AIX</td> |
|
<td width="556">VisualAge C++ Version</td> |
|
</tr> |
|
<tr> |
|
<td width="169">HP-UX</td> |
|
<td width="556">HP aC++ </td> |
|
</tr> |
|
<tr> |
|
<td width="169">Linux Itanium</td> |
|
<td width="556">gcc</td> |
|
</tr> |
|
<tr> |
|
<td width="169">Linux IA-32</td> |
|
<td width="556">gcc (versions 2.9x and 3.xx)</td> |
|
</tr> |
|
<tr> |
|
<td width="169">Windows 2000</td> |
|
<td width="556">Microsoft Visual C++ Ver 6 and Microsoft .Net compiler |
|
Version <font color="#FF0000">7</font></td> |
|
</tr> |
|
<tr> |
|
<td width="169">Windows XP</td> |
|
<td width="556">Microsoft Visual C++ Ver. 6 and Microsoft .Net compiler |
|
Version <font color="#FF0000">7</font></td> |
|
</tr> |
|
</table> |
|
|
|
<h1> |
|
<a name="Pegasus Dependencies">Pegasus Dependencies </a></h1> |
|
|
|
<p> | <p> |
We have worked to minimize the dependence of Pegasus on other software | We have worked to minimize the dependence of Pegasus on other software |
packages and tools. Currently Pegasus has the following dependencies: | packages and tools. Currently Pegasus has the following dependencies: |
<p> |
</p> |
<b>1. GNUMAKE</b> - To simplify the building of Pegasus across multiple platforms we |
<p><b>1. GNUMAKE</b> - To simplify the building of Pegasus across |
|
multiple platforms we |
have standardized on a set of build tools including: GNUMAKE. We are using |
have standardized on a set of build tools including: GNUMAKE. We are |
GNUMAKE 3.79.1 successfully both in Windows and Linux environments. |
using GNUMAKE 3.79.1 successfully both in Windows and Linux |
<p> |
environments. |
GNUMAKE is available from :<p> |
</p> |
<a href="http://www.gnu.org">http://www.gnu.org</a> |
<p>GNUMAKE is available from :</p> |
|
<p> <a target="blank" |
<p> |
href="http://www.gnu.org">http://www.gnu.org</a> |
NOTE: A set of the required tools for |
</p> |
windows platforms is available on the openpegasus web site.<p> |
<p> NOTE: A set of the required |
<b>2. MU.EXE </b>- To minimize the difference between Linux and Windows for GNUMAKE, |
tools for windows platforms is available on the openpegasus web |
|
site. <a href="www.openpegasus.org">www.openpegasus.org</a><br> |
|
</p> |
|
<p><b>2. MU.EXE </b>- To minimize the difference between Linux and |
|
Windows for GNUMAKE, |
we have created a utility called MU.exe. This utility is required for | we have created a utility called MU.exe. This utility is required for |
Pegasus make with ONLY Windows environment. It is provided as an alternative to |
Pegasus make with ONLY Windows environment. It is provided as an |
requiring a number of UNIX utilities (SH, RM, etc.) on the windows platform |
alternative to |
|
requiring a number of UNIX utilities (SH, RM, etc.) on the windows |
|
platform |
and effectively provides the functions of these utilities that GNUMAKE | and effectively provides the functions of these utilities that GNUMAKE |
needs. MU is not required on UNIX or LINUX platforms. | needs. MU is not required on UNIX or LINUX platforms. |
<p> |
</p> |
NOTE: The binary for MU.EXE is not distributed in the Pegasus bin directory. |
<p>NOTE: The binary for MU.EXE is not distributed in the Pegasus bin |
You must build it separately. MU source code is part of the distribution |
directory. |
in the directory src/utils/MU with its own make file. You must compile MU |
You must build it separately. MU source code is part of the |
|
distribution |
|
in the directory src/utils/MU with its own make file. You must compile |
|
MU |
before you initiate the Pegausu make. | before you initiate the Pegausu make. |
<p> |
</p> |
NOTE: A copy of the binary is made available as a zip file on the Pegasus |
<p>NOTE: A copy of the binary is made available as a zip file on the |
|
Pegasus |
WEB site. | WEB site. |
|
</p> |
|
<p>Again, MU is used ONLY if you are using Windows. |
|
</p> |
|
<p><b>3. FLEX and BISON</b> - These tools were used to develop the MOF |
|
compiler and WQL |
|
parser. Anybody intending to recompile the compiler or parser from |
|
scratch will be required to have these tools. They are only required if |
|
changes need to be made to the files for parsing and compiling. |
|
</p> |
|
<p><b>4. DOC++ </b>- The Pegasus documentation is taken from a |
|
combination of text files |
|
and the Pegasus header files themselves. This documentation is |
|
formatted with DOC++ and GAWK. These tools are required if the |
|
documentation is to be recreated but we expect that only the core team |
|
will be recreating documentation. |
|
</p> |
|
<p><b>5. ICU Internationalization libraries</b> - These libraries are |
|
used as the basis for message catalogs for message |
|
internationalization. See the ICU website |
|
(http://oss.software.ibm.com/icu/) for more information on these |
|
libraries</p> |
|
<p>6. <b>OpenSSL </b>- If it is intended to use SSL on the |
|
communication protocol, the OpenSSL libraries are required.</p> |
|
<h1><a name="peg_dir_struc">The Pegasus Directory |
|
Structure</a></h1> |
<p> | <p> |
Again, MU is used ONLY if you are using Windows. |
Pegasus is distributed as a complete source directory structure that |
|
should be |
<p> |
|
<b>3. FLEX and BISON</b> - These tools were used to develop the MOF compiler and WQL |
|
parser. Anybody intending to recompile the compiler or parser from scratch |
|
will be required to have these tools. They are only required if changes need |
|
to be made to the files for parsing and compiling. |
|
<p><b>4. DOC++ </b>- The Pegasus documentation is taken from a combination of text files |
|
and the Pegasus header files themselves. This documentation is formatted |
|
with DOC++ and GAWK. These tools are required if the documentation is to |
|
be recreated but we expect that only the core team will be recreating |
|
documentation. |
|
|
|
<p><b>5. ICU Internationalization libraries</b> - These libraries are used as |
|
the basis for message catalogs for message internationalization. See the ICU |
|
website (http://oss.software.ibm.com/icu/) for more information on these |
|
libraries<p>6. <b>OpenSSL </b>- If it is intended to use SSL on the |
|
communication protocol, the OpenSSL libraries are required.<h1> |
|
<a name="The Pegasus Directory Structure">The Pegasus Directory Structure</a></h1> |
|
<p> |
|
Pegasus is distributed as a complete source directory structure that should be |
|
installed either from one of the snapshots or from CVS. | installed either from one of the snapshots or from CVS. |
|
</p> |
|
The Pegasus Directory is documented in<span |
|
style="color: rgb(51, 255, 51);"> <span style="color: rgb(0, 0, 0);">PEP |
|
191</span> </span>and listed in the |
|
Pegasus /doc directory.<br> |
|
<h1><a name="dev_with_peg">Development with Pegasus and Pegasus Tools</a></h1> |
|
<p>ATTN: This section needs to be completed. It should reference the |
|
more complete documentation. |
|
</p> |
|
<h1><a name="cmnd">Commands</a></h1> |
|
<p> |
|
The manpages for each of the commands are in rpm/manLinux/man1.Z |
|
directory (on CVS) </p> |
|
<p>To see simple help for each of the commands, use the "-h" flag. </p> |
|
<blockquote> |
|
<pre>Examples:<br>bin/cimserver –s (Shuts it down)<br>bin/cimserver traceLevel=4 traceComponents=ALL (starts server with config flags)<br>bin/cimprovider –l –s (lists providers and their status)<br>bin/cimprovider –e –m OperatingSystemModule (enables the OperatingSystem provider)<br>bin/cimuser –a –u guest –w ThePassword<br>bin/cimuser –l (lists the users)<br>bin/tomof CIM_Config (extract CIM_Config from repository and present it in MOF type)<br></pre> |
|
</blockquote> |
|
<h1><a name="docs">Pegasus Documentation</a></h1> |
|
<p>The documentation is currently in preparation. Much of Pegasus |
|
is documented in the PEGASUS PEPs which are the basis for approval of |
|
Pegasus functionality, changes, plans, etc. These documents are |
|
openly available on the PEGASUS web site. The preliminary |
|
documentation |
|
is not provided with this release. The current documentation is |
|
maintained both as a manual created |
|
under the tool DOC++ in the runtime subdirectory manual/html (see |
|
doc/devManual to create), as an api document also creatable from the |
|
source tree (see doc/apidoc) and as other miscellaneous documentation |
|
in the doc directory. Also there is a set of release notes. Normally |
|
the release notes for the current release are available in the root |
|
source directory of CVS.</p> |
|
<p>Note that the Pegasus WEB site at The Open Group will be the source |
|
of most |
|
documentation in the future and today is the source of most discussion |
|
and |
|
design documentation. </p> |
|
<h1><a name="part">Participate!</a></h1> |
|
<p>We are looking for people who want to join the Pegasus work group |
|
and |
|
contribute to effort of getting this Pegasus off the ground. Please |
|
join the mailing list by visiting www.openpegasus.org, and click on |
|
Mailing Lists. |
|
</p> |
|
<h1> |
|
<a name="inst_peg">Install Pegasus</a> </h1> |
<p> | <p> |
This structure is generally as follows:<p> |
You can install and run Pegasus on any of the supported platforms. The |
<font face="Courier New">Pegasus Source Structure</font><p> |
installation process includes the following steps: |
<font face="Courier New">Pegasus Root directory (PEGASUS_ROOT environment |
</p> |
variable)</font><ul> |
<ol> |
<li><font face="Courier New"><b>cgi</b> Source for the Pegasus WEB Based Test client |
<li>Download or checkout Pegasus. </li> |
</font> |
<li>Verify that you have the required software. </li> |
<ul> |
<li>Set environment variables. </li> |
<li><font face="Courier New">cgi-bin CGI Directories for WEB demonstration. |
<li>Build the Pegasus runtime, test files, test clients and |
This directory is normally empty but can |
repository. </li> |
be populated from the runtime with the make |
</ol> |
from cgi. |
<p></p> |
</font></li> |
<p><a name="download"><strong>Step 1: Download or checkout Pegasus</strong></a></p> |
<li><font face="Courier New">htdocs HTML Pages for Pegasus WEB demonstration |
<p> |
</font></li> |
Pegasus is freely available from the open group's Pegasus home page: <a |
</ul> |
target="blank" href="http://www.openpegasus.org">http://www.openpegasus.org</a>. |
</li> |
To |
<li><font face="Courier New"><b>doc</b> Miscellaneous Pegasus Documents. |
obtain Pegasus, you can either check it out using CVS or download a |
</font> |
snapshot image of the soruce distribution. For more information about |
<ul> |
checking out Pegasus using CVS, see: <a href="#avail_of_peg">Availability |
<li><font face="Courier New">apidoc - Source for the public api |
of Pegasus</a>. </p> |
documentation.</font></li> |
<p> |
<li><font face="Courier New">DevManual Source and build files for developers' manual |
Pegasus is not currently releasing binaries, but you can create RPMs |
mak General make files (used by other makes)</font></li> |
using a script included with the source distribution. See <a |
</ul> |
href="#bld_rpms">Building RPMs for Pegasus</a> for more information. |
</li> |
</p> |
<li><font face="Courier New"><b>mak</b> - Common make files for Pegasus |
<p> <a name="vfy_req_sw"><strong>Step 2: Verify that you have |
compilation</font></li> |
the required software</strong></a></p> |
<li><font face="Courier New"><b>Dummy</b> -</font></li> |
<p> |
<li><font face="Courier New"><b>InterfaceArchive</b> -</font></li> |
Refer to the section <a href="#peg_dep">Pegasus |
<li><font face="Courier New"><b>rpm</b> - files for rpm installation for Linux</font></li> |
Dependencies</a> and verify that you have the software required for |
<li><font face="Courier New"><b>Schemas</b> - Schemas used in the installation |
your Operating System and planned usage of Pegasus. |
of Pegasus. This includes currently released versions of the DMTF schemas in |
</p> |
subdirectories (ex. CIM27) and Pegasus local Schemas (ex. </font></li> |
<p> <a name="set_envt_var"><strong>Step 3: Set the environment |
<li><font face="Courier New"><b>src</b> All Pegasus Source Files |
variables</strong></a></p> |
</font> |
<p>Before installing or running Pegasus, ensure that the following |
<ul> |
environment variables have been defined or updated: </p> |
<li><font face="Courier New"><b>ACEExample</b> Test directrory with examples of the use of ACE (obsolete). |
<dl> |
</font></li> |
<dt>PEGASUS_ROOT </dt> |
<li><font face="Courier New"><b>Clients</b> Source for various test |
<dd>Defines the path to the "pegasus" directory you've pulled from |
clients and demonstration clients.</font></li> |
CVS, for example: <tt>/opt/pegasus/pegasus-2.3.2</tt> <br> |
<li><font face="Courier New"><b>CGICLIENT</b> Pegasus test client that uses a WEB browser |
</dd> |
JAVA Java Client support modules |
<dt>PEGASUS_HOME </dt> |
</font></li> |
<dd>Defines the directory that will contain the output binary files. |
<li><font face="Courier New"><b>Pegasus</b> - Core pegasus modules. |
For example, if you set this to <tt>$HOME/pegasus_home</tt>, then the |
</font> |
output will go into <tt>$HOME/pegasus_home/bin</tt> and <tt>$HOME/pegasus_home/lib.</tt> |
<ul> |
<br> |
<li><font face="Courier New"><b>Client</b> Pegasus Client API Tests |
If you plan on doing parallel builds, you may want to define a unique |
depends tests </font></li> |
PEGASUS_HOME value for each build you need, that way the output of each |
<li><font face="Courier New"><b>Common</b> Pegasus Common Functions (C++ source and headers |
build will be placed in its own directory, for example: <tt>$HOME/pegasus_home_LINUX_IX86_GNU.</tt> |
tests Test programs for the common functions</font></li> |
<br> |
<li><font face="Courier New"><b>Compiler</b> Pegasus MOF compiler |
</dd> |
</font></li> |
<dt>PEGASUS_PLATFORM </dt> |
<li><font face="Courier New"><b>Config</b> Pegasus Configuration |
<dd>Identifies the platform to be built. Each supported platform has |
functions</font></li> |
a unique identifier with the following form: <br> |
<li><font face="Courier New"><b>Consumer</b> TBD </font></li> |
<tt><Operating-System>_<Architecture>_<Compiler></tt> |
<li><font face="Courier New"><b>ControlProviders</b> Implementation of Pegasus internal providers |
<p>The following values are tested for the OpenPegasus release:<br> |
</font></li> |
</p> |
<li><font face="Courier New"><b>ExportClient</b> TBD |
|
</font></li> |
|
<li><font face="Courier New"><b>ExportServer</b> TBD |
|
</font></li> |
|
<li><font face="Courier New"><b>Handler</b> TBD </font></li> |
|
<li><font face="Courier New"><b>HandlerService</b> TBD |
|
</font></li> |
|
<li><font face="Courier New"><b>IndicationService</b> TBD |
|
</font></li> |
|
<li><font face="Courier New"><b>Listener</b> TBD </font></li> |
|
<li><font face="Courier New"><b>Protocol</b> Pegasus Client HTTP/XML Protocol Modules |
|
depends </font></li> |
|
<li><font face="Courier New"><b>Provider</b> Pegasus Provider interface functions |
|
</font></li> |
|
<li><font face="Courier New"><b>ProviderManager</b> Provider Manager service that manages providers |
|
</font></li> |
|
<li><font face="Courier New"><b>ProviderManager2</b> Pluggable Provider Manager service. |
|
Today this is not enabled by default It will become the Pegasus |
|
standard provider manager at some time in the future but for now, see |
|
the release notes if you want to enable it.</font></li> |
|
<li><font face="Courier New"><b>Repository</b> Pegasus Repository |
|
Interfaces and Simple Repository tests </font> |
|
<ul> | <ul> |
<li><font face="Courier New">Tests for Repository Functions </font> |
<li>AIX_RS_IBMCXX </li> |
</li> |
<li>HPUX_IA64_ACC </li> |
</ul> |
<li>HPUX_PARISC_ACC </li> |
</li> |
<li>LINUX_IA64_GNU </li> |
<li><font face="Courier New"><b>Security</b> TBD </font></li> |
<li>LINUX_IX86_GNU </li> |
<li><font face="Courier New"><b>Server</b> Pegasus Server Modules |
<li>LINUX_PPC_GNU </li> |
</font></li> |
<li>LINUX_ZSERIES_GNU </li> |
<li><font face="Courier New"><b>WQL</b> TBD |
<li>NSK_NONSTOP_NMCPLUS </li> |
</font></li> |
<li>SOLARIS_SPARC_CC </li> |
</ul> |
<li>SOLARIS_SPARC_GNU </li> |
</li> |
<li>TRU64_ALPHA_DECCXX </li> |
</ul> |
<li>WIN32_IX86_MSVC </li> |
</li> |
<li>ZOS_ZSERIES_IBM </li> |
<li><font face="Courier New"><b>Providers</b> Pegasus test and required providers |
</ul> |
</font> |
<p></p> |
|
</dd> |
|
<dt>PATH </dt> |
|
<dd>Add $PEGASUS_HOME/bin to your path.</dd> |
|
</dl> |
|
<p></p> |
|
<p>Additional configuration: </p> |
<ul> | <ul> |
<li><font face="Courier New"><b>generic</b> TBD this and following IndicationConsumer |
<li>For Unix builds, place $PEGASUS_HOME/lib on your LD_LIBRARY_PATH. |
</font></li> |
|
<li><font face="Courier New"><b>Linux</b> </font></li> |
|
<li><font face="Courier New"><b>ManagedSystem</b> Providers |
|
associated with managing the Pegasus System</font></li> |
|
<li><font face="Courier New"><b>slp</b> - </font></li> |
|
<li><font face="Courier New"><b>statistic</b> - Providers for |
|
Pegasus statistics.</font></li> |
|
<li><font face="Courier New"><b>sample</b> Sample providers for the |
|
major provider types.</font></li> |
|
<li><font face="Courier New"><b>testproviders</b> </font></li> |
|
</ul> |
|
</li> | </li> |
<li><font face="Courier New"><b>Server</b> Pegasus executable build |
<li>For RedHat/SuSE/UL, edit /etc/ld.so.conf and add |
</font></li> |
$PEGASUS_HOME/lib.</li> |
<li><font face="Courier New"><b>slp</b> - TBD</font></li> |
|
<li><font face="Courier New"><b>Standard Includes</b> - TBD</font></li> |
|
<li><font face="Courier New"><b>test</b> - Directory of end-end |
|
tests that are regularly conducted on Pegasus</font></li> |
|
<li><font face="Courier New"><b>tools</b> MU and other utilities written for Pegasus support |
|
</font></li> |
|
<li><font face="Courier New"><b>Unsupported</b> Code that is made available but is not supported or included |
|
in the normal make. </font></li> |
|
<li><font face="Courier New"><b>WMIMapper</b> Pegasus implementation that implements mapping to Microsoft |
|
WMI objects. |
|
|
|
</font></li> |
|
</ul> | </ul> |
|
<p></p> |
|
<p><a name="bld"><strong>Step 4: Build the Pegasus runtime, test |
|
files, test clients and repository</strong></a></p> |
|
<p> |
|
Pegasus includes several make files that enable you to quickly build or |
|
refresh the Pegasus runtime, test files, test client and the |
|
repository. To use these make files, type "make" followed by one of the |
|
supplied targets. </p> |
<p> | <p> |
<font face="Courier New">Pegasus Run Time directory structure (PEGASUS_HOME |
To build Pegasus, run the following commands from the root directory of |
environment variable). Home directory for runtime. All compiler, linker |
the Pegasus distribution: </p> |
documentation creation, etc. are put here. |
<ol> |
</font> |
<li>Enter <tt>make</tt> |
<ul> |
<p>This builds all of Pegasus. </p> |
<li><font face="Courier New"><b>bin</b> - Destination for executable and DLL modules from |
|
Pegasus build. This directory should be make public so that the test functions, |
|
clients, and cimserver can be executed with minimum effort.</font></li> |
|
<li><font face="Courier New"><b>DevManualHTML</b> - HTML output of the Pegasus Manual. |
|
This is only created when the make file for this manual is |
|
executed (doc/DevManual) and then contains the html representing |
|
the document.</font></li> |
|
<li><font face="Courier New"><b>apidochtml</b> - HTML output of |
|
the creation of the public API document. This only exists |
|
when the make file for the api document is executed (see doc/apidoc/Makefile)</font></li> |
|
<li><font face="Courier New"><b>lib</b> - Destination for Pegasus LIB modules |
|
</font></li> |
|
<li><font face="Courier New"><b>log</b> - Standard location for |
|
Pegasus Logs</font></li> |
|
<li><font face="Courier New"><b>obj</b> - Destination for object |
|
modules. Note that today, the trace file is located in the |
|
PEGASUS_HOME directory, not in the log directory if Pegasus |
|
internal tracing is enabled.</font></li> |
|
<li><font face="Courier New"><b>repository</b> - This Directory |
|
contains the created repository </font></li> |
|
</ul> |
|
|
|
<h1> |
|
<a name="Pegasus Installation">Pegasus Installation</a> </h1> |
|
<p> |
|
Pegasus today is provided only as a source distribution. |
|
<p> |
|
To install Pegasus, you must check it out using CVS (Common Version System) |
|
or download a snapshot. You download, compile, and use it. |
|
<p> |
|
For the snapshot, the installation of Pegasus involves expanding the snapshot |
|
distribution files, building the runtime, the test files and test clients, and |
|
building the repository. |
|
<h1> |
|
|
|
<a name="Building Pegasus">Building Pegasus </a> |
|
|
|
</h1> |
|
|
|
<p> |
|
1. Check that you have requisite programs (listed in Pegasus Dependencies). |
|
|
|
These include GNU Make, MU.EXE (if using Windows), Flex, and Bison (Flex |
|
and Bison only required if changes will be made to the MOF compiler or WQL |
|
parser). |
|
<p> |
|
Be sure these are on the path. |
|
|
|
<p> |
|
2. Define the following three environment variables: |
|
<ul> |
|
<li><b>PEGASUS_ROOT</b> - this should be the "pegasus" directory you've pulled from CVS |
|
</li> |
|
<li><b>PEGASUS_HOME</b> - to point to a directory to contain output binary files |
|
(e.g., set it to $HOME/pegasus_home). Then the output will go into |
|
$HOME/pegasus_home/bin and $HOME/pegasus_home/lib |
|
</li> | </li> |
<li><b>PEGASUS_PLATFORM</b> - this must be set to a supported platform identifier. |
<li>Enter <tt>make repository</tt> |
|
<p>This creates the repository, which is needed to serve data. |
|
To create the additional namespaces that represent the test support you |
|
can also execute "make testrepository". </p> |
|
</li> |
|
<li> Enter <tt>make tests</tt> |
|
<p>This executes all the tests included with the Pegasus |
|
distribution, except the client/server tests. The client/server tests |
|
are executed separately from the above because |
|
they require the initiation of separate process for the Pegasus server |
|
and |
|
Pegasus client. To execute these tests, refer to the scripts in |
|
pegasus/mak/BuildMakefile. Refer to the prestarttests and |
|
poststarttests in this file. </p> |
</li> | </li> |
|
</ol> |
|
<p></p> |
|
<p> The following make targets are supported: |
|
</p> |
|
<ul> |
|
<li><default> - Build everything. </li> |
|
<li>clean - Clean out all objects, libs, and executables. </li> |
|
<li>depend - Create the dependencies. </li> |
|
<li>repository - Create the repository in $PEGASUS_HOME/repository </li> |
|
<li>tests - Execute all tests (except client server tests). </li> |
|
<li>rebuild - clean, depend, <default> </li> |
|
<li>world - depend, <default> </li> |
</ul> | </ul> |
<blockquote> |
<p></p> |
<p> |
|
This identifier has the following form: |
|
<p> |
|
<font face="Courier New"> |
|
<Operating-System>_<Architecture>_<Compiler> </font> |
|
<p> |
|
For example (Linux on IA32 platform using the GNU Compiler): |
|
LINUX_IX86_GNU |
|
<p> |
|
For a complete list of platforms supported and platform support keywords, refer to the platform_ make files found in directory |
|
<font face="Courier New">pegasus/mak</font> |
|
|
|
</blockquote> |
|
|
|
<p> |
|
Note: if you plan on doing parallel builds, you might consider setting |
|
PEGASUS_HOME to something like this: |
|
<p> |
|
<font face="Courier New"> |
|
$HOME/pegasus_home_LINUX_IX86_GNU </font> |
|
<p> | <p> |
That way, the output of each build will be placed in its own directory. |
Generally the build commands are as follows: </p> |
<p> |
|
3. Now place $PEGASUS_HOME/bin on your path |
|
<p> and |
|
<p> |
|
|
|
Place $PEGASUS_HOME/lib on your LD_LIBRARY_PATH (for Unix only). |
|
For RedHat/SuSE/UL, edit /etc/ld.so.conf and add $PEGASUS_HOME/lib |
|
<p> |
|
4. Change to the root of the Pegasus distrubution and type "make" |
|
(where make refers to GNU make). |
|
<p> |
|
5. Then create the repository, which is needed to serve data. |
|
"make repository". Note that to create the additional namespaces, etc. |
|
that represent the test support you can also execute "make testrepository:<p> |
|
6. To test the build type "make tests". |
|
The following make targets are supported: |
|
<UL> |
|
<li><default> - Build everything. |
|
<li>clean - Clean out all objects, libs, and executables. |
|
<li>depend - Create the dependencies. |
|
<li>repository - Create the repository in $PEGASUS_HOME/repository |
|
<li>tests - Execute all tests (except client server tests). |
|
<li>rebuild - clean, depend, <default> |
|
<li>world - depend, <default> |
|
</UL> |
|
The Pegasus Client server tests are executed separately from the above because |
|
they require the initiation of separate process for the Pegasus server and |
|
Pegasus client. To execute these tests please refer to the scripts in |
|
pegasus/mak/BuildMakefile - refer to the prestarttests and poststarttests. |
|
<p> |
|
For information on particular installation characteristics, tools, etc. for |
|
each platform see the appropriate sections below: |
|
<p> |
|
Generally the build commands are as follows: |
|
<ol> | <ol> |
<li>There is a Makefile in the Pegasus root directory. Simply executing |
<li>There is a Makefile in the Pegasus root directory. Simply |
make in the Pegasus root directory will make everything. "make rebuild" |
executing make in the Pegasus root directory will make everything. |
will clean and rebuild everything. The "make rebuild" will also populate |
"make rebuild" will clean and rebuild everything. The "make rebuild" |
the repository with the current CIM Schemas. |
will also populate the repository with the current CIM Schemas. </li> |
</li> |
|
<li>To test a fresh release, go to the pegasus root and type | <li>To test a fresh release, go to the pegasus root and type |
"<font face="Courier New">make world</font>". |
"<font face="Courier New">make world</font>". This will build |
This will build dependencies, build binaries, and then run all |
dependencies, build binaries, and then run all tests except the |
tests except the Client/Server tests. |
Client/Server tests. </li> |
</li> |
<li>To execute the basic test suite that is shipped with pegasus |
<li>To execute the basic test suite that is shipped with pegasus type |
type "make tests". This also reinstalls the repository. |
"make tests". This also reinstalls the repository. |
Running "make -s tests" suppresses extraneous output such as the |
Running "make -s tests" suppresses extraneous output such as the |
enter/leave directory messages. </li> |
enter/leave directory messages. |
<li>"make clean" removes all object and library files from the |
</li> |
structure. </li> |
<li>"make clean" removes all object and library files from the structure. |
<li>A new build system has been added to Pegasus where a new CVS |
|
checkout is done, |
</li> |
built, and tests are run. Do it by: "make -f mak/BuildMakefile |
<li>A new build system has been added to Pegasus where a new CVS checkout is |
cleanbuild" </li> |
done, |
|
built, and tests are run. Do it by: "make -f mak/BuildMakefile cleanbuild" |
|
|
|
</li> |
|
</ol> | </ol> |
|
<h2> |
<h1> |
<a name="pop_peg_rep">Populate the Pegasus repository</a> </h2> |
<a name="Populate the Repository">Populating the Pegasus Repository</a> </h1> |
|
|
|
<p> | <p> |
Before using Pegasus you must populate the repository.. The makefile |
Before using Pegasus you must populate the repository. Typically, this |
does it all for you, but in case you are wondering what it does or how to do it |
is done during the buld process when you run the makefile. However, you |
|
can also do it manually after the Pegasus has been built. </p> |
manually: |
|
<ol> | <ol> |
<LI>Register the MOF (Managed Object Format) file describing the skeleton of the |
<li>Register the MOF (Managed Object Format) file describing the |
object. |
skeleton of the object. </li> |
<li>Register a second MOF which only points out which lib*.so file to be loaded |
<li>Register a second MOF which only points out which lib*.so file to |
when a |
be loaded when a specific object is activated. </li> |
specific object is activated. |
|
</ol> | </ol> |
This is done automatically for the providers included in Pegasus by doing: |
<p></p> |
make repository. |
|
<p> | <p> |
The 'make repository' in pegasus/Schemas does three things |
The providers included with Pegasus are automatically entered into the |
Runs MOF compiler (cimmofl) on: |
repository |
-Schema v2.7 |
by running the following command: <tt>make repository</tt> |
Generates the CIM Schema v2.7 in the repository (skeleton of CIM objects) |
</p> |
-PG_InterOp |
|
Internal to Pegasus schema for operating (shutdown, add users, etc) |
|
CIM_Indication’s (SNMP, Events, Alert, Threshold, etc) |
|
-PG_ManagedSystem |
|
Registers included CIM Providers (libOSProvider.so, libDNSProvider.so, … ) |
|
in Pegasus (which are located in src/Providers) |
|
<p> |
|
For more information about using the MOF compiler, refer to user's manual on the |
|
|
|
openpegasus.org. |
|
|
|
<h1> |
|
<a name="Testing a Pegasus Installation">Testing a Pegasus Installation</a></h1> |
|
<p> | <p> |
Pegasus includes an extensive set of test facilities as part of the CVS |
The 'make repository' in pegasus/Schemas does three things: |
enviromentthat can be executed including:<ul> |
</p> |
<li><b>Test Clients</b> - There are several clients that have been built |
<ul> |
specifically to test Pegasus or parts of Pegasus including TestClient, Client, |
<li>Generates the CIM Schema v2.8 in the repository (skeleton of CIM |
CLI, ipinfo, osinfo, WbemEsec, etc. See the src/Clients directory for more |
objects). To do this, it runs the MOF compiler on the CIM schema: <tt>cimmofl |
information. These programs require a server complete with repository to be |
-Schema v2.8</tt> </li> |
running. Note that some of these tests use classes and instances that |
<li>Sets up operations (shutdown, add users, etc) and CIM indications |
are only installed with the "make testrepository" functions including test |
(SNMP, Events, Alert, Threshold, etc) |
namespaces and extra classes and instances in those namespaces and additional |
internal to the Pegasus schema by running the following command: <tt>cimmofl |
providers from the providers/sample and proviers/testproviders directories.</li> |
-PG_InterOp</tt> </li> |
<li><b>Sample and test providers</b> - Test providers exist for the |
<li>Registers included CIM Providers (libOSProvider.so, |
major provider types in the providers/sample directories and the providers/testProviders |
libDNSProvider.so, … ) in Pegasus (which are located in src/Providers) |
directory</li> |
by running: <tt>cimmofl -PG_ManagedSystem</tt> </li> |
<li><b>Unit Tests</b> - Most Pegasus functions include unit tests for the |
</ul> |
functions. These are normally executed with the "make tests" command |
<h2> |
which can be executed at many different levels of the source tree from the top |
<a name="reg_prov">Registering |
level to execute all of the unit tests to individual directories. |
Providers in the Pegasus Environment</a></h2> |
Usually the unit test functions can be found in test directories immediately |
<p> |
below their corresponding source code (i.e common/tests is the unit test |
Pegasus registers providers with a set of provider registration |
functions for the common directory). Unit tests are executed without the |
classes, not using the provider qualifier as is done in most DMTF CIM |
server being operational and normally do not require the existence of a Class |
CIMOM implementations today. This set of classes is close to but not |
repository.</li> |
exactly the same as the current DMTF definition (See the DMTF Interop |
<li><b>An end-to-end Test Suite</b> - the directory "test" contains a set of |
schema, experimental versions starting with 2.6). This will be |
operations tests that cover the major CIM operations. See the make file |
harmonized in the future when the DMTF scheme is moved to final |
TestMakefile in the PEGASUS_ROOT directory to execute these tests. This |
status. </p> |
set of tests executes an extensive set of fixed tests and compares the results |
|
against predefined results.</li> |
|
</ul> |
|
|
|
<h1> |
|
<a name="Registering Providers in the Pegasus Environment">Registering Providers |
|
in the Pegasus Environment</a></h1> |
|
|
|
<p> |
|
Pegasus registers providers with a set of provider registration classes, not |
|
using the provider qualifier as is done in most DMTF CIM CIMOM implementations |
|
today. This set of classes is close to but not exactly the same as the current |
|
DMTF definition (See the DMTF Interop schema, experimental versions starting |
|
with 2.6). This will be harmonized in the future when the DMTF scheme is moved |
|
to final status. </p> |
|
|
|
<p> | <p> |
Registration is performed by defining a MOF for the instances of the | Registration is performed by defining a MOF for the instances of the |
registration classes that represent the porvider module, providers, classes, |
registration classes that represent the porvider module, providers, |
etc. to be registered. The easiest way to create a new registration today |
classes, etc. to be registered. The easiest way to create a new |
is to copy from one of the existing registration MOFs. See the |
registration today is to copy from one of the existing registration |
providers/sample/load directory for examples of several registration instance |
MOFs. See the providers/sample/load directory for examples of |
implementations that do work with Pegasus today.</p> |
several registration instance implementations that do work with Pegasus |
|
today.</p> |
<h1> |
<h2> |
<a name="The MU Utility">The MU Utility </a></h1> |
<a name="bld_rpms">Building RPMs for Pegasus</a> |
|
</h2> |
|
<p> |
|
The source distribution includes a script you can use to create an RPM |
|
for Pegasus. To do this, your environment must meet the following |
|
requirements: |
|
</p> |
|
<ul> |
|
<li>The root directory for Pegasus must be "/Pegasus-1.0" </li> |
|
<li>Your environment variables must be set, as described in <a |
|
href="#set_envt_var">Set evironment variables</a>. </li> |
|
<li>You must be logged in as the root user.</li> |
|
</ul> |
|
<p></p> |
|
<p> |
|
To create the RPMs, run the script <tt>rpmBuild</tt> from the root |
|
directory of the source distribution. For example: <tt>. |
|
/usr/source/pegasus-1.0/rpmBuild</tt> |
|
</p> |
|
<p> |
|
This will result in and RPM file names <tt>pegasus<version |
|
number>.rpm</tt>. |
|
</p> |
|
<p> |
|
<strong>Note</strong>: After you install using the install using the |
|
PRM, you must crate and populate teh repository manually. |
|
</p> |
|
<strong>Question: I'm still working on this procedure (I haven't gotten |
|
it to work yet).<br> |
|
<br> |
|
</strong> |
|
<h2><a name="note_bld_peg_lnx">Notes about |
|
Building |
|
Pegasus on Linux </a></h2> |
|
<p> |
|
Pegasus supports many distributions of Linux. Refer to <a |
|
href="#peg_sup_plat">Pegasus Supported Platforms</a> |
|
for more information. </p> |
|
<p> |
|
To build Pegasus on Linux, ensure that you you have the environment |
|
variables set (PEGASUS_HOME, PEGASUS_ROOT, PEGASUS_PLATFORM. For |
|
32 bit linux, the definition of PEGASUS_PLATFORM is normally |
|
LINUX_IX86_GNU. |
|
</p> |
|
<br> |
|
<h2><a name="bld_peg_win">Notes |
|
on building Pegasus on Windows 2k or Windows XP with Microsoft Visual |
|
C++ </a></h2> |
|
<p> |
|
Use of Windows 2000 SP3 or later is recommended. Pegasus is |
|
regularly tested on both Windows 2000 and Windows XP using the |
|
Microsoft compilers.</p> |
|
<p>Today we build Pegasus on Windows using a set of make files |
|
contained |
|
in the source distribution, the Microsoft compilers (DevStudio 5.x is |
|
not supported, Visual Studio 6.0, SP5 is supported) and the GNUMAKE |
|
make utility. Note that you MUST have the Pegasus <a |
|
href="#mu_utility">mu.exe </a>utility compiled and available |
|
before trying to compile Pegasus on the normal windows platform. The |
|
following is the basic setup steps for the environment. |
|
</p> |
|
<p>Setup the environment variables and path for the Micrososft Visual C |
|
compiler. |
|
Typically this can be done by running the VCVARS32.BAT file supplied |
|
with Microsoft Visual C++. (contained in the same directory as cl.exe). |
|
</p> |
|
<p>For Windows, try the following for an example environment: </p> |
|
<blockquote> |
|
<pre>REM call the standard Microsoft .bat for VC 6 setup. <br>call 'C:/Program Files\Microsoft Visual Studio\VC98\Bin\Vcvars32.bat' <br>REM Set debug to something if you want compile in debug mode <br>set PEGASUS_DEBUG=true <br>REM set PEGASUS_ROOT to top of source tree <br>set PEGASUS_ROOT=C:/cimom/pegasus (Note: <span |
|
class="norm">The '/' characters are intentional and required by the Pegasus build system)</span><br>REM set PEGASUS_HOME to where you want repository and executables<br>set PEGASUS_HOME=%PEGASUS_ROOT% <br>REM setup the path to the runtime files. <br>set path=%path%;%PEGASUS_HOME%\bin <br></pre> |
|
</blockquote> |
|
<h3> |
|
<a name="mu_utility">The MU Utility </a></h3> |
<p> | <p> |
In order to provide a consistent build structure across multiple platforms, we |
In order to provide a consistent build structure across multiple |
developed a small utility to provide a consistent set of small utilities |
platforms, we |
across these platforms. The MU utilityis a simple utility that contains many |
developed a small utility to provide a consistent set of small |
|
utilities |
|
across these platforms. The MU utilityis a simple utility that contains |
|
many |
commands. For example: | commands. For example: |
|
</p> |
<p> |
<p><font face="Courier New"> |
<font face="Courier New"> |
|
C:\> mu rm myfile.cpp yourfile.cpp </font> | C:\> mu rm myfile.cpp yourfile.cpp </font> |
|
</p> |
<p> |
<p>You may type "mu" to get a list of valid commands. Here are some |
You may type "mu" to get a list of valid commands. Here are some |
|
of them: | of them: |
|
</p> |
<p> |
<p> |
|
|
rm, rmdirhier, mkdirhier, echo, touch, pwd, copy, move, compare depend | rm, rmdirhier, mkdirhier, echo, touch, pwd, copy, move, compare depend |
|
</p> |
<p> |
<p>The MU utility supports globing (expansion of wildcards) so |
The MU utility supports globing (expansion of wildcards) so |
|
you can do things like this: | you can do things like this: |
<p> |
</p> |
|
<p><font face="Courier New"> |
<font face="Courier New"> |
|
|
|
C:\> mu rm *.obj *.exe </font> | C:\> mu rm *.obj *.exe </font> |
<p> |
</p> |
MU is required to build under the Windows environment. MU is available as part |
<p>MU is required to build under the Windows environment. MU is |
of the distribution of Pegasus. |
available as part |
|
of the distribution of Pegasus.<br> |
<h1> |
</p> |
<a name="Notes about Building Pegasus on Linux">Notes about Building Pegasus on |
<h2><a name="note_bld_peg_ssl">Notes about |
Linux </a></h1> |
Building Pegasus with SSL |
<p> |
</a></h2> |
No problem. Just make sure you have the environment variables set (PEASUS_HOME, |
<p> |
PEGASUS_ROOT, PEGASUS_PLATFORM. For 32 bit linux, the defintion of |
To build with SSL you need the OpenSSL libraries and header files. They |
PEGASUS_PLATFORM is normally LINUX_IX86_GNU. |
are NOT distributed with Pegasus. Make sure you have them in a standard |
|
directory so Pegasus can find them. If that's not |
<h1><a name="Notes about Building Pegasus with SSL">Notes about Building Pegasus with SSL |
the case, set the environment variable OPENSSL_HOME= to point where |
</a></h1> |
your OpenSSL |
<p> |
|
To build with SSL you need the OpenSSL libraries and header files. They are NOT |
|
distributed with Pegasus. Make sure |
|
you have them in a standard directory so Pegasus can find them. If that's not |
|
|
|
the case, set the environment variable OPENSSL_HOME= to point where your |
|
OpenSSL |
|
installation is. | installation is. |
<p> |
</p> |
Also have the PEGASUS_HAS_SSL=yes variable set. Then just run 'make' in Pegasus |
<p>Also have the PEGASUS_HAS_SSL=yes variable set. Then just run 'make' |
directory and you will have Pegasus with SSL enabled. See section "Creating SSL |
in Pegasus |
|
directory and you will have Pegasus with SSL enabled. See "Creating SSL |
certificates" for more information of how to use SSL. |
certificates" below for more information on how to use SSL. |
|
</p> |
<h1> |
<h3><a name="crt_ssl_cert">Creating SSL certifications </a></h3> |
<a name="Building Pegasus on Windows 2000 or Windows XP With Microsoft Visual C++"> |
<p>Type these commands in your shell to create the SSL certifications. |
Building Pegasus on Windows 2k or Windows XP with Microsoft Visual C++ </a></h1> |
The PEGASUS_ROOT and PEGASUS_HOME have to be set to your respective |
|
installation and source directory.<br> |
<p> |
<span style="color: rgb(0, 0, 0);">Set the sslKeyFilePath to |
Use of Windows 2000 SP3 or later is recommended. Pegasus is regularly |
key.pem. Set the sslCertificateFilePath to cert.pem. To |
tested on both Windows 2000 and Windows XP using the Microsoft compilers.<p> |
create a client truststore to validate the server against, copy the |
Today we build Pegasus on Windows using a set of make files contained |
server's certificate into the client truststore, client.pem.</span><br> |
in the source distribution, the Microsoft compilers (DevStudio 5.x is not |
</p> |
supported, Visual Studio 6.0, SP5 is supported) and the GNUMAKE make utility. |
<pre |
Note that you MUST have the Pegasus <a href="#The MU Utility">mu.exe </a>utility |
style="font-style: italic; font-family: courier new,courier,monospace; margin-left: 40px;"><small>CN="Common Name"<br>EMAIL="test@email.address"<br>HOSTNAME=`uname -n`<br>sed -e "s/$CN/$HOSTNAME/" \<br>-e "s/$EMAIL/root@$HOSTNAME/" $PEGASUS_ROOT/ssl.cnf \<br>> $PEGASUS_HOME/ssl.cnf<br>chmod 644 $PEGASUS_HOME/ssl.cnf<br>chown bin $PEGASUS_HOME/ssl.cnf<br>chgrp bin $PEGASUS_HOME/ssl.cnf<br><br>/usr/bin/openssl req -x509 -days 365 -newkey rsa:512 \<br>-nodes -config $PEGASUS_HOME/ssl.cnf \<br>-keyout $PEGASUS_HOME/key.pem -out $PEGASUS_HOME/cert.pem <br><br>cp $PEGASUS_HOME/cert.pem $PEGASUS_HOME/client.pem</small></pre> |
compiled and available before trying to compile Pegasus on the normal windows |
<p style="color: rgb(0, 0, 0);">Note: key.pem is |
platform. The |
sslKeyFilePath. cert.pem is sslCertificateFilePath</p> |
|
<p></p> |
following is the basic setup steps for the environment. |
<h1> |
<p> |
<a name="test">Testing a Pegasus Installation</a></h1> |
|
<p> |
Setup the environment variables and path for the Micrososft Visual C compiler. |
Pegasus includes an extensive set of test facilities as part of the CVS |
|
enviroment, including: |
Typically this can be done by running the VCVARS32.BAT file supplied with |
</p> |
Microsoft Visual C++. (contained in the same directory as cl.exe). |
<ul> |
<p> |
<li><b>Test Clients</b> - There are several clients that have been |
For Windows, try the following for an example environment: |
built specifically to test Pegasus, or parts of Pegasus, including |
<blockquote> |
TestClient, Client, CLI, ipinfo, osinfo, WbemEsec, etc. See the |
<pre>REM call the standard Microsoft .bat for VC 6 setup. |
src/Clients directory for more information. These programs require a |
call 'C:/Program Files/Microsoft Visual Studio/VC98/Bin/Vcvars32.bat' |
server complete with repository to be running. Note that some of |
REM Set debug to something if you want compile in debug mode |
these tests use classes and instances that are only installed with the |
set PEGASUS_DEBUG=true |
"make testrepository" functions including test namespaces and extra |
REM set PEGASUS_ROOT to top of source tree |
classes and instances in those namespaces and additional providers from |
set PEGASUS_ROOT=C:/cimom/pegasus |
the providers/sample and proviers/testproviders directories. </li> |
REM set PEGASUS_HOME to where you want repository and executables |
<li><b>Sample and test providers</b> - Test providers exist for |
set PEGASUS_HOME=%PEGASUS_ROOT% |
the major provider types in the providers/sample directories and the |
REM setup the path to the runtime files. |
providers/testProviders directory </li> |
set path=%path%;%PEGASUS_HOME%/bin |
<li><b>Unit Tests</b> - Most Pegasus functions include unit tests for |
</pre> |
the functions. These are normally executed with the "make tests" |
</blockquote><h1><a name="Installing the Pegasus HTML Test Client">Installing the Pegasus HTML Test Client</a></h1><p> |
command which can be executed at many different levels of the source |
This is a separate test tool that allows Pegasus requests to be initiated from |
tree from the top level to execute all of the unit tests to individual |
any WEB browser and that uses a WEB browser, CGI scripts and HTML pages for |
directories. Usually the unit test functions can be found in test |
|
directories immediately below their corresponding source code |
|
(i.e common/tests is the unit test functions for the common |
|
directory). Unit tests are executed without the server being |
|
operational and normally do not require the existence of a Class |
|
repository. </li> |
|
<li><b>An end-to-end Test Suite</b> - the directory "test" contains a |
|
set of operations tests that cover the major CIM operations. See |
|
the make file TestMakefile in the PEGASUS_ROOT directory to execute |
|
these tests. This set of tests executes an extensive set of fixed |
|
tests and compares the results against predefined results.</li> |
|
</ul> |
|
<p></p> |
|
<h2><a name="inst_peg_html">Installing the |
|
Pegasus HTML Test Client</a></h2> |
|
<p>This is a separate test tool that allows Pegasus requests to be |
|
initiated from |
|
any WEB browser and that uses a WEB browser, CGI scripts and HTML pages |
|
for |
the formatting and connections. It requires a WEB server, etc. The | the formatting and connections. It requires a WEB server, etc. The |
instructions for setting up this environment are maintained in a separate readme in the CGI directory. <h1><a name="Development with Pegasus and Pegasus Tools">Development with Pegasus and Pegasus Tools</a></h1><p> |
instructions for setting up this environment are maintained in a |
ATTN: This section needs to be completed. It should reference the more |
separate readme in the CGI directory. </p> |
complete documentation |
<h2><a name="test_icu">Testing with ICU enabled</a></h2> |
ATTN: Write about providers? <h1><a name="Commands">Commands</a></h1><p> |
<p>ICU (International Components for Unicode) refers to the set of |
The manpages for each of the commands are in rpm/manLinux/man1.Z directory (on |
libraries that |
CVS) <p> |
Pegasus uses to run globalized. For example: these libraries are used |
To see simple help for each of the commands, use the "-h" flag. <blockquote><pre>Examples: |
to |
bin/cimserver –s (Shuts it down) |
load messages in different languages, format currency and numbers |
bin/cimserver traceLevel=4 traceComponents=ALL (starts server with config flags) |
according to |
bin/cimprovider –l –s (lists providers and their status) |
a specific locale etc. In order to enable globalization in Pegasus, |
bin/cimprovider –e –m OperatingSystemModule (enables the OperatingSystem provider) |
Pegasus |
bin/cimuser –a –u guest –w ThePassword |
must be built with ICU enabled, ie. the right environment variables |
bin/cimuser –l (lists the users) |
must be |
bin/tomof CIM_Config (extract CIM_Config from repository and present it in MOF type) |
set prior to running "make". Refer to the GlobalizationHOWTO.htm in the |
</pre> |
docs |
</blockquote><h1><a name="Creating SSL certifications">Creating SSL certifications </a></h1><p> |
directory for details.<br> |
Type these commands in your shell to create the SSL certifications. The PEGASUS_ROOT and PEGASUS_HOME have to be set to your respective installation and source |
</p> |
directory. <blockquote><pre>CN="Common Name" |
<p> When users run "make poststarttests" |
EMAIL="test@email.address" |
to verify the integrity of a Pegasus download, a series of tests are |
HOSTNAME=`uname -n` |
run that |
sed -e "s/$CN/$HOSTNAME/" \ |
require the cimserver to be running. These tests currently depend on |
-e "s/$EMAIL/root@$HOSTNAME/" $PEGASUS_ROOT/ssl.cnf \ |
specific |
> $PEGASUS_HOME/ssl.cnf |
messages returned from the server. When ICU is enabled, all messages |
chmod 644 $PEGASUS_HOME/ssl.cnf |
come from the resource bundles and these usually do not match the |
chown bin $PEGASUS_HOME/ssl.cnf |
hardcoded default messages within Pegasus. These hardcoded default |
chgrp bin $PEGASUS_HOME/ssl.cnf |
messages are what the various test programs expect in order to complete |
|
|
/usr/bin/openssl req -x509 -days 365 -newkey rsa:512 \ |
|
-nodes -config $PEGASUS_HOME/ssl.cnf \ |
|
-keyout $PEGASUS_HOME/key.pem -out $PEGASUS_HOME/cert.pem |
|
|
|
cat $PEGASUS_HOME/key.pem $PEGASUS_HOME/cert.pem > $PEGASUS_HOME/server.pem |
|
rm $PEGASUS_HOME/key.pem $PEGASUS_HOME/cert.pem |
|
cp $PEGASUS_HOME/cert.pem $PEGASUS_HOME/client.pem |
|
</pre></blockquote><h1><a name="Testing with ICU enabled">Testing with ICU enabled</a></h1><p> |
|
ICU (International Components for Unicode) refers to the set of libraries that |
|
Pegasus uses to run globalized. For example: these libraries are used to |
|
load messages in different languages, format currency and numbers according to |
|
a specific locale etc. In order to enable globalization in Pegasus, Pegasus |
|
must be built with ICU enabled, ie. the right environment variables must be |
|
set prior to running "make". Refer to the GlobalizationHOWTO.htm in the docs |
|
directory for details. That said, when users run "make poststarttests" |
|
to verify the integrity of a Pegasus download, a series of tests are run that |
|
|
|
require the cimserver to be running. These tests currently depend on specific |
|
|
|
messages returned from the server. When ICU is enabled, all messages come |
|
from the resource bundles and these usually do not match the hardcoded default messages within Pegasus. These hardcoded default messages |
|
are what the various test programs expect in order to complete |
|
successfully. If the ICU enabled server is started without | successfully. If the ICU enabled server is started without |
disabling message loading from the bundles, "make poststartests" will fail. |
disabling message loading from the bundles, "make poststartests" will |
In order to run "make poststarttests" successfully with ICU enabled, an |
fail. |
environment variable called PEGASUS_USE_DEFAULT_MESSAGES must exist prior to |
In order to run "make poststarttests" successfully with ICU enabled, an |
starting the server. Once this is defined, when the cimserver starts, all |
environment variable called PEGASUS_USE_DEFAULT_MESSAGES must exist |
messages generated will be the default hardcoded messages. This will enable |
prior to |
"make poststarttests" to complete successfully. Once "make poststarttests" is |
starting the server. Once this is defined, when the cimserver starts, |
complete, you should stop the cimserver and then undefine PEGASUS_USE_DEFAULT_MESSAGES. |
all |
If this variable is left defined, Pegasus will not be able to load messages |
messages generated will be the default hardcoded messages. This will |
using ICU resource bundles. <h1><a name="Pegasus Documentation">Pegasus Documentation</a></h1><p> |
enable |
The documentation is currently in preparation. Much of Pegasus is |
"make poststarttests" to complete successfully. Once "make |
documented in the PEGASUS PEPs which are the basis for approval of Pegasus |
poststarttests" is |
functioanlity, changes, plans, etc. These documents are openly available |
complete, you should stop the cimserver and then undefine |
on the PEGASUS web site. The preliminary documentation |
PEGASUS_USE_DEFAULT_MESSAGES. If this variable is left defined, Pegasus |
is not provided with this release. The current documentation is maintained both as a manual created |
will not be able to load messages |
under the tool DOC++ in the runtime subdirectory manual/html (see doc/devManual |
using ICU resource bundles.<br> |
to create), as an api document also creatable from the source tree (see doc/apidoc) |
</p> |
and as other miscellaneous documentation in the doc directory. Also there is a |
<p><span class="norm"></span><font style="color: rgb(0, 0, 0);">When |
set of release notes. Normally the release notes for the current release are |
running the make tests command with ICU enabled, the PEGASUS_MSG_HOME |
available in the root source directory of CVS.<p> |
environment variable must be set to the home directory where the ICU |
Note that the Pegasus WEB site at The Open Group will be the source of most |
resource bundles are built. By default the resource bundles are built |
documentation in the future and today is the source of most discussion and |
into directories below PEGASUS_HOME/msg, so that should be the setting |
design documentation. <h1><a name="Participate!">Participate!</a></h1><p> |
for PEGASUS_MSG_HOME.<br> |
We are looking for people who want to join the Pegasus work group and |
</font></p> |
contribute to effort of getting this Pegasus off the ground. Please join |
<p><font style="color: rgb(0, 0, 0);">-------------------------------------------------------------------------------------------------------------------------------------<br> |
the mailing list by visiting www.openpegasus.org, and click on Mailing Lists. |
</font></p> |
</p> |
<p><i><font size="2">Copyright (c) 2004 EMC Corporation; |
|
Hewlett-Packard Development Company, L.P.; IBM Corp.; The Open Group; |
|
VERITAS Software Corporation</font><br> |
|
<br> |
|
<font size="1">Permission is hereby granted, free of charge, to any |
|
person obtaining a copy of this software and associated |
|
documentation files (the "Software"), to deal in the Software without |
|
restriction, including without limitation the rights to use, copy, |
|
modify, merge, publish, distribute, sublicense, and/or sell copies of |
|
the Software, and to permit persons to whom the Software is furnished |
|
to do so, subject to the following conditions:</font><br> |
|
<font size="2"><br> |
|
</font> |
|
<font size="1">THE ABOVE COPYRIGHT NOTICE AND THIS PERMISSION NOTICE |
|
SHALL BE INCLUDED IN ALL COPIES OR SUBSTANTIAL PORTIONS OF THE |
|
SOFTWARE. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF |
|
ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE |
|
WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND |
|
NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE |
|
LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION |
|
OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION |
|
WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.<br> |
|
</font></i></p> |
|
<p><i><font size="1"><br style="font-family: arial;"> |
|
<big><big><span style="font-family: arial;">------------------------End |
|
of |
|
Document-------------------------<br> |
|
</span></big></big></font></i></p> |
|
<p><span style="color: rgb(0, 0, 0);"></span> </p> |
</body> | </body> |
|
|
</html> | </html> |