From: Cyrus <cyruspy@gmail.com>
To: Proxmox VE user list <pve-user@lists.proxmox.com>
Subject: FC Storage integration
Date: Thu, 25 Jun 2026 19:06:09 -0300 [thread overview]
Message-ID: <CAEaLa5H_EMepFa5pP728VN9tCfQ74LKa31h-efs6m66C1G8fYg@mail.gmail.com> (raw)
Hello!,
It seems the pve-devel mail list is not very welcoming or I am doing
something wrong. I would try another angle: asking the users.
Is there any interest in having a storage plugin to integrate to FC
Storage systems in a 1 vdisk = 1 LUN fashion?. That should allow you
to offload some operations like cloning/snapshots operations to the
specialized box.
I'm currently testing an integration with Hitachi VSP, but it could be
generalized to accommodate specific brand/model drivers (would assume
Dell, HPE, Huawei, Purestorage are still selling similar systems)
Regards.
next reply other threads:[~2026-06-29 11:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-25 22:06 Cyrus [this message]
2026-06-29 12:03 ` FC Storage integration Andrei Boros
2026-06-29 21:09 ` Karel Beneš
2026-06-30 2:24 ` Cyrus
2026-06-30 19:53 ` Karel Beneš
2026-06-30 21:12 ` Ciro Iriarte
2026-06-29 12:26 ` SPAM: " Chunhui Ouyang
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=CAEaLa5H_EMepFa5pP728VN9tCfQ74LKa31h-efs6m66C1G8fYg@mail.gmail.com \
--to=cyruspy@gmail.com \
--cc=pve-user@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