1 / 6

Hands-On Session: Workload Management System (WMS) Installation and Configuration

Hands-On Session: Workload Management System (WMS) Installation and Configuration. Regional SEE-GRID-SCI Training for Site Administrators Institute of Physics Belgrade March 5-6, 2009. Dusan Vudragovic Institute of Physics Belgrade Serbia dusan@scl.rs.

sabine
Download Presentation

Hands-On Session: Workload Management System (WMS) Installation and Configuration

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Hands-On Session:Workload Management System (WMS) Installation and Configuration Regional SEE-GRID-SCI Training for Site Administrators Institute of Physics Belgrade March 5-6, 2009 Dusan Vudragovic Institute of Physics Belgrade Serbia dusan@scl.rs The SEE-GRID-SCI initiative is co-funded by the European Commission under the FP7 Research Infrastructures contract no. 211338

  2. Overview of WMS [1/5]

  3. Overview of WMS [2/5] • Workload Manager Proxy WMProxy • Provides access to WMS functionality through a Web Services based interface • Each job submitted to a WMProxy Service is given the delegated credentials of the user who submitted it. • These credentials can then be used to perform operations requiring interactions with other services • WMProxy advantages: • web service, SOAP • job collections, DAG jobs, shared and compressed • sandboxes • WMProxy caveats: • needs delegated credentials • Delegate once,submit many

  4. Overview of WMS [3/5] • Workload Manager (WM) • Is responsible for • Calls Matchmaker to find the resource which best matches the job requirements. • Interacting with Information System and File catalog. • Calculates the ranking of all the matchmaked resource • Information Supermarket (ISM) • is responsible for • basically consists of a repository of resource information that is available in read only mode to the matchmaking engine • Job Adapter • is responsible for • making the final touches to the JDL expression for a job, before it is passed to CondorC for the actual submission • creating the job wrapper script that creates the appropriate execution environment in the CE worker node • transfer of the input and of the output sandboxes

  5. Overview of WMS [4/5] • Job Controller (JC) • Is responsible for • Converts the condor submit file into ClassAd • hands over the job to CondorC • Condor • responsible for • performing the actual job management operations: job submission, removal • Log Monitor • is responsible for • watching the Condor log file • intercepting interesting events concerning active jobs • events affecting the job state machine • triggering appropriate actions.

  6. Overview of WMS [5/5] • Task Queue • Gives the possibility to keep track of the requests if no resources are immediatelly avalaible • Non-matching requests will be retried periodically (eager scheduling) • Or wait for notification of avalaible resources (lazy scheduling)

More Related