Preparing Waiting Room and Morgue Tables

Introduction

In this page, we explain how to prepare the waiting room (WR) and morgue tables for the Site Support and Infrastructure meeting page. We highly recommend you to read Waiting Room Morgue And Site Readiness page before reading this page.

Steps

  1. Open the site status board
  2. To detect site movements, check all sites in the WR and morgue and compare them with sites in the WR and morgue tables
  3. If you see a new site is in the WR:
    • Check the site history in the site readiness report and decide whether it needs to be moved into the WR (we will explain later why you should be skeptical)
    • If you think that this site must be moved into the WR;
    • Open a GGUS ticket and inform the site admin that you moved his site into the WR. Please also give him a summary about the problems
      • Subject: T2_XY_ABC was moved into the waiting room
      • Type of issue: CMS_Facilities
      • Notify CMS SITE: select the site name
    • After opening the GGUS ticket, create a row for the site and in this row:
    • CompOps people may want to see summary of the problem(s) in the site so state details for SAM Exit Code, HC Exit Code and Link Problems (please notice the table headers in the meeting page)
    • You should also state general site resources, Disk pledge (TB) and Real Cores. Last thing you should do is to state ticket number and its link
  4. If you see a site is out of the WR:
    • Check the site readiness report for the site and have a look at the site history there
    • The reason why we need to check the site history in the site readiness report is to be sure that the site is really OUT
    • If you notice, we started using fuzzy statements. Waiting room and morgue controller script is not enough to classify site states (IN/OUT) so we need to check status of sites manually (in many cases, it is enough but it is better to check one more time)
    • If the site is really OUT, mark this site as OUT in the meeting page/WR table (Next week, you will need to delete this row from the table)
    • Go to the announcement ticket and mark it as solved
  5. If you see a new site is in the morgue:
    • You should keep in mind that it is impossible to be in the morgue without being in the waiting room (please remember the conditions that are explained in the Waiting Room Morgue And Site Readiness page). So that means this site is in the waiting room and we need to move it from the waiting room to the morgue
    • After checking the history of the site, you need to inform site admin. Go to the ticket, which is opened for the WR announcement, and inform site admin
    • Now, all you need to do is to move the table row from the WR table to the morgue table in the meeting page
  6. If you see a site is out of the morgue:
    • Wait, do not announce it yet! First, you need to wait one or two weeks to see that the site is really stable
    • If site is still doing good, contact Workflow Team (cms-comp-ops-workflow-team@cernNOSPAMPLEASE.ch) and ask them to send some test workflows there
    • If you get successful results from the Workflow Team, you can move this site out of the morgue
    • --but please, also consider the history of the site. For some sites, which have chronic problems, you may need to wait more before announcing that the site is OUT
Edit | Attach | Watch | Print version | History: r2 < r1 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r2 - 2016-07-22 - StephanLammel
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    CMSPublic All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback