Difference: ATLASADCoSShiftDiary (14 vs. 15)

Revision 152010-06-23 - ChrisCollins

Line: 1 to 1

META TOPICPARENT	name="WebHome"

ADCoS shift summary

Line: 6 to 6

See at the bottom of the page for general conclusions.

Added:

>
>

Before Your Shift

To book your shifts, you need to use the Operation Task Planner (OTP)

- if you don't have the option to book ADCoS shifts, then contact Xavier, and he should be able to sort you out. You'll all be glad to know that,as Graeme said, I ran my shift from 9-5 rather than 8-4, and nobody complained (in fact, the expert did his shift 9-4:30 - so even if you want to run by CERN time, that still gives you an extra hour in bed. But Graeme said that it's fine to run it 9-5 by your own time zone.

You can see who is supposed to be on shift:

Line: 25 to 26

a GGUS account (to open TEAM tickets) - which you need log in to using your grid certificate - (grid certificate something.p12 HAS to be imported into your web-browser!)
an ATLAS eLog account - try to log in at: https://prod-grid-logger.cern.ch/elog/ATLAS+Computer+Operations+Logbook/

Added:

>
>

Finally, Savannah:

Check you can log in to Savannah - you may have to raise a bug at some point or search it for other bugs! https://savannah.cern.ch

Starting Your Shift

So, starting your shift: Bear in mind, if you are "senior shifter" you will have to submit a shift report https://twiki.cern.ch/twiki/bin/view/Atlas/ADCoS#Daily_SHIFT_report.

Added:

>
> Even if you are doing a 'Trainee' shift, you should still read the previous shift report- it will tell you what's outstanding and urgent! Go to this page and sort it by "LAST MODIFIED": http://lhcweb01.pic.es/atlas/Shift_Summaries/reports/.

First, open the ADCoS TWiki

, and go to the Checklist

for things to do. Out of the list of links they ask you to open in your browser, I only really looked at the Production Dashboard

, Production (PANDA)

, the DDM Dashboard

and the ADC eLog

. As the checklist says, switch to the cloud view on the Dashboards. Note that of those four, all refresh automatically (with LARGE delays and possible problems!-see later) apart from the ADC eLog. However, every time a new eLog entry is created, you'll get an e-mail, so there's not much to worry about there (TURN OFF your email filter if you have it switched on normally!).

Once you have all the windows open, probably best to check the eLog and previous shift summary (there will be a list of hot issues!) You may also find it useful to have a window open with your 'shifts' emails right by the browser.

Added:

>
>

Frozen URL's - CAREFUL

I always RIGHT-CLICK to open a new tab/window when I am drilling down from one of the main screens. This is because, if you hit 'back' you mostly will end up with a FROZEN URL which will never update... please read on!

ChrisCT got a reply from Graeme: apparently the dashboards do not really update very well at all- be careful! - If you go in to the cloud view and get a url like
http://dashb-atlas-prodsys.cern.ch/dashboard/request.py/overview?grouping=cloud&start-date=2009-11-11%2000:00:00&end-date=2009-11-11%2012:59:59&grouping=cloud
as opposed to:

Line: 47 to 58

In the ADC monitoring window https://sls.cern.ch/sls/service.php?id=ADC_CS if all is not green, the expert (Graeme) should be notified.

Added:

>
>

Changed:

<
< Also have a look at the sheduled downtime for sites here: https://atlas-install.roma1.infn.it/atlas_install/list.php?sitename=AGLT2 or here :https://twiki.cern.ch/twiki///bin/view/Atlas/AtlasGridDowntime. (NB: at the last link, you can import the downtime in to your "Google Calendar" - go on, it's easy to remove when you're not on shift!). If you do raise GGUS tickets, check downtime. GGUS tickets are mainly for SITE problems. Other things (like datasets not being found because they weren't made properly) don't need GGUS tickets.

>
>

Also have a look at the sheduled downtime for sites here: https://goc.gridops.org/downtime?scope=ALL

<--https://atlas-install.roma1.infn.it/atlas_install/list.php?sitename=AGLT2 
-->

or here: https://twiki.cern.ch/twiki///bin/view/Atlas/AtlasGridDowntime

. (NB: at the bottom right of the image showing the calendar, you can import the downtime in to your "Google Calendar" - go on, it's easy to remove when you're not on shift!). If you do raise GGUS tickets, check downtime. GGUS tickets are mainly for SITE problems. Other things (like datasets not being found because they weren't made properly) don't need GGUS tickets.

Raise GGUS tickets as "TEAM". This is important and easy to forget. You have to click the link at the top of the page to get TEAM tickets (as opposed to GGUS tickets!).
In your GGUS ticket, cc the list: "atlas-project-adc-operations-shiftsNOSPAMcern.ch"

View topic | History: r26 < r25 < r24 < r23 | More topic actions...