Difference: NotesAboutInstallationAndConfigurationOfCREAMAndTORQUE (1 vs. 18)

Revision 182012-05-25 - PaoloVeronesi

Line: 1 to 1
 
META TOPICPARENT name="WebHome"

Notes about Installation and Configuration of a CREAM Computing Element using Torque as batch system and ARGUS as authorization method

  • These notes are provided by site admins on a best effort base as a contribution to the IGI communities and MUST not be considered as a subsitute of the Official IGI documentation.
Line: 477 to 477
 

maui settings

In order to reserve a job slot for test jobs, you need to apply some settings in the maui configuration (/var/spool/maui/maui.cfg)
Changed:
<
<
Suppose you have enabled the test VOs (ops, dteam and infngrid) on the "cert" queue and that you have 8 job slots available. Add the following lines in the maui.cfg files:
>
>
Suppose you have enabled the test VOs (ops, dteam and infngrid) on the "cert" queue and that you have 8 job slots available. Add the following lines in the /var/spool/maui/maui.cfg file:
 
CLASSWEIGHT 1

Revision 172012-04-18 - AlessandroPaolini

Line: 1 to 1
 
META TOPICPARENT name="WebHome"

Notes about Installation and Configuration of a CREAM Computing Element using Torque as batch system and ARGUS as authorization method

  • These notes are provided by site admins on a best effort base as a contribution to the IGI communities and MUST not be considered as a subsitute of the Official IGI documentation.
Line: 131 to 131
 hideimgright="/twiki/pub/TWiki/TWikiDocGraphics/toggleclose.gif" }%

users and groups configuration

Changed:
<
<
here an example on how to define pool accounts (ig-users.conf) and groups (ig-groups.conf) for several VOs
>
>
here an example on how to define pool accounts (ig-users.conf) and groups (ig-groups.conf) for several VOs
 </>
<--/twistyPlugin-->

%TWISTY{

Revision 162012-02-13 - AlessandroPaolini

Line: 1 to 1
 
META TOPICPARENT name="WebHome"

Notes about Installation and Configuration of a CREAM Computing Element using Torque as batch system and ARGUS as authorization method

  • These notes are provided by site admins on a best effort base as a contribution to the IGI communities and MUST not be considered as a subsitute of the Official IGI documentation.
Line: 252 to 252
 # for all hosts sharing the lrms and this value can be arbitrary chosen among # these submitting hostnames (you may choose the best one). # Otherwise leave it commented.
Changed:
<
<
#DGAS_USE_CE_HOSTNAME=""
>
>
# we have 2 CEs, cremino is the main one DGAS_USE_CE_HOSTNAME="cremino.cnaf.infn.it"
  # Path for the batch-system log files. # * for torque/pbs:

Revision 152012-02-10 - AlessandroPaolini

Line: 1 to 1
 
META TOPICPARENT name="WebHome"

Notes about Installation and Configuration of a CREAM Computing Element using Torque as batch system and ARGUS as authorization method

  • These notes are provided by site admins on a best effort base as a contribution to the IGI communities and MUST not be considered as a subsitute of the Official IGI documentation.
Line: 136 to 136
  %TWISTY{ mode="div"
Added:
>
>
showlink=" wn-list.conf " hidelink=" wn-list.conf " remember="off" firststart="hide" showimgright="/twiki/pub/TWiki/TWikiDocGraphics/toggleopen.gif" hideimgright="/twiki/pub/TWiki/TWikiDocGraphics/toggleclose.gif" }%

wn-list.conf

Set in this file the WNs list, for example:

# less wn-list.conf 
wn01.cnaf.infn.it
wn02.cnaf.infn.it
wn03.cnaf.infn.it
wn04.cnaf.infn.it
</>
<--/twistyPlugin-->

%TWISTY{ mode="div"

 showlink=" site-info.def " hidelink=" site-info.def " remember="off" firststart="hide"

Revision 142012-02-08 - AlessandroPaolini

Line: 1 to 1
 
META TOPICPARENT name="WebHome"

Notes about Installation and Configuration of a CREAM Computing Element using Torque as batch system and ARGUS as authorization method

  • These notes are provided by site admins on a best effort base as a contribution to the IGI communities and MUST not be considered as a subsitute of the Official IGI documentation.
Line: 389 to 389
  </>
<--/twistyPlugin-->
Added:
>
>
<--/twistyPlugin twikiMakeVisibleInline-->

walltime workaround

If on the queues there is published:
GlueCEStateWaitingJobs: 444444
and in the log /var/log/bdii/bdii-update.log you notice errors like the folllowing:
Traceback (most recent call last):
  File "/usr/libexec/lcg-info-dynamic-scheduler", line 435, in ?
    wrt = qwt * nwait
TypeError: unsupported operand type(s) for *: 'NoneType' and 'int'
probably the queues have no "resources_default.walltime" parameter configured.

So define it for each queue by launching, for example:

# qmgr -c "set queue prod resources_default.walltime = 01:00:00"
# qmgr -c "set queue cert resources_default.walltime = 01:00:00"
# qmgr -c "set queue cloudtf resources_default.walltime = 01:00:00"
<--/twistyPlugin-->
 

Service Checks

%TWISTY{ mode="div"
Line: 451 to 481
 

Revisions

Date Comment By
Added:
>
>
2012-02-08 added walltime workaround Alessandro Paolini
2012-02-02 modified software area settings Alessandro Paolini
 
2012-01-25 installation notes completed Alessandro Paolini
2012-01-16 First draft Alessandro Paolini
Changed:
<
<
-- AlessandroPaolini - 2012-01-25
>
>
-- AlessandroPaolini - 2012-02-08
 
META TOPICMOVED by="AlessandroPaolini" date="1326712426" from="SiteAdminCorner.NotesAboutInstallationAndConfigurationOfCREAM" to="SiteAdminCorner.NotesAboutInstallationAndConfigurationOfCREAMAndTORQUE"

Revision 132012-02-03 - AlessandroPaolini

Line: 1 to 1
 
META TOPICPARENT name="WebHome"

Notes about Installation and Configuration of a CREAM Computing Element using Torque as batch system and ARGUS as authorization method

  • These notes are provided by site admins on a best effort base as a contribution to the IGI communities and MUST not be considered as a subsitute of the Official IGI documentation.
Line: 90 to 90
 # yum install emi-cream-ce # yum install emi-torque-server emi-torque-utils # yum install glite-dgas-common glite-dgas-hlr-clients glite-dgas-hlr-sensors glite-dgas-hlr-sensors-producers yaim-dgas
Added:
>
>
# yum install nfs-utils
 

see here for details

Line: 336 to 337
  </>
<--/twistyPlugin-->
Added:
>
>
<--/twistyPlugin twikiMakeVisibleInline-->

Software Area settings

If the Software Area is hosted on your CE, you have to create it and export to the WNs in the site.def we set:

VO_SW_DIR=/opt/exp_soft
  • directory creation
mkdir /opt/exp_soft/
  • edit /etc/exports creating a line like the following:
/opt/exp_soft/ *.cnaf.infn.it(rw,sync,no_root_squash)
  • check nfs and portmap status
# service nfs status
rpc.mountd is stopped
nfsd is stopped

# service portmap status
portmap is stopped

# service portmap start
Starting portmap:                                          [  OK  ]

# service nfs start
Starting NFS services:                                     [  OK  ]
Starting NFS daemon:                                       [  OK  ]
Starting NFS mountd:                                       [  OK  ]
Starting RPC idmapd:                                       [  OK  ]

# chkconfig nfs on
# chkconfig portmap on
  • after any modification in /etc/exports you can launch
# exportfs -ra
or simply restart nfs daemon

<--/twistyPlugin-->
 

Service Checks

%TWISTY{ mode="div"

Revision 122012-01-27 - AlessandroPaolini

Line: 1 to 1
 
META TOPICPARENT name="WebHome"

Notes about Installation and Configuration of a CREAM Computing Element using Torque as batch system and ARGUS as authorization method

  • These notes are provided by site admins on a best effort base as a contribution to the IGI communities and MUST not be considered as a subsitute of the Official IGI documentation.
Line: 130 to 130
 hideimgright="/twiki/pub/TWiki/TWikiDocGraphics/toggleclose.gif" }%

users and groups configuration

Changed:
<
<
here an example on how to define pool accounts (ig-users.conf) and groups (ig-groups.conf) for several VOs
>
>
here an example on how to define pool accounts (ig-users.conf) and groups (ig-groups.conf) for several VOs
 </>
<--/twistyPlugin-->

%TWISTY{

Revision 112012-01-26 - AlessandroPaolini

Line: 1 to 1
 
META TOPICPARENT name="WebHome"

Notes about Installation and Configuration of a CREAM Computing Element using Torque as batch system and ARGUS as authorization method

  • These notes are provided by site admins on a best effort base as a contribution to the IGI communities and MUST not be considered as a subsitute of the Official IGI documentation.
Line: 397 to 397
 </>
<--/twistyPlugin-->

Revisions

Changed:
<
<
Date Comment
2012-01-25 installation notes completed
2012-01-16 First draft
>
>
Date Comment By
2012-01-25 installation notes completed Alessandro Paolini
2012-01-16 First draft Alessandro Paolini
  -- AlessandroPaolini - 2012-01-25

Revision 102012-01-25 - AlessandroPaolini

Line: 1 to 1
 
META TOPICPARENT name="WebHome"

Notes about Installation and Configuration of a CREAM Computing Element using Torque as batch system and ARGUS as authorization method

  • These notes are provided by site admins on a best effort base as a contribution to the IGI communities and MUST not be considered as a subsitute of the Official IGI documentation.
Line: 12 to 12
 
  1. About IGI Release
  2. IGI Official Installation and Configuration guide
  3. EMI CREAM System Administrator Guide
Deleted:
<
<
  1. Troubleshooting Guide for Operational Errors on EGI Sites
  2. Grid Administration FAQs page
 
  1. Yaim Guide
  2. site-info.def yaim variables
  3. CREAM yaim variables
  4. TORQUE Yaim variables
  5. CREAM v.1.13
  6. CREAM TORQUE module v. 1.0.0-1
Added:
>
>
  1. Troubleshooting Guide for Operational Errors on EGI Sites
  2. Grid Administration FAQs page
 

Service installation

%TWISTY{
Line: 31 to 31
 hideimgright="/twiki/pub/TWiki/TWikiDocGraphics/toggleclose.gif" }%
Changed:
<
<

O.S. and Repos

>
>

O.S. and Repos

 
  • Starts from a fresh installation of Scientific Linux 5.x (x86_64).
# cat /etc/redhat-release 
Line: 77 to 77
 showimgright="/twiki/pub/TWiki/TWikiDocGraphics/toggleopen.gif" hideimgright="/twiki/pub/TWiki/TWikiDocGraphics/toggleclose.gif" }%
Changed:
<
<

yum install

>
>

yum install

 
# yum clean all
Loaded plugins: downloadonly, kernel-module, priorities, protect-packages, protectbase, security, verify, versionlock
Line: 111 to 111
 hideimgright="/twiki/pub/TWiki/TWikiDocGraphics/toggleclose.gif" }%
Changed:
<
<

vo.d directory

>
>

vo.d directory

 Create the vo.d directory for the VO configuration file (you can decide if keep the VO information in the site.def or putting them in the vo.d directory)
# mkdir vo.d
Line: 129 to 129
 showimgright="/twiki/pub/TWiki/TWikiDocGraphics/toggleopen.gif" hideimgright="/twiki/pub/TWiki/TWikiDocGraphics/toggleclose.gif" }%
Changed:
<
<

users and groups configuration

>
>

users and groups configuration

 here an example on how to define pool accounts (ig-users.conf) and groups (ig-groups.conf) for several VOs </>
<--/twistyPlugin-->
Line: 141 to 141
 showimgright="/twiki/pub/TWiki/TWikiDocGraphics/toggleopen.gif" hideimgright="/twiki/pub/TWiki/TWikiDocGraphics/toggleclose.gif" }%
