Certifying WMS HOWTOS

Checks before starting

• hardware requirements for WMS & L&B - see WMS best practices
• disable yum-autoupdate
• disable puppet (if "allowed")
• check eventual important notes for WMS and L&B, and UI

EMI UI

The EMI UI for the certification can be installed following the instructions reported here.
A further configuration is required in order to match the resources tagged with other.GlueCEStateStatus == "Testing":

In /etc/glite-wms/dteam/glite_wmsui.conf and /etc/glite-wms/dteam/glite_wms.conf comment out the following line:

//    requirements  =  other.GlueCEStateStatus == "Production";

WMS

BDII

The wms should be configured in order to point to a bdii that contains both production and testing resources, like cert-42.cnaf.infn.it

Normal submission

In order to test a simple submission, submit a jdl with the following command from a UI (after having created a dteam or testers proxy):

glite-wms-job-submit -a -c wms_XXX.conf ls.jdl

where wms_XXX.conf points to the wms being tested:

WmsClient = [
ErrorStorage="/var/tmp";
OutputStorage=  "/tmp";
ListenerStorage="/tmp";
virtualorganisation="dteam";
RetryCount = 0;
WMProxyEndPoints = {"https://XXX.cnaf.infn.it:7443/glite_wms_wmproxy_server"};
rank = -other.GlueCEStateEstimatedResponseTime;
];

and ls.jdl:

[
Executable = "ls.sh";
Arguments = "-al";
requirements = RegExp("/cream-", other.GlueCEUniqueID) && other.GlueCEStateStatus == "Testing";
retrycount = 4;
shallowretrycount = 3;
StdError = "stderr.log";
StdOutput = "stdout.log";
InputSandbox = "ls.sh";
OutputSandbox = {"stderr.log", "stdout.log"};
]

be sure to have ls.sh in the current directory containing:

#!/bin/sh
/bin/ls $1

The command returns the jobid of the job.
Check for the job status via the following command:

glite-wms-job-status _jobid_

where _jobid_ is the jobid returned by the submit command.

When the job attains the Done Success status try to retrieve the job output via the following command:

glite-wms-job-output _jobid_

Advisory #4039

Submitting this JDL (wms_4039.jdl) will cause arbitrary code to be run as 'glite' user on the WMS, when time to renew the user proxy. It must select only CREAM CEs, so as to trigger the ICE's (WMS component that submits to CREAM) proxy renewal mechanism.

Using a short proxy results in an almost immediate execution.

Standard conformance tests (always)

# yum install glue-validator
# glue-validator -t glue1 -h cert-XX.cnaf.infn.it -p 2170 -b o=grid
# glue-validator -t glue2 -h cert-XX.cnaf.infn.it -p 2170 -b o=glue