public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Travis Osterman <tosterman@gmail.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] any plan for zfs over open-iscsi (linux)?
Date: Tue, 19 Oct 2021 13:01:00 -0500	[thread overview]
Message-ID: <CALrNmKF4rA7NqQ6UUfOSD0dZHk6etY=bbi9ODso8G+nDT1y_eg@mail.gmail.com> (raw)
In-Reply-To: <65ecf123-1411-df36-f32b-50bec27ea26e@proxmox.com>

On Mon, Oct 18, 2021 at 11:56 PM Thomas Lamprecht <t.lamprecht@proxmox.com>
wrote:

> On 18.10.21 20:09, Travis Osterman wrote:
> > On Mon, Oct 18, 2021 at 12:05 AM Thomas Lamprecht <
> t.lamprecht@proxmox.com wrote:
> >> On 18.10.21 04:04, Travis Osterman wrote:
> >>> I think the title says it all. I use open-iscsi for my SAN and wondered
> >>> whether there was a plan to support that the way LIO and IET are
> >> supported
> >>> within Proxmox. Neither LIO or IET are available for my linux
> >> distribution
> >>> and do not seem to be actively supported.
> >>>
> >>> I'm not a native perl coder but would happily be a tester for anyone
> >>> interested in this feature. If I'm alone, I may start trying to come up
> >>> with something. Thanks.
> >>
> >> I'm only waking up so excuse if I overlook something, but what's wrong
> >> with the non-user-mode iSCSI storage type of PVE?
> >>
> >> https://pve.proxmox.com/pve-docs/chapter-pvesm.html#storage_open_iscsi
> >>
> >>
> > That does, indeed, work fine. iSCSI over ZFS provides additional support
> > for quickly provisioning, snapshotting and rolling back images all
> through
> > the UI. From what I can see, proxmox connects to the NAS to issue the
> > commands to perform those functions. When I use the iSCSI (without ZFS),
> I
> > have access both proxmox and my NAS. Does that make sense?
> >
>
> Oh, it seems I just somehow missed the "zfs" part yesterday (local)
> morning..
>
> As we already have the base support for the other target providers it can
> make sense to at least evaluate this and if no show-stoppers come up also
> integrate it into PVE.
>
> Can you please open a enhancement request over at:
> https://bugzilla.proxmox.com/
>
> Some more details regarding your SAN would be also nice to have in that
> request, if possible.
>
> cheers,
> Thomas
>
>
> _______________________________________________
> pve-devel mailing list
> pve-devel@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
>
>
Thanks, Thomas. I also incorrectly wrote "open-iscsi" which is my typical
iscsi client instead of "TGTD" which is my SAN target provider. I've
submitted an enhancement request, linked below.

https://bugzilla.proxmox.com/show_bug.cgi?id=3685

Thanks for your consideration.


      reply	other threads:[~2021-10-19 18:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-18  2:04 Travis Osterman
2021-10-18  5:05 ` Thomas Lamprecht
2021-10-18 18:09   ` Travis Osterman
2021-10-19  4:56     ` Thomas Lamprecht
2021-10-19 18:01       ` Travis Osterman [this message]

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='CALrNmKF4rA7NqQ6UUfOSD0dZHk6etY=bbi9ODso8G+nDT1y_eg@mail.gmail.com' \
    --to=tosterman@gmail.com \
    --cc=pve-devel@lists.proxmox.com \
    --cc=travis@wsor.net \
    /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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal