Closed Bug 628797 Opened 14 years ago Closed 14 years ago

new system to host slave allocator

Categories

(Release Engineering :: General, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: dustin, Unassigned)

References

Details

(Whiteboard: [subject to embargo])

I'd like to get a server set up to run slave allocator on. Preferably dedicated hardware, but not necessarily anything speedy - a recycled Mini would probably do the trick. Distro is not critical - Linux would be nice, Mac is OK. Windows is out. This machine will get traffic from all three datacenters, but it is minimal traffic (one small HTTP request per slave reboot). So for the moment it can be in whichever datacenter is most convenient. As we examine load and redundancy, we may branch it out into multiple servers. Hostname should be something like shepherd-{mtv,mpt,scl}.build.mozilla.org (as appropriate), with a CNAME slavealloc.build.mozilla.org pointing to the same A record. I'm not sure what else you'll need to know.
Blocks: 605278
Ping? Anything I can do to move this along? The code's nearly ready..
This should probably be a VM on the scl kvm cluster. Requires DNS+DHCP changes
Whiteboard: [subject to embargo]
Aiui, DNS+DHCP changes are a checkin into svn -- is that correct? If so, instead of not making any progress on bugs like these during embargoes, could we write the DNS+DHCP patch(es) and attach to a bug? They could potentially be reviewed for obvious mistakes by someone else if that makes sense. It allows for queueing and landing when the embargo is lifted.
This bug is no place to build a bikeshed, but... Treating zone files like code is heavyweight and not entirely appropriate, there are better solutions to this problem. The annoying thing is that this particular VM solution requires DNS/DHCP *first*, so we can't start the work in embargo.
(In reply to comment #2) > This should probably be a VM on the scl kvm cluster. > > Requires DNS+DHCP changes per zandr, this is first step, hence embargo blocks starting here.
per triage, zandr expects this VM to be created tomorrow (thurs 10th)
This is up and reachable from slavealloc.build.scl1.mozilla.com or slavealloc.build.mozilla.org. It is running a modern RHEL6 install. Let me know if anything is wrong or should be corrected.
Assignee: server-ops-releng → nobody
Component: Server Operations: RelEng → Release Engineering
QA Contact: zandr → release
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.