Warning Livedoc is no longer being updated and will be deprecated shortly. Please refer to https://documentation.tjhsst.edu.

Changes

Jump to: navigation, search

Todo - Winter 2014

5,391 bytes added, 14:09, 27 December 2014
initial todo list
The following list of items should ideally be accomplished over winter break. If you are interested in working on a task below, please add your name next to the system name, see [[]] for an example. Items in red need downtime notification provided to users and the Sysadmins mailing list at least 24 hours in advance of maintenance. All other items should have a downtime notice provided to the Sysadmins mailing list at least 6 (preferably 24) hours in advance. Maintenance times should be posted here '''and loaded into Nagios''' as soon as they are available for general awareness.

=General Notes=
Downtime notifications for items highlighted in Red should be posted via Iodine at least 24 hours in advance (but ideally as soon as possible). They should include both a start time and estimated end time. Be generous when estimating end-times :).

In general, a good pattern to follow when updating systems is: Reboot, Update, Reboot again, Verify. This way you are sure that the system is in working order before beginning work. The Verify step is also very important to make sure that you leave systems in working order :). When running updates, check for unexpected downgrades in the package list before starting an emerge; these can indicate packages that need a later version unmasked or keyworded. Always run updates from within a screen on the host system in case of an unexpected disconnection.

You should also make sure you have a current backup (If the system is running Guardian, check /root/scripts/backup.log to make sure the last backup is current and successful).

For paired/redundant systems (eg: casey/smith or ns1/ns2), there should be at least 24 hours between the maintenance windows for the two servers to allow time for any subtle problems to surface.

Please do not claim tasks unless you intend to start working on them shortly. Claiming a bunch of jobs right off the bat leaves other people looking for things to do.

=Updates=

==VM Servers==

===Antipodes===
* <span style="color:red">update system software</span>
* <span style="color:red">update kernel to 3.14.27</span>

===Galapagos===
* <span style="color:red">update system software</span>
* <span style="color:red">update kernel to 3.14.27</span>

===Littleblue===
* update system software
* update kernel to 3.14.27

===Vega===
* <span style="color:red">update system software</span>
* <span style="color:red">update kernel to 3.14.27</span>

===Waitaha===
* update system software
* update kernel to 3.14.27

==VMs==

===bugs===
* update system software
* update kernel to 3.14.27
* update bugzilla to latest release

===casey===
* update system software
* update kernel to 3.14.27

===cups2===
* update system software
* update kernel to 3.14.27

===fcpsapps===
* update system software
* update kernel to 3.14.27

===haimageserver===
* update system software
* update kernel to 3.14.27

===iodine===
* <span style="color:red">update system software</span>
* <span style="color:red">update kernel to 3.14.27</span>

===iodine-ldap===
* <span style="color:red">update system software</span> [[User:Andrew Hamilton|Andrew Hamilton]] ([[User talk:Andrew Hamilton|talk]])
* <span style="color:red">update kernel to 3.14.27</span> [[User:Andrew Hamilton|Andrew Hamilton]] ([[User talk:Andrew Hamilton|talk]])

===ion===
* update system software
* update kernel to 3.14.27

===lists===
* <span style="color:red">update system software</span>
* <span style="color:red">update kernel to 3.14.27</span>

===mysql1===
* <span style="color:red">update system software</span>
* <span style="color:red">update kernel to 3.14.27</span>

===ns1===
* <span style="color:red">update system software</span>
* <span style="color:red">update kernel to 3.14.27</span>

===ns2===
* <span style="color:red">update system software</span>
* <span style="color:red">update kernel to 3.14.27</span>

===openafs1===
* <span style="color:red">update system software</span>
* <span style="color:red">update kernel to 3.14.27</span>

===openafs3===
* update system software

===openafs4===
* <span style="color:red">update system software</span>
* <span style="color:red">update kernel to 3.14.27</span>

===openafs5===
* <span style="color:red">update system software</span>
* <span style="color:red">update kernel to 3.14.27</span>

===openafs6===
* <span style="color:red">update system software</span>
* <span style="color:red">update kernel to 3.14.27</span>
* <span style="color:red">completely rename system to openafs6</span>

===openldap1===
* update system software
* update kernel to 3.14.27

===openldap2===
* update system software
* update kernel to 3.14.27

===openvpn===
* update system software
* update kernel to 3.14.27
* setup second openvpn instance on UDP port 1194

===puppet===
* update system software
* update kernel to 3.14.27

===ras1===
* <span style="color:red">update system software</span>
* <span style="color:red">update kernel to 3.14.27</span>

===ras2===
* <span style="color:red">update system software</span>
* <span style="color:red">update kernel to 3.14.27</span>

===stage64===
* update system software
* update kernel to 3.14.27

===smith===
* update system software
* update kernel to 3.14.27

===steeltoe===
* update system software
* update kernel to 3.14.27

===www===
* <span style="color:red">update system software</span>
* <span style="color:red">update kernel to 3.14.27</span>

Navigation menu