I was thinking to save disk and avoid 3 replication Gluster waste of space, to create a gluster distributed volume (with no redundancy) on top on Raid5 hardware hotswappable on 3 nodes.
Just for a thought, what happens if one node dies completely? I assume, then that portion of the data is not available and I guess the VM/CT using that data will fail.
Just for a thought, what happens if one node dies completely? I assume, then that portion of the data is not available and I guess the VM/CT using that data will fail.
Yes, you are right.
Obviously the 3 nodes will be redundant in every other aspect to avoid or minimize fails.
But if a stop of services are allowed, data are safe in raid5 so you can recover from a node fail simply restarting it o reinstalling it.
This is good only on a small home project or where there's no SLA etc.
"You can use distributed volumes where the requirement is to scale storage and the redundancy is either not important or is provided by other hardware/software layers"...
If someone has another interesting solution with 3 nodes, local storage and Gluster (or Ceph) without losing 2/3 of disk space and have a decency avaibility, I'm all ears
If someone has another interesting solution with 3 nodes, local storage and Gluster or Ceph without losing 2/3 of disk space and have a decency avaibility, I'm all ears