[Buildbot] #2855: Use a configuration-management system for *all* configuration
Buildbot trac
trac at buildbot.net
Wed Nov 5 03:11:00 UTC 2014
#2855: Use a configuration-management system for *all* configuration
-------------------+--------------------------------
Reporter: dustin | Owner: dustin
Type: task | Status: assigned
Priority: major | Milestone: sys - on-bb-infra
Version: 0.8.9 | Resolution:
Keywords: |
-------------------+--------------------------------
Changes (by dustin):
* owner: => dustin
* status: new => assigned
* milestone: sys - future => sys - on-bb-infra
Comment:
I've played with Ansible a little, and here's my basic idea:
* We use a single playbook + hosts file, in the buildbot-infra repo
* All hardware systems - service hosts and vm hosts - configure
themselves with 'ansible-pull' on a crontask. We should be able to write
a quick shell script that we can run on a newly installed FreeBSD host
which can install ansible and run ansible-pull for the first time, which
will re-install the crontask (and everything else).
* In order to avoid running sshd in jails, we'll configure jails using
the jexec connector for Ansible, from the service host, also on a
crontask. So basically each service host will be responsible for keeping
its jails up to date.
* Virtual machines will be configured by the VM host using regular SSH-
based ansible.
I still have a lot to learn about password vaults, etc. etc., but how does
this sound for a start?
--
Ticket URL: <http://trac.buildbot.net/ticket/2855#comment:7>
Buildbot <http://buildbot.net/>
Buildbot: build/test automation
More information about the bugs
mailing list