Yury Luneff
bbcfe3e258
udev skips every key of a rule whose `IMPORT{program}` fails, `OWNER` and `GROUP` included, and `vitastor-disk udev` exits 1 when it rejects the superblock. A freshly added partition whose check failed stayed `root:disk`, and an OSD opening it as user vitastor got EACCES. This happens with dm-multipath: the dm partition's ready event is checked while `/dev/disk/by-partuuid` still points at the path partition. Assign ownership by partition type alone (in `mon/scripts/` and `docker/`); the alias symlink and the OSD start still need a valid superblock.
Tested: `udevadm test` on systemd 249 and 252 with a failing IMPORT — before: no OWNER/GROUP/SYMLINK; after: OWNER/GROUP applied, SYMLINK not. On a VM, a partition re-added by PCI remove/rescan while another device carried its PARTUUID came back `root:disk` before and owned by the OSD user after.
I accept Vitastor CLA agreement: https://git.yourcmc.ru/vitalif/vitastor/src/branch/master/CLA-en.md
Co-authored-by: Yury Luneff <koolkhel@mail.ru>
Co-committed-by: Yury Luneff <koolkhel@mail.ru>
Vitastor
The Idea
Make Clustered Block Storage Fast Again.
Vitastor is a distributed block, file and object SDS, direct replacement of Ceph RBD, CephFS and RGW, and also internal SDS's of public clouds. However, in contrast to them, Vitastor is fast and simple at the same time. The only thing is it's slightly young :-).
Vitastor is architecturally similar to Ceph which means strong consistency, primary-replication, symmetric clustering and automatic data distribution over any number of drives of any size with configurable redundancy (replication or erasure codes/XOR).
Vitastor targets primarily SSD and SSD+HDD clusters with at least 10 Gbit/s network, supports TCP and RDMA and may achieve 4 KB read and write latency as low as ~0.1 ms with proper hardware which is ~10 times faster than other popular SDS's like Ceph or internal systems of public clouds.
Vitastor supports QEMU, UBLK, NBD, NFS protocols, OpenStack, OpenNebula, Proxmox, Kubernetes drivers. More drivers may be created easily.
Read more details in the documentation. You can start from here: Quick Start.
Talks and presentations
- KuberConf'2025: video
- Highload'2025: video, youtube, presentation (in Russian, in English)
- Highload'2022: presentation (in Russian), video
- DevOpsConf'2021: presentation (in Russian, in English), video
Documentation
- Introduction
- Installation
- Configuration
- Usage
- vitastor-cli (command-line interface)
- vitastor-disk (disk management tool)
- fio for benchmarks
- UBLK for kernel mounts
- NBD - old interface for kernel mounts
- QEMU, qemu-img and VDUSE
- NFS clustered file system and pseudo-FS proxy
- Security
- Administration
- Performance
Author and License
Copyright (c) Vitaliy Filippov (vitalif [at] yourcmc.ru), 2019+
Join Vitastor Telegram Chat: https://t.me/vitastor
All server-side code (OSD, Monitor and so on) is licensed under the terms of Vitastor Network Public License 1.1 (VNPL 1.1), a copyleft license based on GNU GPLv3.0 with the additional "Network Interaction" clause which requires opensourcing all programs directly or indirectly interacting with Vitastor through a computer network and expressly designed to be used in conjunction with it ("Proxy Programs"). Proxy Programs may be made public not only under the terms of the same license, but also under the terms of any GPL-Compatible Free Software License, as listed by the Free Software Foundation. This is a stricter copyleft license than the Affero GPL.
Please note that VNPL doesn't require you to open the code of proprietary software running inside a VM if it's not specially designed to be used with Vitastor.
Basically, you can't use the software in a proprietary environment to provide its functionality to users without opensourcing all intermediary components standing between the user and Vitastor or purchasing a commercial license from the author 😀.
Client libraries (cluster_client and so on) are dual-licensed under the same VNPL 1.1 and also GNU GPL 2.0 or later to allow for compatibility with GPLed software like QEMU and fio.
You can find the full text of VNPL-1.1 in the file VNPL-1.1.txt. GPL 2.0 is also included in this repository as GPL-2.0.txt.