NOTES FROM THE WLCG PANEL ON SUPPORT ISSUES 2008-04-22 http://indico.cern.ch/conferenceOtherViews.py?view=standard&confId=6552#2008-04-22 ORDINARY TICKETS IN TERMS OF PRIORITY BUT SPECIAL IN TERMS OF ROUTING ===================================================================== 1. The shifters won't be 2K, they will be 15. We shall call these shifters "The Team". TEAM MEMBERS should have the power to assign GGUS tickets directly to SITES. The Team will be maintained by the VO Manager in a simba list. The Members' DNs will be given to GGUS. Periodic maintenance will be done via automatic data extraction from simba. https://savannah.cern.ch/support/?103378 updated. 2. Tier1s are also ROCs. This is good because current assignment to Support Unit (SU) ROC_bla can continue. IN ADDITION, *if clicked*, the currently already existing button "Affects Specific Site" (with help to find the Site Name in GOCDB) should put the Site_Contact email in the GGUS ticket's Cc field. Examples: For the CERN-SC Site Contact email hep-project-grid-cern-testbed-managers@cern.ch For the PIC Site Contact email lcg.support@pic.es For the NIKHEF-ELPROD Site Contact email grid.sysadmin@nikhef.nl (If these are not the appropriate email addresses, lets agree on the principle work-flow and see how we solve the practicalities later). IS THIS "CC:" EQUIVALENT TO ASSIGNING TO THE SITE? 3. GGUS developers suggest: When a member of "The Team" opens a new ticket (s)he will be able to click on whether this will be updatable by: him/herself only The Team (don't use "public" for this, please) the world BUT!!!!!! Atlas requires that "The Team", the ROC and the Site get the notifications (no further options needed) and can update the ticket. What about the other VOs? ALARM/EMERGENCY TICKETS: ======================= 4. If we call the shifters "The Team" and they are about 15 people, then "The Authorised Alarmers" are, not necessarily a subset of "The Team", but certainly not more than 4 people per VO. 5. GGUS will recognise "The Authorised Alarmers" by their certificate, either in an email signature or in the browser. GGUS will then send out the notification email to the site signed with its own certificate. Thus, the Site Admins will recognise this is an alarm worth handling immediately. A GGUS ticket must be raised in parallel to the signed email. ============================================================================ Time scale: June (26th) GGUS Release *IF* we get enough feedback on the prototype test system to be made available a.s.a.p. ============================================================================ A.O.B.GGUS/FABRIC INTERFACE: ============================ . The NAGIOS-GGUS interface will happen but a lot needs to be understood. We heard about this yesterday, in one of the usual surprise announcements. Jeff and James won't have the requirements' ready for the May 6th USAG. https://savannah.cern.ch/support/?104188 is open to track progress on this. ---- These notes were sent to the following people for review ------- ---- before being published on this page. Corrections by Xavier ------- ---- and Torsten were applied. ------- Subject: WLCG 22/4/08 panel notes Date: Tue, 22 Apr 2008 19:28:16 +0200 From: Maria Dimou-Zacharova To: , Jeff Templon , Gonzalo Merino Arevalo , Xavier Espinal Curull , Graeme Andrew STEWART , John Gordon , Jamie Shiers , Ian Bird , Harry Renshall , James Casey ----- M. Dimou with comments from T.Antoni and X. Espinal Last update 2008-04-29