Document title: OpenPegasus 2.10.0 Packaging Definition for Selected Platforms     Document details     Comments     Help with document reviews

[ ¤1] Pegasus Enhancement Proposal (PEP)

[ ¤2] PEP #: 351

[ ¤3] Title: OpenPegasus 2.10.0 Packaging Definition for Selected Platforms

[ ¤4] Version: 1.0

[ ¤5] Created: 19 January 2010

[ ¤6] Authors: Marek Szermutzky

[ ¤7] Status: Draft

[ ¤8] Version History:

[ ¤9] Version [ ¤10] Date [ ¤11] Author [ ¤12] Change Description
[ ¤13] 1.0 [ ¤14] 19 Jan 2010 [ ¤15] Marek Szermutzky
[ ¤16] 		[ ¤17]
  • [ ¤18] Initial Submission - based on  PEP#341 - OpenPegasus 2.9.0 Runtime Packaging Definition
    • [ ¤19]
    [ ¤20]     		[ ¤21]
    [ ¤22]     		[ ¤23]
    [ ¤24]     		[ ¤25]
    [ ¤26]

    [ ¤27]  

    [ ¤28] Table of Contents

    [ ¤29]
    [ ¤30] Abstract
    [ ¤31] Definition of the Problem
    [ ¤32] Proposed Solution
    [ ¤33]
    [ ¤34] OpenPegasus Directory Structure
    [ ¤35] OpenPegasus Packaged Files
    [ ¤36]
    [ ¤37] Library Files
    [ ¤38]
    [ ¤39] Library-level Versioning Strategy
    [ ¤40] OpenPegasus Libraries
    [ ¤41] OpenPegasus Provider Managers
    [ ¤42] OpenPegasus Provider Libraries
    [ ¤43] Executables Files
    [ ¤44]
    [ ¤45] OpenPegasus Administrative Commands
    [ ¤46] OpenPegasus Administrative Scripts
    [ ¤47] OpenPegasus User Commands
    [ ¤48] Documentation Files
    [ ¤49]
    [ ¤50] Unix Style Man Pages
    [ ¤51] Data Files
    [ ¤52]
    [ ¤53] Static Data Files
    [ ¤54] Variable Data Files
    [ ¤55] OpenPegasus Configuration Files
    [ ¤56] PAM Configuration Files
    [ ¤57] OpenPegasus Build and Install Steps
    [ ¤58]
    [ ¤59] Step 1: Create OpenPegasus Directory Structure
    [ ¤60] Step 2: Copy OpenPegasus Files
    [ ¤61] Step 3: Create OpenPegasus Host-Specific Files
    [ ¤62] Step 4: Create OpenPegasus Repository
    [ ¤63] Step 5: Update System Files

    [ (sahana_prabhakar) TDB needs to be replaced with Linux, HP-UX and Open VMS.
    (k_schopmeyer) Why not just remove the platform list so we have one less thing to modify with each release.
    (r_kumpf) Either way is okay with me. But since so much of the content of the document is platform-specific, I don't see any harm in listing the 3 platforms here. If another platform is documented, it would be a major change and this sentence here would be an easy, obvious change to go with it.
    ¤64]     Abstract: This PEP defines the recommended set of files for inclusion in this release of OpenPegasus.  In this version of the PEP, platform-specific options have been documented for the following platforms: TBD.

    [ ¤65] Note 1: The recommendations defined in this PEP are not intended to document the feature set included in any vendor's OpenPegasus-based product.  Rather, the purpose of this PEP is to provide input to vendors when making product decisions.
    [ ¤66]

    [ ¤67] This PEP defines the recommended set of files for inclusion in this release of OpenPegasus.

    [ ¤68] Definition of the Problem

    The purpose of this PEP is to provide vendors with a recommended set of configuration files, libraries, programs and documentation files for inclusion in an OpenPegasus Release.  Please refer to PEP 204 for instructions on creating OpenPegasus Linux binary and source RPMS.

    [ ¤69]  

    [ ¤70] Proposed Solution

    [ ¤71] OpenPegasus  Configure

    [ ¤72] Please consult the "Recommended OpenPegasus Build and Configuration Options for Selected Platforms" document, BuildAndReleaseOptions.html , in the pegasus/doc directory in CVS for the recommended environment and configuration settings for building OpenPegasus. 

    [ ¤73] OpenPegasus  Directory Structure

    [ ¤74] This section describes the recommended OpenPegasus runtime directory structure.  In addition, it describes the recommended directory permissions. 

    [ ¤75] There are three classes of OpenPegasus runtime directories:

    1. [ ¤76] FIXED LOCATION. Directory locations that are used by the CIM Server and fixed at build time.  A rebuild is required to change a FIXED LOCATION directory.  The runtime directory structure MUST be consistent with the build time definition of FIXED LOCATION directories.  Refer to PEP 308 for recommended default values.
    2. [ ¤77] CONFIGURABLE LOCATION. Directory locations that are used by the CIM Server and configurable using the cimconfig command.  All CONFIGURABLE LOCATION directories are assigned a default value for the directory location. The runtime directory structure WILL assume the default value. Refer to PEP 308 for recommended default values.
    3. [ ¤78] INSTALLATION DEFINED LOCATION. Directory locations that are NOT used by the CIM Server but exist as part of the CIM Server runtime environment. A default location will be defined and used for the directory location.

    [ (venkat_puvvada) I think the we need to mention about PEGASUS_FLAVOR option here, something like :

    The following default installation directories will change if the PEGASUS_FLAVOR option is set. See     PEP 350 for more details.

    ¤79]      

    [ ¤104]  

    [ ¤348]  

    [ ¤349] Although not included in this release, the following directories are planned for future release.
    [ ¤350]  

    [ ¤372]  

    [ ¤373]  OpenPegasus  Packaged Files

    [ ¤374] Library Files

    [ ¤375] Library-level Versioning Strategy

    [ ¤376] Support for forward-compatibility is a fundamental design principle for the OpenPegasus project. Our expectation is that well-behaved OpenPegasus Providers or Clients will continue to work with a minor version upgrade of OpenPegasus.  However, in the future, we do anticipate that there will be a need to release changes that do not support forward-compatibility.  This would happen in situations where the cost (i.e., development effort, performance, resource utilization) of supporting compatibility has become prohibitive. To minimize the impact of major version upgrades, OpenPegasus has been designed to allow multiple versions of a library to coexist in the same runtime environment. This way, new programs will be allowed to take advantage of the new features and old programs will continue to run.

    [ ¤377] To allow multiple versions of a library, OpenPegasus recommends the use of library-level versioning strategy.  With this strategy, a library file is created with a version suffix, $(VER_SUFFIX) (e.g., .1).  This version suffix is changed only when the new version of the library will not support CIM Providers and/or CIM Clients developed using early versions of the library (i.e., SDK).  It is important to note that the library version suffix is NOT the same as the product version. 

    [ ¤378] In addition to the library file, a symbolic link, that points to the latest version of the library, is created using the standard library suffix for the target operating system, $(LIB_SUFFIX) (e.g., .so).   CIM Client and Provider developers would use this link to ensure that they are  linking with the most recent version of the library.  When building a CIM Client or CIM Provider, developers should use include the appropriate link option (e.g., -h on Linux) to ensure that the specific version of the library used to build the product will be loaded during runtime.

    [ ¤379] The following table describes the OpenPegasus library versions and suffixes.

    [ ¤395] OpenPegasus  Libraries

    [ ¤396] This section documents the recommended set of library files to be included with this release of OpenPegasus. Files in this section are expected to be rooted in a single directory $(PEGASUS_DEST_LIB_DIR).

    [ ¤397] Source Location: $(PEGASUS_HOME)/lib

    [ ¤398] The following table describes the permissions that should be assigned to the files in the $(PEGASUS_DEST_LIB_DIR) directory.

    [ ¤412]  

    [ ¤413] The following files should be included in the $(PEGASUS_DEST_LIB_DIR) directory.

    [ ¤447] In addition, the following links should be included in the $(PEGASUS_DEST_LIB_DIR) directory.
    [ ¤448]         
    [ ¤449]           libCIMxmlIndicationHandler.$(LIB_SUFFIX) -> libCIMxmlIndicationHandler.$(LIB_SUFFIX).$(VER_SUFFIX)
    [ ¤450]           libDefaultProviderManager.$(LIB_SUFFIX) -> libDefaultProviderManager.$(LIB_SUFFIX).$(VER_SUFFIX)
    [ ¤451]           libpegclient.$(LIB_SUFFIX) -> libpegclient.$(LIB_SUFFIX).$(VER_SUFFIX)
    [ ¤452]           libpegcommon.$(LIB_SUFFIX) -> libpegcommon.$(LIB_SUFFIX).$(VER_SUFFIX)
    [ ¤453]           libpegprovider.$(LIB_SUFFIX) -> libpegprovider.$(LIB_SUFFIX).$(VER_SUFFIX)
    [ ¤454]           libsnmpIndicationHandler.$(LIB_SUFFIX) -> libsnmpIndicationHandler.$(LIB_SUFFIX).$(VER_SUFFIX)

    [ ¤455]  

    [ ¤456] The following table describes the recommended install, upgrade and remove behavior for the OpenPegasus libraries and links.

    [ ¤469] OpenPegasus Provider Managers

    [ ¤470] This section documents the dynamically loaded provider managers packaged with OpenPegasus.  Files in this section are expected to be rooted in a single directory $(PEGASUS_PROVIDER_MANAGER_LIB_DIR).

    [ ¤471] Source Location: $(PEGASUS_HOME)/lib

    [ ¤472] The following table describes the permissions that should be assigned to the files in the $(PEGASUS_PROVIDER_MANAGER_LIB_DIR) directory.

    [ ¤486]  

    [ ¤487] The following files should be included in the $(PEGASUS_PROVIDER_MANAGER_LIB_DIR) directory.

    [ ¤489] In addition, the following links should be included in the $(PEGASUS_DEST_LIB_DIR) directory.
    [ ¤490]        
    [ ¤491]           libCMPIProviderManager.$(LIB_SUFFIX) -> libCMPIProviderManager.$(LIB_SUFFIX).$(VER_SUFFIX)

    [ ¤492] OpenPegasus Provider Libraries

    [ ¤493] This section documents the Providers packaged with OpenPegasus. Files in this section are expected to be rooted in a single directory $(PEGASUS_PROVIDER_LIB_DIR).  Note that the $(PEGASUS_PROVIDER_LIB_DIR) directory MUST be included as one of the values of the providerDir configuration parameter.   Note that this directory may contain symbolic links to the actual files, there is no requirement for the actual library file to be placed in this directory.

    [ ¤494] Packaged Providers

    [ ¤495]
    [ ¤496] Operating System Provider
    [ ¤497] Computer System Provider
    [ (sahana_prabhakar) Apart from these 3, Processor and IP provider are packed with OP as well. The following is the list of packaged providers on HP-UX : Operating System Provider Computer System Provider Process Provider IP Provider DNS Provider NTP Provider NIS Provider
    ¤498]     Process Provider
    [ ¤499]  
    [ ¤500] The following table describes the permissions that should be assigned to the links or files in the $(PEGASUS_PROVIDER_LIB_DIR) directory.
    [ ¤501]
    [ ¤502]
    [ ¤516]
    [ ¤517]  

    [ ¤518] The following files should be included in the $(PEGASUS_PROVIDER_LIB_DIR) directory.

    [ ¤519]
    [ ¤520]  
    [ ¤521] libComputerSystemProvider.$(LIB_SUFFIX).$(VER_SUFFIX)
    [ ¤522] libOSProvider.$(LIB_SUFFIX).$(VER_SUFFIX)
    [ ¤523] libProcessProvider.$(LIB_SUFFIX).(VER_SUFFIX)

    [ ¤524]
    [ ¤525]  

    [ ¤526] Provider Library Versioning

    [ ¤527] The CIM Server will use the $(LIB_SUFFIX) when attempting to dynamically load a Provider.  This allows Provider developers to use a resource-specific  library versioning strategy. Providers are not required to use this same version suffix as the OpenPegasus libraries.

    [ ¤528] The following links should be included in the $(PEGASUS_PROVIDER_LIB_DIR) directory.

    [ ¤534] The following table describes the recommended install, upgrade and remove behavior for the packaged Provider libraries and links.

    [ ¤547] Executable Files

    [ ¤548] The following table describes the OpenPegasus executable suffixes.

    [ ¤559] OpenPegasus Administrative Commands

    [ ¤560] This section documents the maintenance or administrative commands included with this release of OpenPegasus. Files in this section are expected to be rooted in a single directory $(PEGASUS_SBIN_DIR).

    [ ¤561] Source Location: $(PEGASUS_HOME)/sbin

    [ ¤562] The following table describes the permissions that should be assigned to the files in the $(PEGASUS_SBIN_DIR) directory.

    [ ¤576]  

    [ ¤577] The following files should be included in the $(PEGASUS_SBIN_DIR) directory.

    [ ¤588] The following table describes the recommended install, upgrade and remove behavior for the OpenPegasus commands.

    [ ¤595] OpenPegasus Administrative Scripts

    [ ¤596] This section documents the scripts included with this release of OpenPegasus. Files in this section are expected to be rooted in a single directory $(PEGASUS_SCRIPTS_DIR).

    [ ¤597] Source Location: pegasus/rpm/tog-specfiles

    [ ¤598] The following table describes the permissions that should be assigned to the files in the $(PEGASUS_SCRIPTS_DIR) directory.

    [ ¤612]  

    [ ¤613] The following files should be included in the $(PEGASUS_SCRIPTS_DIR) directory.

    [ ¤616] The following table describes the recommended install, upgrade and remove behavior for the OpenPegasus commands.

    [ ¤623] OpenPegasus User Commands

    [ ¤624] This section documents the user commands included with this release of OpenPegasus. Files in this section are expected to be rooted in a single directory $(PEGASUS_BIN_DIR).

    [ ¤625] Source Location: $(PEGASUS_HOME)/bin

    [ ¤626] The following table describes the permissions that should be assigned to the files in the $(PEGASUS_BIN_DIR) directory.

    [ ¤640]  

    [ ¤641] The following files should be included in the $(PEGASUS_BIN_DIR) directory.

    [ ¤649]  

    [ ¤650] The following table describes the recommended install, upgrade and remove behavior for the OpenPegasus commands.

    [ ¤657]
    [ ¤658]

    [ ¤659] Documentation Files

    [ ¤660] Unix Style Man Pages

    [ ¤661] This section describes the packaging for Operating Systems that support Unix style man pages. Files in this section are expected to be rooted in a single directory $(PEGASUS_MAN_DIR).

    [ ¤662] Source Location: $(ROOT)/rpm/manLinux/man1.Z/
    [ ¤663]                              $(ROOT)/rpm/manLinux/man8.Z

    [ ¤664] The following table describes the permissions that should be assigned to the files in the $(PEGASUS_MAN_DIR) subdirectories.

    [ ¤678]  

    [ ¤679] The following man pages should be included in the $(PEGASUS_MAN_DIR)/man1 directory.

    [ ¤685]  

    [ ¤686] The following man pages should be included in the $(PEGASUS_MAN_DIR)/man8 directory.

    [ ¤692] The following table describes the recommended install, upgrade and remove behavior for the OpenPegasus man pages.

    [ ¤699] User Documentation

    [ ¤700] Files in this section are expected to be rooted in a single directory $(PEGASUS_DOC_DIR).

    [ ¤701] The following table describes the permissions that should be assigned to the files in the $(PEGASUS_DOC_DIR) directory.

    [ ¤715]
    [ ¤716]
    [ ¤717] The following documents are included with OpenPegasus.

    [ ¤718] Staging Location: $(PEGASUS_HOME)/$(PEGASUS_STAGING_DIR)/$(PEGASUS_DOC_DIR)

    [ ¤719] Target Location: $(PEGASUS_DOC_DIR)


    [ ¤730]

    [ ¤731] The following table describes the recommended install, upgrade and remove behavior for the OpenPegasus documentation files.

    [ ¤738]
    [ ¤739]

    [ ¤740] Data Files

    [ ¤741] This section describes the OpenPegasus data files.

    [ ¤742] There are three classes of OpenPegasus data files:

    1. [ ¤743] FIXED LOCATION. Absolute names that are used by the CIM Server and fixed at build time.  A rebuild is required to change the file name.  The runtime file structure MUST be consistent with the build time definition of the FIXED LOCATION files. Refer to PEP 308 for recommended default values.
    2. [ ¤744] CONFIGURABLE LOCATION. Absolute file names that are used by the CIM Server and configurable using the cimconfig command.  All CONFIGURABLE LOCATION files are assigned a default value for the absolute file name. The runtime file structure WILL assume the default value. Refer to PEP 308 for recommended default values.
    3. [ ¤745] INSTALLATION DEFINED LOCATION. Files that are NOT used by the CIM Server but exist as part of the CIM Server runtime environment. Default absolute file names will be defined for these directories.

    [ ¤746]  

    [ ¤776] Static Data Files

    [ ¤777] This section describes OpenPegasus data files that do not change during normal operation.

    [ ¤778] Schema Files

    [ ¤779] The following table describes the permissions that should be assigned to the $(PEGASUS_MOF_DIR) directory.

    [ ¤780] Document Designation
    [ ¤781] Configuration Option    		 [ ¤782] Operating System [ ¤783] Location [ ¤784] Directory
    [ ¤785] Owner
    [ ¤786] Group    		 [ ¤787] Permissions
    [ ¤788] $(PEGASUS_MOF_DIR)
    [ ¤789]      		 [ ¤790] Linux [ ¤791] /usr/share/Pegasus/mof [ ¤792] root/pegasus [ ¤793] drwxr-xr-x
    [ ¤794] HP-UX [ ¤795] /opt/wbem/mof [ ¤796] bin/bin [ ¤797] dr-xr-xr-x
    [ ¤798] OpenVMS [ ¤799] /opt/wbem/mof [ ¤800] system [ ¤801] S:wred,O:re,G:re,W:e

    [ ¤802] The following table describes the permissions that should be assigned to the files in the $(PEGASUS_MOF_DIR) subdirectories.

    [ ¤803]
    [ ¤804]  
    [ ¤805] Operating System [ ¤806] Packaged or Generated? [ ¤807] File
    [ ¤808] Owner/Group [ ¤809] Permissions
    [ ¤810] Linux [ ¤811] Packaged [ ¤812] root/pegasus [ ¤813] -rw-r--r--
    [ ¤814] HP-UX [ ¤815] Packaged [ ¤816] bin/bin [ ¤817] -r--r--r--
    [ ¤818] OpenVMS [ ¤819] Packaged [ ¤820] system [ ¤821] S:wred,O:r,G:r,W:r

    [ ¤822]  

    [ ¤823] The following OpenPegasus specific mof files are packaged in the directory $(PEGASUS_MOF_DIR)/Pegasus.  Note: The class definitions defined in the pegasus/Schemas/Pegasus/Internal/VER20 mof files are for internal use only and subject to change.  Please consult the OpenPegasus External Interface Definition document, ExternalInterface.html, in the pegasus/doc directory in CVS for a list of the mof files included in the OpenPegasus external definition.

    [ ¤824]
    [ ¤825] Source Location: pegasus/Schemas/Pegasus/Internal/VER20
    [ ¤834] Source Location: pegasus/Schemas/Pegasus/InterOp/VER20
    [ ¤839] Source Location: pegasus/Schemas/Pegasus/ManagedSystem/VER20

    [ ¤848]
    [ ¤849]

    [ ¤850] The following table describes the recommended install, upgrade and remove behavior for the OpenPegasus mof files.

    [ ¤857]
    [ ¤858]

    [ ¤859] Variable Data Files

    [ ¤860] This section describes OpenPegasus data files that change during normal operation. Files in this section are expected to be rooted in a single directory $(PEGASUS_VARDATA_DIR).

    [ ¤861] The following table describes the permissions that should be assigned to the files in the $(PEGASUS_VARDATA_DIR) directory.

    [ ¤862] Document Designation
    [ ¤863] Configuration Option    		 [ ¤864] Packaged or Generated? [ ¤865] Operating System [ ¤866] Location [ ¤867] Directory
    [ ¤868] Owner
    [ ¤869] Group    		 [ ¤870] Permissions
    [ ¤871] $(PEGASUS_CIMSERVER_START_LOCK_FILE) [ ¤872] Generated [ ¤873] Linux [ ¤874] /var/run/tog-pegasus/
    [ ¤875] cimserver_start.lock    		 [ ¤876] root/root

    [ ¤877]  cimsvr cimsvr (PS)

    		 [ ¤878] -rw-------
    [ ¤879] HP-UX [ ¤880]
    [ ¤881]     		[ ¤882]
    [ ¤883]     		[ ¤884]
    [ ¤885]
    [ ¤886] OpenVMS [ ¤887]
    [ ¤888]     		[ ¤889]
    [ ¤890]     		[ ¤891]
    [ ¤892]
    [ ¤893] $(PEGASUS_CURRENT
    [ ¤894] _CONFIG_FILE)    		 [ ¤895] Generated [ ¤896] Linux [ ¤897] $(PEGASUS_VARDATA_DIR)/
    [ ¤898] cimserver_current.conf    		 [ ¤899] root/root [ ¤900] -rw-r--r--
    [ ¤901] HP-UX [ ¤902] /var/opt/wbem/pegasus/
    [ ¤903] cimserver_current.conf    		 [ ¤904] root/root [ ¤905] rw-r--r--
    [ ¤906] OpenVMS [ ¤907] /var/opt/wbem/pegasus/
    [ ¤908] cimserver_current.conf    		 [ ¤909] system [ ¤910] S:wred,O:wr,G:r,W:r
    [ ¤911] $(PEGASUS_PLANNED
    [ ¤912] _CONFIG_FILE)
    [ ¤913]      		 [ ¤914] Packaged [ ¤915] Linux [ ¤916] $(PEGASUS_VARDATA_DIR)/

    [ ¤917] cimserver_planned.conf

    		 [ ¤918] root/root [ ¤919] -rw-r--r--
    [ ¤920] HP-UX [ ¤921] /var/opt/wbem/

    [ ¤922] cimserver_planned.conf

    [ ¤923]

    		[ ¤924] root/root [ ¤925] rw-r--r--
    [ ¤926] OpenVMS [ ¤927] /var/opt/wbem/

    [ ¤928] cimserver_planned.conf

    		 [ ¤929] system [ ¤930] S:wred,O:wr,G:r,W:r
    [ ¤931] $(PEGASUS_PID_FILE) [ ¤932] Generated [ ¤933] Linux [ ¤934] /var/run/tog-pegasus/cimserver.pid [ ¤935] root/root

    [ ¤936] cimsvr/cimsvr (PS)

    		 [ ¤937] -rw-------
    [ ¤938] HP-UX [ ¤939] /etc/opt/wbem/
    [ ¤940] cimserver_start.conf    		 [ ¤941] root/root [ ¤942] rw-r--r--
    [ ¤943] OpenVMS [ ¤944] /var/opt/wbem/
    [ ¤945] cimserver_start.conf    		 [ ¤946] system [ ¤947] S:wred,O:wr,G:r,W:r
    [ ¤948] $(PEGASUS_LOCAL_AUTH_DIR) [ ¤949] Generated [ ¤950] Linux [ ¤951] /$(PEGASUS_VARDATA_DIR)/cache/localauth [ ¤952] root/pegasus [ ¤953] drwxr-xr-x
    [ ¤954] HP-UX [ ¤955] /var/opt/wbem/localauth [ ¤956] bin/bin [ ¤957] dr-xr-xr-x
    [ ¤958] OpenVMS [ ¤959] /var/opt/wbem/localauth [ ¤960] system [ ¤961] S:wred,O:re,G:re,W:e
    [ ¤962] $(PEGASUS_LOCAL_DOMAIN
    [ ¤963] _SOCKET_DIR)    		 [ ¤964] Generated [ ¤965] Linux [ ¤966] /var/run/tog-pegasus/socket [ ¤967] root/pegasus

    [ ¤968] cimsvr/cimsvr (PS)

    		 [ ¤969] drwxr-xr-t
    [ ¤970] HP-UX [ ¤971] /var/opt/wbem/socket/ [ ¤972] bin/bin [ ¤973] dr-xr-xr-t
    [ ¤974]   [ ¤975]   [ ¤976]   [ ¤977]  
    [ ¤978] $(PEGASUS_CIMSERVER
    [ ¤979] _RANDOMFILE)
    [ ¤980]
    [ ¤981] Note: This file is only required on platforms that do not support /dev/(u)random.    		 [ ¤982] Generated [ ¤983] Linux [ ¤984] N/A [ ¤985] N/A [ ¤986] N/A
    [ ¤987] HP-UX [ ¤988]   [ ¤989]   [ ¤990]  
    [ ¤991] OpenVMS [ ¤992] /var/opt/wbem/ssl.rnd [ ¤993] system [ ¤994] S:wred,O:r,G:r,W:
    [ ¤995] $(PEGASUS_TRACE_DIR) [ ¤996] Generated [ ¤997] Linux [ ¤998] $(PEGASUS_VARDATA_DIR)/cache/trace [ ¤999] root/pegasus [ ¤1000] drwxrwxrwt
    [ ¤1001]   [ ¤1002] HP-UX [ (sahana_prabhakar) /var/opt/wbem/trace
    ¤1003]
    [ ¤1004]     		[ (sahana_prabhakar) cimsrvr/cimsrvr
    ¤1005]
    [ ¤1006]     		[ (sahana_prabhakar) drwxrwxrwt
    ¤1007]
    [ ¤1008]
    [ ¤1009]   [ ¤1010] OpenVMS [ ¤1011]   [ ¤1012]   [ ¤1013]
    [ ¤1014]
    [ ¤1015] $(PEGASUS_CORE_DIR) [ ¤1016] Generated [ ¤1017] Linux [ ¤1018] $(PEGASUS_VARDATA_DIR)/cache/trace [ ¤1019] root/pegasus [ ¤1020] drwxrwxrwt
    [ ¤1021]   [ ¤1022] HP-UX [ ¤1023]
    [ ¤1024]     		[ ¤1025]
    [ ¤1026]     		[ ¤1027]
    [ ¤1028]
    [ ¤1029]   [ ¤1030] OpenVMS [ ¤1031]   [ ¤1032]   [ ¤1033]
    [ ¤1034]

    [ ¤1035]  

    [ ¤1036] $(PEGASUS_PLANNED_CONFIG_FILE)

    [ ¤1037] The $(PEGASUS_PLANNED_CONFIG_FILE) file is not intended to be user editable. The cimconfig utility should be used to modify this file.  Default settings for configuration options are defined in the source and can vary by vendor, Operating System and release.   In order to differentiate between "customer-defined" values and "default-settings", default-settings are not stored in this file.  With the exception of the following comment, initial version of the $(PEGASUS_PLANNED_CONFIG_FILE) file is empty.

    [ ¤1054] The following table describes the upgrade strategy for the PEGASUS_PLANNED_CONFIG_FILE.


    [ ¤1071] The following generated data files and directories are removed on upgrade and erase: $(PEGASUS_PLANNED_CONFIG_FILE), $(PEGASUS_PID_FILE), $(PEGASUS_LOCAL_AUTH_DIR), $(PEGASUS_LOCAL_DOMAIN_SOCKET_DIR) and $(PEGASUS_TRACE_DIR).
    [ ¤1072] OpenPegasus Configuration Files

    [ ¤1073] This section describes OpenPegasus configuration files. Files in this section are expected to be rooted in a single directory $(PEGASUS_CONFIG_DIR).


    [ ¤1091]

    [ ¤1092] The following table describes the recommended install, upgrade and remove behavior for the OpenPegasus ssl.cnf file.

    [ ¤1104] OpenSSL PEM Files

    [ ¤1105] This section describes the OpenSSL PEM files. Files in this section are expected to be rooted in a single directory $(PEGASUS_PEM_DIR).

    [ ¤1106] File Name

    [ ¤1107] see PEP 308

    		 [ ¤1108] Packaged or Generated? [ ¤1109] File Name [ ¤1110] Operating System [ ¤1111] File
    [ ¤1112] Owner/Group [ ¤1113] Permissions
    [ ¤1114] sslKeyFilePath
    [ ¤1115] $(PEGASUS_SSL_KEY_FILE)    		 [ ¤1116]

    [ ¤1117] Generated

    		 [ ¤1118] file.pem [ ¤1119] Linux [ ¤1120] root/root [ ¤1121] -r--------
    [ ¤1122]   [ ¤1123] HP-UX [ ¤1124] bin/bin [ ¤1125] -r--------
    [ ¤1126]   [ ¤1127] OpenVMS [ ¤1128] system [ ¤1129] S:wred,O:r,G:,W
    [ ¤1130] sslTrustStore
    [ ¤1131] $(PEGASUS_SSL_TRUSTSTORE)    		 [ ¤1132] Empty File [ ¤1133] client.pem [ ¤1134] Linux [ ¤1135] root/root [ ¤1136] -r--r--r--
    [ ¤1137]   [ ¤1138] HP-UX [ ¤1139] root/sys [ ¤1140] -r--------
    [ ¤1141]   [ ¤1142] OpenVMS [ ¤1143] system [ ¤1144] S:wred,O:r,G:,W:
    [ ¤1145] sslCertificateFilePath

    [ ¤1146] $(PEGASUS_SSL_CERT_FILE)

    		 [ ¤1147]

    [ ¤1148] Generated

    		 [ ¤1149] server.pem [ ¤1150] Linux [ ¤1151] root/root [ ¤1152] -r--r--r--
    [ ¤1153]   [ ¤1154] HP-UX [ ¤1155] root/sys [ ¤1156] -r--------
    [ ¤1157]   [ ¤1158] OpenVMS [ ¤1159] system [ ¤1160] S:wred,O:r,G:,W:

    [ ¤1161]

    [ ¤1162] The following table describes the recommended install, upgrade and remove behavior for the OpenPegasus *.pem files.

    [ ¤1174] PAM Configuration Files

    [ ¤1175] This section describes OpenPegasus configuration files.

    [ ¤1204]
    [ ¤1205]

    [ ¤1206] The following table describes the upgrade strategy for the PAM configuration files.

    [ ¤1236] Repository Data Files

    [ ¤1237] This section describes the installation of the Repository Data Files. Files in this section are expected to be rooted in a single directory $(PEGASUS_REPOSITORY_DIR).

    [ ¤1238] The following table describes the recommended install, upgrade and remove behavior for the OpenPegasus Repository data files.

    [ ¤1255] OpenPegasus  Build & Installs Steps

    [ ¤1256] For supported Operating Systems, pegasus/Makefile.Release can be used to perform the steps necessary to build and place the necessary OpenPegasus release files in a staging directory, PEGASUS_STAGING_DIR. 

    [ ¤1258] For successful operation, Makefile.Release is dependent on the existence of an operating system dependent file  that defines the setting of key environment variables.  Two sample files have been placed in the pegasus directory: env_var_HPUX.status and env_var_Linux.status.

    [ ¤1259] Use of this utility has been tested on the following platforms.

    [ ¤1262] References

    [ ¤1263] Note: Starting with the OpenPegasus 2.9.0 release, the OpenPegasus Build and Configuration Options document is available in OpenPegasus CVS Repository, pegasus/doc/BuildAndReleaseOptions.html.

    1. [ ¤1264] PEP#174 - Recommended OpenPegasus 2.4 Build and Configuration Options
    2. [ ¤1265] PEP#200 - Recommended OpenPegasus 2.5 Build and Configuration Options
    3. [ ¤1266] PEP#237 - Recommended OpenPegasus 2.5.1 Build and Configuration Options
    4. [ ¤1267] PEP#277 - Recommended OpenPegasus 2.6.0 Build and Configuration Options for Selected Platforms
    5. [ ¤1268] PEP#292 - Recommended OpenPegasus 2.7.0 Build and Configuration Options for Selected Platforms
    6. [ ¤1269] PEP#308 - Recommended OpenPegasus 2.8.0 Build and Configuration Options for Selected Platforms

    [ ¤1270] Rationale

    [ ¤1271]

    [ ¤1272] Schedule

    [ ¤1273]

    [ ¤1274] Discussion

    [ ¤1275]

    [ (k_schopmeyer) I believe that we should update the copyright statement
    ¤1276]     Copyright (c) 2006 Hewlett-Packard Development Company, L.P.; IBM Corp.;
    [ ¤1277] EMC Corporation; Symantec Corporation; The Open Group.
    [ ¤1278]
    [ ¤1279] Permission is hereby granted, free of charge, to any person obtaining a copy
    [ ¤1280] of this software and associated documentation files (the "Software"), to
    [ ¤1281] deal in the Software without restriction, including without limitation the
    [ ¤1282] rights to use, copy, modify, merge, publish, distribute, sublicense, and/or
    [ ¤1283] sell copies of the Software, and to permit persons to whom the Software is
    [ ¤1284] furnished to do so, subject to the following conditions:
    [ ¤1285]
    [ ¤1286] THE ABOVE COPYRIGHT NOTICE AND THIS PERMISSION NOTICE SHALL BE INCLUDED IN
    [ ¤1287] ALL COPIES OR SUBSTANTIAL PORTIONS OF THE SOFTWARE. THE SOFTWARE IS PROVIDED
    [ ¤1288] "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT
    [ ¤1289] LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR
    [ ¤1290] PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT
    [ ¤1291] HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN
    [ ¤1292] ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
    [ ¤1293] WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

    [ ¤1294] Template last modified: March 26th 2006 by Martin Kirk
    [ ¤1295]     Template version: 1.11