| 13 | | |
| 14 | | [[ListTagged(f2f)]] |
| | 13 | = Adopt a server notes pulled from etherpad = |
| | 14 | It may beg gone, but this came from [https://pad.riseup.net/p/HjVgvhNxt6gW this pad page] |
| | 15 | == Current Responsibilities == |
| | 16 | * minimal responisiblity; make sure the servers stay upgraded. Rationale: Jamie had previously been running (or not) upgrades on n servers. |
| | 17 | === Upcoming Future Responsibilities === |
| | 18 | * Make sure file systems have enough space on them |
| | 19 | * Audit back ups |
| | 20 | * Make sure the RAID arrays are in sync |
| | 21 | * Get nagios alerts for your adopted server |
| | 22 | |
| | 23 | -- If you have a problem with an upgrade, make sure to report it to the support-team. |
| | 24 | |
| | 25 | * How to handle kernel upgrades? |
| | 26 | Always do all upgrades whether or not a reboot is required. Because kernel ugrades are highly unlikely to cause problems even without a reboot. |
| | 27 | * How do we handle physical host upgrades? |
| | 28 | We have been running all of them in the same fashion as kernel upgrades. |
| | 29 | * Timing |
| | 30 | Upgrades should not be run between 900 America/New_York and 1800 America/New_York Monday through Friday |
| | 31 | == Covering Support == |
| | 32 | * Check tickets |
| | 33 | ** between 1100 and 1200 America/New_York |
| | 34 | ** between 1700 and 1800 America/New_York |
| | 35 | ** There has to be some response on all tickets |
| | 36 | ** Answer/resolve easy tickets |
| | 37 | ** Ask for more information, if needed |
