some more bits about libgfapi can be fetched from
https://github.com/gluster/glusterfs/blob/master/doc/features/libgfapi.md
--Humble
On Wed, Jul 9, 2014 at 10:27 AM, Vijay Bellur wrote:
> On 07/09/2014 10:09 AM, Viktor Villafuerte wrote:
>
>> Hi all,
>>
>> On Gluster website I can see section
On 07/09/2014 10:09 AM, Viktor Villafuerte wrote:
Hi all,
On Gluster website I can see section "Language bindings" for the
libgfapi C library for Java/Python/.. However I cannot find any
documentation of the interface itself.
Are there any docs on how to use libgfapi using C?
The api header
SRC:
http://bits.gluster.org/pub/gluster/glusterfs/src/glusterfs-3.4.5beta2.tar.gz
This release is made off jenkins-release-80
-- Gluster Build System
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://supercolony.gluster.org/mailman/lis
On 05/30/2014 01:16 PM, Niels de Vos wrote:
Documentation in the wiki, mainly these pages:
- http://www.gluster.org/community/documentation/index.php/Main_Page#Developers
- http://www.gluster.org/community/documentation/index.php/Developers
- Over time make these new comers as experienced d
- Original Message -
> On Tue, Jul 8, 2014 at 11:33 AM, John Mark Walker
> wrote:
>
> > Here's what I need from you:
> >
> > 1. vote on the topics above. If you don't like the topics, feel free to add
> > one (or a few)
>
> * NSR
I would love a session on NSR. Oh Jeff...
And AFR2, for
On Tue, Jul 8, 2014 at 11:33 AM, John Mark Walker wrote:
> Here's what I need from you:
>
> 1. vote on the topics above. If you don't like the topics, feel free to add
> one (or a few)
* NSR
* SSL
* 4.0
* ARM
* Btrfs
* Erasure coding
> 2. nominate experts to cover the above. This could be anyo
Greetings,
At one point earlier this year, we had a good cadence producing online hangouts
with Gluster experts: https://www.youtube.com/user/GlusterCommunity/videos
There were some really good ones, but we stopped doing them due to resources
and time. However, we'd like to relaunch the program
On 2014-07-08 13:01, Justin Clift wrote:
> On 08/07/2014, at 11:51 AM, Anders Blomdell wrote:
>> It seems like
>> http://www.gluster.org/community/documentation/index.php/CompilingRPMS
>> is missing one crucial step:
>>
>> $ ./autogen.sh
>> $ ./configure --enable-fusermount
>> $ make dist
>> ...
>
On 08/07/2014, at 11:51 AM, Anders Blomdell wrote:
> It seems like
> http://www.gluster.org/community/documentation/index.php/CompilingRPMS
> is missing one crucial step:
>
> $ ./autogen.sh
> $ ./configure --enable-fusermount
> $ make dist
> ...
> $ cd extras/LinuxRPM
> $ make glusterrpms
>
> sh
It seems like
http://www.gluster.org/community/documentation/index.php/CompilingRPMS
is missing one crucial step:
$ ./autogen.sh
$ ./configure --enable-fusermount
$ make dist
...
$ cd extras/LinuxRPM
$ make glusterrpms
should be:
$ rm -f ./autom4te.cache/* # make sure to use current
On 08/07/2014, at 9:53 AM, Anders Blomdell wrote:
> 2. What are the rules for marking a bug as blocking the trackers (can't find
> one for
> 3.6.0 yet, so currently a moot point).
We should probably create an alias thing for 3.6.0, like we
have for 3.5.2:
https://bugzilla.redhat.com/show_bu
On 2014-07-07 21:13, Niels de Vos wrote:
> On Mon, Jul 07, 2014 at 07:29:15PM +0200, Anders Blomdell wrote:
>> On 2014-07-07 18:17, Niels de Vos wrote:
>>> On Mon, Jul 07, 2014 at 04:48:18PM +0200, Anders Blomdell wrote:
On 2014-07-07 15:08, Lalatendu Mohanty wrote:
>> # rpm -U ./glusterfs
Hi,
I have submitted 2 patches for improving User Serviceable Snapshots
experience. Both of them have passed regression tests.
[1] It contains changes which improves snapview-server's compatibility
with NFS server. Changes include these:
A) Make snapview-server xlator handle listxattr ca
Adding rhs-gabbar
On 07/08/2014 01:54 PM, Avra Sengupta wrote:
In the test case, we are checking gluster snap status to see if all
the bricks are alive. One of the snap bricks fail to start up, and
hence we see the failure. The brick fails to bind with "Address
already in use" error. But if we
In the test case, we are checking gluster snap status to see if all the
bricks are alive. One of the snap bricks fail to start up, and hence we
see the failure. The brick fails to bind with "Address already in use"
error. But if we see clearly that same log also says "binding to
failed", where
15 matches
Mail list logo
