875490 - make aws stop idle more intelligent about buildbot master http port

Status: RESOLVED FIXED

(Release Engineering :: General, defect)

Description

[[e-mail] (:bhearsum)]

Attachment: servo in production-masters.json

Right now it looks for pbport - 1000, which isn't working well for servo now that we've got a rw and ro WebStatus. It should probably look at production-masters.json instead...

Attached is a patch to add the servo master...does it make sense to do that, since it's a completely different master?

Comment 1

[Rail Aliiev [:rail]]

Comment on attachment 753467 [details] [diff] [review]
servo in production-masters.json

I think this is not a bad idea, since we manage the masters.

Comment 2

[[e-mail] (:bhearsum)]

Attachment: lookup http port in production masters

Tested this with both a file + http link. Works fine as long you don't use SSL. I won't wait for Catlee's opinion on the production masters patch before landing, but I'd still like it after the fact. If we decide we should keep the masters separate, I can modify this patch to support multiple production masters files.

Comment 3

[[e-mail] (:bhearsum)]

Comment on attachment 755552 [details] [diff] [review]
lookup http port in production masters

Updated cruncher's local repo, too.

Comment 4

[[e-mail] (:bhearsum)]

Comment on attachment 753467 [details] [diff] [review]
servo in production-masters.json

Backed this out because it broke setup-masters.py --test, and there was no clear fix:
+ ./test-masters.sh
Traceback (most recent call last):
  File "./setup-master.py", line 343, in <module>
    dedupe=dedupe)
  File "./setup-master.py", line 231, in load_masters_json
    raise AssertionError("What is a %s role?" % m['role'])
AssertionError: What is a servo role?

Comment 5

[[e-mail] (:bhearsum)]

Doesn't really block...I've been shutting things down by hand for now.

Comment 6

[Chris AtLee [:catlee]]

Comment on attachment 753467 [details] [diff] [review]
servo in production-masters.json

looks ok for starters. if we get to the point of needing split masters for servo (or other projects), we may want to split this file up.

Comment 7

[[e-mail] (:bhearsum)]

Attachment: add support for ignored roles

Best solution I could come up with to solve the setup-master.py problem. It has the added bonus of removing a hack related to universal master testing.

Comment 8

[[e-mail] (:bhearsum)]

Attachment: ignored roles for manage masters

Same thing for manage masters.

Comment 9

[[e-mail] (:bhearsum)]

Comment on attachment 753467 [details] [diff] [review]
servo in production-masters.json

Trying again...

Comment 10

[[e-mail] (:bhearsum)]

This worked:
2013-06-04 07:11:05,516 - servo-linux64 - stopped 1
2013-06-04 07:11:05,516 - tst-linux32 - stopped 16

Comment 11

[Armen [:armenzg]]

Live in production.