1 dudhe.girish 1.6 <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
|
2 karl 1.1 <html>
3 <head>
|
4 dudhe.girish 1.6 <meta name="GENERATOR" content="Microsoft FrontPage 3.0">
5 <meta name="ProgId" content="FrontPage.Editor.Document">
6 <meta http-equiv="Content-Type"
7 content="text/html; charset=windows-1252">
8 <title>OpenPegasus</title>
|
9 karl 1.1 </head>
10 <body>
11 <p align="center"><b><font size="4">Pegasus Enhancement Proposal (PEP)</font></b></p>
|
12 dudhe.girish 1.6 <p style="margin-top: 0pt; margin-bottom: 0pt;"><b>PEP #:</b> 103</p>
13 <p style="margin-top: 0pt; margin-bottom: 0pt;"><b>Title: </b>OpenPegasus
14 Version 2.3 Release Readme file</p>
15 <p style="margin-top: 0pt; margin-bottom: 0pt;"><b>Version: </b>1.1</p>
16 <p style="margin-top: 0pt; margin-bottom: 0pt;"><b>Created:</b> 12
17 November 2003</p>
18 <p style="margin-top: 0pt; margin-bottom: 0pt;"><b>Authors: </b>Karl
19 Schopmeyer, Konrad Rzeszutek</p>
20 <p style="margin-top: 0pt; margin-bottom: 0pt;"><b>Status: </b>draft</p>
21 <p style="margin-top: 0pt; margin-bottom: 0pt;"><b>Version History:</b></p>
|
22 karl 1.1 <table border="1" cellspacing="1" bordercolordark="#666666"
|
23 dudhe.girish 1.6 bordercolorlight="#CCCCCC" width="100%" style="font-family: Arial;">
24 <tbody>
25 <tr>
26 <th bgcolor="#cae6ca">Version</th>
27 <th bgcolor="#cae6ca">Date</th>
28 <th bgcolor="#cae6ca">Author</th>
29 <th bgcolor="#cae6ca">Change Description</th>
30 </tr>
31 <tr>
32 <td align="center">1.0</td>
33 <td align="center">12 November 2003</td>
34 <td align="center">Karl Schopmeyer</td>
35 <td>Update from 2.2 Release notes. Converted to HTML</td>
36 </tr>
37 <tr>
38 <td align="center">1.1</td>
39 <td align="center">March 10 2004</td>
40 <td align="center">Konrad Rzeszutek</td>
41 <td>Added sections describing SSL and PAM configuration</td>
42 </tr>
43 <tr>
44 dudhe.girish 1.6 <td align="center"> </td>
45 <td align="center"> </td>
46 <td align="center"> </td>
47 <td> </td>
48 </tr>
49 </tbody>
50 </table>
|
51 karl 1.1 <hr>
|
52 dudhe.girish 1.6 <p><b>Abstract:</b> Installation, build, operation information on the
53 Pegasus Platform Version 2.3 Release. Note that if this readme conflicts
54 with the documentation in the release notes or interface definition
55 documents for a particular release, those documents should be
56 considered authorative. This is a simplified overview to act as an
57 introduction to Pegasus.</p>
|
58 karl 1.1 <hr>
|
59 dudhe.girish 1.6 <p align="center"><b><font size="5">OpenPegasus - A Manageability
60 Services Broker for the DMTF CIM/WBEM Standards </font></b></p>
61 <p align="left"><b>Tagline:</b> OpenPegasus is an object manager for
62 DMTF CIM objects written in C++ and supported by The Open Group </p>
63 <p align="left"><b>STATUS:</b> Revised November 2003 for Pegasus
64 release version 2.3.0 </p>
65 <p align="center"><b><font size="4">Table of Contents</font></b></p>
66 <p align="left" style="margin-top: 0pt; margin-bottom: 0pt;"><a
67 href="#Overview"> Overview</a> </p>
68 <p align="left" style="margin-top: 0pt; margin-bottom: 0pt;"><a
69 href="#Availability%20of%20Pegasus">Availability of Pegasus</a></p>
70 <p align="left" style="margin-top: 0pt; margin-bottom: 0pt;"><a
71 href="#Pegasus%20Major%20Components">Pegasus Major Components</a></p>
72 <p align="left" style="margin-top: 0pt; margin-bottom: 0pt;"><a
73 href="#Pegasus%20Supported%20Platforms">Pegasus Supported Platforms</a></p>
74 <p align="left" style="margin-top: 0pt; margin-bottom: 0pt;"><a
75 href="#Pegasus%20Dependencies">Pegasus Dependencies </a></p>
76 <p align="left" style="margin-top: 0pt; margin-bottom: 0pt;"><a
77 href="#The%20Pegasus%20Directory%20Structure">The Pegasus Directory
78 Structure</a> </p>
79 <p align="left" style="margin-top: 0pt; margin-bottom: 0pt;"><a
80 dudhe.girish 1.6 href="#Pegasus%20Installation">Installation</a> </p>
81 <p align="left" style="margin-top: 0pt; margin-bottom: 0pt;"><a
82 href="#Building%20Pegasus">Building Pegasus </a></p>
83 <p align="left" style="margin-top: 0pt; margin-bottom: 0pt;"><a
84 href="#Populate%20the%20Repository">Populate the Repository</a> </p>
85 <p align="left" style="margin-top: 0pt; margin-bottom: 0pt;"><a
86 href="#Registering%20Providers%20in%20the%20Pegasus%20Environment">Registering
87 Providers</a></p>
88 <p align="left" style="margin-top: 0pt; margin-bottom: 0pt;"><a
89 href="#The%20MU%20Utility">The MU Utility</a> </p>
90 <p align="left" style="margin-top: 0pt; margin-bottom: 0pt;"><a
91 href="#Notes%20about%20Building%20Pegasus%20on%20Linux">Notes about
92 Building Pegasus on Linux</a> </p>
93 <p align="left" style="margin-top: 0pt; margin-bottom: 0pt;"><a
94 href="#Notes%20about%20Building%20Pegasus%20on%20Mac%20OS%20X/Darwin">Notes
95 about Building Pegasus on Mac OS X/Darwin</a></p>
96 <p align="left" style="margin-top: 0pt; margin-bottom: 0pt;"><a
97 href="#Notes%20about%20Building%20Pegasus%20with%20SSL">Notes on
98 building Pegasus with SSL</a> </p>
99 <p align="left" style="margin-top: 0pt; margin-bottom: 0pt;"><a
100 href="#Building%20Pegasus%20on%20Windows%202000%20or%20Windows%20XP%20With%20Microsoft%20Visual%20C++">Building
101 dudhe.girish 1.6 Pegasus on Windows 2000 or Windows XP With Microsoft Visual C++</a></p>
102 <p align="left" style="margin-top: 0pt; margin-bottom: 0pt;"><a
103 href="#Installing%20the%20Pegasus%20HTML%20Test%20Client">Installing
104 the Pegasus HTML Test Client </a></p>
105 <p align="left" style="margin-top: 0pt; margin-bottom: 0pt;"><a
106 href="#Development%20with%20Pegasus%20and%20Pegasus%20Tools">Development
107 with Pegasus and Pegasus Tools</a> </p>
108 <p align="left" style="margin-top: 0pt; margin-bottom: 0pt;"><a
109 href="#Commands">Commands</a> </p>
110 <p align="left" style="margin-top: 0pt; margin-bottom: 0pt;"><a
111 href="#Creating%20SSL%20certifications">Creating SSL certifications</a> </p>
112 <p align="left" style="margin-top: 0pt; margin-bottom: 0pt;"><a
113 href="#Configuring%20SSL">Configuring Pegasus to use SSL</a> </p>
114 <p align="left" style="margin-top: 0pt; margin-bottom: 0pt;"><a
115 href="#Configuring%20PAM">Configuring Pegasus to use PAM</a> </p>
116 <p align="left" style="margin-top: 0pt; margin-bottom: 0pt;"><a
117 href="#Testing%20with%20ICU%20enabled">Testing with ICU enabled </a></p>
118 <p align="left" style="margin-top: 0pt; margin-bottom: 0pt;"><a
119 href="#Pegasus%20Documentation">Documentation</a> </p>
120 <p align="left" style="margin-top: 0pt; margin-bottom: 0pt;"><a
121 href="#Participate%21">Participate</a> </p>
|
122 karl 1.1 <h1><a name="Overview">Overview</a> </h1>
|
123 dudhe.girish 1.6 <p><b>OpenPegasus (also referred to as Pegasus):</b> Pegasus is an
124 open-source CIM Server for DMTF CIM objects. It is written in C++ and
125 includes the Object manager (CIMOM), a set of defined interfaces, an
126 implemenation of the CIMOperations over HTTP operations and their cimxml
127 HTTP encodings, and Interface libraries for both client and providers.
128 It is maintained consistent with the DMTF CIM and WBEM specifications
129 except for exceptions noted in the documentation. </p>
130 <p>Pegasus is open source and is covered under the MIT open-source
131 license.</p>
132 <p>Pegasus is being developed and maintained under the auspices of The
133 Open Group. Pegasus is maintained under the license defined in the doc
134 directory (LICENSE) of this release. This licensing is intended to
135 support as wide a distribution as possible with minimal demands on the
136 users. </p>
137 <p>More information on this project, access to the CVS, and
138 documentation on Pegasus are available from the OpenGroup WEB site. </p>
139 <p> <a href="http://www.opengroup.org">http://www.openpegaus.org</a></p>
140 <p>There are a number of separate documents representing the status and
141 each release of Pegasus </p>
|
142 karl 1.1 <ul>
|
143 dudhe.girish 1.6 <li>What's new for this release - See the PEPs (Pegasus Enhancement
144 Procedures) release notes on the Pegasus web site and duplicated in
145 the source top level directory</li>
146 <li>What's Broken - BUGS - See the ReleaseNotes for this release in
147 the CVS and the web site as a Pegasus PEP.</li>
148 </ul>
149 <p>The release notes are available on the WEB site as Pegasus PEP
150 documents and in the CVS for each release.</p>
|
151 karl 1.1 <table border="1" cellspacing="1" width="31%" id="AutoNumber3">
|
152 dudhe.girish 1.6 <tbody>
153 <tr>
154 <td width="42%"><b>Release</b></td>
155 <td width="58%"><b>Release Notes PEP</b></td>
156 </tr>
157 <tr>
158 <td width="42%">2.0</td>
159 <td width="58%">None</td>
160 </tr>
161 <tr>
162 <td width="42%">2.1</td>
163 <td width="58%">None</td>
164 </tr>
165 <tr>
166 <td width="42%">2.2</td>
167 <td width="58%">PEP 57</td>
168 </tr>
169 <tr>
170 <td width="42%">2.3</td>
171 <td width="58%">PEP 98</td>
172 </tr>
173 dudhe.girish 1.6 </tbody>
|
174 karl 1.1 </table>
175 <h1><a name="Availability of Pegasus">Availability of Pegasus</a></h1>
|
176 dudhe.girish 1.6 <p>Pegasus is distributed as open source under the MIT open-source
177 license. The distribution is available via CVS and snapshot images in
178 tar and zip file formats on the web site. The source code from CVS can
179 be found at the following Open Group CVS server; </p>
180 <p><font face="Courier New"> cvs.opengroup.org:/cvs/MSB </font></p>
181 <p>using the password authenticating server option (pserve). </p>
182 <p>Anonymous access for read is with the name and password "anon" as
183 follows: </p>
|
184 karl 1.1 <blockquote>
|
185 dudhe.girish 1.6 <p style="margin-top: 0pt; margin-bottom: 0pt;"><font
186 face="Courier New">%export
187 CVSROOT=:pserver:anon@cvs.opengroup.org:/cvs/MSB </font></p>
188 <p style="margin-top: 0pt; margin-bottom: 0pt;"><font
189 face="Courier New">%cvs login </font></p>
|
190 karl 1.1 </blockquote>
|
191 dudhe.girish 1.6 <p>When requested, enter the password "anon". The source tree is in the
192 directory pegasus. To check out the complete Pegasus source tree just
193 type: </p>
194 <p><font face="Courier New"> cvs co pegasus </font></p>
195 <p>A Pegasus directory will be created under the current directory and
196 populated with the complete source tree and documentation. To get the
197 latest updates after a checkout just type this from Pegasus root: </p>
198 <p><font face="Courier New"> cvs update -d </font></p>
199 <p>Active contributors to Pegasus have write access to the CVS
200 repository. If you are interested in contributing back to the Pegasus
201 project, (i.e. write (checkin) access to CVS) please request access from
202 either Martin Kirk (m.kirk@opengroup.org) or Karl Schopmeyer <a
203 href="mailto:%28k.schopmeyer@opengroup.org">(k.schopmeyer@opengroup.org</a>).</p>
204 <h1><a name="Pegasus Major Components">Pegasus Major Components</a></h1>
205 <p>The major components of Pegasus are: </p>
|
206 karl 1.1 <ul>
|
207 dudhe.girish 1.6 <li><b>Pegasus Server</b> - WBEM/CIM Server with interfaces for
208 providers and clients </li>
209 <li><b>Pegasus Repositories</b> - Today Pegasus provides a defined
210 class repository interface and a simple file based class repository.
211 It also includes an instance repository. Note that these repository
212 were created for functionality, not efficieny. It is expected that
213 they will be replaced with other implementations of the respository
214 function as the need arises. </li>
215 <li><b>Pegasus Client Library</b> - Tools for building Pegasus clients
216 based on the Pegasus C++ interfaces and using the WBEM HTTP/XML
217 protocols or directly interfacing with Pegasus. </li>
218 <li><b>Pegasus Test Clients</b> - Simple test clients being developed
219 as part of the Pegasus development process. These can be seen in the
220 src/Clients directory and its subdirectories </li>
221 <li><b>Pegasus HTML Test Client</b> - To aid in testing we created a
222 test client for Pegasus that uses a WEB server (ex. Apache) with a
223 set of CGI modules and HTML to allow the entry of Pegasus operations
224 from a WEB browser as forms and the receipt of the response as WEB
225 pages. This has proven useful as a test tool and can be used for a wide
226 variety of demonstrations. </li>
227 <li><b>Pegasus Provider Library</b> - Tools for building Pegasus
228 dudhe.girish 1.6 providers using the Pegasus C++ interfaces. </li>
229 <li><b>Pegasus Providers</b> - Providers to illustrate the use of
230 Pegasus services including providers for test and demonstration. </li>
231 <li><b>Pegasus Control Providers</b> - Common services for use by
232 other Pegasus components to extend Pegasus capabilites. </li>
233 <li><b>Pegasus MOF Compiler </b>- There standalone compiler
234 (cimmofl) for MOF files that can be used to install MOF into the
235 Pegasus schema repository and also to check syntax. There is also a
236 compiler that operates as a Pegasus client(cimmof) There is also a
237 tool to extract the MOF from the repository. </li>
238 </ul>
239 <h1><a name="Pegasus Supported Platforms">Pegasus Supported Platforms</a></h1>
240 <p>Pegasus is regularly tested against a variety of platforms by the
241 development group. The set of platforms and exact set of compilers for
242 any given release is documented in the Release notes for that release
243 (see the CVS source tree root directory or the Pegasus PEP defining the
244 ReleaseNotes for any particular release).</p>
245 <p>Generally Pegasus is supported on the following Platforms and
246 Compilers.</p>
|
247 karl 1.1 <table border="1" cellspacing="1" id="AutoNumber2" width="728">
|
248 dudhe.girish 1.6 <tbody>
249 <tr>
250 <td width="169" bgcolor="#99ff99"><b>Platform and OS</b></td>
251 <td width="556" bgcolor="#99ff99"><b>Compilers</b></td>
252 </tr>
253 <tr>
254 <td width="169">AIX</td>
255 <td width="556">VisualAge C++ Version</td>
256 </tr>
257 <tr>
258 <td width="169">HP-UX</td>
259 <td width="556">HP aC++ </td>
260 </tr>
261 <tr>
262 <td width="169">Linux Itanium</td>
263 <td width="556">gcc</td>
264 </tr>
265 <tr>
266 <td width="169">Linux IA-32</td>
267 <td width="556">gcc (versions 2.9x and 3.xx)</td>
268 </tr>
269 dudhe.girish 1.6 <tr>
270 <td width="169">Windows 2000</td>
271 <td width="556">Microsoft Visual C++ Ver 6 and Microsoft .Net
272 compiler Version <font color="#ff0000">7</font></td>
273 </tr>
274 <tr>
275 <td width="169">Windows XP</td>
276 <td width="556">Microsoft Visual C++ Ver. 6 and Microsoft .Net
277 compiler Version <font color="#ff0000">7</font></td>
278 </tr>
279 <tr>
280 <td width="169">Mac OS X/Darwin PPC</td>
281 <td width="556">gcc (version 3.3)</td>
282 </tr>
283 </tbody>
284 </table>
285 <h1><a name="Pegasus Dependencies">Pegasus Dependencies </a></h1>
286 <p>We have worked to minimize the dependence of Pegasus on other
287 software packages and tools. Currently Pegasus has the following
288 dependencies: </p>
289 <p><b>1. GNUMAKE</b> - To simplify the building of Pegasus across
290 dudhe.girish 1.6 multiple platforms we have standardized on a set of build tools
291 including: GNUMAKE. We are using GNUMAKE 3.79.1 successfully both in
292 Windows and Linux environments. </p>
293 <p>GNUMAKE is available from :</p>
294 <p> <a href="http://www.gnu.org">http://www.gnu.org</a> </p>
295 <p> NOTE: A set of the required tools for windows platforms is
296 available on the openpegasus web site.</p>
297 <p><b>2. MU.EXE </b>- To minimize the difference between Linux and
298 Windows for GNUMAKE, we have created a utility called MU.exe. This
299 utility is required for Pegasus make with ONLY Windows environment. It
300 is provided as an alternative to requiring a number of UNIX utilities
301 (SH, RM, etc.) on the windows platform and effectively provides the
302 functions of these utilities that GNUMAKE needs. MU is not required on
303 UNIX or LINUX platforms. </p>
304 <p>NOTE: The binary for MU.EXE is not distributed in the Pegasus bin
305 directory. You must build it separately. MU source code is part of the
306 distribution in the directory src/utils/MU with its own make file. You
307 must compile MU before you initiate the Pegausu make. </p>
308 <p>NOTE: A copy of the binary is made available as a zip file on the
309 Pegasus WEB site. </p>
310 <p>Again, MU is used ONLY if you are using Windows. </p>
311 dudhe.girish 1.6 <p><b>3. FLEX and BISON</b> - These tools were used to develop the MOF
312 compiler and WQL parser. Anybody intending to recompile the compiler or
313 parser from scratch will be required to have these tools. They are only
314 required if changes need to be made to the files for parsing and
315 compiling. </p>
316 <p><b>4. DLCOMPAT - </b>dlcompat is a dlopen(3) et.al. compatibility
317 library for Mac OS X/Darwin.<br>
318 <br>
319 <strong>NOTE</strong>: The dlcompat is not distributed with pegasus
320 source.<br>
321 <br>
322 dlcomapt is available from : <br>
323 <br>
324 <a href="http://www.opendarwin.org/projects/dlcompat/">http://www.opendarwin.org/projects/dlcompat/</a><br>
325 <br>
326 Again, dlcomapt needs to be installed ONLY if you are using Mac OS
327 X/Darwin.</p>
328 <p><b>5. DOC++ </b>- The Pegasus documentation is taken from a
329 combination of text files and the Pegasus header files themselves. This
330 documentation is formatted with DOC++ and GAWK. These tools are required
331 if the documentation is to be recreated but we expect that only the
332 dudhe.girish 1.6 core team will be recreating documentation. </p>
333 <p><b>6. ICU Internationalization libraries</b> - These libraries are
334 used as the basis for message catalogs for message internationalization.
335 See the ICU website (http://oss.software.ibm.com/icu/) for more
336 information on these libraries</p>
337 <p><strong>7</strong>. <b>OpenSSL </b>- If it is intended to use SSL
338 on the communication protocol, the OpenSSL libraries are required.</p>
339 <h1><a name="The Pegasus Directory Structure">The Pegasus Directory
340 Structure</a></h1>
341 <p>Pegasus is distributed as a complete source directory structure that
342 should be installed either from one of the snapshots or from CVS. </p>
343 <p>This structure is generally as follows:</p>
344 <p><font face="Courier New">Pegasus Source Structure</font></p>
345 <p><font face="Courier New">Pegasus Root directory (PEGASUS_ROOT
346 environment variable)</font> </p>
347 <ul>
348 <li><font face="Courier New"><b>cgi</b> Source for the Pegasus WEB
349 Based Test client </font>
350 <ul>
351 <li><font face="Courier New">cgi-bin CGI Directories for WEB
352 demonstration. This directory is normally empty but can be
353 dudhe.girish 1.6 populated from the runtime with the make from cgi. </font></li>
354 <li><font face="Courier New">htdocs HTML Pages for Pegasus WEB
355 demonstration </font></li>
|
356 karl 1.1 </ul>
|
357 dudhe.girish 1.6 </li>
358 <li><font face="Courier New"><b>doc</b> Miscellaneous Pegasus
359 Documents. </font>
|
360 karl 1.1 <ul>
|
361 dudhe.girish 1.6 <li><font face="Courier New">apidoc - Source for the public api
362 documentation.</font></li>
363 <li><font face="Courier New">DevManual Source and build files for
364 developers' manual mak General make files (used by other makes)</font></li>
365 </ul>
366 </li>
367 <li><font face="Courier New"><b>mak</b> - Common make files for
368 Pegasus compilation</font></li>
|
369 karl 1.1 <li><font face="Courier New"><b>Dummy</b> -</font></li>
370 <li><font face="Courier New"><b>InterfaceArchive</b> -</font></li>
|
371 dudhe.girish 1.6 <li><font face="Courier New"><b>rpm</b> - files for rpm installation
372 for Linux</font></li>
373 <li><font face="Courier New"><b>Schemas</b> - Schemas used in the
374 installation of Pegasus. This includes currently released versions
375 of the DMTF schemas in subdirectories (ex. CIM27) and Pegasus local
376 Schemas (ex. </font></li>
377 <li><font face="Courier New"><b>src</b> All Pegasus Source Files </font>
378 <ul>
379 <li><font face="Courier New"><b>ACEExample</b> Test directrory
380 with examples of the use of ACE (obsolete). </font></li>
381 <li><font face="Courier New"><b>Clients</b> Source for various
382 test clients and demonstration clients.</font></li>
383 <li><font face="Courier New"><b>CGICLIENT</b> Pegasus test client
384 that uses a WEB browser JAVA Java Client support modules </font></li>
385 <li><font face="Courier New"><b>Pegasus</b> - Core pegasus
386 modules. </font>
|
387 karl 1.1 <ul>
|
388 dudhe.girish 1.6 <li><font face="Courier New"><b>Client</b> Pegasus Client API
389 Tests depends tests </font></li>
390 <li><font face="Courier New"><b>Common</b> Pegasus Common
391 Functions (C++ source and headers tests Test programs for
392 the common functions</font></li>
393 <li><font face="Courier New"><b>Compiler</b> Pegasus MOF
394 compiler </font></li>
395 <li><font face="Courier New"><b>Config</b> Pegasus
396 Configuration functions</font></li>
397 <li><font face="Courier New"><b>Consumer</b> Indication
398 Consumer class header</font></li>
399 <li><font face="Courier New"><b>ControlProviders</b>
400 Implementation of Pegasus internal providers </font></li>
401 <li><font face="Courier New"><b>ExportClient</b> Client
402 connect code for export of indications</font></li>
403 <li><font face="Courier New"><b>ExportServer</b> Server code
404 for import of indications</font></li>
405 <li><font face="Courier New"><b>Handler</b> Indication
406 handlers. Today this includes cimxml, SNMP and email handlers</font></li>
407 <li><font face="Courier New"><b>HandlerService</b> Common code
408 for indication handler service</font></li>
409 dudhe.girish 1.6 <li><font face="Courier New"><b>IndicationService</b> Common
410 service functions for indication subscription processing</font></li>
411 <li><font face="Courier New"><b>Listener</b> Common code that
412 allows CIM Listeners to be created and connected.</font></li>
413 <li><font face="Courier New"><b>Protocol</b> Pegasus Client
414 HTTP/XML Protocol Modules depends </font></li>
415 <li><font face="Courier New"><b>Provider</b> Pegasus Provider
416 interface functions </font></li>
417 <li><font face="Courier New"><b>ProviderManager</b> Provider
418 Manager service that manages providers </font></li>
419 <li><font face="Courier New"><b>ProviderManager2</b> Pluggable
420 Provider Manager service. Today this is not enabled by
421 default It will become the Pegasus standard provider manager
422 at some time in the future but for now, see the release notes if you
423 want to enable it.</font></li>
424 <li><font face="Courier New"><b>Repository</b> Pegasus
425 Repository Interfaces and Simple Repository tests </font>
426 <ul>
427 <li><font face="Courier New">Tests for Repository
428 Functions </font></li>
|
429 karl 1.1 </ul>
430 </li>
|
431 dudhe.girish 1.6 <li><font face="Courier New"><b>Security</b> Authentication
432 and user support functions.</font></li>
433 <li><font face="Courier New"><b>Server</b> Pegasus Server
434 Modules </font></li>
435 <li><font face="Courier New"><b>WQL</b> the WQL query language
436 interpreter.</font></li>
437 </ul>
438 </li>
439 </ul>
440 </li>
441 <li><font face="Courier New"><b>Providers</b> Pegasus test and
442 required providers </font>
443 <ul>
444 <li><font face="Courier New"><b>generic</b> A number of
445 cross-platform providers </font></li>
446 <li><font face="Courier New">IndicationConsumer - Provider that
447 consumes indications</font></li>
448 <li><font face="Courier New"><b>Linux</b> - A number of linux
449 providers</font></li>
450 <li><font face="Courier New"><b>ManagedSystem</b> Providers
451 associated with managing the Pegasus System</font></li>
452 dudhe.girish 1.6 <li><font face="Courier New"><b>slp</b> - Provider for slp
453 service agent support</font></li>
454 <li><font face="Courier New"><b>statistic</b> - Providers for
455 Pegasus statistics.</font></li>
456 <li><font face="Courier New"><b>sample</b> Sample providers for
457 the major provider types.</font></li>
458 <li><font face="Courier New"><b>testproviders</b> </font></li>
459 </ul>
460 </li>
461 <li><font face="Courier New"><b>Server</b> Pegasus executable build </font></li>
462 <li><font face="Courier New"><b>slp</b> - </font></li>
463 <li><font face="Courier New"><b>Standard Includes</b> - </font></li>
464 <li><font face="Courier New"><b>test</b> - Directory of end-end tests
465 that are regularly conducted on Pegasus</font></li>
466 <li><font face="Courier New"><b>tools</b> MU and other utilities
467 written for Pegasus support </font></li>
468 <li><font face="Courier New"><b>Unsupported</b> Code that is made
469 available but is not supported or included in the normal make. </font></li>
470 <li><font face="Courier New"><b>WMIMapper</b> Pegasus implementation
471 that provides mapping to Microsoft WMI objects. </font></li>
472 </ul>
473 dudhe.girish 1.6 <p><font face="Courier New">Pegasus Run Time directory structure
474 (PEGASUS_HOME environment variable). Home directory for runtime. All
475 compiler, linker documentation creation, etc. are put here. </font> </p>
476 <ul>
477 <li><font face="Courier New"><b>bin</b> - Destination for executable
478 and DLL modules from Pegasus build. This directory should be make
479 public so that the test functions, clients, and cimserver can be
480 executed with minimum effort.</font></li>
481 <li><font face="Courier New"><b>DevManualHTML</b> - HTML output of the
482 Pegasus Manual. This is only created when the make file for this
483 manual is executed (doc/DevManual) and then contains the html
484 representing the document.</font></li>
485 <li><font face="Courier New"><b>apidochtml</b> - HTML output of the
486 creation of the public API document. This only exists when the make
487 file for the api document is executed (see doc/apidoc/Makefile)</font></li>
488 <li><font face="Courier New"><b>lib</b> - Destination for Pegasus LIB
489 modules </font></li>
490 <li><font face="Courier New"><b>log</b> - Standard location for
491 Pegasus Logs</font></li>
492 <li><font face="Courier New"><b>obj</b> - Destination for object
493 modules. Note that today, the trace file is located in the
494 dudhe.girish 1.6 PEGASUS_HOME directory, not in the log directory if Pegasus internal
495 tracing is enabled.</font></li>
496 <li><font face="Courier New"><b>repository</b> - This Directory
497 contains the created repository </font></li>
498 </ul>
499 <h1><a name="Pegasus Installation">Pegasus Installation</a> </h1>
500 <p>Pegasus today is provided only as a source distribution. Note that
501 there is code for a Linux RPM distribution but the project is not yet
502 releasing binaies.</p>
503 <p>To install Pegasus, you must check it out using CVS (Common Version
504 System) or download a snapshot. You download, compile, and use it. </p>
505 <p>For the snapshot, the installation of Pegasus involves expanding the
506 snapshot distribution files, building the runtime, the test files and
507 test clients, and building the repository. </p>
508 <h1><a name="Building Pegasus">Building Pegasus </a></h1>
509 <p>1. Check that you have requisite programs (listed in Pegasus
510 Dependencies). These include GNU Make, MU.EXE (if using Windows), Flex,
511 and Bison (Flex and Bison only required if changes will be made to the
512 MOF compiler or WQL parser). </p>
513 <p>Be sure these are on the path. </p>
514 <p>2. Define the following three environment variables: </p>
515 dudhe.girish 1.6 <ul>
516 <li><b>PEGASUS_ROOT</b> - this should be the "pegasus" directory
517 you've pulled from CVS </li>
518 <li><b>PEGASUS_HOME</b> - to point to a directory to contain output
519 binary files (e.g., set it to $HOME/pegasus_home). Then the output
520 will go into $HOME/pegasus_home/bin and $HOME/pegasus_home/lib </li>
521 <li><b>PEGASUS_PLATFORM</b> - this must be set to a supported platform
522 identifier.</li>
523 </ul>
524 <blockquote>
525 <p>This identifier has the following form: </p>
526 <p><font face="Courier New">
527 <Operating-System>_<Architecture>_<Compiler> </font></p>
528 <p>For example (Linux on IA32 platform using the GNU Compiler):
529 LINUX_IX86_GNU </p>
530 <p>For a complete list of platforms supported and platform support
531 keywords, refer to the platform make files found in directory <font
532 face="Courier New">pegasus/mak</font> </p>
533 </blockquote>
534 <p>Note: if you plan on doing parallel builds, you might consider
535 setting PEGASUS_HOME to something like this: </p>
536 dudhe.girish 1.6 <p><font face="Courier New"> $HOME/pegasus_home_LINUX_IX86_GNU </font></p>
537 <p>That way, the output of each build will be placed in its own
538 directory. </p>
539 <p>3. Now place $PEGASUS_HOME/bin on your path </p>
540 <p> and </p>
541 <p> Place $PEGASUS_HOME/lib on your LD_LIBRARY_PATH (for Unix only).
542 For RedHat/SuSE/UL, edit /etc/ld.so.conf and add $PEGASUS_HOME/lib </p>
543 <p>4. Change to the root of the Pegasus distribution and type "make"
544 (where make refers to GNU make). </p>
545 <p>5. Then create the repository, which is needed to serve data. "make
546 repository". Note that to create the additional namespaces, etc. that
547 represent the test support you can also execute "make testrepository:</p>
548 <p>6. To test the build type "make tests". The following make targets
549 are supported: </p>
550 <ul>
551 <li><default> - Build everything. </li>
552 <li>clean - Clean out all objects, libs, and executables. </li>
553 <li>depend - Create the dependencies. </li>
554 <li>repository - Create the repository in $PEGASUS_HOME/repository </li>
555 <li>tests - Execute all tests (except client server tests). </li>
556 <li>rebuild - clean, depend, <default> </li>
557 dudhe.girish 1.6 <li>world - depend, <default> </li>
558 </ul>
559 <p>The Pegasus Client server tests are executed separately from the
560 above because they require the initiation of separate process for the
561 Pegasus server and Pegasus client. To execute these tests please refer
562 to the scripts in pegasus/mak/BuildMakefile - refer to the prestarttests
563 and poststarttests. </p>
564 <p>For information on particular installation characteristics, tools,
565 etc. for each platform see the appropriate sections below: </p>
566 <p>Generally the build commands are as follows: </p>
567 <ol>
568 <li>There is a Makefile in the Pegasus root directory. Simply
569 executing make in the Pegasus root directory will make everything.
570 "make rebuild" will clean and rebuild everything. The "make rebuild"
571 will also populate the repository with the current CIM Schemas. </li>
572 <li>To test a fresh release, go to the pegasus root and type "<font
573 face="Courier New">make world</font>". This will build
574 dependencies, build binaries, and then run all tests except the
575 Client/Server tests. </li>
576 <li>To execute the basic test suite that is shipped with pegasus
577 type "make tests". This also reinstalls the repository. Running
578 dudhe.girish 1.6 "make -s tests" suppresses extraneous output such as the enter/leave
579 directory messages. </li>
580 <li>"make clean" removes all object and library files from the
581 structure. </li>
582 <li>A new build system has been added to Pegasus where a new CVS
583 checkout is done, built, and tests are run. Do it by: "make -f
584 mak/BuildMakefile cleanbuild" </li>
585 </ol>
586 <h1><a name="Populate the Repository">Populating the Pegasus Repository</a> </h1>
587 <p>Before using Pegasus you must populate the repository.. The makefile
588 does it all for you, but in case you are wondering what it does or how
589 to do it manually: </p>
|
590 karl 1.1 <ol>
|
591 dudhe.girish 1.6 <li>Register the MOF (Managed Object Format) file describing the
592 skeleton of the object. </li>
593 <li>Register a second MOF which only points out which lib*.so file to
594 be loaded when a specific object is activated. </li>
|
595 karl 1.1 </ol>
|
596 dudhe.girish 1.6 <p>This is done automatically for the providers included in Pegasus by
597 doing: make repository. </p>
598 <p>The 'make repository' in pegasus/Schemas does three things Runs MOF
599 compiler (cimmofl) on: -Schema v2.7 Generates the CIM Schema v2.7 in the
600 repository (skeleton of CIM objects) -PG_InterOp Internal to Pegasus
601 schema for operating (shutdown, add users, etc) CIM_Indication’s (SNMP,
602 Events, Alert, Threshold, etc) -PG_ManagedSystem Registers included CIM
603 Providers (libOSProvider.so, libDNSProvider.so, … ) in Pegasus (which
604 are located in src/Providers) </p>
605 <p>For more information about using the MOF compiler, refer to user's
606 manual on the openpegasus.org. </p>
607 <h1><a name="Testing a Pegasus Installation">Testing a Pegasus
608 Installation</a></h1>
609 <p>Pegasus includes an extensive set of test facilities as part of the
610 CVS enviromentthat can be executed including: </p>
611 <ul>
612 <li><b>Test Clients</b> - There are several clients that have been
613 built specifically to test Pegasus or parts of Pegasus including
614 TestClient, Client, CLI, ipinfo, osinfo, WbemEsec, etc. See the
615 src/Clients directory for more information. These programs require a
616 server complete with repository to be running. Note that some of these
617 dudhe.girish 1.6 tests use classes and instances that are only installed with the
618 "make testrepository" functions including test namespaces and extra
619 classes and instances in those namespaces and additional providers
620 from the providers/sample and proviers/testproviders directories.</li>
621 <li><b>Sample and test providers</b> - Test providers exist for the
622 major provider types in the providers/sample directories and the
623 providers/testProviders directory</li>
624 <li><b>Unit Tests</b> - Most Pegasus functions include unit tests for
625 the functions. These are normally executed with the "make tests"
626 command which can be executed at many different levels of the source
627 tree from the top level to execute all of the unit tests to
628 individual directories. Usually the unit test functions can be found in
629 test directories immediately below their corresponding source code
630 (i.e common/tests is the unit test functions for the common
631 directory). Unit tests are executed without the server being
632 operational and normally do not require the existence of a Class
633 repository.</li>
634 <li><b>An end-to-end Test Suite</b> - the directory "test" contains a
635 set of operations tests that cover the major CIM operations. See
636 the make file TestMakefile in the PEGASUS_ROOT directory to execute
637 these tests. This set of tests executes an extensive set of fixed
638 dudhe.girish 1.6 tests and compares the results against predefined results.</li>
639 </ul>
640 <h1><a name="Registering Providers in the Pegasus Environment">Registering
641 Providers in the Pegasus Environment</a></h1>
642 <p>Pegasus registers providers with a set of provider registration
643 classes, not using the provider qualifier as is done in most DMTF CIM
644 CIMOM implementations today. This set of classes is close to but not
645 exactly the same as the current DMTF definition (See the DMTF Interop
646 schema, experimental versions starting with 2.6). This will be
647 harmonized in the future when the DMTF scheme is moved to final status. </p>
648 <p>Registration is performed by defining a MOF for the instances of the
649 registration classes that represent the porvider module, providers,
650 classes, etc. to be registered. The easiest way to create a new
651 registration today is to copy from one of the existing registration
652 MOFs. See the providers/sample/load directory for examples of several
653 registration instance implementations that do work with Pegasus today.</p>
654 <h1><a name="The MU Utility">The MU Utility </a></h1>
655 <p>In order to provide a consistent build structure across multiple
656 platforms, we developed a small utility to provide a consistent set of
657 small utilities across these platforms. The MU utilityis a simple
658 utility that contains many commands. For example: </p>
659 dudhe.girish 1.6 <p><font face="Courier New"> C:\> mu rm myfile.cpp yourfile.cpp </font></p>
660 <p>You may type "mu" to get a list of valid commands. Here are some of
661 them: </p>
662 <p> rm, rmdirhier, mkdirhier, echo, touch, pwd, copy, move, compare
663 depend </p>
664 <p>The MU utility supports globing (expansion of wildcards) so you can
665 do things like this: </p>
666 <p><font face="Courier New"> C:\> mu rm *.obj *.exe </font></p>
667 <p>MU is required to build under the Windows environment. MU is
668 available as part of the distribution of Pegasus. </p>
669 <h1><a name="Notes about Building Pegasus on Linux">Notes about
670 Building Pegasus on Linux </a></h1>
671 <p>No problem. Just make sure you have the environment variables set
672 (PEASUS_HOME, PEGASUS_ROOT, PEGASUS_PLATFORM. For 32 bit linux, the
673 defintion of PEGASUS_PLATFORM is normally LINUX_IX86_GNU. </p>
674 <p> </p>
675 <h1><a name="Notes about Building Pegasus on Mac OS X/Darwin">Notes
676 about Building Pegasus on Mac OS X/Darwin</a><a
677 name="Notes about Building Pegasus on Linux"> </a></h1>
678 <p>No problem. Just make sure you have the environment variables set
679 (PEASUS_HOME, PEGASUS_ROOT, PEGASUS_PLATFORM. For Mac OS X/Darwin, the
680 dudhe.girish 1.6 defination of PEGASUS_PLATFORM is <br>
681 DARWIN_PPC_GNU.</p>
682 <p> </p>
683 <h1><a name="Notes about Building Pegasus with SSL">Notes about
684 Building Pegasus with SSL </a></h1>
685 <p>To build with SSL you need the OpenSSL libraries and header files.
686 They are NOT distributed with Pegasus. Make sure you have them in a
687 standard directory so Pegasus can find them. If that's not the case, set
688 the environment variable OPENSSL_HOME= to point where your OpenSSL
689 installation is. </p>
690 <p>Also have the PEGASUS_HAS_SSL=yes variable set. Then just run 'make'
691 in Pegasus directory and you will have Pegasus with SSL enabled. See
692 section "Creating SSL certificates" for more information of how to use
693 SSL. </p>
694 <h1><a
695 name="Building Pegasus on Windows 2000 or Windows XP With Microsoft Visual C++">Building
696 Pegasus on Windows 2k or Windows XP with Microsoft Visual C++ </a></h1>
697 <p>Use of Windows 2000 SP3 or later is recommended. Pegasus is
698 regularly tested on both Windows 2000 and Windows XP using the Microsoft
699 compilers.</p>
700 <p>Today we build Pegasus on Windows using a set of make files
701 dudhe.girish 1.6 contained in the source distribution, the Microsoft compilers (DevStudio
702 5.x is not supported, Visual Studio 6.0, SP5 is supported) and the
703 GNUMAKE make utility. Note that you MUST have the Pegasus <a
704 href="#The%20MU%20Utility">mu.exe </a>utility compiled and available
705 before trying to compile Pegasus on the normal windows platform. The
706 following is the basic setup steps for the environment. </p>
707 <p>Setup the environment variables and path for the Micrososft Visual C
708 compiler. Typically this can be done by running the VCVARS32.BAT file
709 supplied with Microsoft Visual C++. (contained in the same directory as
710 cl.exe). </p>
711 <p>For Windows, try the following for an example environment: </p>
712 <blockquote>
713 <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 <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>
714 </blockquote>
715 <h1><a name="Installing the Pegasus HTML Test Client">Installing the
716 Pegasus HTML Test Client</a></h1>
717 <p>This is a separate test tool that allows Pegasus requests to be
718 initiated from any WEB browser and that uses a WEB browser, CGI scripts
719 and HTML pages for the formatting and connections. It requires a WEB
720 server, etc. The instructions for setting up this environment are
721 maintained in a separate readme in the CGI directory. </p>
722 dudhe.girish 1.6 <h1><a name="Development with Pegasus and Pegasus Tools">Development
723 with Pegasus and Pegasus Tools</a></h1>
724 <p>ATTN: This section needs to be completed. It should reference the
725 more complete documentation.</p>
726 <h1><a name="Commands">Commands</a></h1>
727 <p>The manpages for each of the commands are in rpm/manLinux/man1.Z
728 directory (on CVS) </p>
729 <p>To see simple help for each of the commands, use the "-h" flag. </p>
730 <blockquote>
731 <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>
732 </blockquote>
733 <h1><a name="Creating SSL certifications">Creating SSL certifications </a></h1>
734 <p>Please follow section <a
735 href="#Notes%20about%20Building%20Pegasus%20with%20SSL">Notes on
736 building Pegasus with SSL</a> before embarking on this endeavour. <br>
|
737 konrad.r 1.4 <br>
|
738 dudhe.girish 1.6 Type these commands in your shell to create the SSL certifications. The
739 PEGASUS_ROOT and PEGASUS_HOME have to be set to your respective
740 installation and source directory. </p>
741 <blockquote>
742 <pre>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>cat $PEGASUS_HOME/key.pem $PEGASUS_HOME/cert.pem > $PEGASUS_HOME/server.pem<br>rm $PEGASUS_HOME/key.pem $PEGASUS_HOME/cert.pem<br>cp $PEGASUS_HOME/cert.pem $PEGASUS_HOME/client.pem<br><br></pre>
743 </blockquote>
744 <h1><a name="Configuring SSL">Configuring Pegasus to use SSL</a></h1>
745 <p>Please follow section <a
746 href="#Notes%20about%20Building%20Pegasus%20with%20SSL">Notes on
747 building Pegasus with SSL</a> and <a
748 href="#Creating%20SSL%20certifications">Creating SSL certifications</a>
749 before embarking on this endeavour.<br>
|
750 konrad.r 1.4 <br>
|
751 dudhe.girish 1.6 To configure Pegasus to take advantage of SSL, configure CIMServer to
752 have the following configuration options set to: </p>
753 <blockquote>
754 <pre> sslTrustFilePath=client.pem<br> sslCertificateFilePath=server.pem<br> sslKeyFilePath=file.pem<br> httpsPort=5989<br> enableHttpsConnection=true<br></pre>
755 </blockquote>
756 <p>using the <b>cimconfig</b> utility: </p>
757 <blockquote>
758 <pre> cimconfig -p -s enableHttpsConnection=true<br></pre>
759 </blockquote>
760 <p><br>
761 (The client.pem and server.pem are the certifications files created per
762 the steps in the earlier section). For good riddance you might consider
763 closing down the cleartext 5988 port. Modify your CIMServer
764 configuration to include: </p>
765 <blockquote>
766 <pre> enableHttpConnection=false<br></pre>
767 </blockquote>
768 <p>using <b>cimconfig</b>. </p>
769 <h1><a name="Configuring PAM">Configuring Pegasus to use PAM</a></h1>
770 <p>In order to use PAM Authentication you have to compile Pegasus with
771 one extra enviroment flags: </p>
772 dudhe.girish 1.6 <blockquote>
773 <pre> PEGASUS_PAM_AUTHENTICATION=1<br></pre>
774 </blockquote>
775 <p>You can also set the PEGASUS_ALWAYS_USE_PAM=1 flag to disable
776 Pegasus password authentication using a flag text-file (recommended). <br>
777 After compiling (refer to section <a href="#Building%20Pegasus">Building
778 Pegasus </a>for details), follow these two important steps: <br>
779 </p>
|
780 konrad.r 1.4 <ul>
|
781 dudhe.girish 1.6 <ul>
782 <p>a). Copy the rpm/wbem file in-to /etc/pam.d directory. This
783 notifies PAM what kind of libraries to use when authenticating
784 Pegasus.</p>
785 </ul>
786 <ul>
787 <p>b). Modify CIMServer configuration options: </p>
788 <blockquote>
789 <pre> usePAMAuthentication=true<br> enableAuthentication=true<br> </pre>
790 </blockquote>
791 <p>And if you want to allow 'root' to login (*not recommended*) </p>
792 <blockquote>
793 <pre> enableRemotePrivilegedUserAccess=true<br> </pre>
794 </blockquote>
795 <p>using the <b>cimconfig</b> utility, such as: </p>
796 <blockquote>
797 <pre> cimconfig -p -s usePAMAuthentication=true<br> </pre>
798 </blockquote>
|
799 konrad.r 1.4 </ul>
800 </ul>
|
801 dudhe.girish 1.6 <p>The user is authenticated using HTTP Basic method, thererfore it is
802 strongly suggested you use SSL connection instead of normal HTTP
803 connection. Refer to section <a href="#Configuring%20SSL">Configuring
804 Pegasus to use SSL</a> for more details on creating and using SSL keys. </p>
805 <h1><a name="Testing with ICU enabled">Testing with ICU enabled</a></h1>
806 <p>ICU (International Components for Unicode) refers to the set of
807 libraries that Pegasus uses to run globalized. For example: these
808 libraries are used to load messages in different languages, format
809 currency and numbers according to a specific locale etc. In order to
810 enable globalization in Pegasus, Pegasus must be built with ICU enabled,
811 ie. the right environment variables must be set prior to running
812 "make". Refer to the GlobalizationHOWTO.htm in the docs directory for
813 details. That said, when users run "make poststarttests" to verify the
814 integrity of a Pegasus download, a series of tests are run that require
815 the cimserver to be running. These tests currently depend on specific
816 messages returned from the server. When ICU is enabled, all messages
817 come from the resource bundles and these usually do not match the
818 hardcoded default messages within Pegasus. These hardcoded default
819 messages are what the various test programs expect in order to complete
820 successfully. If the ICU enabled server is started without disabling
821 message loading from the bundles, "make poststartests" will fail. In
822 dudhe.girish 1.6 order to run "make poststarttests" successfully with ICU enabled, an
823 environment variable called PEGASUS_USE_DEFAULT_MESSAGES must exist
824 prior to starting the server. Once this is defined, when the cimserver
825 starts, all messages generated will be the default hardcoded messages.
826 This will enable "make poststarttests" to complete successfully. Once
827 "make poststarttests" is complete, you should stop the cimserver and
828 then undefine PEGASUS_USE_DEFAULT_MESSAGES. If this variable is left
829 defined, Pegasus will not be able to load messages using ICU resource
830 bundles. </p>
831 <h1><a name="Pegasus Documentation">Pegasus Documentation</a></h1>
832 <p>The documentation is currently in preparation. Much of Pegasus is
833 documented in the PEGASUS PEPs which are the basis for approval of
834 Pegasus functionality, changes, plans, etc. These documents are openly
835 available on the PEGASUS web site. The preliminary documentation is not
836 provided with this release. The current documentation is maintained
837 both as a manual created under the tool DOC++ in the runtime
838 subdirectory manual/html (see doc/devManual to create), as an api
839 document also creatable from the source tree (see doc/apidoc) and as
840 other miscellaneous documentation in the doc directory. Also there is a
841 set of release notes. Normally the release notes for the current release
842 are available in the root source directory of CVS.</p>
843 dudhe.girish 1.6 <p>Note that the Pegasus WEB site at The Open Group will be the source
844 of most documentation in the future and today is the source of most
845 discussion and design documentation. </p>
846 <h1><a name="Participate!">Participate!</a></h1>
847 <p>We are looking for people who want to join the Pegasus work group
848 and contribute to effort of getting this Pegasus off the ground. Please
849 join the mailing list by visiting www.openpegasus.org, and click on
850 Mailing Lists. </p>
|
851 karl 1.1 </body>
|
852 konrad.r 1.3 </html>
|
Return to
readme.html
CVS log
Up to [Pegasus] / pegasus