1 / 15

EGI InSPIRE SA3: Status & Plans

EGI InSPIRE SA3: Status & Plans. Jamie.Shiers@cern.ch WLCG Grid Deployment Board June 2010. Overview. Status & Directions of EGI InSPIRE SA3 732 person month project over 36 months ~400 person months for services for HEP Σ (tasks) Duration: 1 st May 2010 – 31 st April 2013

velma-alexander
Download Presentation

EGI InSPIRE SA3: Status & Plans

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. EGI InSPIRE SA3: Status & Plans Jamie.Shiers@cern.ch WLCG Grid Deployment Board June 2010

  2. Overview • Status & Directions of EGI InSPIRE SA3 • 732 person month project over 36 months • ~400 person months for services for HEP Σ(tasks) • Duration: 1st May 2010 – 31st April 2013 • Workplan and directions, including collaboration with other communities • EGEE – EGI transition & outlook

  3. WP6: Tasks • We need a transparent mechanism for agreeing workplan, particularly in TSA3.2

  4. WP6: Partner / Activity Overview

  5. Total “HEP” = 18 + 120 + 263 = 401 PM / 36 months

  6. WP6: “HEP” Manpower • Constraints: • 341 PM (currently at 342) • EUR1,868,618 • Project (task?) end date • (InSPIRE is 48 months…)

  7. WP6: Reporting • In addition to the milestones & deliverables, it is foreseen that each (sub-)task will present its status at the EGI Technical Forum in Amsterdam in September • Starting regular partner / task con-calls • First was yesterday: frequency TBD (≥ 1/month) • Weekly AMB calls with EGI • All WP6 people need to complete time-sheets! • Minimize reporting overhead by (p)re-using reports for multiple purposes • Need to orient reports to specific meetings; • Should probably broaden to entire teams (IT-ES group).

  8. Results from 1st Partner Call • Agenda – wikis, Indico, mailing lists etc. • Wiki areas created for each (sub-)task; contacts ~completed; • Work-plan per task / sub-task • TSA3.6 (ES): 27 PM, one partner • TSA3.5 (A&A): 30 PM, one partner, two contacts • TSA3.4 (LS): 79 PM, two partners, two contacts • TSA3.3 (HEP): 263 PM, two partners, many contacts! • TSA3.2 (all): 315 PM • Frequency of calls (monthly / bi-monthly) • Should correspond to effort / level of activity • Input from different (sub-)tasks will be taken to tomorrow’s TLM in AMS

  9. WP6: Work-plan • We already regularly meet the computing management of the LHC experiments to discuss and agree priorities • This is “independent” of EGI InSPIRE – general Experiment Support issues • Propose we record the outcome of these discussions (at appropriate level) in EGI Request Tracker • Essential for shared services; • Valuable for all in terms of tracking & reporting • We also need to keep in mind the overall goals of the WP / project • Long-term sustainability; • Promoting adoption of common tools. • More details on work-plan later • Input to Task Leaders meeting tomorrow in Amsterdam • Broaden to other projects (same disciplines – others?)

  10. How? EGI TF & Others • In addition to the status reports proposed for the TF have suggested that “related projects” in which CERN is involved (ES: EnviroGRIDS, LS: Partner, ULICE, …) should report at EGI TF; • See CERN Press Release on Physics for Health • Suggesting workshop / track at future IEEE NSS / MIC (probably from 2011…) • Also suggested DM track at EGI TF • Goal: “win-win” – minimize overheads and maximize benefits • [ Projects with funding that does not require matching effort more attractive than those that do. ]

  11. EGI WP6 Workplan • Globally: expect lead / only partner to coordinate the main tasks (“Services for …”) • Less obvious in TSA3.2: for WLCG this concerns Dashboards & Ganga – funded resources • In terms of coordination: try to encourage collaboration, adoption of common tools (or at least ideas…) and ensure M&D are met

  12. EGI WP6 Deliverables • How can these reports be (p)re-used? • CHEP papers? Internal WLCG documents? • 3 deliverables, milestones + additional reporting non-negligible amount of effort…

  13. EGI Transition: Discussion • Not all is defined yet… • Quite a few additional (un-funded) responsibilities have come / are coming our way… • Coordination with OSG; • USAG futures??? • Some of these have been folded into Daily Operations call & fortnightly Service Coordination Meetings • An additional point to watch here is support: effort available globally has reduced significantly • To understand in collaboration with SA3 and NA3, how GGUS existing support units for user-specific issues can be populated. Ticket • Clearly essential for WLCG that nothing breaks: quite a lot of stress! (Coincidence of transition with LHC run!)

  14. Summary • EGI InSPIRE SA3 starting: quite some overhead which hopefully will reduce now… • Important to transparently agree priorities not only within HEP but also across communities • Continue regular discussions with experiment computing management for this purpose

  15. And ROSCOE bis? • Probably not…

More Related