From: Andrei Perapiolkin via pve-devel <pve-devel@lists.proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Cc: Andrei Perapiolkin <andrei.perepiolkin@open-e.com>
Subject: [pve-devel] Cluster storage plugin assistant service
Date: Wed, 28 May 2025 11:42:46 -0400 [thread overview]
Message-ID: <mailman.86.1748447002.395.pve-devel@lists.proxmox.com> (raw)
[-- Attachment #1: Type: message/rfc822, Size: 7530 bytes --]
From: Andrei Perapiolkin <andrei.perepiolkin@open-e.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: [pve-devel] Cluster storage plugin assistant service
Date: Wed, 28 May 2025 11:42:46 -0400
Message-ID: <59e66c97-2337-4717-8c8f-c7b31b47da6b@open-e.com>
Hi Proxmox Community,
I am working on implementing custom storage plugin and after evaluating
various edge cases related to volume live migration, I have decided to
create a 'storage assistant service'.
This service will be responsible for managing my storage plugin volumes
activation and deactivation across all nodes in the cluster.
The idea is to run a service on every cluster node that conducts:
Volume activation upon creation
Volume deactivation upon deletion
To achieve this, the service must receive notifications from the storage
plugin whenever a volume is created or deleted.
However, I am not yet familiar with the internal mechanisms of Proxmox
clustering and am unsure what technology or approach would be most
appropriate for such inter-node communication.
At present, I am considering using the Proxmox Cluster File System
(pmxcfs)—specifically the '/etc/pve/priv' directory—as a means of
transferring notifications through file creation and deletion.
Another option I’m exploring is executing remote commands over SSH.
I would appreciate any feedback on potential issues with this approach.
Additionally, if there are any existing services or projects that have
solved similar design problems, I would be grateful to learn about them.
Best regards,
Andrei
[-- 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-28 15:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-28 15:42 Andrei Perapiolkin via pve-devel [this message]
2025-06-02 8:12 ` Fabian Grünbichler
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.86.1748447002.395.pve-devel@lists.proxmox.com \
--to=pve-devel@lists.proxmox.com \
--cc=andrei.perepiolkin@open-e.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.