Closed
Bug 818191
Opened 13 years ago
Closed 13 years ago
Try buildbot master functionality on AWS
Categories
(Release Engineering :: General, defect, P2)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: jhopkins, Assigned: rail)
References
Details
Attachments
(7 files, 3 obsolete files)
2.95 KB,
patch
|
catlee
:
review+
rail
:
checked-in+
|
Details | Diff | Splinter Review |
2.53 KB,
patch
|
catlee
:
review+
rail
:
checked-in+
|
Details | Diff | Splinter Review |
632 bytes,
patch
|
catlee
:
review+
rail
:
checked-in+
|
Details | Diff | Splinter Review |
6.00 KB,
patch
|
Details | Diff | Splinter Review | |
655 bytes,
patch
|
catlee
:
review+
rail
:
checked-in+
|
Details | Diff | Splinter Review |
2.40 KB,
patch
|
bhearsum
:
review+
rail
:
checked-in+
|
Details | Diff | Splinter Review |
1.80 KB,
patch
|
bhearsum
:
review+
rail
:
checked-in+
|
Details | Diff | Splinter Review |
We need to know if using a buildbot master inside AWS will work. If not, then we may need to get more in-house VM capacity, which will take a while. So the sooner we know if an AWS build master works the better.
The complication here is a combination of 1) we have no centos5.5 images in aws; 2) we have no centos6 puppet support for build masters
The existing puppet manfifests for build masters assume centos 5.x in a bunch of places...it may work with minor adjustments for centos6. This is with our old style puppet (puppet-manifests). Massimo is working on puppetagain manifests for centos6.
Comment 1•13 years ago
|
||
i-58957f6a (10.132.48.232) in us-west-2a has been created for this
Reporter | ||
Comment 2•13 years ago
|
||
Massimo's work will not be ready in time for me to make use of, so the options are either:
a) get the old manifests working with centos6, or
b) set up the master by hand.
Reporter | ||
Updated•13 years ago
|
Assignee: jhopkins → rail
Assignee | ||
Updated•13 years ago
|
Severity: normal → major
Priority: -- → P2
Assignee | ||
Comment 3•13 years ago
|
||
The idea is to limit a master to a branch so we don't touch production quality builds. The patch helps to limit branches to be tested in staging. Worked fine for me.
Attachment #692956 -
Flags: review?(catlee)
Assignee | ||
Comment 4•13 years ago
|
||
A little enhancement to stringify sometimes sneaking in unicode due to json/simplejson - buildbot uses "assert isinstance(b, str)" for builderNames.
Attachment #692956 -
Attachment is obsolete: true
Attachment #692956 -
Flags: review?(catlee)
Attachment #692966 -
Flags: review?(catlee)
Comment 5•13 years ago
|
||
Comment on attachment 692966 [details] [diff] [review]
[configs] limit branches
Review of attachment 692966 [details] [diff] [review]:
-----------------------------------------------------------------
r+ with the unicode fixes
Attachment #692966 -
Flags: review?(catlee) → review+
Assignee | ||
Comment 6•13 years ago
|
||
Comment on attachment 692966 [details] [diff] [review]
[configs] limit branches
http://hg.mozilla.org/build/buildbot-configs/rev/e8320b597f19
Attachment #692966 -
Flags: checked-in+
Assignee | ||
Comment 8•13 years ago
|
||
The patch adds and enables bm50, limiting it to the build-system branch.
Two thing to pay attention at:
* "scl3" as "datacentre"
* IP address as hostname
Attachment #693918 -
Flags: review?(catlee)
Assignee | ||
Comment 9•13 years ago
|
||
I created a new pool for slaves to be attached to this master:
INSERT INTO pools (name) VALUES ('build-aws-pp');
SELECT * FROM pools WHERE name = 'build-aws-pp'; -- got 45 for ID
INSERT INTO slave_passwords (poolid, distroid, password) VALUES (45, 15, 'xxx');
Assignee | ||
Comment 10•13 years ago
|
||
I've just realized that buildbot-configs/update-master-json.py uses `hostname` to figure out which configs should be applied.
Attachment #693918 -
Attachment is obsolete: true
Attachment #693918 -
Flags: review?(catlee)
Attachment #693936 -
Flags: review?(catlee)
Assignee | ||
Comment 11•13 years ago
|
||
* use IP for fabric actions
Attachment #693936 -
Attachment is obsolete: true
Attachment #693936 -
Flags: review?(catlee)
Attachment #693987 -
Flags: review?(catlee)
Comment 12•13 years ago
|
||
Comment on attachment 693987 [details] [diff] [review]
add bm50
_==|
_==| )__) |
)_) )___) ))
)___) )____))_)
_ )____)_____))__)\
\---__|____/|___|___-\\---
^^^^^^^^^\ oo oo oo oo /~~^^^^^^^
~^^^^ ~~~~^^~~~~^^~~^^~~~~~
~~^^ ~^^~ ~^~ ~^ ~^
~^~~ ~~~^^~
Attachment #693987 -
Flags: review?(catlee) → review+
Assignee | ||
Comment 13•13 years ago
|
||
Comment on attachment 693987 [details] [diff] [review]
add bm50
http://hg.mozilla.org/build/tools/rev/63efa1c676db
Attachment #693987 -
Flags: checked-in+
Assignee | ||
Comment 14•13 years ago
|
||
Forgot to the IP to secrets.pp/$masterIPs. Done now.
Assignee | ||
Comment 15•13 years ago
|
||
So far the finished builds have been green (since I added the IP address to signing servers). It'd be great to increase load gradually and see how it behaves for 3-4 hours, then enable it fully.
Let's start by adding Thunderbird and projects.
Attachment #694290 -
Flags: review?(catlee)
Assignee | ||
Comment 16•13 years ago
|
||
The current changes need to bootstrap the master.
Updated•13 years ago
|
Attachment #694290 -
Flags: review?(catlee) → review+
Assignee | ||
Comment 17•13 years ago
|
||
Comment on attachment 694290 [details] [diff] [review]
Increase load on bm50
http://hg.mozilla.org/build/tools/rev/f58c08e73bb4
Attachment #694290 -
Flags: checked-in+
Assignee | ||
Comment 18•13 years ago
|
||
I would like to turn all branches tomorrow
Attachment #694570 -
Flags: review?(catlee)
Comment 19•13 years ago
|
||
<nagios-releng> Thu 16:39:19 PST [403] 10.132.48.232:swap is CRITICAL: SWAP CRITICAL - 100% free (0 MB out of 0 MB) (http://m.allizom.org/swap)
[cltbld@buildbot-master50 ~]$ free -m
total used free shared buffers cached
Mem: 7467 1384 6082 0 134 830
-/+ buffers/cache: 419 7047
Swap: 0 0 0
so no swap configured, I've acked the alert to this bug.
For comparison:
[cltbld@buildbot-master12 ~]$ free -m
total used free shared buffers cached
Mem: 5970 5442 527 0 683 1670
-/+ buffers/cache: 3088 2881
Swap: 6149 0 6149
Updated•13 years ago
|
Attachment #694570 -
Flags: review?(catlee) → review+
Assignee | ||
Comment 20•13 years ago
|
||
Comment on attachment 694570 [details] [diff] [review]
release the beast!
http://hg.mozilla.org/build/tools/rev/562761934a56
Attachment #694570 -
Flags: checked-in+
Assignee | ||
Comment 21•13 years ago
|
||
It's time to test it as a tests masters.
Attachment #695495 -
Flags: review?(bhearsum)
Updated•13 years ago
|
Attachment #695495 -
Flags: review?(bhearsum) → review+
Assignee | ||
Comment 22•13 years ago
|
||
Comment on attachment 695495 [details] [diff] [review]
convert bm50 into a tests master
http://hg.mozilla.org/build/tools/rev/420f9fd1da86
Attachment #695495 -
Flags: checked-in+
Assignee | ||
Comment 23•13 years ago
|
||
Since it's been under load, bm50-build1's (m1.large) max CPU utilization was ~12% on Friday. Load average was around 0.1-0.3 during that peak.
Assignee | ||
Comment 24•13 years ago
|
||
Time to shut it down
Attachment #696291 -
Flags: review?(bhearsum)
Updated•13 years ago
|
Attachment #696291 -
Flags: review?(bhearsum) → review+
Assignee | ||
Comment 25•13 years ago
|
||
Comment on attachment 696291 [details] [diff] [review]
rm bm50
http://hg.mozilla.org/build/tools/rev/76c1243fba73
Attachment #696291 -
Flags: checked-in+
Assignee | ||
Comment 26•13 years ago
|
||
All done here.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Summary: Create buildbot master instance on AWS → Try buildbot master functionality on AWS
Updated•12 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•