ROC Managers' Meeting

→ Europe/Zurich
CERN

CERN

Alistair Mills, Nick Thackray
Description
Actions, https://edms.cern.ch/document/753089 Minutes, https://edms.cern.ch/document/829338 This meeting is 10:00 to 11:30 UTC (11:00 to 12:30 Swiss local time). Phone number is: +41 22 767 6000 Access code is: 0147097 Or click here: https://audioconf.cern.ch/call/0147097 The conference call opens 5 minutes before the meeting starts. The rota for minute takers can be found here: http://egee-docs.web.cern.ch/egee-docs/roc_managers/meetings/ROC%20managers%20meeting%20minutes%20-%20rota.pdf
Recording of the meeting
    • 11:00 → 12:30
      ROC Managers' Meeting
      • 11:00
        Admin matters 5m
      • Quarterly Report
      • Meetings
      • Milestones
      • Deliverables
      • Moderators
      Speaker: Alistair Mills
      more information
  • 11:00
    Comments on minutes of the last meeting 1m
  • 11:05
    GGUS reports 10m
    Speakers: Alistair Mills, Maria Dimou
    • TPM Monitoring
      more information
    • GGUS ticket escalation report
      At the meeting all ROCs will be asked to explain what is the status of all tickets which
      have an Inactivity Index > 50
      more information
  • 11:15
    Response to JRA1: Collecting missing/broken CLI middleware commands 10m
    AIm: To identify who will work on this and set a target date.
  • 11:25
    Organization of Top level BDIIs 10m
    • Waiting for input from SE Europe.
    • Should it be one end point per region?
    • Current status in attached file
    more information
  • 11:35
    Review by ROC of site not publishing accounting data 10m
    text
  • 11:45
    New reporting schedule for Grid Operations Meetings 10m
    In order to improve the efficacy of the weekly Joint Grid Operations meeting I’d like to propose a change to the ROC reporting windows. Currently the sites can fill their reports continuously during the week and then ROCs have a window from Saturday at 06:00 (UTC) until Monday 12:00 (UTC) to fill their reports. This leaves only 2-3 hours (depending on time of year) for the preparation of the operations meeting which is simply insufficient time to create the agenda, contact all the necessary people for the issues being raised and give the attendees sufficient time to understand (or even know about) the issues that will be raised at the meeting. This drastically reduces the utility of the meeting. I would like to ask that we move the reporting window for the ROCs (and the VOs) so that it finishes on Friday at 08:00 (UTC). This then gives 1.5 working days to prepare the meeting. I would suggest that the ROCs shouldn’t need a lot of time (<1 day?) to complete their reports.
  • 11:55
    How to deal with 'inappropriate' jobs 15m
    Recently there have been a couple of issues with users running jobs which did not fall within the scope of the work of VO (as described in the VO's AUP). It highlighted that we don't have a procedure to deal with this - it's not considered to be a security incident. Questions arising:
    1. Do VOs make it clear to their users what work is acceptable to run?
    2. Do users accept this? If not why should sites trust the VO?
    3. Do VOs know what their users are doing? And do they care? And will they take action against the users when they become aware of unsuitable use?
  • 12:10
    Review of action items 10m
  • 12:20
    AOB 5m
    • Request for ROCs to suggest to their sites to use Nagios for site monitoring, taking advantage of the work being done in the Monitoring working group.
    • CA update procedure: call for volunteer to propose an updated procedure