Changes between Version 6 and Version 7 of installation_QCG_BES_AR

Show
Ignore:
Timestamp:
05/16/11 13:31:04 (10 years ago)
Author:
bartek
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • installation_QCG_BES_AR

    v6 v7  
    216216 SQL>quit 
    217217 $ 
     218}}} 
    218219}}} 
    219220 '''Note:''' It is recommended to run this command as user different than root (e.g. the smoa_comp user). 
     
    497498 
    498499In most cases it should be enough to change only following elements: 
    499 ; ''Database'' : the contact data for the Database created in the previously steps 
    500 ; ''Transport/Module/Host'' :  the hostname of the machine where the service is deployed  
    501 ; ''Transport/Module/Authentication/Module/X509CertFile'' and  ''Transport/Module/Authentication/Module/X509KeyFile'' : - the service private key and X.509 certificate (consult the [http://www.globus.org/toolkit/docs/4.0/security/prewsaa/rn01re02.html Globus User Gide] on how to generate service certificate request or use the host certificate/key pair). Make sure that the key and certificate is owned by the <code>smoa_comp</code> user and the private key is not password protected (generating certificate with the <code>-service</code> option implies this). 
    502 ; ''Module[type="smc:notification_wsn"]/Module/ServiceURL'' : the URL of the [[SMOA_Notification|SMOA Notification Service]] (You can do it later, i.e. after installing the SMOA Notification service) 
    503 ; ''FactoryAttributes/ContainedResources'' : list of the all worker nodes managed by the LRMS. You should provide at least hostnames (''<bes-factory:ResourceName>'') and cpus count (''<bes-factory:CPUCount>'') for every worker node in your cluster. If you are using Torque batch system this information can be provided automatically by enabling ''python/monitoring.py'' module. 
    504 ;  Module[type="submission_drmaa"]/@path : path to the DRMAA library (the <code>libdrmaa.so</code> - search for this file within the LRMS lib directory. e.g. <code>/opt/sge/lib/</code> or <code>/opt/QCG/LSF/lsf7.0.3/7.0/linux2.6-glibc2.3-x86_64/lib/</code>) 
    505 ;  Module[type="reservation_ares"]/@path : path to the ARES library (LSF only) 
    506 ;  Module[type="reservation_python"]/@path : path to the Python reservation module (SGE only) - only if you installed SMOA Computing in location other than /opt/QCG/smoa. 
    507 ;  ReservationsAdministrator : the user authorized to create and manage reservations. Usually the LRMS administrator user (like <code>sgeadmin</code> in SGE or <code>lsfadmin</code> in LSF, or any user other than root given in ADMIN* sections of the Maui config file) has sufficient rights. 
    508  
    509 {{Note}} Later in this manual you will read that the [[GRMS]]  credentials must be mapped to this user (see [[GRMS#Resource_Providers_setup%23Resource%20Providers%20setup| GRMS Resource Providers setup]]). 
     500 Database::  
     501  the contact data for the Database created in the previously steps 
     502 !Transport/Module/Host::   
     503  the hostname of the machine where the service is deployed  
     504 !Transport/Module/Authentication/Module/X509CertFile and Transport/Module/Authentication/Module/X509KeyFile::  
     505  the service private key and X.509 certificate (consult the [[http://www.globus.org/toolkit/docs/4.0/security/prewsaa/rn01re02.html|Globus User Gide]] on how to generate service certificate request or use the host certificate/key pair). Make sure that the key and certificate is owned by the `smoa_comp` user and the private key is not password protected (generating certificate with the `-service` option implies this). 
     506 Module[type="smc:notification_wsn"]/Module/ServiceURL::  
     507  the URL of the [[SMOA_Notification|SMOA Notification Service]] (You can do it later, i.e. after installing the SMOA Notification service) 
     508 !FactoryAttributes/ContainedResources::  
     509  list of the all worker nodes managed by the LRMS. You should provide at least hostnames (`<bes-factory:ResourceName>`) and cpus count (`<bes-factory:CPUCount>`) for every worker node in your cluster. If you are using Torque batch system this information can be provided automatically by enabling `python/monitoring.py` module. 
     510 Module[type="submission_drmaa"]/@path::  
     511  path to the DRMAA library (the `libdrmaa.so` - search for this file within the LRMS lib directory. e.g. `/opt/sge/lib/` or `/opt/QCG/LSF/lsf7.0.3/7.0/linux2.6-glibc2.3-x86_64/lib/`) 
     512 Module[type="reservation_ares"]/@path:: 
     513  path to the ARES library (LSF only) 
     514 Module[type="reservation_python"]/@path::  
     515  path to the Python reservation module (SGE only) - only if you installed SMOA Computing in location other than `/opt/QCG/smoa`. 
     516 !ReservationsAdministrator::  
     517  the user authorized to create and manage reservations. Usually the LRMS administrator user (like `sgeadmin` in SGE or `lsfadmin` in LSF, or any user other than root given in ADMIN* sections of the Maui config file) has sufficient rights. 
     518 
     519''Note:''' Later in this manual you will read that the [[GRMS]] credentials must be mapped to this user (see [[GRMS#Resource_Providers_setup%23Resource%20Providers%20setup| GRMS Resource Providers setup]]). 
    510520{{Security Note}}  
    511521 
    512522Finally make this configuration file readable '''only''' by the <code>smoa_comp</code> user (in order to protect database password): 
     523{{{ 
     524#!div style="font-size: 90%" 
     525{{{#!sh 
    513526  chmod 0600 /opt/QCG/smoa/etc/smoa-compd.xml 
     527}}} 
     528}}} 
    514529 
    515530== Configuring BAT accounting module (PL-Grid only) ==