On Tue, Apr 29, 2014 at 2:31 AM, Joe Julian j...@julianfamily.org wrote:
+10 for json... ;)
Well if it has --xml, then adding --json is pretty easy:
gluster command argument --xml | ./xml2json
--i-dont-know-if-this-is-real-but-it-is-trivial-to-write
Supporting more than one stable output
OTOH, it should also be trivial to use a json library.
On April 28, 2014 11:35:50 PM PDT, James purplei...@gmail.com wrote:
On Tue, Apr 29, 2014 at 2:31 AM, Joe Julian j...@julianfamily.org
wrote:
+10 for json... ;)
Well if it has --xml, then adding --json is pretty easy:
gluster command
The --xml option is in plan as a good to have. I am trying to
get this done by code freeze time.
Best Regards,
Rajesh
- Original Message -
From: James purplei...@gmail.com
To: gluster-devel gluster-devel@gluster.org
Sent: Tuesday, April 29, 2014 11:45:06 AM
Subject: Re: [Gluster-devel]
On 04/29/2014 03:41 AM, Niels de Vos wrote:
On Tue, Apr 29, 2014 at 05:30:14AM +0100, Justin Clift wrote:
Hi Kaleb,
Investigating a failure in rpm.t on Rackspace, in release-3.5
branch (but not master).
Noticed something interesting while looking. (May not be related
to the problem). In
On Tue, Apr 29, 2014 at 06:25:15AM -0400, Vikhyat Umrao wrote:
Hi,
I am interested in TODO wireshark features for GlusterFS :
I can start from below given feature for one procedure:
= display the filename or filehandle on the summary for common procedures
Things to get you and others
I guess my point about loss of data following a restore boils down to the
change of brick names that the restore process forces. I may be wrong but
doesn't this mean that any downstream monitoring/scripts have to adjust their
idea of what the volume looked like - it just sounds like more work
Hi All,
As discussed in the last community meeting [1], we are considering
addition of sub-maintainers to GlusterFS. The intent of this activity is
to streamline our patch management and make it more scalable.
The responsibilities of sub-maintainers would include:
1. Overall patch
Hi All,
I am happy to announce that Niels de Vos will be the release maintainer
for release-3.5. Kaleb Keithley will continue to function as the release
maintainer for release-3.4. Please join me in congratulating Niels on
his new role and extend your co-operation to him for further 3.5.x
