Vitaliy Filippov
926be372fd
Test / test_move_reappear (push) Successful in 17s
Details
Test / buildenv (push) Successful in 9s
Details
Test / build (push) Successful in 2m33s
Details
Test / make_test (push) Successful in 32s
Details
Test / test_add_osd (push) Successful in 1m38s
Details
Test / test_cas (push) Successful in 9s
Details
Test / test_change_pg_count (push) Successful in 35s
Details
Test / test_change_pg_count_ec (push) Successful in 34s
Details
Test / test_change_pg_size (push) Successful in 9s
Details
Test / test_create_nomaxid (push) Successful in 7s
Details
Test / test_etcd_fail (push) Successful in 1m1s
Details
Test / test_failure_domain (push) Successful in 9s
Details
Test / test_interrupted_rebalance (push) Successful in 1m26s
Details
Test / test_interrupted_rebalance_imm (push) Successful in 2m15s
Details
Test / test_interrupted_rebalance_ec (push) Successful in 1m31s
Details
Test / test_interrupted_rebalance_ec_imm (push) Successful in 1m32s
Details
Test / test_minsize_1 (push) Successful in 13s
Details
Test / test_rebalance_verify (push) Successful in 2m49s
Details
Test / test_rebalance_verify_imm (push) Successful in 2m45s
Details
Test / test_rebalance_verify_ec (push) Successful in 3m9s
Details
Test / test_rebalance_verify_ec_imm (push) Successful in 3m3s
Details
Test / test_rm (push) Successful in 12s
Details
Test / test_snapshot (push) Successful in 24s
Details
Test / test_snapshot_ec (push) Successful in 35s
Details
Test / test_splitbrain (push) Successful in 21s
Details
Test / test_write (push) Successful in 1m10s
Details
Test / test_write_xor (push) Successful in 2m23s
Details
Test / test_write_no_same (push) Successful in 19s
Details
Test / test_heal_pg_size_2 (push) Successful in 3m58s
Details
Test / test_heal_ec (push) Successful in 4m8s
Details
Test / test_scrub (push) Successful in 1m3s
Details
Test / test_scrub_zero_osd_2 (push) Successful in 36s
Details
Test / test_scrub_xor (push) Successful in 34s
Details
Test / test_scrub_pg_size_3 (push) Successful in 51s
Details
Test / test_scrub_pg_size_6_pg_minsize_4_osd_count_6_ec (push) Successful in 32s
Details
Test / test_scrub_ec (push) Successful in 43s
Details
- Measure and report scrub I/O statistics in vitastor-cli status - Make aggregated statistics in vitastor-cli status much smoother (first derive, then sum instead of first summing and then deriving) - Fix an old rare bug leading to journal corruption (try to use scrub if you think you're affected...) - Do not start EC PGs without at least <data chunks> OSDs in each old set (prevents spurious read errors with EC during reconnections/restarts) - Fix failed assert(!scrub_list_op) on OSD restart with pending scrubs - Fix future planned scrubs not starting because of incorrect time comparison - Build packages for Debian 12 (Bookworm) |
||
---|---|---|
.gitea/workflows | ||
cpp-btree@45e6d1f131 | ||
csi | ||
debian | ||
docker | ||
docs | ||
json11@fd37016cf8 | ||
mon | ||
patches | ||
rpm | ||
src | ||
tests | ||
.dockerignore | ||
.gitignore | ||
.gitmodules | ||
CMakeLists.txt | ||
GPL-2.0.txt | ||
LICENSE | ||
README-ru.md | ||
README.md | ||
VNPL-1.1-RU.txt | ||
VNPL-1.1.txt | ||
copy-fio-includes.sh | ||
copy-qemu-includes.sh |
README.md
Vitastor
The Idea
Make Clustered Block Storage Fast Again.
Vitastor is a distributed block SDS, direct replacement of Ceph RBD and 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 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, NBD, NFS protocols, OpenStack, Proxmox, Kubernetes drivers. More drivers may be created easily.
Read more details below in the documentation.
Talks and presentations
- DevOpsConf'2021: presentation (in Russian, in English), video
- Highload'2022: presentation (in Russian), video
Documentation
- Introduction
- Installation
- Configuration
- Usage
- vitastor-cli (command-line interface)
- vitastor-disk (disk management tool)
- fio for benchmarks
- NBD for kernel mounts
- QEMU and qemu-img
- NFS emulator for VMWare and similar
- 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.