From: "Fabian Grünbichler" <f.gruenbichler@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] TrueNAS Storage Plugin
Date: Tue, 13 May 2025 10:53:49 +0200 (CEST) [thread overview]
Message-ID: <1131042857.14243.1747126429341@webmail.proxmox.com> (raw)
In-Reply-To: <mailman.366.1747114488.394.pve-devel@lists.proxmox.com>
> Lorne Guse via pve-devel <pve-devel@lists.proxmox.com> hat am 13.05.2025 07:34 CEST geschrieben:
> 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.
the rough plan (as previously discussed on this list, CCing Roland who might be interested as well)
would be for the plugin to provide a "UI schema", and the UI code to derive a basic form for adding
and editing the storage configuration based on that.
we are basically waiting for some third-party plugin developer to drive this feature together with
us - if you want to step up to do that it would be great!
a rough sketch:
- plugin gets a new property defining how each of its options should be presented on the UI
- an endpoint is added that returns the existing storage types + their schema
- JS code gets written that calls that endpoint and generates the 'add' and 'edit' windows
what's needed from the plugin dev side is mainly feedback on how the schema could/should
look like, what kind of control would be desirable, and of course, validation of the
implementation once it exists.
what we definitely don't want is to provide some sort of hookpoint for arbitrary JS code,
that is far too brittle.
hope this helps,
Fabian
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2025-05-13 8:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-13 5:34 Lorne Guse via pve-devel
2025-05-13 8:53 ` Fabian Grünbichler [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=1131042857.14243.1747126429341@webmail.proxmox.com \
--to=f.gruenbichler@proxmox.com \
--cc=pve-devel@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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal