1 / 6

Scheduling Policy

Scheduling Policy. Andrew Sansum e-Science Centre, CCLRC-RAL Tier1 Board May 2004. So What Exactly is a Tier1 . Three(?) Levels of Scheduling External (GRID Level) Selection of destination by users Direction of work by RB Macro (Farm Level/Experiment)

duane
Download Presentation

Scheduling Policy

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. Scheduling Policy Andrew Sansum e-Science Centre, CCLRC-RAL Tier1 Board May 2004

  2. So What Exactly is a Tier1 Three(?) Levels of Scheduling • External (GRID Level) • Selection of destination by users • Direction of work by RB • Macro (Farm Level/Experiment) • Deploy Hardware into appropriate infrastructure (eg Babar Tier A or LCG) • Meet target instantaneous shares and priorities set by EB • Problematic when multiple clusters • Micro (User Level) • Schedule individual jobs to meet Macro requirements • While (VERY IMPORTANT TOO): • Allowing newcomers to get rapid job starts • Prevent jobs running for too long hogging resources • While letting test work start for users even though production is running • Prioritising mission critical user ids • Preventing resources being underused • …. Moan moan moan moan  why doesn’t my job(s) start .. Why do THEY get more than me .. Tier1 Group

  3. EB Scheduling Policy (Macro Policy) • EB Reviews Quarterly • Will set “Target Allocation” of disk, CPU and Tape(?) • Function of Time (for example weekly) • Tier 1 will provide scheduling system (EG MAUI, PBS FIFO etc etc) • Departures from agreed priorities need agreement of EB chair. • EB will compare usage to allocation and require explanation of discrepancies • Load factor must exceed 70% Tier1 Group

  4. Issues Discussed • Request for ability for devolved responsibility to Tier 1 to make local short term urgent adjustments. Denied unless request is “small” need OK of EB chair. • Concern expressed by experiments that running at 70% plus load was not consistent with GRID development work they needed to carry out. Tier1 Group

  5. Farm Scheduling Status • MACRO • Run MAUI on Tier A – already control macro level allocations • Run PBS FIFO on LCG. Some capability to do macro level scheduling but rather limited. Currently testing. Otherwise could run Scalable PBS (provides MAUI) • MICRO • Not yet a problem on LCG – FIFO scheduler rather limited • Using MAUI on Tier A. No recent complaints, but Roger sceptical:“Current scheduling may not be optimal but it is not clear if a better solution exists”(C. Brew 2004) • MAUI rather complex and some strange features • Lack good objective scheduling metrics – may start “probing” regularly Tier1 Group

  6. OS Installation System • Deliverable in GRIDPP2 for deployment in December 2004 • Need something to operate LCG once Redhat Enteprise is deployed. • Have tested Quator for LCG community project (Steve).Given feedback on documentation. • Have a Quator installation (For EGEE JRA1 – which will use) • “Amazingly Complicated” Steve Traylen 2004!! • But if not Quator – then what. Quator still most likely candidate. Tier1 Group

More Related