From: Andrei Perapiolkin <andrei.perepiolkin@open-e.com>
To: Thomas Lamprecht <t.lamprecht@proxmox.com>,
Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
dietmar@proxmox.com
Subject: Re: [pve-devel] Adding new data storage
Date: Thu, 17 Dec 2020 18:16:40 +0200 [thread overview]
Message-ID: <7e06eb9c-a298-60bf-cfe3-15b6a630fc98@open-e.com> (raw)
In-Reply-To: <bcfeb6cb-9a1e-9605-24b5-5e97920d1a3c@proxmox.com>
Hi Thomas, Dietmar,
Thanks for the quick reply.
Sorry for ambiguity with "API". By API I meant usage of SSH to send
commands to Open-E JovianDSS.
The problem here is that this commands are different from the one used
in "ZFS over iSCSI" plugin.
That is why Im thinking about adding separate plugin.
Also this plugin is going to be OpenSource and API is public, so there
should not be any legal complications with adding it to Proxmox repo.
My concern is whether I should provide additional CI, Unit tests or
something else?
Coding style goes without saying.
On 12/17/20 5:35 PM, Thomas Lamprecht wrote:
> 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.
Best regards,
Andrei Perepiolkin
next prev parent reply other threads:[~2020-12-17 16:23 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
2020-12-17 16:16 ` Andrei Perapiolkin [this message]
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=7e06eb9c-a298-60bf-cfe3-15b6a630fc98@open-e.com \
--to=andrei.perepiolkin@open-e.com \
--cc=dietmar@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=t.lamprecht@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