[Gluster-users] Gluster setup for virtualization cluster
Greetings! I am currently evaluating our options to replace our old mixture of IBM SAN storage boxes. This will be a strategic decision for the next years. One of the solutions I am reviewing is a GlusterFS installation. Planned usage: - Central NFS server for around 25 systems providing around 400 docker containers - Central storage for a small VMWare vCenter cluster and a RedHat virtualization cluster. In total maybe around 15 machines The following requirements ensue from this: - Fast storage - High availability After reading all kind of tutorials and documentation, I came to the conclusion that for the expected traffic a "Distributed Replicate Volume" is the proper setup. Nothing has been purchased but I think about following small setup for the beginning (call it PoC): 4 x server, each with 8 x 1.8TB 10k SAS disks in a RAID60 Two 10 GBit interfaces per server: One for communication betweens the 4 systems only (separate VLAN), the other one for regular traffic between clients and servers. Does this all make sense? Generally speaking: Is such a setup capable of providing fast enough storage for a virtualization cluster? Do you have any hints? Thanks Markus Community Meeting Calendar: APAC Schedule - Every 2nd and 4th Tuesday at 11:30 AM IST Bridge: https://bluejeans.com/441850968 NA/EMEA Schedule - Every 1st and 3rd Tuesday at 01:00 PM EDT Bridge: https://bluejeans.com/441850968 Gluster-users mailing list Gluster-users@gluster.org https://lists.gluster.org/mailman/listinfo/gluster-users
Re: [Gluster-users] To RAID or not to RAID...
Hi Strahil, thanks for you answer - but now I am completely lost :) From this documentation: https://docs.oracle.com/cd/E52668_01/F10040/html/gluster-312-volume-distr-disp.html "As a dispersed volume must have a minimum of three bricks, a distributed dispersed volume must have at least six bricks. For example, six nodes with one brick, or three nodes with two bricks on each node are needed for this volume type." So for a distributed dispersed volume I need at least six bricks. If each brick is a RAID6, I have 6 x 2 Parity disks = 12 disks for parity. In your example you only have one brick per node in a three node setup. This is no distributed dispersed volume then, right? A confused Markus Am 14.01.2020 16:29, schrieb Strahil: Hi Markus, Distributed dispersed volume is just LVM's linear LV -> so in case of brick failiure - you loose the data on it. Raid 6 requires 2 disks for parity, so you can make a large RAID6 and use that as a single brick - so the disks that hold the parity data are only 6 ( 3 nodes x 2 disks). Of course if you have too many disks for a single raid controller ,that you can consider a replica volume with an arbiter. Best Regards, Strahil Nikolov On Jan 14, 2020 13:36, Markus Kern wrote: Greetings again! After reading RedHat documentation regarding optimizing Gluster storage another question comes to my mind: Let's presume that I want to go the distributed dispersed volume way. Three nodes which two bricks each. According to RedHat's recommendation, I should use RAID6 as underlying RAID for my planned workload. I am frightened by that "waste" of disks in such a case: When each brick is a RAID6, I would "loose" two disks per brick - 12 lossed disks in total. In addition to this, distributed dispersed volume adds another layer of lossed disk space. Am I wrong here? Maybe I didn't understand the recommendations wrong? Markus Community Meeting Calendar: APAC Schedule - Every 2nd and 4th Tuesday at 11:30 AM IST Bridge: https://bluejeans.com/441850968 NA/EMEA Schedule - Every 1st and 3rd Tuesday at 01:00 PM EDT Bridge: https://bluejeans.com/441850968 Gluster-users mailing list Gluster-users@gluster.org https://lists.gluster.org/mailman/listinfo/gluster-users Community Meeting Calendar: APAC Schedule - Every 2nd and 4th Tuesday at 11:30 AM IST Bridge: https://bluejeans.com/441850968 NA/EMEA Schedule - Every 1st and 3rd Tuesday at 01:00 PM EDT Bridge: https://bluejeans.com/441850968 Gluster-users mailing list Gluster-users@gluster.org https://lists.gluster.org/mailman/listinfo/gluster-users
[Gluster-users] To RAID or not to RAID...
Greetings again! After reading RedHat documentation regarding optimizing Gluster storage another question comes to my mind: Let's presume that I want to go the distributed dispersed volume way. Three nodes which two bricks each. According to RedHat's recommendation, I should use RAID6 as underlying RAID for my planned workload. I am frightened by that "waste" of disks in such a case: When each brick is a RAID6, I would "loose" two disks per brick - 12 lossed disks in total. In addition to this, distributed dispersed volume adds another layer of lossed disk space. Am I wrong here? Maybe I didn't understand the recommendations wrong? Markus Community Meeting Calendar: APAC Schedule - Every 2nd and 4th Tuesday at 11:30 AM IST Bridge: https://bluejeans.com/441850968 NA/EMEA Schedule - Every 1st and 3rd Tuesday at 01:00 PM EDT Bridge: https://bluejeans.com/441850968 Gluster-users mailing list Gluster-users@gluster.org https://lists.gluster.org/mailman/listinfo/gluster-users
[Gluster-users] Expanding distributed dispersed volumes
Greetings! I am unsure if I understood that volume properly - or, to be more specific, I am unsure how to increase available storage there properly. Say I have three servers with two bricks on each server, providing one volume. Free space gets low in that volume and I want to expand it. Do I need to add 6 bricks (two to each server) at a minimum then? Markus Community Meeting Calendar: APAC Schedule - Every 2nd and 4th Tuesday at 11:30 AM IST Bridge: https://bluejeans.com/441850968 NA/EMEA Schedule - Every 1st and 3rd Tuesday at 01:00 PM EDT Bridge: https://bluejeans.com/441850968 Gluster-users mailing list Gluster-users@gluster.org https://lists.gluster.org/mailman/listinfo/gluster-users
