all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: Seth Cagampang via pve-devel <pve-devel@lists.proxmox.com>
To: pve-devel@lists.proxmox.com
Cc: Seth Cagampang <seth.cagampang@osnexus.com>
Subject: [pve-devel] QuantaStor PVE plugin
Date: Mon, 24 Feb 2025 10:41:22 -0800	[thread overview]
Message-ID: <mailman.526.1740485791.293.pve-devel@lists.proxmox.com> (raw)

[-- Attachment #1: Type: message/rfc822, Size: 5348 bytes --]

From: Seth Cagampang <seth.cagampang@osnexus.com>
To: pve-devel@lists.proxmox.com
Subject: QuantaStor PVE plugin
Date: Mon, 24 Feb 2025 10:41:22 -0800
Message-ID: <CABaJVXMO3Fe_6ZT5peMvONvDh2WKNMTp3Z8FRL5iLcDA6N0Gfg@mail.gmail.com>

To Whom It May Concern,

My name is Seth, I am a Sr. Engineer at OSNEXUS. We have a storage solution
called QuantaStor that we are developing a storage plug-in for proxmox PVE.
The idea is to serve ZFS volumes from a QuantaStor node to the PVE via
iscsi. I have been hacking away at a QuantaStorPlugin.pm module, using
existing modules as examples. I have implemented the scan (QuantaStor ZFS
Pools), add (storage config), and remove (storage config) commands. Running
into various snags in development, and would like to learn more about
proxmox storage modules to make sure the QuantaStor plug-in is implemented
correctly.

Would love to start a dialog with the proxmox team or other plugin devs, to
ensure I'm on the right track. Any advice on development for production
level proxmox plugins would be greatly appreciated.

-- 
Seth Cagampang
Senior Software Engineer
OSNEXUS Corporation

[-- 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

             reply	other threads:[~2025-02-25 12:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-24 18:41 Seth Cagampang via pve-devel [this message]
     [not found] <CABaJVXMO3Fe_6ZT5peMvONvDh2WKNMTp3Z8FRL5iLcDA6N0Gfg@mail.gmail.com>
2025-02-25 14:21 ` Max Carrara

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.526.1740485791.293.pve-devel@lists.proxmox.com \
    --to=pve-devel@lists.proxmox.com \
    --cc=seth.cagampang@osnexus.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.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal