ReleaseEngineering:RelEngITSharedDowntime: Difference between revisions

ReleaseEngineering:RelEngITSharedDowntime (view source)

1,120 bytes removed , 16 January 2012

canmove, Confirmed users

2,850

edits

@@ Line 1: / Line 1: @@
-Maintaining or rebooting any of the following systems needs coordinated downtimes with RelEng and IT. It usually also needs advance notice of Tree Closures posted to dev.tree-management.
+#REDIRECT [[ReleaseEngineering:Buildduty:Downtimes#How_do_I_coordinate_downtimes_with_IT.3F]]
-* build.m.o (clobberer, build data, tryserver symbols)
-* cruncher.build.m.o (graphs dashboard, dumping build data, dashboards, pulse)
-* cvs.mozilla.org (talos)
-* hg.mozilla.org (firefox source repos, build repos)
-* tinderbox.mozilla.org (central reporting point for all builds)
-* ftp.mozilla.org (release updates on beta channel)
-* stage.mozilla.org (publishing builds, downloading builds for talos/unittest)
-* graphs.mozilla.org (performance tracking)
-* tm-b01-master01.mozilla.org (buildbot scheduler db, graphserver?)
-* tm-b01-slave01.mozilla.org (used by cruncher)
-* mail.build.mozilla.org - currently dm-mail03.m.o (build mail to tinderbox)
-* aus2-staging.mozilla.org (update snippets)
-* nm-ops03.build.mozilla.org (releng VMs)
-* nagios.mozilla.org (monitoring)
-* tbpl.mozilla.org (build status)
-Per mrz,
-* <s>DNS, DHCP (build slaves reboot all the time)(not an issue, because DNS, DHCP are fully redundant)</s>
-For any questions, or if you're not sure about a particular server, please check with "buildduty" in #ops.