Closed
Bug 660318
Opened 14 years ago
Closed 12 years ago
revise POSIX puppet/buildbot startup process
Categories
(Release Engineering :: General, defect, P5)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: dustin, Unassigned)
Details
(Whiteboard: [buildslaves][puppet])
You can see how slaves are started now:
https://wiki.mozilla.org/ReleaseEngineering/Buildslave_Startup_Process
I'd like to do for *all* slaves what I've proposed for macs in bug 658678:
* a universal run-puppet-until-it's-done shell script
* reboot after N failures (N=10 now)
* block system startup on the script's completion
* already done on Centos
* bug 658678 shows how to do it on macs
* easy to do on Fedora
* Startup buildbot either at graphical login or via another initscript
* ensure SSH logins are enabled before puppet starts
This:
1. separates puppet startup from buildbot startup
2. works the same way everywhere
Finally, along with a basic install of Buildbot, we can include this system in our "clean" reference images (a project that will be making progress in the new relops lab) for all of these platforms. Then a newly-imaged system will immediately come up and try to configure itself from puppet, with no login required. Just sign the cert on the puppet master (or let autosign do it..).
Updated•14 years ago
|
Priority: -- → P5
Whiteboard: [buildslaves] → [buildslaves][puppet]
| Assignee | ||
Updated•12 years ago
|
Product: mozilla.org → Release Engineering
Comment 1•12 years ago
|
||
Dustin: is there anything left to do here after the migration to PuppetAgain? I don't think we really tackled the startup process as part of that move.
| Reporter | ||
Comment 2•12 years ago
|
||
This pretty much got implemented.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•