Changes between Version 2 and Version 3 of installation_QCG_BES_AR_in_PLGrid

Timestamp:

05/19/11 15:11:50 (13 years ago)

Author:

bartek

Comment:

--

installation_QCG_BES_AR_in_PLGrid

@@ -235 +235 @@
 === The Grid Mapfile  ===
 ==== Manually created grid mapfile (for testing purpose only) ====
+{{{
+#!div style="font-size: 90%"
+{{{#!default
   #for test purpose only add mapping for your account
   echo '"MyCertDN" myaccount' >> /etc/grid-security/grid-mapfile
+}}}
+}}}
 ==== LDAP based grid mapfile ====
+{{{
+#!div style="font-size: 90%"
+{{{#!default
  #install grid-mapfile generator from PL-Grid repository
  yum install plggridmapfilegenerator
@@ -255 +263 @@
  format=^plgridX509CertificateDN, uid
  EOF
- 
  #add the gridmapfile generator as the cron.job
  cat > /etc/cron.hourly/gridmapfile.cron << EOF
@@ -265 +272 @@
  #try it!
  /etc/cron.hourly/gridmapfile.cron
-
+}}}
+}}}
 
 Add appropriate rights for the smoa_comp and grms users in the Maui scheduler configuaration file:
+{{{
+#!div style="font-size: 90%"
+{{{#!default
   vim /var/spool/maui/maui.cfg
   # primary admin must be first in list
@@ -273 +284 @@
   ADMIN2                grms
   ADMIN3                smoa_comp
-
+}}}
+}}}
 Copy the service certificate and key into the <code>/opt/plgrid/qcg/smoa/etc/certs/</code>. Remember to set appropriate rights to the key file.
+{{{
+#!div style="font-size: 90%"
+{{{#!default
   cp /etc/grid-security/hostcert.pem /opt/plgrid/qcg/smoa/etc/certs/smoacert.pem
   cp /etc/grid-security/hostkey.pem /opt/plgrid/qcg/smoa/etc/certs/smoakey.pem
@@ -280 +295 @@
   chown smoa_comp /opt/plgrid/qcg/smoa/etc/certs/smoakey.pem 
   chmod 0600 /opt/plgrid/qcg/smoa/etc/certs/smoakey.pem
-
+}}}
+}}}
 == DRMAA library ==
-* DRMAA library must be compiled from SRC RPM: 
+DRMAA library must be compiled from SRC RPM: 
+{{{
+#!div style="font-size: 90%"
+{{{#!default
   wget http://fury.man.poznan.pl/qcg-packages/sl/SRPMS/pbs-drmaa-1.0.6-2.src.rpm
   rpmbuild  --rebuild pbs-drmaa-1.0.6-2.src.rpm
   cd /usr/src/redhat/RPMS/x86_64/
   rpm -i pbs-drmaa-1.0.6-2.x86_64.rpm 
-
-* however if you are using it for the first time then you should try to compile it with enabled logging:
+}}}
+}}}
+however if you are using it for the first time then you should try to compile it with enabled logging:
+{{{
+#!div style="font-size: 90%"
+{{{#!default
   wget http://fury.man.poznan.pl/qcg-packages/sl/SRPMS/pbs-drmaa-1.0.6-2.src.rpm
   rpmbuild  --define 'configure_options --enable-debug' --rebuild pbs-drmaa-1.0.6-2.src.rpm
   cd /usr/src/redhat/RPMS/x86_64/
   rpm -i pbs-drmaa-1.0.6-2.x86_64.rpm
-
+}}}
+}}}
 After installation  you need '''either''':
-* configure the DRMAA library to use Torque logs ('''RECOMMENDED'''). Sample configuration file of the DRMAA library (<code>/opt/plgrid/qcg/smoa/etc/pbs_drmaa.conf</code>):
+* configure the DRMAA library to use Torque logs ('''RECOMMENDED'''). Sample configuration file of the DRMAA library (`/opt/plgrid/qcg/smoa/etc/pbs_drmaa.conf`):
+{{{
+#!div style="font-size: 90%"
+{{{#!default
   # pbs_drmaa.conf - Sample pbs_drmaa configuration file.
   
@@ -303 +330 @@
     
   cache_job_state: 600,
-{{Note}} Remember to mount server log directory as described in the eariler [[Smoa_Computing_on_separate_machine|note]].
+}}}
+}}}
+'''Note:''' Remember to mount server log directory as described in the eariler [[Smoa_Computing_on_separate_machine|note]].
 
 '''or'''
-* configure Torque to keep information about completed jobs (e.g.: by setting: qmgr -c 'set server keep_completed = 300').
-  
-It is possible to limit users to submit job to predefined queue by setting default job category (in the <code>/opt/plgrid/qcg/smoa/etc/pbs_drmaa.conf</code> file):
-
+* configure Torque to keep information about completed jobs (e.g.: by setting: `qmgr -c 'set server keep_completed = 300'`).
+  
+It is possible to limit users to submit job to predefined queue by setting default job category (in the `/opt/plgrid/qcg/smoa/etc/pbs_drmaa.conf` file):
+{{{
+#!div style="font-size: 90%"
+{{{#!default
   job_categories: {
         default: "-q plgrid",
   },
+}}}
+}}}
 
 == Restricting advance reservation ==
-In some deployments enabling advance reservation for the whole cluster is not desirable. In such cases one can limit advance reservation to particular partition by editing <code>/opt/plgrid/qcg/smoa/lib/smoa-comp/modules/python/reservation_maui.py</code> file and changing the following line:
+In some deployments enabling advance reservation for the whole cluster is not desirable. In such cases one can limit advance reservation to particular partition by editing `/opt/plgrid/qcg/smoa/lib/smoa-comp/modules/python/reservation_maui.py` file and changing the following line:
+{{{
+#!div style="font-size: 90%"
+{{{#!default
   cmd = "setres -x BYNAME -r PROCS=1"
+}}}
+}}}
 to
+{{{
+#!div style="font-size: 90%"
+{{{#!default
   cmd = "setres -x BYNAME -r PROCS=1 -p wp4"
+}}}
+}}}
 
 = Service configuration =
-Edit the preinstalled service configuration file (<code>/opt/plgrid/qcg/smoa/etc/smoa-compd.xml</code>):
-
+Edit the preinstalled service configuration file (`/opt/plgrid/qcg/smoa/etc/smoa-compd.xml`):
+{{{
+#!div style="font-size: 90%"
+{{{#!xml
   <?xml version="1.0" encoding="UTF-8"?>
   <sm:SMOACore
@@ -399 +444 @@
         </Configuration>
   </sm:SMOACore>
-  <!-- vim: set ts=2 sw=2: -->
+}}}
+}}}
 
 In most cases it should be enough to change only following elements:
