EGI InSPIRE SA3: Status & Plans

Jamie.Shiers@cern.ch

WLCG Grid Deployment BoardJune 2010

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 & outlook2

WP6: TasksTask (PM) Purpose Contact / Leader

TSA3.1 (18) Management Jamie Shiers (50%)

TSA3.2 (315) Shared Services & Tools1. Dashboards2. Applications3. Services4. Workflows & Schedulers5. MPI

Jamie Shiers

TSA3.3 (263) Services for HEP Maria Girone

TSA3.4 (79) Services for LS Johan Montagnat

TSA3.5 (30) Services for A&A Claudio Vuerli

TSA3.6 (27) Services for ES Horst Schwichtenberg

• We need a transparent mechanism for agreeing workplan, particularly in TSA3.2

3

WP6: Partner / Activity OverviewPartner (by ID) Areas of work (may not be complete…)

KIT-G TSA3.6 Services for ES

CSIC TSA3.2.4 Workflows and Schedulers

CSC TSA3.2.4 Workflows and Schedulers

CNRS TSA3.2.3 Services: HYDRA , TSA3.4 Services for LS

TCD TSA3.2.5 MPI

INFN TSA3.2.3 Services: GReIC, TSA3.2.5 MPI, TSA3.3 (HEP), TSA3.4 (A&A)

CYFRONET TSA3.2.4 Workflows and Schedulers

ARNES TSA3.2.2 Applications

UI SAV TSA3.2.2 Applications

CERN TSA3.1, TSA3.2, TSA3.3

EMBL TSA3.2.4 Workflows and Schedulers

4

5

Participant Number

Participant Short name / Lead Beneficiary

WP 6 (SA3): Services for Heavy User CommunitiesPerson Months per Task

Person Months

per Effort Type

Total Person Months

TSA3.1 TSA3.2+F+CCMST

TSA3.3HEP

TSA3.4LS

TSA3.5A&A

TSA3.6ES

General

10 KIT-G 27 27 27

Fraunhofer 27 27 27

12 CSIC 45 45 45

CSIC 27 27 27

CIEMT 18 18 18

13 CSC 18 18 18

14 CNRS 30 53 83 83

19 TCD 21 21 21

21 INFN 36 60 30 126 126

INFN 60 60 60

UNIPG 9 9 9

SPACI 27 27 27

28 CYFRONET 6 6 6

31 ARNES 3 3 3

32 UI SAV 18 18 18

35 CERN 18 120 203 341 341

37 EMBL 18 26 44 44

TOTALS 18 315 263 79 30 27 732 732

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

WP6: “HEP” ManpowerTSA1.1 Management 18PM Jamie Shiers (staff)

TSA3.2.1 Dashboards 60PM Julia Andreeva (staff)Edward Karavakis (FELL) 1 July 2010

TSA3.2.2 Ganga / Diane 60PM Massimo Lamanna (staff)LD / FELL

TSA3.3 HEP: CERN 203PM Maria Girone (staff)Fernando Barreiro Megino (FELL) 1 June 2010Alexander Loth (DOCT) 1 June 2010Raffaello Trentadue (FELL) 1 July 2010~3 LD / FELL slots - IT-ES-2010-153-LD

TSA3.3 HEP: INFN 60PM 2 slots – 2011?

401PM

6

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).

7

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

8

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?)

9

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. ]

10

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

11

Milestone Responsible Month Due

Contact points & support model CSC 1 (now)

S/W roadmap INFN 4 (~EGI Technical Forum)

Services for HEP CERN 4

EGI WP6 Deliverables# What When

1 Capabilities offered by the HUCs to other communities (report) 4

2 Sustainability plans for the HUC activities 9

3 Annual Report on the HUC Tools and Services 11

4 Capabilities offered by the HUCs to other communities 16

5 Sustainability plans for the HUC activities 21

Etc.

12

• How can these reports be (p)re-used?• CHEP papers? Internal WLCG documents?

• 3 deliverables, milestones + additional reporting non-negligible amount of effort…

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!) 13

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

14

And ROSCOE bis?

• Probably not…

15