1 Installazione di un CE CREAM Alessandro Paolini (INFN-CNAF) III corso di formazione INFN per amministratori di siti GRID INFN-CATANIA 2 – 6 Novembre 2009

2 Link utili Guida all’installazione del middleware, release INFNGRID 3.1 per sl4: – doc:guides:install-3_1http://igrelease.forge.cnaf.infn.it/doku.php?id= doc:guides:install-3_1 CE Cream troubleshooting: – REAMTroubleshootinghttp://grid.pd.infn.it/cream/field.php?n=Main.C REAMTroubleshooting

3 Procedura d’installazione Scelta dei repository cd /etc/yum.repos.d/ wget

4 Procedura d’installazione Azzeramento del repository: yum clean all Installazione di java e tomcat yum install java sun-compat tomcat5 Installazione delle CA: yum install lcg-CA installazione metapackage (CE Cream che si appoggia ad un server lsf esterno) yum install ig_CREAM_LSF

5 configurazione ~]# ls /opt/glite/yaim/examples/siteinfo/ ig-site-info.def services site-info.def vo.d ~]# ls /opt/glite/yaim/examples/siteinfo/services/ glite-creamce glite-mpi_ce ig-hlr ig-lfc_oracle ig-mpi_ce ig-px glite-mpi glite-mpi_wn ig-lfc_mysql ig-mpi ig-mpi_wn Yaim configuration file for the IG release Additional yaim service modules Copy the siteinfo content in root cp -r /opt/glite/yaim/examples/siteinfo/* /root/ Edit (and rename) ig-site-info.def and cancel site-info.def Edit services/glite-cream

6 variabili

7 services/glite-creamce ~]# less services/glite-creamce # # 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=set_to_fully_qualified_host_name_of_localhost # # CREAM database user CREAM_DB_USER=set_to_your_cream_db_user CREAM_DB_PASSWORD=set_to_your_cream_db_user # # 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 continua…

8 services/glite-creamce # # The following variables already have a default value defined in # defaults/glite-creamce.pre, but if needed you can overwrite their values # # CREAM databases settings # By default the cream db is on localhost and accessible from localhost. # Setting ACCESS_BY_DOMAIN to yes, you allow the cream db access from all # computers in your domain. #ACCESS_BY_DOMAIN=no # # To refer to the the port where Blah Log Parser is running #BLP_PORT=33333 # # To refer to the parser listening cream port #CREAM_PORT=56565 # Value to be published as GlueCEStateStatus instead of Production #CREAM_CE_STATE=Special # # The following parameter sets the BLAH jobId prefix (it MUST be 6 chars # long, begin with cr and terminate by '_') # It is important in case of more than one ce connecting to the same blparser. # In this case, it is better that each CREAM_CE has its own prefix #BLAH_JOBID_PREFIX=cream_

9 ig-site-info.def Potete usare gli stessi valori delle variabili nel site.def del CE lcg

10 ig-site-info.def WN_LIST, USERS_CONF, GROUPS_CONF, MYSQL_PASSWORD, SITE_NAME, SITE_ , SITE_LAT, SITE_LONG, CE_HOST, CE_CAPABILITY, CE_OTHERDESCR, BATCH_SERVER, JOB_MANAGER, CE_BATCH_SYS, BATCH_LOG_DIR, BATCH_VERSION, BATCH_CONF_DIR, DPM_HOST or STORM_HOST, SE_LIST, SE_MOUNT_INFO_LIST, VOS, QUEUES, _GROUP_ENABLE Potete usare gli stessi valori delle variabili nel site.def del CE lcg

11 Operazioni aggiuntive Sul master server, aggiungere in /etc/exports. (rw,no_root_squash) /etc/grid-security/gridmapdir. (rw,no_root_squash) Quindi far ripartire nfs e fare un refresh delle directory esportate service nfs start exportfs -r Inserire il CE-CREAM nel cluster lsf: In /opt/lsf/conf/.../lsb.cluster ed lsb.host aggiungere le righe relative al nome del CE- CREAM Lanciare: lsadmin reconfig loadamin reconfig

12 Operazioni aggiuntive Creare le directory e montarle mkdir -p mkdir -p /etc/grid-security/gridmapdir mount mount /etc/grid-security/gridmapdir Sul CE secondario, aggiungere in /etc/fstab:. : nfs rw,defaults 0 0. :/etc/grid-security/gridmapdir /etc/grid-security/gridmapdir nfs rw,defaults 0 0 Creare l’utente “lsadmin”

