Core operations team - F2F - core tasks

Friday 11 Nov 2011, 09:30 → 16:00 Europe/London

EVO - GridPP Operations team meeting

- This is a special face to face meeting for the core ops team. It will take place in QMUL ( GO Jones (physics) Room 410 ). - The intention is to have an EVO connection: http://evo.caltech.edu/evoGate/. Join the meeting in the GridPP Community area. The EVO connection is: http://evo.caltech.edu/evoNext/koala.jnlp?meeting=MeMMMu2v2uD8DB929lDv9e - The phone bridge number is +44 (0)161 306 6802 (CERN number +41 22 76 71400). The phone bridge ID is 4282778 with code: 2688. Apologies:

1 Introduction & objectives

https://www.gridpp.ac.uk/wiki/Category:GridPP_Operations

Slides Core-tasks.pdf Core-tasks.ppt

2 Wider VOs

3 Documentation

https://www.gridpp.ac.uk/wiki/Documentation

4 Accounting

https://www.gridpp.ac.uk/wiki/Accounting The Ops-Team helps the UK sites to publish the correct accounting information by leading benchmarking activities and performing checks on the published data.

5 Regional tools

https://www.gridpp.ac.uk/wiki/Category:GridPP_Operations Tools such as Site Availability Monitoring (SAM) servers coupled with Nagios probes; a regional dashboard; and instances of the APEL accounting and Grid Operations databases, have been devolved to the regions in the move towards the EGI/NGI model. These tools provide monitoring, accounting and coordination at a national level. The Ops-Team ensures that these tools are deployed and individual members are experts who track technical developments and represent the UK in international discussions.

6 Monitoring

https://www.gridpp.ac.uk/wiki/Monitoring The Ops-Team oversees the deployment of the increasing suite of Grid monitoring tools and helps sys-admins find, customise and interpret information relevant to their own sites.

7 LUNCH

8 Security

https://www.gridpp.ac.uk/wiki/Security

9 Core services (... or On-duty if time)

10 Ticket follow-up

https://www.gridpp.ac.uk/wiki/Ticket_follow-up Tickets may be raised by users via their VOs, from the on-duty team as described above, or from site-administrators experiencing problems with the middleware or infrastructure. Tickets may need to be forwarded through several interfaced ticketing systems to arrive at the appropriate expert and, once there, additional information if often required. The Ops-Team ensures that tickets are followed-up by facilitating communication; providing advice on the next step; and ensuring that tickets do not stagnate in the system.

11 Staged rollout

https://www.gridpp.ac.uk/wiki/Staged_rollout The Grid is based on well-defined middleware components that are periodically updated with new functionality, security patches and bug fixes. Although verified at the developer-level, the UK needs to contribute to the worldwide rollout process that requires site-testing and feedback. The GridPP operations team (Ops-Team) must coordinate the certification of all releases in the UK context before rolling out to all UK sites.

12 Grid interoperation

https://www.gridpp.ac.uk/wiki/Grid_interoperation Otherwise known as working with other grids. The ops-team need to remain aware of and contribute to developments in the NGI/NGS, in EGI and so on. This task is about how we work with those other grids and knowing for example what is required in the wider context.

Slides GridInteropQMUL.pdf

13 Review & conclusions