[Gluster-devel] glusterd log file is renamed now

2016-07-06 Thread Atin Mukherjee
This is a heads up to all devs that we have now renamed the glusterd log file from $INSTALL_PREFIX-etc-glusterfs-glusterd.vol.log to glusterd.log in mainline [1] to avoid confusions for many gluster users. I've seen users reverting to emails asking for which log file to look at when asked for

[Gluster-devel] [PATCH v2 1/1] block/gluster: add support to choose libgfapi logfile

2016-07-06 Thread Prasanna Kumar Kalever
currently all the libgfapi logs defaults to '/dev/stderr' as it was hardcoded in a call to glfs logging api, in case if debug level is chosen to DEBUG/TRACE gfapi logs will be huge and fill/overflow the console view. this patch provides a commandline option to mention log file path which helps in

[Gluster-devel] Securing GlusterD management

2016-07-06 Thread Jeff Darcy
As some of you might already have noticed, GlusterD has been notably insecure ever since it was written. Unlike our I/O path, which does check access control on each request, anyone who can craft a CLI RPC request and send it to GlusterD's well known TCP port can do anything that the CLI

[Gluster-devel] Weekly community meeting - 06/Jun/2016

2016-07-06 Thread Kaushal M
Today's meeting didn't go according to the agenda, as we initially had low attendance. Attendance overall was low as well owing to a holiday in Bangalore. The meeting minutes and logs for the meeting are available at the links below, Minutes:

[Gluster-devel] rebalance immediately fails 3.7.11, 3.7.12, 3.8.0

2016-07-06 Thread Wade Holler
Hi All, i am trying to do some gluster testing for my customer. I am experiencing the same issue as described here: http://serverfault.com/questions/782602/glusterfs-rebalancing-volume-failed Except: I have dispersed-distributed volume. And I only let the fix-layout run for a few hours

Re: [Gluster-devel] Non Shared Persistent Gluster Storage with Kubernetes

2016-07-06 Thread Pranith Kumar Karampuri
On Wed, Jul 6, 2016 at 12:24 AM, Shyam wrote: > On 07/01/2016 01:45 AM, B.K.Raghuram wrote: > >> I have not gone through this implementation nor the new iscsi >> implementation being worked on for 3.9 but I thought I'd share the >> design behind a distributed iscsi