Comment

Comment on Shared storage between virtual instances

Thanks. I will take a closer look into GlusterFS and Ceph.

The use case would be a file storage for anything (text, documents, images, audio and video files). I’d like to share this data among multiple instances and don’t want to store that data multiple times - it is bad for my bank account and I don’t want to keep track of the various redundant file sets. So data and service decoupling.

Service scaling isn’t a requirement. It’s more about different services (some as containers, some as VMs) which should work on the same files, sometimes concurrently.

That jellyfin/arr approach works well and is easy to set up, if all containers access the same docker volume. But it doesn’t when VMs (KVM) or other containers (lxc) come into play. So I can’t use it in this context.

Failover is nice to have. But there is more to it than just the data replication between hosts. It’s not a priority to me right now.

Database replication isn’t required.

source

Sort:hotnew top

speculate7383@lemmy.today ⁨1⁩ ⁨week⁩ ago
GlusterFS is (was) really cool, but I would not set up a new instance. It used to have significant support and development from RedHat, but they decided to halt their work on it, and focus on Ceph.

GlusterFS is getting a few slow updates from some alternate developers, but I would only count on that being fixes for current installations.

source
hendrik@palaver.p3x.de ⁨1⁩ ⁨week⁩ ago
Just be warned that those two are relatively complicated pieces of tech. And they're meant to set up a distributed storage network including things like replication and load-balancing. Clusters with failover to a different datacenter and such. If you just want access to the same storage on one server from different instances, that's likely way to complicated for you.

source
- hsdkfr734r@feddit.nl ⁨1⁩ ⁨week⁩ ago
  Moot point. I do not really need the distributed storage part for my scenario. Not right now.
  
  Maybe I start with NFS and explore gluster as soon as storage distribution is needed. Looks like it could be a drop-in eplacement for NFSv3. Since it doesn’t access the block devices directly, I still could use the respective fs’ tool set (I.e. ext4 or btrfs) for maintenance tasks.
  
  source