ROC Managers' Meeting <big>(Note the change of date)</big>

→ Europe/Zurich
CERN

CERN

Alistair Mills, Nick Thackray
Description
Actions, https://edms.cern.ch/document/893956 Minutes, https://edms.cern.ch/document/893655 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 taking the minutes can be found here: ROTA
    • 11:00 → 12:30
      ROC Managers' Meeting
      • 11:00
        Admin matters 10m
      • Quarterly Report
      • Meetings
      • Milestones
      • Deliverables
      • Moderators
      Speaker: Alistair Mills
      document
      Notes for Lyon in February
  • 11:00
    Comments on minutes of the last meeting 1m
  • 11:10
    GGUS reports 15m
    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


      Update from UK/I:
      27468: I have closed this today, it is solved.
      28940: I have closed this ticket today.
      28998: Has been closed today.
      29397: In progress, changes to website pages.
      more information
  • 11:25
    CA Update procedure 5m
  • 11:30
    Roll-out of SA1 SLD 5m
    In the latest iSGTW there is an article about the SLD (http://www.isgtw.org/?pid=1000798). It states (quote from Ian): "ROCs are now being encouraged to start the process of signing agreements with their sites." So let's start!
  • 11:35
    Collecting missing/broken CLI middleware commands 10m
  • 11:45
    Review of sites not publishing accounting data 10m
    From UK/I:
    Tickets raised for:
    cpDIASie
    csTCDie
    giHECie
    mpUCDie
    ScotGRID-Edinburgh
    UKI-LT2-RHUL
    UKI-NORTHGRID-LIV-HEP
    UKI-SCOTGRID-DURHAM
    UKI-SOUTHGRID-OX-HEP
  • 11:55
    Regional top-level BDIIs: Review on status 5m
  • 12:00
    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:15
    Review of action items 10m
  • 12:25
    AOB 5m