Closed Bug 541953 Opened 10 years ago Closed 10 years ago

bring new win32 ix machines up to date after they arrive

Categories

(Release Engineering :: General, defect)

All
macOS
defect
Not set

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: bhearsum, Assigned: bhearsum)

References

Details

(Whiteboard: [buildslaves])

Attachments

(8 files)

There's going to be some delta between these new win32 machines and what's currently running on the existing build slaves, once they arrive. This bug is to track what we need to install on the new slaves before we can put them in production. For now, the only thing is the disable-jit-debugger OPSI package from bug 533185.
Whiteboard: [buildslaves]
I think it's best to keep these slaves named differently than the VMs for purposes of easily identifying issues that only happen one. I had to shorten win32 to 'w32' to accommodate the 'ix' without breaching the 15 char limit. We've got room to grow one more character there, too, so if we hit 100 (or 999) we're OK.
Attachment #425012 - Flags: review?(catlee)
Pretty straightforward. I'm happy to change the balance of staging vs. production - though we probably don't want most of these in production.
Attachment #425014 - Flags: review?(catlee)
Attachment #425016 - Flags: review?(catlee)
Without this, buildbot-tac.py won't be able to generate tac files for win32 IX machines. Unfortunately, this means there will be some manual intervention when they first come up - we'll have to update the clone of build-tools and possibly delete the control file.
Attachment #425019 - Flags: review?(catlee)
Attachment #425019 - Flags: review?(catlee) → review+
Attachment #425014 - Flags: review?(catlee) → review+
Attachment #425012 - Flags: review?(catlee) → review+
Comment on attachment 425016 [details] [diff] [review]
add ix slaves to puppet configs

r+ except for moz2-linux-ix-slave01 in site-production.pp
Attachment #425016 - Flags: review?(catlee) → review+
Comment on attachment 425019 [details] [diff] [review]
add ix machine support to buildbot-tac.py

changeset:   501:6dad2790b649
Attachment #425016 - Flags: checked-in+
Attachment #425019 - Flags: checked-in+
Comment on attachment 425016 [details] [diff] [review]
add ix slaves to puppet configs

changeset:   90:681f7c7fd998
Comment on attachment 425014 [details] [diff] [review]
add ix slaves to the opsi configs

changeset:   35:378a823c1669
Attachment #425014 - Flags: checked-in+
Comment on attachment 425012 [details] [diff] [review]
add ix machines to buildbot-configs

changeset:   2055:a4b03dee88f8
Attachment #425012 - Flags: checked-in+
Attachment #426340 - Flags: review?(catlee) → review+
Attachment #426335 - Flags: review?(catlee) → review+
Attachment #426338 - Flags: review?(catlee) → review+
Comment on attachment 426338 [details] [diff] [review]
update puppet configs with new slave names

changeset:   93:85b97a7ce927
Attachment #426338 - Flags: checked-in+
Comment on attachment 426340 [details] [diff] [review]
update opsi configs with new slavenames

changeset:   38:1590a01bbe61
Attachment #426340 - Flags: checked-in+
Comment on attachment 426335 [details] [diff] [review]
update buildbot-configs with new slave names

changeset:   2070:9cd7c33e4c3a
Attachment #426335 - Flags: checked-in+
There's a few things we need to do these by hand:
Change OPSI key:
* Find host in /etc/opsi/pckeys on production-opsi (or staging-opsi for mw32-ix-slave01), copy key
* Replace key in c:\program files\opsi.org\preloginloader\cfg\locked.cfg with it

Then reboot. OPSI is setup to reinstall the other broken packages. After the machine has finished rebooting, reboot again to get all of the changes to take effect.
Also need to turn off the screensaver after all of this. Do it through VNC as cltbld.
The initial batch of machines are all in staging (01-06, 18-23, 25). 01 is to stay there permanently.
Depends on: 545876
Tested on ix slave01.
Attachment #426693 - Flags: review?(catlee)
Attachment #426693 - Flags: review?(catlee) → review+
Comment on attachment 426693 [details] [diff] [review]
opsi package to rename the vim install.exe file

changeset:   39:d4dbe50d71ab
Attachment #426693 - Flags: checked-in+
Also need to update the tools checkout.
Okay, going to move the following to production today:
10.250.49.125    mw32-ix-slave01    10.250.49.174
10.250.49.126    mw32-ix-slave02    10.250.49.175
10.250.49.127    mw32-ix-slave03    10.250.49.176
10.250.49.128    mw32-ix-slave04    10.250.49.177
10.250.49.129    mw32-ix-slave05    10.250.49.178
10.250.49.130    mw32-ix-slave06    10.250.49.179
10.250.49.142    mw32-ix-slave18    10.250.49.191
10.250.49.143    mw32-ix-slave19    10.250.49.192
10.250.49.144    mw32-ix-slave20    10.250.49.193
10.250.49.145    mw32-ix-slave21    10.250.49.194
10.250.49.146    mw32-ix-slave22    10.250.49.195
10.250.49.147    mw32-ix-slave23    10.250.49.196
10.250.49.149    mw32-ix-slave25    10.250.49.198

mw32-ix-slave01-06, 18-23, and 25.

The others are turned on, and will head to staging today.
need to also click through the licenses for pskill and friends.
also had to set the 'profilevars' package to install, to fix-up the mozillabuild installation
We're all done here.
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.