glusterfs-quota.git/cli/src, branch test

cli :remove-brick process output leads to ambiguity

2013-07-24T18:05:04+00:00

The output of remove-brick  status as "Not started" leads to
ambiguity.We should not show the status of the Server nodes
which do not participate in the remove-brick process.

Change-Id: I85fea40deb15f3e2dd5487d881f48c9aff7221de
BUG: 986896
Signed-off-by: susant 
Reviewed-on: http://review.gluster.org/5383
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

cli: gluster volume heal commands are more elaborative

2013-07-24T12:18:05+00:00

1. "gluster volume heal volume-name"
output :Launching heal operation to perform index self heal on volume volume-name has been successful

2. "gluster volume heal volume-name full"
Output :Launching heal operation to perform full self heal on volume volume-name has been successful

3. "gluster volume heal volume-name info"
Output :Gathering list of entries to be healed on volume volume-name has been successful 

4. "gluster volume heal volume-name info healed"
Output :Gathering list of healed entries on volume volume-name has been successful 

5. "gluster volume heal volume-name info split-brain"
Output :Gathering list of split brain entries on volume volume-name has been successful 

6. "gluster volume heal volume-name info heal-failed"    
Output :Gathering list of heal failed entries on volume volume-name has been successful 

Change-Id: I74c90e8129d23d513ddb7879358a9d21c94a5c0d
BUG: 978936
Signed-off-by: Venkatesh Somyajulu 
Reviewed-on: http://review.gluster.org/5286
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

cli: Increased timeout for gluster volume heal commnads

2013-07-23T09:52:42+00:00

Problem:
If number of files are very large, then gluster volume heal
volumename info commnads take large time. So timeout of 2
minutes seems to be insufficient.

Fix:
Increased timeout to 10 minutes

Change-Id: I5f847163e01c4afbb587b726833ad80183f1a928
BUG: 986945
Signed-off-by: Venkatesh Somyajulu 
Reviewed-on: http://review.gluster.org/5372
Reviewed-by: Kaushal M 
Tested-by: Gluster Build System

cli: check for null in is_server_debug_xlator()

2013-07-12T11:14:12+00:00

Command: gluster volume set  diagnostics.client-log-level trace
Expected output:
"volume set: failed: option log-level trace: 'trace' is not valid
(possible options are DEBUG, WARNING, ERROR, INFO, CRITICAL, NONE,
TRACE.)"
Current output: gluster cli receives a segmentation fault
Fix: check for NULL before calling strstr

Change-Id: If4c7a85a635849a388cf122543e12349c109643c
BUG: 982174
Signed-off-by: Ravishankar N 
Reviewed-on: http://review.gluster.org/5298
Reviewed-by: Kaushal M 
Tested-by: Gluster Build System

cli: Fix remove brick cli out for wrong volume name

2013-07-04T12:25:31+00:00

Problem:  gluster volume remove-brick command, was not printing the error in
          case of volume-name specified is wrong.

Fix:      Fix will print error message to indicate that provided volume name is
          invalid. Although patch for bug 961669
          http://review.gluster.org/#/c/4975/ does print cli-output now, but
          still xml is unable to use the response values

Change-Id: I2ee1df86c1e756fb8e93b4d6bbdd102b4f368f87
BUG: 961307
Signed-off-by: Venkatesh Somyajulu 
Reviewed-on: http://review.gluster.org/4972
Reviewed-by: Pranith Kumar Karampuri 
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

cli: Fix in letter case in volume heal output

2013-07-04T05:29:52+00:00

Change-Id: I25d13444c2cbff9b26642e91677ad1e09e77aa1e
BUG: 978936
Signed-off-by: Venkatesh Somyajulu 
Reviewed-on: http://review.gluster.org/5259
Reviewed-by: Pranith Kumar Karampuri 
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

glusterd: Log peer op status at the appropriate time

2013-06-19T05:15:12+00:00

Change-Id: Ia8e1af082078f2f791708ba4faa4992bf291dd6e
BUG: 961339
Signed-off-by: Krutika Dhananjay 
Reviewed-on: http://review.gluster.org/5023
Reviewed-by: Amar Tumballi 
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

glusterd: Add a cmd for getting uuid of local node

2013-06-10T19:20:05+00:00

Usage: gluster system:: uuid get

This is needed since we generate uuid of a node in a lazy manner. ie, we
generate a uuid for the node only on the first volume or peer operation,
when the node needs an external identity.  With this command, we can
force[1] the uuid generation, without a volume or peer operation performed.

[1]: Querying for uuid (or uuid get), forces uuid to come into
existence.

Change-Id: I62c8b6754117756aa4d773dd48af4ddeb1a1d878
BUG: 971661
Signed-off-by: Krishnan Parthasarathi 
Reviewed-on: http://review.gluster.org/5175
Tested-by: Gluster Build System 
Reviewed-by: Kaushal M

cli: Remove unused port info from peer status.

2013-06-05T12:28:17+00:00

Problem: "gluster peer status" on some nodes gives port info and fails to give
on other. But it is a hard coded value.

Fix: Removing the port info from command

Change-Id: I919f0349f252e658bfc13e60bb8e171da32eaf25
BUG: 964026
Signed-off-by: Venkatesh Somyajulu 
Reviewed-on: http://review.gluster.org/5027
Reviewed-by: Kaushal M 
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

cli: set min-op-version and max-op-version for getspec

2013-05-31T06:46:38+00:00

Change-Id: I2185df5d6b560d9367ae404c91812048e1655180
BUG: 969193
Signed-off-by: Jeff Darcy 
Reviewed-on: http://review.gluster.org/5119
Reviewed-by: Kaushal M 
Tested-by: Gluster Build System