GridPP Deployment: Troubleshooting

Please note: this page is still under construction.

Troubleshooting an LCG Site

CIC-on-duty

  • CIC notices at problem with a UK/I site.
  • They:
    1. open an internal (CIC) Savannah report;
    2. email the site directly using the support address in the GOC DB;
    3. email to UK/I ROC (?)
    NB. (3) may be automated in future?
  • UK/I ROC opens a Footprints report for the bug and assigns to a member of the UK/I ROC responsible for the site
  • (i.e. the relevant T2 Co-ordinator) Question: who at the UK/I ROC (a) receives email from (iii) and (b) is responsible for opening and assigning Footprints report? NB. hopefully this is automated!
  • Combination of site admin and UK/I ROC responsible fix problem through variety of means
  • UK/I ROC responsible closes Footprints report with statement of action taken.
  • UK/I ROC responsible emails CIC to report action taken.
  • Question: who/how is this supposed to happen? Is it the project-egee-sa1-followup@cern.ch mailing list? NB. This may be automated in future?
  • If after further tests by CIC problem does appear resolved, CIC closes internal (CIC) Savannah report.


Last modified Thu 24 February 2005 . View page history
Switch to HTTPS . Website Help . Print View . Built with GridSite 1.4.3
For more about GridPP please contact Neasan O'Neill