Changes between Version 6 and Version 7 of installation_QCG_BES_AR

Timestamp:

05/16/11 13:31:04 (13 years ago)

Author:

bartek

Comment:

--

installation_QCG_BES_AR

@@ -216 +216 @@
  SQL>quit
  $
+}}}
 }}}
  '''Note:''' It is recommended to run this command as user different than root (e.g. the smoa_comp user).
@@ -497 +498 @@
 
 In most cases it should be enough to change only following elements:
-; ''Database'' : the contact data for the Database created in the previously steps
-; ''Transport/Module/Host'' :  the hostname of the machine where the service is deployed 
-; ''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).
-; ''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)
-; ''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.
-;  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>)
-;  Module[type="reservation_ares"]/@path : path to the ARES library (LSF only)
-;  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.
-;  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.
-
-{{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]]).
+ Database:: 
+  the contact data for the Database created in the previously steps
+ !Transport/Module/Host::  
+  the hostname of the machine where the service is deployed 
+ !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 `smoa_comp` user and the private key is not password protected (generating certificate with the `-service` option implies this).
+ 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)
+ !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.
+ Module[type="submission_drmaa"]/@path:: 
+  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/`)
+ Module[type="reservation_ares"]/@path::
+  path to the ARES library (LSF only)
+ 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`.
+ !ReservationsAdministrator:: 
+  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.
+
+''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]]).
 {{Security Note}} 
 
 Finally make this configuration file readable '''only''' by the <code>smoa_comp</code> user (in order to protect database password):
+{{{
+#!div style="font-size: 90%"
+{{{#!sh
   chmod 0600 /opt/QCG/smoa/etc/smoa-compd.xml
+}}}
+}}}
 
 == Configuring BAT accounting module (PL-Grid only) ==