The%20EGEE%20project:%20building%20an%20international%20production%20grid%20infrastructure%20David%20Fergusson%20NeSC%20Edinburgh

1
The EGEE project building an international
production grid infrastructureDavid
FergussonNeSC Edinburgh
Crossgrid 2004
EGEE is a project co-funded by the European
Commission under contract INFSO-RI-508833
2
Contents

• EGEE - what is it and why is it needed?
• Middleware current and future
• Operations providing a stable service
• Networking enabling collaboration
• Summary
• The material for this talk has been contributed
  by many colleagues in the EGEE LCG projects.
• It is heavily based on Bob Jones talk at UK AHM
  2004.

Despite its name EGEE is an International project
involving in particular Israel, Russia and the US
3
The next generation of gridsEGEE Enabling Grids
for E-science in Europe

• Build a large-scale production grid service to
• Underpin European science and technology
• Link with and build on national, regional and
  international initiatives
• Foster international cooperation both in the
  creation and the use of the e-infrastructure

4
In 2 years EGEE will

• Establish production quality sustained Grid
  services
• 3000 users from at least 5 disciplines
• over 8,000 CPU's, 50 sites
• over 5 Petabytes (1015) storage
• Demonstrate a viable general process to bring
  other scientific communities on board
• Propose a second phase in mid 2005 to take over
  EGEE in early 2006

5
EGEE and LCG

• EGEE builds on the work of LCG to establish a
  grid operations service

• LCG (LHC Computing Grid) - Building and operating
  the LHC Grid
• A collaboration between
• The physicists and computing specialists from the
  LHC experiment
• The projects in Europe and the US that have been
  developing Grid middleware
• The regional and national computing centres that
  provide resources for LHC
• The research networks

6
production grid service
Launched Sept03 with 12 sites, now more than 70
sites and continues to grow
Live updates http//goc.grid-support.ac.uk/lcg2
7
EGEE Activities
32 Million Euros EU funding over 2 years starting
1st April 2004

• 48 service activities (Grid Operations, Support
  and Management, Network Resource Provision)
• 24 middleware re-engineering (Quality
  Assurance, Security, Network Services
  Development)
• 28 networking (Management, Dissemination and
  Outreach, User Training and Education,
  Application Identification and Support, Policy
  and International Cooperation)

Emphasis in EGEE is on operating a
production grid and supporting the end-users
8

• EGEE - what is it and why is it needed?
• Middleware current and future
• Operations providing a stable service
• Networking enabling collaboration
• Summary

9
EGEE view of history
2001

DataTAG
AliEn
CrossGrid
...
SRM
2004
USA
EU
Used in
10
Current production mware LCG-2

• Regular updates (latest is LCG-2.2.0 August 2004)
• short term developments driven by operational
  priorities

11
gLite

• gLite - the new EGEE middleware (under test)
• Service oriented - components that are
• Loosely coupled (by messages)
• Accessible across network modular and
  self-contained clean modes of failure
• So can change implementation without changing
  interfaces
• Can be developed in anticipation of new uses
• and are based on standards. Opens EGEE to
• New middleware (plethora of tools now available)
• Heterogeneous resources (storage, computation)
• Interact with other Grids (international,
  regional and national)

12
Architecture Guiding Principles

• Lightweight (existing) services
• Easily and quickly deployable
• Use existing services where possible asbasis for
  re-engineering
• Interoperability
• Allow for multiple implementations
• Resilience and Fault Tolerance
• Co-existence with deployed infrastructure
• Reduce requirements on site components
• Co-existence (and convergence) with LCG-2 and
  Grid3 are essential for the EGEE Grid service
• Service oriented approach
• Follow WSRF standardization
• No mature WSRF implementations exist to date so
  start with plain WS (WS-I)
• Provide framework to others so higher-level
  services can be developed quickly
• Architecture
  https//edms.cern.ch/document/476451

13
gLite Approach

• Exploit experience and components from existing
  projects
• AliEn, VDT, EDG, LCG, and others
• Design team works out architecture and design
• Feedback and guidance from EGEE PTF
  applications Operations, LCG GAG ARDA
• Components are initially deployed on a prototype
  infrastructure
• Small scale (CERN Univ. Wisconsin)
• Get user feedback on service semantics and
  interfaces
• After internal integration and testing,
  components are delivered to grid operations group
  and deployed on the pre-production service

Draft Design - https//edms.cern.ch/document/48787
1/ PTF Project Technical Forum
(http//egee-ptf.web.cern.ch/egee-ptf/default.htm)
GAG Grid Application Group (http//project-lcg-
gag.web.cern.ch/project-lcg-gag/) ARDA - A
Realisation of Distributed Analysis for LHC
(http//lcg.web.cern.ch/LCG/peb/arda/Default.htm)
14
Future EGEE Middleware - gLite

• Intended to replace LCG-2
• Starts with existing components from AliEN, EDG,
  VDT etc.
• Aims to address LCG-2 shortcoming and advanced
  needs from applications
• Prototyping short development cycles for fast
  user feedback
• Initial web-services based prototypes being
  tested with representatives from the application
  groups

Application requirements http//egee-na4.ct.infn.i
t/requirements/
15

• EGEE - what is it and why is it needed?
• Middleware current and future
• Operations providing a stable service
• Needs more than middleware
• Organisational, operational infrastructure
• Networking enabling collaboration
• Summary

16
User-view of EGEE a multi-VO Grid
User Interface
User Interface
Grid services
17
EGEE adding a VO

• EGEE has a formal procedure for adding selected
  new user communities (Virtual Organisations)
• Negotiation with one of the Regional Operations
  Centres
• Seek balance between the resources contributed by
  a VO and those that they consume.
• Resource allocation will be made at the VO level.
  
• Many resources need to be available to multiple
  VOs shared use of resources is fundamental to a
  Grid

18
Authentication, Authorisation

• Authentication
• User obtains certificate from CA
• Connects to UI by ssh
• Downloads certificate
• Invokes Proxy server
• Single logon to UI - then Secure Socket Layer
  with proxy identifies user to other nodes

CA
Personal
VO mgr
VO service

• Authorisation - currently
• User joins Virtual Organisation
• VO negotiates access to Grid nodes and resources
  (CE, SE)
• Authorisation tested by CE, SE
• gridmapfile maps user to local account

VO database
SSL (proxy)
Gridmapfiles On CE, SE nodes
19
Running the Production Service

• Grid deployment has entered a new phase
• Basic middleware is working
• responsible now for a small fraction of the
  problems
• Outstanding performance/functionality issues
• RLS, RB / little modularity lack of consistent
  interfaces
• some solutions are being developed but many
  cannot be addressed in current software/architectu
  re - set priorities for new middleware (gLite)
• Many operational issues
• mis-configuration, out of date mware, single
  points of failure, failover, mgmt interfaces
• resources unsuitable for applications needs (e.g.
  insufficient disk space)
• slow response by sites to problems (holiday
  periods, security concerns)
• new middleware will not help for many of these
  issues - grid partners must think Service

The grid still does not appear as a single
coherent facility applications must adapt to the
current service to gain maximum profit but
result has been very effective for LHCb - 3000
concurrent jobs (August)
20
EGEE Operations (I) OMC and CIC

• Operation Management Centre
• located at CERN, coordinates operations and
  management
• coordinates with other grid projects
• Core Infrastructure Centres
• behave as single organisations
• operate core services (VO specific and general
  Grid services)
• develop new management tools
• provide support to the Regional Operations
  Centres

21
EGEE Operations (II) ROC

• Regional Operations Centre responsibilities and
  roles
• Testing (certification) of new middleware on a
  variety of platforms before deployment
• Deployment of middleware releases coordination
  distribution inside the region
• integration of Local VO
• Development of procedures and capabilities to
  operate the resources
• First-line user support
• Bring new resources into the infrastructure and
  support their operation
• Coordination of integration of national grid
  infrastructures Provide resources for
  pre-production service

22
EGEE Middleware Migration

• LCG-2
• Current base for production services
• Evolves with certified new or improved services
  from the preproduction
• Pre-production Service
• Early application access for new developments
• Certification of selected components from gLite
• Starts with LCG-2
• Migrate new mware in 2005
• Organising smooth/gradual transition from LCG-2
  to gLite for production operations

23

• EGEE - what is it and why is it needed?
• Middleware current and future
• Operations providing a stable service
• Networking enabling collaboration
• Current application communities
• Summary

24
EGEE pilot application Large Hadron Collider

• Data Challenge
• 10 Petabytes/year of data !!!
• 20 million CDs each year!
• Simulation, reconstruction, analysis
• LHC data handling requires computing power
  equivalent to 100,000 of today's fastest PC
  processors!
• Operational challenges
• Reliable and scalable through project lifetime of
  decades

Mont Blanc (4810 m)
Downtown Geneva
25
EGEE pilot application BioMedical

• BioMedical
• Bioinformatics (gene/proteome databases
  distributions)
• Medical applications (screening, epidemiology,
  image databases distribution, etc.)
• Interactive application (human supervision or
  simulation)
• Security/privacy constraints
• Heterogeneous data formats - Frequent data
  updates - Complex data sets - Long term archiving
  
• BioMed applications deployed and going live in
  September
• GATE - Geant4 Application for Tomographic
  Emission
• GPS_at_ - genomic web portal
• CDSS - Clinical Decision Support System

• http//egee-na4.ct.infn.it/biomed/applications.htm
  l

26
BLAST comparing DNA or protein sequences

• BLAST is the first step for analysing new
  sequences to compare DNA or protein sequences to
  other ones stored in personal or public
  databases. Ideal as a grid application.
• Requires resources to store databases and run
  algorithms
• Can compare one or several sequence against a
  database in parallel
• Large user community

27
A look at the future the HealthGrid vision
HealthGRID
In this context "Health" does not involve only
clinical practice but covers the whole range of
information from molecular level (genetic and
proteomic information) over cells and tissues, to
the individual and finally the population level
(social healthcare).
Patient related data
Public Health
Databases
Association Modelling Computation
Public Health
Patient
Patient
Tissue, organ
Tissue, organ
Cell
Cell
Molecule
Molecule
INDIVIDUALISED HEALTHCARE MOLECULAR MEDICINE
S. Nørager Y. Paindaveine European
Commission DG-INFSO
Computational recommendation
28
Earth Sciences in EGEE

• Research
• Earth observations by satellite
• (ESA(IT), KNMI(NL), IPSL(FR), UTV(IT),
  RIVM(NL),SRON(NL))
• Climate
• DKRZ(GE),IPSL(FR)
• Solid Earth Physics
• IPGP (FR)
• Hydrology
• Neuchâtel University (CH)
• Industry
• CGG Geophysics Company (FR)

29
Climate Applications in EGEE

• Model Atmosphere, Ocean, Hydrology, Atmospheric
  and Marine chemistry.
• Goal Comparison of model outputs from different
  runs and/or institutes
• Large volume of data (TB) from different model
  outputs, and experimental data
• Run made on supercomputer      gt Link the EGEE
  infrastruture with supercomputer Grids (DEISA)

EXAMPLE For the IPCC Assessment reports many
experiment are performed with different models
(different spatial resolution, different
time-step, different "physics" ..) and various
sites. The generated data need to be compared in
a comprehensive and "unified" way.
30
Earth Observation Application Approach to Data
and Metadata deployment on European DataGrid
testbedand on EGEE

• IPSL M. Petitdidier, S. Godin, C. Boonne, C.
  Leroy
• KNMI W. Som de Cerff
• ESA-ESRIN L. Fusco, J. Linford

31
Earth Observation Ozone

• Building on European Datagrid experience
• To produce and store the Ozone profiles or
  columns
• Enhance availability
• To extend the processing capabilities
• Validation against other data
• Mid-latitude ozone studies
• ...
• To facilitate collaboration
• Including with emerging large scale European
  projects

GOME instrument (75 GB - 5000 orbits/y) 28000
profiles/day
32
Resources added to EGEE

• Starting point
• ESA UI, CE (15 nodes), SE (1.4 TB)
• IPSLIPGP at Paris University Computer Center
  4PC, SE (500Gb), UI
• IPGP UI
• DKRZ UI, CE (2nodes), SE up to several TB as a
  function of the application
• KNMI UI possibility to use VO NIKHEF and Sara
  facilities for the Research ES
• As new applications are ported new resources will
  be added

33
Solid Earth Physics Application

• Objectives demonstration to drive the
  community, and production of scientific results
• GPS data final goal workflow with data storage,
  processing, analysis and visualisation
• Synthetic seismograms
• Numerous data and computations, access to
  databases
• Earth Core dynamo

• Strategy
• Demonstrate the secure and restricted access to
  database
• Propose tests inside EU project like SPICE
• Obtain scientific results to constitute databases
  and propose to the concerned community access via
  the Grid

34
Geophysics Applications
Seismic processing Generic Platform - Based on
Geocluster, an industrial application to be a
starter of the core member VO. - Include several
standard tools for signal processing, simulation
and inversion.

• - Opened any user can write new algorithms in
  new modules (shared or not)
• - Free for academic research
• Controlled by license keys (opportunity to
  explore license issue at a grid level)
• initial partners F, CH, UK, Russia, Norway

35
Computational Chemistry molecular simulator
Ar - Benzene
36
Critical Features of the Individual Programs

• AB INITIO METHODS (molpro, gamess, adc, gaussian,
  ) resource requests are proportional to N3 (N is
  the number of electrons) and to MD (M is the
  number of grid points per dimension D) for CPU
  and disc demand.
• EMPIRICAL FORCE FIELDS (Venus, dl_poly, )
  resource requests are proportional to P!
  (P is the number of atoms)

• DYNAMICS (APH3D, TIMEDEP, ) these programs use
  as input the output of the previous module most
  critical dependence is on the total angular
  momentum J value that can increase up to several
  hundred units and the size of the matrices depend
  on 2J1
• KINETICS PROGRAMS use dynamics results for
  integrating relevant time dependent applications

37
The MAGIC telescope

• Largest Imaging Air Cherenkov Telescope (17 m
  mirror dish)
• Located on Canary Island La Palma (_at_ 2200 m asl)
• Lowest energy threshold ever obtained with a
  Cherenkov telescope
• Aim detect ?ray sources in the unexplored
  energy range 30 (10)-gt 300 GeV

38
The MAGIC Physics Program

• Cosmological g-Ray Horizon

• AGNs

• Pulsars

• Tests of Quantum Gravity effects

• Origin of Cosmic Rays

• SNRs

• Cold Dark Matter

• GRBs

39
Data Acquisition Rate Storage

• Event Size
• 577 PM x 1 Byte x 30 samples
• ? 20 kByte/event

• Data Acquisition Rate
• 500 Hz typical trigger rate
• ? 10 MByte/sec

• Data Storage Requirements
• 1000 h / year useful moonless observation time
  
• ? 36 TByte/year

40
MAGIC Summary

• MAGIC
• is a new generation gamma ray Cherenkov telescope
  
• has large discovery potential both in
  astrophysics and fundamental physics
• just started data taking
• has large computing requirements
• gt 100 CPU
• gt 50 TB / year
• is well suited to join and test GRID technology
  with 16 participating institutions over all
  Europe (and beyond)some with strong links to
  mayor GRID sites (Bologna, Barcelona)

41
Applications in EGEE

• Production service supporting multiple VOswith
  different requirements
• Data
• Volume
• Location distributed?
• Write Once or Update?
• Metadata archives?
• Controlled or open access?
• Computation
• High throughput ( current LCG)
• High performance, supercomputing
• No. of sites, scientists,
• Establish viable general process to bring other
  scientific communities on board

42

• EGEE - what is it and why is it needed?
• Middleware current and future
• Operations providing a stable service
• Networking enabling collaboration
• Current application communities
• Enabling new and effective use of EGEE
• Summary

43
Who else can benefit from EGEE?

• EGEE Generic Applications Advisory Panel
• For new applications
• EU projects MammoGrid, Diligent, SEE-GRID
• Expression of interest Planck/Gaia
  (astroparticle), SimDat (drug discovery)
• http//agenda.cern.ch/age?a042351
• Next meeting at EGEE conference (November)

44
Bringing new applications to the grid

• Outreach events inform people about the grid /
  EGEE
• Application experts discuss specific
  characteristics with the users
• Migrate application to EGEE infrastructure with
  the help of EGEE experts
• Initial deployment for testing purposes
• Production usage - user community contributes
  computing resources for heavy production
  demands - Canadian dinner party

45
Dissemination

• 1st project conference
• Over 300 delegates came to the 4 day event during
  April in Cork Ireland
• Kick-off meeting bringing together
  representatives from the 70 partner organisations
• 2nd conference scheduled
• 22-26 November in The Hague
• http//public.eu-egee.org/conferences/2nd/
• Websites, Brochures and press releases
• For project and general public www.eu-egee.org
• Information packs for the general public, press
  and industry

46
User training and induction

• Training material and courses from introductory
  to advanced level
• Train a wide variety of users both internal to
  the EGEE consortium and external groups from
  across Europe
• 20 courses/presentations already held and many
  more planned (see roadmap)
• Experience with GENIUS portal and GILDA testbed
• Courses inline with the needs of the projects and
  applications

Training http//www.egee.nesc.ac.uk/ Roadmap
http//www.egee.nesc.ac.uk/schedreg/index.html R
epository http//www.egee.nesc.ac.uk/trgmat/index
.html
47
EGEE Industry Forum

• EGEE Industry Forum
• raise awareness of the project in industry to
  encourage industrial participation in the project
• foster direct contact of the project partners
  with industry
• ensure that the project can benefit from
  practical experience of industrial applications
• For more info
• http//public.eu-egee.org/industry/

48
Private vs Federated Resources

• For applications that must operate in a closed
  environment, EGEE middleware can be downloaded
  and installed on closed infrastructures
• Approach being used by MammoGrid

EGEE sites are administered/owned by different
organisations Sites have ultimate control over
how their resources are used Limiting the demands
of your application will make it acceptable to
more sites and hence make more resources
available to you
49

• EGEE - what is it and why is it needed?
• Middleware current and future
• Operations providing a stable service
• Networking enabling collaboration
• Current application communities
• Enabling new and effective use of EGEE
• Building with international, regional and
  national grids
• Summary

50
SEE-GRIDExpanding the eInfrastructure
inclusion into South-East Europe!

• Prof. Vasilis Maglaris
• GRNET - Greek Research Technology Network
• maglaris_at_grnet.gr, http//www.grnet.gr
• Dublin, April 2004

51
Foundation SEEREN
52
Project Members

• Key words
• Human network
• South-East Europe
• Grid eInfrastructure

• Contractors
• GRNET (Co-ord.) Greece
• CERN Switzerland
• CLPP-BAS Bulgaria
• ICI Romania
• TUBITAK Turkey
• SZTAKI Hungary
• INIMA Albania
• BIHARNET Bosnia-Herzegovina
• UKIM FYROM
• UOB Serbia-Montenegro
• RBI Croatia
• Third Parties
• 18 universities and research institutes

53

• EGEE - what is it and why is it needed?
• Middleware current and future
• Operations providing a stable service
• Networking enabling collaboration
• Current application communities
• Enabling new and effective use of EGEE
• Building with international, regional and
  national grids
• Intellectual property and EGEE
• Summary

54
Intellectual Property

• The existing EGEE grid middleware (LCG-2) is
  distributed under an Open Source License
  developed by EU DataGrid
• Derived from modified BSD - no restriction on
  usage (academic or commercial) beyond
  acknowledgement
• Same approach for new middleware (gLite)
• Application software maintains its own licensing
  scheme
• Sites must obtain appropriate licenses before
  installation

55

• EGEE - what is it and why is it needed?
• Middleware current and future
• Operations providing a stable service
• Networking enabling collaboration
• Current application communities
• Enabling new and effective use of EGEE
• Building with international, regional and
  national grids
• Intellectual property and EGEE
• Summary

56
EGEE Plans for the coming year

• September
• First non-HEP applications running on LCG-2
  production service
• Security architecture/ Grid services design for
  new mware
• Deployment of 2nd gLite prototype
• November
• 2nd EGEE conference (Den Hague) in common with
  DEISA, SEE-GRID, DILIGENT etc.
• December
• Application migration reports
• February 2005
• 1st EU review
• March 2005
• Large-scale deployment of gLite software
• Annual report

42 deliverables in 1st year
57

• e-Infrastructure
• Integrating networks, grids and emerging
  technologies
• Based on standards
• Underpinning research, industry, the knowledge
  economy
• International, collaborative effort
• Moving to a Service Orientated Architecture
• Focus Production grids for multiple VOs
• Demands massive effort in organisation and
  administration
• Operations
• Support
• Training

58
Summary

• EGEE is the first attempt to build a worldwide
  Grid infrastructure for data intensive
  applications from many scientific domains
• A large-scale production grid service is already
  deployed and being used for HEP and BioMed
  applications with new applications being ported
• Resources user groups will rapidly expand
  during the project
• A process is in place for migrating new
  applications to the EGEE infrastructure
• A training programme has started with events
  already held
• Prototype next generation middleware is being
  tested (gLite)
• Plans for a follow-on project are being discussed

59
Further Information
EGEE www.eu-egee.org LCG lcg.web.cern.ch/LCG/ NeS
C www.nesc.ac.uk The Grid Cafe www.gridcafe.org