Script 'mail_helper' called by obssrc Hello community, here is the log from the commit of package velero for openSUSE:Factory checked in at 2024-11-14 16:08:59 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Comparing /work/SRC/openSUSE:Factory/velero (Old) and /work/SRC/openSUSE:Factory/.velero.new.2017 (New) ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "velero" Thu Nov 14 16:08:59 2024 rev:28 rq:1224000 version:1.15.0 Changes: -------- --- /work/SRC/openSUSE:Factory/velero/velero.changes 2024-09-18 15:28:18.660411184 +0200 +++ /work/SRC/openSUSE:Factory/.velero.new.2017/velero.changes 2024-11-14 16:10:01.966144453 +0100 @@ -1,0 +2,93 @@ +Tue Nov 12 06:24:04 UTC 2024 - [email protected] + +- Update to version 1.15.0: + Changelog: https://velero.io/docs/v1.15/ + Upgrading: https://velero.io/docs/v1.15/upgrade-to-1.15/ + * Data mover micro service + Data transfer activities for CSI Snapshot Data Movement are + moved from node-agent pods to dedicate backupPods or + restorePods. This brings many benefits such as: + - This avoids to access volume data through host path, while + host path access is privileged and may involve security + escalations, which are concerned by users. + - This enables users to to control resource (i.e., cpu, memory) + allocations in a granular manner, e.g., control them per + backup/restore of a volume. + - This enhances the resilience, crash of one data movement + activity won't affect others. + - This prevents unnecessary full backup because of host path + changes after workload pods restart. + - For more information, check the design + https://github.com/vmware-tanzu/velero/blob/main/design/Implemented/vgdp-micro-service/vgdp-micro-service.md. + * Item Block concepts and ItemBlockAction (IBA) plugin + Item Block concepts are introduced for resource backups to help + to achieve multiple thread backups. Specifically, correlated + resources are categorized in the same item block and item + blocks could be processed concurrently in multiple threads. + ItemBlockAction plugin is introduced to help Velero to + categorize resources into item blocks. At present, Velero + provides built-in IBAs for pods and PVCs and Velero also + supports customized IBAs for any resources. + In v1.15, Velero doesn't support multiple thread process of + item blocks though item block concepts and IBA plugins are + fully supported. The multiple thread support will be delivered + in future releases. + For more information, check the design + https://github.com/vmware-tanzu/velero/blob/main/design/backup-performance-improvements.md. + * Node selection for repository maintenance job + Repository maintenance are resource consuming tasks, Velero now + allows you to configure the nodes to run repository maintenance + jobs, so that you can run repository maintenance jobs in idle + nodes or avoid them to run in nodes hosting critical workloads. + To support the configuration, a new repository maintenance + configuration configMap is introduced. + For more information, check the document + https://velero.io/docs/v1.15/repository-maintenance/. + * Backup PVC read-only configuration + In 1.15, Velero allows you to configure the data mover + backupPods to read-only mount the backupPVCs. In this way, the + data mover expose process could be significantly accelerated + for some storages (i.e., ceph). + To support the configuration, a new backup PVC configuration + configMap is introduced. + For more information, check the document + https://velero.io/docs/v1.15/data-movement-backup-pvc-configuration/. + * Backup PVC storage class configuration + In 1.15, Velero allows you to configure the storageclass used + by the data mover backupPods. In this way, the provision of + backupPVCs don't need to adhere to the same pattern as workload + PVCs, e.g., for a backupPVC, it only needs one replica, + whereas, the a workload PVC may have multiple replicas. + To support the configuration, the same backup PVC configuration + configMap is used. + For more information, check the document + https://velero.io/docs/v1.15/data-movement-backup-pvc-configuration/. + * Backup repository data cache configuration + The backup repository may need to cache data on the client side + during various repository operations, i.e., read, write, + maintenance, etc. The cache consumes the root file system space + of the pod where the repository access happens. + In 1.15, Velero allows you to configure the total size of the + cache per repository. In this way, if your pod doesn't have + enough space in its root file system, the pod won't be evicted + due to running out of ephemeral storage. + To support the configuration, a new backup repository + configuration configMap is introduced. + For more information, check the document + https://velero.io/docs/v1.15/backup-repository-configuration/. + * Performance improvements + In 1.15, several performance related issues/enhancements are + included, which makes significant performance improvements in + specific scenarios: + - There was a memory leak of Velero server after plugin calls, + now it is fixed, see issue #7925 + - The client-burst/client-qps parameters are automatically + inherited to plugins, so that you can use the same velero + server parameters to accelerate the plugin executions when + large number of API server calls happen, see issue #7806 + - Maintenance of Kopia repository takes huge memory in + scenarios that huge number of files have been backed up, + Velero 1.15 has included the Kopia upstream enhancement to + fix the problem, see issue #7510 + +------------------------------------------------------------------- Old: ---- velero-1.14.1.obscpio New: ---- velero-1.15.0.obscpio ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Other differences: ------------------ ++++++ velero.spec ++++++ --- /var/tmp/diff_new_pack.iC0HXs/_old 2024-11-14 16:10:03.742218624 +0100 +++ /var/tmp/diff_new_pack.iC0HXs/_new 2024-11-14 16:10:03.742218624 +0100 @@ -17,7 +17,7 @@ Name: velero -Version: 1.14.1 +Version: 1.15.0 Release: 0 Summary: Backup program with deduplication and encryption License: Apache-2.0 @@ -25,8 +25,10 @@ URL: https://velero.io Source0: %{name}-%{version}.tar.gz Source1: vendor.tar.gz -BuildRequires: golang-packaging -BuildRequires: golang(API) = 1.22 +BuildRequires: bash-completion +BuildRequires: fish +BuildRequires: go >= 1.22 +BuildRequires: zsh %description velero is a backup program. It supports verification, encryption, @@ -93,8 +95,8 @@ %{buildroot}/%{_bindir}/%{name} completion bash > %{buildroot}%{_datarootdir}/bash-completion/completions/%{name} # create the zsh completion file -mkdir -p %{buildroot}%{_datarootdir}/zsh_completion.d -%{buildroot}/%{_bindir}/%{name} completion zsh > %{buildroot}%{_datarootdir}/zsh_completion.d/_%{name} +mkdir -p %{buildroot}%{_datarootdir}/zsh/site-functions +%{buildroot}/%{_bindir}/%{name} completion zsh > %{buildroot}%{_datarootdir}/zsh/site-functions/_%{name} # create the fish completion file mkdir -p %{buildroot}%{_datadir}/fish/vendor_completions.d @@ -106,18 +108,11 @@ %{_bindir}/%{name} %files bash-completion -%defattr(-,root,root) -%dir %{_datarootdir}/bash-completion/completions/ %{_datarootdir}/bash-completion/completions/%{name} %files zsh-completion -%defattr(-,root,root) -%dir %{_datarootdir}/zsh_completion.d/ -%{_datarootdir}/zsh_completion.d/_%{name} +%{_datarootdir}/zsh/site-functions/_%{name} %files fish-completion -%defattr(-,root,root) -%dir %{_datarootdir}/fish -%dir %{_datarootdir}/fish/vendor_completions.d %{_datarootdir}/fish/vendor_completions.d/%{name}.fish ++++++ _service ++++++ --- /var/tmp/diff_new_pack.iC0HXs/_old 2024-11-14 16:10:03.774219961 +0100 +++ /var/tmp/diff_new_pack.iC0HXs/_new 2024-11-14 16:10:03.778220128 +0100 @@ -3,9 +3,9 @@ <param name="url">https://github.com/vmware-tanzu/velero</param> <param name="scm">git</param> <param name="exclude">.git</param> + <param name="revision">v1.15.0</param> <param name="versionformat">@PARENT_TAG@</param> <param name="versionrewrite-pattern">v(.*)</param> - <param name="revision">v1.14.1</param> <param name="changesgenerate">enable</param> </service> <service name="set_version" mode="manual"> ++++++ _servicedata ++++++ --- /var/tmp/diff_new_pack.iC0HXs/_old 2024-11-14 16:10:03.798220963 +0100 +++ /var/tmp/diff_new_pack.iC0HXs/_new 2024-11-14 16:10:03.802221130 +0100 @@ -1,6 +1,6 @@ <servicedata> <service name="tar_scm"> <param name="url">https://github.com/vmware-tanzu/velero</param> - <param name="changesrevision">8afe3cea8b7058f7baaf447b9fb407312c40d2da</param></service></servicedata> + <param name="changesrevision">1d4f1475975b5107ec35f4d19ff17f7d1fcb3edf</param></service></servicedata> (No newline at EOF) ++++++ velero-1.14.1.obscpio -> velero-1.15.0.obscpio ++++++ /work/SRC/openSUSE:Factory/velero/velero-1.14.1.obscpio /work/SRC/openSUSE:Factory/.velero.new.2017/velero-1.15.0.obscpio differ: char 48, line 1 ++++++ velero.obsinfo ++++++ --- /var/tmp/diff_new_pack.iC0HXs/_old 2024-11-14 16:10:03.842222801 +0100 +++ /var/tmp/diff_new_pack.iC0HXs/_new 2024-11-14 16:10:03.846222968 +0100 @@ -1,5 +1,5 @@ name: velero -version: 1.14.1 -mtime: 1724118663 -commit: 8afe3cea8b7058f7baaf447b9fb407312c40d2da +version: 1.15.0 +mtime: 1730086408 +commit: 1d4f1475975b5107ec35f4d19ff17f7d1fcb3edf ++++++ vendor.tar.gz ++++++ /work/SRC/openSUSE:Factory/velero/vendor.tar.gz /work/SRC/openSUSE:Factory/.velero.new.2017/vendor.tar.gz differ: char 5, line 1