13 Lancio di ig-yaim # /opt/glite/yaim/bin/ig_yaim -c -s ig-site-info.def -n ig_CREAM_LSF Lanciare quindi …e buona fotuna! Al termine della configurazione, eseguire i seguenti comandi: service tomcat5 stop /opt/glite/etc/init.d/glite-ce-blparser start service tomcat5 start

14 processi root ? S<s Oct27 0:23 /usr/share/lsf/7.0/linux2.6-glibc2.3-x86/etc/lim root ? S<s Oct27 0:00 \_ /usr/share/lsf/7.0/linux2.6-glibc2.3-x86/etc/melim root ? S< Oct27 0:00 | \_ /bin/sh /usr/share/lsf/7.0/linux2.6-glibc2.3-x86/etc/elim.data root ? S< 08:57 0:00 | | \_ sleep 60 root ? S< Oct27 0:00 | \_ /bin/sh /usr/share/lsf/7.0/linux2.6-glibc2.3-x86/etc/elim.diskspaceXslot root ? S< 08:56 0:00 | | \_ sleep 60 root ? S< Oct27 0:00 | \_ /usr/share/lsf/7.0/linux2.6-glibc2.3-x86/etc/elim.jsdl root ? S Oct27 0:00 \_ /usr/share/lsf/7.0/linux2.6-glibc2.3-x86/etc/pim root ? S Oct27 0:00 \_ /usr/share/lsf/7.0/linux2.6-glibc2.3-x86/etc/pem root ? S<s Oct27 0:00 /usr/share/lsf/7.0/linux2.6-glibc2.3-x86/etc/res root ? S Oct27 0:00 /bin/sh /usr/bin/mysqld_safe --datadir=/var/lib/mysql -- socket=/var/lib/mysql/mysql.sock --err-log=/var/log/mysqld.log --pid-file=/var/run/mysqld/mysqld.pid mysql ? Sl Oct27 0:02 \_ /usr/libexec/mysqld --basedir=/usr --datadir=/var/lib/mysql --user=mysql --pid- file=/var/run/mysqld/mysqld.pid --skip-external-locking --socket=/var/lib/mysql/mysql.sock lsf mysql

15 processi gridftp BLParser root ? Ss Oct27 0:00 /opt/globus/sbin/globus-gridftp-server -p d error,warn,info -l /var/log/gridftp- session.log -Z /var/log/globus-gridftp.log -s root ? S Oct27 0:00 /opt/glite/bin/blparser_master root ? Sl Oct27 0:25 \_ /opt/glite/bin/BLParserLSF -d 1 -l /opt/glite/var/log/glite-lsfparser.log -b /usr/share/lsf/7.0/linux2.6-glibc2.3-x86/bin -c lsf_install_path/conf -p m root ? S Oct27 0:00 /opt/glite/bin/blparser_master Vedrete anche tomcat, bdii, dgas, glite-lb*….

16 Verifica della conf # wget # chmod +x CheckCreamConf.pl #./CheckCreamConf.pl This is CheckCreamConf v This is devce.cnaf.infn.it Checking versions of relevant RPMs... Checking if some needed environment variables are defined... Checking the installed CREAM and CEMon wars... Checking if there are old jar arounds... Checking glexec executable... Checking BLAH configuration... Checking some info published in the resource BDII... Checking CREAM conf file... Done: please check CheckCreamConf.log

17 per testarlo Controllare le informazioni pubblicate sulla 2170 Controllare via web all’indirizzo: – :8443/ce-cream/serviceshttps:// Provare un globus-url-copy globus-url-copy gsiftp://devce.cnaf.infn.it:2811/opt/glite/yaim/etc/versions/ig-yaim file:/tmp/ig-version-cnaf Provare a mandare un job $ glite-ce-allowed-submission devce.cnaf.infn.it: :18:34,402 WARN - No configuration file suitable for loading. Using built-in configuration Job Submission to this CREAM CE is enabled

18 per testarlo $ less wmcream_var.conf [ OutputStorage = "/tmp/jobOutput"; JdlDefaultAttributes = [ RetryCount = 3; rank = - other.GlueCEStateEstimatedResponseTime; PerusalFileEnable = false; AllowZippedISB = true; requirements = other.GlueCEStateStatus != "Production"; ShallowRetryCount = 10; SignificantAttributes = {"Requirements", "Rank", "FuzzyRank"}; MyProxyServer = "myproxy.cnaf.infn.it"; ]; virtualorganisation = "infngrid"; ErrorStorage = "/tmp"; ListenerStorage = "/tmp"; WMProxyEndpoints = {" ] glite-wms-job-submit -a -c wmcream_var.conf zaza.jdl glite-ce-job-submit --autm-delegation -r bocecream.bo.infn.it:8443/cream-pbs-cert test.jdl oppure