Set up a GlusterFS cluster and recover an individual brick (node) in case of a single node failure.
GlusterFS requires a security group with specific ports opened to itself. Ensure that TCP ports 111, 24007,24008, 24009-(24009 + number of bricks across all volumes) are open on all Gluster servers.
Below is an example security group setup:
Unlike the example above, which is only for illustrative purposes, you will need to open the ports above to itself by adding the security group to itself and to the security group of the clients accessing the GlusterFS nodes.
Configure the following inputs at the deployment level:
|Storage Path||Location of the brick data on the node. The default will try and use any local ephemeral storage.||text:/mnt/ephemeral/glusterfs|
|Volume Name||Sets the name of the export GlusterFS volume.||text:glusterfs|
|Replica Count||Number of Replica instances (one per brick) that will be started and setup to form a cluster. You must launch this number of instances to initially setup a cluster.||text:2|
|Volume Type||The type of volume to build. Replicated and Distributed are options, though only Replica is currently supported with expected behavior.||text:Replicated|
|Replace Brick||If a node is to be replaced, this is the ‘bricknum’ tag value of the node or brick number.||text:Ignore|
|Force Brick Replace||If a node is completely unresponsive, this option will force a config change without migrating the data from the dead node.||text:No|
|Mount point||Location on the local filesystem when you want to access the mounted GlusterFS volume.||text:/mnt/glusterfs|
|Mount Options||Sets any specific or custom mount options you may have.||text:Ignore|
Eventually, a situation will arise that will require you to migrate a brick off to another node (instance). If the source node that you want to migrate from is still active:
On clouds without native security groups, you may enable firewall support by adding the sys_firewall::do_list_rules and sys_firewall::setup_rule recipes and placing them after the sys_firewall::default rule. Specify the same ports as described under ‘Prerequisites’ above.
© 2006-2014 RightScale, Inc. All rights reserved.
RightScale is a registered trademark of RightScale, Inc. All other products and services may be trademarks or servicemarks of their respective owners.