This is a follow up to [0] but only includes the refactored changes to make it possible to have other features around the VZDump functionality.
It is moving the following logic into its own methods: * which guests are included in a backup job * which volumes / mountpoints of a guest are included in the backup The behavior of VZDump should still be the same. [0] https://pve.proxmox.com/pipermail/pve-devel/2020-January/041268.html pve-manager: Aaron Lauterer (1): backup: move logic to include guests into method PVE/API2/VZDump.pm | 36 +++------------------- PVE/VZDump.pm | 74 ++++++++++++++++++++++++++++++++-------------- 2 files changed, 55 insertions(+), 55 deletions(-) pve-guest-common: Aaron Lauterer (1): abstractconfig: add prototype for get_backup_volumes PVE/AbstractConfig.pm | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) pve-container: Aaron Lauterer (2): vzdump: add reason for mountpoint backup inclusion vzdump: move include logic for mountpoints to method src/PVE/LXC/Config.pm | 48 ++++++++++++++++++++++++++++++++++++------- src/PVE/VZDump/LXC.pm | 31 ++++++++++++++-------------- 2 files changed, 57 insertions(+), 22 deletions(-) qemu-server: Aaron Lauterer (1): vzdump: move include logic for volumes to method PVE/QemuConfig.pm | 31 +++++++++++++++++++++++++++++++ PVE/VZDump/QemuServer.pm | 38 +++++++++++++++++++------------------- 2 files changed, 50 insertions(+), 19 deletions(-) -- 2.20.1 _______________________________________________ pve-devel mailing list pve-devel@pve.proxmox.com https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