Changed:
<
<

site-info.def

>
>

site-info.def

 SUGGESTION: use the same site-info.def for CREAM and WNs: for this reason in this example file there are yaim variable used by CREAM, TORQUE or emi-WN.

It is also included the settings of some VOs

Line: 157 to 157
 showimgright="/twiki/pub/TWiki/TWikiDocGraphics/toggleopen.gif" hideimgright="/twiki/pub/TWiki/TWikiDocGraphics/toggleclose.gif" }%
Changed:
<
<

services/glite-creamce

>
>

services/glite-creamce

 
#
# YAIM creamCE specific variables
Line: 189 to 189
 showimgright="/twiki/pub/TWiki/TWikiDocGraphics/toggleopen.gif" hideimgright="/twiki/pub/TWiki/TWikiDocGraphics/toggleclose.gif" }%
Changed:
<
<

services/dgas_sensors

>
>

services/dgas_sensors

 
#
# YAIM DGAS Sensors specific variables
Line: 257 to 257
 hideimgright="/twiki/pub/TWiki/TWikiDocGraphics/toggleclose.gif" }%
Changed:
<
<

host certificate

>
>

host certificate

 # ll /etc/grid-security/host* -rw-r--r-- 1 root root 1440 Oct 18 09:31 /etc/grid-security/hostcert.pem -r-------- 1 root root 887 Oct 18 09:31 /etc/grid-security/hostkey.pem
Line: 272 to 272
 showimgright="/twiki/pub/TWiki/TWikiDocGraphics/toggleopen.gif" hideimgright="/twiki/pub/TWiki/TWikiDocGraphics/toggleclose.gif" }%
Changed:
<
<

munge configuration

>
>

munge configuration

 IMPORTANT: The updated EPEL5 build of torque-2.5.7-1 as compared to previous versions enables munge as an inter node authentication method.

  • verify that munge is correctly installed:
Line: 370 to 370
 showimgright="/twiki/pub/TWiki/TWikiDocGraphics/toggleopen.gif" hideimgright="/twiki/pub/TWiki/TWikiDocGraphics/toggleclose.gif" }%
Changed:
<
<
>
>

