From: Felix Driessler - inett GmbH via pve-devel <pve-devel@lists.proxmox.com>
To: "pve-devel@lists.proxmox.com" <pve-devel@lists.proxmox.com>
Cc: Felix Driessler - inett GmbH <fdriessler@inett.de>,
"timo.veith@uni-tuebingen.de" <timo.veith@uni-tuebingen.de>
Subject: Re: [pve-devel] iscsi and multipathing
Date: Tue, 18 Nov 2025 08:28:41 +0000 [thread overview]
Message-ID: <mailman.1428.1763739923.362.pve-devel@lists.proxmox.com> (raw)
In-Reply-To: <mailman.84.1745526459.394.pve-devel@lists.proxmox.com>
[-- Attachment #1: Type: message/rfc822, Size: 15650 bytes --]
From: Felix Driessler - inett GmbH <fdriessler@inett.de>
To: "pve-devel@lists.proxmox.com" <pve-devel@lists.proxmox.com>
Cc: "m.limbeck@proxmox.com" <m.limbeck@proxmox.com>, "timo.veith@uni-tuebingen.de" <timo.veith@uni-tuebingen.de>
Subject: Re: [pve-devel] iscsi and multipathing
Date: Tue, 18 Nov 2025 08:28:41 +0000
Message-ID: <0d084e55-8404-46b7-a211-21466705835c@inett.de>
Hi,
1 1/2 months ago we opened a related thread on the mailing list [0],
checking for demand/approval of implementing features related to this
thread. Sadly, we've not received a reply, so I'm checking back here if
there are any issues with the suggested additions/changes.
As the scope isn't entirely the same as was discussed in this thread, I
wanted to confirm if any other additional points would also be worth
looking into.
Regards,
Felix Driessler
[0] https://lists.proxmox.com/pipermail/pve-devel/2025-October/075765.html
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
prev parent reply other threads:[~2025-11-21 15:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-09 17:21 Timo Veith via pve-devel
2025-04-15 9:09 ` Mira Limbeck
2025-04-15 14:10 ` Timo Veith via pve-devel
2025-04-18 6:24 ` DERUMIER, Alexandre via pve-devel
[not found] ` <BE392B97-179A-4168-A3F0-B8ED4EF46907@uni-tuebingen.de>
2025-04-18 8:45 ` Mira Limbeck
2025-04-24 20:27 ` Timo Veith via pve-devel
[not found] ` <f53ca227-2275-443f-84f8-48b2785269b2.2bc2ceb6-a3a3-4c49-9566-519c7d2ab20e.cf5c4005-75ac-4330-ae52-568d0c758e75@emailsignatures365.codetwo.com>
2025-11-18 8:28 ` Felix Driessler - inett GmbH via pve-devel [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=mailman.1428.1763739923.362.pve-devel@lists.proxmox.com \
--to=pve-devel@lists.proxmox.com \
--cc=fdriessler@inett.de \
--cc=timo.veith@uni-tuebingen.de \
/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