andy/glusterfs
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
461888bb63
glusterfs/doc
History
Amar Tumballi 250cdb3005 rpc: add more document on programs and actors 
Also give hints on where to look for relevant structures.

Fixes #140

Change-Id: If29f67fb6fd39379045fe774559934fb13cbede8
Signed-off-by: Amar Tumballi <amarts@redhat.com>
Reviewed-on: https://review.gluster.org/16925
Smoke: Gluster Build System <jenkins@build.gluster.org>
Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
Tested-by: Raghavendra G <rgowdapp@redhat.com>
CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
Reviewed-by: Vijay Bellur <vbellur@redhat.com>
2017-05-15 02:19:41 +00:00
..
debugging glusterd: add a cli command to trigger a statedump on a client 2017-01-23 19:13:15 -05:00
developer-guide rpc: add more document on programs and actors 2017-05-15 02:19:41 +00:00
features common-ha: reliable grace using pacemaker notify actions 2016-03-14 21:34:27 -07:00
gluster.8 glusterd: Add client details to get-state output 2017-04-12 23:43:08 -04:00
glusterd.8 Fix docs to reflect change in GLUSTERD_DEFAULT_WORKDIR 2012-10-05 09:52:51 -07:00
glusterfs.8 Made spelling changes to 19 files 2014-03-16 11:57:21 -07:00
glusterfsd.8 core: assorted typos and spelling mistakes reported by Debian lintian 2016-05-18 02:21:42 -07:00
Makefile.am doc: Move glusterd.vol to extras/ directory 2013-08-22 23:59:01 -07:00
mount.glusterfs.8 core: assorted typos and spelling mistakes reported by Debian lintian 2016-05-18 02:21:42 -07:00
README.md Adding README for gluster documentation project 2015-07-26 03:26:57 -07:00

README.md

Admin Guide

The gluster administration guide is maintained at github. The browsable admin guide can be found here.

The doc patch has to be sent against the above mentioned repository.

Features/Spec

The Gluster features which are 'in progress' or implemented can be found at github.

Upgrade Guide

The gluster upgrade guide is maintained at github. The browsable upgrade guide can be found here

The doc patch has to be sent against the above mentioned repository.

For more details about the docuemntation workflow please refer this discussion