Closed Bug 664500 Opened 14 years ago Closed 14 years ago

sync time on esx vms to their esx server

Categories

(Infrastructure & Operations :: RelOps: General, task)

x86
macOS
task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: arich, Assigned: mlarrain)

Details

All esx vms should be configured to sync to their esx server's clock so we don't fall out of sync with other physical hosts.
Do you have a list of IP's for all the ESX servers so I don't miss any.
Inventory is the best palce to look: https://inventory.mozilla.org/ search for bm-vmware (we have 01 - 13)
Updated buildbot-master09 and buildbot-master10
Per convo with jhford and dustin will wait to change the sync for moz2-linux64-slavexx machines for when the next downtime is.
Flags: needs-treeclosure?
time required will be roughly 20 minutes tops
Need to find out who owns nb-l10n-dashboard01 and nb-l10n-db
(In reply to comment #6) > Need to find out who owns nb-l10n-dashboard01 and nb-l10n-db Axel might know. Weird, they are not named bm-* anymore but nb-*; is this from when they were moved outside of the build network? did that happen?
Created Bug 666742 to deal with nb-l10n-dashboard01
For production-opsi and staging opsi I have added notes in vsphere; digipengi - June 23rd 2011 - This machine is running in Germany's Timezone and thus shouldn't be synced to the host.
It will take me around 30min for me to update the time sync. clients involved are moz2-linux64-slave01-12 and try-linux64-slave01-10
The list of machines that needs to be sync'd is; moz2-linux64-slave03 - 12 nb-l10n-db try-linux64-slave01 - 19 buildbot-master07 buildbot-master08 moz2-linux64-slave01 - 02
Flags: needs-treeclosure? → needs-treeclosure+
Two hour downtime scheduled for tmorrow, Friday July 8th, 2011 at 11:00 AM PDT.
Flags: needs-treeclosure+
I finished my task on time
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Component: Server Operations: RelEng → RelOps
Product: mozilla.org → Infrastructure & Operations
You need to log in before you can comment on or make changes to this bug.