1. https://bugzilla.mozilla.org/show_bug.cgi?id=662396 — Fix time on dm-wwwbuild01
2. https://bugzilla.mozilla.org/show_bug.cgi?id=600980 — Set journal_mode = WAL for dirty places profiles — This mean new performance numbers will start on Thursday morning after the downtime
3. https://bugzilla.mozilla.org/show_bug.cgi?id=649123 — Run ANALYZE on dirty places.sqlite files — This mean new performance numbers will start on Thursday morning after the downtime
4. https://bugzilla.mozilla.org/show_bug.cgi?id=663568 — reboot the DNS and DHCP servers in scl1 — Rebooting these servers has been shown to burn builds in the past, requires a short (~5min) outage to reboot these servers to allow updates to take effect.
5. https://bugzilla.mozilla.org/show_bug.cgi?id=663963 — change LDAP to see if that speeds up mercurial — This change should be entirely transparent. Hg processes that are running at the time that the change was made will have already loaded the NSS LDAP module and will continue to use it until they exit. The only issue to be aware of is that changes to hg access (group membership, or the creation of a new account) will not automatically propagate to the hg servers the way they do now. If any hg access changes need to be pushed urgently, we can do that manually.
If anyone has a reason not to proceed with this downtime, please let me know.
