gregsfortytwo

4 ms·

1. 1.▲
   by gregsfortytwo 8y ago

   Just for future reference, RADOS is actually not very S3-like. It is an object store; it does map from object names to buckets of bytes. But unlike S3 and many similar object stores or key-value DBs, RADOS allows you to do file-like operati
2. 2.▲
   by gregsfortytwo 8y ago

   These abstraction statements just aren't true. Yes, you can architect a storage system this way. But 1) Even if you do, many, many, many high-performance systems are "on top" of a filesystem but don't actually use the
3. 3.▲
   by gregsfortytwo 10y ago

   "haven't figured out consistency yet" is the issue. Seemingly very small decisions have huge impacts that you don't expect, and the state of the art is far enough along that you don't get better than the existing so
4. 4.▲
   by gregsfortytwo 10y ago

   Torus is also definitely single mount.
5. 5.▲
   by gregsfortytwo 10y ago

   You're providing a block device interface to the container. The container's FS is addressing LBAs. Sequential reads to the container's adjacent LBAs get turned into reads to whatever random Torus node is storing the data, bas
6. 6.▲
   by gregsfortytwo 10y ago

   Okay, so from reading the developer docs at https://github.com/coreos/torus/Documentation , I'm inferring that: * Single reader/writer. If you try and set up more, Bad Things happen (even if it's sin