Operations Bulletin 040213

From GridPP Wiki
Jump to: navigation, search

Bulletin archive


Week commencing 28th January 2013
Task Areas
General updates

  • The monitoring links page has been updated.

Tuesday 29th January

  • A reminder that this week represents the standard cut-off for migration away from gLite.
  • Also a reminder that the daily WLCG operations meeting notes are available online. Useful to get an up-to-date and broad picture of WLCG activity.
  • ATLAS have a timeout issues with lcg_util and/or GFAL commands. This is fixed in EMI-2 Update 8 released on Jan 28. ATLAS supporting sites are requested to update as soon as possible.
  • We will in coming weeks revisit information publishing. Please check your site data in gstat2.
  • A proposal has been discussed by the WLCG MB to remove OPS VO testing from monthly WLCG reporting and to replace with separate reports for each LHC VO. (Ops tests will continue but not form part of the reporting).
  • Other MB news: Helge Meinhard claimed that for most people the migration to SL6 will be seen to happen when the alias for LXPLUS moves from SLC5 to SLC6. The proposed timetable is to move the default login for LXPLUS to SLC6 at the end of April 2013, but SLC5 will continue to be available after that date.


Monday 21st January

  • A permanent nagios probe working group will be created under coordination of COD. The objectives are to evaluate existing current nagios probes starting from known problem areas; evaluate new probes before integration within SAM and propose to the EGI OMB probes to be integrated/rejected. If you would like to be involved speak to Jeremy.
  • Moving tickets to 'in-progress' and the status of re-opened tickets.
  • Posters and demonstrations submissions/proposals for the EGI CF: 27 January 2013
  • EGI request for an NGI core services 'Service Group'.
  • Last Tuesday there was a pre-GDB on operations topics. See the talks on the agenda for more information. Will cover some areas under relevant bulletin updates.
  • The WLCG T2 availability/reliability report is now final.
  • EGI now host a middleware support calendar. For EMI-1 probes will warn from January and go critical in March. Deadline end of April.
  • There is now an inter-NGI resource consumption report
  • The next WLCG Operations Coordination meeting takes place on 24th (agenda)
  • Middleware configuration post-EMI will be the subject of a survey to be circulated soon.
  • EGI calls for more participation in its Resource Allocation task force. The idea is to make more resources available (for a testbed in the first instance) to help smaller VOs get access to resources.


Tier-1 - Status Page

Tuesday 29th January

  • Roll-out of new version of Top BDII under way (EMI2 on SL6).
  • Participating in Atlas FAX (Federated Atlas Xrootd) tests.
  • CVMFS for minor VOs deployed on batch farm (Thursday 24th Jan)
  • The work on the power supply to site which has been ongoing for many months was completed on Monday (28th Jan).
  • Test instance of FTS version 3 being tested by Atlas & CMS.
Storage & Data Management - Agendas/Minutes

Wednesday 23 jan

  • Storage Federations
    • See slides on [[1][storage meeting agenda]] for details.
    • ATLAS and CMS both pushing ahead with xrootd based requirements.
    • (whether they are) Benefits still to be seen.
    • UK in good shape on this with many sites in ATLAS "FAX" federation. And the big CMS sites in their one too.


Accounting - UK Grid Metrics HEPSPEC06 Atlas Dashboard HS06

Tuesday 30th October

  • Storage availability in SL pages has been affected by a number of sites being asked by ATLAS to retire the ATLASGROUPDISK space token while the SUM tests were still testing it as critical. The availability will be corrected manually once the month ends. Sites affected in different degrees are RHUL, CAM, BHAM, SHEF and MAN.

Friday 28th September

  • Tier-2 pledges to WLCG will be made shortly. The situation is fine unless there are significant equipment retirements coming up.
  • See Steve Lloyd's GridPP29 talk for the latest on the GridPP accounting.

Wednesday 6th September

  • Sites should check the atlas page reporting HS06 coefficient because according to the latest statement from Steve that is what it's going to be used Atlas Dashboard coefficients are averages over time.

I am going to suggest using the ATLAS production and analysis numbers given in hs06 directly rather than use cpu secs and try and convert them ourselves as we have been doing. There doesn't seem to be any robust way of doing it any more and so we may as well use ATLAS numbers which are the ones they are checking against pledges etc anyway. If the conversion factors are wrong then we should get them fixed in our BDIIs. No doubt there will be a lively debate at GridPP29!

Documentation - KeyDocs

See the worst KeyDocs list for documents needing review now and the names of the responsible people.

Tuesday 29th January

KeyDocs monitoring status: Grid Storage(7/0) Documentation(3/0) On-duty coordination(3/0) Staged rollout(3/0) Ticket follow-up(3/0) Regional tools(3/0) Security(3/0) Monitoring(3/0) Accounting(3/0) Core Grid services(3/0) Wider VO issues(3/0) Grid interoperation(3/0) Cluster Management(1/0) (brackets show total/missing)

Thursday, 29th November

The Approved VOs document has been updated to automatically contain a table that lays out the resource requirements for each VO, as well as the maximum. We need to discuss whether this is useful - it seems that the majority of WN software requirements are passed around by word of mouth etc. Should this be formalized? Please see 

   https://www.gridpp.ac.uk/wiki/GridPP_approved_VOs#VO_Resource_Requirements

This table will be kept up to date with a regular process that syncs it with the CIC Portal, should it prove to be useful.


Tuesday 6th November

  • Do we need the Approved VOs document the set out the software needs for the VOs?

Tuesday 23rd October

KeyDocs monitoring status: Grid Storage(7/0) Documentation(3/0) On-duty coordination(3/0) Staged rollout(3/0) Ticket follow-up(3/0) Regional tools(3/0) Security(3/0) Monitoring(3/0) Accounting(3/0) Core Grid services(3/0) Wider VO issues(3/0) Grid interoperation(3/0) Cluster Management(1/0) (brackets show total/missing)

Thursday 26th July

All the "site update pages" have been reconfigured from a topic oriented structure into a site oriented structure. This is available to view at https://www.gridpp.ac.uk/wiki/Separate_Site_Status_Pages#Site_Specific_Pages

Please do not edit these pages yet - any changes would be lost when we refine the template. Any comments gratefully received, contact: sjones@hep.ph.liv.ac.uk

Interoperation - EGI ops agendas

