Difference: Savannah (3 vs. 4)

Revision 42009-09-19 - ZhangXiaomei

Line: 1 to 1
 
META TOPICPARENT name="WebHome"
Changed:
<
<

register you as a new user in the savannah system

>
>

Register you as a new user in the savannah system

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

register your user account as a member of the cmscompinfrasup group

>
>

Register your user account 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.
Changed:
<
<

enter CMS Computing Infrastructure Support

>
>

Enter CMS Computing Infrastructure Support

 
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.
Changed:
<
<

open a ticket with right options(IMPORTANT)

>
>

Open a ticket with right options(IMPORTANT)

 

instruction

  • choose a Category for you problem, typically SAM test, CMS JobRobot, Data Transfers (or any other more sensible field)
Line: 32 to 32
 
  • Site : correct Site if it's open for site.
  • Assigned to : correct squad for sites or services.
Changed:
<
<

fill a ticket with right Summary and Body(IMPORTANT)

>
>

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:
     
 
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