Red Hat Bugzilla – Bug 764695
Need a mechanism to get inputs from community
Last modified: 2013-12-18 19:06:20 EST
Need a mechanism to collect troubleshooting information, deployment scenarios, QA test cases etc from the community.
Some thoughts from the community on this topic are in this thread
I am still not clear about how CLI can do this... lets talk more on it
the idea here is a command which will get user a tarball, which will contain volume information, cluster info (peer status etc), log files, (if there is a core; core details)
bash# gluster get-setup details [VOLNAME]
details captured in /tmp/gluster.<PID>.<EPOCH>.tar.gz
How about coming out with some scripts which will be doing this for us? Instead of making 'glusterd' bulky to handle all these.
Will give out these two scripts and we can make it a separate rpm altogether, or even we can add them in 'extras/' directory of glusterfs release tarballs/rpms
Fine with me Amar.
VS, we have 'sosreport' now with RHS, and significant command line options are added to get the brick status. Hope that suffice as reason to close this bug. Will close it as WORKSFORME, please re-open this, if you have more thoughts.