[pve-devel] [PATCH pve-storage 0/4] v4 Support for snapshot LXC backup

[Michael Rasmussen]

V4 Adds support for creating snapshot backups of LXC containers. This more or less makes the plugin feature complete. Only outstanding feature depends on a bug fix in the FreeNAS API which is first scheduled for next stable release: https://bugs.freenas.org/issues/23881 (Targeted for 11.1)

This patch series adds a storage plugin for FreeNAS using the FreeNAS API.
The plugin supports both Qemu and LXC VM. Features supported, see below:

                    VM          CT
create              YES         YES
delete              YES         YES
resize              (YES)       (YES) Note 1
snapshot
   offline          YES         YES
   live             YES         "YES" (state is not saved)
backup
   snapshot         YES         YES
   standby          YES         YES
   offline          YES         YES
clone
   full             YES         YES (Unavailable in GUI)
   linked           YES         YES (Unavailable in GUI)

Note 1: Due to a bug in the FreeNAS API live resizing has been disabled
in the plugin. See https://bugs.freenas.org/issues/24432

Since the plugin attaches disks through the local scsi subsystem via
openiscsi and therefore not uses libiscsi there should be support for
MPIO and authentication. MPIO is not tested since I don't have the
required hardware to do so. Authentication is not enabled but should be
easy to do if the requirements exists.

Michael Rasmussen (4):
  First beta of FreeNAS storage plugin. Missing snapshot backup for LXC
  Proper check if VM/CT is running
  Fix missing $vmid
  Add support for creating LXC snapshot backup

 PVE/Storage.pm               |    2 +
 PVE/Storage/FreeNASPlugin.pm | 1313 ++++++++++++++++++++++++++++++++++++++++++
 PVE/Storage/Makefile         |    2 +-
 PVE/Storage/Plugin.pm        |    2 +-
 4 files changed, 1317 insertions(+), 2 deletions(-)
 create mode 100644 PVE/Storage/FreeNASPlugin.pm

-- 
2.1.4


----

This mail was virus scanned and spam checked before delivery.
This mail is also DKIM signed. See header dkim-signature.