Difference: ProblemTracking (1 vs. 10)

Revision 102010-05-01 - RonMaharik

Line: 1 to 1
 
META TOPICPARENT name="ImagerLabAdministration"

Imager-Tech Group and Problem Tracking Procedures

The committee has the following members:

Changed:
<
<
  • Tamara Munzner - faculty rep
>
>
  • Robert Bridson - faculty rep
 
  • Glen Lee - techstaff rep for Imager
  • Cheryl Lau - imager-tech czar
  • Christopher Batty - Windows and Mac czar
Changed:
<
<
  • Tiberiu Popa - Linux czar
>
>
  • Ron Maharik - Linux czar
 

Current Open Problems

Line: 45 to 45
 

Imager Machine List

Changed:
<
<
>
>
 

Conference Freeze Dates

Revision 92008-07-23 - llachlan

Line: 1 to 1
 
META TOPICPARENT name="ImagerLabAdministration"

Imager-Tech Group and Problem Tracking Procedures

Line: 44 to 44
 ImagerTechnicalInformation

Imager Machine List

Deleted:
<
<
  • CLL, please link to new machine list here!
 
Changed:
<
<
>
>
 

Conference Freeze Dates

Revision 82008-02-21 - TamaraMunzner

Line: 1 to 1
 
META TOPICPARENT name="ImagerLabAdministration"

Imager-Tech Group and Problem Tracking Procedures

Line: 43 to 43
 Imager folks might need to know. It's up at ImagerTechnicalInformation
Added:
>
>

Imager Machine List

  • CLL, please link to new machine list here!

 

Conference Freeze Dates

We're also trying to be proactive about freezing system updates for

Revision 72008-01-24 - TamaraMunzner

Line: 1 to 1
 
META TOPICPARENT name="ImagerLabAdministration"

Imager-Tech Group and Problem Tracking Procedures

The committee has the following members:

Changed:
<
<
  • Tamara Muzner - faculty rep
>
>
  • Tamara Munzner - faculty rep
 
  • Glen Lee - techstaff rep for Imager
  • Cheryl Lau - imager-tech czar
  • Christopher Batty - Windows and Mac czar

Revision 62007-10-12 - TamaraMunzner

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

Problem Tracking Procedures

>
>

Imager-Tech Group and Problem Tracking Procedures

 
Changed:
<
<
We have established a wiki page under StatusReport, that is used to track open system administration issues.
>
>
The committee has the following members:
 
Changed:
<
<
This page tracks all known open problems. Progress on the issues on this list will be discussed with the technical staff on a weekly basis (Wednesdays this term).
>
>
  • Tamara Muzner - faculty rep
  • Glen Lee - techstaff rep for Imager
  • Cheryl Lau - imager-tech czar
  • Christopher Batty - Windows and Mac czar
  • Tiberiu Popa - Linux czar

Current Open Problems

The main avenue for technical problems is always the helpdesk, help@cs, for problems like "my graphics driver no longer works". Most of the time, those problems get fixed quickly. Sometimes things are more complicated and drag on for longer. We keep track of those in a Current Open Problems list, and have weekly meetings to track the progress and keep things from falling through the cracks. We often add items to that list ourselves. It's a wiki, so you can add items to the list yourself if there's something that is lingering unresolved for longer than a week or so. Our weekly meetings are currently Thursdays at 11am, we'll address everything that's been added by Wednesday morning. The list itself is at StatusReport

Czarships and Sudo

In Imager, specific representatives (czars) have sudo admin privileges. Tibi (stpopa@cs) is the Linux czar, and Christopher (batty@cs) is the Windows/Mac czar. Sudo access is intended only for problems that are urgent, after normal hours, and relatively straightforward. (Of course, the czars do not commit to on-call 24/7, but if they're around they'll try to help you out.) We send mail to the techstaff after every sudo to let them know what we fixed, so that they're aware of it for the record.

Imager Technical Information

We maintain a list of technical and/or policy tidbits that general Imager folks might need to know. It's up at ImagerTechnicalInformation

Conference Freeze Dates

We're also trying to be proactive about freezing system updates for specific machines before conference deadlines relevant for their main users. We are maintaining a list of upcoming conferences, and the list of machines that will be frozen for those. Again, it's a wiki, please add information yourself if there's a conference that's not currently listed that should be. That list is at ConferenceFreezeDates

 
Changed:
<
<
In order for this mechanism to work, we need your collaboration. If you encounter a problem with the computer systems, you should do the following:

  • send mail to help@csDELETEthisTEXT.ubc.ca as usual.
  • if the problem does not get resolved within a few days, add it to the above wiki page. Make sure you list your name, so we can contact you if necessary. Also specify the help system tracking number. Any entry that makes it by Tuesday around noon will be discussed at our meeting in the afternoon.
  • if you have problems or question regarding the wiki, contact Cheryl Lau (cherylsl@csDELETEthisTEXT.ubc.ca). Cheryl is not responsible for solving the problem, but she takes care of the tracking, and might be able to tell you the result of the discussion at the weekly meetings.
  • once your request to help@cs is addressed, please send Cheryl a note, and remove the entry from the wiki.

In addition to this mechanism, we also have 3 students to fix urgent(!) problems, or perform trivial tasks that would take the technical staff too long to get around to. The three are:

Tibi already has sudo access on the lab's Linux machines, and has been using it for some while to help people out. The exact mechanisms that David and Ken can use to help with Mac and Windows will have to evolve. It is likely that Macs will see Linux-style management at some point. The situation for Windows is more complicated due to registry fun.

We will review this new mechanism after a few months, so if you have any concerns or suggestions, send email to heidrich@csDELETEthisTEXT.ubc.ca, or talk to your supervisor.

-- WolfgangHeidrich - 07 Feb 2006

>
>
-- updated by Tamara 12 Oct 2007
-- originally started by Wolfgang 07 Feb 2006
 

Revision 52007-02-08 - cherylsl

Line: 1 to 1
 
META TOPICPARENT name="ImagerLabAdministration"

Problem Tracking Procedures

We have established a wiki page under StatusReport, that is used to track open system administration issues.

Changed:
<
<
This page tracks all known open problems. Progress on the issues on this list will be discussed with the technical staff on a weekly basis (Tuesday afternoons this term).
>
>
This page tracks all known open problems. Progress on the issues on this list will be discussed with the technical staff on a weekly basis (Wednesdays this term).
  In order for this mechanism to work, we need your collaboration. If you encounter a problem with the computer systems, you should do the following:
Line: 14 to 14
 
  • if the problem does not get resolved within a few days, add it to the above wiki page. Make sure you list your name, so we can contact you if necessary. Also specify the help system tracking number. Any entry that makes it by Tuesday around noon will be discussed at our meeting in the afternoon.
  • Changed:
    <
    <
  • if you have problems or question regarding the wiki, contact Cheryl Lau (cherylsl@csDELETEthisTEXT.ubc.ca). Cheryl is not responsible for solving the problem, but he takes care of the tracking, and might be able to tell you the result of the discussion at the weekly meetings.
  • >
    >
  • if you have problems or question regarding the wiki, contact Cheryl Lau (cherylsl@csDELETEthisTEXT.ubc.ca). Cheryl is not responsible for solving the problem, but she takes care of the tracking, and might be able to tell you the result of the discussion at the weekly meetings.
  •  
  • once your request to help@cs is addressed, please send Cheryl a note, and remove the entry from the wiki.
  • Revision 42007-02-08 - BradAtcheson

    Line: 1 to 1
     
    META TOPICPARENT name="ImagerLabAdministration"

    Problem Tracking Procedures

    Line: 14 to 14
     
  • if the problem does not get resolved within a few days, add it to the above wiki page. Make sure you list your name, so we can contact you if necessary. Also specify the help system tracking number. Any entry that makes it by Tuesday around noon will be discussed at our meeting in the afternoon.
  • Changed:
    <
    <
  • if you have problems or question regarding the wiki, contact Brad Atcheson (atcheson@csDELETEthisTEXT.ubc.ca). Brad is not responsible for solving the problem, but he takes care of the tracking, and might be able to tell you the result of the discussion at the weekly meetings.
  • >
    >
  • if you have problems or question regarding the wiki, contact Cheryl Lau (cherylsl@csDELETEthisTEXT.ubc.ca). Cheryl is not responsible for solving the problem, but he takes care of the tracking, and might be able to tell you the result of the discussion at the weekly meetings.
  •  
    Changed:
    <
    <
  • once your request to help@cs is addressed, please send Brad a note, and remove the entry from the wiki.
  • >
    >
  • once your request to help@cs is addressed, please send Cheryl a note, and remove the entry from the wiki.
  •  
    Line: 24 to 24
     
    Changed:
    <
    <
  • Tyson Brochu (tbrochu@csDELETEthisTEXT.ubc.ca) for Mac
  • >
    >
  • David Young (hdfy@csDELETEthisTEXT.ubc.ca) for Mac
  •  
  • Ken Rose (kenrose@csDELETEthisTEXT.ubc.ca) for Windows
  • Changed:
    <
    <
    Tibi already has sudo access on the lab's Linux machines, and has been using it for some while to help people out. The exact mechanisms that Tyson and Ken can use to help with Mac and Windows will have to evolve. It is likely that Macs will see Linux-style management at some point. The situation for Windows is more complicated due to registry fun.
    >
    >
    Tibi already has sudo access on the lab's Linux machines, and has been using it for some while to help people out. The exact mechanisms that David and Ken can use to help with Mac and Windows will have to evolve. It is likely that Macs will see Linux-style management at some point. The situation for Windows is more complicated due to registry fun.
      We will review this new mechanism after a few months, so if you have any concerns or suggestions, send email to heidrich@csDELETEthisTEXT.ubc.ca, or talk to your supervisor.

    Revision 32006-05-30 - BradAtcheson

    Line: 1 to 1
     
    META TOPICPARENT name="ImagerLabAdministration"

    Problem Tracking Procedures

    Line: 14 to 14
     
  • if the problem does not get resolved within a few days, add it to the above wiki page. Make sure you list your name, so we can contact you if necessary. Also specify the help system tracking number. Any entry that makes it by Tuesday around noon will be discussed at our meeting in the afternoon.
  • Changed:
    <
    <
  • if you have problems or question regarding the wiki, contact Shruthi Achutha (shruthi@csDELETEthisTEXT.ubc.ca). Shruthi is not responsible for solving the problem, but she takes care of the tracking, and might be able to tell you the result of the discussion at the weekly meetings.
  • >
    >
  • if you have problems or question regarding the wiki, contact Brad Atcheson (atcheson@csDELETEthisTEXT.ubc.ca). Brad is not responsible for solving the problem, but he takes care of the tracking, and might be able to tell you the result of the discussion at the weekly meetings.
  •  
    Changed:
    <
    <
  • once your request to help@cs is addressed, please send Shruthi a note, and remove the entry from the wiki.
  • >
    >
  • once your request to help@cs is addressed, please send Brad a note, and remove the entry from the wiki.
  •  

    Revision 22006-02-08 - WolfgangHeidrich

    Line: 1 to 1
     
    META TOPICPARENT name="ImagerLabAdministration"

    Problem Tracking Procedures

    Line: 12 to 12
     
    Changed:
    <
    <
  • if the problem does not get resolved within a few days, add it to the above wiki page. Make sure you list your name, so we can contact you if necessary. Also specify the help system tracking number. Any entry that makes it by Monday morning will be discussed at our meeting Tuesday afternoon.
  • >
    >
  • if the problem does not get resolved within a few days, add it to the above wiki page. Make sure you list your name, so we can contact you if necessary. Also specify the help system tracking number. Any entry that makes it by Tuesday around noon will be discussed at our meeting in the afternoon.
  •  
  • if you have problems or question regarding the wiki, contact Shruthi Achutha (shruthi@csDELETEthisTEXT.ubc.ca). Shruthi is not responsible for solving the problem, but she takes care of the tracking, and might be able to tell you the result of the discussion at the weekly meetings.
  • Line: 29 to 29
     
    Changed:
    <
    <
    Tibi already has sudo access on the lab's Linux machines, and has been using it for some while to help people out. The exact mechanisms that Tyson and Ken can use to help with Mac and Windows will have to evolve.(*)
    >
    >
    Tibi already has sudo access on the lab's Linux machines, and has been using it for some while to help people out. The exact mechanisms that Tyson and Ken can use to help with Mac and Windows will have to evolve. It is likely that Macs will see Linux-style management at some point. The situation for Windows is more complicated due to registry fun.
     
    Changed:
    <
    <
    We will review this new mechanism after a few months, so if you have any concerns or suggestions, drop me an email, or talk to your supervisor.

    Cheers,

    Wolfgang

    (*) It is likely that Macs will see Linux-style management at some point. The situation for Windows is more complicated due to registry fun.

    >
    >
    We will review this new mechanism after a few months, so if you have any concerns or suggestions, send email to heidrich@csDELETEthisTEXT.ubc.ca, or talk to your supervisor.
     

    -- WolfgangHeidrich - 07 Feb 2006

    Revision 12006-02-07 - WolfgangHeidrich

    Line: 1 to 1
    Added:
    >
    >
    META TOPICPARENT name="ImagerLabAdministration"

    Problem Tracking Procedures

    We have established a wiki page under StatusReport, that is used to track open system administration issues.

    This page tracks all known open problems. Progress on the issues on this list will be discussed with the technical staff on a weekly basis (Tuesday afternoons this term).

    In order for this mechanism to work, we need your collaboration. If you encounter a problem with the computer systems, you should do the following:

    • send mail to help@csDELETEthisTEXT.ubc.ca as usual.
    • if the problem does not get resolved within a few days, add it to the above wiki page. Make sure you list your name, so we can contact you if necessary. Also specify the help system tracking number. Any entry that makes it by Monday morning will be discussed at our meeting Tuesday afternoon.
    • if you have problems or question regarding the wiki, contact Shruthi Achutha (shruthi@csDELETEthisTEXT.ubc.ca). Shruthi is not responsible for solving the problem, but she takes care of the tracking, and might be able to tell you the result of the discussion at the weekly meetings.
    • once your request to help@cs is addressed, please send Shruthi a note, and remove the entry from the wiki.

    In addition to this mechanism, we also have 3 students to fix urgent(!) problems, or perform trivial tasks that would take the technical staff too long to get around to. The three are:

    Tibi already has sudo access on the lab's Linux machines, and has been using it for some while to help people out. The exact mechanisms that Tyson and Ken can use to help with Mac and Windows will have to evolve.(*)

    We will review this new mechanism after a few months, so if you have any concerns or suggestions, drop me an email, or talk to your supervisor.

    Cheers,

    Wolfgang

    (*) It is likely that Macs will see Linux-style management at some point. The situation for Windows is more complicated due to registry fun.

    -- WolfgangHeidrich - 07 Feb 2006

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