From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Andrei Perapiolkin <andrei.perepiolkin@open-e.com>
Subject: Re: [pve-devel] Adding new data storage
Date: Thu, 17 Dec 2020 16:35:51 +0100 [thread overview]
Message-ID: <bcfeb6cb-9a1e-9605-24b5-5e97920d1a3c@proxmox.com> (raw)
In-Reply-To: <fd2392ca-f829-24ee-502b-e86712373db0@open-e.com>
Hi,
On 17/12/2020 16:06, Andrei Perapiolkin wrote:
> I would like to add new data storage. This storage would resemble ZFS over iSCSI but will use different API to access storage.
>
What do you mean here, what API will it use? If you want to include this in our
repository some more details would be appreciated. Else, for storages with have
a external plugin system which can be used to include plugins which are proprietary
or otherwise unfit for inclusion.
> Should I create/provide anything besides pve-storage/PVE/Storage/<new-driver>.pm ?
Once above is cleared, then yes, and base it off the closed related
storage plugin - i.e., maybe ZFS, else the base plugin.
>
>
> Is there any documentation I should familiarize myself with beside coding style?
our Perl style guide is here:
https://pve.proxmox.com/wiki/Perl_Style_Guide
Besides that, check the developer documentation in general, especially those two
sections:
https://pve.proxmox.com/wiki/Developer_Documentation#Preparing_Patches
https://pve.proxmox.com/wiki/Developer_Documentation#Software_License_and_Copyright
regards,
Thomas
next prev parent reply other threads:[~2020-12-17 15:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-17 15:06 Andrei Perapiolkin
2020-12-17 15:35 ` Thomas Lamprecht [this message]
2020-12-17 16:16 ` Andrei Perapiolkin
2020-12-17 16:40 ` Thomas Lamprecht
2020-12-17 15:40 ` Dietmar Maurer
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=bcfeb6cb-9a1e-9605-24b5-5e97920d1a3c@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=andrei.perepiolkin@open-e.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox