1 / 7

Impact of end of EMI+EGI-SA3

Impact of end of EMI+EGI-SA3. April 2013: EMI project finishes EGI-Inspire-SA3 finishes (mainly CERN affected) EGI-Inspire continues until April 2014 EGI.eu continues indefinitely Impact on WLCG & CERN IT. Impact in IT.

hector
Download Presentation

Impact of end of EMI+EGI-SA3

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. Impact of end of EMI+EGI-SA3 • April 2013: • EMI project finishes • EGI-Inspire-SA3 finishes (mainly CERN affected) • EGI-Inspire continues until April 2014 • EGI.eu continues indefinitely • Impact on WLCG & CERN IT

  2. Impact in IT • Significant reduction in staff in ES and GT groups (~33% and ~45% reduction resp.) • No prospect of additional equivalent funding in the near future • Re-prioritisation of functions is unavoidable

  3. Evolution of functions • CERN has some ongoing commitments to EGI.eu and NGIs • Esp since we expect EGI to support WLCG • These are in-line with what we need for LHC • Must focus remaining effort where can have the most impact • Better in areas that benefit >1 experiment; • Less “labelled” staff (dedicated to experiments) • EMI: • Complex infrastructure used by EMI no longer required • Middleware support process under active discussion with partners • IT responsible for DM m/w + info system – must be maintained

  4. What IT must do • WLCG operations, service coordination, support • Consolidate related efforts (daily ops, integration, deployment, problem follow-up etc) • Broader than just CERN – encourage other labs to participate • Common solutions • Set of activities benefitting several experiments. Coordinates experiment work as well as IT-driven work. Experiments see this as strategic for the future; beneficial for long term sustainability • Grid monitoring • Must be consolidated (SAM/Dashboards). Infrastructure becoming more common (also with AI mon); focus on commonalities, less on experiment-specifics • Grid swdev+support • WLCG DM tools (FTS, DPM/LFC, Coral/COOL, etc), information system; Simplification of build, packaging, etc.  open source community processes; (See WLCG doc)

  5. What can no longer be supported • Support for Ganga core • Agreed with Ganga collaboration • POOL • Now only used by ATLAS; they assume responsibility • Activities where no interest from experiments: • Gridview, SE-catalog sync, … will be stopped • Experiment-specific customisations of (e.g. dashboards, SAM tests) • Move to experiment teams • Previous level of dedicated expert support to experiments unsustainable • Understood by ATLAS/CMS; issue for LHCb and ALICE • Some reduction in this effort already – but…

  6. Notes • There is no simple definition of "common solutions" - actually this can be part of many different activities, but a coordination of this is required, as well as available effort to work on priority projects • Support for middleware: • Proposal for methodology under discussion (document) with EMI and EGI as well as within WLCG • Relies on on-going commitments from m/w development partners • Encouraging broader community involvement and support where possible (e.g. WLCG Operations, middleware such as DPM, …)

  7. Level of staffing in IT • To support the core activities we will have ~24 FTE from May 2013 • In addition some other staff/Fellows whose contracts have not yet ended during 2013, and involvements in other EU projects can help (e.g. in data management)

More Related