Closed Bug 726309 Opened 12 years ago Closed 12 years ago

linux VM for buildbot

Categories

(Infrastructure & Operations :: Virtualization, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: dustin, Assigned: afernandez)

References

Details

The Buildbot project currently has a fleet of 8 minis in sjc1.  Obviously, these are going away.  For the most part, the project's windows and OS X needs are being taken care of elsewhere, but not linux.

I think that Mozilla should not cease its commitment to Buildbot as a consequence of an unrelated dc move.  And continuing support is easy with Linux - just a VM.

So, I'd like a VM in scl3 with the following specs:

cb-bbot-linux4 (to not confuse with existing 001..003)
vlan21
1 CPU
2G RAM
20G disk
whatever unlicensed Linux is easiest (probably CentOS 5.5 as a clone of the releng builder image)

mrz, I have an obvious conflict of interest here, as Buildbot maintainer.  Can you ack that this is OK?
(mrz, see comment 0 please)
Component: Server Operations → Server Operations: Virtualization
QA Contact: cshields → dparsons
Is there a scl3 bug we can set this as blocking on?
Just scl3-move.  If you want to open an scl3-esx bug for when ESX is ready to roll, that'd be good by me.  Only if it's useful for you, though.
Well, this will have to wait until after I get the scl3 netapp/esx infra up, which is what I'm building next week. I should have the NetApp done by end of next week I imagine, with the rest of ESX done the week after.
(In reply to Dustin J. Mitchell [:dustin] from comment #0)
> cb-bbot-linux4 (to not confuse with existing 001..003)

Let's get away from the lettered prefixes -- buildbot-linux4
(In reply to Dustin J. Mitchell [:dustin] from comment #0)
> Can you ack that this is OK?

(mrz agreed by email)
Assignee: server-ops → dparsons
I need more information before I can act on this.

This is a template I paste into VM request bugs when required information is missing. Please update this bug with the missing information following the below format:

Host FQDN: hostname1.vlan.dc.mozilla.com
RAM: X GB
CPU: X CPUs
Disk: X GB
Notes: include special details here like ESX host isolation
Host FQDN: buildbot4.community.scl3.mozilla.com
RAM: 2G
Disk: 20G
Notes: Any linux OS is fine - if RHEL is easy, cool, otherwise CentOS is OK too.  This host does not need to be puppetized - I can take care of the setup.
Assignee: dparsons → mburns
Working on this.
Status: NEW → ASSIGNED
Assignee: mburns → afernandez
The VM has be "up" but not online, can't ping gateway.
Essentially Ravi set the flow on the network side but doesn't work.
Public IP: 64.245.223.20
Correct hostname: buildbot-linux4.community.scl3.mozilla.com
(removing previous entry and adding new)
VM is online with requested password (not puppetized as requested)

If there's anything else that needs to be done, please let us know.
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Product: mozilla.org → Infrastructure & Operations
You need to log in before you can comment on or make changes to this bug.