version 1.11, 2006/02/18 03:27:11
|
version 1.12, 2006/03/28 19:56:18
|
|
|
//%2006//////////////////////////////////////////////////////////////////////// |
|
// |
|
// Copyright (c) 2000, 2001, 2002 BMC Software; Hewlett-Packard Development |
|
// Company, L.P.; IBM Corp.; The Open Group; Tivoli Systems. |
|
// Copyright (c) 2003 BMC Software; Hewlett-Packard Development Company, L.P.; |
|
// IBM Corp.; EMC Corporation, The Open Group. |
|
// Copyright (c) 2004 BMC Software; Hewlett-Packard Development Company, L.P.; |
|
// IBM Corp.; EMC Corporation; VERITAS Software Corporation; The Open Group. |
|
// Copyright (c) 2005 Hewlett-Packard Development Company, L.P.; IBM Corp.; |
|
// EMC Corporation; VERITAS Software Corporation; The Open Group. |
|
// Copyright (c) 2006 Hewlett-Packard Development Company, L.P.; IBM Corp.; |
|
// EMC Corporation; Symantec Corporation; The Open Group. |
|
// |
|
// 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: |
|
// |
|
// 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. |
|
// |
|
//============================================================================== |
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> | <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> |
<html> |
<html><head> |
<head> |
|
<meta name="GENERATOR" content="Microsoft FrontPage 5.0"> |
|
|
<link rel="stylesheet" href="PEP_251_Draft_251_Readme_Version_1_2_files/info1margins.css"> |
|
|
|
<meta name="GENERATOR" content="Microsoft FrontPage 6.0"> |
<meta name="ProgId" content="FrontPage.Editor.Document"> | <meta name="ProgId" content="FrontPage.Editor.Document"> |
<meta http-equiv="Content-Type" |
<meta http-equiv="Content-Type" content="text/html; charset=windows-1252"><title>OpenPegasus</title> |
content="text/html; charset=windows-1252"> |
|
<title>OpenPegasus</title> |
<script language="javascript" src="PEP_251_Draft_251_Readme_Version_1_2_files/js.js"></script></head><body> |
</head> |
|
<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: 0pt; margin-bottom: 0pt;"><b>PEP #:</b> 235<br> |
<p style="margin-top: 0pt; margin-bottom: 0pt;"><b>PEP #:</b> 251<br> |
</p> | </p> |
|
<p style="margin-top: 0pt; margin-bottom: 0pt;"> </p> |
<p style="margin-top: 0pt; margin-bottom: 0pt;"><b>Title: </b>OpenPegasus | <p style="margin-top: 0pt; margin-bottom: 0pt;"><b>Title: </b>OpenPegasus |
Version 2.5 Release Readme file</p> |
Release 2.5.1 Readme file</p> |
<p style="margin-top: 0pt; margin-bottom: 0pt;"><b>Version: </b><span |
<p style="margin-top: 0pt; margin-bottom: 0pt;"> </p> |
style="color: rgb(0, 0, 0);">1.4<br> |
<p style="margin-top: 0pt; margin-bottom: 0pt;"><b>Version: </b><span style="color: rgb(0, 0, 0);"> |
|
1.<br> |
</span></p> | </span></p> |
<p style="margin-top: 0pt; margin-bottom: 0pt;"><b>Created:</b> 6 Sept |
<p style="margin-top: 0pt; margin-bottom: 0pt;"><b>Created:</b> 20th March 2006</p> |
2005</p> |
<p style="margin-top: 0pt; margin-bottom: 0pt;"> </p> |
<p style="margin-top: 0pt; margin-bottom: 0pt;"><b>Authors: </b>Warren |
<p style="margin-top: 0pt; margin-bottom: 0pt;"><b>Authors: </b>Martin Kirk<br> |
Grunbok<br> |
</p> |
</p> |
<p style="margin-top: 0pt; margin-bottom: 0pt;"> </p> |
<p style="margin-top: 0pt; margin-bottom: 0pt;"><b>Status: </b>draft</p> |
<p style="margin-top: 0pt; margin-bottom: 0pt;"><b>Status: </b>Draft</p> |
|
<p style="margin-top: 0pt; margin-bottom: 0pt;"> </p> |
<p style="margin-top: 0pt; margin-bottom: 0pt;"><b>Version History:</b></p> | <p style="margin-top: 0pt; margin-bottom: 0pt;"><b>Version History:</b></p> |
<table bordercolordark="#666666" bordercolorlight="#cccccc" |
<table bordercolordark="#666666" bordercolorlight="#cccccc" style="font-family: Arial;" border="1" cellspacing="1" width="100%"> |
style="font-family: Arial;" border="1" cellspacing="1" width="100%"> |
|
<tbody> | <tbody> |
<tr> | <tr> |
<th bgcolor="#cae6ca">Version</th> | <th bgcolor="#cae6ca">Version</th> |
|
|
</tr> | </tr> |
<tr> | <tr> |
<td align="center">1.0</td> | <td align="center">1.0</td> |
<td align="center">5, Sept 2005</td> |
<td align="center">March 20th 2006</td> |
<td align="center">Warren Grunbok<br> |
<td align="center">Martin Kirk</td> |
</td> |
<td>First draft, basically unchanged from 2.5 ReadMe except for version |
<td>Initial draft<br> |
numbers and typos</td> |
</td> |
|
</tr> | </tr> |
<tr> | <tr> |
<td style="vertical-align: top; text-align: center;">1.1<br> |
<td style="vertical-align: top;" align="center">1.1</td> |
</td> |
<td style="vertical-align: top; text-align: center;">March 23rd 2006</td> |
<td style="vertical-align: top; text-align: center;"> 13, |
<td style="vertical-align: top; text-align: center;">Martin Kirk</td> |
Sept 2005<br> |
<td style="vertical-align: top; text-align: center;"> |
</td> |
<p style="text-align: left;">Draft for ballot incorporating draft 1.0 |
<td style="vertical-align: top; text-align: center;">Warren |
comments.</p></td> |
Grunbok/Roger Kumpf<br> |
|
</td> |
|
<td style="vertical-align: top; text-align: center;">Updates |
|
based on Architecture team review<br> |
|
</td> |
|
</tr> | </tr> |
<tr> | <tr> |
<td style="vertical-align: top;">1.2<br> |
<td style="vertical-align: top;" align="center">1.2</td> |
</td> |
<td style="vertical-align: top;" align="center">March 26th 2006</td> |
<td style="vertical-align: top;">22, Sept 2005<br> |
<td style="vertical-align: top;" align="center">Martin Kirk</td> |
</td> |
<td style="vertical-align: top;">Draft for Steering Committee approval.</td> |
<td style="vertical-align: top;">Warren Grunbok<br> |
|
</td> |
|
<td style="vertical-align: top;">Updates from posted comments to |
|
1.1<br> |
|
</td> |
|
</tr> | </tr> |
<tr> | <tr> |
<td style="vertical-align: top; color: rgb(0, 0, 0);">1.3<br> |
<td style="vertical-align: top; color: rgb(0, 0, 0);" align="center"> </td> |
</td> |
<td style="vertical-align: top; color: rgb(0, 0, 0);"> </td> |
<td style="vertical-align: top; color: rgb(0, 0, 0);">22,Sept 2005<br> |
<td style="vertical-align: top; color: rgb(0, 0, 0);"> </td> |
</td> |
<td style="vertical-align: top; color: rgb(0, 0, 0);"> </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);">changed _ |
|
to - <br> |
|
</td> |
|
</tr> | </tr> |
<tr> | <tr> |
<td style="vertical-align: top;">1.4<br> |
<td style="vertical-align: top;" align="center"> </td> |
</td> |
<td style="vertical-align: top;"> </td> |
<td style="vertical-align: top;">26, Sept 2005<br> |
<td style="vertical-align: top;"> </td> |
</td> |
<td style="vertical-align: top;"> </td> |
<td style="vertical-align: top;">Warren Grunbok/Dave Sudlik<br> |
|
</td> |
|
<td style="vertical-align: top;">Cleanup on example lists<br> |
|
</td> |
|
</tr> | </tr> |
</tbody> | </tbody> |
</table> | </table> |
<hr> | <hr> |
<p><b>Abstract:</b> Installation, build, operation information on | <p><b>Abstract:</b> Installation, build, operation information on |
the OpenPegasus Version 2.5.0 Release. Note that if this readme |
the OpenPegasus Version 2.5.1 Release. Note that if this readme |
conflicts with the documentation in the release notes or interface | conflicts with the documentation in the release notes or interface |
definition documents for a particular release, those documents should | definition documents for a particular release, those documents should |
be considered authorative. This is a simplified overview to act as an |
be considered authoritative. This is a simplified overview to act as an |
introduction to OpenPegasus.</p> | introduction to OpenPegasus.</p> |
<hr> | <hr> |
<p align="center"><b><font size="5">OpenPegasus - A Manageability | <p align="center"><b><font size="5">OpenPegasus - A Manageability |
|
|
DMTF CIM objects written in C++ | DMTF CIM objects written in C++ |
and hosted by The Open Group </p> | and hosted by The Open Group </p> |
<p align="left"> | <p align="left"> |
<b>STATUS:</b> Revised Sept 2005 for Pegasus release version |
<b>STATUS:</b> Revised March 2006 for Pegasus release version |
2.5.0 |
2.5.1 |
- Draft<br> | - Draft<br> |
</p> | </p> |
<a href="#Overview">Overview</a> | <a href="#Overview">Overview</a> |
<blockquote style="margin-top: 0pt; margin-bottom: 0pt;"> <a |
<blockquote style="margin-top: 0pt; margin-bottom: 0pt;"> |
href="#avail_of_peg">Availability of Pegasus</a><br> |
|
<a href="#peg_sup_plat">Pegasus Supported Platforms</a><br> | <a href="#peg_sup_plat">Pegasus Supported Platforms</a><br> |
<a href="#peg_dep">Pegasus Dependencies</a><br> |
<a href="#cmnd">Commands</a><br> |
<a href="#peg_dir_struc"></a><a href="#cmnd">Commands</a><br> |
|
<a href="#docs">Documentation</a><br> | <a href="#docs">Documentation</a><br> |
<a href="#part">How to Participate</a><br> | <a href="#part">How to Participate</a><br> |
</blockquote> | </blockquote> |
<a href="#inst_peg">Install Pegasus</a> |
<a href="#inst_peg">Installing Pegasus</a> |
<blockquote style="margin-top: 0pt; margin-bottom: 0pt;"><a |
<blockquote style="margin-top: 0pt; margin-bottom: 0pt;"><a href="#download"> |
href="#download">Download or checkout Pegasus</a><br> |
Obtain Pegasus in Source Code or Binary Executable Format</a><br> |
<a href="#vfy_req_sw">Verify that you have the required |
<a href="#peg_dep">Verify Dependencies</a><br> |
software</a><br> |
<a href="#set_envt_var">Set the environment variables</a></blockquote> |
<a href="#set_envt_var">Set the environment variables</a><br> |
<a href="#build_peg">Building Pegasus</a><blockquote style="margin-top: 0pt; margin-bottom: 0pt;"> |
<a href="#bld">Build the Pegasus runtime, test files, test clients, |
<a href="#note_bld_peg_lnx">Building Pegasus on Linux</a><br> |
and repository</a><br> |
<a href="#note_bld_peg_ssl">Building Pegasus with SSL</a><br> |
<a href="#pop_peg_rep">Populate the Pegasus repository</a><br> |
<a href="#bld_peg_win">Building Pegasus on Windows 2000 or Windows XP With Microsoft Visual C++</a><br> |
<a href="#reg_prov">Register providers in the Pegasus environment</a><br> |
<blockquote style="margin-top: 0pt; margin-bottom: 0pt;"> <a href="#mu_utility">The MU Utility</a><br> |
<a href="#note_bld_peg_lnx">Notes |
|
about Building Pegasus on Linux</a><br> |
|
<a href="#note_bld_peg_ssl">Notes on building Pegasus with SSL</a><br> |
|
<a href="#bld_peg_win">Building |
|
Pegasus on Windows 2000 or Windows XP With Microsoft Visual C++</a><br> |
|
<blockquote style="margin-top: 0pt; margin-bottom: 0pt;"> <a |
|
href="#mu_utility">The MU Utility</a><br> |
|
</blockquote> | </blockquote> |
</blockquote> | </blockquote> |
|
<a href="#pop_peg_rep">Populate the Pegasus repository</a><br> |
|
<a href="#reg_prov">Register providers in the Pegasus environment</a><br> |
<a href="#test">Test the Pegasus installation</a><br> | <a href="#test">Test the Pegasus installation</a><br> |
<blockquote style="margin-top: 0pt; margin-bottom: 0pt;"> <a |
<blockquote style="margin-top: 0pt; margin-bottom: 0pt;"> <a href="#test_icu">Testing with ICU enabled</a></blockquote> |
href="#test_icu">Testing with ICU enabled</a><br> |
<a href="#sec0">Security Considerations</a><br> |
</blockquote> |
|
<hr> | <hr> |
<h1><a name="Overview">Overview</a> </h1> | <h1><a name="Overview">Overview</a> </h1> |
<b>OpenPegasus (also referred to as Pegasus):</b> | <b>OpenPegasus (also referred to as Pegasus):</b> |
|
|
includes class and instance repositories and interfaces for creating | includes class and instance repositories and interfaces for creating |
CIM | CIM |
Providers and CIM Clients.</li> | Providers and CIM Clients.</li> |
<li>Provider interfaces so that providers may be build in multiple |
<li>Provider interfaces so that providers may be developed in multiple |
languages (i.e. | languages (i.e. |
C++, C, Java).</li> | C++, C, Java).</li> |
<li>A number of CIM providers.</li> |
<li>A number of CIM clients and providers for basic instrumentation.</li> |
<li>A mof compiler.</li> |
<li>A number of CIM server administration commands.</li> |
<li>A number of CIM CLients to provide usage examples, CIMServer |
<li>A MOF compiler.</li> |
test functions, |
<li>A number of sample CIM clients and providers to provide usage examples,</li> |
and administration functions.</li> |
<li>CIM server test functions providing both unit tests and end-to-end |
|
system tests.</li> |
<li>More complete information on the exact functions | <li>More complete information on the exact functions |
and their functional state is available from the release notes for each | and their functional state is available from the release notes for each |
OpenPegasus release.</li> | OpenPegasus release.</li> |
</ol> | </ol> |
OpenPegasus is open source and is covered under the MIT open-source | OpenPegasus is open source and is covered under the MIT open-source |
license. | license. |
<p>OpenPegasus is being developed and maintained under the auspices of |
OpenPegasus is being developed and maintained under the auspices of The Open |
The |
Group. OpenPegasus is maintained under the license defined in <font style="color: rgb(0, 0, 0);">pegasus/doc/license.txt</font>. |
Open |
|
Group. OpenPegasus is maintained under the license defined in the |
|
doc |
|
directory of this release. The specific file is: <font |
|
style="color: rgb(0, 0, 0);">pegasus/doc/license.txt</font>. |
|
This licensing is intended to support as | This licensing is intended to support as |
wide a | wide a |
distribution as possible with minimal demands on the users. |
distribution as possible with minimal demands on the users.<br> |
</p> |
|
<p>More information on this project, access to the CVS, and |
|
documentation on |
|
Pegasus are available from the OpenGroup WEB site. |
|
</p> |
|
<p> <a target="blank" |
|
href="http://www.openpegasus.org/">http://www.openpegasus.org</a></p> |
|
<h2><a name="avail_of_peg">Availability of Pegasus</a></h2> |
|
<h2></h2> |
|
<h2></h2> |
|
<ol> |
|
Pegasus can be obtained via any of the following:<br> |
|
<ol> |
|
<li>Released tarballs (see <a |
|
href="http://www.openpegasus.org/protected/page.tpl?CALLER=index.tpl&ggid=392">Relase |
|
tarballs link</a>)</li> |
|
<li>CVS (See <a |
|
href="http://www.openpegasus.org/protected/page.tpl?CALLER=index.tpl&ggid=667">CVS |
|
code repository</a> for |
|
more information.)</li> |
|
<li>Linux RPMs. See |
|
(<a |
|
href="http://www.openpegasus.org/protected/page.tpl?CALLER=index.tpl&ggid=667">RPM |
|
link</a> for |
|
more information |
|
)</li> |
|
</ol> |
|
</ol> |
|
<p>NOTE: The Linux RPM reference is for 2.4.1 because that is all we |
|
have. We |
|
need a general page to get to the RPMs, not one per release. |
|
</p> |
|
<p>Pegasus is distributed as open source under the MIT open-source |
|
license. The distribution is available via CVS and snapshot images in |
|
tar and zip file formats on the web site. |
|
The source code from CVS can be found at the following Open Group CVS |
|
server; |
|
</p> |
|
<p><span class="norm"></span><font style="color: rgb(0, 0, 0);">CVS |
|
write accounts are managed by Martin Kirk of The Open Group </font> |
|
(<a href="mailto:%28k.m.kirk@opengroup.org">m.kirk@opengroup.org</a>) |
|
</p> |
|
<br> | <br> |
<h2><a name="peg_sup_plat">Pegasus Supported Platforms</a></h2> |
More information on this project, access to the CVS, and |
|
documentation on |
|
Pegasus are available from the OpenGroup WEB site - <a target="blank" href="http://www.openpegasus.org/">http://www.openpegasus.org</a><br> |
|
<h4><a name="peg_sup_plat">Pegasus Supported Platforms</a></h4> |
<p> | <p> |
Pegasus is regularly tested against a variety of platforms by the | Pegasus is regularly tested against a variety of platforms by the |
development group. The results of the nightly tests can be found | development group. The results of the nightly tests can be found |
here: <a |
here: <a href="http://cvs.opengroup.org/cgi-bin/pegasus-build-status.cgi">Nightly |
href="http://cvs.opengroup.org/cgi-bin/pegasus-build-status.cgi">Nightly |
|
test status</a> . The Release notes provides additional details | test status</a> . The Release notes provides additional details |
regarding the platforms. <a |
regarding the platforms. |
href="http://www.openpegasus.org/pp/protected/revdoc.tpl?CALLER=revdocuments.tpl&grid=1692"> |
PEP 249 is the Release Notes PEP for 2.5.1.<br> |
PEP 230</a> is the release notes PEP for 2.5.<br> |
|
</p> | </p> |
<h2><a name="peg_dep">Pegasus Dependencies</a></h2> |
<h4><a name="cmnd">Commands</a></h4> |
<p> |
<p></p>The manpages for each of the commands can be found in the Pegasus source |
We have worked to minimize the dependence of Pegasus on other software |
tree in the pegasus/rpm/manLinux/ directory.<p></p> |
packages and tools. Currently Pegasus has the following dependencies: |
<p>To see simple help for a command, invoke it with the "--help" option.</p> |
</p> |
<p><font face="Verdana">Here is a list of useful |
<p><b>1. GNUMAKE</b> - To simplify the building of Pegasus across |
commands:</font></p> |
multiple platforms we |
<span style="font-weight: bold;" class="norm"></span><span style="font-family: times new roman; font-weight: bold;"><span class="norm"></span></span><span style="font-weight: bold;">Some of |
have standardized on a set of build tools including: GNUMAKE. We are |
|
using GNUMAKE 3.79.1 successfully both in Windows and Linux |
|
environments. |
|
</p> |
|
<p>GNUMAKE is available from :</p> |
|
<p> <a target="blank" |
|
href="http://www.gnu.org/">http://www.gnu.org</a> |
|
</p> |
|
<b>2. FLEX and BISON</b> - These tools were used to develop the |
|
MOF |
|
compiler and WQL |
|
parser. <span class="norm"></span><font |
|
style="color: rgb(0, 0, 0);">These tools are required only for |
|
development of the parsers, not for building Pegasus.</font> |
|
<p><b>3. 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. <span class="norm"></span><font |
|
style="color: rgb(0, 0, 0);">These tools are required to build the |
|
interface documentation set.</font> |
|
</p> |
|
<p><b>4. 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><span style="font-weight: bold;">5</span>. <b>OpenSSL </b>- If it |
|
is intended to use SSL on the |
|
communication protocol, the OpenSSL libraries are required.<br> |
|
</p> |
|
<p> NOTE: A set of the required |
|
tools for windows platforms is available on the openpegasus web |
|
site. <a href="../Pegasus24/www.openpegasus.org">www.openpegasus.org</a></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 "--help" flag. </p> |
|
<span style="font-family: times new roman;">Here is a list of useful |
|
commands:<br> |
|
<br style="font-weight: bold;"> |
|
</span><span style="font-weight: bold;" class="norm"></span><span |
|
style="font-family: times new roman; font-weight: bold;"><span |
|
class="norm"></span></span><span style="font-weight: bold;">Some of |
|
the basic commands:</span> | the basic commands:</span> |
<br> | <br> |
NOTE: Refer to the admin guide in pegasus/doc/Admin_Guide_Release.pdf | NOTE: Refer to the admin guide in pegasus/doc/Admin_Guide_Release.pdf |
|
|
<li>cimprovider -l -s (Lists providers and their status)</li> | <li>cimprovider -l -s (Lists providers and their status)</li> |
<li>cimprovider -e -m OperatingSystemModule (Enables the | <li>cimprovider -e -m OperatingSystemModule (Enables the |
OperatingSystem provider)</li> | OperatingSystem provider)</li> |
<li>cimuser -a -u guest _w <ThePassword> (Adds the user <span |
<li>cimuser -a -u guest -w <ThePassword> (Adds the user <span style="font-style: italic;">guest</span> with specified password)<br> |
style="font-style: italic;">guest</span> with specified password)<br> |
|
</li> | </li> |
<li>cimuser -l (Lists the users )<br> | <li>cimuser -l (Lists the users )<br> |
</li> | </li> |
|
|
windows it | windows it |
must be specifically installed as a service (ex. cimserver -install) | must be specifically installed as a service (ex. cimserver -install) |
and then | and then |
started as a service (cimserver -start). The cimserver --h option |
started as a service (cimserver -start). The cimserver --help option |
explains the | explains the |
exact format of the start and stop options.<br |
exact format of the start and stop options.<h4><a name="docs">Pegasus Documentation</a></h4> |
style="color: rgb(0, 0, 0);"> |
<p>Much of Pegasus |
<font><font color="RED"><br |
|
style="color: rgb(0, 0, 0); font-weight: bold;"> |
|
<span style="color: rgb(0, 0, 0); font-weight: bold;">Makefile commands |
|
<br> |
|
</span></font></font>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. <br> |
|
The following list contains some of the make targets that are |
|
supported: |
|
<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> |
|
<font><font color="RED"><span |
|
style="color: rgb(0, 0, 0); font-weight: bold;"></span><span |
|
style="color: rgb(0, 0, 0);">For a comprehensive list of the |
|
make targets, refer to the make files.<br> |
|
</span><br style="color: rgb(0, 0, 0);"> |
|
<span style="color: rgb(0, 0, 0); font-weight: bold;">TestMakefile |
|
commands |
|
</span><br style="color: rgb(0, 0, 0);"> |
|
<span style="color: rgb(0, 0, 0);"></span></font></font><font><font |
|
color="RED"><span class="norm"></span></font></font> TestMakefile is a |
|
make file |
|
that in the top level Pegasus source directory that defines |
|
functionality to |
|
initiate the Pegasus tests. The targets defined in this makefile allow |
|
the |
|
user to run the various tests and test suites that are included in the |
|
Pegasus |
|
source package.<br> |
|
<font><font color="RED"><span class="norm"></span></font></font>Example: |
|
From the $PEGASUS_ROOT directory. |
|
make -f TestMakefile [testoption]<br> |
|
<br style="color: rgb(0, 0, 0);"> |
|
<font><font color="RED"><span style="color: rgb(0, 0, 0);">## rebuild - |
|
Rebuild |
|
</span><br style="color: rgb(0, 0, 0);"> |
|
<span style="color: rgb(0, 0, 0);">## build - Build |
|
</span><br style="color: rgb(0, 0, 0);"> |
|
<span style="color: rgb(0, 0, 0);">## prestarttests - Execute |
|
functional tests |
|
</span><br style="color: rgb(0, 0, 0);"> |
|
<span style="color: rgb(0, 0, 0);">## poststarttests - Execute |
|
poststarttests (No security, No SSL) |
|
</span><br style="color: rgb(0, 0, 0);"> |
|
<span style="color: rgb(0, 0, 0);">## tests - Execute prestarttests and |
|
poststarttests |
|
</span><br style="color: rgb(0, 0, 0);"> |
|
<span style="color: rgb(0, 0, 0);">## standardtests - Execute |
|
poststarttests and a series of |
|
</span><br style="color: rgb(0, 0, 0);"> |
|
<span style="color: rgb(0, 0, 0);">## posstarttests using multiple |
|
options. |
|
</span><br style="color: rgb(0, 0, 0);"> |
|
<span style="color: rgb(0, 0, 0);">## |
|
</span><br style="color: rgb(0, 0, 0);"> |
|
<br> |
|
<span style="color: rgb(0, 0, 0);">Some examples: <br> |
|
make -f TestMakefile prestarttests |
|
- runs the unit tests, builds |
|
</span><span style="color: rgb(0, 0, 0);">the repositories. |
|
</span><br style="color: rgb(0, 0, 0);"> |
|
<span style="color: rgb(0, 0, 0);"> make -f TestMakefile poststarttests |
|
- starts the server, </span><span style="color: rgb(0, 0, 0);">runs |
|
the poststarttest suites |
|
</span><span style="color: rgb(0, 0, 0);">(make poststarttests plus |
|
more) |
|
</span><br style="color: rgb(0, 0, 0);"> |
|
<span style="color: rgb(0, 0, 0);">make -f TestMakefile tests - |
|
combines prestarttests and |
|
</span><span style="color: rgb(0, 0, 0);">poststarttests |
|
</span><br style="color: rgb(0, 0, 0);"> |
|
<span style="color: rgb(0, 0, 0);">make -f TestMakefile standardtests - |
|
runs the basic poststarttests </span><span style="color: rgb(0, 0, 0);">(make |
|
poststarttests) multiple |
|
</span><span style="color: rgb(0, 0, 0);">times with various options. |
|
</span><br style="color: rgb(0, 0, 0);"> |
|
<br style="color: rgb(0, 0, 0);"> |
|
<br style="color: rgb(0, 0, 0);"> |
|
<span style="color: rgb(0, 0, 0); font-weight: bold;">BuildMakefile |
|
commands </span><br style="color: rgb(0, 0, 0);"> |
|
<span style="color: rgb(0, 0, 0);"></span><br> |
|
</font></font>Some examples:<font><font color="RED"><br |
|
style="color: rgb(0, 0, 0);"> |
|
<span style="color: rgb(0, 0, 0);"> make -f pegasus/mak/BuildMakefile |
|
cleanbuild - Remove the existing pegasus </span><span |
|
style="color: rgb(0, 0, 0);">directory, perform a CVS |
|
</span><span style="color: rgb(0, 0, 0);">checkout of the pegasus |
|
source, |
|
</span><span style="color: rgb(0, 0, 0);">build, and run tests. |
|
</span><br style="color: rgb(0, 0, 0);"> |
|
<span style="color: rgb(0, 0, 0);">make -f pegasus/mak/BuildMakefile |
|
removeall |
|
- Remove the existing pegasus |
|
</span><span style="color: rgb(0, 0, 0);">directory. |
|
</span><br style="color: rgb(0, 0, 0);"> |
|
<span style="color: rgb(0, 0, 0);"></span><span |
|
style="color: rgb(0, 0, 0);"></span><span style="color: rgb(0, 0, 0);">make |
|
-f pegasus/mak/BuildMakefile |
|
recheckout - Remove the existing pegasus |
|
</span><span style="color: rgb(0, 0, 0);">directory and perform a CVS |
|
</span><span style="color: rgb(0, 0, 0);">checkout of the pegasus |
|
source. |
|
</span><br style="color: rgb(0, 0, 0);"> |
|
<br> |
|
<span style="color: rgb(0, 0, 0);">The following sequence builds the |
|
tree, the repository, the testrepository, |
|
</span><span style="color: rgb(0, 0, 0);">starts the server and runs |
|
the server tests suites. |
|
</span><br style="color: rgb(0, 0, 0);"> |
|
<br style="color: rgb(0, 0, 0);"> |
|
<span style="color: rgb(0, 0, 0);"> make world |
|
</span><br style="color: rgb(0, 0, 0);"> |
|
<span style="color: rgb(0, 0, 0);"> make testrepository |
|
</span><br style="color: rgb(0, 0, 0);"> |
|
<span style="color: rgb(0, 0, 0);"> make -f TestMakefile poststarttests |
|
</span><br style="color: rgb(0, 0, 0);"> |
|
<span style="color: rgb(0, 0, 0);"> |
|
</span><br> |
|
</font></font><br> |
|
<span style="font-family: monospace;"><br> |
|
</span> |
|
<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 | is documented in the PEGASUS PEPs which are the basis for approval of |
Pegasus functionality, changes, plans, etc. These documents are | Pegasus functionality, changes, plans, etc. These documents are |
openly available on the PEGASUS web site. The preliminary |
openly available on the PEGASUS web site. The current documentation is |
documentation |
|
is not provided with this release. The current documentation is |
|
maintained both as a manual created | maintained both as a manual created |
under the tool DOC++ in the runtime subdirectory manual/html (see | under the tool DOC++ in the runtime subdirectory manual/html (see |
doc/devManual to create), as an api document also creatable from the | doc/devManual to create), as an api document also creatable from the |
|
|
documentation in the future and today is the source of most discussion | documentation in the future and today is the source of most discussion |
and | and |
design documentation. </p> | design documentation. </p> |
<h1><a name="part">How to Participate</a></h1> |
<h4><a name="part">How to Participate</a></h4> |
<p><span class="norm"></span><font style="color: rgb(0, 0, 0);">Contributors | <p><span class="norm"></span><font style="color: rgb(0, 0, 0);">Contributors |
are welcome to participate in the OpenPegasus development effort. Join | are welcome to participate in the OpenPegasus development effort. Join |
the mailing list by visiting www.openpegasus.org and clicking on |
the mailing list by visiting <a href="http://www.openpegasus.org/">http://www.openpegasus.org</a> and clicking on |
Mailing Lists.</font></p> |
Mailing Lists. Joining the pegasus-l mailing list will provide a login/password |
|
for the website.</font></p> |
<h1> | <h1> |
<a name="inst_peg">Pegasus Install</a> </h1> |
<a name="inst_peg">Installing Pegasus</a> </h1> |
<p>RPM installation instructions can be found here: <a |
<h4><a name="download">Obtain Pegasus in Source Code or Binary Executable Format</a></h4> |
href="http://www.openpegasus.org/pr/">http://www.openpegasus.org/pr</a><br> |
<h2></h2> |
</p> |
<h2></h2> |
<p><strong><strong>Verify Dependencies<br> |
|
</strong></strong></p> |
|
<p><strong><strong><span style="font-weight: bold;"></span>Be</strong></strong>fore |
|
you install Pegasus be sure you have the proper set of software |
|
Pegasus is dependent on. <a href="#peg_dep">See Dependencies |
|
section.</a><br> |
|
</p> |
|
<strong></strong> |
|
<p> <a name="set_envt_var"><strong>Set the environment |
|
variables<br> |
|
</strong></a></p> |
|
<p>Before installing or running OpenPegasus, environment variables may |
|
have to be defined or updated. <br> |
|
<strong><br> |
|
</strong></p> |
|
<p><a |
|
href="http://www.openpegasus.org/pp/uploads/40/8502/PEP200_RecommendedReleaseOptions.htm">PEP |
|
200</a> contains the list of environment variables and setup necessary |
|
to use OpenPegasus.<br> |
|
</p> |
|
<p></p> |
|
<ul> |
|
</ul> |
|
<p></p> |
|
<h2><a name="pop_peg_rep">Populate the Pegasus repository</a> </h2> |
|
<p> |
|
Before using Pegasus you must populate the repository. Typically, this |
|
is done during the build process when you run the makefile. However, |
|
you |
|
can also do it manually after the Pegasus has been built. </p> |
|
<ol> | <ol> |
<li>Register the MOF (Managed Object Format) file describing the |
Pegasus can be obtained via any of the following:<br> |
skeleton of the object. </li> |
<ol> |
<li>Register a second MOF which only points out which lib*.so file to |
<li>Released tarballs (see |
be loaded when a specific object is activated. </li> |
<a href="http://www.openpegasus.org/page.tpl?ggid=392">Release |
|
tarballs link</a>)</li> |
|
<li>CVS (See <a href="http://www.openpegasus.org/page.tpl?ggid=667">CVS |
|
code repository</a> for |
|
more information.)</li> |
|
<li>Linux RPMs. See |
|
(<a href="http://www.openpegasus.org/pr">RPM |
|
link</a> for |
|
more information |
|
)</li> |
</ol> | </ol> |
|
</ol> |
|
<p>NOTE: Linux RPMs are only available for a limited set of releases. |
|
</p> |
|
<p>The distribution is available via CVS and snapshot images in |
|
tar and zip file formats on the web site. |
|
The source code from CVS can be found at the Open Group CVS server - |
|
cvs.opengroup.org. The source can be checked out anonymously using the |
|
instructions at <a href="http://www.openpegasus.org/protected/page.tpl?ggid=667"> |
|
http://www.openpegasus.org/page.tpl?ggid=667</a></p> |
|
<p><span class="norm"></span><font style="color: rgb(0, 0, 0);">CVS |
|
write accounts are managed by Martin Kirk of The Open Group </font> |
|
(<a href="mailto:%28k.m.kirk@opengroup.org">m.kirk@opengroup.org</a>) |
|
</p> |
|
<p>RPM installation instructions can be found here: <a href="http://www.openpegasus.org/pr/">http://www.openpegasus.org/pr</a><br> |
|
</p> |
|
<strong></strong> |
<p></p> | <p></p> |
|
<h4><a name="peg_dep">Verify Dependencies</a></h4> |
<p> | <p> |
The providers included with Pegasus are automatically entered into the |
We have worked to minimize the dependence of Pegasus on other software |
repository |
packages and tools. Currently Pegasus has the following dependencies: |
by running the following command: <tt>make repository</tt> |
|
</p> | </p> |
<p> |
<p><b>1. GNUMAKE</b> - To simplify the building of Pegasus across |
The 'make repository' in the pegasus directory does three things: |
multiple platforms we |
|
have standardized on a set of build tools including: GNUMAKE. We are |
|
using GNUMAKE 3.79.1 successfully both in Windows and Linux |
|
environments. |
</p> | </p> |
<ul> |
<p>GNUMAKE is available from :</p> |
<li><span class="norm"></span> Removes the existing repository if one |
<p> <a target="blank" href="http://www.gnu.org/">http://www.gnu.org</a> |
exists.</li> |
</p> |
<li>Generates the CIM Schema v2.9 in the repository (skeleton of CIM |
<p><b>2. FLEX and BISON</b> - These tools were used to develop the |
objects). </li> |
MOF |
<li><span class="norm"></span><font style="color: rgb(0, 0, 0);">Loads |
compiler and WQL |
schema for CIM Server functions </font>(shutdown, add users, etc) and |
parser. <span class="norm"></span><font style="color: rgb(0, 0, 0);">These tools are required only for |
CIM indications |
development of the parsers, not for building Pegasus.</font></p> |
(SNMP, Events, Alert, Threshold, etc) |
<p><b>3. DOC++ </b>- The Pegasus documentation is taken from a |
internal to the Pegasus. </li> |
combination of text files |
<li>Registers included CIM Providers (libOSProvider.so, |
and the Pegasus header files themselves. This documentation is |
libDNSProvider.so, … ) in Pegasus (which are located in |
formatted with DOC++ and GAWK. <span class="norm"></span><font style="color: rgb(0, 0, 0);">These tools are required to build the |
src/Providers) </li> |
interface documentation set.</font> |
</ul> |
</p> |
<h2> |
<p><b>4. ICU Internationalization libraries</b> - These libraries are |
<a name="reg_prov">Registering |
used as the basis for message catalogs for message |
Providers in the Pegasus Environment</a></h2> |
internationalization. See the ICU website |
<p> |
(http://oss.software.ibm.com/icu/) for more information on these |
Pegasus registers providers with a set of provider registration |
libraries</p> |
classes, not using the provider qualifier as is done in most DMTF CIM |
<p><span style="font-weight: bold;">5</span>. <b>OpenSSL </b>- If it |
CIMOM implementations today. This set of classes is close to but not |
is intended to use SSL on the |
exactly the same as the experimental DMTF definition (See the DMTF |
communication protocol, the OpenSSL libraries are required.<br> |
Interop |
</p> |
schema, experimental versions starting with 2.6). This will be |
<p> NOTE: A set of the required |
harmonized in the future when the DMTF scheme is moved to final |
tools for windows platforms is available on the openpegasus web |
status. </p> |
site. <a href="http://www.openpegasus.org/pp/uploads/40/Pegasus24/www.openpegasus.org">www.openpegasus.org</a></p> |
<p><span class="norm"></span><font style="color: rgb(0, 0, 0);">Registration |
<h4><a name="set_envt_var"><strong>Set the Environment |
is performed by creating instances</font> of the |
Variables</strong></a></h4> |
registration classes that represent the provider module, providers, |
<p>Before installing or running OpenPegasus, environment variables may |
classes, etc. to be registered. The easiest way to create a new |
have to be defined or updated. <br> |
registration today is to copy from one of the existing registration |
</p> |
MOFs. See the providers/sample/load directory for examples of |
<p>PEP 237 contains the list of environment variables and setup necessary |
several registration instance implementations that do work with |
to use OpenPegasus.</p> |
OpenPegasus |
<p></p>At a minimum, the following need to be set:<p></p> |
today.</p> |
<blockquote> |
<strong><br> |
PEGASUS_ROOT=<location of your pegasus source tree> |
</strong> |
<br> |
<h2><a name="note_bld_peg_lnx">Notes about |
PEGASUS_HOME=<location for the built executables, repository, etc> |
Building OpenPegasus on Linux </a></h2> |
|
|
<br> |
|
PEGASUS_PLATFORM=<your platform> |
|
</blockquote> |
|
<p>For a list of valid |
|
platforms, enter "make listplatforms" from the root of the Pegasus |
|
source tree. <br> |
|
</p> |
|
<h1><a name="build_peg">Building Pegasus</a></h1> |
|
<div> |
|
<div> |
|
To accept the default build options and get started quickly, use the</div> |
|
<div> |
|
following commands from the root of the Pegasus source tree:</div> |
|
<br> |
|
<div> |
|
make build</div> |
|
<div> |
|
This will build the dependencies, any utilities that are needed, |
|
all</div> |
|
<div> |
|
the Pegasus and test executable code, and do any necessary setup |
|
to</div> |
|
<div> |
|
run the CIM Server.</div> |
|
<br> |
|
<div> |
|
make alltests</div> |
|
<div> |
|
This will run the unit tests, create the repository by compiling |
|
in</div> |
|
<div> |
|
the MOF for the default CIM Schema (2.9 for Pegasus 2.5.1), |
|
compile</div> |
|
<div> |
|
in the MOF for all Pegasus test cases, do any other configuration</div> |
|
<div> |
|
necessary to run the tests, and then run a large automated test |
|
suite</div> |
|
<div> |
|
to verify Pegasus CIM Server functionality.`1<p> </p></div> |
|
<div> |
|
There are many variations possible. Refer to PEP 237 for possible build |
|
and</div> |
|
<div> |
|
run-time configuration options. Enter "make usage" for more information |
|
on</div> |
|
<div> |
|
make targets that are available for building and testing Pegasus.</div> |
|
</div> |
|
<h4><a name="note_bld_peg_lnx">Building OpenPegasus on Linux </a></h4> |
<p> | <p> |
To build OpenPegasus on Linux, ensure that you you have the environment | To build OpenPegasus on Linux, ensure that you you have the environment |
variables set (PEGASUS_HOME, PEGASUS_ROOT, PEGASUS_PLATFORM. For | variables set (PEGASUS_HOME, PEGASUS_ROOT, PEGASUS_PLATFORM. For |
32 bit linux, the definition of PEGASUS_PLATFORM is normally | 32 bit linux, the definition of PEGASUS_PLATFORM is normally |
LINUX_IX86_GNU). |
LINUX_IX86_GNU).<br> |
</p> | </p> |
<br> |
<h4><a name="note_bld_peg_ssl">Building OpenPegasus with SSL |
<h2><a name="bld_peg_win">Notes |
</a></h4> |
on building OpenPegasus on Windows 2k or Windows XP with Microsoft |
<p> |
|
To build with SSL you need the OpenSSL libraries and header files. They |
|
are NOT distributed with OpenPegasus. Make sure you have them in a |
|
standard |
|
directory so OpenPegasus can find them. If that's not |
|
the case, set the environment variable OPENSSL_HOME= to point where |
|
your OpenSSL |
|
installation is. |
|
</p> |
|
<p>Also have the PEGASUS_HAS_SSL=true variable set. Then just run 'make' |
|
in Pegasus |
|
directory and you will have OpenPegasus with SSL enabled. See "Creating |
|
SSL |
|
certificates" below for more information on how to use SSL. |
|
</p> |
|
Refer to the OpenPegasus SSL Guidelines guide found in the doc directory for details on |
|
using OpenPegasus with SSL.<br> |
|
<h4><a name="bld_peg_win">Building OpenPegasus on Windows 2k or Windows XP with Microsoft |
Visual | Visual |
C++ </a></h2> |
C++ </a></h4> |
<p> | <p> |
Use of Windows 2000 SP3 or later is recommended. OpenPegasus is | Use of Windows 2000 SP3 or later is recommended. OpenPegasus is |
regularly tested on both Windows 2000 and Windows XP using the | regularly tested on both Windows 2000 and Windows XP using the |
|
|
contained | contained |
in the source distribution, the Microsoft compilers (DevStudio 5.x is | in the source distribution, the Microsoft compilers (DevStudio 5.x is |
not supported, Visual Studio 6.0, SP5 is supported) and the GNUMAKE | not supported, Visual Studio 6.0, SP5 is supported) and the GNUMAKE |
make utility. Note that you MUST have the OpenPegasus <a |
make utility. Note that you MUST have the OpenPegasus <a href="#mu_utility">mu.exe </a>utility compiled and available |
href="#mu_utility">mu.exe </a>utility compiled and available |
|
before trying to compile OpenPegasus on the normal windows platform. | before trying to compile OpenPegasus on the normal windows platform. |
The | The |
following is the basic setup steps for the environment. | following is the basic setup steps for the environment. |
|
|
</p> | </p> |
<p>For Windows, try the following for an example environment: </p> | <p>For Windows, try the following for an example environment: </p> |
<blockquote> | <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 |
<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 OpenPegasus 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> |
class="norm">The '/' characters are intentional and required by the OpenPegasus 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> | </blockquote> |
<h3> |
<h6> |
<a name="mu_utility">The MU Utility </a></h3> |
<a name="mu_utility">The MU Utility </a></h6> |
<p> | <p> |
In order to provide a consistent build structure across multiple | In order to provide a consistent build structure across multiple |
platforms, we | platforms, we |
|
|
A copy of the binary is made available as a zip file on the OpenPegasus | A copy of the binary is made available as a zip file on the OpenPegasus |
WEB site. | WEB site. |
<p></p> | <p></p> |
<h2><a name="note_bld_peg_ssl">Notes about |
<h1><a name="pop_peg_rep">Populate the Pegasus Repository</a> </h1> |
Building OpenPegasus with SSL |
|
</a></h2> |
|
<p> | <p> |
To build with SSL you need the OpenSSL libraries and header files. They |
Before using Pegasus you must populate the repository. Typically, this |
are NOT distributed with OpenPegasus. Make sure you have them in a |
is done during the build process when you run the makefile. However, |
standard |
you |
directory so OpenPegasus can find them. If that's not |
can also do it manually after the Pegasus has been built. </p> |
the case, set the environment variable OPENSSL_HOME= to point where |
<ol> |
your OpenSSL |
<li>Register the MOF (Managed Object Format) file describing the |
installation is. |
skeleton of the object. </li> |
|
<li>Register a second MOF which only points out which lib*.so file to |
|
be loaded when a specific object is activated. </li> |
|
</ol> |
|
<p></p> |
|
<p> |
|
The providers included with Pegasus are automatically entered into the |
|
repository |
|
by running the following command: <tt>make repository</tt> |
</p> | </p> |
<p>Also have the PEGASUS_HAS_SSL=yes variable set. Then just run 'make' |
<p> |
in Pegasus |
The 'make repository' in the pegasus directory does three things: |
directory and you will have OpenPegasus with SSL enabled. See "Creating |
|
SSL |
|
certificates" below for more information on how to use SSL. |
|
</p> | </p> |
Refer to the SSL Admin guide found in the doc directory for details on |
<ul> |
using OpenPegasus with SSL.<br> |
<li><span class="norm"></span> Removes the existing repository if one |
<p></p> |
exists.</li> |
|
<li>Generates the CIM Schema v2.9 in the repository (skeleton of CIM |
|
objects). </li> |
|
<li><span class="norm"></span><font style="color: rgb(0, 0, 0);">Loads |
|
schema for CIM Server functions </font>(shutdown, add users, etc) and |
|
CIM indications |
|
(SNMP, Events, Alert, Threshold, etc) |
|
internal to the Pegasus. </li> |
|
<li>Registers included CIM Providers (libOSProvider.so, |
|
libDNSProvider.so, … ) in Pegasus (which are located in |
|
src/Providers) </li> |
|
</ul> |
<h1> | <h1> |
<a name="test">Testing a OpenPegasus Installation</a></h1> |
<a name="reg_prov">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 experimental 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><span class="norm"></span><font style="color: rgb(0, 0, 0);">Registration |
|
is performed by creating instances</font> of the |
|
registration classes that represent the provider module, providers, |
|
classes, etc. to be registered. The easiest way to create a new |
|
registration today is to copy from one of the existing registration |
|
MOFs. See the providers/sample/load directory for examples of |
|
several registration instance implementations that do work with |
|
OpenPegasus |
|
today.</p> |
|
<h1> |
|
<a name="test">Testing an OpenPegasus Installation</a></h1> |
<p> | <p> |
OpenPegasus includes an extensive set of test facilities as part of the | OpenPegasus includes an extensive set of test facilities as part of the |
CVS | CVS |
|
|
<li><b>Test Clients</b> - There are several clients that have been | <li><b>Test Clients</b> - There are several clients that have been |
built specifically to test OpenPegasus, or parts of OpenPegasus, | built specifically to test OpenPegasus, or parts of OpenPegasus, |
including | including |
TestClient, Client, CLI, ipinfo, osinfo, WbemEsec, etc. See the |
TestClient, Client, CLI, ipinfo, osinfo, wbemexec, etc. See the |
src/Clients directory for more information. These programs require a |
pegasus/src/Clients directory for more information. These programs require a |
server complete with repository to be running. Note that some of | server complete with repository to be running. Note that some of |
these tests use classes and instances that are only installed with the | these tests use classes and instances that are only installed with the |
"make testrepository" functions including test namespaces and extra | "make testrepository" functions including test namespaces and extra |
classes and instances in those namespaces and additional providers from | classes and instances in those namespaces and additional providers from |
the providers/sample and providers/testproviders directories. </li> |
the pegasus/Providers/sample and pegasus/Providers/TestProviders directories. </li> |
<li><b>Sample and test providers</b> - Test providers exist for | <li><b>Sample and test providers</b> - Test providers exist for |
the major provider types in the providers/sample directories and the |
the major provider types in the pegasus/Providers/sample directories and the |
providers/testProviders directory </li> |
pegasus/Providers/TestProviders directory </li> |
<li><b>Unit Tests</b> - Most OpenPegasus functions include unit tests | <li><b>Unit Tests</b> - Most OpenPegasus functions include unit tests |
for | for |
the functions. These are normally executed with the "make tests" | the functions. These are normally executed with the "make tests" |
|
|
these tests. This set of tests executes an extensive set of fixed | these tests. This set of tests executes an extensive set of fixed |
tests and compares the results against predefined results.</li> | tests and compares the results against predefined results.</li> |
</ul> | </ul> |
<p></p> |
<h4><a name="test_icu">Testing with ICU enabled</a></h4> |
<br> |
|
<h2><a name="test_icu">Testing with ICU enabled</a></h2> |
|
<p>ICU (International Components for Unicode) refers to the set of | <p>ICU (International Components for Unicode) refers to the set of |
libraries that OpenPegasus uses to run globalized. For example: these | libraries that OpenPegasus uses to run globalized. For example: these |
libraries are used | libraries are used |
|
|
environment variable must be set to the home directory where the ICU | environment variable must be set to the home directory where the ICU |
resource bundles are built. By default the resource bundles are built | resource bundles are built. By default the resource bundles are built |
into directories below PEGASUS_HOME/msg, so that should be the setting | into directories below PEGASUS_HOME/msg, so that should be the setting |
for PEGASUS_MSG_HOME.<br> |
for PEGASUS_MSG_HOME.</font></p> |
</font></p> |
<p></p> |
<p><font style="color: rgb(0, 0, 0);">-------------------------------------------------------------------------------------------------------------------------------------<br> |
<h1> |
</font></p> |
<a name="sec0">Security Considerations</a></h1> |
<p><i><font size="2">Copyright (c) 2005 EMC Corporation; |
<p>Some of the steps of installing and running Pegasus have |
Hewlett-Packard Development Company, L.P.; IBM Corp.; The Open Group; |
security properties that you should be aware of. If you plan to administer a |
VERITAS Software Corporation</font><br> |
Pegasus server, see the 'security considerations' section of the administrators |
|
guide <pointer>. If you plan to write clients or providers for integration into |
|
Pegasus, see the developer's security guidance.<br> |
|
</pointer></p> |
|
<hr> |
|
<p><font size="2"><i>Copyright (c) 2006 Hewlett-Packard Development Company, |
|
L.P.; IBM Corp.;<br> |
|
EMC Corporation; Symantec Corporation; The Open Group.<br> |
<br> | <br> |
<font size="1">Permission is hereby granted, free of charge, to any |
Permission is hereby granted, free of charge, to any person obtaining a copy<br> |
person obtaining a copy of this software and associated |
of this software and associated documentation files (the "Software"), to<br> |
documentation files (the "Software"), to deal in the Software without |
deal in the Software without restriction, including without limitation the<br> |
restriction, including without limitation the rights to use, copy, |
rights to use, copy, modify, merge, publish, distribute, sublicense, and/or<br> |
modify, merge, publish, distribute, sublicense, and/or sell copies of |
sell copies of the Software, and to permit persons to whom the Software is<br> |
the Software, and to permit persons to whom the Software is furnished |
furnished to do so, subject to the following conditions:<br> |
to do so, subject to the following conditions:</font><br> |
<br> |
<font size="2"><br> |
THE ABOVE COPYRIGHT NOTICE AND THIS PERMISSION NOTICE SHALL BE INCLUDED IN<br> |
</font> |
ALL COPIES OR SUBSTANTIAL PORTIONS OF THE SOFTWARE. THE SOFTWARE IS PROVIDED<br> |
<font size="1">THE ABOVE COPYRIGHT NOTICE AND THIS PERMISSION NOTICE |
"AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT<br> |
SHALL BE INCLUDED IN ALL COPIES OR SUBSTANTIAL PORTIONS OF THE |
LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR<br> |
SOFTWARE. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF |
PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT<br> |
ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE |
HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN<br> |
WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND |
ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION<br> |
NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE |
WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.</i></font></p> |
LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION |
<hr> |
OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION |
<p><i><font size="1"><big><big><span style="font-family: arial;">End of Document<br> |
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> | </span></big></big></font></i></p> |
<p><span style="color: rgb(0, 0, 0);"></span> </p> | <p><span style="color: rgb(0, 0, 0);"></span> </p> |
</body> |
|
</html> |
<script language="javascript">postamble();</script> |
|
</body></html> |