glusterfs.git/cli/src/cli-cmd-parser.c, branch v3.2.1qa2

cli: fix up parsing of geo-replication status

2011-04-22T11:05:20+00:00

Signed-off-by: Csaba Henk 
Signed-off-by: Anand Avati 

BUG: 2785 (gsyncd logs on slave side go to /dev/null)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2785

cli: change geo-replication syntax to support slave-only invocation

2011-04-21T07:39:55+00:00

(for sake of slave side configurability).

Also pulled out sub-op, now we have

  volume geo-replication [] [] {start|stop|config|status} [options...]

-- more convenient to use when working on a given session (ie. we just change the
geo-rep subcommands), and aligns better with other volume commands, cf. eg.

  volume replace-brick    {start|pause|abort|status|commit}

Signed-off-by: Csaba Henk 
Signed-off-by: Anand Avati 

BUG: 2785 (gsyncd logs on slave side go to /dev/null)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2785

geo-replication: revamp CONFIG command

2011-04-21T07:39:50+00:00

Drop the config_type RPC req field, use just a "subop" key in the param dict.

Signed-off-by: Csaba Henk 
Signed-off-by: Anand Avati 

BUG: 2785 (gsyncd logs on slave side go to /dev/null)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2785

mgmt/glusterd: unify the geo-replication status rpc messages.

2011-04-18T04:40:59+00:00

the intelligence of determining the type of status command is now at glusterd,
rather then explicitly setting it while parsing at cli.

Signed-off-by: Kaushik BV 
Signed-off-by: Anand Avati 

BUG: 2536 (gsync service introspection)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2536

TOP: validate bs/count pair for write/read-perf measurement

2011-04-16T06:33:14+00:00

If either one the above args are supplied, the other arg should be
supplied too.

Signed-off-by: shishir gowda 
Signed-off-by: Anand Avati 

BUG: 2771 (bs or count tag missing with volume top write-perf/read-perf command blocks glusterd)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2771

top: Modified integer bounds check for count/bs

2011-04-15T11:28:46+00:00

Signed-off-by: Krishnan Parthasarathi 
Signed-off-by: Anand Avati 

BUG: 2721 (Incorrect validation message in gluster top CLI)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2721

use "geo-replication" all over as the official name of this feature

2011-04-15T07:31:08+00:00

Use GEOREP macro if you want to refer to the feature in code.

Signed-off-by: Csaba Henk 
Signed-off-by: Anand Avati 

BUG: 2757 (refactory gsync/gsyncd/syncdaemon/whatever to geo-replication)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2757

mgmt/glusterd: Implementation of volume gsync status [master [slave]]

2011-04-14T08:00:55+00:00

Changes made in the path of gsync start/stop as well, where we
maintain a list of  active gsync sessions, hence gsync stop could be
executed at all nodes.
A new dict in glusterd_volinfo_t added to maintain an active list
of gsync slaves running on each master.

Signed-off-by: Kaushik BV 
Signed-off-by: Anand Avati 

BUG: 2536 (gsync service introspection)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2536

cli: simplfy gsysnc configuration command

2011-04-13T11:43:27+00:00

New syntax is

 volume gsync config   [[!]opt [val]]

In details:

- instead of "volume gsyncd configure M S config-get-all" :
             "volume gsyncd config M S"
- instead of "volume gsyncd configure M S config-get O" :
             "volume gsyncd config M S O"
- instead of "volume gsyncd configure M S config-del O" :
             "volume gsyncd config M S !O"
- instead of "volume gsyncd configure M S config-set O V" :
             "volume gsyncd config M S O V"

Signed-off-by: Csaba Henk 
Signed-off-by: Anand Avati 

BUG: 2738 ("volume gsync configure   config- ..." is overly verbose)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2738

cli: join value arguments of "gsync config-set" with spaces

2011-04-13T11:43:22+00:00

When a given gsync tunable is supposed to hold a command (which
can take options), it's quite possible that it spaces in its value.
Try to approximate this situation by joining the leftover arguments.

Signed-off-by: Kaushik BV 
Signed-off-by: Csaba Henk 
Signed-off-by: Anand Avati 

BUG: 2713 ([glusterfs-3.2.0qa10]: config-set works only for one value)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2713