version 1.2, 2001/01/20 22:44:43
|
version 1.13, 2003/10/16 19:42:15
|
|
|
Pegasus - A Manageability Services Broker for the DMTF CIM/WBEM Standards |
|
| |
|
OpenPegasus - A Manageability Services Broker for the DMTF CIM/WBEM Standards |
| |
Author: Mike Brasher, Karl Schopmeyer | Author: Mike Brasher, Karl Schopmeyer |
| |
HISTORY_BEGIN |
Tagline: OpenPegasus is an object manager for DMTF CIM objects written in C++ |
$Log$ |
and supported by The Open Group |
Revision 1.2 2001/01/20 22:44:43 karl |
|
retrofit for provider interfaces |
|
| |
Revision 1.1 2001/01/15 04:26:04 karl |
STATUS: Revised June 2003 to match Pegasus release 2.2 |
added Readme |
Contents: |
|
========= |
|
|
|
1. Overview |
|
2. Availability of Pegasus |
|
3. Pegasus major components |
|
4. Pegasus Dependencies |
|
5. The Pegasus Directory Structure |
|
6. Installation |
|
7. Building Pegasus |
|
8. Populate the Repository |
|
9. The MU Utility |
|
10. Notes about Building Pegasus on Linux |
|
11. Notes on building Pegasus with SSL |
|
12. Building Pegasus on Windows 2000 or Windows XP With Microsoft Visual C++ |
|
13. Installing the Pegasus HTML Test Client |
|
14. Development with Pegasus and Pegasus Tools |
|
15. Commands |
|
16. Creating SSL certifications. |
|
17. Testing with ICU enabled |
|
18. Documentation |
|
19. Participate |
| |
| |
Tagline: Pegasus is an object manager for DMTF CIM objects written in C++ |
|
and supported but The Open Group |
|
| |
HISTORY_END |
|
| |
|
1. Overview: |
|
============ |
|
|
|
OpenPegasus (also refered to as Pegasus): |
| |
Pegasus is an object manager for DMTF CIM objects It is written in C++ and |
Pegasus is an open-source object manager for DMTF CIM objects. It is written |
includes the Object manager, a set of defined interfaces, and SDKs for both |
in C++ and includes the Object manager, a set of defined interfaces, and SDKs |
client, providers, and services extensions. It is maintained consistent with |
for both client, providers, and services extensions. It is maintained |
the DMTF CIM and WBEM specifications except for any exceptions noted in the |
consistent with the DMTF CIM and WBEM specifications except for any exceptions |
documentation. |
noted in the documentation. |
| |
This distribution represents a work in progress towards building a Pegasus | This distribution represents a work in progress towards building a Pegasus |
release. Pegasus is open source and is covered under the following licnese. |
release. Pegasus is open source and is covered under the following license. |
This version is incomplete and is directed towards evaluators and developers | This version is incomplete and is directed towards evaluators and developers |
of the Pegasus Architecture. | of the Pegasus Architecture. |
| |
|
|
(LICENSE) of this release. This licensing is intended to support as wide a | (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. |
| |
This distribution represnts a snapshot of the current work. Currently Pegasus |
This distribution represents a snapshot of the current work. Currently Pegasus |
is in phase 1 of a multiphase development project. This snapshot is primarily | is in phase 1 of a multiphase development project. This snapshot is primarily |
for developers and for evaluation of the project. | for developers and for evaluation of the project. |
| |
More information and on this project, access to the CVS, and documentation on |
More information on this project, access to the CVS, and documentation on |
Pegasus is available from the OpenGroup WEB site. |
Pegasus are available from the OpenGroup WEB site. |
| |
There are separate files in the release for | There are separate files in the release for |
| |
|
|
In addition, the roadmap for Pegasus and further information on the project is | In addition, the roadmap for Pegasus and further information on the project is |
available on The Opengroup Pegasus WEB Site. | available on The Opengroup Pegasus WEB Site. |
| |
http://www.opengroup.org/MSB |
http://www.openpegasus.org |
|
|
Availability of Pegasus |
|
======================= |
|
| |
Pegasus is distributed as open source. Today the distribution is limited |
|
because we want to reach a predefined level of development before making the |
|
project publically available. The move from limited to open distribution will |
|
be a decision of the Pegasus development team and The Open Group and should |
|
occur before March 2001. |
|
| |
To get on the distribution list for Pegasus today, send an email to |
2. Availability of Pegasus: |
|
============================ |
m.kirk@opengroup.org |
|
or |
|
k.schopmeyer@opengroup.org |
|
|
|
Pegasus Major Components |
|
======================== |
|
The major components of Pegasus are: |
|
| |
Pegasus Server - WBEM/CIM CIM_Server with interfaces for providers and Clients |
Pegasus is distributed as open source. The distribution is available via |
|
CVS and snapshot images in tar and zip file formats. |
| |
Pegasus Repository - Today Pegasus provides a defined class repository interface and a simple |
The source code from CVS can be found at the following Open Group CVS server; |
file based class repository. Future will include the object repository |
|
| |
Pegasus Client SDK - Tools for building Pegasus clients based on the Pegasus C++ interfaces |
cvs.opengroup.org:/cvs/MSB |
and using the WBEM HTTP/XML protocols or directly interfacing with Pegasus |
|
| |
Pegasus Test Clients - Simple test clients being developed as part of the Pegasus development |
using the password authenticating server option (pserve). |
process |
|
| |
Pegasus HTML Test Client - To aid some testing we created a test client for Pegasus that uses |
Anonymous access for read is with the name and password "anon" as follows: |
a WEB server (ex. Apache) with a set of CGI modules and HTML to allow the entry of Pegasus |
|
operations from a WEB browser as forms and the recept of the response as WEB pages. This has |
|
proven useful as a test tool and can be used for a wide variety of demonstrations. |
|
| |
Pegasus Providers - Future (Version 1.0) |
%export CVSROOT=:pserver:anon@cvs.opengroup.org:/cvs/MSB |
|
%cvs login |
Pegasus Service Extensions - Future (version 1.0) |
|
|
|
Pegasus MOF Compiler - Future (Version 0.9) |
|
|
|
Pegasus Dependencies |
|
=========== |
|
|
|
We have worked to minimize the dependence of Pegasus on other software |
|
packages and tools. Currently Pegasus has the following dependencies |
|
| |
1. ACE_Wrappers communication package - The ACE Wrappers package is used for communication and |
When requested, enter the password "anon" |
some low level functions within the MSB, the Pegasus client SDK, and the Pegasus Provider SDK. |
|
ACE is available from the following site. |
|
| |
|
The source tree is in the directory pegasus. To check out the complete Pegasus |
|
source tree just type: |
| |
http://ace.cs.wustl.edu/cvsweb/ace-cvs.cgi/ACE_wrappers/ |
cvs co pegasus |
| |
Currently we are using version 5.1 of ACE_Wrappers both in Linux and Windows |
A Pegasus directory will be created under the current directory and populated |
|
with the complete source tree and documentation. To get the latest updates |
|
after a checkout just type this from Pegasus root: |
| |
http://www.cs.wustl.edu/~schmidt/ACE_wrappers/ACE-5.1.tar.gz |
cvs update -d |
| |
COMMENTS: Pegasus only uses limited facilities from ACE. However, today we demand the |
|
installation of the complete ACE library. One of the action items for the future is |
|
to provide a more limited ACE library and possibly even to provide an environment |
|
independent of ACE. This will depend on the demands of the users. |
|
| |
2. To simplify the building of Pegasus across multiple platforms we have |
Active contributors to Pegasus have write access to the CVS repository. |
stnadardized on a set of build tools including: GNUMAKE. We are using GNUAKE |
If you are interested in contributing back to the Pegasus project, |
4.79.1 successfully both in Windows and Linux environments. |
(i.e. write (checkin) access to CVS) please request access from either |
|
Martin Kirk (m.kirk@opengroup.org) or Karl Schopmeyer (k.schopmeyer@opengroup.org). |
| |
GNUMAKE is available from |
|
| |
http://www.gnu.org |
3. Pegasus Major Components: |
|
============================= |
| |
ATTN: I think we need to make our version available on the TOG site. |
The major components of Pegasus are: |
| |
COMMENT: Unless other users of Pegasus demand it, we will NOT create any build environment |
Pegasus Server - WBEM/CIM Server with interfaces for providers and clients |
for Pegasus that does not require GNUMAKE (ex Visual C++). We are open to other developers who |
|
want to contribute other build structures for particular environments. |
|
| |
|
Pegasus Repositories - Today Pegasus provides a defined class repository |
|
interface and a simple file based class repository. It also includes |
|
an instance repository. Note that these repository were created for |
|
functionality, not efficieny. It is expected that they will be replaced |
|
with other implementations of the respository function as the need arises. |
| |
3. MU.EXE - To minimize the difference between Linux and Windows for GUNMAKE, |
Pegasus Client SDK - Tools for building Pegasus clients based on the Pegasus |
we have created a utility called MU.exe. The source for this is available |
C++ interfaces and using the WBEM HTTP/XML protocols or directly |
with the distribution and the binary is distributed in the bin directory of |
interfacing with Pegasus. |
the the snapshots for now. |
|
| |
The Pegasus Directory Structure |
Pegasus Test Clients - Simple test clients being developed as part of the |
=============================== |
Pegasus development process |
| |
Pegasus is distributed as a complete directory structure that should be installed either |
Pegasus HTML Test Client - To aid in testing we created a test client for |
from one of the snapshots or from CVS. |
Pegasus that uses a WEB server (ex. Apache) with a set of CGI modules and |
|
HTML to allow the entry of Pegasus operations from a WEB browser as forms |
|
and the receipt of the response as WEB pages. This has proven useful as a |
|
test tool and can be used for a wide variety of demonstrations. |
| |
This structure is generally as follows |
Pegasus Provider SDK - Tools for building Pegasus providers using the Pegasus |
Pegasus - Root directory |
C++ interfaces. |
bin |
|
build Destination for all intermediate files from build |
|
bin Destination for executable and DLL modules from Pegasus build |
|
lib |
|
obj |
|
cgi-bin Source and make for the Pegasus WEB Based Test client software |
|
doc Miscelaneous Pegasus Documents. Includes the DMTF XML for CIM 2.4 |
|
html HTML files for the Browser test client. |
|
mak General make files (used by the root make and other makes) |
|
Repository This Directory containes the created repository |
|
src All Pegasus Source Files |
|
ACEExamples Test directrory with examples of the use of ACE (developers) |
|
Pegasus |
|
CGI CGI files for the WEB test client |
|
CGIClient |
|
Client Pegasus Client SDK and Test client using the SDK |
|
depends |
|
tests |
|
Common Pegasus Common Functions (C++ source and headers |
|
tests Test programs for the common functions |
|
Protocol Pegasus Client HTTP/XML Protocol Modules |
|
depends |
|
Repository Pegasus Repository Interfaces and Simple Repository |
|
tests Tests for Repository Functions |
|
Server Pegasus Server Modules |
|
depends |
|
tests |
|
| |
Utils |
Pegasus Providers - Providers to illustrate the use of Pegasus services including |
manual Pegasus User/developer manual source modules |
providers for test and demonstration. |
HTML Output from the Pegasus Manual compilartion. |
|
| |
In the near future we will add directories for: |
Pegasus Service Extensions - Common services for use by other Pegasus |
|
components to extend Pegasus capabilites. |
| |
Service Extensions |
Pegasus MOF Compiler - FA standalone compiler for MOF files that can be used |
Providers |
to install MOF into the Pegasus schema repository and also to check syntax. |
|
There is also a tool to extract the MOF from the repository. |
| |
| |
Installation |
4. Pegasus Dependencies: |
============ |
========================= |
| |
Pegasus today is provided only as a source distribution. You download compile and use it. |
We have worked to minimize the dependence of Pegasus on other software |
Pegasus currently compiles and runs under both Linux and Windows NT environments. |
packages and tools. Currently Pegasus has the following dependencies: |
| |
The installation of Pegasus involves expanding the snapshot distribution files, building the |
1. GNUMAKE - To simplify the building of Pegasus across multiple platforms we |
runtime, the test files and test clients, and building the repository. |
have standardized on a set of build tools including: GNUMAKE. We are using |
|
GNUMAKE 3.79.1 successfully both in Windows and Linux environments. |
| |
NOTE: Since the compiler integration is not complete today, the class repository is populated |
GNUMAKE is available from |
from the XML defintions for the complete CIM schema. This process is included in the build |
|
process so that at the end of a complete build, the class repository is completely populated |
|
from the CIM 2.4 release schema. |
|
| |
|
http://www.gnu.org |
| |
Building from a Distribution --- General |
|
======================================== |
|
| |
Pegasus is buildable and runnable on either Linux or WIndows Platforms today. |
2. MU.EXE - To minimize the difference between Linux and Windows for GNUMAKE, |
It uses a common build system for the two platforms based on build files and |
we have created a utility called MU.exe. This utility is required for |
GUNMAKE. |
Pegasus make with ONLY Windows environment. It is provided as an 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 |
|
needs. MU is not required on UNIX or LINUX platforms. |
| |
Generally we support four targets in our make system: |
NOTE: The binary for MU.EXE is not distributed in the Pegasus bin directory. |
|
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. |
| |
|
NOTE: A copy of the binary is made available as a zip file on the Pegasus |
|
WEB site. |
| |
C:\> make clean |
Again, MU is used ONLY if you are using Windows. |
C:\> make depend |
|
C:\> make |
|
C:\> make tests |
|
| |
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. These tests can |
|
be executed as follows: |
|
| |
ATTN: Add the procedure for Client/Server Test start here. |
3. FLEX and BISON - 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. |
| |
|
4. DOC++ - 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 |
|
documentaiton. |
| |
For information on particular installation characteristics, tools, etc. for each platform see |
|
the appropriate sections below: |
|
| |
Generally the build commands are as follows: |
5. The Pegasus Directory Structure |
|
=================================== |
| |
1. There is a Makefile in the Pegasus root. Simply executing make in the Pegasus |
Pegasus is distributed as a complete directory structure that should be |
root directory will make everything. |
installed either from one of the snapshots or from CVS. |
| |
2. In order to provide a working class repository for Pegasus until the MOF compiler |
This structure is generally as follows |
is integrated, There is a utility to load the CIM Schema from XML into the repository. |
|
This executes the LoadRepository executable which is defined in |
|
| |
pegasus/src/Pegasus/Repository/tests/LoadRepository |
Pegasus Pegasus Root directory |
| |
with the binary in pegasus/bin. This program will load the CIM XML repository |
cgi Source for the Pegasus WEB Based Test client |
definitions into the class repository. |
cgi-bin CGI Directories for WEB demonstration. |
|
This directory is normally empty but can |
|
be populated from the runtime with the make |
|
from cgi. |
|
htdocs HTML Pages for Pegasus WEB emonstration |
|
doc Miscellaneous Pegasus Documents. |
|
DevManual Source and build files for developers' manual |
|
mak General make files (used by other makes) |
|
src All Pegasus Source Files |
|
ACEExample Test directrory with examples of the use of ACE |
|
Clients Source for various test clients and client SDK |
|
CGICLIENT Pegasus test client that uses a WEB browser |
|
Pegasus |
|
Client Pegasus Client API Tests |
|
depends |
|
tests |
|
Common Pegasus Common Functions (C++ source and headers |
|
tests Test programs for the common functions |
|
Protocol Pegasus Client HTTP/XML Protocol Modules |
|
depends |
|
Provider Pegasus Provider interface functions |
|
Repository Pegasus Repository Interfaces and Simple Repository |
|
tests Tests for Repository Functions |
|
Server Pegasus Server Modules |
|
Providers Pegasus test and required providers |
| |
3. To test a fresh release, go to the pegasus root and type |
Utils |
| |
"make world". |
Runtime Directories |
|
$PEGASUS_HOME$ Home directory for runtime. All compiler, linker |
|
documentation creation, etc. is put here. |
|
bin Destination for executable and DLL modules from |
|
Pegasus build |
|
Manual HTML output of the Pegasus Manual |
|
lib Destination for Pegasus LIB modules |
|
obj Destination for object modules |
|
repository This Directory contains the created repository |
| |
| |
This will clean, build dependencies, build binaries, and then run all |
6. Installation |
tests except the Client/Server tests. |
================ |
| |
4. To execute the basic test suite that is shipped with pegasus type |
Pegasus today is provided only as a source distribution. |
| |
"make tests" |
To install Pegasus, you must check it out using CVS (Common Version System) |
|
or download the snapshot. You download, compile, and use it. |
| |
5. To run the Client/Server tests provided, simply type |
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. |
| |
"make tests" |
|
| |
Running "make -s tests" suppresses extraneous output such as the |
7. Building Pegasus |
enter/leave directory messages. |
===================== |
| |
6. "Make Clean" removes all object and library files from the |
1. Check that you have requisite programs (listed in Pegasus Dependencies). |
structure. |
|
| |
Build Variables |
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). |
| |
The build system depends on the following environment variables |
Be sure these are on your path. |
| |
PEGASUS_ACE_ROOT - required (points to ACE_wrappers directory). This must be set |
|
before you initiate make |
|
| |
PEGASUS_BUILD - optional (points to build directory; defaults to build |
2. Define the following three environment variables: |
directory under root of pegasus distribution). This must be set before you iniiate |
|
make |
|
| |
PEGASUS_OS_TYPE - optional. The is currently set to windows. If you build on Linux |
PEGASUS_ROOT - this should be the "pegasus" directory you've pulled from CVS |
you must change this before initiating make. |
|
| |
COMMENTS: In the future, we will probably automate this more. However, setting these |
PEGASUS_HOME - to point to a directory to contain output binary files |
variables today is manual. |
(e.g., set it to $HOME/pegasus_home). Then the output will go into |
|
$HOME/pegasus_home/bin and $HOME/pegasus_home/lib |
| |
|
PEGASUS_PLATFORM - this must be set to a supported platform identifier. |
| |
The MU Utility |
This identifier has the following form: |
============== |
|
| |
In order to provide a consistent build structure across multiple platforms, we developed a |
<Operating-System>_<Architecture>_<Compiler> |
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: |
|
| |
|
For example (Linux on IA32 platform using the GNU Compiler): |
|
LINUX_IX86_GNU |
| |
C:\> mu rm myfile.cpp yourfile.cpp |
For a complete list, refer to the platform_ make files found in directory |
|
pegasus/mak |
| |
| |
You may type "mu" to get a list of valid commands. Here are some |
Note: if you plan on doing parallel builds, you might consider setting |
of them: |
PEGASUS_HOME to something like this: |
| |
|
$HOME/pegasus_home_LINUX_IX86_GNU |
| |
rm, rmdirhier, mkdirhier, echo, touch, pwd, copy, move, compare depend |
That way, the output of each build will be placed in its own directory. |
| |
|
3. Now place $PEGASUS_HOME/bin on your path |
| |
The MU utility supports globing (expansion of wildcards) so |
and |
you can do things like this: |
|
| |
|
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 |
| |
C:\> mu rm *.obj *.exe |
4. Change to the root of the Pegasus distrubution and type "make" |
|
(where make refers to GNU make). |
| |
MU is required to build under the Windows environment.MU is available as part of the |
5. Then create the repository, which is needed to serve data. |
distribution of Pegasus. |
"make repository" |
| |
Building Pegausu on Linux |
6. To test the build type "make tests". |
========================= |
|
| |
1. Obtain, unpack and build the ACE_Wrappers package for Linux. |
The following make targets are supported: |
| |
2. Define an environment variable called ACE_ROOT that points to the root of the ACE_WRAPPERS |
<default> - Build everything. |
distribution. For example |
clean - Clean out all objects, libs, and executables. |
|
depend - Create the dependencies. |
|
repository - Create the repository in $PEGASUS_HOME/repository |
|
tests - Execute all tests (except client server tests). |
|
rebuild - clean, depend, <default> |
|
world - depend, <default> |
| |
IMPORT ACE_ROOT=\local\ACE_Wrappers |
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. |
| |
ATTN: Mike. what is a viable directory for Linux (what do you use) |
For information on particular installation characteristics, tools, etc. for |
|
each platform see the appropriate sections below: |
| |
3. Define an environment variable PEGASUS_ROOT that points to the |
Generally the build commands are as follows: |
root of the Pegasus Distribution |
|
| |
4. Append %PEGASUS_ROOT%/bin to your path |
1. There is a Makefile in the Pegasus root directory. Simply executing |
|
make in the Pegasus root directory will make everything. "make rebuild" |
|
will clean and rebuild everything. The "make rebuild" will also populate |
|
the repository with the current CIM Schemas. |
| |
5. Unpack the ace distribution. |
2. To test a fresh release, go to the pegasus root and type |
| |
ATTN: Unpack with what since ZIP. |
"make world". |
| |
5. Build using the make commands defined in the section on General Build. |
|
| |
make world |
This will build dependencies, build binaries, and then run all |
make tests |
tests except the Client/Server tests. |
| |
Building Pegasus on NT or Windows 2000 With Visual C++ |
3. To execute the basic test suite that is shipped with pegasus type |
======================================================= |
|
| |
Today we build Pegasus on Windows NT using a set of make files contained |
"make tests". This also reintalls the repository. |
in the source distribution, the Microsoft compilers (tested so far with |
|
versions 5 and 6) and the GNUMAKE make utility. The following is the basic |
|
set up steps for the |
|
| |
|
Running "make -s tests" suppresses extraneous output such as the |
|
enter/leave directory messages. |
| |
1. Setup the environment variables and path for the Micrososft Visual C compiler. |
4. "make clean" removes all object and library files from the structure. |
Typically this can be done by running the VCVARS32.BAT file supplied with Microsoft Visual |
|
C++. (contained in the same directory as cl.exe). |
|
| |
2. Define an environment variable called ACE_ROOT that points to the |
|
root of the ACE_Wrappers distribution. For example: |
|
| |
C:\> set PEGASUS_ACE_ROOT=c:/ACE_wrappers |
5. A new build system has been added to Pegasus where a new CVS checkout is done, |
|
built, and tests are run. Do it by: "make -f mak/BuildMakefile cleanbuild" |
| |
Now append %ACE_ROOT%/bin to the path like this: |
|
| |
C:\> set path=%path%;%PEGASUS_ACE_ROOT%/bin |
8. Populate the Repository |
|
=========================== |
| |
3. Define an environment variable called PEGASUS_ROOT that points to |
Before using Pegasus you must populate the repository with the providers. The makefile |
the root of the Pegasus distribution. For example: |
does it all for you, but in case you are wondering what it does or how to do it |
|
manually: |
| |
C:\> set PEGASUS_ROOT=c:/pegasus |
1. Register the MOF (Managed Object Format) file describing the skeleton of the object. |
|
2. Register a second MOF which only points out which lib*.so file to be loaded when a |
|
specific object is activated. |
| |
Now append %PEGASUS_ROOT%/bin to your path like this: |
This is done automatically for the providers included in Pegasus by doing: |
|
make repository. |
| |
set path=%path%;%PEGASUS_ROOT%/bin |
The 'make repository' in pegasus/Schemas does three things |
|
Runs MOF compiler (cimmofl) on: |
|
-Schema v2.7 |
|
Generates the CIM Schema v2.7 in the repository (skeleton of CIM objects) |
|
-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) |
| |
4. Unpack and build the ACE_Wrappers distribution for windows. |
For more information about using the MOF compiler, refer to user's manual on the |
|
openpegasus.org. |
| |
As an example, we created a file called %ACE_ROOT%/ace/config.h |
|
containing the following: |
|
| |
#include "ace/config-win32.h" |
9. The MU Utility |
|
=================== |
| |
and then opened this DSW file in MSVC++ IDE: |
In order to provide a consistent build structure across multiple platforms, we |
|
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: |
| |
%ACE_ROOT%/ace/ace.dsw |
|
| |
From the build menu we picked "aced.dll". For me it built without complaint. |
C:\> mu rm myfile.cpp yourfile.cpp |
| |
BUG: there is still one open problem that has not been resolved. With |
|
the Visucal C++ version 6 compiler, the ace libraries default to |
|
| |
acemfc.dll |
You may type "mu" to get a list of valid commands. Here are some |
|
of them: |
| |
With the version 5 visual C, apparently they default to the names |
|
| |
ace.dll |
rm, rmdirhier, mkdirhier, echo, touch, pwd, copy, move, compare depend |
or |
|
aced.dll (debug verions |
|
| |
We will correct this in a future snapshot. |
|
| |
|
The MU utility supports globing (expansion of wildcards) so |
|
you can do things like this: |
| |
5. Unpack the Pegasus distribution. On Windows systems, PKzip25 or WINZIP can be used. |
|
Be certain to use the option that expands the directory tree of the files. This expansionwill |
|
create a directory called ./pegasus |
|
| |
If you are using pkzip25.exe do this: |
C:\> mu rm *.obj *.exe |
C:\> pkzip25 -extract -recurse -directories pegasus.zip |
|
| |
This will create a directory tree called ./pegasus under the |
MU is required to build under the Windows environment.MU is available as part |
current directory. |
of the distribution of Pegasus. |
| |
ATTN: Define for Linux also |
|
| |
6. Change directory to %PEGASUS_ROOT% and type "make world". See the general build section |
10. Notes about Building Pegasus on Linux |
for the full set of make commands. |
=========================================== |
| |
This builds Pegasus and all of its examples. |
No problem. Just make sure you have the environment variables set. |
| |
7. To verify that it built okay, run the tests |
|
| |
make tests |
11. Notes about Building Pegasus with SSL |
|
========================================== |
| |
Installing the Pegasus HTML Test Client |
To build with SSL you need the OpenSSL libraries and header files. Make sure |
======================================= |
you have them in a standard directory so Pegasus can find them. If that's not |
|
the case, set the environment varialble OPENSSL_HOME= to point where your OpenSSL |
|
installation is. |
|
|
|
Also have the PEGASUS_HAS_SSL=yes variable set. Then just run 'make' in Pegasus |
|
directory and you will have Pegasus with SSL enabled. See section "Creating SSL |
|
certificates" for more information of how to use SSL. |
|
|
|
|
|
12. Building Pegasus on Windows 2000 (SP3 or later recommended) or Windows XP |
|
With Microsoft Visual C++ |
|
====================================================================== |
|
|
|
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 supported) and the GNUMAKE make utility.The |
|
following is the basic setup steps for the environment. |
|
|
|
|
|
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). |
|
|
|
For Windows, try the following for an example environment: |
|
|
|
REM call the standard Microsoft .bat for VC 6 setup. |
|
call 'C:/Program Files/Microsoft Visual Studio/VC98/Bin/Vcvars32.bat' |
|
REM Set debug to something if you want compile in debug mode |
|
set PEGASUS_DEBUG=true |
|
REM set PEGASUS_ROOT to top of source tree |
|
set PEGASUS_ROOT=C:/cimom/pegasus |
|
REM set PEGASUS_HOME to where you want repository and executables |
|
set PEGASUS_HOME=%PEGASUS_ROOT% |
|
REM setup the path to the runtime files. |
|
set path=%path%;%PEGASUS_HOME%/bin |
|
|
|
13. Installing the Pegasus HTML Test Client: |
|
============================================= |
|
|
|
This is a separate test tool that allows Pegasus requests to be initiated from |
|
any WEB browser and that uses a WEB browser, CGI scritps and HTML pages for |
|
the formating 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. |
| |
This is a separate test tool that allows Pegasus requests to be initiated from any WEB browser |
|
and that uses a WEB browser, CGI scritps and HTML pages for the formating 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. |
|
| |
Development with Pegasus and Pegasus Tools |
14. Development with Pegasus and Pegasus Tools: |
========================================== |
================================================ |
| |
ATTN: This section needs to be completed. It should reference the more | ATTN: This section needs to be completed. It should reference the more |
complete documentation | complete documentation |
|
ATTN: Write about providers? |
=================== |
|
Documentation |
|
|
|
The documentation is currently in preperation. The preliminary documentation is not provided |
|
with this snapshot but is avialable from the OpenGroup Pegasus WEB pages. The current |
|
documentation is maintained both as a manual created under the tool DOC++ in the |
|
subdirectory manual/html and as other miscelaneous documentation in the doc directory. |
|
|
|
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. |
|
|
|
Participate! |
|
============ |
|
We are looking for people who want to join the effort of getting this |
|
next release off the ground. Please send me email for details. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
| |
|
15. Commands: |
|
============= |
| |
|
The manpages for each of the commands are in rpm/manLinux/man1.Z directory (on CVS) |
| |
|
To see simple help for each of the commands, use the "-h" flag. |
|
Examples: |
|
bin/cimserver –s (Shuts it down) |
|
bin/cimserver traceLevel=4 traceComponents=ALL (starts server with config flags) |
|
bin/cimprovider –l –s (lists providers and their status) |
|
bin/cimprovider –e –m OperatingSystemModule (enables the OperatingSystem provider) |
|
bin/cimuser –a –u guest –w ThePassword |
|
bin/cimuser –l (lists the users) |
|
bin/tomof CIM_Config (extract CIM_Config from repository and present it in MOF type) |
|
|
|
|
|
16. Creating SSL certifications |
|
================================ |
|
|
|
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 directory. |
|
|
|
CN="Common Name" |
|
EMAIL="test@email.address" |
|
HOSTNAME=`uname -n` |
|
sed -e "s/$CN/$HOSTNAME/" \ |
|
-e "s/$EMAIL/root@$HOSTNAME/" $PEGASUS_ROOT/ssl.cnf \ |
|
> $PEGASUS_HOME/ssl.cnf |
|
chmod 644 $PEGASUS_HOME/ssl.cnf |
|
chown bin $PEGASUS_HOME/ssl.cnf |
|
chgrp bin $PEGASUS_HOME/ssl.cnf |
|
|
|
/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 |
|
|
|
17. Testing with ICU enabled: |
|
============================== |
|
|
|
ICU (International Compoments 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 |
|
disabling message loading from the bundles, "make poststartests" will fail. |
|
In order to run "make poststarttests" successfully with ICU enabled, an |
|
environment variable called PEGASUS_USE_DEFAULT_MESSAGES must exist prior to |
|
starting the server. Once this is defined, when the cimserver starts, all |
|
messages generated will be the default hardcoded messages. This will enable |
|
"make poststarttests" to complete successfully. Once "make poststarttests" is |
|
complete, you should stop the cimserver and then undefine PEGASUS_USE_DEFAULT_MESSAGES. |
|
If this variable is left defined, Pegasus will not be able to load messages |
|
using ICU resource bundles. |
| |
|
18. Documentation: |
|
=================== |
| |
|
The documentation is currently in preperation. The preliminary documentation |
|
is not provided with this snapshot but is avialable from the OpenGroup Pegasus |
|
WEB pages. The current documentation is maintained both as a manual created |
|
under the tool DOC++ in the runtime subdirectory manual/html and as other |
|
miscelaneous documentation in the doc directory. |
|
|
|
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. |
|
|
|
|
|
19. Participate! |
|
================= |
|
|
|
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. |