Distributed Replicated Block Device (DRBD) announcements
 help / color / mirror / Atom feed
From: Roland Kammerer <roland.kammerer@linbit.com>
To: drbd-announce@lists.linbit.com, drbd-user@lists.linbit.com
Subject: linstor-proxmox v8.0.0
Date: Wed, 17 Apr 2024 09:55:35 +0200	[thread overview]
Message-ID: <Zh-Adx0FnNAultpA@arm64> (raw)

[-- Attachment #1: Type: text/plain, Size: 2262 bytes --]

Dear PVE on LINSTOR/DRBD users,

after some calmer period I'm happy to announce the final version 8.0.0
that includes two new features, but let me first notice that this
version needs LINSTOR 1.27.0 or later!

We did not find any bugs in the RC, for your convenience the last RC
announce mail:

- reassigning disks from one VM to another
- online migration of external storage like LVM to LINSTOR/DRBD

Reassining disks:
In order to allow reassigning disks between VMs we had to change the
naming scheme. New disks (also clones of old ones) will have names like
"pm-12cf742a_101" on PVE level, and "pm-12cf742a" on LINSTOR/DRBD level.
This is a static prefix ("pm-"), 8 characters of a UUID, and on PVE
level the VMID separated by an underscore ("_101"). The new naming
obsoletes the old "vm-101-disk-1" like names. Old VMs with legacy names
still work with version 8 of the plugin. For the user this change should
be completely transparent and should not require any changes besides
getting accustomed to the new names.

Online migration from external storage:
So far it was only possible to migrate data from external storage like
LVM to LINSTOR/DRBD if the data was migrated offline. If you want to
migrate data online you can now *temporarily* set "exactsize yes" in
your "storage.cfg" for a particular DRBD storage and then migrate disks
to it. After you are done, remove the "exactsize" option from the
"storage.cfg" again. The LINSTOR property that allowed temporary online
migration is then deleted when the disk is activated again (but not if
it is currently active). If you want to delete the property for all
active disks after migration, or you want to be extra sure, you can run
a command like this:

# linstor -m --output-version v1 rd l | jq '.[][].name' | \
  xargs -I {} linstor rd sp {} DrbdOptions/ExactSize False

Regards, rck

GIT: https://github.com/LINBIT/linstor-proxmox/commit/2da369dba902b7f540c6c36a28a29c07c3bc1030
TGZ: https://pkg.linbit.com//downloads/connectors/linstor-proxmox-8.0.0.tar.gz

Changelog:

[Roland Kammerer]
 * show diskless disks in "VM Disks"
 * allow reassigning disks
 * test: add simple test script
 * api: also check for APIAGE
 * add online mv storage
 * fix spelling
 * set allow-two-primaries in RD creation

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

                 reply	other threads:[~2024-04-17  7:55 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=Zh-Adx0FnNAultpA@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