Monday 28th January

  • There was an EGI ops [ https://wiki.egi.eu/wiki/Agenda-28-01-2013 meeting] yesterday.
  • EMI release: DPM 1.8.6 (Small update with security fixes) and VOMS 2.0.10-1 (Small update with security fixes)
  • EMI3 due in April. Looking for SR sites.
  • For UMD-2, CREAM is released to production, WMS had problems found.
  • CA update 1.52-1 under SR, release expected 30-01-2013 (so get ready to update the CA certs...), and SAM-Update 20


Monitoring - Links MyWLCG

Monday 2nd July

  • DC has almost finished an initial ranking. This will be reviewed by AF/JC and discussed at 10th July ops meeting

Wednesday 6th June

  • Ranking continues. Plan to have a meeting in July to discuss good approaches to the plethora of monitoring available.
  • Glasgow dashboard now packaged and can be downloaded here.
On-duty - Dashboard ROD rota

Monday 21st January

  • Good week, with only a few downtimes and long lived alarms. All outstanding alarms are covered by tickets as of now.
  • As summarised in Daniela's handover from last week, several sites have red COD-level status because the tickets are more than a month old. This due to the lack of upgrade of the WNs due to lack of the new tar-balls, and results in raising sec alarms. Some details in this ticket: https://ggus.eu/ws/ticket_info.php?ticket=90184

Tuesday 15th January

  • Main issue relates to COD tickets as mentioned last week.

Monday 7th January

  • Several sites are in the red due to the middleware tickets being older than 30 days. We got a COD ticket for this despite the ticket being filed as a top priority, COD did not answer so I reset the priority to something sensible. We aren't the only ones hit by this problem.
  • At the moment the security alerts don't seem to update on the dashboard - at least ceprod08 has not cleared all day.
Rollout Status WLCG Baseline

Tuesday 21st January

References


Security - Incident Procedure Policies Rota

Monday 21st January

  • SHA-2 and glexec updates given at pre-GDB.
  • EUGridPMA agreed on timeline where SHA-2 becomes the default in August 2013. SHA-1 will still be requestable.

Tuesday 15th January

  • There has been a recent java patch. Sites should consider to roll out updates to client machines (especially those containing user certificates). The most current version is "Version 7 Update 11".


Services - PerfSonar dashboard | GridPP VOMS

Tuesday 22nd January

  • VOMS changes
  • There was an LHCONE P2P workshop in December (summary). Do we have coverage?

Tuesday 20th November

  • Reminder for sites to add perfSONAR services in GOCDB.
  • VOMS upgraded at Manchester. No reported problems. Next step to do the replication to Oxford/Imperial.
Tickets

Monday 28th January 2013 14.30 GMT</br> 49 Open UK tickets today. We're slowly whittling them down. Most are being kept well in hand though.

Time Frames:</br> There's been some discussion concerning the Time Frames for sites getting their tickets "poked" whilst in various states. The first pass of these looked like: 

   * Ticket looks finished/closed [1 or maybe 2 days]
   * Ticket is assigned but not set to "in progress" by assignees [1 or maybe 2 days - send poke to them]
   * No progress on ticket for > 3 days - send poke

What we want to have is usefully timed reminders, not nagging, so I'll ask what you guys think of this tomorrow.

Security Tickets:</br> These are getting quite urgent, although tarball sites (ECDF) probably will get a reprieve. Durham and Glasgow are a little worrying, do you guys have a plan?

The ATLAS space token tickets seem to have stalled, and with Brian heading to the other side of the world for a month there might not be much progress on them.

  • NGI</br>

https://ggus.eu/ws/ticket_info.php?ticket=90451 (15/1)</br> Ticket for the grouping of core ngi services. JK has posed a question as to who it should be assigned to (I reckon gridpp-ops). In progress (28/1)

  • Tier 1</br>

https://ggus.eu/ws/ticket_info.php?ticket=90528 (17/1)</br> Sno+ have got back concerning this ticket about their jobs not being submitted to Sheffield, they see one WMS behaving (lcgwms03) and another not (lcgwms02). In progress (23/1)

https://ggus.eu/ws/ticket_info.php?ticket=90151 (8/1)</br> The neiss VO has been enabled on the RAL WMSes, Catalin has requested that they get tested. Waiting for reply (24/1)

  • Sussex</br>

https://ggus.eu/ws/ticket_info.php?ticket=90518 (17/1) One of a few tickets affecting Sussex, has there been a chance for the "big sort out" in the last week? Stuart has extended the ticket. In progress (17/1)

  • Glasgow</br>

https://ggus.eu/ws/ticket_info.php?ticket=90386 (14/1)</br> enmr.eu problems at Glasgow. If you chaps are waiting on your new Argus server could this ticket be On Held? Depends on the timeframe for the deployment. (similar for https://ggus.eu/ws/ticket_info.php?ticket=90362)

  • Durham</br>

https://ggus.eu/ws/ticket_info.php?ticket=90340 (12/1)</br> This lhcb ticket is looking very neglected. In progress (14/1)

Tools - MyEGI Nagios

Tuesday 13th November

  • Noticed two issues during tier1 powercut. SRM and direct cream submission uses top bdii defined in Nagios configuration to query about the resource. These tests started to fail because of RAL top BDII being not accessible. It doesn't use BDII_LIST so I can not define more than one BDII. I am looking into that how to make it more robust.
  • Nagios web interface was not accessible to few users because of GOCDB being down. It is a bug in SAM-nagios and I have opened a ticket.

Availability of sites have not been affected due to this issue because Nagios sends a warning alert in case of not being able to find resource through BDII.


VOs - GridPP VOMS VO IDs Approved VO table

Monday 14 January 2012

  • Neiss.org.uk
    • Now have VO-ID card in operations-portal (previously CIC portal)
    • GridPP/NGS VOMSs server issues
    • NGS WMS hadn't enabled current CEs at QMUL and Lancs, so I've requested the GridPP WMSs enable it - as the VO is supported on GridPP sites.
    • Would be a good use case for SARONGS - but they don't have the time to debug this.


Tuesday 9 January 2012

  • Please can VOs report publications (there's now a section on the Quarterly report for them)
  • Spring Cleaning of VO support
    • GridPP VOMS server support - affects ngs.ac.uk and neiss.org.uk - expect tickets soon.
    • Removal of VOs no longer in use - totalep and some others.
  • Neiss.org.uk: NGS WMS hasn't enabled QMUL and Lancs CEs. Should we support it on the GridPP WMSs
  • T2k FTS transfers slowed due to copying files that already exist - T2k script now more robust.

Mon 17th December

Tue 4th December

Thursday 29 November

Tuesday 27 November

  • VOs supported at sites page updated
    • now lists number of sites supporting a VO, and number of VOs supported by a site.
    • Linked to by Steve Lloyd's pages


Tuesday 23 October

  • A local user is wanting to get on the grid and wants to set up his own UI. Do we have instructions?


Site Updates

Tuesday 22nd January

  • Site updates at Tuesday's meeting.


Meeting Summaries
Project Management Board - MembersMinutes Quarterly Reports

Monday 1st October

  • ELC work


Tuesday 25th September

  • Reviewing pledges.
  • Q2 2012 review
  • Clouds and DIRAC
GridPP ops meeting - Agendas Actions Core Tasks

Tuesday 21st August - link Agenda Minutes

  • TBC


RAL Tier-1 Experiment Liaison Meeting (Wednesday 13:30) Agenda EVO meeting

Wednesday 23rd January

  • Operations report
  • Problem of CRL updates at CERN on Saturday (19 Jan) caused problems for our services.
  • There was a presentation about Castor 2.1.13 - both what is in this upgrade and initial plans for roll-out.
  • The first SL6/EMI-2 Top-BDII node is now in production. This is the start of a transparent rolling upgrade to the Top-BDII.
  • Test with FTS3 are ongoing.
  • The Tier1 team is checking whether any VO requires the AFS client on the worker nodes.
WLCG Grid Deployment Board - Agendas MB agendas

October meeting Wednesday 10th October




NGI UK - Homepage CA

Wednesday 22nd August

  • Operationally few changes - VOMS and Nagios changes on hold due to holidays
  • Upcoming meetings Digital Research 2012 and the EGI Technical Forum. UK NGI presence at both.
  • The NGS is rebranding to NES (National e-Infrastructure Service)
  • EGI is looking at options to become a European Research Infrastructure Consortium (ERIC). (Background document.
  • Next meeting is on Friday 14th September at 13:00.
Events

WLCG workshop - 19th-20th May (NY) Information

CHEP 2012 - 21st-25th May (NY) Agenda

GridPP29 - 26th-27th September (Oxford)

UK ATLAS - Shifter view News & Links

Thursday 21st June

  • Over the last few months ATLAS have been testing their job recovery mechanism at RAL and a few other sites. This is something that was 'implemented' before but never really worked properly. It now appears to be working well and saving allowing jobs to finish even if the SE is not up/unstable when the job finishes.
  • Job recovery works by writing the output of the job to a directory on the WN should it fail when writing the output to the SE. Subsequent pilots will check this directory and try again for a period of 3 hours. If you would like to have job recovery activated at your site you need to create a directory which (atlas) jobs can write too. I would also suggest that this directory has some form of tmp watch enabled on it which clears up files and directories older than 48 hours. Evidence from RAL suggest that its normally only 1 or 2 jobs that are ever written to the space at a time and the space is normally less than a GB. I have not observed more than 10GB being used. Once you have created this space if you can email atlas-support-cloud-uk at cern.ch with the directory (and your site!) and we can add it to the ATLAS configurations. We can switch off job recovery at any time if it does cause a problem at your site. Job recovery would only be used for production jobs as users complain if they have to wait a few hours for things to retry (even if it would save them time overall...)
UK CMS

Tuesday 24th April

  • Brunel will be trialling CVMFS this week, will be interesting. RALPP doing OK with it.
UK LHCb

Tuesday 24th April

  • Things are running smoothly. We are going to run a few small scale tests of new codes. This will also run at T2, one UK T2 involved. Then we will soon launch new reprocessing of all data from this year. CVMFS update from last week; fixes cache corruption on WNs.
UK OTHER
  • N/A
To note

  • N/A



Retrieved from "https://www.gridpp.ac.uk/w/index.php?title=Operations_Bulletin_040213&oldid=3457"