Before Starting

1. HOSTNAME: cert-09.cnaf.infn.it
2. OS: SL5 X86_64 Installed + Network
3. Host certificate required: must be copied under /etc/grid-security/ before yaim configuration

LSF INSTALLATION

Install lsf on lsf master following instructions provided by vendor (example):

1. Get the LSF installation script tar file lsf6.0_lsfinstall.tar.Z and extract it (e.g., # zcat lsf6.0_lsfinstall.tar.Z | tar xvf -)
2. Read lsf6.0_lsfinstall/README for information about the contents of lsf6.0_lsfinstall.tar.Z
3. Get the LSF distribution tar files for all host types you need, and put them in the same directory as lsf6.0_lsfinstall.tar.Z (e.g., for AIX: lsf6.0_aix4.tar.Z). Do not extract the distribution tar files.
4. Get an LSF license key and create an LSF license file (license.dat) in the same directory as the distribution files and lsf6.0_lsfinstall.tar.Z
5. Log on as root to the LSF installation file server. If you are not root, you can continue to install LSF, but by default, only root can start the LSF daemons.
6. Edit lsf6.0_lsfinstall/install.config to specify the installation variables you want.
7. Choose an LSF installation directory on your file server (e.g., LSF_TOP="/usr/share/lsf")
8. Choose LSF hosts (master host, server hosts, and client-only hosts; e.g., LSF_ADDSERVERS="hosta hostb hostc")
9. Choose a cluster name (39 characters or less with no white spaces; e.g., LSF_CLUSTER_NAME="cluster1")
10. Choose a primary LSF administrator (owns the LSF configuration files and log files; e.g., LSF_ADMINS="lsfadmin")

1. Required install.config variables
   • LSF_TOP="/path"
   • LSF_ADMINS="user_name [user_name ...]"
   • LSF_CLUSTER_NAME="cluster_name"

1. Variables that require an absolute path
   • LSF_TOP="/path"
   • LSF_TARDIR="/path"
   • LSF_LICENSE="/path/license_file"

1. Change to lsf6.0_lsfinstall/.
2. # Run ./lsfinstall -f install.config.
3. # Before using your cluster, follow the steps in these documents:
   • lsf6.0_lsfinstall/lsf_getting_started.html to set up your LSF hosts, start LSF, and test your new LSF cluster
   • lsf6.0_lsfinstall/lsf_quick_admin.html to learn more about your new LSF cluster

1. # Customize *. conf/ adding hosts with theirs characteristic *. conf/lsbatch//configdir/lsb.host *. conf/lsbatch//configdir/lsb.queues *. conf/lsbatch//configdir/lsb.users

1. # Be sure the directory LSF_TOP is available(mounted) in each host of the cluster

After installing Platform LSF

1. Optional. Run hostsetup to set up LSF hosts.
   1. Log on to each LSF server host as root. Start with the LSF master host.
2. If you are not root, you can continue with host setup, but by default, only root can start the LSF daemons.
   1. Run hostsetup on each LSF server host. For example:
      1. # cd /usr/share/lsf/6.0/install
      2. # ./hostsetup --top="/usr/share/lsf" --boot="y"
      3. For complete hostsetup usage, enter hostsetup -h.
   2. Log on to the LSF master host as root, and set your LSF environment:
      • For csh or tcsh: % source LSF_TOP/conf/cshrc.lsf
      • For sh, ksh, or bash: $ . LSF_TOP/conf/profile.lsf
3. Run lsfstartup to start the cluster.
4. Test your cluster by running some basic LSF commands (e.g., lsid, lshosts, bhosts)

After testing your cluster, be sure all LSF users include LSF_CONFDIR/cshrc.lsf or LSF_CONFDIR/profile.lsf in their .cshrc or .profile.

This last part can be done using two script (thanks to Simone dalla Fina and Enrico Ferro) located in /opt/lsf/scripts/install_lsf_client.sh /opt/lsf/scripts/install_lsf_master.sh customized for your cluster.

Service Installation

1. Repositories ( see EMI basic configuration):
   1. egi-trustanchors.repo + emi1.repo + epel.repo
2. $> yum clean all
3. $> yum makecache
4. $> yum install emi-cream-ce emi-lsf-utils
   1. $> yum install lcg-CA
   2. $> yum install yum-protectbase.noarch
   3. $> yum install ca-policy-egi-core

Service Configuration

1. PREPARING FOR YAIM CONFIGURATION:
   1. COPY YAIM FILES UNDER ROOT: $>cp -r /opt/glite/yaim/examples/siteinfo/ /root/siteinfo/
   2. TESTERS VO files: follow description at [[https://twiki.cern.ch/twiki/bin/view/EMI/TestBed] [VO TESTERS HOWTO section 3.5]], download the following files: groups.conf, users.conf + vo.d directory
   3. CONTENT of /root/siteinfo: site-info.def + groups.conf + users.conf + vo.d (DIR) + wn-list.conf + services/
   4. Find below the settings for Inter-Component testing EMI Testbed. Of course you will need to adapt these values to your own site (hostnames of other servers (SE, BDII, ARGUS..) , passwd, etc. etc. )

[root@cert-09 siteinfo]# cat wn-list.conf 
emitestbed11.cnaf.infn.it
emitestbed14.cnaf.infn.it

[root@cert-09 siteinfo]# grep -v "#" site-info.def services/glite-* |grep "="
site-info.def:YAIM_LOGGING_LEVEL=DEBUG
site-info.def:MY_DOMAIN="cnaf.infn.it"
site-info.def:INSTALL_DIR="/root/siteinfo"
site-info.def:WN_LIST=$INSTALL_DIR/wn-list.conf
site-info.def:USERS_CONF=$INSTALL_DIR/users.conf
site-info.def:GROUPS_CONF=$INSTALL_DIR/groups.conf
site-info.def:FUNCTIONS_DIR=/opt/glite/yaim/functions
site-info.def:OUTPUT_STORAGE=/tmp/jobOutput
site-info.def:JAVA_LOCATION="/usr/lib/jvm/java"
site-info.def:CRON_DIR=/etc/cron.d
site-info.def:MYSQL_PASSWORD="XXXXXXXXXXXX"
site-info.def:CE_HOST=cert-09.$MY_DOMAIN
site-info.def:CE_PHYSCPU=2
site-info.def:CE_LOGCPU=2
site-info.def:CE_CPU_MODEL=XEON
site-info.def:CE_CPU_VENDOR=Intel
site-info.def:CE_CPU_SPEED=2800
site-info.def:CE_OS="ScientificCERNSLC"
site-info.def:CE_OS_RELEASE="4.6"
site-info.def:CE_OS_VERSION="Beryllium"
site-info.def:CE_OS_ARCH=i686
site-info.def:CE_MINPHYSMEM=2048
site-info.def:CE_MINVIRTMEM=4096
site-info.def:CE_SMPSIZE=2
site-info.def:CE_SI00=1286
site-info.def:CE_SF00=1496
site-info.def:CE_OUTBOUNDIP=TRUE
site-info.def:CE_INBOUNDIP=FALSE
site-info.def:CE_RUNTIMEENV="
site-info.def:BASE_SW_DIR=/flatfiles/SE01/exp_soft
site-info.def:BATCH_SERVER=cert-09.$MY_DOMAIN
site-info.def:JOB_MANAGER=lsf
site-info.def:CE_BATCH_SYS=lsf
site-info.def:BATCH_BIN_DIR=/opt/lsf/7.0/linux2.6-glibc2.3-x86_64/bin
site-info.def:BATCH_VERSION=7.0
site-info.def:BATCH_LOG_DIR=/opt/lsf/work/EMI_testbed/logdir/
site-info.def:BATCH_CONF_DIR=/opt/lsf/conf
site-info.def:CLASSIC_HOST=prod-se-01.pd.infn.it
site-info.def:CLASSIC_STORAGE_DIR=/flatfiles/SE00
site-info.def:SE_LIST="$CLASSIC_HOST"
site-info.def:BDII_HOST=certtbrc-bdii-top.cern.ch
site-info.def:BDII_DELETE_DELAY=0
site-info.def:SITE_BDII_HOST=certtbrc-bdii-site.cern.ch
site-info.def:SITE_NAME="EMI1-RC-INFN"
site-info.def:BDII_SITE_TIMEOUT=120
site-info.def:BDII_RESOURCE_TIMEOUT=`expr "$BDII_SITE_TIMEOUT" - 5`
site-info.def:GIP_RESPONSE=`expr "$BDII_RESOURCE_TIMEOUT" - 5`
site-info.def:GIP_FRESHNESS=60
site-info.def:GIP_CACHE_TTL=300
site-info.def:GIP_TIMEOUT=150
site-info.def:GIP_CACHE_DIR=/var/tmp/lcg-info-dynamic-cache
site-info.def:BDII_HTTP_URL="http://grid-it.cnaf.infn.it/fileadmin/bdii/egee-all-sites.conf"
site-info.def:VOS="dteam testers.eu-emi.eu"
site-info.def:ALL_VOMS_VOS="dteam testers.eu-emi.eu"
site-info.def:QUEUES="demo"
site-info.def:DEMO_GROUP_ENABLE="dteam testers.eu-emi.eu"
site-info.def:VO_SW_DIR=/opt/exp_soft
site-info.def:VO_DTEAM_SW_DIR=$VO_SW_DIR/dteam
site-info.def:VO_DTEAM_DEFAULT_SE=$CLASSIC_HOST
site-info.def:VO_DTEAM_STORAGE_DIR=$CLASSIC_STORAGE_DIR/dteam
site-info.def:VO_DTEAM_VOMS_SERVERS='vomss://voms.hellasgrid.gr:8443/voms/dteam?/dteam/'
site-info.def:VO_DTEAM_VOMSES="'dteam voms.hellasgrid.gr 15004 /C=GR/O=HellasGrid/OU=hellasgrid.gr/CN=voms.hellasgrid.gr dteam 24' 'dteam voms2.hellasgrid.gr 15004 /C=GR/O=HellasGrid/OU=hellasgrid.gr/CN=voms2.hellasgrid.gr dteam 24'"
site-info.def:VO_DTEAM_VOMS_CA_DN="'/C=GR/O=HellasGrid/OU=Certification Authorities/CN=HellasGrid CA 2006' '/C=GR/O=HellasGrid/OU=Certification Authorities/CN=HellasGrid CA 2006'"
site-info.def:MON_HOST=notreallyneeded.$MY_DOMAIN
site-info.def:APEL_DB_PASSWORD="notreallyneeded"
services/glite-creamce:CEMON_HOST=cert-09.pd.infn.it
services/glite-creamce:ACCESS_BY_DOMAIN=no
services/glite-creamce:CREAM_DB_USER=XXXXXXXX
services/glite-creamce:CREAM_DB_PASSWORD=XXXXXXXXXXX
services/glite-creamce:BLPARSER_HOST=cert-09.pd.infn.it
services/glite-creamce:BLP_PORT=33333
services/glite-creamce:CREAM_PORT=56565
services/glite-creamce:BLAH_JOBID_PREFIX=cre09
services/glite-creamce:RESET_CREAM_DB_GRANTS=yes
services/glite-creamce:SE_MOUNT_INFO_LIST="none"
services/glite-creamce:CE_OTHERDESCR="Cores=1"
services/glite-creamce:CE_CAPABILITY="CPUScalingReferenceSI00=10"
services/glite-creamce:GLEXEC_CREAM_LOG_DESTINATION=file
services/glite-creamce:USE_ARGUS=no
services/glite-creamce:ARGUS_PEPD_ENDPOINTS="https://emitestbed10.cnaf.infn.it:8154/authz"
services/glite-creamce:CREAM_PEPC_RESOURCEID="http://cnaf.infn.it/cert-09"

Note :

1. YAIM variables set into /root/siteinfo/services/XXXfiles will overrid variables in siteinfo.def file with same name
2. some YAIM variables are set in the yaim defaults files: /opt/glite/yaim//defaults/XXXfiles

1. After all yaim files are OK run the following commands:
   1. $> /opt/glite/yaim/bin/yaim -c -s /root/siteinfo/site-info.def -n creamCE -n LSF_utils
2. If everything's OK yaim will end with (BTW yaim output is in /opt/glite/yaim/log/yaimlog file)

.....
  INFO: Configuration Complete.                                               [  OK  ]
  INFO: YAIM terminated succesfully.

Service Testing

1. Test daemons:

[root@cert-09 siteinfo]# service gLite status
*** tomcat5:
/etc/init.d/tomcat5 is already running (19310)

*** glite-lb-locallogger:
glite-lb-logd running as 20936
glite-lb-interlogd running as 20936

*** glite-ce-blahparser:
BNotifier (pid 18442) is running...
BUpdaterLSF (pid 18446) is running...


root@cert-09 siteinfo]# /etc/init.d/lsf status
Show status of the LSF subsystem
lim (pid 28815) is running...
res (pid 28817) is running...
sbatchd (pid 28819) is running...

1. Other basic test on CREAM CE was done testing job submission as reported at this page EMI gLite Job Management Tests Page

-- DaniloDongiovanni - 24-May-2011