Closed Bug 488378 Opened 16 years ago Closed 16 years ago

Migrate existing talos slaves to the pool

Categories

(Release Engineering :: General, defect)

Product:
Release Engineering
Component:
General
Platform:
x86
Linux
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: catlee, Unassigned)

References

Details

Attachments

(1 file)

Disable schedulers for branches that have been moved to the pool
4.68 KB, patch
anodelman
: review+
catlee
: checked-in+
Details | Diff | Splinter Review
Enough slaves to handle incoming builds with no queue compression need to be moved from the existing set of talos machines to the new pool. For each slave this means: - Shutdown slave when idle - Rename slave hostname and DNS - Update buildbot.tac to point to new master - Update apache configs. - DocumentRoot and Directory directives should be updated to point to {/home/mozqa,/Users/mozqa,C:}/talos-slave/talos-data/talos - Start slave
Thinking of using talos-rev2-$OS-slave$NN as the host name. $OS would be one of tiger,leopard,xp,vista,linux (or ubuntu? or gutsy?)
Assignee: nobody → catlee
Ok, here's the plan. We're going to start by moving over some of the Firefox 3.0 machines to the pool. Below are the list of slaves and their new names. After the slaves have been reconfigured, DNS and nagios need to be updated. Original name Rename to qm-mini-xp01 talos-rev2-xp05 qm-mini-xp02 talos-rev2-xp06 qm-mini-xp03 talos-rev2-xp07 qm-mini-xp05 talos-rev2-xp08 qm-mini-vista01 talos-rev2-vista05 qm-mini-vista02 talos-rev2-vista06 qm-mini-vista03 talos-rev2-vista07 qm-mini-vista05 talos-rev2-vista08 qm-mini-ubuntu01 talos-rev2-linux03 qm-mini-ubuntu02 talos-rev2-linux04 qm-mini-ubuntu03 talos-rev2-linux05 qm-mini-ubuntu05 talos-rev2-linux06 qm-pmac01 talos-rev2-tiger03 qm-pmac02 talos-rev2-tiger04 qm-pmac03 talos-rev2-tiger05 qm-pmac05 talos-rev2-tiger06 qm-pleopard-trunk06 talos-rev2-leopard03 qm-pleopard-trunk07 talos-rev2-leopard04 qm-pleopard-trunk08 talos-rev2-leopard05 Windows instructions: - VNC in - Shutdown buildbot (Ctrl-C in terminal) - In C:/talos-slave/buildbot.tac, update following fields: buildmaster_host = 'talos-master.mozilla.org' port = 9010 slavename = '<new slavename goes here>' keepalive=None umask=002 - Delete old build directory (will be called something like win32-trunk* / vista-trunk*) - mkdir -p C:/talos-slave/talos-data/talos - On XP you can go into the Start Menu, All Programs, Apache HTTP Server 2.2.4, Configure Apache Server, Edit the Apache httpd.conf Configuration File - On Vista find notepad in the start menu, then Run As Administrator - Edit C:/Program Files/Apache Software Foundation/Apache2.2/conf/httpd.conf - Set DocumentRoot to "C:/talos-slave/talos-data/talos" - Update Directory directive to match - Update hostname: - Start Menu, Right-click on Computer, select Properties - On XP, choose the "Computer Name" tab. - On Vista, There's a section for computer name, description. Click 'change settings' - Click on the "Change" button next to "To rename this computer or ..." - Click OK to confirm changes - Reboot! Mac instructions: - VNC in - Shutdown buildbot (buildbot stop ~/talos-slave) - In /Users/mozqa/talos-slave/buildbot.tac, update following fields: buildmaster_host = 'talos-master.mozilla.org' port = 9010 slavename = '<new slavename goes here>' keepalive=None umask=002 - Delete old build directory (will be called something like mac-trunk* / leopard-trunk*) - mkdir -p /Users/mozqa/talos-slave/talos-data/talos - sudo vi /etc/apache2/conf/httpd.conf - Set DocumentRoot to "/Users/mozqa/talos-slave/talos-data/talos" - Update Directory directive to match - Update hostname: - System Preferences, Sharing - Reboot! (sudo reboot) Linux instructions: - ssh in as mozqa - Shutdown buildbot (buildbot stop ~/talos-slave) - In /Users/mozqa/talos-slave/buildbot.tac, update following fields: buildmaster_host = 'talos-master.mozilla.org' port = 9010 slavename = '<new slavename goes here>' keepalive=None umask=002 - Delete old build directory (will be called something like linux-trunk*) - mkdir -p /home/mozqa/talos-slave/talos-data/talos - sudo vi /etc/apache2/sites-available/default - Set DocumentRoot to "/home/mozqa/talos-slave/talos-data/talos" - Update Directory directive to match - Update hostname: - sudo vi /etc/hostname - Reboot! (sudo reboot)
All of the above have been migrated over.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
All of the above, except the leopard slaves, have been taken out of the production pool and put into staging. It turns out that they're 1.6GHz machines, and not suitable for use in the production pool. Hopefully they'll figure out how to run .2 GHz faster while in staging, but if not then they'll be useful as permanent fixtures in the staging environment.
Working on migrating these slaves over: Original New qm-plinux-trunk01 talos-rev2-linux03 qm-plinux-trunk02 talos-rev2-linux04 qm-plinux-trunk03 talos-rev2-linux05 qm-plinux-trunk07 talos-rev2-linux06 qm-pxp-trunk01 talos-rev2-xp05 qm-pxp-trunk02 talos-rev2-xp06 qm-pxp-trunk03 talos-rev2-xp07 qm-pxp-trunk07 talos-rev2-xp08 qm-pmac-trunk01 talos-rev2-tiger03 qm-pmac-trunk02 talos-rev2-tiger04 qm-pmac-trunk03 talos-rev2-tiger05 qm-pmac-trunk10 talos-rev2-tiger06 qm-pleopard-trunk01 talos-rev2-leopard06 qm-pleopard-trunk02 talos-rev2-leopard07 qm-pleopard-trunk03 talos-rev2-leopard08 qm-pleopard-trunk04 talos-rev2-leopard09 qm-pvista-trunk01 talos-rev2-vista05 qm-pvista-trunk02 talos-rev2-vista06 qm-pvista-trunk03 talos-rev2-vista07 qm-pvista-trunk04 talos-rev2-vista08
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Attachment #383032 - Flags: review?(anodelman) → review+
Comment on attachment 383032 [details] [diff] [review] Disable schedulers for branches that have been moved to the pool changeset: 1197:c1b712c3ea18
Attachment #383032 - Flags: checked‑in+
Depends on: 498349
Quick note that qm-pxp-trunk07 and qm-plinux-trunk03 were offline at the time, so were not moved over to the pool. See bugs #498019 and #498021.
Now doing: Original name New name qm-plinux-trunk04 talos-rev2-linux07 qm-plinux-trunk05 talos-rev2-linux08 qm-plinux-trunk06 talos-rev2-linux09 qm-pmac-trunk07 talos-rev2-tiger07 qm-pmac-trunk08 talos-rev2-tiger08 qm-pmac-trunk09 talos-rev2-tiger09 qm-pxp-trunk04 talos-rev2-xp09 qm-pxp-trunk05 talos-rev2-xp10 qm-pxp-trunk06 talos-rev2-xp11
And the next batch: Original name New name qm-plinux-talos01 talos-rev2-linux10 qm-plinux-talos02 talos-rev2-linux11 qm-plinux-talos03 talos-rev2-linux12 qm-plinux-talos04 talos-rev2-linux13 qm-pxp-talos01 talos-rev2-xp12 qm-pxp-talos02 talos-rev2-xp13 qm-pxp-talos03 talos-rev2-xp14 qm-pxp-talos04 talos-rev2-xp15 qm-pmac-talos01 talos-rev2-tiger10 qm-pmac-talos02 talos-rev2-tiger11 qm-pmac-talos03 talos-rev2-tiger12 qm-pmac-talos04 talos-rev2-tiger13 qm-pleopard-talos01 talos-rev2-leopard10 qm-pleopard-talos02 talos-rev2-leopard11 qm-pleopard-talos03 talos-rev2-leopard12 qm-pleopard-talos04 talos-rev2-leopard13 qm-pvista-talos01 talos-rev2-vista09 qm-pvista-talos02 talos-rev2-vista10 qm-pvista-talos03 talos-rev2-vista11 qm-pvista-talos04 talos-rev2-vista12
Depends on: 499918
These were done last week: qm-pxp-jss01 talos-rev2-xp16 qm-pxp-jss02 talos-rev2-xp17 qm-pxp-jss03 talos-rev2-xp18
Any other talos slaves left to convert or are we all done here?
Just the fast slaves.
Assignee: catlee → nobody
Component: Release Engineering → Release Engineering: Future
(In reply to comment #13) > Just the fast slaves. Bug#509744 is tracking work to poweroff/reimage the fast talos slaves.
Depends on: 509744
All done here once again.
Status: REOPENED → RESOLVED
Closed: 16 years ago → 16 years ago
Resolution: --- → FIXED
Moving closed Future bugs into Release Engineering in preparation for removing the Future component.
Component: Release Engineering: Future → Release Engineering
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: