From: Travis Osterman <tosterman@gmail.com>
To: Thomas Lamprecht <t.lamprecht@proxmox.com>
Cc: travis@wsor.net,
Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] any plan for zfs over open-iscsi (linux)?
Date: Mon, 18 Oct 2021 13:09:13 -0500 [thread overview]
Message-ID: <CALrNmKEMm8bXvMW5cbQbppWCgaFOW-uyg4ZyoxGCk9XN-U4cPQ@mail.gmail.com> (raw)
In-Reply-To: <250ce9d4-6ff9-782e-e3c4-e7e933af7626@proxmox.com>
On Mon, Oct 18, 2021 at 12:05 AM Thomas Lamprecht <t.lamprecht@proxmox.com>
wrote:
> Hi,
>
> 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
>
> cheers,
> Thomas
>
>
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?
next prev parent reply other threads:[~2021-10-18 18:10 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 [this message]
2021-10-19 4:56 ` Thomas Lamprecht
2021-10-19 18:01 ` Travis Osterman
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=CALrNmKEMm8bXvMW5cbQbppWCgaFOW-uyg4ZyoxGCk9XN-U4cPQ@mail.gmail.com \
--to=tosterman@gmail.com \
--cc=pve-devel@lists.proxmox.com \
--cc=t.lamprecht@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