1 / 8

CPT Demo May 10 2004

CPT Demo May 10 2004. Build on SC03 Demo and extend it. Phase 1: Doing Root Analysis and add BOSS, Rendezvous, and Pool RLS catalog to analysis workflow Phase 2: Add analysis web client to analysis front end Phase 3: Add MC run job service and ability to submit ORCA files

trina
Télécharger la présentation

CPT Demo May 10 2004

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. CPT Demo May 10 2004 Build on SC03 Demo and extend it. Phase 1: Doing Root Analysis and add BOSS, Rendezvous, and Pool RLS catalog to analysis workflow Phase 2: Add analysis web client to analysis front end Phase 3: Add MC run job service and ability to submit ORCA files Phase 1 is certainly feasible, Phase 3 uncertain (Therefore Phase 1 and 2 as backup)

  2. People involved: People Involved: Rick Cavanaugh (UFL) Applications Dimitri Bourilkov (UFL) CAVES Mandar Kulkarni (UFL) CAVES/Sphinx Craig Prescott (UFL) (consultant on CMS production tools) Jang Uk (UFL) Sphinx Laukik Chitnis (UFL) Monitoring Conrad Steenberg (Caltech) Michael Thomas (Caltech) Frank v. Lingen (Caltech) …….??

  3. Components used and work to be done for Demo: (between brackets an estimate of how “finished” these components are) • Root Clarens Client (100%) • Web based Client (70%) • Chimera Clarens Service (100%) • Sphinx Job Submission Client (90%) • BOSS Clarens Service (90%) • Clarens Rendezvous Service (85%) • Clarens File Service (100%) • Clarens POOL Service (90%) • MCRunJob Clarens Service (??%) (Contact Anzar from FNAL) • MonaLisa (100%) • Web Interface for JClarens (80%) • BOSS WSDL (0%) • ACL Management GUI(70%) • Catalog Browser Interface (90%) • Which hosts will we use (one at least located at CERN?) • What analysis and data will we use? • Will we show a multi user analysis?

  4. Storage Element Computing Element Chimera Virtual Data Catalog Clarens-Service Service Flow for SC03 Demo (Rick’s mods) Analysis Client (ROOT+Web) 6 3 File Service Clarens-Service 4.4.2 Grid Site 4 4.4.1 4.1 MonALISAMonitoring Workflow Management: McRunJob/MOP Sphinx-Client Clarens-Service 4.4.1 Execution Globus + local sched 4.4 4.3 4.4.1 4.4.2 Sphinx Scheduler Clarens-Service 4.3.1 Sphinx Database MonALISA Central Repostiory RLS (LRC) RLS (RLI) 4.4.2

  5. Storage Element Computing Element Chimera Virtual Data Catalog Clarens-Service VO management Clarens-Service Look up Clarens-Service Service Flow for CPT Demo (Rick’s mods) Analysis Client (ROOT+Web) 1 6 5 2 3 File Service Clarens-Service BOSS Job-monitoring Clarens-Service 4.4.2 Grid Site 4 4.4.1 4.1 MonALISAMonitoring Workflow Management: McRunJob/MOP Sphinx-Client Clarens-Service 4.4.1 Execution Globus + local sched 4.2 4.4 POOL RLS - Meta Data Catalog Clarens-Service 4.3 Job = BOSS + Clarens-client 4.4.1 4.4.2 Sphinx Scheduler Clarens-Service 4.3.1 Sphinx Database MonALISA Central Repostiory RLS (LRC) RLS (RLI) 4.4.2 4.4.2

  6. Service Flow (Rick’s Mods) • 1 User authenticates • 2 User looks-up which services are available • 3 User queries either: • VDC for input data and defines the application + output data • or, POOL for input data • 4 User sends “job” request to Workflow Manager • 4.1 WM extracts/puts abstract “job” into VDC • 4.2 WM extracts input POOL information for abstract “job” • 4.3 WM sends abstract “job” to scheduler • 4.3.1 Scheduler queries RLS, MonALISA ; sends concrete “job” back to WM • 4.4 WM submits “concrete” job to grid site • 4.4.1 Job executes under a BOSS-Clarens-Client Wrapper; • 4.4.2 Job finishes ; RLS/POOL is updated ; data is available via Clarens FS • 5 User checks on status of “job” by querying BOSS Job-monitor • 6 User uses Clarens File Service to access ROOT files

  7. Service Flow for CPT Demo (CMS) Implementations Storage Element Computing Element Virtual Data Catalog VO management Look up authentication Analysis Client Clarens Root Client Java web interface client Clarens Register Clarens File Service Data collection Register GUI GUI GUI GUI Clarens GUI Grid Pool RLS MonALISA Monitoring Meta Data Catalog GUI Sphinx Job Submission GUI Workflow Management MC RunJob Clarens BOSS Execution Chimera ROOT FAMOS ORCA GUI Replica Location & Selection Sphinx Scheduling Scheduling

  8. Our Original Architecture as Comparison with the demo setup Storage Element Computing Element Virtual Data Catalog Policy & Accounting Replica Catalog Look up VO management Look up Look up (CMS) Implementations ROOT- Clarens/ Cojac/ IGUANA authentication Analysis Client 14 1 Clarens Register Reservation Experation Data collection Register 2 3 Register discovery Clarens Grid Authorized feedback feedback Supervisor Specification Analysis versioning 5 10 12 Autonomous decisions on behalf of user 13 CAVES Authorized 6 4 Clarens Authorized Pool Meta Data Catalog RefDB Authorized 12 10 MonALISA Authorized Steering Monitoring Workflow Management Shakar 12 BOSS BOSS 12 Condor Execution VDT-Server 7 11 Chimera Authorized Authorized 8 ROOT FAMOS ORCA 13 VDT-Client allocate Authorized Sphinx Replica Location & Selection 9 9 Sphinx Release resources Scheduling EDG RB CondorG Schedule Performance analysis 9 Replication based on trend analysis Clarens Authorized Replica Management Multiple applications/users will execute multiple service flows in a grid environment resources

More Related