glusterfs.git/xlators/mgmt/glusterd, branch v3.2.0

mgmt/glusterd: Fix ret value in importing of options/gsync slaves

2011-04-22T17:36:31+00:00

In case the volume options or gsync slaves are absent the import should
succeed.

Signed-off-by: Pranith Kumar K 
Signed-off-by: Anand Avati 

BUG: 2832 (peer probe hangs)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2832

mgmt/glusterd: fix up the buffer sizes to accomodate a correct estimate of sizes of the snprintf invocations, and errout if not feasible

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

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

BUG: 2561 (gsyncd command's must be preconfigured)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2561

cli: check if gsyncd is present in the configured place, enable geo-replication if present

2011-04-22T10:52:28+00:00

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

BUG: 2744 (make geo-replication package friendly)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2744

glusterd / cli: make the needed changes to let a masterless geo-rep config request get thru

2011-04-21T14:38:23+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

do not allow create volume or add-brick if given path or any brick is a part of either

2011-04-21T10:35:45+00:00

Signed-off-by: Raghavendra Bhat 
Signed-off-by: Anand Avati 

BUG: 2803 ([glusterfs-3.2.0qa14]: volume create succeeds even though there is a volume with an export directory in the path of current volume)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2803

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

glusterd: log the error immedietly after the syscall failure

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

Signed-off-by: Raghavendra Bhat 
Signed-off-by: Anand Avati 

BUG: 2346 (Log message enhancements in GlusterFS - phase 1)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2346

glusterd / geo-rep: harvesting further benefits of static gsyncd pre-config

2011-04-19T09:30:47+00:00

- log-file does not need to be a reserved option anymore as we
  wouldn't overwrite the user setting
- reimplement glusterd_gsync_get_param_file(): all use cases
  have now pre-configured values, so instead of putting together
  the needed pathname by ourselves, we can just get it from
  gsyncd config
  - refactor it to a common backend with glusterd_get_canon_url()

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

glusterd / geo-rep: do all gsyncd pre-configuration in glusterd init

2011-04-19T09:30:43+00:00

This is made possible by gsyncd config templating, by which
session specific settings can be expressed in a generic form.

Benefits:
- in glusterd we use only generic (rx pattern based) config settings
  so we don't violate users' freedom to make settigs for their sessions
- don't have to invoke gsyncd in excess to prepare a session
- we can pre-configure slave side too (relying on the templates and
  gsyncd service auto-discovery)
- much leaner, much more expressive code

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

gsyncd service auto-discovery

2011-04-19T09:30:28+00:00

If glusterd is running, gsyncd will find it out and adopt related settings
automagically (even if started from not by glusterd)

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