|author||Michael Adam <email@example.com>||2017-05-23 11:08:25 +0200|
|committer||Prasanna Kumar Kalever <firstname.lastname@example.org>||2017-06-06 14:06:17 +0530|
README: refer to upstream documentation instead of downstream...
Change-Id: I8c8cf5f179d0cacb2dc9ffbdc6ed6c5bbcc04abb Signed-off-by: Michael Adam <email@example.com>
Diffstat (limited to 'README.md')
1 files changed, 3 insertions, 2 deletions
@@ -106,9 +106,10 @@ The hosts involved:
* Create a gluster trusted storage pool of the 3 nodes
- (192.168.1.11, 192.168.1.12 and 192.168.1.13).
+ 192.168.1.11, 192.168.1.12, and 192.168.1.13.
+ * Read more about [trusted storage pools](https://gluster.readthedocs.io/en/latest/Administrator%20Guide/Storage%20Pools/).
* Create a gluster volume called `block-test` on the gluster cluster.
-* Read More on how to [create a gluster volume](https://access.redhat.com/documentation/en-US/Red_Hat_Storage/2.1/html/Administration_Guide/sect-User_Guide-Setting_Volumes-Replicated.html)
+ * Read More on how to [create a gluster volume](https://gluster.readthedocs.io/en/latest/Administrator%20Guide/Setting%20Up%20Volumes/#creating-replicated-volumes).
In the following, you can execute gluster-block CLI from any of the 3
nodes where glusterd and gluster-blockd are running.