At this stage already built jails aren't permanent. Thus, each time the builder is deployed, every jail must be created again. While this is quite fast for architectures that support binary creation, it takes a lot of time for jails that must be built from source. E.g., this is the case for arm.armv6.
To save time and resources, already built jails should be permanent. One idea to approach this is to save jails on a separate EBS drive that can be re-attached. Practically, this can be done by structuring the skeleton in different layers, as shortly discusses here: https://groups.google.com/forum/#!topic/terraform-tool/lZzspHANlSA
An additional advantage of this approach is that the poudriere filesystem can be created on ZFS. I just started working on this in branch ftr/perm-ebs .
It's not only /usr/local/poudriere, additionally, /usr/local/etc/poudriere.{d,conf} should also be stored on the zpool. Probably symlinking makes sense...
At this stage already built jails aren't permanent. Thus, each time the builder is deployed, every jail must be created again. While this is quite fast for architectures that support binary creation, it takes a lot of time for jails that must be built from source. E.g., this is the case for
arm.armv6
.To save time and resources, already built jails should be permanent. One idea to approach this is to save jails on a separate EBS drive that can be re-attached. Practically, this can be done by structuring the skeleton in different layers, as shortly discusses here: https://groups.google.com/forum/#!topic/terraform-tool/lZzspHANlSA
An additional advantage of this approach is that the
poudriere
filesystem can be created on ZFS. I just started working on this in branch ftr/perm-ebs .