-; ''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). If you installed cert and key file in the recommended location you do not need to edit these fields.
-; ''Module[type="smc:notification_wsn"]/Module/ServiceURL'' : the URL of the [[SMOA_Notification_in_PL-Grid|Smoa Notification Service]] (You can do it later, i.e. after installing the Smoa Notification service)
-;  Module[type="submission_drmaa"]/@path : path to the DRMAA library (the <code>libdrmaa.so</code>). Also, if you installed the DRMAA library using provided SRC RPM you do not need to change this path.
-;  ''Database/Password'' : the <code>smoa_comp</code> database password
-;  ''FactoryAttributes/CommonName'' : a common name of the cluster (e.g. reef.man.poznan.pl). You can use any name that is unique among all systems (e.g. cluster name + domain name of your institution)
-;  ''FactoryAttributes/LongDescription'' : a human readable description of the cluster
+ `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). If you installed cert and key file in the recommended location you do not need to edit these fields.
+ `Module[type="smc:notification_wsn"]/Module/ServiceURL` :: 
+  the URL of the [[SMOA_Notification_in_PL-Grid|Smoa Notification Service]] (You can do it later, i.e. after installing the Smoa Notification service)
+ `Module[type="submission_drmaa"]/@path` ::
+  path to the DRMAA library (the `libdrmaa.so`). Also, if you installed the DRMAA library using provided SRC RPM you do not need to change this path.
+ `Database/Password` :: 
+  the `smoa_comp` database password
+ `FactoryAttributes/CommonName` :: 
+  a common name of the cluster (e.g. reef.man.poznan.pl). You can use any name that is unique among all systems (e.g. cluster name + domain name of your institution)
+ `FactoryAttributes/LongDescription` :: 
+  a human readable description of the cluster
 
 == Configuring BAT accounting module ==
-In order to report resource usage to the central PL-Grid accounting service you must enable the <code>bat_updater</code> module. You can do this by including the following snippet in the aforementioned configuration file (<code>/opt/plgrid/qcg/smoa/etc/smoa-comp.xml</code>). Please put the following snippet just before the <code>Database</code> section:
+In order to report resource usage to the central PL-Grid accounting service you must enable the `bat_updater` module. You can do this by including the following snippet in the aforementioned configuration file (`/opt/plgrid/qcg/smoa/etc/smoa-comp.xml`). Please put the following snippet just before the `Database` section:
+{{{
+#!div style="font-size: 90%"
+{{{#!xml
   <sm:Module xsi:type="bat_updater">
         <BATServiceURL>tcp://acct.grid.cyf-kr.edu.pl:61616</BATServiceURL>
@@ -417 +473 @@
         <QueueName>test-jobs</QueueName>
   </sm:Module>
-
+}}}
+}}}
 where:
-;BATServiceURL : URL of the BAT accounting service
-;SiteName : local site name as reported to the BAT service
-;QueueName : queue name to which report usage data
+* BATServiceURL : URL of the BAT accounting service
+* !SiteName : local site name as reported to the BAT service
+* !QueueName : queue name to which report usage data
 
 = Note on the security model =
 The Smoa Computing can be configured with various authentication and authorization modules. However in the typical deployment we assume that the Smoa Computing is configured as in the above example, i.e.:
 * authentication is provided on basics of ''httpg'' protocol
-* authorization is based on the local <code>grid-mapfile</code> mapfile (see [[GridFTP#Users_configuration|  Users configuration]]).
+* authorization is based on the local `grid-mapfile` mapfile (see [[GridFTP#Users_configuration|Users configuration]]).
 
 =Starting the service=
 As root type:
- 
+{{{
+#!div style="font-size: 90%"
+{{{#!sh
  # /etc/init.d/smoa-compd start
+}}}
+}}}
 
 The service logs can be found in:
+{{{
+#!div style="font-size: 90%"
+{{{#!sh
   /opt/plgrid/var/log/smoa-comp/smoa-comp.log
+}}}
+}}}
 
 The service assumes that the following commands are in the standard search path:
-* pbsnodes
-* showres
-* setres
-* releaseres
-* checknode
-If any of the above commands is not installed in a standard location (e.g. <code>/usr/bin</code>) you may need to edit the <code>/opt/plgrid/qcg/smoa/etc/sysconfig/smoa-compd</code> file and set the PATH variable appropriately, e.g.:
+* `pbsnodes`
+* `showres`
+* `setres`
+* `releaseres`
+* `checknode`
+If any of the above commands is not installed in a standard location (e.g. `/usr/bin`) you may need to edit the `/opt/plgrid/qcg/smoa/etc/sysconfig/smoa-compd` file and set the `PATH` variable appropriately, e.g.:
+{{{
+#!div style="font-size: 90%"
+{{{#!sh
   # INIT_WAIT=5
   #
@@ -448 +517 @@
   
   export PATH=$PATH:/opt/maui/bin
+}}}
+}}}
 
 If you compiled DRMAA with logging switched on you can set there also DRMAA logging level:
+{{{
+#!div style="font-size: 90%"
+{{{#!sh
   # INIT_WAIT=5
   #
@@ -455 +529 @@
 
   export DRMAA_LOG_LEVEL=INFO
-
-=Stopping the service=
+}}}
+}}}
+
+= Stopping the service =
 The service can be stopped using the following command:
+{{{
+#!div style="font-size: 90%"
+{{{#!sh
   # /etc/init.d/smoa-compd stop
-
-=Verifying the installation=
-
-*  For convenience you can add the <code>/opt/plgrid/qcg/smoa/bin</code> and <code>/opt/plgrid/qcg/smoa-dep/globus/bin/</code> to your <code>PATH</code> variable.
-*  Edit the Smoa Computing client configuration file (<code>/opt/plgrid/qcg/smoa/etc/smoa-comp.xml</code>):
-**  set the ''Host'' and ''Port''  to reflects the changes in the service configuration file (<code>smoa-compd.xml</code>).
-
+}}}
+}}}
+
+= Verifying the installation =
+
+*  For convenience you can add the `/opt/plgrid/qcg/smoa/bin` and `/opt/plgrid/qcg/smoa-dep/globus/bin/` to your `PATH` variable.
+*  Edit the Smoa Computing client configuration file (`/opt/plgrid/qcg/smoa/etc/smoa-comp.xml`):
+ *  set the `Host` and `Port` to reflects the changes in the service configuration file (`smoa-compd.xml`).
+{{{
+#!div style="font-size: 90%"
+{{{#!sh
  <?xml version="1.0" encoding="UTF-8"?>
  <sm:SMOACore
@@ -492 +575 @@
         </Configuration>
  </sm:SMOACore>
-
+}}}
+}}}
 * Initialize your credentials:
-
+{{{
+#!div style="font-size: 90%"
+{{{#!sh
  $ grid-proxy-init 
  Your identity: /O=Grid/OU=QosCosGrid/OU=PSNC/CN=Mariusz Mamonski
@@ -500 +586 @@
  Creating proxy .................................................................. Done
  Your proxy is valid until: Wed Sep 16 05:01:02 2009
-  
+}}}
+}}}
 * Query the SMOA Computing service:
+{{{
+#!div style="font-size: 90%"
+{{{#!sh
   $ smoa-comp -G | xmllint --format - # the xmllint is used only to present the result in more pleasant way
   
@@ -523 +613 @@
     <smcf:NotificationProviderURL xmlns:smcf="http://schemas.smoa-project.com/comp/2009/01/factory">http://localhost:2211/</smcf:NotificationProviderURL>
  </bes-factory:FactoryResourceAttributesDocument>
-
+}}}
+}}}
 * Submit a sample job:
+{{{
+#!div style="font-size: 90%"
+{{{#!sh
   $ smoa-comp -c -J /opt/plgrid/qcg/smoa/share/smoa-comp/doc/examples/jsdl/sleep.xml
   Activity Id: ccb6b04a-887b-4027-633f-412375559d73
-
+}}}
+}}}
 * Query it status:
+{{{
+#!div style="font-size: 90%"
+{{{#!sh
   $ smoa-comp -s -a ccb6b04a-887b-4027-633f-412375559d73
   status = Executing
@@ -536 +634 @@
   status = Finished
   exit status = 0
-
+}}}
+}}}
 * Create an advance reservation:
 :* copy the provided sample reservation description file (expressed in ARDL - Advance Reservation Description Language)