Closed Bug 1239785 Opened 8 years ago Closed 8 years ago

Move some XP test machines to the Windows 7 pool

Categories

(Infrastructure & Operations Graveyard :: CIDuty, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: jgriffin, Assigned: vciobancai)

References

Details

Attachments

(3 files, 1 obsolete file)

+++ This bug was initially created as a clone of Bug #1226729 +++

Let's move another 10 machines from the WinXP pool to the Windows 7 pool. Windows 7 wait times are much longer than XP, and I still need to enable several more e10s suites on XP.
(In reply to Jonathan Griffin (:jgriffin) from comment #0)
> +++ This bug was initially created as a clone of Bug #1226729 +++
> 
> Let's move another 10 machines from the WinXP pool to the Windows 7 pool.
> Windows 7 wait times are much longer than XP, and I still need to enable
> several more e10s suites on XP.

That should be, I need to enable several more e10s suites on Windows 7.
we have the capability to do windows 7 in the cloud, I am not sure this is required.  Q, are we running a pool of windows 7 machines in AWS to compliment our hardware?  Maybe we can add more if that is the case.
Flags: needinfo?(q)
We don't have production capability with w7 in the cloud right now. That's a goal for this quarter.
Flags: needinfo?(q)
Can I disable another 10 xp slaves in order to be moved to win7 pool ?
Disabled the following xp slaves
t-xp32-ix-001.wintest.releng.scl3.mozilla.com
t-xp32-ix-002.wintest.releng.scl3.mozilla.com
t-xp32-ix-003.wintest.releng.scl3.mozilla.com
t-xp32-ix-004.wintest.releng.scl3.mozilla.com
t-xp32-ix-005.wintest.releng.scl3.mozilla.com
t-xp32-ix-006.wintest.releng.scl3.mozilla.com
t-xp32-ix-007.wintest.releng.scl3.mozilla.com
t-xp32-ix-008.wintest.releng.scl3.mozilla.com
t-xp32-ix-009.wintest.releng.scl3.mozilla.com
t-xp32-ix-010.wintest.releng.scl3.mozilla.com
(In reply to Vlad Ciobancai [:vladC] from comment #5)
> Disabled the following xp slaves
> t-xp32-ix-001.wintest.releng.scl3.mozilla.com
> t-xp32-ix-002.wintest.releng.scl3.mozilla.com
> t-xp32-ix-003.wintest.releng.scl3.mozilla.com
> t-xp32-ix-004.wintest.releng.scl3.mozilla.com
> t-xp32-ix-005.wintest.releng.scl3.mozilla.com
> t-xp32-ix-006.wintest.releng.scl3.mozilla.com
> t-xp32-ix-007.wintest.releng.scl3.mozilla.com
> t-xp32-ix-008.wintest.releng.scl3.mozilla.com
> t-xp32-ix-009.wintest.releng.scl3.mozilla.com
> t-xp32-ix-010.wintest.releng.scl3.mozilla.com

Sorry for mistake, I enabled the above slaves and I disabled the following slaves:

t-xp32-ix-053.wintest.releng.scl3.mozilla.com
t-xp32-ix-054.wintest.releng.scl3.mozilla.com
t-xp32-ix-055.wintest.releng.scl3.mozilla.com
t-xp32-ix-056.wintest.releng.scl3.mozilla.com
t-xp32-ix-057.wintest.releng.scl3.mozilla.com
t-xp32-ix-058.wintest.releng.scl3.mozilla.com
t-xp32-ix-059.wintest.releng.scl3.mozilla.com
t-xp32-ix-060.wintest.releng.scl3.mozilla.com
t-xp32-ix-061.wintest.releng.scl3.mozilla.com
t-xp32-ix-062.wintest.releng.scl3.mozilla.com
I took a look, and none of the ones in comment 6 seem to be disabled, but that's okay, because those are the wrong ones listed. I've disabled the following:

t-xp32-ix-153.wintest.releng.scl3.mozilla.com
t-xp32-ix-154.wintest.releng.scl3.mozilla.com
t-xp32-ix-155.wintest.releng.scl3.mozilla.com
t-xp32-ix-156.wintest.releng.scl3.mozilla.com
t-xp32-ix-157.wintest.releng.scl3.mozilla.com
t-xp32-ix-158.wintest.releng.scl3.mozilla.com
t-xp32-ix-159.wintest.releng.scl3.mozilla.com
t-xp32-ix-160.wintest.releng.scl3.mozilla.com
t-xp32-ix-161.wintest.releng.scl3.mozilla.com
t-xp32-ix-162.wintest.releng.scl3.mozilla.com

These will become:

t-w732-ix-244.wintest.releng.scl3.mozilla.com
t-w732-ix-245.wintest.releng.scl3.mozilla.com
t-w732-ix-246.wintest.releng.scl3.mozilla.com
t-w732-ix-247.wintest.releng.scl3.mozilla.com
t-w732-ix-248.wintest.releng.scl3.mozilla.com
t-w732-ix-249.wintest.releng.scl3.mozilla.com
t-w732-ix-250.wintest.releng.scl3.mozilla.com
t-w732-ix-251.wintest.releng.scl3.mozilla.com
t-w732-ix-252.wintest.releng.scl3.mozilla.com
t-w732-ix-253.wintest.releng.scl3.mozilla.com
Attached you can find the patch to increase the pool of slaves
Attachment #8708943 - Flags: review?(kmoir)
Attached the patch to add the slaves in slavealloc DB
Attached file bug1239785_data.sql
Attachment #8708947 - Flags: review?(kmoir)
Assignee: nobody → vlad.ciobancai
Attachment #8708944 - Flags: review?(kmoir)
Updated the patch by decreasing the rang for xp slaves
Attachment #8708943 - Attachment is obsolete: true
Attachment #8708943 - Flags: review?(kmoir)
Attachment #8708949 - Flags: review?(kmoir)
Attachment #8708944 - Flags: review?(kmoir) → review+
Attachment #8708947 - Flags: review?(kmoir) → review+
Attachment #8708949 - Flags: review?(kmoir) → review+
:kmoir should I start pushing the changes or we can wait for the hosts to be moved ?
Flags: needinfo?(kmoir)
You can push the changes, just wait until the new machines are up before enabling in slavealloc :-)
Flags: needinfo?(kmoir)
drive by comment - do we need to adjust graph server to have the machine definitions?  I assume we have new machine names and when talos runs it will fail to upload results.
Usually vlad and alin insert the sql for the graph server
Inventory and nagios updated. Will work on reimaging these after the changes take effect.
Attachment #8708949 - Flags: checked-in+
Slaves added in slavealloc DB and in graphs DB
Machines reimaged, onboard graphics disabled, and machines enabled in slavealloc. These are in production.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Restarted the new win7 slaves in order to start taking jobs.
Product: Release Engineering → Infrastructure & Operations
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: