From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [IPv6:2a01:7e0:0:424::9]) by lore.proxmox.com (Postfix) with ESMTPS id 9643E1FF17C for ; Tue, 16 Dec 2025 14:03:03 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 1B0A8F1A2; Tue, 16 Dec 2025 14:03:12 +0100 (CET) From: Fiona Ebner To: pve-devel@lists.proxmox.com Date: Tue, 16 Dec 2025 14:02:17 +0100 Message-ID: <20251216130230.104772-7-f.ebner@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20251216130230.104772-1-f.ebner@proxmox.com> References: <20251216130230.104772-1-f.ebner@proxmox.com> MIME-Version: 1.0 X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1765890145809 X-SPAM-LEVEL: Spam detection results: 0 AWL -0.016 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment KAM_SHORT 0.001 Use of a URL Shortener for very short URL SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Subject: [pve-devel] [PATCH storage 06/11] bump API age and version X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Proxmox VE development discussion Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: pve-devel-bounces@lists.proxmox.com Sender: "pve-devel" Signed-off-by: Fiona Ebner --- ApiChangeLog | 20 ++++++++++++++++++++ src/PVE/Storage.pm | 4 ++-- 2 files changed, 22 insertions(+), 2 deletions(-) diff --git a/ApiChangeLog b/ApiChangeLog index de41192..5a78ca4 100644 --- a/ApiChangeLog +++ b/ApiChangeLog @@ -6,6 +6,26 @@ without breaking anything unaware of it.) Future changes should be documented in here. +## Version 14: + +* Add new `$snapname` parameter to the `volume_resize()` plugin method + + If specified, the snapshot is the target of the resize operation. This is currently only used in + combination with the `snapshot-as-volume-chain` configuration option before a commit operation. + Plugins that do not support the `snapshot-as-volume-chain` configuration option may either die + when `$snapname` is set or must implement resizing snapshots. + +* Add `virtual-size` to the information returned by the `volume_snapshot_info()` plugin method + + This is the virtual size of the volume at the time the snapshot was taken. This information is + required for storages with the `snapshot-as-volume-chain` configuration option, to make snapshot + removal work correctly in combination with resizing images. + +* Properly document `volume_snapshot_info()` plugin method + + If you already implement this method, check that the returned information is in line with the + documentation. + ## Version 13: * Add new parameter $hints to the `activate_volume()` and `map_volume()` plugin methods diff --git a/src/PVE/Storage.pm b/src/PVE/Storage.pm index c45d35b..24d35a8 100755 --- a/src/PVE/Storage.pm +++ b/src/PVE/Storage.pm @@ -41,11 +41,11 @@ use PVE::Storage::BTRFSPlugin; use PVE::Storage::ESXiPlugin; # Storage API version. Increment it on changes in storage API interface. -use constant APIVER => 13; +use constant APIVER => 14; # Age is the number of versions we're backward compatible with. # This is like having 'current=APIVER' and age='APIAGE' in libtool, # see https://www.gnu.org/software/libtool/manual/html_node/Libtool-versioning.html -use constant APIAGE => 4; +use constant APIAGE => 5; our $KNOWN_EXPORT_FORMATS = ['raw+size', 'tar+size', 'qcow2+size', 'vmdk+size', 'zfs', 'btrfs']; -- 2.47.3 _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel