Closed Bug 1007981 Opened 10 years ago Closed 10 years ago

Deploy new .boto configuration for Windows build slaves (GPO)

Categories

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

Product:
Infrastructure & Operations
Component:
RelOps: General
Platform:
All
Windows Server 2008
Type:
task

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: glandium, Assigned: q)

References

Details

The file added in bug 993728 needs updating like in bug 1007976. As it contains secrets, I'm not going to attach it here. How do I get it to you?
Note the file should be deployed on try build slaves only, not non-try build slaves (and if the file from bug 993728 was also deployed on non-try, it should be removed).
Blocks: 1008015
Assignee: relops → q
Blocks: 1009348
There's no way for us to differentiate between try and normal build slaves, but we could deploy it to both.
If you want us to split build and try in scl1, we'd need a full list of which hosts belonged to which class of servers.
The current list is here:
http://hg.mozilla.org/build/buildbot-configs/file/default/mozilla/production_config.py#l40

which expands out to:
w64-ix-slave03
w64-ix-slave32
w64-ix-slave33
w64-ix-slave34
w64-ix-slave35
w64-ix-slave36
w64-ix-slave37
w64-ix-slave38
w64-ix-slave39
w64-ix-slave40
w64-ix-slave41
w64-ix-slave44
w64-ix-slave45
w64-ix-slave46
w64-ix-slave47
w64-ix-slave48
w64-ix-slave49
w64-ix-slave50
w64-ix-slave51
w64-ix-slave52
w64-ix-slave53
w64-ix-slave54
w64-ix-slave55
w64-ix-slave56
w64-ix-slave57
w64-ix-slave58
w64-ix-slave59
w64-ix-slave60
w64-ix-slave61
w64-ix-slave62
w64-ix-slave63
w64-ix-slave64
w64-ix-slave65
w64-ix-slave66
w64-ix-slave67
w64-ix-slave68
w64-ix-slave69
w64-ix-slave70
w64-ix-slave71
w64-ix-slave72
w64-ix-slave73
w64-ix-slave74
w64-ix-slave110
w64-ix-slave159
w64-ix-slave160
w64-ix-slave161
w64-ix-slave162
w64-ix-slave163
w64-ix-slave164
w64-ix-slave165
w64-ix-slave166
w64-ix-slave167
w64-ix-slave168
w64-ix-slave169
w64-ix-slave170
Time flies, and requirements change. We now need a different file deployed. Which doesn't matter much, since the first one didn't make it anyways.

In puppet template terms, this is the content of that file:

[Credentials]
aws_access_key_id = <%=scope.function_secret(["sccache_s3_storage_access_key_id_try"])%>
aws_secret_access_key = <%=scope.function_secret(["sccache_s3_storage_secret_access_key_try"])%>

Please tell me how to communicate the corresponding secrets.
Flags: needinfo?(q)
Blocks: 1013060
Priority: -- → P1
Now that he move train is done and the build try structure has been fixed I will get to rolling this out.
Flags: needinfo?(q)
After multiple tests over the weekend including re-images and OU moves this fix is good and going out to wide distribution.
It looks like it's good on those slaves. Unfortunately, there are more:

b-2008-ix-0018
b-2008-ix-0019
b-2008-ix-0020
b-2008-ix-0021
b-2008-ix-0022
b-2008-ix-0023
b-2008-ix-0024
b-2008-ix-0025
b-2008-ix-0026
b-2008-ix-0027
b-2008-ix-0028
b-2008-ix-0029
b-2008-ix-0030
b-2008-ix-0031
b-2008-ix-0032
b-2008-ix-0033
b-2008-ix-0034
b-2008-ix-0035
b-2008-ix-0036
b-2008-ix-0037
b-2008-ix-0038
b-2008-ix-0039
b-2008-ix-0040
b-2008-ix-0041
b-2008-ix-0042
b-2008-ix-0043
b-2008-ix-0044
b-2008-ix-0045
b-2008-ix-0046
b-2008-ix-0047
b-2008-ix-0048
b-2008-ix-0049
b-2008-ix-0050
b-2008-ix-0051
b-2008-ix-0052
b-2008-ix-0053
b-2008-ix-0054
b-2008-ix-0055
b-2008-ix-0056
b-2008-ix-0057
b-2008-ix-0058
b-2008-ix-0059
b-2008-ix-0060
b-2008-ix-0061
b-2008-ix-0062
b-2008-ix-0063
b-2008-ix-0064
b-2008-ix-0173
b-2008-ix-0174
b-2008-ix-0175
b-2008-sm-0001
b-2008-sm-0002
b-2008-sm-0003
b-2008-sm-0004
b-2008-sm-0005
b-2008-sm-0006
b-2008-sm-0007
b-2008-sm-0008
b-2008-sm-0009
b-2008-sm-0010
b-2008-sm-0011
b-2008-sm-0012
b-2008-sm-0013
b-2008-sm-0014
b-2008-sm-0015
b-2008-sm-0016
b-2008-sm-0017
b-2008-sm-0018
b-2008-sm-0019
b-2008-sm-0020
b-2008-sm-0021
b-2008-sm-0022
b-2008-sm-0023
b-2008-sm-0024
b-2008-sm-0025
b-2008-sm-0026
b-2008-sm-0027
b-2008-sm-0028
b-2008-sm-0029
b-2008-sm-0030
b-2008-sm-0031
b-2008-sm-0032
b-2008-sm-0033
b-2008-sm-0034
b-2008-sm-0035
b-2008-sm-0036
b-2008-sm-0037
b-2008-sm-0038
b-2008-sm-0039
b-2008-sm-0040
b-2008-sm-0041
b-2008-sm-0042
b-2008-sm-0043
b-2008-sm-0044
b-2008-sm-0045
b-2008-sm-0046
b-2008-sm-0047
b-2008-sm-0048
b-2008-sm-0049
b-2008-sm-0050
b-2008-sm-0051
b-2008-sm-0052
b-2008-sm-0053
b-2008-sm-0054
b-2008-sm-0055
b-2008-sm-0056
b-2008-sm-0057
b-2008-sm-0058
b-2008-sm-0059
b-2008-sm-0060
b-2008-sm-0061
b-2008-sm-0062
b-2008-sm-0063
b-2008-sm-0064

The list above is derived from http://hg.mozilla.org/build/buildbot-configs/file/default/mozilla/production_config.py#l40 but not all of them actually exist. Those that actually are listed on slave health are:

b-2008-ix-0018
b-2008-ix-0019
b-2008-ix-0020
b-2008-ix-0021
b-2008-ix-0022
b-2008-ix-0023
b-2008-ix-0024
b-2008-ix-0025
b-2008-ix-0026
b-2008-ix-0027
b-2008-ix-0028
b-2008-ix-0029
b-2008-ix-0173
b-2008-ix-0174
b-2008-ix-0175
b-2008-sm-0001
b-2008-sm-0002
b-2008-sm-0003
Flags: needinfo?(q)
Any of the machines imaged into the try vlan going forward will get the config automatically so we should be good for the machines that do not yet exists.
Flags: needinfo?(q)
What about the others listed that do exist?
Flags: needinfo?(q)
all existing machines are getting the .boto for build and try respectively. The defaukt logic is if machine is a 2008 builder not in loaner atate and not in try then give build key. If machine is not in loaner and in try give try key.
Flags: needinfo?(q)
All machines tested got the files via gpupdate.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.