Quick-Start-Guide: add ansible reference#379
Conversation
Also change the default example to 'supported' replica 3 volume type, instead of unsupported replica 2 type. Signed-off-by: Amar Tumballi <amarts@redhat.com>
| - Push the changes to review.gluster.org for review. If you had | ||
| provided a bug id, it assigns the topic of the change as "bug-XYZ". | ||
| If not it sets the topic as "rfc". | ||
| provided a reference id, it assigns the topic of the change as |
There was a problem hiding this comment.
it should either be Reference ID or, reference id - can't be both.
| using Fedora 26 (or later) virtual machines. | ||
| We also do not explain the steps in detail here as this guide is just to help | ||
| you get it up and running as soon as possible. | ||
|
|
There was a problem hiding this comment.
This document is intended to provide a step-by-step guide to setting up GlusterFS for the first time. For the purposes of this guide, it is required to use Fedora 26 (or, higher) virtual machine instances.
|
|
||
| #### Using Ansible to deploy and manage GlusterFS | ||
|
|
||
| If you are already an ansible user, and are more comfortable with setting |
| @@ -152,12 +152,16 @@ To submit your change for review, run the rfc.sh script, | |||
| $ ./rfc.sh | |||
|
|
|||
| The script will ask you to enter a bugzilla bug id. Every change | |||
There was a problem hiding this comment.
The script will prompt for a valid bug number in the Red Hat Bugzilla
|
|
||
| #### Automatically deploying GlusterFS with Puppet-Gluster+Vagrant | ||
|
|
||
| If you'd like to deploy GlusterFS automatically using |
There was a problem hiding this comment.
To deploy GlusterFS using scripted methods, please read this ...
|
|
||
| - Fedora 22 (or later) on two nodes named "server1" and "server2" | ||
| - Fedora 26 (or later) on 3 nodes named "server1", "server2" and "server3" | ||
| - A working network connection |
There was a problem hiding this comment.
Is it required to add a line about functional DNS (and/or, name resolution)?
There was a problem hiding this comment.
Also, what about NTP?
| at `/var/lib/glusterd`. If at any point in time GlusterFS is unable to | ||
| write to these files (for example, when the backing filesystem is full), | ||
| it will at minimum cause erratic behavior for your system; or worse, | ||
| take your system offline completely. It is advisable to create separate |
There was a problem hiding this comment.
It is recommended to create separate partitions for directories such as /var/log to reduce the chances of this happening.
|
|
||
| **Note**: We are going to use the XFS filesystem for the backend bricks. But Gluster is designed to work on top of any filesystem, which supports extended attributes. | ||
|
|
||
| These examples are going to assume the brick is going to reside on /dev/sdb1. |
There was a problem hiding this comment.
The following examples assume that the brick will be residing on /dev/sdb1
| transport.address-family: inet | ||
|
|
||
|
|
||
| Note: If the volume is not started, clues as to what went wrong will be |
There was a problem hiding this comment.
If the volume does not show "Started", the files under /var/log/glusterfs/glusterd.log should be checked in order to debug and diagnose the situation. These logs can be looked at on one or, all the servers configured.
3 participants
Also change the default example to 'supported' replica 3 volume type,
instead of unsupported replica 2 type.
Fix minor changes to identify how to commit in other docs.
Signed-off-by: Amar Tumballi amarts@redhat.com