cream-test-monitored-submit

NAME
cream-test-monitored-submit - submit a sequence of jobs and poll for the status

SYNOPSIS
cream-test-monitored-submit [OPTION] -R | --resourceURI RESOURCEURI

DESCRIPTION
Submit a given number of jobs and keep track of the status of each job polling the service (getStatus operation). The test keeps a given number of job running on the CE.

OPTIONS

  • -D --delegationType STRING specify the delegation management type: single, one delegated proxy for all submissions,or multiple, one delegated proxy per job (DEFAULT is single)

  • -h --help Print the man pages for this command

  • --interactive Enable the test control via terminal (EXPERIMENTAL)

  • -j --jdl STRING define the path for the jdl file, if omitted a predefined jdl will be used with simple sleep as executable (5 times the rate)

  • -l --logConf STRING Set the location of the configuration file for log4py, (DEFAULT as provided by log4py)

  • -C --maxConcurrentSubmit NUMBER define the number of concurrent submit, (DEFAULT is 1)

  • -m --maxRunningJobs NUMBER set the max number of job which can be enqueued in the service (DEFAULT 100)

  • --nopurge Disable the purge operation for all jobs submitted (CRITICAL)

  • -n --numberOfJob NUMBER set the number of jobs to submit (DEFAULT 1)

  • -Q --queryType STRING speficy the polling mechanism used for retrieving the status of the jobs.
The supported types are event (new event query), list (internal job list used) or timestamp (query by timestamp). The default is event.

  • -r --rate NUMBER set the sleep time in seconds between two polling operations (DEFAULT 30s, Min 5s)

  • -R --resourceURI STRING define the URI of the resource under testing, the format is [:]/cream--. This option is mandatory and no default value is defined

  • --sotimeout NUMBER Socket timeout in seconds (DEFAULT 30s)

  • --valid STRING set the voms-proxy duration in the format HH:MM (DEFAULT 00:10)

  • --vo STRING set the VO name to be used for the test; this parameter is mandatory whenever X509_USER_CERT and X509_USER_KEY are defined, no default is available

ENVIRONMENT

  • GLITE_LOCATION location of gLite packages (DEFAULT=/opt/glite)

  • X509_USER_PROXY location of the user proxy

  • X509_USER_CERT location of the user certificate, this variable has priority upon the X509_USER_PROXY variable

  • X509_USER_KEY location of the user private key. The key must be protected by a passphrase.

  • MONITORED_SUBMIT_CONFIG_FILE location of the configuration file for this test. The configuration file contains a list of properties (the format is key=value); the set of keys correspond to the set of the long options of this test
Edit | Attach | PDF | History: r4 < r3 < r2 < r1 | Backlinks | Raw View | More topic actions
Topic revision: r4 - 2010-03-02 - PaoloAndreetto
 
This site is powered by the TWiki collaboration platformCopyright © 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback