Forge Home

Modules

Resources

PuppetEcosystemPuppet CommunityUpdates

iocell

Jail management with Puppet, using iocell
Project URLRSS FeedReport issues

6,313 downloads

6,140 latest version

2.4 quality score

We run a couple of automated
scans to help you access a
module's quality. Each module is
given a score based on how well
the author has formatted their
code and documentation and
modules are also checked for
malware using VirusTotal.

Please note, the information below
is for guidance only and neither of
these methods should be considered
an endorsement by Puppet.

Version information

  • 4.0.2 (latest)
  • 4.0.0
released Mar 4th 2018
This version is compatible with:
  • Puppet Enterprise 2017.2.x, 2017.1.x, 2016.5.x, 2016.4.x
  • Puppet >= 4.0.0 < 5.0.0

Start using this module

  • r10k or Code Manager
  • Bolt
  • Manual installation
  • Direct download

Add this module to your Puppetfile:

mod 'hackerhorse-iocell', '4.0.2'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

bolt module add hackerhorse-iocell
Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install hackerhorse-iocell --version 4.0.2

Direct download is not typically how you would use a Puppet module to manage your infrastructure, but you may want to download the module in order to inspect the code.

Download
Tags: freebsd, zfs, containers, jails, iocell

Documentation

hackerhorse/iocell — version 4.0.2 Mar 4th 2018

FreeBSD Jail management with Puppet, using iocell

Puppet Forge

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

Compatibility Warning

This module conflicts with zleslie/jail

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 'iocell' 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|127.0.1.0/29',
  ip6_addr  => 'em0|fc00::10/64',
  hostname  => 'myjail1.example.com',
  boot      => 'on',
  pcpu      => '20'
  memoryuse => '4G',
  quota     => '15G',
  release   => '11.1-RELEASE'
  rlimits   => 'on',
  user_data => template('mysite/user_data.sh.erb'),
}

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