A tool to remotely provision, configure and maintain FreeBSD jails
BSDploy – FreeBSD jail provisioning
Its main design goal is to lower the barrier to repeatable jail setups.
Instead of performing updates on production hosts you are encouraged to update the description of your setup, test it against an identically configured staging scenario until it works as expected and then apply the updated configuration to production with confidence.
- provision complete jail hosts from scratch
- describe one or more jail hosts and their jails in a canonical configuration
- declarative configuration – apply Ansible playbooks to hosts and jails
- imperative maintenance – run Fabric scripts against hosts and jails
- configure ZFS pools and filesystems with whole-disk-encryption
- modular provisioning with plugins for VirtualBox and Amazon EC2 and an architecture to support more.
How it works
BSDploy takes the shape of a commandline tool by the name of ploy which is installed on a so-called control host (typically your laptop or desktop machine) with which you then control one or more target hosts. The only two things installed on target hosts by BSDploy are Python and ezjail – everything else stays on the control host.
Here’s what an abbreviated bootstrapping session of a simple website inside a jail on an Amazon EC2 instance could look like:
# ploy start ec-instance [...] # ploy configure jailhost [...] # ploy start webserver [...] # ploy configure webserver [...] # ploy do webserver upload_website
Best of both worlds
Combining a declarative approach for setting up the initial state of a system with an imperative approach for providing maintenance operations on that state has significant advantages:
- Since the imperative scripts have the luxury of running against a well-defined context, you can keep them short and concise without worrying about all those edge cases.
- And since the playbooks needn’t concern themselves with performing updates or other tasks you don’t have to litter them with awkward states such as restarted or updated or – even worse – with non-states such as shell commands.
Under the hood
BSDploy’s scope is quite ambitious, so naturally it does not attempt to do all of the work on its own. In fact, BSDPloy is just a fairly thin, slightly opinionated wrapper around existing excellent tools.
The full documentation is hosted at RTD.
2.2.0 - 2016-11-08
- [feature] add fabric helpers to keep pkg up-to-date on the host, inside jails and for the bsdploy flavour
- [feature] add support for bootstrapping on Digital Ocean by setting bootstrap to digitalocean in the ez-master definition
- [fix] allow setting a non-default zfs root for ezjail by setting jails_zfs_root in the ez-master definition
2.1.0 - 2015-07-26
- [feature] enable jail_parallel_start in rc.conf of jail host
- [fix] import existing zpool in zpool ansible module if the name matches
- [fix] try to attach geli device first in zpool ansible module, in case it already exists, only if that fails create it from scratch
- [fix] properly handle multiple geli encrypted devices in zpool ansible module
- [fix] also honor the ploy_jail_host_pkg_repository variable during bootstrapping (not just jailhost configuration)
- [feature] files copied during bootstrap can be encrypted using the ploy vault commands. This is useful for the private ssh host keys in bootstrap-files.
- [fix] fixed setting of virtualbox defaults, so they can be properly overwritten
- [feature] added new variables: ploy_jail_host_cloned_interfaces/ploy_jail_host_default_jail_interface to give more flexiblity around network interface setup
- [change] dropped support for Ansible versions < 1.8 (supports 1.8.x and 1.9.x now)
- [fix] honour proxy setting while installing ezjail itself, not just during ezjail’s install run (thanks mzs114! https://github.com/ployground/bsdploy/pull/81)
2.0.0 - 2015-03-05
- [feature] add support for http proxies
- [change] deactivate pkg’s auto update feature by default
- [feature] add support for firstboot-freebsd-update (disabled by default)
- [change] [BACKWARDS INCOMPATIBLE] switched from ipfilter to pf - you must convert any existing ipnat_rules to the new pf_nat_rules.
- [feature] provide defaults for VirtualBox instances (less boilerplate)
- [fix] set full /etc/ntp.conf instead of trying to fiddle with an existing one.
- [feature] Support configuration as non-root user (see https://github.com/ployground/bsdploy/issues/62)
- [change] switched to semantic versioning (see http://semver.org)
1.3 - 2014-11-28
- [deprecation] rsync_project is not working in all cases, print a warning
- [feature] added rsync helper, which is a tiny wrapper around the rsync command
- [fix] change format of /usr/local/etc/pkg/repos/FreeBSD.conf so the package repository is properly recognized
- [change] use quarterly package repository everywhere
1.2 - 2014-10-26
- [feature] provide default and by-convention assignment of fabfiles
- [doc] document provisioning of EC2 instances
- [fix] fix string escapes for geli setup in rc.conf
- [feature] make sshd listen address configurable
- [fix] fix permission of periodic scripts in zfs_auto_snapshot role
- [doc] describe how to use a http proxy for mfsBSD
1.1.1 - 2014-09-25
- increase memory for virtual machines in documentation from 512MB to 1024MB
- fix escaping for jail settings in rc.conf preventing jails from starting
1.1.0 - 2014-08-13
- use FreeBSD 10.0 as default for bootstrapping and documentation
- always encode result of templates as utf-8
- fix compatibility with ansible 1.7
1.0.0 - 2014-07-20
- added bsdploy.fabutils with a wrapper for rsync_project
- automatically set env.shell for fabric scripts.
- generate ssh host keys locally during bootstrap if possible.
- set fingerprint option for ezjail master automatically if a ssh host key exists locally.
1.0b4 - 2014-07-08
- remove custom ploy and ploy-ssh console scripts.
1.0b3 - 2014-07-07
- make ploy_virtualbox an optional dependency
1.0b2 - 2014-07-07
- migrate from mr.awsome* dependencies to ploy*
- various bugfixes
- added tests
1.0b1 - 2014-06-17
- Initial public release