UK NGI Operations John Gordon 15 th May 2012

NGS continuation NGI Security Monitoring VOMS Helpdesk I am reacting to some issues highlighted by Jeremy on your behalf. We both apologise if anything has been lost in translation.

NGS Continuation What is the NGS? Since March 2011 the NGS has not been funded to run resources but to run a variety of e-infrastructure services for the UK. (see next slide) GridPP is one Grid that uses some of these services. Other projects will/do use different sets of these services. There is no trite definition ‘This is the NGS’, instead it is an umbrella to protect and foster many projects and communities under the UK NGI banner. This meeting (or some attendees) seems to need rigid definitions and structures. If the NGS doesn’t have these, that is your problem, not theirs. As soon as you write down ‘this is what we do’ the implication is drawn that this is all you do. The NGS wants to be flexible enough to meet as yet unknown requirements.

NGS Services Continuing with NGS and other funds: CA Infrastructure and SARoNGS (CA, CertWizard, CTS...) Training Marketplace Federated Cloud Task Force Leadership NGI-EGI International tasks Management/International engagement MEG UAS Website Helpdesk WLCG Nagios (POEM enabled) test instance Non-NGS funded services continuing: APEL GOCDB Security role VOMS - is being passed back to GridPP All other services will be assessed and if appropriate deprecated.

UK in Europe GridPP sites are well integrated in WLCG and EGI. Some other sites will follow this model and run alongside GridPP sites in the wider EGI (eg EFDA-JET). I expect them to follow the same certification, monitoring, deployment path as GridPP and to join your teams, meetings etc. Some projects may adopt a similar model but with a different middleware stack. (Arc, Unicore, Globus, whatever). EGI’s model is to integrate them alongside glite services. There are already services for them known to GOCDB, monitoring defined, and accounting in place or being developed. There is scope for some of these to interwork /integrate with GridPP (eg MAPPER, DIRAC, XSEDE) and share things like ROD but the details can’t be worked out in advance. I will follow the principle that we integrate in areas that are little work. Some projects will follow a completely different model and may only use the CA and their own distributed web services. There will be different ways of doing things.

NGI Security All NGS Sites in GOCDB have security contacts defined but are not certified so don’t get them from the main EGI list. There is an NGS-CSIRTS list which UK can use to propagate alerts etc. Will consider an NGS person on Security Team to widen the coverage. Discussions with new communities take many forms and paths. If the project wants to use the security services like the CA, etc then the security issues are explained to them through AUPs etc. Similarly sites providing resources are covered by the same policies as GridPP.

Monitoring NGS has a plan to run a nagios using POEM to define project and/or infrastructure-specific tests. This has stalled due to e-infrastructure capital installations but is still the plan. Once proven and production-ready, these tests will be moved to the UK production nagios where they can be viewed alongside the others.

VOMS The NGS UAS tool uses a VOMS client interface to populate and de-populate Vos in VOMS. Migration of NGS VOs between servers will be hidden from most (but not all) NGS users. As part of UK NGI NGS VOs should follow same EGI policies as GridPP. NGS will review all VOs before migrating.

HELPDESK Almost ready to go with proposed changes next week. New tool GGUS report generator shows performance of Support Units. E.g. response time stats for NGI_UK DateSUResponsesTicketsAverageMedian NGI_UK65 0d 0h 42min0d 0h 30min NGI_UK63 0d 0h 44min0d 0h 24min NGI_UK88 0d 1h 24min0d 0h 17min NGI_UK70 0d 1h 16min0d 0h 15min NGI_UK70 0d 1h 21min0d 0h 35min NGI_UK93920d 3h 30min0d 0h 47min

NGI_AEGIS550d 0h 57min0d 0h 43min NGI_ARMGRID20 2d 5h 12min1d 7h 1min NGI_BA220d 2h 20min NGI_BG37 3d 0h 43min0d 5h 14min NGI_BY11 4d 2h 4min5d 7h 51min NGI_CH21 5d 2h 25min0d 1h 57min NGI_CYGRID11 2d 7h 32min2d 4h 5min NGI_CZ31 1d 3h 27min0d 6h 58min NGI_DE d 5h 53min0d 0h 52min NGI_FI220d 2h 1min NGI_FRANCE d 2h 13min0d 1h 57min NGI_GE227d 7h 6min NGI_GRNET45 6d 3h 43min2d 1h 40min NGI_HR887d 5h 10min3d 5h 20min NGI_HU12 2d 1h 44min0d 2h 59min NGI_IBERGRID d 1h 20min0d 0h 44min NGI_IE14 2d 2h 5min1d 2h 1min NGI_IL57 3d 7h 37min0d 1h 51min NGI_IT d 1h 53min0d 2h 34min NGI_MARGI23 7d 5h 29min4d 7h 48min NGI_MD223d 5h 39min NGI_ME15 8d 5h 15min4d 0h 0min NGI_NDGF79 1d 1h 14min0d 2h 25min NGI_NL97 0d 5h 53min0d 0h 34min NGI_PL58 1d 4h 59min0d 1h 49min NGI_RO93923d 6h 25min2d 0h 0min NGI_SI770d 6h 3min0d 0h 13min NGI_SK330d 1h 53min0d 1h 48min NGI_TR33 0d 6h 40min0d 1h 27min NGI_UA660d 3h 10min0d 0h 53min NGI_UK d 1h 37min0d 0h 25min NGI_ZA553d 3h 18min0d 7h 4min ROC_Asia/Pacific d 0h 36min0d 2h 5min ROC_CERN d 7h 37min0d 0h 50min ROC_Canada83 1d 5h 29min0d 7h 16min ROC_IGALC58571d 6h 16min0d 7h 59min ROC_LA44 8d 7h 6min6d 7h 5min ROC_Russia76753d 7h 36min0d 2h 19min