glusterfs.git/xlators/mgmt/glusterd/src/glusterd.c, branch v3.3.1qa1

glusterd: Run post hooks on a different thread

2012-05-29T10:20:37+00:00

This change ensures post hooks can 'wait' if need be
and _not_ prevent glusterd from being able to run other operations
meanwhile.

Also ensures that post hook scripts are 'serialized'
between transactions. ie, post hook scripts of txn1 are completed
before post hook scripts of txn2 are started, where txn1 happens before
txn2.

Change-Id: Iaeb676737d8c67e7151127c8d1fd8c2891e10aee
BUG: 806996
Signed-off-by: Krishnan Parthasarathi 
Reviewed-on: http://review.gluster.com/3476
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

glusterd / mountbroker: warn if mountbroker-root permissions are suspected to be too strict

2012-05-23T09:01:02+00:00

At the level of mountbroker, this is a best effort, as "too strict" depends
on the purpose it's being used for (thus we just warn, don't err). However,
it's a good guess, as it stands for existing use cases of mountbroker.

Change-Id: Ic5e7d6cb44ced5509c05e0ee8a9043252470683f
BUG: 765214
Signed-off-by: Csaba Henk 
Reviewed-on: http://review.gluster.com/3171
Tested-by: Gluster Build System 
Reviewed-by: Anand Avati 
Reviewed-on: http://review.gluster.com/3406
Reviewed-by: Vijay Bellur

glusterd: Fixed glusterd_brick_create_path algo.

2012-05-19T10:27:20+00:00

- check if any prefix of the brick path has "trusted.gfid"
  or "trusted.glusterfs.volume-id" set.
- set trusted.glusterfs.volume-id on the bricks as soon as
  its induction into the volume is settled. Earlier, the setting of
  "volume-id" used to happen during the first run of the brick process,
  leaving of window for bricks part of one volume to be (ab)used by another
  volume inadvertently.
- removed creation of brick directory (if missing), during start volume force.
  This is to avoid directory creation as part 'force'ful starting of volume
  and leave the responsibility with the user, who understands the
  'availability' of the export directory (brick) better.

Change-Id: I4237ec4ea7a4e38a7501027e7de7112edd67de8c
BUG: 812214
Signed-off-by: Krishnan Parthasarathi 
Reviewed-on: http://review.gluster.com/3280
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur 
Reviewed-on: http://review.gluster.com/3313

core: coverity issues fixed

2012-04-23T21:52:57+00:00

this is not a complete set of issues getting fixed. Will
address other issues in another patch.

Change-Id: Ib01c7b11b205078cc4d0b3f11610751e32d14b69
Signed-off-by: Amar Tumballi 
BUG: 789278
Reviewed-on: http://review.gluster.com/3145
Tested-by: Gluster Build System 
Reviewed-by: Jeff Darcy

glusterd: Moved 'hooks' interface code to glusterd-hooks.*

2012-04-19T07:36:26+00:00

Change-Id: Ia7c0e37154414bddb05516e11b3cc4e6ae83ff38
BUG: 806996
Signed-off-by: Krishnan Parthasarathi 
Reviewed-on: http://review.gluster.com/3142
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

glusterd: Modified algo for creating hooks directories.

2012-04-09T16:23:14+00:00

- This change will ensure that hooks directories are created
when glusterd is upgraded from a version that doesn't have
the hooks feature or the 'current' hooks version.

Change-Id: I8a0ea64eda52a15b1605b98588b9b19df209a73e
BUG: 806996
Signed-off-by: Krishnan Parthasarathi 
Reviewed-on: http://review.gluster.com/3111
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

glusterd: Added init scripts like interface for gluster commands

2012-03-31T12:15:08+00:00

Directories to hold the scripts mentioned above would be created for each
gluster command under glusterd's 'working dir' as follows:
(eg.)
/hooks/version/create/pre

/hooks/version/create/post

where, version corresponds to the version of hook scripts.

The scripts beginning with 'S' under the above directories would be run before
(pre) and after (post) the volume created. The scripts would receive a command
line argument as below:
--volname=

This can be optionally used  by the script.

Change-Id: Ia81b4ff9dd4477d99dd59b39c805aa645521edb0
BUG: 806996
Signed-off-by: Krishnan Parthasarathi 
Reviewed-on: http://review.gluster.com/3010
Tested-by: Gluster Build System 
Reviewed-by: Csaba Henk 
Reviewed-by: Vijay Bellur

glusterd: bring in feature to use syncop for mgmt ops

2012-03-21T18:58:11+00:00

* new sycnop routines added to mgmt program
* one should not use 'glusterd_op_begin()', instead can use the
  synctask framework, 'glusterd_op_begin_synctask()'
* currently using for below operations:
  'volume start', 'volume rebalance', 'volume quota',
  'volume replace-brick' and 'volume add-brick'

Change-Id: I0bee76d06790d5c5bb5db15d443b44af0e21f1c0
BUG: 762935
Signed-off-by: Amar Tumballi 
Reviewed-on: http://review.gluster.com/479
Tested-by: Gluster Build System 
Reviewed-by: Anand Avati

Change option brick-with-valgrind to run-with-valgrind

2012-03-18T06:45:04+00:00

brick-with-valgrind does not make much sense because all the
glusterfs/glusterfsd server processes are run with valgrind.
So changing the option from brick-with-valgrind to
run-with-valgrind.
Also fix misspelt 'valgrnd' for valgrind log file namenames.

Change-Id: I87aad6d65ffc37d8f8679be215709a9174385ecd
BUG: 804293
Signed-off-by: Rahul C S 
Reviewed-on: http://review.gluster.com/2965
Tested-by: Gluster Build System 
Reviewed-by: Anand Avati

cli, glusterd, nfs: "volume status|profile|top" for nfs servers

2012-03-14T09:27:42+00:00

Enables usage of volume monitoring operations "volume status", "volume top" and
"volume profile" for nfs servers. These operations can be performed on
nfs-servers  by passing "nfs" as an option in cli. The output is similar to the
normal brick outputs for these commands.

The new syntaxes for the changed commands are as below,
 #gluster volume profile  {start|info|stop} [nfs]
 #gluster volume top  {[open|read|write|opendir|readdir [nfs]]
               |[read-perf|write-perf [nfs|{bs  count }]]}
               [brick ] [list-cnt ]
 #gluster volume status [all |  [nfs|]]
          [detail|clients|mem|inode|fd|callpool]

Change-Id: Ia6eb50c60aecacf9b413d3ea993f4cdd90ec0e07
BUG: 795267
Signed-off-by: Kaushal M 
Reviewed-on: http://review.gluster.com/2820
Tested-by: Gluster Build System 
Reviewed-by: Krishnan Parthasarathi