Page History

...

1.  Introduce `CLVM` and `CLVM_NG` as first-class `StoragePoolType` entries in CloudStack. CLVM supports RAW volumes on LVM and CLVM_NG support QCOW2.
2. Design a lock-tracking layer that records and reconciles which KVM host holds the exclusive LVM activation for each volume.
3. Implement a lock-transfer mechanism so CloudStack can safely move the exclusive lock between hosts without copying data.
4. Introduce a three-tier migration strategy that avoids unnecessary data copying:
      - Lock Transfer - same pool, wrong host: transfer lock only.
      - Lightweight Migration - different CloudStack pool records sharing the same LVM Volume Group: transfer lock only.Same LV but different hosts - no data copy, just lock transfer
      - Full Migration - different Volume Groups: full data copy (existing behavior).
5. Provide a secure-erase option for LVs at deletion time to prevent data leakage.
6. Incremental snapshots for CLVM_NG leveraging bitmap - not supported in 4.23
   Note: Only full snapshots will be supported for clvm and clvm-ng

...