maui settings

 In order to reserve a job slot for test jobs, you need to apply some settings in the maui configuration (/var/spool/maui/maui.cfg)

Suppose you have enabled the test VOs (ops, dteam and infngrid) on the "cert" queue and that you have 8 job slots available. Add the following lines in the maui.cfg files:

Revision 92012-01-25 - AlessandroPaolini

Line: 1 to 1
 
META TOPICPARENT name="WebHome"
Changed:
<
<

Notes about Installation and Configuration of a CREAM Computing Element using Torque as batch system and ARGUS as authorization method (WORK IN PROGRESS)

>
>

Notes about Installation and Configuration of a CREAM Computing Element using Torque as batch system and ARGUS as authorization method

 
  • These notes are provided by site admins on a best effort base as a contribution to the IGI communities and MUST not be considered as a subsitute of the Official IGI documentation.
  • This document is addressed to site administrators responsible for middleware installation and configuration.
Changed:
<
<
  • The goal of this page is to provide some hints and examples on how to install and configure an IGI CREAM CE service based on EMI middleware, in no cluster mode, with TORQUE as batch system on the same host and using an external ARGUS server for the users authorization
>
>
  • The goal of this page is to provide some hints and examples on how to install and configure an IGI CREAM CE service based on EMI middleware, in no cluster mode, with TORQUE as batch system on the same host and using an external ARGUS server for the users authorization
 
Line: 66 to 66
 epel.repo epel-testing.repo sl-contrib.repo sl-fastbugs.repo sl-security.repo sl-testing.repo sl-debuginfo.repo sl.repo sl-srpms.repo
Added:
>
>
IMPORTANT: remove the dag repository if present
 </>
<--/twistyPlugin-->

%TWISTY{

Line: 76 to 77
 showimgright="/twiki/pub/TWiki/TWikiDocGraphics/toggleopen.gif" hideimgright="/twiki/pub/TWiki/TWikiDocGraphics/toggleclose.gif" }%
Added:
>
>

yum install

 
# yum clean all
Loaded plugins: downloadonly, kernel-module, priorities, protect-packages, protectbase, security, verify, versionlock
Line: 109 to 111
 hideimgright="/twiki/pub/TWiki/TWikiDocGraphics/toggleclose.gif" }%
Added:
>
>

vo.d directory

 Create the vo.d directory for the VO configuration file (you can decide if keep the VO information in the site.def or putting them in the vo.d directory)
# mkdir vo.d
Line: 126 to 129
 showimgright="/twiki/pub/TWiki/TWikiDocGraphics/toggleopen.gif" hideimgright="/twiki/pub/TWiki/TWikiDocGraphics/toggleclose.gif" }%
Changed:
<
<
>
>

users and groups configuration

 here an example on how to define pool accounts (ig-users.conf) and groups (ig-groups.conf) for several VOs </>
<--/twistyPlugin-->
Line: 138 to 141
 showimgright="/twiki/pub/TWiki/TWikiDocGraphics/toggleopen.gif" hideimgright="/twiki/pub/TWiki/TWikiDocGraphics/toggleclose.gif" }%
Added:
>
>

site-info.def

 SUGGESTION: use the same site-info.def for CREAM and WNs: for this reason in this example file there are yaim variable used by CREAM, TORQUE or emi-WN.

It is also included the settings of some VOs

Line: 153 to 157
 showimgright="/twiki/pub/TWiki/TWikiDocGraphics/toggleopen.gif" hideimgright="/twiki/pub/TWiki/TWikiDocGraphics/toggleclose.gif" }%
Changed:
<
<
>
>

services/glite-creamce

 
#
# YAIM creamCE specific variables
Line: 185 to 189
 showimgright="/twiki/pub/TWiki/TWikiDocGraphics/toggleopen.gif" hideimgright="/twiki/pub/TWiki/TWikiDocGraphics/toggleclose.gif" }%
Changed:
<
<
>
>

services/dgas_sensors

 
#
# YAIM DGAS Sensors specific variables
Line: 253 to 257
 hideimgright="/twiki/pub/TWiki/TWikiDocGraphics/toggleclose.gif" }%
Added:
>
>

host certificate

 # ll /etc/grid-security/host* -rw-r--r-- 1 root root 1440 Oct 18 09:31 /etc/grid-security/hostcert.pem -r-------- 1 root root 887 Oct 18 09:31 /etc/grid-security/hostkey.pem
Line: 267 to 272
 showimgright="/twiki/pub/TWiki/TWikiDocGraphics/toggleopen.gif" hideimgright="/twiki/pub/TWiki/TWikiDocGraphics/toggleclose.gif" }%
Changed:
<
<
>
>

munge configuration

 IMPORTANT: The updated EPEL5 build of torque-2.5.7-1 as compared to previous versions enables munge as an inter node authentication method.

  • verify that munge is correctly installed:
Line: 393 to 398
 

Revisions

Date Comment
Added:
>
>
2012-01-25 installation notes completed
 
2012-01-16 First draft
Changed:
<
<
-- AlessandroPaolini - 2012-01-16
>
>
-- AlessandroPaolini - 2012-01-25
 
META TOPICMOVED by="AlessandroPaolini" date="1326712426" from="SiteAdminCorner.NotesAboutInstallationAndConfigurationOfCREAM" to="SiteAdminCorner.NotesAboutInstallationAndConfigurationOfCREAMAndTORQUE"

Revision 82012-01-24 - AlessandroPaolini

Line: 1 to 1
 
META TOPICPARENT name="WebHome"
Changed:
<
<

Notes about Installation and Configuration of a CREAM Computing Element using Torque (WORK IN PROGRESS)

>
>

Notes about Installation and Configuration of a CREAM Computing Element using Torque as batch system and ARGUS as authorization method (WORK IN PROGRESS)

 
  • These notes are provided by site admins on a best effort base as a contribution to the IGI communities and MUST not be considered as a subsitute of the Official IGI documentation.
  • This document is addressed to site administrators responsible for middleware installation and configuration.
Changed:
<
<
  • The goal of this page is to provide some hints and examples on how to install and configure an IGI CREAM CE service based on EMI middleware, in no cluster mode, with TORQUE as batch system on the same host
>
>
  • The goal of this page is to provide some hints and examples on how to install and configure an IGI CREAM CE service based on EMI middleware, in no cluster mode, with TORQUE as batch system on the same host and using an external ARGUS server for the users authorization
 
Line: 380 to 380
 CLASSCFG[cert] PRIORITY=5000
Added:
>
>
After the modification restart maui.

In order to avoid that yaim overwrites this file during the host reconfiguration, set:

CONFIG_MAUI="no"

in your site.def (the first time you launch the yaim script, it has to be set to "yes"

 </>
<--/twistyPlugin-->

Revisions

Revision 72012-01-24 - AlessandroPaolini

Line: 1 to 1
 
META TOPICPARENT name="WebHome"

Notes about Installation and Configuration of a CREAM Computing Element using Torque (WORK IN PROGRESS)

  • These notes are provided by site admins on a best effort base as a contribution to the IGI communities and MUST not be considered as a subsitute of the Official IGI documentation.
Line: 366 to 366
 hideimgright="/twiki/pub/TWiki/TWikiDocGraphics/toggleclose.gif" }%
Added:
>
>
In order to reserve a job slot for test jobs, you need to apply some settings in the maui configuration (/var/spool/maui/maui.cfg)

Suppose you have enabled the test VOs (ops, dteam and infngrid) on the "cert" queue and that you have 8 job slots available. Add the following lines in the maui.cfg files:

CLASSWEIGHT 1
QOSWEIGHT 1

QOSCFG[normal] MAXJOB=7

CLASSCFG[prod] QDEF=normal
CLASSCFG[cert] PRIORITY=5000
 </>
<--/twistyPlugin-->

Revisions

Revision 62012-01-20 - AlessandroPaolini

Line: 1 to 1
 
META TOPICPARENT name="WebHome"

Notes about Installation and Configuration of a CREAM Computing Element using Torque (WORK IN PROGRESS)

  • These notes are provided by site admins on a best effort base as a contribution to the IGI communities and MUST not be considered as a subsitute of the Official IGI documentation.
Line: 120 to 120
  %TWISTY{ mode="div"
Added:
>
>
showlink=" users and groups configuration " hidelink=" users and groups configuration " remember="off" firststart="hide" showimgright="/twiki/pub/TWiki/TWikiDocGraphics/toggleopen.gif" hideimgright="/twiki/pub/TWiki/TWikiDocGraphics/toggleclose.gif" }%

here an example on how to define pool accounts (ig-users.conf) and groups (ig-groups.conf) for several VOs </>

<--/twistyPlugin-->

%TWISTY{ mode="div"

 showlink=" site-info.def " hidelink=" site-info.def " remember="off" firststart="hide"
Line: 294 to 306
 showimgright="/twiki/pub/TWiki/TWikiDocGraphics/toggleopen.gif" hideimgright="/twiki/pub/TWiki/TWikiDocGraphics/toggleclose.gif" }%
Added:
>
>
Verify to have set all the yaim variables by launching:
# /opt/glite/yaim/bin/yaim -v -s site-info_cremino.def -n creamCE -n TORQUE_server -n TORQUE_utils -n DGAS_sensors
 
Added:
>
>
see details
 </>
<--/twistyPlugin-->

%TWISTY{

Line: 306 to 323
 hideimgright="/twiki/pub/TWiki/TWikiDocGraphics/toggleclose.gif" }%
