Difference: Savannah (1 vs. 5)

instruction

check list

• good example1:

• good example2 (when to open a savannah ticket):

   
     Subject: [ELOG] T2_US_UCSD
     Logbook URL: https://prod-grid-logger.cern.ch/elog/Distributed+Grid+Sites/81
     Since T2_US_UCSD downtime is over since nearly 12 hours now, they are still  failing the CMS-CE-analysis test, 
     due to an eror when trying to open the analysis-test file. Therefore, it is probably worth informing the site about 
     this error by suggesting them to check everyhing was put back in production correctly after their downtime with 
     the following ticket:
      - Category: SAM tests, Assigned to: cmscompinfrasup-t2usucsd, Use GGUS: No, Severity: Normal, Privacy: Public,
  Site: T2_US_UCSD
      - Clearly specify the Subject in the forseen field, for example "CE-CMS-analysis SAM failure at T2_US_UCSD since
  end of downtime"
      - provide the link to the SAM error in the body of the ticket and sign as CSP
      - submit
     

Better to inform the next shifters and the CRC about the ticket in the elog after opening

Register you as a new user in the savannah system

Register your user account as a member of the cmscompinfrasup group

Enter CMS Computing Infrastructure Support

Open a ticket with right options(IMPORTANT)

Fill a ticket with right Summary and Body(IMPORTANT)

https://savannah.cern.ch/projects/cmscompinfrasup/ 

• at the middle top bar, choose support to view the ticket already opened. choose submit to create a new ticket.
• when you view the support, there is a Display Criteria which filter the tickets with parameters.

instruction

• choose a Category for you problem, typically SAM test, CMS JobRobot, Data Transfers (or any other more sensible field)
• select the following other fields:
  Privacy : Public
  Severity : usually Normal or Important
  Use GGUS : No
  Status : whatever is most appropriate (not very relevant)
• always ASSIGN your ticket to the correct person or site (to what we call a squad). Once you are a member of cmscompinfrasup, you will see a roll-down menu called Assigned to and you need to select the correct squad. Typically this will be a CMS site, for example if there is a problem at the T2 in Bristol, you will select cmscompinfrasup-t2uksgridbristol. If you don’t do that, local site admins will not receive your ticket.
• make sure also to select the site concerned with the problem. You can do that via the Site roll-down menu, for example if there is a problem in the T2 at Bristor, select T2_UK_SGrid_Bristol . This is very important for the search engine in Savannah.

check list

• Category : SAM test , CMS JobRobot , Data Transfers
• Privacy : Public
• Severity : Normal or Important
• Use GGUS : No
• Status : (not necessary)
• Site : correct Site if it's open for site.
• Assigned to : correct squad for sites or services.

• be very explicit about the problem in the subject of your ticket, by filling the Summary field. For example, say there is a SAM-SRM error at T2_UK_SGrid_Bristol, then the minimum summary would be : “SAM-SRM failure at T2_UK_SGrid_Bristol” or anything sensible like that. Imagine that CMS Computing Experts have to deal with many many tickets, so the more explicit your are in the Subject, the easier for us !
• be even more explicit about the details of your obervations in the BODY of your ticket. To the least, you should provide the time since the problem has occurred (or if you don’t know, then the time of observations) + an explanation of the problem + the pointer the actual error message.
• good examples:

register you as a new user in the savannah system

register your user account as a member of the cmscompinfrasup group

enter CMS Computing Infrastructure Support

https://savannah.cern.ch/projects/cmscompinfrasup/

open a ticket with right options(IMPORTANT)

• choose a “Category” for you problem, typically “SAM test”, “CMS JobRobot” or “Data Transfers” (or any other more sensible field)
• select the following other fields: Privacy : “Public” / Severity : usually “Normal” or “Important”/ Use GGUS : “No” / Status : whatever is most appropriate (not very relevant)
• always ASSIGN your ticket to the correct person or site (to what we call a “squad”). Once you are a member of cmscompinfrasup, you will see a roll-down menu called “Assigned to” and you need to select the correct “squad”. Typically this will be a CMS site, for example if there is a problem at the T2 in Bristol, you will select “cmscompinfrasup-t2uksgridbristol”. If you don’t do that, local site admins will not receive your ticket.
• make sure also to select the site concerned with the problem. You can do that via the “Site” roll-down menu, for example if there is a problem in the T2 at Bristor, select “T2_UK_SGrid_Bristol”. This is very important for the search engine in Savannah.

fill a ticket with right Summary and Body(IMPORTANT)

• be very explicit about the problem in the subject of your ticket, by filling the “Summary” field. For example, say there is a SAM-SRM error at T2_UK_SGrid_Bristol, then the minimum summary would be : “SAM-SRM failure at T2_UK_SGrid_Bristol” or anything sensible like that. Imagine that CMS Computing Experts have to deal with many many tickets, so the more explicit your are in the Subject, the easier for us !
• be even more explicit about the details of your obervations in the BODY of your ticket. To the least, you should provide the time since the problem has occurred (or if you don’t know, then the time of observations) + an explanation of the problem + the pointer the actual error message.
• good examples:

https://savannah.cern.ch/my/groups.php

https://savannah.cern.ch/support/index.php?109709

register as a new user in the savannah system

 https://savannah.cern.ch/account/register.php

register you as a member of the cmscompinfrasup group

 https://savannah.cern.ch/my/groups.php 

• Ways: Down on the bottom right you can search and request to join the CMS Computing Infrastructure Support group. Please specify this membership is required for your CSP work.

Hands on machine setup

1. Install SLC5X i386 via http from mirror.ihep.ac.cn

1. ATI driver:

 
   ./ati-driver-installer-9-6-x86.x86_64.run

   aticonfig --initial=dual-head

1. AFS login:

   cd afs_all_patch_3.0_for_x86_64
   ./afs_patch_install.sh
   vi /etc/ssh/sshd_config
   # comment out "TcpRcvBufPoll yes" in /etc/ssh/sshd_config file

1. create a firefox profile share with all shifters.

   firefox -p /afs/ihep.ac.cn/users/l/liangd/public
   find /afs/ihep.ac.cn/users/l/liangd/public -exec chmod  777 {} \;
   make a /data/control_room_beijing/start_shift_firefox.sh to modify ~/.mozilla/firefox/profiles.ini

Shift procedures

1. logon machine with his AFS account
2. open a console

   sh /data/control_room_beijing/start_shift_firefox.sh

-- LiangDong - 2009-07-10