1. WMS LB Installation and Configuration
Lanxin Ma (马兰馨)
IHEP, CAS
Asia EPIKH School for Grid Site Administrators

2. WMS LB
The Workload Management System (WMS) is the gLite service that allows users to submit jobs, and performs all tasks required to execute them, without exposing the user to the complexity of the Grid.
The Logging and Bookkeeping service (LB) tracks jobs in terms of event (important points of job life, e.g. submission, finding a matching CE, starting execution etc.) gathered from various WMS components as well as CEs.

3. Workload Management System
The Workload Management System (WMS) consists of a set of Grid middleware components in charge of distributing and managing
jobs across Grid resources
Purpose of the Workload Manager (WM) is to accept and satisfy requests for job management coming from its clients
The WM hands over the job to an appropriate Computing Element (CE) for execution taking into account requirements and the preferences expressed in the job description.
The decision on which resource should be used is the outcome of the so called matchmaking process:
- requests from the users for their jobs are matched against the available resources and their features 3

4. gLite WMS Architecture4

5. gLite WMS Architecture
Job management
requests (submission,
cancellation) expressed
via a Job Description
Language (JDL) 5

6. gLite WMS Architecture
Finds an appropriate
CE for each submission
request, taking into account
job requests and preferences,
Grid status, utilization policies
on resources 6

7. gLite WMS Architecture
Keeps submission
requests
Requests are kept
for a while
if no resources are
immediately available 7 7

8. gLite WMS Architecture
Repository of resource
information
available to matchmaker
Updated via notifications
and/or active
polling on resources 8 8

9. gLite WMS Architecture
Performs the actual
job submission
and monitoring 9

10. gLite WMS Architecture
The LB is responsible to:
- Stores events generated by the various components of the WMS
- Querying the LB user can retrieve information about the status of the job 10

11. The instructions provided in this presentation assume that you are going to use a machine with Scientific Linux 4.8 installed.
Virtual Machine image (GILDA VM Base_SLC4._i386) available at: 11 11

12. ssh root@gildaXX.ihep.ac.cn XX = 25,...,28 Password:

13. Repository settings Specify the mrepo host:
export MREPO=
Configure the repository as follows:
REPOS="dag ig glite-generic lcg-ca glite-wms glite-lb"
Get repositories with:
for name in $REPOS;
do wget $MREPO/$name.repo -O /etc/yum.repos.d/$name.repo; done
Copy the gilda utils:
wget -O /etc/yum.repos.d/gilda.repo
To get a full mirror of GILDA repository:
wget -mp -nH -np
Follows a brief explanations of the used parameters:
-m This option is used to make mirrors. This means that the next time the command will be issued it will download just the updated files rather than the whole site again.
-p It will include other elements like images to correctly show the mirrored web pages
-nH This command avoids to create the subdirectories: ‘grid018.ct.infn.it/rep’ onthe destination
Follows a brief explanations of the used parameters:-mThis option is used to make mirrors. This means that the next time the command will be issued it will download just the updated files rather than the whole site again.-pIt will include other elements like images to correctly show the mirrored web pages -nHThis command avoids to create the subdirectories: ‘grid018.ct.infn.it/rep’ onthe destination
Then replace baseurl filed in any .repo file inside repos/ directorty
#!/bin/bash #
# Change repo host
MREPO_FROM=
MREPO_TO=
MREPO_FROM_ESCAPE=$(echo $MREPO_FROM | sed s/'\/'/'\\\/'/g)
MREPO_TO_ESCAPE=$(echo $MREPO_TO | sed s/'\/'/'\\\/'/g)
for repo in $(ls -1 *.repo) do
echo $repo
mv $repo $repo.todo
cat $repo.todo | sed s/"${MREPO_FROM_ESCAPE}"/"${MREPO_TO_ESCAPE}"/g > $repo
rm -f $repo.todo
done

14. Repository settings Add /etc/yum.repos.d/jpackage.repo #
# JPackage repositories
[jpackage5_generic_free]
name = JPackage 5 (generic free)
#baseurl =
baseurl =
# gpgkey =
gpgcheck = 0
enabled = 1
protect = 0
[jpackage5_generic_non-free]
name = JPackage 5 (generic non-free)
baseurl =
enabled = 0
protect = 1
To get a full mirror of GILDA repository:
wget -mp -nH -np
Follows a brief explanations of the used parameters:
-m This option is used to make mirrors. This means that the next time the command will be issued it will download just the updated files rather than the whole site again.
-p It will include other elements like images to correctly show the mirrored web pages
-nH This command avoids to create the subdirectories: ‘grid018.ct.infn.it/rep’ onthe destination
Follows a brief explanations of the used parameters:-mThis option is used to make mirrors. This means that the next time the command will be issued it will download just the updated files rather than the whole site again.-pIt will include other elements like images to correctly show the mirrored web pages -nHThis command avoids to create the subdirectories: ‘grid018.ct.infn.it/rep’ onthe destination
Then replace baseurl filed in any .repo file inside repos/ directorty
#!/bin/bash #
# Change repo host
MREPO_FROM=
MREPO_TO=
MREPO_FROM_ESCAPE=$(echo $MREPO_FROM | sed s/'\/'/'\\\/'/g)
MREPO_TO_ESCAPE=$(echo $MREPO_TO | sed s/'\/'/'\\\/'/g)
for repo in $(ls -1 *.repo) do
echo $repo
mv $repo $repo.todo
cat $repo.todo | sed s/"${MREPO_FROM_ESCAPE}"/"${MREPO_TO_ESCAPE}"/g > $repo
rm -f $repo.todo
done 14 14

15. System requirements Please check: If you have a valid hostname
To verify, type: hostname -f
To edit the hostname:
vim /etc/hosts
vim /etc/hostname
vim /etc/sysconfig/network
hostname <pc_name>

16. NTP Setting Install ntp: /etc/ntp.conf
yum install ntp
/etc/ntp.conf
server
restrict mask nomodify notrap noquery
Add it to the automatic boot and start the server
/sbin/chkconfig ntpd on
/sbin/service ntpd start 16 16

17. ig Repo Modify the ig.repo as following: # # INFNGRID repositories
[ig_sl4_i386]
name = INFNGRID 3.1 i386
baseurl =
enabled = 1
protect = 0
[ig_sl4_i386_externals]
name = INFNGRID 3.1 i386 (externals)
baseurl =
[ig_sl4_i386_jpackage]
name = INFNGRID 3.1 i386 (jpackage)
baseurl =
enabled = 0

18. the glite-generic.repo as following:#
# gLite generic repositories
[glite-generic_sl4_i386_release]
name = gLite generic 3.1 i386 (release)
baseurl =
enabled = 1
protect = 0
[glite-generic_sl4_i386_updates]
name = gLite generic 3.1 i386 (updates)
baseurl =
[glite-generic_sl4_i386_externals]
name = gLite generic 3.1 i386 (externals)
baseurl =

19. yum install gilda_utils
Then update your host:
yum clean all
Install CAs on ALL profiles:
yum install -y lcg-CA
Gilda utils:
yum install gilda_utils

20. YUM install
WMS install:
yum install ig_WMS

21. Transaction Check Error
Transaction Check Error: file /opt/glite/lib/libvomsapi_nog.a conflicts between attempted installs of glite-security-voms-api-cpp slc4 and glite-security-voms-api-noglobus slc4
file /opt/glite/lib/libvomsapi_nog.so conflicts between attempted installs of glite-security-voms-api-cpp slc4 and glite-security-voms-api-noglobus slc4
file /opt/glite/lib/libvomsapi_nog.so.0 conflicts between attempted installs of glite-security-voms-api-cpp slc4 and glite-security-voms-api-noglobus slc4
file /opt/glite/lib/libvomsapi_nog.so conflicts between attempted installs of glite-security-voms-api-cpp slc4 and glite-security-voms-api-noglobus slc4
If continuing having this error try yum remove glite-security-voms-cpp

22. LB install /etc/yum.repos.d/glite-lb.repo # # gLite LB repositories
[glite-LB_sl4_i386_release]
name = gLite LB 3.1 i386 (release)
baseurl =
enabled = 1
protect = 0
[glite-LB_sl4_i386_updates]
name = gLite LB 3.1 i386 (updates)
baseurl =
[glite-LB_sl4_i386_externals]
name = gLite LB 3.1 i386 (externals)
baseurl =

23. YUM install
LB install:
yum install ig_LB 23

24. Place the host certificate in the right location:
/root/gilda12-28certs.tar
tar cvf gilda12-28certs.tar
Move those in the right path
mv /root/gildaXX/hostcert.pem /etc/grid-security/hostcert.pem
mv /root/gildaXX/hostkey.pem /etc/grid-security/hostkey.pem
Give them the right permissions
chmod 400 /etc/grid-security/hostkey.pem
chmod 644 /etc/grid-security/hostcert.pem
~]# ll /etc/grid-security/
total 32
drwxr-xr-x 2 root root Jun 27 12:08 certificates
-rw-r--r-- 1 root root Jun 16 10:02 hostcert.pem
-r root root Jun 16 10:02 hostkey.pem
drwxr-xr-x 2 root root Jun 27 11:21 vomsdir

25. site-info.def Copy the ig-site-info.def script template
Open your own site-info.def and customize it:
cp /opt/glite/yaim/examples/siteinfo/site-info.def /opt/glite/yaim/examples/siteinfo/mysite-info.def
vi /opt/glite/yaim/examples/siteinfo/mysite-info.def

26. WMS-LB Configuration (1/3)
WMS Configuration (vi /opt/glite/yaim/examples/siteinfo/mysite-info.def)
INSTALL_ROOT=/opt
MYSQL_PASSWORD=secret
PX_HOST=myproxy.ct.infn.it
WMS_HOST=gildaXX.ihep.ac.cn
SITE_NAME=gildaxx.ihep.ac.cn
BDII_HOST=gilda02.ihep.ac.cn
VOS="gilda"  Add gilda here
#########
# gilda #
VO_GILDA_VOMS_CA_DN="/C=IT/O=INFN/OU=Host/L=Catania/CN=voms.ct.infn.it"
VO_GILDA_SW_DIR=$VO_SW_DIR/gilda
VO_GILDA_DEFAULT_SE=$DPM_HOST
VO_GILDA_STORAGE_DIR=$CLASSIC_STORAGE_DIR/gilda
VO_GILDA_VOMS_SERVERS="voms://voms.ct.infn.it:8443/voms/gilda?/gilda"
VO_GILDA_VOMSES="gilda voms.ct.infn.it /C=IT/O=INFN/OU=Host/L=Catania/CN=voms.ct.infn.it gilda"

27. WMS-LB Configuration (2/3)
vi /opt/glite/yaim/examples/siteinfo/services/glite-wms
LB_HOST="gildaXX.ihep.ac.cn:9000"
GLITE_WMS_LCGMON_FILE="/var/log/wms_lcgmon.log"
Copy the gilda profiles inside ig ones
cat /opt/glite/yaim/etc/gilda/gilda_ig-groups.conf >> /opt/glite/yaim/examples/ig-groups.conf
cat /opt/glite/yaim/etc/gilda/gilda_ig-users.conf >> /opt/glite/yaim/examples/ig-users.conf
cat /opt/glite/yaim/examples/ig-groups.conf | grep gilda
"/gilda/ROLE=SoftwareManager":::sgm:
"/gilda/grelc/das/*":gilda:::
"/gilda"::::
Location, Meeting title, dd.mm.yyyy

28. WMS-LB Configuration (3/3)
CONFIGURE
/opt/glite/yaim/bin/yaim -c -s /opt/glite/yaim/examples/siteinfo/mysite-info.def -n glite-WMS -n glite-LB
Location, Meeting title, dd.mm.yyyy 28

