Ops meeting minutes * This is a reminder that this is an important task. The minute taker gives access to the discussions for those not present and provides a reference for others to refer back to afterwards. * The team composition has been changing. If everybody contributes then the task comes around less often. * From the start of GridPP4+ those in fully funded GridPP positions will be expected to contribute. Others are welcome to volunteer! * The minutes should contain a list of who attended; apologies; note who took the minutes and highlight actions. * A count is maintained at https://www.gridpp.ac.uk/wiki/Operations_Team_Action_items. * After uploading minutes to the agenda page the minute taker is expected to: ** Update the list of ops actions. ** Update their 'count' so the task can be shared fairly. Thank you for your support!

Experiment problems/issues Review of weekly issues by experiment/VO - LHCb - CMS https://cms-site-readiness.web.cern.ch/cms-site-readiness/SiteReadiness/HTML/SiteReadinessReport.html#T2_UK_London_Brunel - ATLAS - Other -- Already in use -- LSST, UCLan, LIGO. - DIRAC status -- http://www.gridpp.ac.uk/php/gridpp-dirac-sam.php?action=view

Meetings & updates With reference to: http://www.gridpp.ac.uk/wiki/Operations_Bulletin_Latest - General updates - WLCG ops coordination - Tier-1 status - Storage and data management - Accounting - Documentation - Interoperation - Monitoring - On-duty - Rollout - Security - Services - Tickets - Tools - VOs - Site updates

Site roundtable - the remaining sites....or follow-up Any comments from/for: UCL; EFDA-JET; Bristol; Durham or Brunel? - Current work areas and issues by site - Multi-core: Done? Just UCL, Birmingham and Bristol without queues. 1. Hardware: https://www.gridpp.ac.uk/wiki/HEPSPEC06 2. perfSONAR: http://tinyurl.com/m3do897 3. Batch system: https://www.gridpp.ac.uk/wiki/Batch_system_status 4. VM/cloud plans 5. Network (including IPv6): https://www.gridpp.ac.uk/wiki/IPv6_site_status 6. Site priorities & issues 7. Squid in GOCDB? From our last review in December..... According to our table for cloud/VMs 26%->33% YES: RAL T1; Brunel; Imperial; Manchester; Oxford; Lancaster (5+1) PLAN: QMUL; NO: RHUL; UCL; Liverpool; Sheffield; Durham; ECDF; Glasgow; Birmingham; Bristol; Cambridge; RALPP; Sussex (14-2) GridPP DIRAC jobs successful 58%->66% YES: Bristol; Cambridge (+1); Glasgow; Lancaster; Liverpool; Manchester; Oxford; Sheffield; Brunel; IC; QMUL; RHUL (11) NO: Durham (?); RALPP; RAL T1 (3) + ECDF; Sussex; UCL; Birmingham (4) IPv6 status Allocation - 42%->50% YES: RAL T1; Brunel; IC; QMUL; Manchester; Sheffield; Cambridge; Oxford; + Glasgow (9) NO: RHUL; UCL; Lancaster; Liverpool; Durham; ECDF; Birmingham; Bristol; RALPP(in progress); Sussex Dual stack nodes - 21% -> 21% YES: Brunel; IC; QMUL; Oxford (4) NO: RHUL; UCL; Lancaster; Glasgow; Liverpool; Manchester; Sheffield; Durham; ECDF; Birmingham; Bristol; Cambridge; RALPP; Sussex, RAL T1 (15) Squids not in GOCDB for: UCL (-1); Birmingham (-1); Durham(-1); IC(-1); Sussex(-1) Squids in GOCDB for: EFDA-JET; Manchester; Liverpool; Cambridge; Sheffield; Bristol; Brunel; QMUL; T1; Oxford; Glasgow; RALPPD + ECDF; RHUL and Lancaster. 60%->75%

Middleware testing & readiness work * Which sites are supporting the work. * Current impressions * State of the nation: http://www.hep.ph.ic.ac.uk/~dbauer/grid/state_of_the_nation.html * EMI3 testing: https://www.gridpp.ac.uk/wiki/Staged_rollout_emi3 * Any further feedback on the http deployment task force proposal? https://indico.cern.ch/event/372875/contribution/5/material/slides/0.pdf.

DIRAC overview * A reminder of how it works and where we are going! * HEPSYSMAN talk:https://indico.cern.ch/event/350917/session/0/contribution/11/material/slides/0.pdf * Quick guide: https://www.gridpp.ac.uk/wiki/Quick_Guide_to_Dirac * New user checklist: https://www.gridpp.ac.uk/wiki/DIRAC_new_user_checklist * GitHub docs: ** https://github.com/gridpp/dirac-getting-started ** https://github.com/gridpp/dirac-getting-started/wiki

AOB - CERN accounts. JC will circulate next steps this week. - Proposed next core ops meeting: Thursday 12th. 11:00 or 14:00?