1 / 4

ProdSys2 ADC SW Development meeting , CERN, 4 February 2013

ProdSys2 ADC SW Development meeting , CERN, 4 February 2013. Kaushik De, Alexei Klimentov. Progress and Status. Blackboard at IJS (Jun 2012). Documentation, Twiki , Blogs (more in Maxim’s and Tadashi’s talks) Fundamental principals New development shouldn’t affect current operations

sirvat
Download Presentation

ProdSys2 ADC SW Development meeting , CERN, 4 February 2013

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. ProdSys2ADC SW Development meeting, CERN, 4 February 2013 Kaushik De, Alexei Klimentov

  2. Progress and Status Blackboard at IJS (Jun 2012) • Documentation, Twiki, Blogs (more in Maxim’s and Tadashi’s talks) • Fundamental principals • New development shouldn’t affect current operations • Implement new features on the way it will be in ProdSys2 • Whenever it is possible • Main effort in the last 3 months • Jobs Execution Definition Interface (T.Maeno) • Database Engine for Tasks (M.Potekhin) • Database schemas (G.Dimitrov, T.Maeno) and backend (M.Nowak) • Conceptual database design for JEDI • Monitoring and AGIS integration are not discussed today, but on both fronts there is a significant progress. Starting from March : expect more time from Sasha, Paul, Dmitry (at CERN, TBC), Kaushik and Alexei (+Wolfgang for the upper level I/F and DEfT matters) US ATLAS Computing committed additional 0.5 FTE (aka RBT) for ProdSys2 development Alexei Klimentov – ProdSys2

  3. Simulation Production Chain • AP tasks were defined ~at the same time • Less than one month from AP to Group Production NTUP • Transientdatasets (tasks) can be identified in task submission time and deleted at the ‘end of chain’ • ‘End of chain’ : (1) TAG production (2) GP production • Production steps naming convention should be revisited Production chain example Observations : the consistency in production step naming convention is broken. Need attention from meta-data coordination Now we are paying for many ad-hoc solutions implemented in ProdSys1 Two approaches - modify TR submission and implement automatic datasets obsoletion in the current system. Use it later for ProdSys2 - continue scripts maintenance (+ writing new scripts) and postpone everything to a new system Alexei Klimentov – ProdSys2

  4. Timetable Kaushik talk (SW&C week October 2012) : • Approximate schedule • Schema – by end of 2012 • First JeDi task – summer 2013 • Complete transition – by end of 2013 • Need discussions to collect requirements • Will have dedicated meetings during the next 6 months with all teams that request tasks, and transform, PanDA, Rucioteams • We are on schedule, despite of many recent requirements • Near term plan • JEDI – DEfT ‘integration’ • ‘task chain’ with marking ‘transient’ tasks and integration it with the current system • Revision of production steps • Archiving logs (Hadoop prototype) • Technical Design Report and “final” list of requirements by May TIM in Tokyo Alexei Klimentov – ProdSys2

More Related