check_workflow

Usage
./check_workflow.pl [OPTIONS] [-f configuration_file]
Options
  • -h or --help: prints short usage tips

  • -V or --version: prints plugin versions

  • -v X or --verbose X: sets verbosity level to X (see UMI docs)

  • -t Y or --timeout Y: sets plugin execution timeout to Y seconds

Description

This is the plugin that does integration test of complete UNICORE installation. Requires UCC in version 1.3.0 or higher, because core of plugin is implemented in Groovy as UCC script (it gives eightfold time decrease in comparison to previous version). Plugin gets list of TSFs that sholud be tested in the workflow and:

  • check if all of them are available and respond (tries to create TSS), if some not, then avoids them and adds proper information to the output.

  • creates workflow description that will execute in two-step subworkflows over all working TSFs, when each subworkflow executes on two different sites (to test files staging between sites)

  • uploads sample file to given global storage

  • runs workflow on given WorkflowFactory and waits to the end of execution

  • uses LocationMapper to check existence of result files, downloads them and compares to the schema

  • uses Tracer to check all executes

  • prints stats of TSFs used in workflow and cleans environment.

If the whole test is successful you can assume that every module of standard UNICORE installation (except CIS or CIP) works fine.

Configuration file for plugin
  • UCC_PATH: absolute path to UNICORE Commandline Client binary (in version 1.3.1 or higher)

  • UCC_CONFIG: absolute path to valid configuration file for UCC (remember to set absolute paths to keystore and trustore in this file!)

  • REGISTRY_URL: address of registry that contains Workflow Service you want to check

  • WORKFLOWSERVICE_NAME: URL of Workflow Service (or any part of this URL while it is not ambiguous)

  • GLOBAL_STORAGE_URL: URL of Global Storage to use

  • SITES: list of TSFs to test

  • LOGS_DIR: Path to logs directory

Possible outputs with description
  • OK: Wokflow succeeded! Time elapsed: …: Workflow succeded on all reqiured sites. It means that whole UNICORE installation works fine.

  • WARNING: Workflow failed on … sites: Workflow failed due to failures on some sites (by default <50% sites). Whole workflow installation works fine, test should pass after fixing sites-related problems.

  • WARNING: All jobs succeded, but some output files are missing: Sholudn’t happen. That would mean that some sites marked jobs as succeded, but they failed in real.

  • WARNING: Workflow was unable to be executed on some sites: Workflow succeded but some sites was removed from workflow description because of initial TFSs check (see probe description)

  • CRITICAL: Workflow failed: jobs failed on too many sites, CRITICAL: Workflow was unable to be executed on too many sites:: Workflow failed (or was unable to run due to TSFs unavailability) on >= 50% of sites. This state is critical, because grid workflow system is unusable.

  • CRITICAL: Unable to connect to the Registry: UCC cannot connect to given Registry URL.

  • CRITICAL: Unable to upload test file: Global Storage URL you given is not properly defined (script cannot get supported file protocols) or there is server-side failure in creating file.

  • CRITICAL: WorkflowFactory exists in the Registry, but doesn’t respond: WorkflowFactory at url given in configuration is not found in the Registry or is registered but cannot be contacted.

  • CRITICAL: Workflow execution failed: Execution of workflow failed for unknown reason. This should not happen because workflow should ignore subworkflows failures.

  • CRITICAL: Location mapping service is not available: Workflow execution succeeded but output file cannot be mapped using LM service.

  • CRITICAL: Tracer service is not available: Unable to find any Tracer service in the Registry, so workflow statistics cannot be retreived.