GridPP Deployment: Overview

The GridPP deployment pages may contain formatting and content issues which we need to address. Please help by offering your feedback. A list of useful contacts for feedback is here. Many thanks.

Background

GridPP operates a tiered structure in line with the Worldwid Large Hadron Collider Grid (WLCG) computing model. Within the UK we have a Tier-1 based at the Rutherford Appleton Laboratory and a number of institutes joined into 4 virtual UK Tier-2 regional centres. The Tier-2 structure is primarily to aid organisational, management and support activities.

The makeup of the GridPP Tier-2 centres

Who is involved?

Each UK Tier-2 has its own manager and technical coordinator who organise and progress deployment work within a Tier-2. This work requires the full participation of system administrators at each of the sites together with a number of GridPP funded support posts which are distributed across the institutes according to the resources they have agreed to provide. Details for the Tier-2s and institutes can be found on the pages linked from here:

ScotGrid: Edinburgh, Durham, Glasgow

SouthGrid: Bristol, Birmingham, Cambridge, Oxford, RAL, Sussex, Swansea, Warwick

London Tier-2: Brunel, Imperial, Queen Mary, Royal Holloway, University College

NorthGrid: Lancaster, Liverpool, Manchester, Sheffield

What is involved?

Each participating site is required to sign the LCG/EGEE acceptable use and security policy before joining and undertakes to meet the needs of the community. A site will typically:
  • Provide machines configured with a compatible operating system
  • Install and maintain (in a timely manner) required Grid middleware
  • Run agreed software stacks
  • Respond to Core Infrastructure Centre and Regional Operations Centre queries and requests
  • Notify the community of scheduled and unscheduled downtime
  • Actively monitor provided resources
  • Provide resources according to agreed schedules
  • Report and respond to security incidents
  • Feedback issues and coordinate work with the relevant Coordinator
  • Keep backups of log files for accounting and security purposes

The wider community

How does GridPP deployment and operations fit into wider activities?

GridPP was the response of the UK to Particle Physics computing needs beyond when the Large Hadron Collider begins operations at CERN in Switzerland (now scheduled for the end of 2009). Originally GridPP formed part of the European Data Grid (EDG) project and contributed to the evolution of the middleware and deployment of testbeds. EDG has evolved into the Enabling Grids for E-sciencE (EGEE) project and GridPP now forms a major part of the United Kingdom & Ireland (UKI) region contribution to this project. Our lead Tier-2 sites are partners in the EGEE project together with STFC and Trinity College Dublin (who represent Grid Ireland). Together we run the UKI Regional Operations Centre and contribute UKI effort to EGEE wide operations.

What is involved?

  • GridPP sites allow non-HEP use of their resources according to a GridPP VO policy and Tier-1 or Tier-2 scheduling requirements

  • GridPP deployment and operations tasks form part of EGEE deployment and operations (known as project area SA1). EGEE has the following governance and operating structures (explained in more detail on the meetings page):

     

     

  • A large part of the EGEE infrastructure comes from resources provided for the Worldwide Large Hadron Computing Grid project (WLCG). GridPP works closely with other WLCG members to ensure that LHC requirements are going to be met over the coming years. A large part of this work involves planning for and taking part in a number of service challenges and experiment data challenges. This body of work is coordinated by the Worldwide LCG Deployment Board which meets monthly and a WLCG Management Board which meets weekly.

 


Last modified Fri  6 November 2009 . View page history
Switch to HTTPS . Website Help . Print View . Built with GridSite 1.4.3
For more about GridPP please contact Neasan O'Neill