29. Log file Location, Meeting title, dd.mm.yyyy 29
examples]# service gLite status
*** globus-gridftp:
globus-gridftp-server (pid 13095) is running...
*** glite-wms-wmproxy:
WMProxy httpd listening on port 7443
httpd (pid ) is running ....
===
WMProxy Server running instances:
UID PID PPID C STIME TTY TIME CMD
*** glite-wms-wm:
/opt/glite/bin/glite-wms-workload_manager (pid 12466) is running...
*** glite-wms-lm:
Logmonitor running...
*** glite-wms-jc:
JobController running in pid: 12525
CondorG master running in pid: 12581
CondorG schedd running in pid: 12662
*** glite-wms-ice:
/opt/glite/bin/glite-wms-ice-safe (pid 12636) is running...
*** glite-proxy-renewald:
glite-proxy-renewd running
*** glite-lb-proxy:
glite-lb-proxy running as 13250
*** glite-lb-locallogger:
glite-lb-logd running
glite-lb-interlogd not running
*** glite-lb-bkserverd:
glite-lb-notif-interlogd running
glite-lb-bkserverd running as 13764
Location, Meeting title, dd.mm.yyyy 29

30. Log file
/var/log/gLite
Location, Meeting title, dd.mm.yyyy 30

31. Testing WMS-LB From a UI enter:
~]$ voms-proxy-init –voms gilda
~]$ export GLITE_WMS_WMPROXY_ENDPOINT=
~]$ vi more test.jdl
Executable = "/bin/hostname";
StdOutput = "std.out";
StdError = "std.err";
OutputSandbox = {"std.out","std.err"};

32. Testing WMS-LB
~]$ glite-wms-job-list-match -a test.jdl
Connecting to the service
=====================================================================
COMPUTING ELEMENT IDs LIST
The following CE(s) matching your job requirements have been found:
*CEId*
- ce.hpc.iit.bme.hu:2119/jobmanager-lcgpbs-gilda
- ce1-egee.srce.hr:2119/jobmanager-sge-prod
- dgt01.ui.savba.sk:2119/jobmanager-lcgpbs-gilda
- gilda-01.pd.infn.it:2119/jobmanager-lcgpbs-gilda
- gilda04.ihep.ac.cn:8443/cream-pbs-gilda
- grisuce.scope.unina.it:2119/jobmanager-lcgpbs-grisu_long
- grisuce.scope.unina.it:2119/jobmanager-lcgpbs-grisu_short
- vega-ce.ct.infn.it:2119/jobmanager-lcgsge-gilda
- sirius-ce.ct.infn.it:2119/jobmanager-lcgpbs-gilda
- grid010.ct.infn.it:2119/jobmanager-lcgpbs-gilda
- iceage-ce-01.ct.infn.it:2119/jobmanager-lcgpbs-gilda 32

33. References
INFNGrid installation

34. Backup 34 34

35. Configuration Error
/opt/glite/etc/init.d/glite-wms-wmproxy: line 37: Segmentation fault $httpdpath -k -f $config
ABORT: Service glite-wms-wmproxy failed to start!
ERROR: Error during the execution of function: config_glite_wms
ERROR: Error during the configuration.Exiting [FAILED]
- yum.repos.d]# rpm -qa |grep gridsite
gridsite-apache
gridsite-shared
rpm -e --nodeps gridsite-apache gridsite-shared
wget
wget
rpm -ivh gridsite-shared i386.rpm
rpm -ivh gridsite-apache i386.rpm
CONFIGURE AGAIN
/opt/glite/yaim/bin/ig_yaim -c -s /opt/glite/yaim/examples/siteinfo/mysite-info.def -n ig_WMS -n ig_LB 35

36. YUM install yum install ig_WMS
Error: Missing Dependency: google-perftools >= is needed by package ig_WMS
Error: Missing Dependency: google-perftools-devel >= is needed by package ig_WMS
rpm -ivh
rpm -ivh
yum install ig_WMS 36