From: Lorne Guse via pve-devel <pve-devel@lists.proxmox.com>
To: "pve-devel@lists.proxmox.com" <pve-devel@lists.proxmox.com>
Cc: Lorne Guse <boomshankerx@hotmail.com>
Subject: [pve-devel] TrueNAS Storage Plugin
Date: Tue, 13 May 2025 05:34:36 +0000 [thread overview]
Message-ID: <mailman.366.1747114488.394.pve-devel@lists.proxmox.com> (raw)
[-- Attachment #1: Type: message/rfc822, Size: 10531 bytes --]
From: Lorne Guse <boomshankerx@hotmail.com>
To: "pve-devel@lists.proxmox.com" <pve-devel@lists.proxmox.com>
Subject: TrueNAS Storage Plugin
Date: Tue, 13 May 2025 05:34:36 +0000
Message-ID: <CO1PR17MB53060FFAB141E6E3AAE7D309D096A@CO1PR17MB5306.namprd17.prod.outlook.com>
I'm working on an update to https://github.com/TheGrandWazoo/freenas-proxmox
My repo can be found here: https://github.com/boomshankerx/proxmox-truenas
I'm considering writing a pure TrueNAS plugin to fully utilize their WebSocket API. I think
I have a reasonable grasp on the existing storage plugins for ZFS over ISCSI however I'm not sure how to go about developing the UI component for a brand new plugin.
The exiting plugins above inject some UI code via patch to accommodate some extra UI components. I imagine that this would be the case if I were to build a TrueNAS plugin from the ground up.
I'd like some suggestions if there are any to give.
Thank you
Lorne Guse
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next reply other threads:[~2025-05-13 5:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-13 5:34 Lorne Guse via pve-devel [this message]
2025-05-13 8:53 ` Fabian Grünbichler
2025-07-06 1:29 Lorne Guse via pve-devel
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=mailman.366.1747114488.394.pve-devel@lists.proxmox.com \
--to=pve-devel@lists.proxmox.com \
--cc=boomshankerx@hotmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.