From: Roland Kammerer <roland.kammerer@linbit.com>
To: drbd-announce@lists.linbit.com
Subject: linstor-proxmox v8.2.0-rc.1
Date: Fri, 13 Feb 2026 13:23:06 +0100 [thread overview]
Message-ID: <aY8Xqi_E44ebbIBJ@arm64> (raw)
Dear PVE users,
this is the first RC of the upcoming 8.2.0 release. We added NVMe-oF
support, allowing LINSTOR-managed NVMe over Fabrics resources alongside
existing DRBD setups. See the commit for requirements and limitations.
We will update the official documentation soon. We also added a
configurable allowtwoprimaries option that allows using DRBD replication
protocols other than C (at the cost of disabling live migration), and
fixed list_images to correctly show all volumes in the storage pool
regardless of which node you query from.
Please test, if we don't find any issues I will release the final
version in about a week from now. Packages are available in the public
testing repos.
Regards, rck
GIT: https://github.com/LINBIT/linstor-proxmox/commit/a61b58a765e12e8b411720c66af6b2eb79145aa8
TGZ: https://pkg.linbit.com/downloads/connectors/linstor-proxmox-8.2.0-rc.1.tar.gz
Changelog:
[ Roland Kammerer ]
* Add configurable allow-two-primaries option
[ Tydus ]
* Fix list_images to show all volumes in storage pool
* Add NVMe-oF support
reply other threads:[~2026-02-13 12:23 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=aY8Xqi_E44ebbIBJ@arm64 \
--to=roland.kammerer@linbit.com \
--cc=drbd-announce@lists.linbit.com \
--cc=drbd-user@lists.linbit.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