all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: Max Carrara <m.carrara@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH v1 pve-storage 6/8] pluginbase: document image operation methods
Date: Wed, 26 Mar 2025 15:20:57 +0100	[thread overview]
Message-ID: <20250326142059.261938-7-m.carrara@proxmox.com> (raw)
In-Reply-To: <20250326142059.261938-1-m.carrara@proxmox.com>

Add documentation for the following methods:
- list_images
- create_base
- clone_image
- alloc_image
- free_image

Signed-off-by: Max Carrara <m.carrara@proxmox.com>
Co-authored-by: Maximiliano Sandoval <m.sandoval@proxmox.com>
---
 src/PVE/Storage/PluginBase.pm | 111 ++++++++++++++++++++++++++++++++++
 1 file changed, 111 insertions(+)

diff --git a/src/PVE/Storage/PluginBase.pm b/src/PVE/Storage/PluginBase.pm
index b3ce684..37b1471 100644
--- a/src/PVE/Storage/PluginBase.pm
+++ b/src/PVE/Storage/PluginBase.pm
@@ -721,26 +721,137 @@ sub on_delete_hook {
 
 =cut
 
+=head3 $plugin->list_images($storeid, \%scfg [, $vmid, \@vollist, \%cache])
+
+B<REQUIRED:> Must be implemented in every storage plugin.
+
+Returns a listref of all disk images of a storage. If the storage does not
+support storing disk images, returns an empty listref.
+
+Optionally, if C<\@vollist> is provided, return only disks whose volume ID is
+within C<\@vollist>. Note that this usually has higher precedence than
+C<$vmid>.
+
+C<die>s in case of errors.
+
+This method may reuse L<< cached information via C<\%cache>|/"CACHING EXPENSIVE OPERATIONS" >>.
+
+The returned listref has the following structure:
+
+    [
+	{
+	    ctime => "1689163322", # creation time as unix timestamp
+	    format => "raw",
+	    size => 8589934592, # in bytes!
+	    vmid => 101,
+	    volid => "local-lvm:base-101-disk-0", # volume ID, storage-specific
+	},
+	# [...]
+    ]
+
+=cut
+
 sub list_images {
     my ($class, $storeid, $scfg, $vmid, $vollist, $cache) = @_;
     croak "implement me in sub-class\n";
 }
 
+=head3 $plugin->create_base($storeid, \%scfg, $volname)
+
+B<OPTIONAL:> May be implemented in a storage plugin.
+
+Creates a base volume from an existing volume, allowing the volume to be
+L<< cloned|/"$plugin->clone_image(...)" >>. This cloned volume (usually
+a disk image) may then be used as a base for the purpose of creating linked
+clones. See L<C<PVE::Storage::LvmThinPlugin>> and
+L<C<PVE::Storage::ZFSPoolPlugin>> for example implementations.
+
+On completion, returns the name of the new base volume (the new C<$volname>).
+
+This method is called in the context of C<L<< cluster_lock_storage()|/"cluster_lock_storage(...)" >>>,
+i.e. when the storage is B<locked>.
+
+=cut
+
 sub create_base {
     my ($class, $storeid, $scfg, $volname) = @_;
     croak "implement me in sub-class\n";
 }
 
+=head3 $plugin->clone_image($scfg, $storeid, $volname, $vmid [, $snap])
+
+=head3 $plugin->clone_image(...)
+
+B<REQUIRED:> Must be implemented in every storage plugin.
+
+Clones a disk image or a snapshot of an image, returning the name of the new
+image (the new C<$volname>). Note that I<cloning> here means to create a linked
+clone and not duplicating an image. See L<C<PVE::Storage::LvmThinPlugin>> and
+L<C<PVE::Storage::ZFSPoolPlugin>> for example implementations.
+
+C<die>s in case of an error of if the underlying storage doesn't support
+cloning images.
+
+This method is called in the context of C<L<< cluster_lock_storage()|/"cluster_lock_storage(...)" >>>,
+i.e. when the storage is B<locked>.
+
+=cut
+
 sub clone_image {
     my ($class, $scfg, $storeid, $volname, $vmid, $snap) = @_;
     croak "implement me in sub-class\n";
 }
 
+=head3 $plugin->alloc_image($storeid, $scfg, $vmid, $fmt, $name, $size)
+
+B<REQUIRED:> Must be implemented in every storage plugin.
+
+Allocates a disk image with the given format C<$fmt> and C<$size> in bytes,
+returning the name of the new image (the new C<$volname>). See
+C<L<< plugindata()|/"$plugin->plugindata()" >>> for all disk formats.
+
+Optionally, if given, set the name of the image to C<$name>. If C<$name> isn't
+provided, the next name should be determined via C<L<< find_free_diskname()|/"$plugin->find_free_diskname(...)" >>>.
+
+C<die>s in case of an error of if the underlying storage doesn't support
+allocating images.
+
+This method is called in the context of C<L<< cluster_lock_storage()|/"cluster_lock_storage(...)" >>>,
+i.e. when the storage is B<locked>.
+
+=cut
+
 sub alloc_image {
     my ($class, $storeid, $scfg, $vmid, $fmt, $name, $size) = @_;
     croak "implement me in sub-class\n";
 }
 
+=head3 $plugin->free_image($storeid, $scfg, $volname [, $isBase, $format])
+
+=head3 $plugin->free_image(...)
+
+B<REQUIRED:> Must be implemented in every storage plugin.
+
+Frees (deletes) the disk image given by C<$volname>. Optionally, the image may
+be a base image (C<$isBase>) and have a certain C<$format>. See
+C<L<< plugindata()|/"$plugin->plugindata()" >>> for all disk formats.
+
+If a cleanup is required after freeing the image, returns a reference to a
+subroutine that performs the cleanup, and C<undef> otherwise.
+
+C<die>s in case of errors, if the image has a L<< C<protected> attribute|/"$plugin->get_volume_attribute(...)" >>
+(and may thus not be freed), or if the underlying storage implementation
+doesn't support freeing images.
+
+This method is called in the context of C<L<< cluster_lock_storage()|/"cluster_lock_storage(...)" >>>,
+i.e. when the storage is B<locked>.
+
+B<NOTE:> The returned cleanup subroutine is called in a separate worker and
+should L<< lock|/"$plugin->cluster_lock_storage(...)" >> the underlying storage
+separately.
+
+=cut
+
 sub free_image {
     my ($class, $storeid, $scfg, $volname, $isBase, $format) = @_;
     croak "implement me in sub-class\n";
-- 
2.39.5



_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel


  parent reply	other threads:[~2025-03-26 14:21 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-26 14:20 [pve-devel] [PATCH v1 pve-storage 0/8] Base Module + Documentation for PVE::Storage::Plugin API Max Carrara
2025-03-26 14:20 ` [pve-devel] [PATCH v1 pve-storage 1/8] pluginbase: introduce PVE::Storage::PluginBase with doc scaffold Max Carrara
2025-03-31 15:13   ` Fabian Grünbichler
2025-04-02 16:31     ` Max Carrara
2025-04-03  7:12       ` Fabian Grünbichler
2025-04-03 14:05         ` Max Carrara
2025-03-26 14:20 ` [pve-devel] [PATCH v1 pve-storage 2/8] pluginbase: add high-level plugin API description Max Carrara
2025-03-31 15:13   ` Fabian Grünbichler
2025-04-02 16:31     ` Max Carrara
2025-04-03  7:12       ` Fabian Grünbichler
2025-04-03 14:05         ` Max Carrara
2025-03-26 14:20 ` [pve-devel] [PATCH v1 pve-storage 3/8] pluginbase: document SectionConfig methods Max Carrara
2025-03-31 15:13   ` Fabian Grünbichler
2025-04-02 16:31     ` Max Carrara
2025-04-11 13:49     ` Wolfgang Bumiller
2025-03-26 14:20 ` [pve-devel] [PATCH v1 pve-storage 4/8] pluginbase: document general plugin methods Max Carrara
2025-03-28 12:50   ` Maximiliano Sandoval
2025-03-31 15:12   ` Fabian Grünbichler
2025-04-02 16:31     ` Max Carrara
2025-04-11 14:04       ` Wolfgang Bumiller
2025-03-26 14:20 ` [pve-devel] [PATCH v1 pve-storage 5/8] pluginbase: document hooks Max Carrara
2025-03-28 13:07   ` Maximiliano Sandoval
2025-03-31 15:12   ` Fabian Grünbichler
2025-03-26 14:20 ` Max Carrara [this message]
2025-03-31 15:12   ` [pve-devel] [PATCH v1 pve-storage 6/8] pluginbase: document image operation methods Fabian Grünbichler
2025-04-02 16:32     ` Max Carrara
2025-04-03  7:23       ` Fabian Grünbichler
2025-04-03 14:05         ` Max Carrara
2025-04-11 14:08   ` Wolfgang Bumiller
2025-03-26 14:20 ` [pve-devel] [PATCH v1 pve-storage 7/8] pluginbase: document volume operations Max Carrara
2025-03-31 15:12   ` Fabian Grünbichler
2025-04-02 16:32     ` Max Carrara
2025-04-14  8:24       ` Wolfgang Bumiller
2025-03-26 14:20 ` [pve-devel] [PATCH v1 pve-storage 8/8] pluginbase: document import and export methods Max Carrara
2025-04-01  8:40   ` Fabian Grünbichler
2025-04-01  9:40     ` Fiona Ebner
2025-04-14 14:35       ` Wolfgang Bumiller
2025-04-02 16:32     ` Max Carrara
2025-04-11 13:27 ` [pve-devel] [PATCH v1 pve-storage 0/8] Base Module + Documentation for PVE::Storage::Plugin API Wolfgang Bumiller

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=20250326142059.261938-7-m.carrara@proxmox.com \
    --to=m.carrara@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.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal