rtyler
/
puppet-jail
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
FreeBSD Jails with Puppet
51 Commits 4 Branches 19 Tags 219 KiB
Ruby 95.8%
HTML 2.6%
Puppet 1.6%
Go to file
Zach Leslie 4983086ac8 (rel) 2.0.6 2016-03-08 14:27:14 -08:00
lib/puppet Update regex for hostname matching 2016-02-21 16:30:12 -08:00
manifests Iocage service only need be set enabled 2016-03-08 14:26:08 -08:00
spec Update regex for hostname matching 2016-02-21 16:30:12 -08:00
templates Improve the deployment of jails 2014-02-09 12:45:13 -08:00
tests Lint the test 2014-10-18 20:34:00 -07:00
.gitignore Ignore things 2014-10-18 20:17:23 -07:00
.rspec Import testing from skeleton 2014-10-18 20:01:29 -07:00
.travis.yml Update the tested Puppet version 2015-08-16 14:28:55 -07:00
Gemfile Improve testing 2015-08-16 14:20:20 -07:00
README.md Fix boot parameter in readme 2015-08-23 18:11:42 -07:00
Rakefile Improve testing 2015-08-16 14:20:20 -07:00
metadata.json (rel) 2.0.6 2016-03-08 14:27:14 -08:00

README.md

FreeBSD Jail management with Puppet

Build Status

Manage FreeBSD jails with Puppet, leveraging iocage for jail management.

Setup

This module expects to be the only jail manager on a given system. Each system where jails will be managed needs to include the jail::setup class as well.

include jail::setup

This simply installs 'iocage' and removes '/etc/jail.conf'.

This allows the type to use the correct jail without having to specify the pool on each jail.

A simple jail

jail { 'myjail1':
  ensure   => present,
  state    => 'up',
  ip4_addr => 'em0|10.0.0.10/24',
  ip6_addr => 'em0|fc00::10/64',
  hostname => 'myjail1.example.com',
  boot     => 'on'
}

Note the ip4_addr and the ip6_addr properties take an interface name and an IP address seperated by a pipe character. This value is passed directly to iocage(8). You may wish to read the man page.