Closed Bug 818191 Opened 13 years ago Closed 13 years ago

Try buildbot master functionality on AWS

Categories

(Release Engineering :: General, defect, P2)

x86
Linux

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: jhopkins, Assigned: rail)

References

Details

Attachments

(7 files, 3 obsolete files)

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.
i-58957f6a (10.132.48.232) in us-west-2a has been created for this
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.
Depends on: 818608
Assignee: jhopkins → rail
Severity: normal → major
Priority: -- → P2
Attached patch [configs] limit branches (obsolete) — Splinter Review
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)
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 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+
in production
Attached patch add bm50 (obsolete) — Splinter Review
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)
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');
Attached patch add bm50 (obsolete) — Splinter Review
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)
Attached patch add bm50Splinter Review
* use IP for fabric actions
Attachment #693936 - Attachment is obsolete: true
Attachment #693936 - Flags: review?(catlee)
Attachment #693987 - Flags: review?(catlee)
Comment on attachment 693987 [details] [diff] [review] add bm50 _==| _==| )__) | )_) )___) )) )___) )____))_) _ )____)_____))__)\ \---__|____/|___|___-\\--- ^^^^^^^^^\ oo oo oo oo /~~^^^^^^^ ~^^^^ ~~~~^^~~~~^^~~^^~~~~~ ~~^^ ~^^~ ~^~ ~^ ~^ ~^~~ ~~~^^~
Attachment #693987 - Flags: review?(catlee) → review+
Forgot to the IP to secrets.pp/$masterIPs. Done now.
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)
Attached patch puppet-manifestsSplinter Review
The current changes need to bootstrap the master.
Attachment #694290 - Flags: review?(catlee) → review+
Depends on: 823603
I would like to turn all branches tomorrow
Attachment #694570 - Flags: review?(catlee)
<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
Attachment #694570 - Flags: review?(catlee) → review+
Depends on: 824485
It's time to test it as a tests masters.
Attachment #695495 - Flags: review?(bhearsum)
Attachment #695495 - Flags: review?(bhearsum) → review+
Attachment #695495 - Flags: checked-in+
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.
Attached patch rm bm50Splinter Review
Time to shut it down
Attachment #696291 - Flags: review?(bhearsum)
Attachment #696291 - Flags: review?(bhearsum) → review+
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
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: