This patch series is a follow up to [0]. I did refactor the code that decides which disks / volumes of a guest will be included in a vzdump backup into it's own method as suggested by Fabian [1]. With this it is possible to run the same code for the backup detail view as for the actual backup itself.
More details are in the individual patches. [0] https://pve.proxmox.com/pipermail/pve-devel/2019-December/041011.html [1] https://pve.proxmox.com/pipermail/pve-devel/2019-December/041028.html ------------ pve-guest-common: Aaron Lauterer (1): abstractconfig: add prototype for get_volumes_backup_status PVE/AbstractConfig.pm | 7 +++++++ 1 file changed, 7 insertions(+) qemu-server: Aaron Lauterer (1): backup: refactor disk included in backup to use from other modules PVE/QemuConfig.pm | 30 ++++++++++++++++++++++++++++++ PVE/VZDump/QemuServer.pm | 28 ++++++++++++++-------------- 2 files changed, 44 insertions(+), 14 deletions(-) pve-container: Aaron Lauterer (2): Whitespace cleanup backup: refactor mp included in backup to use from other modules src/PVE/LXC/Config.pm | 38 ++++++++++++++++++++++++++++++ src/PVE/VZDump/LXC.pm | 55 ++++++++++++++++++++++++------------------- 2 files changed, 69 insertions(+), 24 deletions(-) pve-manager: Aaron Lauterer (3): api: backup: add endpoint for disks included in backup gui: dc/backup: move renderers to Utils.js gui: dc/backup: add new backup detail view PVE/API2/Backup.pm | 165 +++++++++++++++++ www/manager6/Utils.js | 91 ++++++++++ www/manager6/dc/Backup.js | 367 ++++++++++++++++++++++++++++++++------ 3 files changed, 564 insertions(+), 59 deletions(-) -- 2.20.1 _______________________________________________ pve-devel mailing list pve-devel@pve.proxmox.com https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
