Setting up NGI operations Ron Trompert EGI-InSPIRE – ROD teams workshop1

Outline What is an NGI? What is expected of NGIs? –NGI national tasks NGI operations in Turkey NGI operations in Germany

What is an NGI? NGI stands for “National Grid Initiative”, but how national is an NGI? –There are countries where there is a 1 to 1 mapping between the EGI partner and the GOCdb –But…the Spanish and Portuguese NGI are called CSIC and UMIC but IBERGRID is in the GOCdb and UMIC and CSIC not –There are a number of NGIs in Scandinavia but a ROD team from NDGF will do monitoring of sites and NGI_NDGF will be in the GOCdb

What is an NGI? In the context of ROD work a “NGI” is an entity known in the EGI infrastructure (GGUS, GOCdb,..) which supplies a ROD team monitoring sites in the region covered by that NGI, operates a nagios box which enables them to do this etc.

NGI national tasks O-N-1 –Operation of the Grid topology and configuration repositories –Involves interfacing of local topology and configuration databases with the GOCdb O-N-2 –Operation of accounting repositories for international VOs –Involves making accounting data available

NGI national tasks O-N-3 –Operation of Grid repositories storing monitoring and performance data and other related information O-N-4 –Operation of the Grid Operations Portals

NGI national tasks O-N-5 –Grid operation and oversight of the e- Infrastructure O-N-6 – Operation of the NGI ticketing system, gathering of new requirements for support tools in the region

NGI national tasks O-N-7 –Regional helpdesk: support to users and site managers via a local/regional helpdesk and documentation O-N-8 –Operation of production grid core software services

NGI national tasks O-N-9 –Operations coordination at the NGI level Security and incident response coordination in the region Roll out of middleware updates in the NGI Resource allocation in the NGI Interoperation with national and regional Grids

NGI national tasks What does this mean for the work of the ROD team in practice?

NGI e-Infrastructure oversight Establishing a ROD team that will fulfill their duty as described in the operational documentation. Make sure that their ROD team is adequately staffed and trained. The ROD team member should be acquainted with the operational procedures and be able to operate the operational tools. Ensure that the necessary operational tools are available and operational. This may be by, for example, establishing a regional view on a central instance or by running a local instance themselves. Run a regional nagios instance for the monitoring the sites in their region. The ROD team should actively participate in conferences and meetings. The ROD team should provide input for the operational, best practices and training documentation effort.

NGI e-Infrastructure oversight Ensure that the necessary operational tools are available and operational. This may be by, for example, establishing a regional view on a central instance or by running a local instance. Run a regional nagios instance for the monitoring the sites in their region.

NGI e-Infrastructure oversight The ROD team should actively participate in conferences and meetings. The ROD team should provide input for the operational, best practices and training documentation effort.

NGI e-Infrastructure oversight 1 st line support –When an alarm is triggered in the dashboard, there should be a GGUS ticket raised to the site when the alarm is still there after 24 hours –This 24 hours may be used for a NGI 1 st line support team to get into contact with the site to resolve the issue.

Belgium and the Netherlands in EGI Ron Trompert EGI-InSPIRE – ROD teams workshop15

Belgium and the Netherlands Two NGIs –BEgrid (Belgium) 3 sites in the EGI production infrastructure Universities of Brussels, Leuven, Louvain-La- Neuve Represented in the EGI council but does not take part in EGI InSPIRE –BigGrid, a.k.a NCF (Netherlands) 15 sites in the EGI production infratsructure SARA, NIKHEF, University in Groningen, PHILIPS, Life Sciences Grid (several universities and KeyGene)

Belgium and the Netherlands BEgrid and BigGrid will continue to cooperate until at least one year after EGI has started. –BiGGrid will perform the NGI local tasks on behalf of Belgium and the Netherlands BigGrid is going through the process of setting up the NGI

Belgium and the Netherlands User support –Helpdesk Both BigGrid have a helpdesk but they do not interface with GGUS. We do not intend to do that in the future. Use GGUS directly Users from VOs based in the Netherlands contact the helpdesk of SARA or NIKHEF directly or can contact the BigGrid Helpdesk Users from international VOs contact us the same way or though GGUS

BigGrid BigGrid’s effort in EGI InSPIRE

BigGrid Operations people of the sites meet every three weeks –Security issues –Resource allocation –Middleware updates –Roll out of new middleware

BigGrid Accounting database –Sites are still publishing accounting data through R-GMA –Setting up an own NGI accounting database is in progress

BigGrid Operation of tools –GOCDB The GOCDB setup as it is at the moment works fine for us. –Nagios We have setup a NE-ROC nagios box Currently setting up a NGI_NL Nagios box

BigGrid Operation of tools –Dashboard We use the regional view on the central CiC portal instance. This works fine for us.

BigGrid E-Infrastructure Oversight –ROD team consisting of 5 people, all at SARA –Every ROD member takes weekly shifts –COD duty in a weekly rota shared between Poland and The Netherlands. In the Netherlands, the ROD team member on duty also takes on the COD task –1st line support at a very low level

BigGrid Helpdesk –BigGrid has its -based support address In practice, however, almost all dutch users contact the support addresses of NIKHEF and SARA directly with general grid-related –Currently, we are investigating other trouble ticket systems. –This trouble ticket system will not interface with GGUS and GGUS will be used directly –Daily rotating shift involving 13 people.

BigGrid Services –VOMS For ESR and national VOs –Global LFC For ESR, pheno and national VOs –Local LFC For ATLAS and LHCb –VOBOX For ATLAS, LHCb and ALICE –FTS For ATLAS, LHCb