yesBad/pve-storage
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

plugin api: bump api version and age

Browse Source 
Introduce qemu_blockdev_options() plugin method.

In terms of the plugin API only, adding the qemu_blockdev_options()
method is a fully backwards-compatible change. When qemu-server will
switch to '-blockdev' however, plugins where the default implemenation
is not sufficient, will not be usable for virtual machines anymore.
Therefore, this is intended for the next major release, Proxmox VE 9.

Signed-off-by: Fiona Ebner <f.ebner@proxmox.com>
FG: fixed typo, add paragraph break

Signed-off-by: Fabian Grünbichler <f.gruenbichler@proxmox.com>
This commit is contained in:
Fiona Ebner
2025-07-02 18:27:49 +02:00
committed by Fabian Grünbichler
parent 3bba744b0b
commit 280bb6be77
2 changed files with 18 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

16
ApiChangeLog
View File

@ -6,6 +6,22 @@ without breaking anything unaware of it.)
Future changes should be documented in here. Future changes should be documented in here.
## Version 12:
* Introduce `qemu_blockdev_options()` plugin method
Proxmox VE will switch to the more modern QEMU command line option `-blockdev` replacing `-drive`.
With `-drive`, it was enough to specify a path, where special protocol paths like `iscsi://` were
also supported. With `-blockdev`, the data is more structured, a driver needs to be specified
alongside the path to an image and each driver supports driver-specific options. Most storage
plugins should be fine using driver `host_device` in case of a block device and `file` in case of
a file and no special options. See the default implemenation of the base plugin for guidance, also
if the plugin uses protocol paths. Implement this method for Proxmox VE 9.
See `$allowed_qemu_blockdev_options` in `PVE/Storage.pm` for currently allowed drivers and option.
Feel free to request allowing more drivers or options on the pve-devel mailing list based on your
needs.
## Version 11: ## Version 11:
* Allow declaring storage features via plugin data * Allow declaring storage features via plugin data

4
src/PVE/Storage.pm
View File

@ -41,11 +41,11 @@ use PVE::Storage::BTRFSPlugin;
use PVE::Storage::ESXiPlugin; use PVE::Storage::ESXiPlugin;
# Storage API version. Increment it on changes in storage API interface. # Storage API version. Increment it on changes in storage API interface.
use constant APIVER => 11; use constant APIVER => 12;
# Age is the number of versions we're backward compatible with. # Age is the number of versions we're backward compatible with.
# This is like having 'current=APIVER' and age='APIAGE' in libtool, # This is like having 'current=APIVER' and age='APIAGE' in libtool,
# see https://www.gnu.org/software/libtool/manual/html_node/Libtool-versioning.html # see https://www.gnu.org/software/libtool/manual/html_node/Libtool-versioning.html
use constant APIAGE => 2; use constant APIAGE => 3;
our $KNOWN_EXPORT_FORMATS = ['raw+size', 'tar+size', 'qcow2+size', 'vmdk+size', 'zfs', 'btrfs']; our $KNOWN_EXPORT_FORMATS = ['raw+size', 'tar+size', 'qcow2+size', 'vmdk+size', 'zfs', 'btrfs'];