With GlusterFS, high availability can be delivered through the volume configuration; deciding how this is done depends on the application needs, available space, and required performance.
Since GlusterFS handles high availability, there is no need to configure any form of redundancy at the brick level. This is especially true with cloud instances and virtual machines, where there are no physical disks that can go bad. For physical installations, it is always better to have an extra layer of redundancy by configuring the local disks with RAID5 or RAID6 for a balance in performance and resiliency. For now, let's stick to cloud deployments.
With GlusterFS, only two volume types offer high availability: replicated and dispersed. Replicated volumes are reasonably straightforward since data is just replicated from one node to another. These...
