TWiki> EGEE Web>SA3>ServiceReferenceCards>GliteWMS (revision 7)EditAttachPDF

gLite Workload Management Service

Functional description

The Workload Management System (WMS) comprises a set of grid middleware components responsible for the distribution and management of tasks across grid resources, in such a way that applications are conveniently, efficiently and effectively executed.

The core component of the Workload Management System is the Workload Manager (WM), whose purpose is to accept and satisfy requests for job management coming from its clients. For a computation job there are two main types of request: submission and cancellation.

In particular the meaning of the submission request is to pass the responsibility of the job to the WM. The WM will then pass the job to an appropriate Computing Element for execution, taking into account the requirements and the preferences expressed in the job description. The decision of which resource should be used is the outcome of a matchmaking process between submission requests and available resources.

Released version

gLite WMS has been released for the gLite 3.1 release series. You can find the latest released version together with the installation instructions and repositories at the gLite WMS release pages.

Daemons running

The following daemons need to be running:

For gLite:

  • /etc/init.d/gLite

starting the following services:

  • /opt/glite/etc/init.d/glite-wms-jc
  • /opt/glite/etc/init.d/glite-wms-lm
  • /opt/glite/etc/init.d/glite-wms-wm
  • /opt/glite/etc/init.d/glite-proxy-renewald
  • /opt/glite/etc/init.d/glite-wms-wmproxy
  • /opt/glite/etc/init.d/glite-lb-proxy

For the MySQL server:

  • /etc/init.d/mysqld

For globus:

  • /etc/init.d/globus-gridftp

For BDII:

  • /etc/init.d/bdii

Init scripts and options (start|stop|restart|...)

  • /etc/init.d/gLite
  • /etc/init.d/globus-gridftp
  • /etc/init.d/mysqld

Configuration files location with example or template

The configuration files for the WMS service are located in:

  • /opt/glite/etc/

and are

  • glite_wms.conf
  • glite_wms_wmproxy_httpd.conf
  • wmproxy_gacl

Corresponding templates are:

  • glite_wms.conf.template
  • glite_wms_wmproxy_httpd.conf.template
  • wmproxy_gacl.template

in the same directory.

Logfile locations (and management) and other useful audit information

The gLite log files can be found in general under

  • /var/log/glite

and for the WMS, there are the following log files:

  • glite-lb-purger.log
  • glite-wms-purgeStorage.log
  • glite-wms-wmproxy-purge-proxycache.log
  • httpd-wmproxy-access.log
  • httpd-wmproxy-errors.log
  • jobcontoller_events.log
  • lcmaps.log
  • logmonitor_events.log
  • wmproxy.log
  • workload_manager_events.log

The condor log files are located under

  • /var/local/condor/log/

and are:

  • CollectorLog
  • GridmanagerLog.glite
  • MasterLog
  • MatchLog
  • NegotiatorLog
  • SchedLog

Open ports

Possible unit test of the service

Submission of job.

Where is service state held (and can it be rebuilt)

The submitted jobs are first stored in:

  • /var/glite/workload_manager/input.fl

once submitted to job controller they are stored in:

  • /var/glite/jobcontrol/queue.fl

and for condor, the information can be found in

  • /var/local/condor/spool

Cron jobs

The cron jobs can be found in:

  • /etc/cron.d/

and are:

  • bdii-proxy
  • fetch-crl
  • glite-lb-purge.cron
  • glite-wms-purger.cron
  • glite-wms-wmproxy-purge-proxycache.cron
  • glite-wms-check-daemons.cron
  • lcg-expiregridmapdir
  • lcg-mon-job-status-proxy
  • wmproxy_logrotate

Security information

  • The authZ in WMS is managed by GridFTP and GridSite with two different mechanisms:
    • GridFTP: performed by LCAS
    • GridSite: specified by means of GACL, an XML-based formalism

How the site admin can block a specific user

  • The file "/opt/glite/etc/glite_wms_wmproxy.gacl" contains the identities (VO, user, etc) with distinct permissions (exec, read, write, ...) to use the WMS.
  • If it is necessary to ban a user/group/VO the site admin must add his/her DN/FQAN and a deny tag, e.g.:
         <entry>
           <person>
             <dn>/C=IT/O=INFN/OU=Personal Certificate/L=DATAMAT DSAGRD/CN=John Doe</dn>
           </person>
           <deny>
             <exec/>
           </deny>
         </entry>

Utility scripts

The wms scripts/binaries can be found in

  • /opt/glite/bin

and are:

  • glite-lb-proxy
  • glite-proxy-renew
  • glite-proxy-renewd
  • glite-wms-get-configuration
  • glite-wms-grid-console-shadow
  • glite-wms-job_controller
  • glite-wms-job-agent
  • glite-wms-log_monitor
  • glite-wms-pipe-input
  • glite-wms-pipe-output
  • glite-wms-stats.py
  • glite_wms_wmproxy_dirmanager
  • glite-wms-wmproxy-gacladmin
  • glite-wms-wmproxy-gridmapfile2gacl
  • glite-wms-wmproxy-purge-proxycache
  • glite_wms_wmproxy_server
  • glite-wms-workload_manager

Location of reference documentation for users

Location of reference documentation for administrators

See user documentation.

-- JoachimFlammer - 15 May 2008

Edit | Attach | Watch | Print version | History: r15 | r9 < r8 < r7 < r6 | Backlinks | Raw View | Raw edit | More topic actions...
Topic revision: r7 - 2009-01-09 - LorenzoSbolgi
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    EGEE All webs login

This site is powered by the TWiki collaboration platform Powered by Perl This site is powered by the TWiki collaboration platformCopyright & by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Ask a support question or Send feedback