150 likes | 303 Views
Feasibility study – server side. Fernando H. Barreiro Megino Mattia Cinquilli Daniele Spiga Daniel C. van der Ster CERN IT-ES-VOS. News. Meetings with the experts to review the analysis frameworks used by ATLAS and CMS This week focusing on server side (PanDA server and CMS WMS)
E N D
Feasibility study – server side Fernando H. Barreiro Megino Mattia Cinquilli Daniele Spiga Daniel C. van der Ster CERN IT-ES-VOS
News • Meetings with the experts to review the analysis frameworks used by ATLAS and CMS • This week focusing on server side (PanDA server and CMS WMS) • Thanks to Paul Nilsson, Tadashi Maeno, Steve Foulkes, Simone Campana & Eric Vaandering for their time • Information is tracked on our document • Now readable by anyone who has the link • https://docs.google.com/document/d/1PJDBuH4gd5w5CzUJ5n2i7uOaFrhcYo5-5YErQdpzjvo/ed • This presentation should give an overview of our findings and the recommendations so far • Please interrupt for discussion, questions and corrections
CMS analysis framework DISTRIBUTED CENTRAL
Ideas about Common Approach:Data I/O Issues • After comparing the functionalities, we asked each of the server experts how the systems could be used as a common solution • The existing tight coupling between the data management and WM systems was previously seen as a potential showstopper, so we focused on this
PanDA Data I/O Solution • Could PanDA server handle CMS data? • Not a very tight DQ2/Panda coupling • New libraries would have to be written • Input files • Store just LFN in PandaDB • CMSSW queries the Trivial File Catalog (TFC) and stages the data • Panda pilot would use a no-op mover (CMSSW reads the LFNs directly) • Output files • Wrapper/pilot copies files to the SE • Place files according to Trivial File Catalog • Write LFN’s and storage site name back to PanDA • Still need optional DBS registration and external asynchronous stage out service
CMS WMSystem Data I/O Solution • Could CMS WMSystem handle ATLAS data? • Data discovery/registration: • Not a very tight DM/WM coupling • Interface to DM service is pluggable • Input and output would remain responsibility of the pilot “wrapper script”
Priority & Fairshare Issues • PanDA has flexible priority mechanisms which are implemented and used in production for a few years • CMS WMSystem priorities extend to the requests – nothing in the model prevents priorities from being implemented down to Local Agents
Conclusions • This week was focused on PanDA and the CMS WMSystem at the server side • Main differences between the two systems • Complexity of the systems and levels of queuing • CMS designed a distributed architecture to achieve scalability and fault tolerance • PanDA has a simple, central architecture and it has demonstrated scalability • Clear tradeoffs: • Central service has global view/control but single point of failure • Distributed service has higher scalability reliability but lacks global view/control • Resource allocation • Dynamic brokerage in PanDA, more fixed in WMSystem given distributed character • No show stoppers detected and positive attitude seen • Next weeks: investigate pilot frameworks and glideInWMS