Closed Bug 985482 Opened 12 years ago Closed 12 years ago

Move machines from scl1->scl3 to test platforms on new vlans

Categories

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

x86
macOS
task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: arich, Assigned: arich)

References

Details

We want to take at least one machine of each type that needs to move out of scl1 that does not already exist in scl3 and make sure that dns, dhcp, and the network flows are all functional for the platform. b-linux64-hp-001.build.scl1.mozilla.com -> b-linux64-hp-0001.try.releng.scl3.mozilla.com (scl3-releng-vlan264) bld-linux64-ix-027.build.scl1.mozilla.com -> b-linux64-ix-0001.build.releng.scl3.mozilla.com (scl3-releng-vlan252) w64-ix-slave03.winbuild.scl1.mozilla.com -> b-2008-ix-0018.wintry.releng.scl3.mozilla.com (scl3-releng-vlan244) talos-r4-snow-001.build.scl1.mozilla.com -> t-snow-r4-0001.test.releng.scl3.mozilla.com (scl3-releng-vlan256) callek will handle removing these from the pool and updating buildbot/slavealloc/puppet/etc. dcops will move the machines and update inventory. relops will reimage each machine and hand them back to releng for validation.
Depends on: 985115
Depends on: 985625
Since the w64-ix machine was loaned out, this list is now: b-linux64-hp-001.build.scl1.mozilla.com -> b-linux64-hp-0001.try.releng.scl3.mozilla.com (scl3-releng-vlan264) bld-linux64-ix-027.build.scl1.mozilla.com -> b-linux64-ix-0001.build.releng.scl3.mozilla.com (scl3-releng-vlan252) w64-ix-slave31.winbuild.scl1.mozilla.com -> b-2008-ix-0019.wintry.releng.scl3.mozilla.com (scl3-releng-vlan244) talos-r4-snow-001.build.scl1.mozilla.com -> t-snow-r4-0001.test.releng.scl3.mozilla.com (scl3-releng-vlan256)
Depends on: 985701
I've commented out the old hosts in puppet-nagios since they're yanked from DNS which stalls puppet runs.
all machines have been moved, all but b-2008-ix-0019.wintry.releng.scl3.mozilla.com are ready to test (we're still working out some kinks with the imaging for the wintry vlan). I'll submit a separate bug to update nagios once we are confident these are working.
STATUS CHECKPOINT: b-2008-ix-0019.wintry.releng.scl3.mozilla.com - needs: https://wiki.mozilla.org/ReleaseEngineering/How_To/Adjust_SSH_keys_on_a_slave b-linux64-hp-0001.try.releng.scl3.mozilla.com b-linux64-ix-0001.build.releng.scl3.mozilla.com t-snow-r4-0001.test.releng.scl3.mozilla.com all imaged fine, rebooted into production
(In reply to Justin Wood (:Callek) from comment #4) > STATUS CHECKPOINT: > b-linux64-hp-0001.try.releng.scl3.mozilla.com Looking good: https://secure.pub.build.mozilla.org/builddata/reports/slave_health/slave.html?name=b-linux64-hp-0001 > b-linux64-ix-0001.build.releng.scl3.mozilla.com Looking good: https://secure.pub.build.mozilla.org/builddata/reports/slave_health/slave.html?name=b-linux64-ix-0001 > t-snow-r4-0001.test.releng.scl3.mozilla.com Looking good: https://secure.pub.build.mozilla.org/builddata/reports/slave_health/slave.html?name=t-snow-r4-0001
(In reply to Justin Wood (:Callek) from comment #4) > STATUS CHECKPOINT: > > b-2008-ix-0019.wintry.releng.scl3.mozilla.com - needs: > > https://wiki.mozilla.org/ReleaseEngineering/How_To/Adjust_SSH_keys_on_a_slave Just enabled in production
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
And to be clear, the production run on windows has had 2 green (successful) jobs since its deployment today
You need to log in before you can comment on or make changes to this bug.