The release of the Stratis 3.0 project, developed by Red Hat and the Fedora community to unify and simplify tools for configuring and managing a pool of one or more local drives, has been published. Stratis provides features such as dynamic storage allocation, snapshots, integrity, and caching layers. Stratis support has been integrated into Fedora and RHEL distributions since the Fedora 28 and RHEL 8.2 releases. The project code is distributed under the MPL 2.0 license.
The system largely repeats the advanced ZFS and Btrfs partition management tools in its capabilities, but is implemented as a layer (stratisd daemon) running on top of the device-mapper subsystem of the Linux kernel (modules dm-thin, dm-cache, dm-thinpool, dm- raid and dm-integrity) and the XFS file system. Unlike ZFS and Btrfs, Stratis components work only in user space and do not require loading specific kernel modules. The project is initially presented as not requiring the qualifications of an expert in storage systems for administration.
D-Bus API and cli-utility are provided for control. Stratis has been tested with LUKS-based block devices (encrypted partitions), mdraid, dm-multipath, iSCSI, LVM logical volumes, and various hard drives, SSDs, and NVMe drives. If there is one disk in the pool, Stratis allows you to use snapshot-enabled logical partitions to roll back changes. When multiple drives are added to a pool, the drives can be logically combined into a contiguous area. Features such as RAID, data compression, deduplication, and failover are not currently supported, but are planned for the future.
The significant change in version number is due to the change in interface for D-Bus control and the deprecation of the FetchProperties interfaces in favor of D-Bus based properties and methods. The new release also added checking udev rules with libblkid before making changes, redone the handling of events from DeviceMapper, changed the internal representation of error handlers, redesigned the code for rolling back changes (rollback), and allowed specifying a logical size when creating a file system. The Clevis framework, which is used to automatically encrypt and decrypt data on disk partitions, uses SHA-256 hashes instead of SHA-1. Provided the ability to change the passphrase and regenerate bindings to Clevis.
Source: opennet.ru