From: Felix Driessler - inett GmbH via pve-devel <pve-devel@lists.proxmox.com>
To: "m.limbeck@proxmox.com" <m.limbeck@proxmox.com>
Cc: Felix Driessler - inett GmbH <fdriessler@inett.de>,
"pve-devel@lists.proxmox.com" <pve-devel@lists.proxmox.com>
Subject: [pve-devel] Further development of iSCSI functionalities in Proxmox VE
Date: Mon, 19 Jan 2026 11:27:11 +0000 [thread overview]
Message-ID: <mailman.425.1768822931.353.pve-devel@lists.proxmox.com> (raw)
In-Reply-To: <51f85c59-89ee-4879-a0ca-e9d1e0961e44@proxmox.com>
[-- Attachment #1: Type: message/rfc822, Size: 15829 bytes --]
From: Felix Driessler - inett GmbH <fdriessler@inett.de>
To: "m.limbeck@proxmox.com" <m.limbeck@proxmox.com>
Cc: "pve-devel@lists.proxmox.com" <pve-devel@lists.proxmox.com>
Subject: [pve-devel] Further development of iSCSI functionalities in Proxmox VE
Date: Mon, 19 Jan 2026 11:27:11 +0000
Message-ID: <96a58595-849c-4e90-ad51-8a63143b7490@inett.de>
Hi Mira,
as I've not subscribed to the mailing list, having thought that replies
would be sent to the original author automatically, I've not seen your
reply until now.
When do you think this new iSCSI Plugin would be introduced and where
could I find the source code of it?
For now I'd start implementing changes to the GUI, such as displayed
WWID names and refresh functionality.
Additionally I plan to check how feasible it is to automate deletion of
unused LUNs and see if I can find anything that your colleague's might
have missed.
Felix Driessler
Junior Systems Engineer // #GernPerDU
Linux - Open Source - IT Solutions
T: 0681-410993-0
E: fdriessler@inett.de
https://www.inett.de
inett GmbH | Altenkesseler Strasse 17 / B8 | 66115 Saarbrücken | Germany
Vertrieb: vertrieb@inett.de // 0681-410993-33
Support: support@inett.de // 0681-410993-42
Geschäftsführung: Marco Gabriel | Amtsgericht Saarbrücken HRB 16588
[-- 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 prev parent reply other threads:[~2026-01-19 11:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <f53ca227-2275-443f-84f8-48b2785269b2.2bc2ceb6-a3a3-4c49-9566-519c7d2ab20e.bc79f8c9-009c-47a0-8987-9e43cd7308aa@emailsignatures365.codetwo.com>
2025-10-01 12:54 ` Felix Driessler - inett GmbH via pve-devel
2025-11-19 12:44 ` Mira Limbeck
2025-11-20 10:00 ` Mira Limbeck
[not found] ` <f53ca227-2275-443f-84f8-48b2785269b2.2bc2ceb6-a3a3-4c49-9566-519c7d2ab20e.1ae60d36-41bd-415c-a84c-7b5364dcb486@emailsignatures365.codetwo.com>
2026-01-19 11:27 ` Felix Driessler - inett GmbH via pve-devel [this message]
2026-01-19 18:36 ` Gilberto Ferreira 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.425.1768822931.353.pve-devel@lists.proxmox.com \
--to=pve-devel@lists.proxmox.com \
--cc=fdriessler@inett.de \
--cc=m.limbeck@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