From: Fiona Ebner <f.ebner@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH storage v3 06/11] bump API age and version
Date: Tue, 19 May 2026 13:06:31 +0200 [thread overview]
Message-ID: <20260519110646.25060-7-f.ebner@proxmox.com> (raw)
In-Reply-To: <20260519110646.25060-1-f.ebner@proxmox.com>
Signed-off-by: Fiona Ebner <f.ebner@proxmox.com>
---
ApiChangeLog | 20 ++++++++++++++++++++
src/PVE/Storage.pm | 4 ++--
2 files changed, 22 insertions(+), 2 deletions(-)
diff --git a/ApiChangeLog b/ApiChangeLog
index 7a55ec3..80c5994 100644
--- a/ApiChangeLog
+++ b/ApiChangeLog
@@ -6,6 +6,26 @@ without breaking anything unaware of it.)
Future changes should be documented in here.
+## Version 15:
+
+* 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 14:
* Introduce `get_identity()` plugin method
diff --git a/src/PVE/Storage.pm b/src/PVE/Storage.pm
index 24d35a8..64ea9da 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 => 14;
+use constant APIVER => 15;
# 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 => 5;
+use constant APIAGE => 6;
our $KNOWN_EXPORT_FORMATS = ['raw+size', 'tar+size', 'qcow2+size', 'vmdk+size', 'zfs', 'btrfs'];
--
2.47.3
next prev parent reply other threads:[~2026-05-19 11:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-19 11:06 [PATCH-SERIES storage/qemu-server v3 00/11] fix #7094: external snapshot delete: ensure commit target is large enough Fiona Ebner
2026-05-19 11:06 ` [PATCH storage v3 01/11] plugin: document volume_snapshot_info() method Fiona Ebner
2026-05-19 11:06 ` [PATCH storage v3 02/11] plugin: volume snapshot info: also return virtual size Fiona Ebner
2026-05-19 11:06 ` [PATCH storage v3 03/11] plugin: document volume_resize() method Fiona Ebner
2026-05-19 11:06 ` [PATCH storage v3 04/11] plugin/storage: volume resize: add snapname parameter Fiona Ebner
2026-05-19 11:06 ` [PATCH storage v3 05/11] lvm plugin: snapshot delete: clarify comment about using commit Fiona Ebner
2026-05-19 11:06 ` Fiona Ebner [this message]
2026-05-19 11:06 ` [PATCH storage v3 07/11] partially fix #7094: lvm: snapshot delete: ensure commit target is large enough Fiona Ebner
2026-05-19 11:06 ` [PATCH storage v3 08/11] plugin: volume snapshot info: don't set 'order' for internal snapshots Fiona Ebner
2026-05-19 11:06 ` [PATCH storage v3 09/11] plugin: volume snapshot info: correctly return internal snapshot information Fiona Ebner
2026-05-19 11:06 ` [PATCH storage v3 10/11] plugin: volume snapshot info: do not set 'ext' property Fiona Ebner
2026-05-19 11:06 ` [PATCH qemu-server v3 11/11] partially fix #7094: external snapshot delete: ensure commit target is large enough Fiona Ebner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260519110646.25060-7-f.ebner@proxmox.com \
--to=f.ebner@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.