Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Our requirements from the storage are pretty much the same any other cloud provider has:-        

  • Full disk encryption. In more traditional cloud providers this is done to guard users from each other and from cloud provider employees. Guaranteeing that data will never leak. In our conditions we also don’t like the idea of the device being stolen, and unencrypted data can be accessed

...

  • Thin provisioning. Efficient usage of the storage - the blocks which are not used by a user should not be occupied

...

  • Snapshotting.  Snapshot a state of guest and easily roll back or forward between the snapshots

...

  • Compression also adds up to the efficiency of storage usage. And as well might increase read speeds on slower volumes (e.g. emmc)

Problem with current architecture

...

Here another advantage of the Intermediate step appears. If a production-ready zfs-based solution comes before the next wave of customers, we will endup with fewer nodes based on the legacy storage format. And transitioning from SCSI-vhost to NVMe-vhost is significantly easier than reformatting the whole system disk.

...

  • /dev/vda for virtio-scsi (current Eve implementation)
  • /dev/sda for vhost-scsi-pci (implementation described in the chapter Intermediate step)
  • /dev/nvme0n1 for nvme emulation

...

We will get the first numbers already pretty soon, when the Intermediate step PoC is ready. This would be also interesting to see what is going to be the bottleneck of such architecture, and potentially adjust the development plan according to the discoveries. 

...