Create a basic Jail management interface

[yaroslav-gwit]

One of our customers has requested a feature, that will help them manage FreeBSD Jails in a similar fashion to VMs: automated provisioning, ZFS clone as a templating mechanism, automatic snapshots and replication, parent/backup detection, prod vs test, REST API functions, access to existing VM network bridges, default and VM-like resource limits, Jail uptime monitoring, start/stop/snapshot using our WebUI, automatic HA failover, etc.

Jails will never be a primary focus of our project, but having even a basic Jail management system will definitely help us in a long run.

I don't plan on publishing any app based, or pre-packaged Jails. Instead I would focus on creating the cross-platform app deployment approaches within Jails, FreeBSD VMs or FreeBSD baremetal hosts using Ansible, shell scripts, installation tutorials, and so on. This way it can be useful to a broader community of admins and users out there, and will boost the FreeBSD exposure.

[yaroslav-gwit]

hoster jail start and hoster jail stop are mostly working now (just a couple of things left to do, like resolv.conf generation on jail start, check and create an empty fstab file if it doesn't exist, and generate an rc.conf file if it doesn't exist).

Moving on to implementing the hoster jail bootstrap -r 13.2-RELEASE functionality. Will keep the issue updated.

[yaroslav-gwit]

• hoster jail start is now fully working
• hoster jail bootstrap has been implemented
• a bug showed up in hoster jail stop, which requires me to implement a mechanism to clean-up Jail mounts:

mount | grep twelveFour

# Example output
devfs on /zroot/vm-encrypted/twelveFour/root_folder/dev (devfs)

Moving on to hoster jail deploy -r 13.2-RELEASE

[yaroslav-gwit]

Done:

• hoster jail deploy is mostly ready, just need to implement the flags to pick different resources on creation: cpu limit, ram limit, network name, ip address, etc
• hoster jail start-all has been implemented
• hoster jail stop-all has been implemented
• hoster jail destroy has been implemented
• Jail name DNS support has been implemented

Still TBD:

• hoster jail cireset (to keep it consistent with the vm counterpart)
• hoster jail set parent
• hoster jail unlock-all