140 likes | 301 Views
WMS+LB Server Installation. Eduardo Murrieta DGSCA-UNAM Based on the presentation of Tony Calanducci INFN – Catania Fourth EELA Tutorial for Managers and Users Mexico City, 28 August - 01 September 2006. Outline. Installation of the WMSLB Testing the installation
E N D
WMS+LB Server Installation • Eduardo Murrieta • DGSCA-UNAM • Based on the presentation of Tony Calanducci • INFN – Catania • Fourth EELA Tutorial for Managers and Users • Mexico City, 28 August - 01 September 2006
Outline • Installation of the WMSLB • Testing the installation • Logs location and references
Pre-requisites • Do all the pre-requirement steps illustrated in the IntroSysAdmin tutorial • Java SDK • Date and Time • GILDA CA and VOMS RPM • Check Host certificates and permissions • Download and install glite-yaim and gilda_ig-yaim
Firewall • WMS+LB services requires a wide range of ports • Set the firewall allowing input for any protocol in the range of ports > 1023 • Edit the file /etc/sysconfig/iptables and • Replace the last line • -A RH-Firewall-1-INPUT –j REJECT - -reject-with icmp-host-prohibited • With these two • -A RH-Firewall-1-INPUT -p tcp - -dport 1:1023 -j REJECT - -reject-with icmp-host-prohibited • -A RH-Firewall-1-INPUT -p udp - -dport 1:1023 -j REJECT - -reject-with icmp-host-prohibited • Restart the iptables with the new rules • # service iptables restart && service ntpd restart
WMSLS YAIM relevant variables • Edit your site-info.def file • MY_DOMAIN=super.unam.mx • WMS_HOST=eela-XXX.$MY_DOMAIN <- Replace XXX to your hostname • PX_HOST=grid001.ct.infn.it • BDII_HOST=eela-136.$MY_DOMAIN • MON_HOST=rgmasrv.ct.infn.it • AMGA_HOST=amga.ct.infn.it • REG_HOST=rgmasrv.ct.infn.it • LFC_HOST=lfc-gilda.ct.infn.it • MYSQL_PASSWORD=MysQL • GRID_TRUSTED_BROKERS=“ • ’/C=IT/O=GILDA/OU=Host/L=EELA/CN=eela-XXX.super.unam.mx/emailAddress=roberto.barbera@ct.infn.it’ • ” • You can get this DN with: • openssl x509 -in /etc/grid-security/hostcert.pem -subject -noout
Middleware installation with YAIM • We are ready to install the services running: • /opt/glite/bin/gilda_ig_install_node /root/my-site-info.def GILDA_ig_WMSLB • This command will download and install all the needed packages. • Now we can configure the node: • /opt/glite/bin/gilda_ig_configure_node /root/my-site-info.def GILDA_ig_WMSLB
Applying WMS Patches • Stop all the WMSLB services: • service gLite stop • Download and install the following RPMs: • wget http://grid-it.cnaf.infn.it/certification/downloads/glite-security-gsoap-plugin-2.2.3-0_U200605160140.i386.rpm • rpm -Uvh glite-security-gsoap-plugin-2.2.3-0_U200605160140.i386.rpm • wget http://grid-it.cnaf.infn.it/certification/downloads/glite-wms-jobsubmission-1.5.8-1.i386.rpm • rpm -Uvh glite-wms-jobsubmission-1.5.8-1.i386.rpm
WMS Patches (II) • Edit the file /opt/glite/etc/glite_wms.conf: • add the following line to the LogMonitor section to improve Condor reliability: • GlobusDownTimeout = 7200; • and change the following parameters in the WorkloadManager section to improve matchmaking performances: • PipeDepth = 200; • WorkerThreads = 20; (you have to rename the NumberOfWorkerThreads parameter into WorkerThreads) • Restart gLite services: • service gLite start
Testing the WMS • Login to a user interface (eela-132.super.unam.mx): • Edit rb-test.conf with the following line (replace XXX to match your WMS+LB host): • [ • VirtualOrganisation = "gilda"; • NSAddresses = { • “eela-XXX.super.unam.mx:7772" • }; • LBAddresses = { • {“eela-XXX.super.unam.mx:9000"} • }; • MyProxyServer = "grid001.ct.infn.it"; • ] • Try: • glite-job-list-match –config-vo rb-test.conf hostname.jdl • And • glite-job-submit –config-vo rb-test.conf hostname.jdl • Monitor the run of your job and if you will be able to retrieve its output your are in the right way!
Testing the WMS (II) • $ glite-job-submit --config-vo rb-test.conf hostname.jdl • Selected Virtual Organisation name (from proxy certificate extension): gilda • Connecting to host eela-XXX.super.unam.mx, port 7772 • Logging to host eela-XXX.super.unam.mx, port 9002 • ********************************************************************************* • JOB SUBMIT OUTCOME • The job has been successfully submitted to the Network Server. • Use glite-job-status command to check job current status. Your job identifier is: • - https://eela-XXX.super.unam.mx:9000/BdCMtt1wtlLamqmXEJN8DQ • *********************************************************************************
Testing the WMS (III) • $ glite-job-status https://eela-XXX.super.unam.mx:9000/BdCMtt1wtlLamqmXEJN8DQ • ************************************************************* • BOOKKEEPING INFORMATION: • Status info for the Job : https://eela-XXX.super.unam.mx:9000/BdCMtt1wtlLamqmXEJN8DQ • Current Status: Running • Status Reason: Job successfully submitted to Globus • Destination: grid010.ct.infn.it:2119/jobmanager-lcgpbs-long • Submitted: Wed Aug 23 05:35:50 2006 CEST • ************************************************************* • $ glite-job-status https://eela-XXX.super.unam.mx:9000/BdCMtt1wtlLamqmXEJN8DQ • ************************************************************* • BOOKKEEPING INFORMATION: • Status info for the Job : https://eela-XXX.super.unam.mx:9000/BdCMtt1wtlLamqmXEJN8DQ • Current Status: Done (Success) • Exit code: 0 • Status Reason: Job terminated successfully • Destination: grid010.ct.infn.it:2119/jobmanager-lcgpbs-long • Submitted: Wed Aug 23 05:35:50 2006 CEST • *************************************************************
Testing the WMS (IV) • $ glite-job-output https://eela-XXX.super.unam.mx:9000/BdCMtt1wtlLamqmXEJN8DQ • Retrieving files from host: eela-XXX.super.unam.mx ( for https://eela-134.super.unam.mx:9000/BdCMtt1wtlLamqmXEJN8DQ ) • ********************************************************************************* • JOB GET OUTPUT OUTCOME • Output sandbox files for the job: • - https://eela-134.super.unam.mx:9000/BdCMtt1wtlLamqmXEJN8DQ • have been successfully retrieved and stored in the directory: • /tmp/glite/glite-ui/mexicocityXX_BdCMtt1wtlLamqmXEJN8DQ • ********************************************************************************* • $ cd /tmp/glite/glite-ui/mexicocityXX_BdCMtt1wtlLamqmXEJN8DQ/ • $ ls • hostname.err hostname.out • $ cat hostname.err • $ cat hostname.out • grid047.ct.infn.it
Logs • Logs can be found in /var/log/glite • networkserver_events.log • workload_manager_events.log • They are the best starting point to deal with eventual problems. • You can monitor and follow the jobs • See if the BDII and RGMA purchasing is working fine
References • gLite 3.0 General Installation manual • http://grid-deployment.web.cern.ch/grid-deployment/documentation/LCG2-Manual-Install/ • GILDA gLite 3.0 installation manual: • https://gilda.ct.infn.it/docs/GILDAsiteinstall-3_0_0.html • GILDA gLite 3.0 installation notes wiki • https://grid.ct.infn.it/twiki/bin/view/GILDA/GliteElementsInstallation • EGEE Users Guide: WMS Service • http://documents.eu-eela.org/getfile.py?docid=188&name=EGEE-JRA1-TEC-572489-WMS-guide-v0-2&format=pdf&version=1