glusterfs-afrv1.git/cli/src/cli-cmd-volume.c, branch v3.3.0qa15

glusterd: Extended glusterd_is_service_running to get svcs's pid.

2011-11-18T12:22:25+00:00

Also, volume status cmd would print "N/A" if pid couldn't be
retrieved from pidfile.

Change-Id: Ie83d228b1cf86397d181885b325e337a403e6ed2
BUG: 3043
Reviewed-on: http://review.gluster.com/650
Tested-by: Gluster Build System 
Reviewed-by: Amar Tumballi 
Reviewed-by: Vijay Bellur

glusterd/cli: rpc cleanup

2011-11-16T09:45:24+00:00

no more backward compatibility between glusterd <-> glusterd

Change-Id: Ibfcca1c7e315a90b2639c4cba8da19b11875051a
BUG: 3158
Reviewed-on: http://review.gluster.com/610
Tested-by: Gluster Build System 
Reviewed-by: Shishir Gowda 
Reviewed-by: Krishnan Parthasarathi 
Reviewed-by: Vijay Bellur

XDR: cli-glusterd xdr consolidation

2011-11-16T09:42:29+00:00

By using only 1 xdr struct for request and 1 xdr struct for response,
we will be able scale better and also be able to parse the o/p better

For request use-
        gf1_cli_req - contains dict
For response use-
        gf1_cli_rsp - conains op_ret, op_errno, op_errstr, dict

Change-Id: I94b034e1d8fa82dfd0cf96e7602d4039bc43fef3
BUG: 3720
Reviewed-on: http://review.gluster.com/662
Tested-by: Gluster Build System 
Reviewed-by: Amar Tumballi

changing of the volume types after volume is created.

2011-10-28T12:42:08+00:00

with this patch, one can do all the below operations:

on a simple distribute volume 'test' with bricks A,B, add bricks C and D:

 bash# gluster volume add-brick test replica 2 C D

now the volume 'test' becomes distribute-replicate, with pairs A-C, B-D.
same holds good for stripe.

and now, one can change the replica count 2 on volume 'test' to 4 like below:

 bash# gluster volume add-brick test replica 4 E F G H

now, volume has 'replica' count 4, with pairs being 'A-C-E-F' and 'B-D-G-H'.

after this, if user wants to reduce the replica count, he can do

 bash# gluster volume remove-brick test replica 3 C H # (one from each pair)

This should work to reduce the replica count

Change-Id: I4f109141a9ba7be4a92a5f5810a4163baeb92973
BUG: 3305
Reviewed-on: http://review.gluster.com/158
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

cli: add geo-replication log-rotate command

2011-10-21T06:26:23+00:00

Rotating geo-replication master/monitor log files from cli.
On invocation, the log file for a given master-slave session
is backed up with the current timestamp suffixed to the file
name and signal is sent to gsyncd to start logging to a new
log file.

Sample commands:

* Rotate log file for this : session:
gluster volume geo-replication   log-rotate

* Rotate log files for all session for master volume 
gluster volume geo-replication  log-rotate

* Rotate log files for all sessions:
gluster volume geo-replication log-rotate

Change-Id: I75f641b4e082a04d5373c18583ca4a1d9651d27a
BUG: 3519
Reviewed-on: http://review.gluster.com/529
Tested-by: Gluster Build System 
Reviewed-by: Csaba Henk

cli : new volume statedump command

2011-09-27T13:45:10+00:00

Changes:
        1. Add a new 'volume statedump' command, that performs statedumps of
        all the bricks in the volume and saves them in a specified location.
        2. Add new server option 'server.statedump-path'.
        3. Remove multiple function definitions in glusterd.h

Statedump Information:

The 'volume statedump' command performs statedumps on all the bricks in
a given volume. The syntax of the command is,
        gluster volume statedump  [type]......

Types include,
        * all
        * mem
        * iobuf
        * callpool
        * priv
        * fd
        * inode
Defaults to 'all' when no type is specified.

The statedump files are created by default in /tmp directory of the
server on which the bricks are present.
This path can be changed by setting the 'server.statedump-path' option.

The statedump files will be named as,
        ..dump

Change-Id: I01c0e1a8aad490da818e086d89f292bd2ed06fd4
BUG: 1964
Reviewed-on: http://review.gluster.com/321
Tested-by: Gluster Build System 
Reviewed-by: Amar Tumballi

glusterd: support for resetting single option

2011-09-27T12:38:36+00:00

Allows resetting of only single options using 'volume reset' command.
New syntax of volume reset is: 'volume reset [option] [force]'.
Giving "all" as options or not specifying an option, causes all options
to be reset.

Change-Id: Ib9e220f326adeb1be1a774737a0b12c910012cea
BUG: 2980
Reviewed-on: http://review.gluster.com/450
Tested-by: Gluster Build System 
Reviewed-by: Amar Tumballi

glusterd: Implemented cmd to trigger self-heal on a replicate volume.

2011-09-22T16:43:25+00:00

This cmd is used in the context of proactive self-heal for replicated
volumes. User invokes the following cmd when (s)he suspects that self-heal
needs to be done on a particular volume,
        gluster volume heal .

Change-Id: I3954353b53488c28b70406e261808239b44997f3
BUG: 3602
Reviewed-on: http://review.gluster.com/454
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

cli: enable order checking stripe-replicate volumes

2011-09-19T11:36:42+00:00

This is a followup patch to  e378778686fca24934e76c41e6496b12162a5420
Enables brick order checking for volumes of type stripe replicate.

Change-Id: Ib9b090a3514d05bb7602c423de7d3123f107a3b5
BUG: 2441
Reviewed-on: http://review.gluster.com/455
Reviewed-by: Amar Tumballi 
Tested-by: Gluster Build System

cli : check for bad brick order while creating replicate volume

2011-09-19T06:46:09+00:00

gluster cli now checks the brick order when creating
a replicate or distributed-replicate volume.
If a non-optimal order is found the user is given a
warning and asked if the volume creation can proceed.

Change-Id: I38c4cb65bffb40ccf95319cf3f4f3423a4cdebe9
BUG: 2407
Reviewed-on: http://review.gluster.com/151
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur