[Buildbot] #2855: Use a configuration-management system for *all* configuration (was: Use a configuration-management system)
Buildbot trac
trac at buildbot.net
Wed Nov 5 00:17:27 UTC 2014
#2855: Use a configuration-management system for *all* configuration
-------------------+---------------------------
Reporter: dustin | Owner:
Type: task | Status: new
Priority: major | Milestone: sys - future
Version: 0.8.9 | Resolution:
Keywords: |
-------------------+---------------------------
Comment (by dustin):
I'd like to very quickly get to the point where all changes to the
buildbot infra are made by ansible, and not by hand. I don't really want
to burn time trying multiple tools -- Ansible puts us all on an equal
(n00b!) footing, so let's just use that.
That will involve:
* setting up ansible
* building out ansible configurations for each host and each jail within
the host
* rebuilding jails one by one from ansible
* rebuilding hosts (perhaps in a "fake" way in a jail) to ensure that all
details are handled by ansible. In other words, we need to demonstrate or
prove convincingly that the *entire* infrastructure can be rebuilt from
the buildbot-infra repository. This is particularly important since we're
running on non-redundant hardware and should expect a catastrophic failure
at some point. Recovery by re-installation in that case is OK, but
recovery by guessing is not.
--
Ticket URL: <http://trac.buildbot.net/ticket/2855#comment:6>
Buildbot <http://buildbot.net/>
Buildbot: build/test automation
More information about the bugs
mailing list