663195 - Migrate masters off of pm01, pm02, pm03

Status: RESOLVED FIXED

(Release Engineering :: General, defect, P2)

Description

[Chris AtLee [:catlee]]

Now that our new build masters are set up in SJC1, we can start moving stuff off of pm01, pm03.

Comment 1

[Chris AtLee [:catlee]]

Attachment: support release branches in the json

Before shutting off pm01/03 we need bm07/08 to support doing releases. They use build_localconfig.py, which doesn't allow setting ACTIVE_RELEASE_BRANCHES at the moment.

Comment 2

[Chris AtLee [:catlee]]

Attachment: Turn on release branches on bm07/08

Comment 3

[Chris AtLee [:catlee]]

Attachment: enable releases if release_branches is set

Comment 4

[Nick Thomas [:nthomas] (UTC+12)]

Are there any plans to save release logs before these masters get the chop ?

Comment 5

[Chris AtLee [:catlee]]

(In reply to comment #4)
> Are there any plans to save release logs before these masters get the chop ?

other than what's on ftp?

where's a good place for them?

Comment 6

[Chris AtLee [:catlee]]

Attachment: Disable pm01/02/03 in production-masters.json

Comment 7

[[e-mail] (:bhearsum)]

Comment on attachment 543994 [details] [diff] [review]
Disable pm01/02/03 in production-masters.json

Any reason to keep the entries around at all?

Comment 8

[Chris AtLee [:catlee]]

(In reply to comment #7)
> Any reason to keep the entries around at all?

I'd like to for a little while so that buildapi will continue to work for builds that happened on them.

Comment 9

[Chris AtLee [:catlee]]

shadow-central poller and addon-sendchanges need to be moved as well.

Comment 10

[Chris AtLee [:catlee]]

Attachment: remove assumption about pb port

Comment 11

[Chris AtLee [:catlee]]

pm01/pm03 halted

Comment 12

[Chris AtLee [:catlee]]

pm02 halted