[Feature Request] Template Management System

[notbasetwo]

(This would be required to solve #4)

A template management system will need to be implemented in the module should provisioning from a template be a desired feature.

For LXC containers, this is relatively trivial as most of the heavy lifting for the deployment and management is done by Proxmox. Just pass the name of the OS Template and allow some user customisation (e.g. friendly name, logo, etc.).

For QEMU, this is a little more complicated due to the wide array of variables (such as OS-type, cloudinit support, specific disk names, etc.). This will either need to be achieved by the system grabbing information about the template before storing information about it, or putting this on to the user.

In addition to the above, whilst LXC containers are already mostly covered with built in template downloads - there will likely need to be some documentation on our part (and potentially even giving out some templates for usage/example) on how to prepare a template for automatic deployment and how to configure it to work with FB.