Closed Bug 776987 Opened 8 years ago Closed 8 years ago

Set up one buildbot master and a foopy on SCL1 for acceptance testing

Categories

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

x86
Linux
task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: armenzg, Assigned: arich)

References

Details

We will need a buildbot master to handle the initial set of pandas.
A foppy is also needed. I believe this can be a Linux foopy since Callek got the work most of the way done.
I will let Callek follow up on spec for the foopy.

We will add more buildbot masters and foopies once we're further down the line of purchasing.

This should do to test the final setup (foopy spec is still to be settle AFAIK).

Thanks in advance!
(In reply to Armen Zambrano G. [:armenzg] - Release Engineer from comment #0)
> We will need a buildbot master to handle the initial set of pandas.
> A foppy is also needed. I believe this can be a Linux foopy since Callek got
> the work most of the way done.
> I will let Callek follow up on spec for the foopy.

CentOS6.2 kickstarted for PuppetAgain. We'll need to add a node-name, etc.
Depends on: 776977
Do we have any preference on hostnames for foopies (do we even still want to call them foopies, since this seems like a good time to break that naming convention if not)?
I've created buildbot-master29.build.scl1.mozilla.com for this purpose.  I'm not sure who on the releng side is setting it up.
Assignee: server-ops-releng → arich
mobile-controllerNN
dustin's proposal works. I would prefer not to have a new name since I really hope we can get rid of the foopy model all together in the next 2-3 quarters; either way works. I can also see how a different spec might need for a new name but could get on the way of our other tools.

I will let Callek have the last say (since he deals with them much more).
Blocks: 777370
(In reply to Amy Rich [:arich] [:arr] from comment #3)
> I've created buildbot-master29.build.scl1.mozilla.com for this purpose.  I'm
> not sure who on the releng side is setting it up.

Filed as bug 777370.
(In reply to Armen Zambrano G. [:armenzg] - Release Engineer from comment #5)
> dustin's proposal works. I would prefer not to have a new name since I
> really hope we can get rid of the foopy model all together in the next 2-3
> quarters; either way works. I can also see how a different spec might need
> for a new name but could get on the way of our other tools.
> 
> I will let Callek have the last say (since he deals with them much more).

Short term, I want foopyNN

Much of our current code, and dashboard code relies on this naming pattern. I *really* want to move away from that requirement and plan to, but I also don't want to have to refactor tons of additional code that can be solved short-term with just naming.
foopy25 and up it is.  As soon as one of the hps is freed up, I can build the one in scl1 for the pandas.
foopy25.build.scl1.mozilla.com has been kickstarted with the puppetized centos 6.2 image.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Could you add the .build.mozilla.org CNAME to DNS ?

$ host buildbot-master29.build.mozilla.org 10.2.74.125
Using domain server:
Name: 10.2.74.125
Address: 10.2.74.125#53
Aliases: 

Host buildbot-master29.build.mozilla.org not found: 3(NXDOMAIN)
It was pointing to mtv1.  Fixed.
Component: Server Operations: RelEng → RelOps
Product: mozilla.org → Infrastructure & Operations
You need to log in before you can comment on or make changes to this bug.