Menu
▾
▴
[Sblim-commit] cmpi-network README,1.5,1.6 README.TEST,1.1,1.2
|
From: Heidi E. <hei...@us...> - 2005-04-19 08:33:51
|
Update of /cvsroot/sblim/cmpi-network In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv26359 Modified Files: README README.TEST Log Message: updated Installation Description Index: README =================================================================== RCS file: /cvsroot/sblim/cmpi-network/README,v retrieving revision 1.5 retrieving revision 1.6 diff -u -d -r1.5 -r1.6 --- README 18 Apr 2005 12:06:56 -0000 1.5 +++ README 19 Apr 2005 08:33:42 -0000 1.6 @@ -49,18 +49,34 @@ Build Instructions ------------------ + Prerequisites ............. -- CIMOM is installed -- CMPI (package cmpi-adapter) latest version -- CIM Schema Version 2.7 and higher loaded into the CIMOM's +- CIMOM installed +- CMPI enabled CIMOM +- CIM Schema Version 2.7 or higher loaded into the CIMOM's repository -- cmpi-base package installed +- to enable Indication support: + SBLIM package indication_helper installed +- to enable Testsuite support: + SBLIM package sblim-testsuite installed +- sblim-cmpi-devel package installed +- sblim-cmpi-base package installed + Building CIMOM and CMPI for this CIMOM ......................................... -Please follow the instructions in the README.cmpi file of -the cmpi-adapter package. + +CMPI support is available for SBLIM's sfcb, OpenPegasus, OpenCimom +(former SNIA CIMOM) and OpenWBEM + +- sfcb ... CMPI as only provider interface +- Pegasus ... CMPI is part of Pegasus +- OpenCimom ... install SBLIM cmpi-adapter for snia (please follow + the instructions in the README.cmpi file of SBLIM's + cmpi-adapter package) +- OpenWBEM ... CMPI is part of OpenWBEM + Building cmpi-base .................. @@ -70,37 +86,49 @@ Building cmpi-network ..................... -In order to compile and install cmpi-network instrumentation, -the path to the CMPI/cmpi-base header files and the library -path to libCMPIAdapter.so needs to be added to the search path. -This is configured by editing the "setting.cmpi" file. Once -all the pathes are configured, do : -- make -- make install -> copy all shared libraries to the library - path of the CIMOM; copy some header files - to the inlcude path (necessary if other - instrumentation packages use tool functions - of cmpi-network) -- make clean -> to delete all shared libs in this source - directory +This package is now GNU autotool enabled, refer to the file +named INSTALL for generic instructions. + +The generated configure script tries to determine where the CMPI header files +are located. For this purpose it searches a set of well-known locations. +The "canonical" location is /usr/include/cmpi or /usr/local/include/cmpi, +depending on how configure is invoked. + +Further, configure "determines" where providers are to be installed. Actually, +there's no detection logic. The provider directory will always be +/usr/lib/cmpi or /usr/local/lib/cmpi. If a CIM server requires a particular +directory this can be selected by specifying the PROVIDERDIR variable. + +And finally, configure tries to find out which CIM server type is being used. +This is necessary in order to select the appropriate schema and provider +registration technique. If the CIM server is not or incorrectly identified, +it is possible to specify it via the CIMSERVER variable. +Supported values are pegasus, sfcb, openwbem and sniacimom. + +For instance, in order to configure for a locally installed Pegasus you can +issue the following command: +./configure CIMSERVER=pegasus PROVIDERDIR=$PEGASUS_HOME/lib + + Load Schema into CIMOM's repository ................................... -with Pegasus : -.............. +with Pegasus/sfcb : +................. The loading and registering of the classes/associations and -their provider is done during the "make install" process. +their provider is done during the "make postinstall". with OpenCimom/SNIA CIMOM : ........................... Start the cimbrowser (/usr/sniacimom/bin). Load the schema -file Linux_Network.mof with "File" -> "Reload Mof" into the +file Linux_Base.mof with "File" -> "Reload Mof" into the namespace root/cimv2. Before at least CIM Core and System schemata have to be loaded into the repository. + Common Libraries ---------------- @@ -153,4 +181,4 @@ of providers. How to set up and drive the test is described in the -README file of the test sub directory. +README.TEST file. Index: README.TEST =================================================================== RCS file: /cvsroot/sblim/cmpi-network/README.TEST,v retrieving revision 1.1 retrieving revision 1.2 diff -u -d -r1.1 -r1.2 --- README.TEST 18 Apr 2005 12:06:56 -0000 1.1 +++ README.TEST 19 Apr 2005 08:33:42 -0000 1.2 @@ -7,28 +7,20 @@ Prerequisites ............. +- sblim-testsuite package propertly installed +- sblim-cmpi-base package propertly installed - sblim-cmpi-network package propertly installed -- testsuite package - - -Pepare Test -........... - -edit the makefile and set the path to your testsuite path Install Configuration Files ........................... -make test -... to test the existence of a testsuite directory - -make install -... to install the input files into the corresponding testsuite -directories +make install +... also installs the configuration file into the testsuite directory +as indicated by configure make uninstall -... to delete the cmpi-network specific files out of the testsuite +... also deletes the cmpi-network specific files out of the testsuite directories @@ -36,4 +28,4 @@ ........ Run the test in the testsuite dir by executing -. test-cmpi-network.sh +./test-cmpi-network.sh |
