Bug 1823695 - [Gdeploy] Content modification required under gdeploy section in Administration Guide.
Summary: [Gdeploy] Content modification required under gdeploy section in Administrati...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: Documentation
Version: rhgs-3.5
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: RHGS 3.5.z Batch Update 2
Assignee: Amrita
QA Contact: Mugdha Soni
URL:
Whiteboard:
Depends On:
Blocks: 1822630
TreeView+ depends on / blocked
 
Reported: 2020-04-14 09:57 UTC by Mugdha Soni
Modified: 2021-01-11 08:58 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-01-11 08:58:13 UTC
Embargoed:


Attachments (Terms of Use)

Description Mugdha Soni 2020-04-14 09:57:53 UTC
Document URL: 
----------------------------
1. In section " 5.1. Setting up Gluster Storage Volumes using gdeploy" under sub section "5.1.1. Getting Started" there is a command " ,After modifying the configuration file, invoke the configuration using the command: 

"# gdeploy -c conf.txt".

This commands is present in various sections and needs to be modified to " gdeploy -c txt.conf".

------------------------------------------------------------------------------
2.Under section "5.1.4. Creating Volumes" under "For example, for a basic trusted storage pool of a 3 x 3 replicate volume the configuration details in the configuration file will be as follows: "
The brick_dirs need to be added in this conf file else the volume creation will fail.

##The conf file is suppose to be :-

[hosts]
10.70.47.X
10.70.47.Y
10.70.46.Z

[volume]
action=create
volname=rep1
replica=yes
replica_count=3
brick_dirs=/glus/brick1/b1,/glus/brick1/b1,/glus/brick1/b1
force=yes

Comment 1 Mugdha Soni 2020-04-15 13:12:26 UTC
If the user directly copies the command from the documentation he will not be able to run any of gdeploy conf files.

Comment 4 Mugdha Soni 2020-04-28 16:15:09 UTC
I see this command as "gdeploy -c conf_filename" ,somewhere  as "gdeploy -c <config_file_name>" and some where as "gdeploy -c txt.conf" . This a standard command used for the execution of the gdeploy conf file.
So can we keep this command same everywhere?

Comment 6 Mugdha Soni 2020-04-29 06:54:22 UTC
All the changes as requested are made .
Hence,moving the bug to verified state.


Note You need to log in before you can comment on or make changes to this bug.