[pve-devel] [PATCH v3] Add support for custom storage plugins

[Lindsay Mathieson]

On 26/08/2016 6:53 PM, Dmitry Petuhov wrote:
> That's not really API :)
> Just create module with base class PVE::Storage::Plugin, add api() 
> method and reload methods:
>
> type, plugindata, properties, options, parse_volname, filesystem_path, 
> create_base, clone_image, alloc_image, free_image, list_images, 
> status, activate_storage, deactivate_storage, activate_volume, 
> deactivate_volume, volume_resize, volume_snapshot, 
> volume_snapshot_rollback, volume_snapshot_delete, volume_has_feature.
>
> Many of them may be just placeholders, dying with errors or silently 
> returning true, if your module not provides some functionality. See 
> /usr/share/perl5/PVE/Storage/Plugin.pm for lists of parameters and 
> returning values.

Ok, seems straightforward enough.

>
> Although, simple description of parameters and returning values of 
> these methods in comments in Plugin.pm (maybe in POD format?) could be 
> helpful.

That would be nice :)

In reply to earlier concerns about OSS and sharing, for my case I would 
like to experiment with samba storage and having a plugin framework 
makes that much easier rather than hacking the pve src directly. And I 
would most certainly be keeping it OSS.

Maybe useful/popular plugins could be migrated to core PVE?


-- 
Lindsay Mathieson