Added:
>
>
# /opt/glite/yaim/bin/yaim -c -s site-info_cremino.def -n creamCE -n TORQUE_server -n TORQUE_utils -n DGAS_sensors

see details

</>

<--/twistyPlugin-->

Service Checks

<--/twistyPlugin twikiMakeVisibleInline-->

  • After service installation to have a look if all were installed in a proper way, you could have a look to Service CREAM Reference Card
  • You can also perform some checks after the installation and configuration of your CREAM
 
Changed:
<
<
see details
>
>

TORQUE checks:

  • check the pbs settings:
# qmgr -c 'p s'
  • check the WNs state
# pbsnodes -a

<--/twistyPlugin-->

<--/twistyPlugin twikiMakeVisibleInline-->
 
<--/twistyPlugin-->

Revision 52012-01-20 - AlessandroPaolini

Line: 1 to 1
 
META TOPICPARENT name="WebHome"

Notes about Installation and Configuration of a CREAM Computing Element using Torque (WORK IN PROGRESS)

  • These notes are provided by site admins on a best effort base as a contribution to the IGI communities and MUST not be considered as a subsitute of the Official IGI documentation.
Line: 306 to 306
 hideimgright="/twiki/pub/TWiki/TWikiDocGraphics/toggleclose.gif" }%
Added:
>
>
see details
 </>
<--/twistyPlugin-->

Revisions

Revision 42012-01-19 - AlessandroPaolini

Line: 1 to 1
 
META TOPICPARENT name="WebHome"

Notes about Installation and Configuration of a CREAM Computing Element using Torque (WORK IN PROGRESS)

  • These notes are provided by site admins on a best effort base as a contribution to the IGI communities and MUST not be considered as a subsitute of the Official IGI documentation.
  • This document is addressed to site administrators responsible for middleware installation and configuration.
Changed:
<
<
  • The goal of this page is to provide some hints and examples on how to install and configure an IGI CREAM CE service based on EMI middleware, in no cluster mode, with TORQUE as batch system on the same host
>
>
  • The goal of this page is to provide some hints and examples on how to install and configure an IGI CREAM CE service based on EMI middleware, in no cluster mode, with TORQUE as batch system on the same host
 
Line: 14 to 14
 
  1. EMI CREAM System Administrator Guide
  2. Troubleshooting Guide for Operational Errors on EGI Sites
  3. Grid Administration FAQs page
Added:
>
>
  1. Yaim Guide
  2. site-info.def yaim variables
  3. CREAM yaim variables
  4. TORQUE Yaim variables
 
  1. CREAM v.1.13
  2. CREAM TORQUE module v. 1.0.0-1
Line: 96 to 100
 # cp -r /opt/glite/yaim/examples/siteinfo/* .
Added:
>
>
<--/twistyPlugin twikiMakeVisibleInline-->
 Create the vo.d directory for the VO configuration file (you can decide if keep the VO information in the site.def or putting them in the vo.d directory)
# mkdir vo.d
Added:
>
>
here an example for some VOs.

Information about the several VOs are available at the CENTRAL OPERATIONS PORTAL.

<--/twistyPlugin-->
  %TWISTY{ mode="div"
Line: 109 to 126
 showimgright="/twiki/pub/TWiki/TWikiDocGraphics/toggleopen.gif" hideimgright="/twiki/pub/TWiki/TWikiDocGraphics/toggleclose.gif" }%
Changed:
<
<
SUGGESTION: use the same site-info.def for CREAM and WNs
>
>
SUGGESTION: use the same site-info.def for CREAM and WNs: for this reason in this example file there are yaim variable used by CREAM, TORQUE or emi-WN.

It is also included the settings of some VOs

For your convenience there is an explanation of each yaim variable. For more details look at [8, 9, 10] </>

<--/twistyPlugin-->

<--/twistyPlugin twikiMakeVisibleInline-->

#
# YAIM creamCE specific variables
#

# LSF settings: path where lsf.conf is located
#BATCH_CONF_DIR=lsf_install_path/conf
#
# CE-monitor host (by default CE-monitor is installed on the same machine as 
# cream-CE)
CEMON_HOST=$CE_HOST
#
# CREAM database user
CREAM_DB_USER=*********
#
CREAM_DB_PASSWORD=*********
# Machine hosting the BLAH blparser.
# In this machine batch system logs must be accessible.
#BLPARSER_HOST=set_to_fully_qualified_host_name_of_machine_hosting_blparser_server
BLPARSER_HOST=$CE_HOST
<--/twistyPlugin-->

<--/twistyPlugin twikiMakeVisibleInline-->

#
# YAIM DGAS Sensors specific variables
#


################################
# DGAS configuration variables #
################################
# For any details about DGAS variables please refer to the guide:
# http://igrelease.forge.cnaf.infn.it/doku.php?id=doc:guides:dgas

# Reference Resource HLR for the site.
DGAS_HLR_RESOURCE="prod-hlr-01.pd.infn.it"

# Specify the type of job which the CE has to process.
# Set ”all” on “the main CE” of the site, ”grid” on the others.
# Default value: all
#DGAS_JOBS_TO_PROCESS="all"

# This parameter can be used to specify the list of VOs to publish.
# If the parameter is specified, the sensors (pushd) will forward
# to the Site HLR just records belonging to one of the specified VOs.
# Leave commented if you want to send records for ALL VOs
# Default value: parameter not specified
#DGAS_VO_TO_PROCESS="vo1;vo2;vo3..."


# Bound date on jobs backward processing.
# The backward processing does not consider jobs prior to that date.
# Default value: 2009-01-01.
#DGAS_IGNORE_JOBS_LOGGED_BEFORE="2011-11-01"

# Main CE of the site.
# ATTENTION: set this variable only in the case of site with a “singleLRMS”
# in which there are more than one CEs or local submission hosts (i.e. host
# from which you may submit jobs directly to the batch system).
# In this case, DGAS_USE_CE_HOSTNAME parameter must be set to the same value
# for all hosts sharing the lrms and this value can be arbitrary chosen among
# these submitting hostnames (you may choose the best one).
# Otherwise leave it commented.
#DGAS_USE_CE_HOSTNAME=""

# Path for the batch-system log files.
# * for torque/pbs:
# DGAS_ACCT_DIR=/var/torque/server_priv/accounting
# * for LSF:
# DGAS_ACCT_DIR=lsf_install_path/work/cluster_name/logdir
# * for SGE:
# DGAS_ACCT_DIR=/opt/sge/default/common/
DGAS_ACCT_DIR=/var/torque/server_priv/accounting

# Full path to the 'condor_history' command, used to gather DGAS usage records
# when Condor is used as a batch system. Otherwise leave it commented.
#DGAS_CONDOR_HISTORY_COMMAND=""
<--/twistyPlugin-->

<--/twistyPlugin twikiMakeVisibleInline-->
# ll /etc/grid-security/host*
-rw-r--r-- 1 root root 1440 Oct 18 09:31 /etc/grid-security/hostcert.pem
-r-------- 1 root root  887 Oct 18 09:31 /etc/grid-security/hostkey.pem
<--/twistyPlugin-->

<--/twistyPlugin twikiMakeVisibleInline-->

IMPORTANT: The updated EPEL5 build of torque-2.5.7-1 as compared to previous versions enables munge as an inter node authentication method.

  • verify that munge is correctly installed:
# rpm -qa | grep munge
munge-libs-0.5.8-8.el5
munge-0.5.8-8.el5
  • On one host (for example the batch server) generate a key by launching:
# /usr/sbin/create-munge-key

# ls -ltr /etc/munge/
total 4
-r-------- 1 munge munge 1024 Jan 13 14:32 munge.key
  • Copy the key, /etc/munge/munge.key to every host of your cluster, adjusting the permissions:
# chown munge:munge /etc/munge/munge.key
  • Start the munge daemon on each node:
# service munge start
Starting MUNGE:                                            [  OK  ]

# chkconfig munge on

<--/twistyPlugin-->

<--/twistyPlugin twikiMakeVisibleInline-->

<--/twistyPlugin-->

<--/twistyPlugin twikiMakeVisibleInline-->
 
<--/twistyPlugin-->

Revisions

Revision 32012-01-17 - AlessandroPaolini

Line: 1 to 1
 
META TOPICPARENT name="WebHome"

Notes about Installation and Configuration of a CREAM Computing Element using Torque (WORK IN PROGRESS)

  • These notes are provided by site admins on a best effort base as a contribution to the IGI communities and MUST not be considered as a subsitute of the Official IGI documentation.
  • This document is addressed to site administrators responsible for middleware installation and configuration.
Changed:
<
<
  • The goal of this page is to provide some hints and examples on how to install and configure an IGI CREAM CE service based on EMI middleware, in no glite-cluster mode, with TORQUE as batch system on the same host
>
>
  • The goal of this page is to provide some hints and examples on how to install and configure an IGI CREAM CE service based on EMI middleware, in no cluster mode, with TORQUE as batch system on the same host
 
Line: 17 to 17
 
  1. CREAM v.1.13
  2. CREAM TORQUE module v. 1.0.0-1
Changed:
<
<

Service installation

>
>

Service installation

 %TWISTY{ mode="div" showlink=" O.S. and Repos "
Line: 90 to 90
  </>
<--/twistyPlugin-->
Added:
>
>

Service configuration

You have to copy the configuration files in another path, for example root, and set them properly (see later):
# cp -r /opt/glite/yaim/examples/siteinfo/* .

Create the vo.d directory for the VO configuration file (you can decide if keep the VO information in the site.def or putting them in the vo.d directory)

# mkdir vo.d

<--/twistyPlugin twikiMakeVisibleInline-->
SUGGESTION: use the same site-info.def for CREAM and WNs
<--/twistyPlugin-->
 

Revisions

Date Comment
2012-01-16 First draft

Revision 22012-01-16 - AlessandroPaolini

Line: 1 to 1
 
META TOPICPARENT name="WebHome"
Changed:
<
<

Notes about Installation and Configuration of a CREAM Computing Element based on Torque

>
>

Notes about Installation and Configuration of a CREAM Computing Element using Torque (WORK IN PROGRESS)

 
  • These notes are provided by site admins on a best effort base as a contribution to the IGI communities and MUST not be considered as a subsitute of the Official IGI documentation.
  • This document is addressed to site administrators responsible for middleware installation and configuration.
Changed:
<
<
  • The goal of this page is to provide some hints and examples on how to install and configure an IGI CREAM CE service based on EMI middleware.
>
>
  • The goal of this page is to provide some hints and examples on how to install and configure an IGI CREAM CE service based on EMI middleware, in no glite-cluster mode, with TORQUE as batch system on the same host
 
Added:
>
>
 
Added:
>
>

References

  1. About IGI - Italian Grid infrastructure
  2. About IGI Release
  3. IGI Official Installation and Configuration guide
  4. EMI CREAM System Administrator Guide
  5. Troubleshooting Guide for Operational Errors on EGI Sites
  6. Grid Administration FAQs page
  7. CREAM v.1.13
  8. CREAM TORQUE module v. 1.0.0-1

Service installation

<--/twistyPlugin twikiMakeVisibleInline-->

O.S. and Repos

  • Starts from a fresh installation of Scientific Linux 5.x (x86_64).
# cat /etc/redhat-release 
Scientific Linux SL release 5.7 (Boron) 

* Install the additional repositories: EPEL, Certification Authority, UMD

# yum install yum-priorities yum-protectbase
# cd /etc/yum.repos.d/
# rpm -ivh http://mirror.switch.ch/ftp/mirror/epel//5/x86_64/epel-release-5-4.noarch.rpm
# wget http://repo-pd.italiangrid.it/mrepo/repos/egi-trustanchors.repo
# rpm -ivh http://repo-pd.italiangrid.it/mrepo/EMI/1/sl5/x86_64/updates/emi-release-1.0.1-1.sl5.noarch.rpm
# wget http://repo-pd.italiangrid.it/mrepo/repos/igi/sl5/x86_64/igi-emi.repo

  • Be sure that SELINUX is disabled (or permissive). Details on how to disable SELINUX are here:

# getenforce 
Disabled

  • Check the repos list (sl-*.repo are the repos of the O.S. and they should be present by default).

# ls /etc/yum.repos.d/
egi-trustanchors.repo  
emi1-third-party.repo emi1-base.repo emi1-updates.repo
igi-emi.repo
epel.repo epel-testing.repo  
sl-contrib.repo sl-fastbugs.repo sl-security.repo sl-testing.repo sl-debuginfo.repo sl.repo sl-srpms.repo
<--/twistyPlugin-->

<--/twistyPlugin twikiMakeVisibleInline-->
# yum clean all
Loaded plugins: downloadonly, kernel-module, priorities, protect-packages, protectbase, security, verify, versionlock
Cleaning up Everything

# yum install ca-policy-egi-core
# yum install xml-commons-apis
# yum install emi-cream-ce
# yum install emi-torque-server emi-torque-utils
# yum install glite-dgas-common glite-dgas-hlr-clients glite-dgas-hlr-sensors glite-dgas-hlr-sensors-producers yaim-dgas

see here for details

<--/twistyPlugin-->

Revisions

Date Comment
2012-01-16 First draft
  -- AlessandroPaolini - 2012-01-16

Revision 12012-01-16 - AlessandroPaolini

Line: 1 to 1
Added:
>
>
META TOPICPARENT name="WebHome"

Notes about Installation and Configuration of a CREAM Computing Element based on Torque

  • These notes are provided by site admins on a best effort base as a contribution to the IGI communities and MUST not be considered as a subsitute of the Official IGI documentation.
  • This document is addressed to site administrators responsible for middleware installation and configuration.
  • The goal of this page is to provide some hints and examples on how to install and configure an IGI CREAM CE service based on EMI middleware.

-- AlessandroPaolini - 2012-01-16

META TOPICMOVED by="AlessandroPaolini" date="1326712426" from="SiteAdminCorner.NotesAboutInstallationAndConfigurationOfCREAM" to="SiteAdminCorner.NotesAboutInstallationAndConfigurationOfCREAMAndTORQUE"
 
This site is powered by the TWiki collaboration platformCopyright © 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback