Changes between Version 31 and Version 32 of InstallationGuide
- Timestamp:
- 07/06/13 20:37:40 (11 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
InstallationGuide
v31 v32 173 173 <Configuration> 174 174 <sm:ModuleManager> 175 <sm:Directory>/ opt/plgrid/qcg/lib/qcg-core/modules/</sm:Directory>176 <sm:Directory>/ opt/plgrid/qcg/lib/qcg-comp/modules/</sm:Directory>175 <sm:Directory>/usr/lib64/qcg-core/modules/</sm:Directory> 176 <sm:Directory>/usr/lib64/qcg-comp/modules/</sm:Directory> 177 177 </sm:ModuleManager> 178 178 179 179 <sm:Service xsi:type="qcg-compd" description="QCG-Computing"> 180 180 <sm:Logger> 181 <sm:Filename>/ opt/plgrid/var/log/qcg-comp/qcg-compd.log</sm:Filename>181 <sm:Filename>/var/log/qcg/qcg-comp/qcg-compd.log</sm:Filename> 182 182 <sm:Level>INFO</sm:Level> 183 183 </sm:Logger> … … 190 190 <sm:Authentication> 191 191 <sm:Module xsi:type="sm:atc_transport_gsi.service"> 192 <sm:X509CertFile>/ opt/plgrid/qcg/etc/qcg-comp/certs/qcgcert.pem</sm:X509CertFile>193 <sm:X509KeyFile>/ opt/plgrid/qcg/etc/qcg-comp/certs/qcgkey.pem</sm:X509KeyFile>192 <sm:X509CertFile>/etc/grid-security/hostcert.pem</sm:X509CertFile> 193 <sm:X509KeyFile>/etc/grid-security/hostkey.pem</sm:X509KeyFile> 194 194 </sm:Module> 195 195 </sm:Authentication> … … 205 205 <sm:Module xsi:type="pbs_jsdl_filter"/> 206 206 <sm:Module xsi:type="atz_ardl_filter"/> 207 <sm:Module xsi:type="sm:general_python" path="/ opt/plgrid/qcg/lib/qcg-comp/modules/python/monitoring.py"/>208 <sm:Module xsi:type="sm:general_python" path="/ opt/plgrid/qcg/lib/qcg-comp/modules/python/plgrid_info.py"/>209 <sm:Module xsi:type="sm:general_python" path="/ opt/plgrid/qcg/lib/qcg-comp/modules/python/modules_info.py"/>210 211 <sm:Module xsi:type="submission_drmaa" path="/ opt/plgrid/qcg/lib/libdrmaa.so"/>212 <sm:Module xsi:type="reservation_python" path="/ opt/plgrid/qcg/lib/qcg-comp/modules/python/reservation_maui.py"/>207 <sm:Module xsi:type="sm:general_python" path="/usr/lib64/qcg-comp/modules/python/monitoring.py"/> 208 <sm:Module xsi:type="sm:general_python" path="/usr/lib64/qcg-comp/modules/python/plgrid_info.py"/> <!-- PL-Grid only !!! --> 209 <sm:Module xsi:type="sm:general_python" path="/usr/lib64/qcg-comp/modules/python/modules_info.py"/> 210 211 <sm:Module xsi:type="submission_drmaa" path="/usr/local/lib/libdrmaa.so"/> 212 <sm:Module xsi:type="reservation_python" path="/usr/lib64/qcg-comp/modules/python/reservation_maui.py"/> 213 213 214 214 <sm:Module xsi:type="notification_wsn"> … … 224 224 225 225 <sm:Module xsi:type="application_mapper"> 226 <ApplicationMapFile>/ opt/plgrid/qcg/etc/qcg-comp/application_mapfile</ApplicationMapFile>226 <ApplicationMapFile>/etc/qcg/qcg-comp/application_mapfile</ApplicationMapFile> 227 227 </sm:Module> 228 228 … … 237 237 238 238 <FactoryAttributes> 239 <CommonName> klaster.plgrid.pl</CommonName>240 <LongDescription> PL Grid cluster</LongDescription>239 <CommonName>hpc.mydomain.org</CommonName> 240 <LongDescription>Cluster description</LongDescription> 241 241 </FactoryAttributes> 242 242 </sm:Service> … … 290 290 Please use [http://www.qoscosgrid.org/trac/qcg-computing/wiki/QCG-Accounting QCG-Accounting] agent. You must enable `bat` as one of the publisher plugins. 291 291 292 = Creating applications' script space - TODO = 293 A common case for the QCG-Computing service is that an application is accessed using abstract app name rather than specifying absolute executable path. The application name/version to executbale path mappings are stored in the file `/opt/plgrid/qcg/etc/qcg-comp/application_mapfile`: 294 295 {{{ 296 #!div style="font-size: 90%" 297 {{{#!default 292 = Creating applications' script space = 293 A common case for the QCG-Computing service is that an application is accessed using abstract app name rather than specifying absolute executable path. The application name/version to executbale path mappings are stored in the file `/etc/qcg/qcg-comp/application_mapfile`: 294 295 {{{ 298 296 cat /opt/plgrid/qcg/etc/qcg-comp/application_mapfile 299 297 # ApplicationName ApplicationVersion Executable 300 298 301 date * /bin/date 302 LPSolve 5.5 /usr/local/bin/lp_solve 303 QCG-OMPI /opt/QCG/qcg/share/qcg-comp/tools/cross-mpi.starter 304 }}} 305 }}} 306 307 It is also common to provide here wrapper scripts rather than target executables. The wrapper script can handle such aspects of the application lifetime like: environment initialization, copying files from/to scratch storage and application monitoring. It is recommended to create separate directory for those wrapper scripts (e.g. the application partition) for an applications and add write permission to them to the QCG Developers group. This directory must be readable by all users and from every worker node (the application partition usually fullfils those requirements). For example: 308 309 {{{ 310 #!div style="font-size: 90%" 311 {{{#!default 312 mkdir /opt/exp_soft/plgrid/qcg-app-scripts 313 chown :qcg-dev /opt/exp_soft/plgrid/qcg-app-scripts 314 chmod g+rwx /opt/exp_soft/plgrid/qcg-app-scripts 315 }}} 316 }}} 299 bash * /opt/app/app-scripts/bash.qcg 300 301 }}} 302 303 It is also common to provide here wrapper scripts rather than target executables. The wrapper script can handle such aspects of the application lifetime like: environment initialization, copying files from/to scratch storage and application monitoring. It is recommended to create separate directory for those wrapper scripts (e.g. the application partition) for an applications. This directory must be readable by all users and from every worker node (the application partition usually fullfils those requirements). For example: 317 304 318 305 More on [ApplicationScripts Application Scripts]. … … 355 342 <Configuration> 356 343 <sm:ModuleManager> 357 <sm:Directory>/ opt/qcg/lib/qcg-core/modules/</sm:Directory>358 <sm:Directory>/ opt/qcg/lib/qcg-comp/modules/</sm:Directory>344 <sm:Directory>/usr/lib64/qcg-core/modules/</sm:Directory> 345 <sm:Directory>/usr/lib64/qcg-comp/modules/</sm:Directory> 359 346 </sm:ModuleManager> 360 347