Closed Bug 491298 Opened 15 years ago Closed 15 years ago

Rename win32 slaves so they can work with OPSI

Categories

(Release Engineering :: General, defect, P3)

x86
Windows Server 2003
defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: joduinn, Assigned: bhearsum)

References

Details

Attachments

(1 obsolete file)

Last quarter, bhearsum discovered that OPSI requires the win32 slaves to be using netbios-compatible names (ie 15char limit). As experiment, he used the following format, going from:
moz2-win32-slave03.b.m.o
...to:
win32-slave03.b.m.o

1) Does this format seem ok to everyone? Want to make sure we are ok with this before we start renaming all win32 slaves. 

2) Assuming we want to keep try slaves in different pool, what naming convention should we use for them? 

3) This requires changes to buildbot-master, which can be tracked here also. 

4) This required changes to DNS, which should be tracked in a separate dep.bug.

5) While this change is caused by OPSI on win32, it seems reasonable to do the same for slaves on all other platform also. If people agree, I can file separate bugs for that.

Anything else?
(In reply to comment #0)

> 2) Assuming we want to keep try slaves in different pool, what naming
> convention should we use for them? 
> 

Good question. t-win32-slaveNN would work, how do you feel about that?


> 3) This requires changes to buildbot-master, which can be tracked here also. 

> 5) While this change is caused by OPSI on win32, it seems reasonable to do the
> same for slaves on all other platform also. If people agree, I can file
> separate bugs for that.

We really don't need to change buildbot-configs at all. I specifically made sure the moz2-win32-slaveNN names still worked to avoid all the annoying buildbot-configs work, and unnecessary changes to linux/mac. moz2-* style names are 100% valid for all platforms still, so I'd really really rather avoid these changes.


> 4) This required changes to DNS, which should be tracked in a separate dep.bug.
>

This is inherently part of "rename win32 slaves" IMHO (and being done by me), so need for another bug.
Assignee: nobody → bhearsum
Status: NEW → ASSIGNED
Priority: -- → P2
Priority: P2 → P3
Depends on: 495948
Blocks: 495948
No longer depends on: 495948
Depends on: 497091
Depends on: 497092
The moz2 slaves' DNS got updated today, eg:
bitters-2:~ bhearsum$ host win32-slave08.build.mozilla.org
win32-slave08.build.mozilla.org has address 10.2.71.154
bitters-2:~ bhearsum$ host moz2-win32-slave08.build.mozilla.org
moz2-win32-slave08.build.mozilla.org is an alias for win32-slave08.build.mozilla.org.
win32-slave08.build.mozilla.org has address 10.2.71.154

Try slaves are being tracked in the blocking bug (495948).
No longer blocks: 495948
No longer depends on: 497091, 497092
(In reply to comment #2)
> Try slaves are being tracked in the blocking bug (495948).

That is to say, bug 497092
(fixing deps)
Blocks: 495948
Depends on: 497091, 497092
this is donen ow.
Status: ASSIGNED → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Attachment #403485 - Flags: review?(catlee)
Comment on attachment 403485 [details] [diff] [review]
add the new win32 slaves to the masters

wrong bug
Attachment #403485 - Attachment is obsolete: true
Attachment #403485 - Flags: review?(catlee)
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: