Difference: ImagerTechnicalInformation (5 vs. 6)

Line: 1 to 1

META TOPICPARENT	name="WebHome"

Imager Technical Information

Line: 6 to 6

Changed:

<
<

UPDATE POLICY IS STILL BEING DECIDED UPON.
If you would like your machine to be frozen during a conference freeze period, add your machine to the Conference Freeze Dates wiki page and send an email to imager-tech@csDELETEthisTEXT.ubc.ca .
For Imager computers (subnet 54), if you don't want your machine to be upgraded, then turn off cfengine.
Frozen and non-frozen periods for updating machines will be determined at the Imager Tech Staff Meetings in accordance with the calendar of conferences. There will be a 48 hour notification on updates during the non-frozen period. No updates (including security updates) will occur during the frozen period. The updates will be tested on 'tom' first, and 'tom' will generate an email to imager-tech when it is upgraded.

>
>

Update policy applies to Imager computers on subnet 54.
The imager tech members will decide upon conference freeze periods. To determine these periods, a calendar of conferences will be consulted. This calendar will list the freeze periods and the machines to be frozen during each period. Tech staff will check the calendar for freeze periods and will not update the listed machines until the freeze period is over. No updates (including security updates) will occur on listed machines during their freeze periods. * There will be a 48 hour notification on updates during non-frozen times. The updates will be tested on 'tom' first, and 'tom' will generate an email to imager-tech when it is upgraded.

Look at the file /var/log/yum.log to see a list of recent updates to Linux machines.

Line: 28 to 27

Changed:

<
<

>
>

The Joint Admin Model exists for Imager machines so that representatives have admin privileges as well as the tech staff. One representative per OS has sudo access. This is currently Tibi for Linux and David for Windows. Sudo access can be used in emergency situations. When performing a sudo access, the representative needs to notify the tech staff by email. The tech staff will keep track of sudo accesses and will report un-emailed incidents.