, view all tags

CREAM-CE metrics and WN probes

CREAM-CE metrics

These metrics are used to test worker nodes submitting ad-hoc jdls which run some grid's checks.

  1. emi.cream.CREAMCE-JobState. Submits grid job to CREAMCE using a given WMS. Accepts passive check updates from emi.wms.CREAMCE-JobMonit.
  2. emi.creamCREAMCE-JobMonit. Monitors grid jobs submitted to CREAM-CE.
  3. emi.cream.CREAMCE-JobCancel. Cancel active grid jobs.
  4. emi.cream.CREAMCE-JobSubmit. Passive check. Holds terminal status of job submissiom to CREAM-CE.


Submit a grid job to a given CREAM-CE through a WMS. These are the generic parameters:

--wms <wms> WMS to be used for job submission. If not given, default WMProxy end-points defined on the UI will be used.
--jdl-templ <file> JDL template file (full path). Default: <emi.cream.ProbesLocation>/CREAM-jdl.template
--jdl-retrycount <val> JDL RetryCount (Default: 0).
--jdl-shallowretrycount <val> JDL ShallowRetryCount (Default: 1).
--timeout-job-discard <sec> Discard job after the timeout. (Default: 21600)
--prev-status <0-3> Previous Nagios status of the metric.

This is the default jdl template used for submission:

Executable = "<jdlExecutable>";
StdError = "gridjob.out";
StdOutput = "gridjob.out";
Arguments = "<jdlArguments>";
InputSandbox =  {"<jdlInputSandboxExecutable>", "<jdlInputSandboxTarball>"};
OutputSandbox = {"gridjob.out","wnlogs.tgz"};
RetryCount = <jdlRetryCount>;
ShallowRetryCount = <jdlShallowRetryCount>;
Requirements = other.GlueCEInfoHostName == "<jdlReqCEInfoHostName>";

The message transfer agent (MTA)

To manage checks on the worker node it is used the executable nagrun.sh (see below). The arguments are dinamically composed by the metrics translating the ones given to the probes. In particular results from the worker nodes are sent via a message transfer agent (MTA) to Message Brokers. The code for MTA mta-simple is located under <WN_codebase>/bin/ and implementation in <WN_codebas>e/lib/python2.3/site-packages/mig.

The MTA:

  • tries to establish connection to a broker (either a given one or found via discovery in IS and successive application of ranking)
  • takes messages from directory based queue and sends them to the broker.
Messages with metric results are stored in outgoing messages queue by a Nagios handler handle_service_check invoked by Nagios after execution of each check. The parameters to manage resource broker are:

--mb-destination <dest> Mandatory parameter (if --no-mb is not specified). The destination queue/topic on Message Broker to publish to.
--mb-uri <URI> Message Broker URI. If not given, MB discovery will be performed on WN to find working MB.
Format for <URI>: [failover://\(]<uri>,[...][\)] <uri> - stomp://FQDN:port/ or http://FQDN/message
(Default: service discovery on WN.)
--mb-network <net> Brokers network for broker discovery on WN. (Default: PROD)
--mb-no-discovery Do not do broker discovery on WN. If a given <URI> is not accessible, WN part of the framework will exit with UKNOWN.
(Default: if <URI> is not given or not accessible from WN perform broker discovery in <net>.)
--mb-choice <best or random> How to choose MB on WN. 'best' - min response time. (Defalult: best)
--no-mb Do not send results messages to Message Broker

Note that the last option --no-mb disabilitates messages transfer; in that case results e-mail messages can be found in the job's output file wnlogs.tgz.

Output files

Default JDL's output sandbox defines two files that will be taken from WN

OutputSandbox = {"gridjob.out","wnlogs.tgz"};

  • gridjob.out contains logging output of WN job as seen by WMS job wrapper. I.e., stdout and stderr from the testing framework launching script on WN (nagrun.sh).
  • wnlogs.tgz contains the following directories from WN: //nagios/{var,tmp}. The framework's messaging and Nagios logging and debuging is stored there.
    • when writing probes for WN, one can direct output into some files in that directories - they will be brought to UI in wnlogs.tgz.
On Nagios Server/UI OutputSandbox is stored per CE under /var/lib/gridprobes//emi.cream/CREAMCE//jobOutput* directories. jobOutput.LAST contains last historical output from WN.

Third-party WN checks

To describe which checks must be execute on the worker node the following parameters should be used:

--add-wntar-nag <d1,d2,..> Comma-separated list of top level directories with Nagios compliant directories structure to be added to tarball to be sent to WN.
--add-wntar-nag-nosam Instructs the metric not to include standard SAM WN probes and their Nagios config to WN tarball.
(Default: WN probes are included)
--add-wntar-nag-nosamcfg Instructs the metric not to include Nagios configuration for SAM WN probes to WN tarball.
The probes themselves and respective Python packages, however, will be included.
--wnjob-location <dir> Full path to directory contaning WN scheduler.
(Default: <emi.cream.ProbesLocation>/wnjob)

NOTE: with --add-wntar-nag <d1,d2,..> parameter the respective "Nagios compliant directories structure" should look like this:

        |-- etc
        |   `-- wn.d
        |       `-- org.my
        |           |-- commands.cfg
        |           `-- services.cfg
        `-- probes
            `-- org.my
                |-- check_A
                |-- check_B
                `-- checks_lib.sh

  • probes/org.my/* should contain your probes/checks
  • etc/wn.d/org.my/ should contain file(s) with .cfg extension with Nagios command and service objects definitions (optionally, service dependencies definitions). In your etc/wn.d/org.my/*.cfg files please use the following paths defining Nagios macros and the framework template names:
    • $USER3$ macro defining path to /probes/ directory on WN. Usage:
                          define command{
                                 command_name   check_A1
                                 command_line   $USER3$/org.my/check_A
    • <wnjobWorkDir> will be substituted with the job's working directory on WN. Handy if your check requires and creates a working directory. Possible usage (assumes -w instructs check_A to create <wnjobWorkDir>/.mygridprobes directory):
                    define command{
                           command_name   check_A2
                           command_line   $USER3$/org.my/check_A -w <wnjobWorkDir>/.mygridprobes

For this particular part of Nagios objects configuration and macros please see the Nagios documentation for resources configuration.

With these last parameters you can manage some timeouts in WNs:

--timeout-wnjob-global <sec> Global timeout for a job on WN. (Default: 600)
--wn-verb <0-3> Metrics verbosity level on WN. [-v <VERBOSITY>] (Default: 0)
--wn-verb-fw <0-3> Framework verbosity level on WN (Default: 1)

  • --wn-verb on WN the given value is substituted for <VERBOSITY> in Nagios metric definition *.cfg files.
  • --wn-verb-fw is used by nagrun.sh for setting its debugging output as well as setting logging and debugging output of messages publishing client (Message Transfer Agent - MTA) and Nagios.
    • >= 2 - 'debug'
    • == 1 - 'info'
    • == 0 - 'warn'


On WN (as specified in JDL with Executable = "<jdlExecutable>") nagrun.sh script (on Nagios UI located in <WN_codebase>) is used to

  • set required environment variables
  • launch messages transfer agent (MTA) - metric results publisher to message brokers
  • make substitutions in templated (mainly Nagios) configuration files
  • launch and monitor Nagios
  • after all metrics are executed (or on timeout) terminate Nagios and MTA
  • do on-exit cleanup
Parameters to nagrun.sh specified by Arguments = "" define what and how should be launched.
usage: nagrun.sh -v <vo> -d <dest> [-b <broker_uri>]
 [-n <broker_network>] [-t <timeout>] [-w <fw_verb>]
 [-z <metric_verb>] [-f <fqan>] [-i <host:port,..>] -B -R -N -h -m
 -v and -d (if not -m) are mandatory paramters. Defaults:
 <broker_network> - PROD
 <timeout> - 600 sec
 <metrics_verb> - 0
 <fw_verb> - 1 (2 - messages, 3 - Nagios config/stats/debug)
 -f <fqan> - VOMS FQAN
 -B - don't do broker discovery
 -R - take MB randomly; by default sort by min response time
 -N - don't run WN tests
 -m - don't use mta service to transfer messages

In most cases the parameters is the translation of corresponding ones given to emi.cream.CREAMCE-JobState metric.

emi.cream.CREAMCE-JobState nagrun.sh
--mb-network <net> Brokers network for broker discovery on WN. -n <broker_network>
--mb-uri <URI> Message Broker URI. -b <broker_uri>
--mb-destination <dest> queue/topic on MB to publish to. -d <dest>
--mb-no-discovery Do not do broker discovery on WN. -B
--mb-choice <best or random> How to choose MB on WN. -R
--vo <name> Virtual Organization. -v <vo>
--vo-fqan <name> VOMS primary attribute as FQAN. -f <fqan>
--wn-verb <0-3> Metrics verbosity level on WN. -z <metric_verb>
--wn-verb-fw <0-3> Framework verbosity level on WN. -w <fw_verb>
--timeout-wnjob-global <sec> Global timeout for a job on WN. -t <timeout>
--no-mb -m


Monitors status of all submitted jobs (as defined in activejob.map files) and updates states of emi.cream.CREAMCE-JobState and emi.wms.CREAMCE-JobMonit metrics. Acts as a babysitter for all grid jobs submitted by emi.cream.CREAMCE-JobState. emi.cream.CREAMCE-JobState and emi.cream.CREAMCE-JobMonit are updated (as passive checks) either via Nagios command file or NSCA. It accepts these parameters:

--timeout-job-global <sec>    Global timeout for jobs. Job will be cancelled and dropped 
                              if it is not in terminal state by that time. (Default: 3300)
--timeout-job-waiting <sec>   Time allowed for a job to stay in Waiting with 'no compatible 
                              resources'. (Default: 2700)
--timeout-job-discard <sec>   Discard job after the timeout. (Default: 21600)
--timeout-job-schedrun <sec>  Scheduled/Running states timeout. (Default: 19800)
--hosts <h1,h2,..>            Comma-separated list of CE hostnames to run the monitor on.

WN Probes

Using the default wntag directory emi.wn these probes are performed on the worker node using the wrapper samtest-run:

  • WN-csh
  • WN-softver
  • WN-brokerinfo


Checking if CSH works running the command: /bin/csh -c "env|sort" > env-csh.txt and then cheking if the variable PATH is defined. Accept only the parameter: debug.

Example of a message sent as output:

serviceURI: cream-30.pd.infn.it:8443/cream-pbs-creamtest2
hostName: localhost.localdomain
serviceFlavour: CE
siteName: FAKE-SITE
metricStatus: OK
metricName: emi.wn.WN-Csh
summaryData: OK
gatheredAt: cream-wn-030.pn.pd.infn.it
timestamp: 2011-09-22T15:25:36Z
nagiosName: emi.wn.WN-Csh-dteam
role: site
voName: dteam
serviceType: emi.wn.WN
detailsData: Checking if CSH works\nTest: OK.\n


Detects the version of software which is really installed on the WN. To detect the version lcg-version, glite-version commands and the cat of the /etc/emi-version file are tried and if the commands are not available the script exits with an error.

Example of a message sent as output:

serviceURI: cream-30.pd.infn.it:8443/cream-pbs-creamtest2
hostName: localhost.localdomain
serviceFlavour: CE
siteName: FAKE-SITE
metricStatus: OK
metricName: emi.wn.WN-SoftVer
summaryData: OK: EMI 1.2.0-1
gatheredAt: cream-wn-030.pn.pd.infn.it
timestamp: 2011-09-22T15:25:37Z
nagiosName: emi.wn.WN-SoftVer-dteam
role: site
voName: dteam
serviceType: emi.wn.WN
detailsData: Installed software version\n+ type=unknow\n+ mwver=error\n+ type -f glite-version\n/home/dteam009/home_cre30_262167654/CREAM262167654/nagios/probes/emi.wn/sam/WN-softver: line 31: type: glite-version: not found\n+ '[' -f /etc/emi-version ']'\n+ type=EMI\n++ cat /etc/emi-version\n+ mwver=1.2.0-1\n+ set +x\nVersion pattern: ^2\\.[456789]OR^3\\.OR^1\\.\nDeducted middleware version: EMI 1.2.0-1\n


Check if BrokerInfo works. The procedure is the following:

  • Firstly check if BrokerInfo file is defined in $GLITE_WMS_RB_BROKERINFO, $GLITE_WL_RB_BROKERINFO or $EDG_WL_RB_BROKERINFO variables
  • Then try to get CE host name using edg-brokerinfo getCE or glite-brokerinfo getCE command respectively. If previous command result value is different from 0 test is failed.
Example of a message sent as output:
serviceURI: cream-30.pd.infn.it:8443/cream-pbs-creamtest2
hostName: localhost.localdomain
serviceFlavour: CE
siteName: FAKE-SITE
metricStatus: OK
metricName: emi.wn.WN-Bi
summaryData: OK: getCE: cream-30.pd.infn.it:8443/cream-pbs-creamtest2
gatheredAt: cream-wn-030.pn.pd.infn.it
timestamp: 2011-09-22T15:25:35Z
nagiosName: emi.wn.WN-Bi-dteam
role: site
voName: dteam
serviceType: emi.wn.WN
detailsData: Checking if BrokerInfo works\nBrokerInfo file: /home/dteam009/home_cre30_262167654/CREAM262167654/.BrokerInfo\n+ ls -l /home/dteam009/home_cre30_262167654/CREAM262167654/.BrokerInfo\n-rw-r--r-- 1 dteam009 dteam 367 Sep 22 17:25 /home/dteam009/home_cre30_262167654/CREAM262167654/.BrokerInfo\n+ set +x\nCheck if we can get the name of CE using glite-brokerinfo command\n+ glite-brokerinfo -v getCE\nBrokerInfo::getBIFileName(): /home/dteam009/home_cre30_262167654/CREAM262167654/.BrokerInfo\nBrokerInfo::getCE(): \n -> cream-30.pd.infn.it:8443/cream-pbs-creamtest2\n -> BI_SUCCESS\n+ result=0\n+ set +x\n
Edit | Attach | PDF | History: r7 | r5 < r4 < r3 < r2 | Backlinks | Raw View | More topic actions...
Topic revision: r3 - 2011-11-08 - AlessioGianelle

  • Edit
  • Attach
This site is powered by the TWiki collaboration platformCopyright © 2008-2020 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback