basic bootstrapping of a daemonology ami
fetch the config from further up the hierarchy - if we're dealing with an ec2 master it won't have a master.instance
this completes bootstrapping a daemonology instance

this, in theory, should allow to run ``configure-jailhost`` against it...
this conditional did not work when the master is an ec2 instance
bugfix: don't assume ``/dev/gpt`` already exists

this allows creating zpools on systems that haven't got any gpt labels yet
fix copy&paste artefacts
allow uphrading the zpool during creation

still untested... *blush*
allow to set the latest zpool version directly during creation instead of upgrading post-create
adapt to upstream changes in mr.awsome.ezjail
document debugging configure-jailhost
Revert "this conditional did not work when the master is an ec2 instance"

This reverts commit aee27c722c385c4571d658aac218c4e8b5217776.
remove leftover from f183f4853f851b350a50f091d8e14f75653264f3
update zfs snapshot with current state from https://github.com/fschulze/bsd_ansible_roles/tree/master/roles/bsd_zfs_auto_snapshot
update to newer upstream releases
remove obsolete entries
mention EC2 support
cosmetics
allow installation of a development version via make+buildout
ignore development and build artefacts
fix development make