It started off so nice and friendly, and then reads so hostile at the end. Sort of like a shit sandwich, except with the bottom slice of bread missing.
I am curious to understand how Torus is similar to Sheepdog [0].
From the Sheepdog website:
Sheepdog is a distributed object storage system for
volume and container services and manages the disks
and nodes intelligently. Sheepdog features ease of use,
simplicity of code and can scale out to thousands of
nodes.
The block level volume abstraction can be attached to
QEMU virtual machines and Linux SCSI Target and supports
advanced volume management features such as snapshot,
cloning, and thin provisioning.
The object level container abstraction is designed to
be Openstack Swift and Amazon S3 API compatible and can
be used to store and retrieve any amount of data with a
simple web services interface.
They're both basically block storage, with similar approaches to sharding and replication. Sheepdog seems to be using the term "object" more than they used to, but it's important to note that sheepdog objects have semantics closer to files or virtual disks than to S3/Swift style objects. The two also use related approaches (consensus vs. virtual synchrony) for coordination. Most of the differences are related to the fact that Sheepdog has already evolved over several years to have many of the features that are still on Torus's nascent road map. Ceph's RADOS/RBD is only a bit further from either one than they are from each other. None of them are identical, of course, and I never said they were, but from a purely technical perspective Torus's stated goals could have been achieved more quickly by contributing to Sheepdog than by starting a new project.
I am curious to understand how Torus is similar to Sheepdog [0].
From the Sheepdog website:
[0] https://sheepdog.github.io/sheepdog/