From EGEE-see WIki

Contents 1 About 2 Installation 3 Usage 4 Maintenance

About

Standalone SAM is a modified version of SAM client than can be used to test sites without the need for a dedicated SAM server. It is intended to be used by:

• site admins for manually checking their sites,
• country representatives for certifying new sites.

Installation

Standalone SAM can be downloaded from http://www.irb.hr/users/vvidic/seegrid/ssam.tar.gz. The archive contents are:

 -rw-r--r--  1 vvidic vvidic   154 2006-12-06 14:01 Makefile
 -rw-r--r--  1 vvidic vvidic   226 2006-12-06 13:59 grid1.irb.hr.jdl
 -rwxr-xr-x  1 vvidic vvidic 10017 2006-12-06 10:39 makeself
 -rw-r--r--  1 vvidic vvidic  8740 2006-12-06 10:39 makeself-header
 -rw-r--r--  1 vvidic vvidic  3164 2006-12-06 15:30 README
 drwxr-xr-x  3 vvidic vvidic  1024 2006-12-06 15:45 same

In detail:

• README - this text,
• Makefile - automates common actions,
• *.jdl - example JDL files for submitting SAM jobs to sites,
• makeself* - shell scripts used to build the self-extracting archive,
• same/ - slightly modified version of the SAM client.

To build the self-extracting archive run:

 $ make

This will create same.sfx:

 -rwxr-xr-x 1 vvidic vvidic 234260 2006-12-06 15:48 same.sfx

same.sfx is a self-extracting shell archive (tar.gz file wrapped in a shell script that extracts it and runs the predefined command). In this case the predefined command is same/same.sh, a small shell script that in turn calls SAM testjob sensor. This will run all the standard tests but instead of publishing them to the SAM server, it will create an HTML page with a report. This report is the output of standalone SAM client.

Usage

After you have created the same.sfx you can send it to the site as an executable and it will generate a report HTML page on standard output. Standard output is used so you can test the site directly using just one command.

You can either submit directly:

 globus-job-run ce.host.name/jobmanager-lcgpbs -q dteam -s ./same.sfx > ce.host.name_report.html

or using RB/WMS:

 edg-job-submit --vo dteam dteam.jdl
 glite-job-submit --vo dteam dteam.jdl

where JDL is like this:

 Executable = "same.sfx";
 StdOutput = "results.html";
 StdError = "results.html";
 InputSandbox = {"same.sfx"};
 OutputSandbox = {"results.html"};
 Requirements = RegExp("grid1.irb.hr", other.GlueCEUniqueID);

Note: it is not possible to use globus-job-submit in combination with executable stage-in because this functionality is broken in lcgpbs jobmanager (savannah bug #4400).

If any arguments are specified they will be converted to environment variables:

 globus-job-run ce.host.name/jobmanager-lcgpbs -q dteam -s ./same.sfx LCG_GFAL_INFOSYS=bdii.phy.bg.ac.yu:2170 > ce.host.name_report.html

This command will force SAM client to use a different LCG_GFAL_INFOSYS.

In addition to the usual grid environment variables, standalone SAM also uses a few of it's own. It tries to guess the correct values from the WN environment, but you can override this as shown before:

• CE_NAME - hostname of the CE
• CENTRAL_SE - off-site SE to be used in RM tests
• SENSOR - sensor to run (should be testjob or glite-testjob based on the CE type)
• VO_NAME - name of the VO (lowercase)

Note: if you are using direct submission to pbs jobmanager, it might be necessary to specify the job type:

 globus-job-run ce.host.name/jobmanager-pbs -q dteam -x '(jobType=single)' -s ./same.sfx > ce.host.name_report.html

Maintenance

SAM client needs to be updated periodically to get new tests (most notably CA tests):

 $ make update

This will update the client from CVS (watch out for conflicts as they can brake the client). Don't forget to rebuild the same.sfx afterwards, for example:

 $ make clean update same.sfx