| Summary: | Need a mechanism to get inputs from community | ||
|---|---|---|---|
| Product: | [Community] GlusterFS | Reporter: | Vidya Sakar <vs> |
| Component: | cli | Assignee: | Amar Tumballi <amarts> |
| Status: | CLOSED WORKSFORME | QA Contact: | |
| Severity: | low | Docs Contact: | |
| Priority: | medium | ||
| Version: | mainline | CC: | gluster-bugs, vraman |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-04-17 19:10:03 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | DP | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Vidya Sakar
2011-05-31 09:21:23 UTC
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 bash# VS, 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. |