On 08/12/2013 01:52 PM, Justin Clift wrote:
For 3.5, I'd like to propose we add a way for people to easily add custom
translators they've written. (using C, or Glupy, or whatever)
I'm not actually sure (yet) how we'd go about doing it, so would like to
discuss it first before writing things up.
On 12/08/2013, at 8:55 PM, Joe Julian wrote:
> Or as json:
> {
> "translator": {
>"name": "features/marker",
>"type": "server",
>"graph": { "before": "debug/io-stats" },
>"subvolume": { "count": 1 },
>"cli": {
> "target": "volume",
> "options": {
>"option": [
On 08/12/2013 12:52 PM, Joe Julian wrote:
On 08/12/2013 12:17 PM, Justin Clift wrote:
On 12/08/2013, at 7:44 PM, Jay Vyas wrote:
i like the install file idea. packaging always seems easier and
memorizing CLI magic seems like another feature which would lend
itself more to forcing devs to rea
On 08/12/2013 12:17 PM, Justin Clift wrote:
On 12/08/2013, at 7:44 PM, Jay Vyas wrote:
i like the install file idea. packaging always seems easier and memorizing
CLI magic seems like another feature which would lend itself more to forcing
devs to read documentation to get it working correct
On 12/08/2013, at 8:50 PM, Jay Vyas wrote:
> okay makes sense. so .. um How about json ? :)
Yeah, might be a bunch more readable. Also easier to
work with from things like Node.js.
Just personally not sure how to structure it well
with JSON.
Suggestions? :)
+ Justin
--
Open Source and Stand
okay makes sense. so .. um How about json ? :)
___
Gluster-devel mailing list
Gluster-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/gluster-devel
On 12/08/2013, at 7:44 PM, Jay Vyas wrote:
> i like the install file idea. packaging always seems easier and memorizing
> CLI magic seems like another feature which would lend itself more to forcing
> devs to read documentation to get it working correctly. The deployment via
> packaging is al
i like the install file idea. packaging always seems easier and
memorizing CLI magic seems like another feature which would lend itself
more to forcing devs to read documentation to get it working correctly.
The deployment via packaging is always easier to modify and learn on the
fly
Hi all,
For 3.5, I'd like to propose we add a way for people to easily
add custom translators they've written. (using C, or Glupy,
or whatever)
I'm not actually sure (yet) how we'd go about doing it, so
would like to discuss it first before writing things up. :)
As a first thought, maybe we coul
On 08/11/2013 04:26 PM, KueiHuan Chen wrote:
Hi,
I can't find the bugzilla record for this. When 3.4 release comes
out, there has a Known issue list inside it[1]. Replace-brick operation
is broken in this release and i had also tested and make sure it's
broken in 3.4. So i wonder is there any
Hi all,
For Gluster 3.5, I'd like to propose we get some kind of
*multi-node* testing framework in place for Gluster.
The existing test framework is single node only, which
doesn't fit well for a distributed file system.
I've recently looked into Autotest in depth, but ruled
it out since it's:
On 08/12/2013 10:10 PM, Kaleb S. KEITHLEY wrote:
On 08/12/2013 12:19 PM, Mike Ma wrote:
Hi Kaleb,
I've recently managed to mount and use a gluster volume on FreeBSD, with
the latest FreeBSD head.
So maybe the next step is to test it with some test suites?
Can I ask what benchmarks you normally
On 12/08/2013, at 5:40 PM, Kaleb S. KEITHLEY wrote:
> On 08/12/2013 12:19 PM, Mike Ma wrote:
>> Hi Kaleb,
>>
>> I've recently managed to mount and use a gluster volume on FreeBSD, with
>> the latest FreeBSD head.
>> So maybe the next step is to test it with some test suites?
>> Can I ask what benc
On 08/12/2013 12:19 PM, Mike Ma wrote:
Hi Kaleb,
I've recently managed to mount and use a gluster volume on FreeBSD, with
the latest FreeBSD head.
So maybe the next step is to test it with some test suites?
Can I ask what benchmarks you normally use?
What tests should I pass?
In the source tre
On 12.08.2013 11:45, Nux! wrote:
I've done the wireshark test and here are the results. There don't
seem to be any NFS v2 calls. "Properties" on the mounted volume shows
NFS version 3 as well.
Everything is very slow and the mounted volume shows as
"disconnected" (i.e. has a big red X on it). I'
On 09.08.2013 21:06, Niels de Vos wrote:
Slow browsing could indicate that the NFS-client does not use
READDIRP(LUS) but only READDIR with a lot of LOOKUP calls.
If you capture a tcpdump and feed it through a recent version of
wireshark you can get some statistics. When you capture a tcpdump, u
Hi all,
- Original Message -
> From: "Balamurugan Arumugam"
> To: "Niels de Vos"
> Cc: "Balamurugan Arumugam" , gluster-devel@nongnu.org,
> gluster-us...@gluster.org
> Sent: Friday, August 9, 2013 6:53:11 PM
> Subject: Re: [Gluster-devel] new glusterfs logging framework
>
>
>
> ---
Hi all,
- Original Message -
> From: "Balamurugan Arumugam"
> To: "Niels de Vos"
> Cc: "Balamurugan Arumugam" , gluster-devel@nongnu.org,
> gluster-us...@gluster.org
> Sent: Friday, August 9, 2013 6:53:11 PM
> Subject: Re: [Gluster-devel] new glusterfs logging framework
>
>
>
> ---
18 matches
Mail list logo
