Bug 1365837

Hi Atin,

Could you please provide all the required info needed to work on this RFE?

Regards,
Divya

Samikshan,

Please work with Divya to provide all the required contents for CCS team to proceed with documenting this RFE.

~Atin

(In reply to Atin Mukherjee from comment #4)
> Samikshan,
> 
> Please work with Divya to provide all the required contents for CCS team to
> proceed with documenting this RFE.
> 
> ~Atin

Samikshan,

I have drafted the content for this RFE based on your inputs and our discussion.

Link to the draft: https://docs.google.com/document/d/1tn6AdgwVqYgS1VjAk5tEUmTPUxuFkzouqioWWxq5LLU/edit#

Could you please review the draft and share your comments in the google doc?

Thanks!

(In reply to Divya from comment #5)
> (In reply to Atin Mukherjee from comment #4)
> > Samikshan,
> > 
> > Please work with Divya to provide all the required contents for CCS team to
> > proceed with documenting this RFE.
> > 
> > ~Atin
> 
> Samikshan,
> 
> I have drafted the content for this RFE based on your inputs and our
> discussion.
> 
> Link to the draft:
> https://docs.google.com/document/d/
> 1tn6AdgwVqYgS1VjAk5tEUmTPUxuFkzouqioWWxq5LLU/edit#
> 
> Could you please review the draft and share your comments in the google doc?
> 

Hi Divya. The draft looks good. Thanks.

~Samikshan

(In reply to Divya from comment #5)
> (In reply to Atin Mukherjee from comment #4)
> > Samikshan,
> > 
> > Please work with Divya to provide all the required contents for CCS team to
> > proceed with documenting this RFE.
> > 
> > ~Atin
> 
> Samikshan,
> 
> I have drafted the content for this RFE based on your inputs and our
> discussion.
> 
> Link to the draft:
> https://docs.google.com/document/d/
> 1tn6AdgwVqYgS1VjAk5tEUmTPUxuFkzouqioWWxq5LLU/edit#
> 
> Could you please review the draft and share your comments in the google doc?
> 

I have found 2 issues with the draft document and have suggested the respective changes.

~ Samikshan

Thanks  Samikshan!

I have incorporated your suggestions and ported the content to the Admin Guide. Link to the Admin Guide: http://ccs-jenkins.gsslab.brq.redhat.com:8080/job/doc-Red_Hat_Gluster_Storage-3.2-Administration_Guide-branch-BZ-1365837-Node_Level_Status/lastSuccessfulBuild/artifact/tmp/en-US/html-single/index.html#obtaining_node_level_information


Merge request WIP lodged here: https://gitlab.cee.redhat.com/red-hat-gluster-storage-documentation/3.2-Administration_Guide/merge_requests/18

This is now waiting on peer review to move to ON_QA.

NI on Anjana to assign a reviewer.

Incorporated peer review comments; setting to ON_QA.

You can find "Obtaining Node Information" section here: http://ccs-jenkins.gsslab.brq.redhat.com:8080/job/doc-Red_Hat_Gluster_Storage-3.2-Administration_Guide-branch-master/lastSuccessfulBuild/artifact/tmp/en-US/html-single/index.html#obtaining_node_information

Please keep in mind that this build contains only merged changes and not all changes for RHGS 3.2 are merged yet.

Divya,

Here is the following change that is required:
Under - "Executing the get-state Command" of section 19.6

The command goes as below:
#  gluster get-state glusterd [odir path_to_output_dir] [file filename] 
Usage:  get-state [options]

Please change it to:
#  gluster get-state [odir path_to_output_dir] [file filename] 
Usage:  get-state [options]

Hint: There is no 'glusterd' keyword required with get-state command

(In reply to SATHEESARAN from comment #12)

Sas,

I have updated the get-state command based on your comment 12.

Link to the latest doc: http://ccs-jenkins.gsslab.brq.redhat.com:8080/job/doc-Red_Hat_Gluster_Storage-3.2-Administration_Guide-branch-master/lastSuccessfulBuild/artifact/tmp/en-US/html-single/index.html#obtaining_node_information

Moving the bug ON_QA.

Verified the doc changes as per comment13

RHGS 3.2.0 GA completed on 23 March 2017