Hi!
Right before Christmas we finally could finish a feature that was in the works
for more than 10 months, the as we called it advanced clone.
Before clone could only handle simple cases of cloning in the same storage pool
and the same layer stack. Starting with this release you can now also specify a different
layer-stack and also another resource-group which will than use this resource-groups
storage pools. Of course such operations have to rely on a basic dd’ing of data and won’t
be the fastest, but at least they are possible now.
At the last minute we found a migration issue with 1.30.0, so we had to fix that in a 1.30.1 release.
[1.30.1] - 2024-12-17
Fixed
- Migration: Fixed splitSnapProps bug not properly handling KVS properties
[1.30.0] - 2024-12-17
Added
- Added options dst_rsc_grp and force_rsc_grp to BackupShip, BackupRestore and BackupSchedule
- Added timing of REST and internal API calls to prometheus /metrics
- Backup,L2L: Add property to only wait with shipping until snapshot is created
Changed
- Split snapshot properties into snapshot-specific- and resource-properties
- SOS: use local timestamp as well as relative delta for dmesg output
- SOS: use lvmconfig to show full lvm.conf
- SOS: use lsblk -O, also include json output
- SOS: include /proc/sys/kernel/tainted
- DRBD state tracking: Fixed tracking of a peer’s diskless volume’s client flag
- Clone: It is now possible to clone into different storage-pools and layer-stacks.
This can be done by using the new resource-group and layer-stack arguments
Fixed
- EBS: Fixed retrieving EC2 instance-id
https://pkg.linbit.com//downloads/linstor/linstor-server-1.30.1.tar.gz
Linstor PPA:
https://launchpad.net/~linbit/+archive/ubuntu/linbit-drbd9-stack
Cheers,
Rene