Re: [Gluster-devel] Branching out Gluster docs

[Humble Devassy Chirammal]

Hi Nigel,

I am fine with  branching out current master to a new branch and keep
master with 4.x series as long as the urls are properly redirected or
doesnt give 404. That said, gluster documentation is referred from various
sources and we should not break it.

Regarding version banner, I am more than 100% happy to have it.


--Humble


On Sat, Mar 17, 2018 at 7:29 PM, Nigel Babu  wrote:

> Hello folks,
>
> Our docs need a significant facelift. Nithya has suggested that we branch
> out the current docs into a branch called version-3 (or some such, please
> let's not bikeshed about the name) and have the master branch track 4.x
> series. We will significantly change the documentation for master branch so
> that it has a better content flow as well as give correct instructions for
> working with GD2.
>
> Among other things, we'll have to add a banner to the docs that highlights
> which version you're looking at. This is not a problem, I can handle that.
>
> Humble and Prashant, do you both agree this is a good idea? I'm happy to
> do all the work needed to make this happen.
>
> --
> nigelb
>
> ___
> Gluster-devel mailing list
> Gluster-devel@gluster.org
> http://lists.gluster.org/mailman/listinfo/gluster-devel
>
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] [GD2] New dev release - GlusterD2 v4.0dev-3

[Humble Devassy Chirammal]

Good going !!

Does this embedded etcd capable of connecting or working with external etcd
if its availble ?

--Humble


On Thu, Nov 17, 2016 at 8:36 PM, Kaushal M  wrote:

> I'm pleased to announce the third development release of GD2.
>
> The big news in this release is the move to embedded etcd. You no
> longer need to install etcd separately. You just install GD2, and do
> you work, just like old times with GD1.
>
> Prashanth was all over this release, in addition to doing the
> embedding work, he also did a lot of minor cleanup and fixes, and a
> lot of linter fixes.
>
> Prebuilt binaries for Linux x86-64 are available from the release page
> [1]. A docker image gluster/glusterd2-test [2] has also been created
> with this release.
>
> Please refer to the 'Testing releases' wiki [3] page for more
> information on how to go about installing, running and testing GD2.
> This also contains instructions on how to make use of the docker image
> with Vagrant to set up a testing environment.
>
> Thanks,
> Kaushal
>
> [1]: https://github.com/gluster/glusterd2/releases/tag/v4.0dev-3
> [2]: https://hub.docker.com/r/gluster/glusterd2-test/builds/
> bgr3aitcjysvfmgubfk3ud/
> [3]: https://github.com/gluster/glusterd2/wiki/Testing-releases
> ___
> Gluster-devel mailing list
> Gluster-devel@gluster.org
> http://www.gluster.org/mailman/listinfo/gluster-devel
>
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] Container Repo Change + > 50K downloads of Gluster Container images

[Humble Devassy Chirammal]

On Thu, Oct 20, 2016 at 11:56 AM, Humble Devassy Chirammal <
humble.deva...@gmail.com> wrote:

> Hi All,
>
> We have kept our official Gluster Container images  in Docker hub for
> CentOS and Fedora distros for some time now.
>
> https://hub.docker.com/r/gluster/gluster-centos/
> https://hub.docker.com/r/gluster/gluster-fedora/
>
>
> I see massive increase in the download of these container images for past
> few months. This is indeed a good sign.  :) .. It seems that, we will be
> crossing 100k+ downloads soon. :)
>


Yes, we are  in 100k+ club , Waiting for 200k+   :)


>
> As a side note, to address some of the copyright issues, I have renamed
> our source container repo to "https://github.com/gluster/
> gluster-containers" from "https://github.com/gluster/docker;.   Whoever
> forked this repo or contributing to this repo may  take a note of this
> change .
>
> Please let us know if you  have any queries on this.
>
> --Humble
>
>
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel

[Gluster-devel] Container Repo Change + > 50K downloads of Gluster Container images

[Humble Devassy Chirammal]

Hi All,

We have kept our official Gluster Container images  in Docker hub for
CentOS and Fedora distros for some time now.

https://hub.docker.com/r/gluster/gluster-centos/
https://hub.docker.com/r/gluster/gluster-fedora/


I see massive increase in the download of these container images for past
few months. This is indeed a good sign.  :) .. It seems that, we will be
crossing 100k+ downloads soon. :)

As a side note, to address some of the copyright issues, I have renamed our
source container repo to "https://github.com/gluster/gluster-containers;
from "https://github.com/gluster/docker;.   Whoever  forked this repo or
contributing to this repo may  take a note of this change .

Please let us know if you  have any queries on this.

--Humble
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] Interested in contributing to Gluster Documentation

[Humble Devassy Chirammal]

Hi Srravya,

Welcome to Gluster Community !

>
I am Srravya. I recently came across Gluster on the list of
communities/organisations participating in Outreachy
. Upon going through
the list of projects Gluster has listed for the internship, I noticed that
one of them is a documentation project. As a new comer to Gluster, I
believe this would be a good way for me to get started in understanding
Gluster and make my first contributions.
>

Yes, it will give a good start and introduction to the  community.

>
I would love to interact with community members including developers and
documentation team members to know how best I can begin working on Gluster.
It would be great if I could be pointed to any documentation bugs/tasks I
could pick and also general docs on getting started and initial set up
steps.
>

Give a start with the workflow which Nigel mentioned.

Please feel free to open issues/PRs in github documentation project and if
need help, ping us on #gluster or #gluster-dev.


--Humble
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] [Gluster-users] CFP for Gluster Developer Summit

[Humble Devassy Chirammal]

You are very welcome !

--Humble


On Fri, Aug 19, 2016 at 5:10 PM, Mohamed Ashiq Liyazudeen <
mliya...@redhat.com> wrote:

> Hi,
>
> I would like to be co-presenter for the talk(Containers and Persistent
> Storage for Containers).
>
> --ashiq
>
> - Original Message -
> From: "Humble Devassy Chirammal" <humble.deva...@gmail.com>
> To: "Manoj Pillai" <mpil...@redhat.com>
> Cc: "Gluster Devel" <gluster-devel@gluster.org>, "Amye Scavarda" <
> ascav...@redhat.com>, "gluster-users Discussion List" <
> gluster-us...@gluster.org>
> Sent: Friday, August 19, 2016 1:46:52 PM
> Subject: Re: [Gluster-users] [Gluster-devel] CFP for Gluster Developer
> Summit
>
> Title: Containers and Perisstent Storage for Containers.
>
> Theme: Integration with emerging technologies.
>
> I would like to cover below topics in this talk.
>
> *) Brief Overview about containers.
> *) Storage in containers
> *) Persistent Storage for containers.
> *) Storage hyperconvergence.
>
> --Humble
>
>
>
>
>
> ___
> Gluster-users mailing list
> gluster-us...@gluster.org
> http://www.gluster.org/mailman/listinfo/gluster-users
>
> --
> Regards,
> Mohamed Ashiq.L
>
>
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] CFP for Gluster Developer Summit

[Humble Devassy Chirammal]

Title: Containers and Perisstent Storage for Containers.

Theme: Integration with emerging technologies.

I would like to cover below topics in this talk.

*) Brief Overview about containers.
*) Storage in containers
*) Persistent Storage for containers.
*) Storage hyperconvergence.

--Humble
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] Reducing the size of the glusterdocs git repository

[Humble Devassy Chirammal]

On Wed, May 18, 2016 at 3:26 PM, Amye Scavarda  wrote:

>
>
>
>
>>
> All in favor of the 'everyone working on this should clone again'
> approach.
>

+2 on the same thought. :)

>
>
>
>
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] Suggest a feature redirect

[Humble Devassy Chirammal]

Hi Amye,

afaict, the feature proposal has start from glusterfs-specs (
http://review.gluster.org/#/q/project:glusterfs-specs) project under
review.gluster.org

--Humble


On Wed, May 18, 2016 at 12:15 PM, Amye Scavarda  wrote:

> Currently on the gluster.org website, we're directing the 'Suggest a
> feature' to the old mediawiki site for 'Features'.
> http://www.gluster.org/community/documentation/index.php/Features
>
> In an ideal world, this would go somewhere else. Where should this go?
> Let me know and I'll fix it.
> - amye
>
> --
> Amye Scavarda | a...@redhat.com | Gluster Community Lead
>
> ___
> Gluster-devel mailing list
> Gluster-devel@gluster.org
> http://www.gluster.org/mailman/listinfo/gluster-devel
>
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] Documentation @ readthedocs.org - search broken

[Humble Devassy Chirammal]

Hi Andre,

Thanks for pointing this. Yes, we see  its broken due to some rearrangement
in the directory structure of 'features' and  'feature planning'
directories. This happens  mainly because, the search results are still
taken from the previous directory layout and not the latest one.
We are working on this with readthedocs team and hopefully will have a
resolution soon. Till then you can also go through
the feature pages repo which is https://github.com/gluster/glusterfs-specs.

Please let us know if you need any help.

--Humble


On Tue, Jan 19, 2016 at 3:48 PM, André Bauer  wrote:

> Hi List,
>
> for me it seems the documentation is somewhat broken at them moment.
>
> If you go to https://gluster.readthedocs.org/en/latest/ an search for
> "sharding" you get 3 links. All links are broken:
>
> "SORRY - This page does not exist yet"
>
> If you search for something in Google (e.g. "glusters sharding") you're
> pointed to the old gluster documentation with the first link, which
> should have an info, that the docs now are at readthedocs.org
>
>
> --
> Regards
> André Bauer
> ___
> Gluster-devel mailing list
> Gluster-devel@gluster.org
> http://www.gluster.org/mailman/listinfo/gluster-devel
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] Writing a new xlator is made a bit easier now

[Humble Devassy Chirammal]

Nice one Poornima++ !!

--Humble


On Thu, Dec 24, 2015 at 11:32 AM, Poornima Gurusiddaiah  wrote:

> Hi All,
>
> Here is a patch http://review.gluster.org/#/c/13061/ that creates the
> initial template for any new xlator that you wish to write.
>
> How to use:
> $ python ./generate_xlator.py   
>
> Eg: python ./generate_xlator.py /home/u1/glusterfs/xlators/features
> compression cmpr
> This command will create the following files with some initial contents
> like copyright, fops definition, header definition etc. :
> * /home/u1/glusterfs/xlators/features/compression/Makefile.am
> * /home/u1/glusterfs/xlators/features/compression/src/Makefile.am
> * /home/u1/glusterfs/xlators/features/compression/src/compression.c
> * /home/u1/glusterfs/xlators/features/compression/src/compression.h
> *
> /home/u1/glusterfs/xlators/features/compression/src/compression-mem-types.h
> *
> /home/u1/glusterfs/xlators/features/compression/src/compression-messages.h
>
> By default all the fops and other functions are generated, if you do not
> need to implement certain functions, delete those functions from the the
> file `config.py`.
> One can customize the fop definition by changing CBK_TEMPLATE/FOP_TEMPLATE
> in generate_xlator.py.
>
> This is an addition to Jeff's http://review.gluster.org/#/c/9411/
> Reviews are welcome.
>
> Merry Christmas:)
>
> Regards,
> Poornima
>
>
>
>
>
> ___
> Gluster-devel mailing list
> Gluster-devel@gluster.org
> http://www.gluster.org/mailman/listinfo/gluster-devel
>
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] few queries regarding file snapshot feature in gluster

[Humble Devassy Chirammal]

Hi Prasanna,

The feature page has some details about this
http://www.gluster.org/community/documentation/index.php/Features/File_Snapshot
https://github.com/gluster/glusterfs-specs/blob/master/done/Features/file-snapshot.md

--Humble


On Wed, Dec 23, 2015 at 5:20 AM, Vijay Bellur  wrote:

> On 12/21/2015 06:47 AM, Prasanna Kumar Kalever wrote:
>
>> Hi Team,
>>
>> I have few queries regarding file snapshot feature in gluster
>>
>> what are the limitations of Block device translator and qemu-block
>> translator ?
>> Are we using them some where ?
>> Do we have plans to improve them ?
>> Or someone have a design to implement file snapshot feature ?
>>
>>
> I have not heard much feedback about these two translators. The qemu-block
> functionality can be handy for exposing virtual block devices and due to
> features like native snapshotting, it could be quite interesting in use
> cases that require virtual block devices.
>
> The qemu-block translator has not been tested of late. A few months back I
> tried mkfs.xfs after attaching the block device and it failed. I did not
> find more time to look into that further.
>
> file snapshotting could be a possibility with dht2 but I don't think much
> work has happened in that direction.
>
> The other possibilities for file snapshotting include reflinks and
> overlay. Given that reflinks support is most probably going to land
> sometime in xfs, we might be able to leverage this feature and explore the
> possibility of providing snapshots with backend filesystems that are
> reflink capable (btrfs, xfs etc.).
>
>
>> I am really thankful if some one gives more details about qemu-block
>> xlator,
>> I don't see enough documentation regarding this :(
>>
>>
> qemu-block xlator provides the ability to snapshot files by relying on
> qcow2/qed image formats. what specific details are you looking for?
>
> Avati & Brian probably have the maximum context about this translator.
>
> Regards,
> Vijay
>
>
>
> ___
> Gluster-devel mailing list
> Gluster-devel@gluster.org
> http://www.gluster.org/mailman/listinfo/gluster-devel
>
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] few queries regarding file snapshot feature in gluster

[Humble Devassy Chirammal]

Hi Prasanna,

>I am really thankful if some one gives more details about qemu-block
xlator,
I don't see enough documentation regarding this :(
>
Have you gone through
https://github.com/gluster/glusterfs/blob/master/doc/developer-guide/bd-xlator.md
? It has enough pointers to the bd xlator.

--Humble


On Mon, Dec 21, 2015 at 5:17 PM, Prasanna Kumar Kalever  wrote:

> Hi Team,
>
> I have few queries regarding file snapshot feature in gluster
>
> what are the limitations of Block device translator and qemu-block
> translator ?
> Are we using them some where ?
> Do we have plans to improve them ?
> Or someone have a design to implement file snapshot feature ?
>
> Are we just waiting till btrfs or zfs are fully stable ?
>
> I am really thankful if some one gives more details about qemu-block
> xlator,
> I don't see enough documentation regarding this :(
>
> Thanks,
> -Prasanna ​
>
>
> ___
> Gluster-devel mailing list
> Gluster-devel@gluster.org
> http://www.gluster.org/mailman/listinfo/gluster-devel
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] removing "Target Release" from GlusterFS bug reports.

[Humble Devassy Chirammal]

Hi Kaleb,

I do think, this field is not used by gluster users when reporting the bug,
so 'ack' from me as conveyed in bug triaging meeting.

--Humble


On Tue, Nov 24, 2015 at 6:16 PM, Kaleb KEITHLEY  wrote:

> Hi,
>
> As discussed during today's Bug Triage meeting it is proposed to remove
> the Target Release from all GlusterFS bug reports.
>
> This field is apparently not used by anyone, and it's not described in
> the Bug Triage process at
> http://gluster.readthedocs.org/en/latest/Contributors-Guide/Bug-Triage/
>
> Any objections?
>
> --
>
> Kaleb
> ___
> Gluster-devel mailing list
> Gluster-devel@gluster.org
> http://www.gluster.org/mailman/listinfo/gluster-devel
>
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] Glusterfs mainline BZs to close...

[Humble Devassy Chirammal]

Hi Niels,

>
  Our shiny docs (or my bookmarks?) are broken again...

http://gluster.readthedocs.org/en/latest/Developer-guide/Bug%20report%20Life%20Cycle/
  http://gluster.readthedocs.org/en/latest/Developer-guide/Bug%20Triage/

>
As you know, the "Developer Guide" is now part of glusterfs source code (
https://github.com/gluster/glusterfs/tree/master/doc/developer-guide) [1].
The decision to split the glusterfs documentation  into three parts (
developer spec/feature , Administration ) came late and it caused the
bookmark to break.

Being Media Wiki  READONLY, we thought this type of documents can be part
of Developer Guide for now. May be we need to sort the "developer guide" in
source code repo  again and put it into correct buckets, but this needs
some time and effort.


[1]

Because of the gerrit plugin issue, the commits in gerrit has not been
synced to github since Sep 10. However you can see the the change here
http://review.gluster.org/#/c/12227/

--Humble


On Mon, Oct 26, 2015 at 2:44 PM, Niels de Vos  wrote:

> On Wed, Oct 21, 2015 at 05:22:49AM -0400, Nagaprasad Sathyanarayana wrote:
> > I came across the following BZs which are still open in mainline.  But
> > they are fixed and made available in a upstream release.  Planning to
> > close them this week, unless there are any objections.
>
> We have a policy to close bugs when their patches land in a released
> version. The bugs against mainline will get closed when a release is
> made that contains those fixes. For many of the current mainline bugs,
> this would be the case when glusterfs-3.8 is released.
>
> What is the concern of having bugs against the mainline version open
> until a release contains that particular fix? There are many bugs that
> also get backports to stable versions (3.7, 3.6 and 3.5). Those bugs get
> closed with each minor releases for that stable version.
>
> Of course we can change our policy to close mainline bugs earlier. But,
> we need to be consistent in setting the rules for that, and document
> them well. There is an ongoing task about automatically changing the
> status of bugs when patches get posted/merged and releases made. Closing
> mainline bugs should be part of that process.
>
> When do you suggest that a bug against mainline should be closed, when
> one of the stable releases containst the fix, or when all of them do?
> What version with fix should we point the users at when we closed a
> mainline bug?
>
>   Our shiny docs (or my bookmarks?) are broken again...
>
> http://gluster.readthedocs.org/en/latest/Developer-guide/Bug%20report%20Life%20Cycle/
>   http://gluster.readthedocs.org/en/latest/Developer-guide/Bug%20Triage/
>
>   This is the old contents:
>
> http://www.gluster.org/community/documentation/index.php/Bug_report_life_cycle
>   http://www.gluster.org/community/documentation/index.php/Bug_triage
>
> I was about to suggest to send a pull request so that we can discuss
> your proposal during the weekly Bug Triage meeting on Tuesdays.
> Unfortunately I don't know where the latest documents moved to, so
> please send your changes by email.
>
> Could you explain what Bugzilla query you used to find these bugs? We
> have some keywords (like "Tracking") that should be handled with care,
> and probably should not get closed even when patches were merged in
> mainline and stable releases.
>
> Thanks,
> Niels
>
>
> >
> >
> 1211836,1212398,1211132,1215486,1213542,1212385,1210687,1209818,1210690,1215187,1215161,1214574,1218120,1217788,1216067,1213773,1210684,1209104,1217937,1200262,1204651,1211913,1211594,1163561,1176062,
> >
> 1219784,1176837,1208131,1200704,1220329,1221095,1172430,1219732,1219738,1213295,1212253,1211808,1207615,1216931,1224290,1217701,1223213,1223889,1223385,1221104,1221696,1219442,1224596,1165041,1225491,
> >
> 1221938,1226367,1215002,1222379,1221889,1220332,1223338,1224600,1222126,1212413,1211123,1225793,1226551,1218055,1220713,1223772,1222013,1227646,1228635,1227884,1224016,1223432,1227904,1228952,1228613,
> >
> 1209461,1226507,1225572,1227449,1220670,1225564,1225424,1200267,1229825,1230121,1228696,1228680,1229609,1229134,1231425,1229172,1232729,1208482,1169317,1180545,1231197,1188242,1229658,1232686,1234842,
> >
> 1235216,1235359,1235195,1235007,1232238,1233617,1235542,1233162,1233258,1193388,1238072,1236270,1237381,1238508,1230007,1210689,1240254,1240564,1241153,1193636,1132465,1226717,1242609,1238747,1242875,
> >
> 1226279,1240210,1232678,1242254,1232391,1242570,1235231,1240654,1240284,1215117,1240184,1228520,1244165,1243187,1243774,1209430,1196027,1232572,1202244,1229297,1246052,1246082,1238135,1245547,1234819,
> >
> 1224611,1221914,1207134,1245981,1246432,1178619,1243890,1240598,1240949,1247930,1247108,1245544,1238936,1232420,1245142,1226223,1250441,1229860,1245276,1246275,1250582,1249499,1231437,1241274,1212437,
> >
> 

Re: [Gluster-devel] Journal translator spec

[Humble Devassy Chirammal]

HI All,

>>
I thought all specifications and design documented were supposed to get
pushed into Gerrit for glusterfs-specs?

  https://github.com/gluster/glusterfs-specs

>>

glusterfs-specs in github is READONLY mirror of*
http://review.gluster.org/#/q/project:glusterfs-specs
* project in gerrit,
same as glusterfs project.

So, the feature spec should land in gerrit first and review can happen from
there.

>
My understanding is that someone (Humble?) was working on getting the
merged documents included on the readthedocs page.
>

Its not there yet.

To conclude:

The admin docs patches  has to go in  *https://github.com/gluster/glusterdocs
* as PRs . As soon as the patch is
merged it will reflect in gluster.readthedocs.org.

The feature spec or design in
*http://review.gluster.org/#/q/project:glusterfs-specs
* project in gerrit
and its auto synced to https://github.com/gluster/glusterfs-specs/

The developer doc is inside GlusterFS source code repo ( *
https://github.com/gluster/glusterfs/tree/master/doc/developer-guide
* ).

--Humble


On Fri, Oct 16, 2015 at 11:19 PM, Niels de Vos  wrote:

> On Fri, Oct 16, 2015 at 02:29:22PM +, Jeff Darcy wrote:
> > October 14 2015 11:02 PM, "Atin Mukherjee"  wrote:
> > > Could you push the design document along with the journal spec to
> > > gluster.readthedocs.org as PRs?
> >
> > It's not clear where in the hierarchy these should go.  I would have
> > guessed "Developer-guide" but that's back in the main source tree now.
> > Should I create a new directory for design specs?
>
> I thought all specifications and design documented were supposed to get
> pushed into Gerrit for glusterfs-specs?
>
>   https://github.com/gluster/glusterfs-specs
>
> My understanding is that someone (Humble?) was working on getting the
> merged documents included on the readthedocs page. Not sure when we can
> expact that...
>
> Niels
>
> ___
> Gluster-devel mailing list
> Gluster-devel@gluster.org
> http://www.gluster.org/mailman/listinfo/gluster-devel
>
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] Next v3.6 maint release suggested commits

[Humble Devassy Chirammal]

Thanks !!
Ccing 3.6.X release maintainer to make sure he is not missing this mail.

--Humble


On Fri, Sep 11, 2015 at 1:30 AM, Richard Wareing  wrote:

> Greetings,
>
> Just a heads up, there's a very nasty deadlock bug w/ multi-core e-poll in
> v3.6.x (latest branch) which appear to be due to DHT doing naughty things
> (like racing among other things).  So to fix these issues we had to pull in
> these (trivial cherry-pick) commits from master:
>
> 565ef0d826b356d188028410575da1f0fa9416b7
> 5a0aced9802d12f45cebf1b318e20676395570f9
> b387c485c069c201ddabebe00c7176f960f4be32
> 2691a650f94ed9f82ecb8dda5d9b12f52147dc51
> 532566802b58d847d1ff1818ea857b583049ee76
> 50a92b2d72a43a940b0e38340d161fa7687a7104
> df83769d4c6c6bb13df70751640b2a90af0064d7
> 9f8b4c2ef3523f91213a00edec863f322e92a6d5
> 68dfe137c7dfa08fb601257309f3db7e3ce6e4e8
> e57a5eef4ea0da579986e9b61fec47a50ddf2b8a
> 2a3b7086957b095a5bbb5325aab0f765496e8491
> 393de0d7fd4309f4262a8747183f164e8f6d23c1
> 48aa51d49800bafbad5825165d4798cbbe592f5a
> 4fcf231aac51668742114320068b1570cee75667
> 8ac26cf2302dc452d7448a769b6b117dbdaaf05c
> 40da6554acabedebc2259a8c867159e41e1079c2
> 39bbf0ed97c3a1e8bf2966b2561f964013cde606
> 20a014332504efbc0204a591cad257abb167fce7
> 83b65187148e1dd145752c61660b8e5902e9a94f
> 83b65187148e1dd145752c61660b8e5902e9a94f
> d60943ff2f6d58c129a66308f29986b471762210
> 6588d8f2a8975f032cb1567eef5ed35e5f992357
> 4ac9399be4f620abdaeee1054a48458c8238b907
> a7e30beef3ab41985e7435dc1a90cde30e07dc47
>
> (yes this is a lot of commits...but it fixes a lot of brokenness :) ).
>
> So for the next maintenance release it might be wise to include these
> fixes to better the experience for v3.6.x users out there who do not
> maintain their own builds.  Without these multi-core epoll under high load
> prone to deadlocks (repro'able by rsync'ing [rsync -avR --inplace] a 100k
> or so small files from one tmpfs mount to another tmpfs backed GFS cluster
> on a development/test machine).  Not sure if it's worth filing a bug report
> since the issue has clearly been fixed in newer releases.
>
> Richard
>
>
> ___
> Gluster-devel mailing list
> Gluster-devel@gluster.org
> http://www.gluster.org/mailman/listinfo/gluster-devel
>
>
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel

[Gluster-devel] Reminder: Gluster weekly community meeting

[Humble Devassy Chirammal]

Hi All,

In about 15 minutes from now, we will have the regular weekly Gluster
Community meeting.

Meeting details:
- location: #gluster-meeting on Freenode IRC
- date: every Wednesday
- time: 12:00 UTC, 14:00 CEST, 17:30 IST
   (in your terminal, run: date -d "12:00 UTC")
- agenda: https://public.pad.fsfe.org/p/gluster-community-meetings

Currently the following items are listed:
* Roll Call
* Status of last week's action items
* Gluster 3.7
* Gluster 3.6
* Gluster 3.5
* Gluster 3.8
* Gluster 4.0
* Open Floor
   - bring your own topic!

The last topic has space for additions. If you have a suitable topic to
discuss, please add it to the agenda. See you on IRC in 30 minutes!

Thanks,
--Humble
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel

[Gluster-devel] Minutes of the Weekly Gluster Community Meeting ( 9th Sep 2015)

[Humble Devassy Chirammal]

Hi All,

The minutes of today's meeting can be found at,

Minutes:
http://meetbot.fedoraproject.org/gluster-meeting/2015-09-09/gluster-meeting.2015-09-09-12.00.html
Minutes (text):
http://meetbot.fedoraproject.org/gluster-meeting/2015-09-09/gluster-meeting.2015-09-09-12.00.txt
 Log:
http://meetbot.fedoraproject.org/gluster-meeting/2015-09-09/gluster-meeting.2015-09-09-12.00.log.html

Meeting summary
---
* agenda is available @
  https://public.pad.fsfe.org/p/gluster-community-meetings  (hchiramm,
  12:01:43)
* roll call  (hchiramm, 12:04:49)

* Action items from last week:  (hchiramm, 12:05:17)

* msvbhat/rastar to send update mailing list with a DiSTAF how-to and
  start discussion on enhancements to DiSTAF  (hchiramm, 12:05:53)
  * LINK:
http://www.gluster.org/pipermail/gluster-devel/2015-September/046728.html
(anoopcs, 12:07:08)
  * LINK:
http://www.gluster.org/pipermail/gluster-devel/2015-September/046728.html
(hchiramm, 12:07:20)

* kshlm to check back with misc on the new jenkins slaves.  (hchiramm,
  12:08:57)

* krishnan_p to update Gluster News about Gluster.next progress
  (hchiramm, 12:10:02)
  * bi-weekly update on gluster news  (hchiramm, 12:13:36)
  * ACTION: kshlm to update Gluster News about Gluster.next progress
(hchiramm, 12:13:38)

* kshlm to check back with misc on the new jenkins slaves.  (hchiramm,
  12:14:03)
  * LINK: https://public.pad.fsfe.org/p/gluster-weekly-news kshlm
(hchiramm, 12:14:28)
  * ACTION: kshlm to check back with misc on the new jenkins slaves.
(hchiramm, 12:15:36)

* hagarth to post a note on gluster-devel asking for volunteers for the
  role of release maintainer for 3.7.5  (hchiramm, 12:16:02)

* poornimag to send a mail on gluster-devel asking for volunteers to
  backport glfs_fini patches to release-3.5  (hchiramm, 12:17:42)
  * ACTION: poornimag to send a mail on gluster-devel asking for
volunteers to backport glfs_fini patches to release-3.5  (hchiramm,
12:19:54)

* rastar to initiate discussion on exploring the different approaches
  towards doing GlusterFS release management and announcements
  (hchiramm, 12:20:21)
  * ACTION: rastar to initiate discussion on exploring the different
approaches towards doing GlusterFS release management and
announcements  (hchiramm, 12:24:19)
  * ACTION: kshlm or pkarampu need to setup 3.7.5 tracker.  (kshlm,
12:28:52)
  * LINK:

http://gluster.readthedocs.org/en/latest/Developer-guide/GlusterFS%20Release%20process/
(ndevos, 12:29:35)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1260420   (raghu`,
12:30:48)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1260420   (kshlm,
12:31:03)
  * 3.6.6 targetted for 21-09-2015  (kshlm, 12:31:25)
  * ACTION: raghu to announce target for 3.6.6 release  (kshlm,
12:33:13)
  * ndevos to do 3.5.6 release this weekend (~ 11 Sept)  (kshlm,
12:37:53)
  * ACTION: hagarth to di announcement about 3.8 once he finishes
collating information.  (kshlm, 12:45:01)
  * jdarcy is progressing with code-generation and etcd for NSR.
(kshlm, 12:46:17)
  * ACTION: tigert needs to be contacted to fix the favicon.  (kshlm,
12:50:06)
  * Jepsen could be used to test Gluster-4.0  (kshlm, 12:54:01)
  * LINK: https://github.com/aphyr/jepsen   (kshlm, 12:54:10)
  * kkeithley requires more reviewers for
http://review.gluster.org/#/c/11814  (kshlm, 12:56:41)

Meeting ended at 13:05:58 UTC.




Action Items

* kshlm to update Gluster News about Gluster.next progress
* kshlm to check back with misc on the new jenkins slaves.
* poornimag to send a mail on gluster-devel asking for volunteers to
  backport glfs_fini patches to release-3.5
* rastar to initiate discussion on exploring the different approaches
  towards doing GlusterFS release management and announcements
* kshlm or pkarampu need to setup 3.7.5 tracker.
* raghu to announce target for 3.6.6 release
* hagarth to di announcement about 3.8 once he finishes collating
  information.
* tigert needs to be contacted to fix the favicon.




Action Items, by person
---
* hagarth
  * hagarth to di announcement about 3.8 once he finishes collating
information.
* kshlm
  * kshlm to update Gluster News about Gluster.next progress
  * kshlm to check back with misc on the new jenkins slaves.
  * kshlm or pkarampu need to setup 3.7.5 tracker.
* **UNASSIGNED**
  * poornimag to send a mail on gluster-devel asking for volunteers to
backport glfs_fini patches to release-3.5
  * rastar to initiate discussion on exploring the different approaches
towards doing GlusterFS release management and announcements
  * raghu to announce target for 3.6.6 release
  * tigert needs to be contacted to fix the favicon.




People Present (lines said)
---
* kshlm (90)
* hchiramm (67)
* ndevos (42)
* justinclift (37)
* hagarth (33)
* atinm (18)
* krishnan_p (12)
* kkeithley (11)
* jdarcy (9)
* amye1 (8)
* raghu` (7)
* 

Re: [Gluster-devel] Gluster SOS plugin expansion

[Humble Devassy Chirammal]

Thanks Bipin for the input.
On Aug 28, 2015 9:50 AM, Bipin Kunal bku...@redhat.com wrote:

 Hi Hari/Humble,

 You might have already got my reply regarding the same on some different
 mail thread, Just sending here again,

 Here  is the few more area which I would wish part of gluster SOS plugin:
 1) geo-replication status corresponding to each geo-replication
 session(wherever applicable)

 # gluster volume geo-replication *MASTER_VOL **SLAVE_HOST*::*SLAVE_VOL* status

 2) Quota related information(wherever applicable)
 # gluster volume quota *VOLNAME* list
 # gluster volume quota *VOLNAME* status

 3) Heal information
 # gluster volume heal *VOLNAME* info
 4) Split-brain files
 # gluster volume heal *VOLNAME* info split-brain

 Thanks,
 Bipin Kunal

 On Thu, Aug 27, 2015 at 6:43 PM, Hari Gowtham hgowt...@redhat.com wrote:

 Hi Vijay,

 Thanks for the feed back. We will add those two in the plugin.

 - Original Message -
 From: Vijay Bellur vbel...@redhat.com
 To: Humble Devassy Chirammal humble.deva...@gmail.com, Gluster
 Devel gluster-devel@gluster.org
 Cc: hari gowtham005 hari.gowtham...@gmail.com
 Sent: Thursday, August 27, 2015 6:35:05 PM
 Subject: Re: [Gluster-devel] Gluster SOS plugin expansion

 On Thursday 27 August 2015 01:16 PM, Humble Devassy Chirammal wrote:
  Hi All,
 
  We have been working on the gluster plugin of SOS package [1].
 
  There were three commands (volume info, volume status and peer status)
  in it already and to expand it, we have added a few more( snapshot
  status, snapshot list, snapshot info, pool list, rebalance status).
 
  We would be happy if you could suggest the changes for this, as of to
  remove any command from the list or add anything more which can help
  gluster troubleshooting.
 
  [1] https://github.com/sosreport/sos/blob/master/sos/plugins/gluster.py
 

 Adding the following could be useful:

 volume quota volname info

 volume heal volname info

 Regards,
 Vijay

 ___
 Gluster-devel mailing list
 Gluster-devel@gluster.org
 http://www.gluster.org/mailman/listinfo/gluster-devel

 --
 Regards,
 Hari.

 ___
 Gluster-devel mailing list
 Gluster-devel@gluster.org
 http://www.gluster.org/mailman/listinfo/gluster-devel



 ___
 Gluster-devel mailing list
 Gluster-devel@gluster.org
 http://www.gluster.org/mailman/listinfo/gluster-devel


___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel

[Gluster-devel] Gluster SOS plugin expansion

[Humble Devassy Chirammal]

Hi All,

We have been working on the gluster plugin of SOS package [1].

There were three commands (volume info, volume status and peer status) in
it already and to expand it, we have added a few more( snapshot status,
snapshot list, snapshot info, pool list, rebalance status).

We would be happy if you could suggest the changes for this, as of to
remove any command from the list or add anything more which can help
gluster troubleshooting.

[1] https://github.com/sosreport/sos/blob/master/sos/plugins/gluster.py


--Humble
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] release schedule for glusterfs

[Humble Devassy Chirammal]

Hi Ragavendra,

This LGTM . However Is there any guide line on :

How many beta releases hit for each minor release ? and the gap between
these releases ?

--Humble


On Wed, Aug 5, 2015 at 5:12 PM, Raghavendra Bhat rab...@redhat.com wrote:


 Hi,

 In previous community meeting it was discussed to come up with a schedule
 for glusterfs releases. It was discussed that each of the supported release
 branches (3.5, 3.6 and 3.7) will make a new release every month.

 The previous releases of them happened at below dates.

 glusterfs-3.5.5 - 9th July
 glusterfs-3.6.4 - 13th July
 glusterfs-3.7.3 - 29th July.

 Is it ok to slightly align those dates? i.e. on 10th of every month 3.5
 based release would happen (in general the oldest supported and most stable
 release branch). On 20th of every month 3.6 based release would happen (In
 general, the release branch which is being stabilized). And on 30th of
 every month 3.7 based release would happen (in general, the latest release
 branch).

 Please provide feedback. Once a schedule is finalized we can put that
 information in gluster.org.

 Regards,
 Raghavendra Bhat

 ___
 Gluster-devel mailing list
 Gluster-devel@gluster.org
 http://www.gluster.org/mailman/listinfo/gluster-devel

___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] release schedule for glusterfs

[Humble Devassy Chirammal]

Indeed , no feedback on QA releases happens between minor versions.
I do think , there is no point to keep alpha/beta releases between minor
versions , but we can do that for Major as Kaleb mentioned.

--Humble


On Wed, Aug 5, 2015 at 6:32 PM, Kaleb S. KEITHLEY kkeit...@redhat.com
wrote:

 On 08/05/2015 08:45 AM, Raghavendra Bhat wrote:
  On 08/05/2015 05:57 PM, Humble Devassy Chirammal wrote:
  Hi Ragavendra,
 
  How many beta releases hit for each minor release ? and the gap
  between these releases ?
 
  --Humble
 
 
  I am not sure about the beta releases. As per my understanding there are
  no beta releases happening in release-3.5 branch and also the latest
  release-3.7 branch. I was doing beta releases for release-3.6 branch.
  But I am also thinking of moving away from it and make 3.6.5 directly
  (and also future release-3.6 releases).

 We get zero feedback from alphas and betas. Nobody has complained about
 the lack of them.

 IMO we should still to alpha and beta for x.y.0 releases though.

 --

 Kaleb
 ___
 Gluster-devel mailing list
 Gluster-devel@gluster.org
 http://www.gluster.org/mailman/listinfo/gluster-devel

___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] [Gluster-users] Gentle Reminder.. (Was: GlusterFS Documentation Improvements - An Update)

[Humble Devassy Chirammal]

This is still confising me a little. The presentations from the
Mediawiki instance have been put in the glusterdocs/presentations/
directory. If we should put them on the website instead, they should not
be part of glusterdocs. However, there is currently no page that I can
find on the website that lists the different presentations. The only
link that I can find is this one:

  http://gluster.readthedocs.org/en/latest/presentations/

Is that going to be replaced with an explanation (or pointer) on how to
get the presentation on the website?



Well, we are yet to finalize on it.  If we can render it on website we will
do the same. Otherwise it will be a pointer from website.


--Humble


On Fri, Jul 24, 2015 at 2:00 AM, Niels de Vos nde...@redhat.com wrote:

 On Wed, Jul 22, 2015 at 03:51:59PM +0530, Anjana Sriram wrote:
  Hello All,
 
  Thank you for the feedback and suggestions provided on the GlusterFS
  Documentation improvements. We have analyzed them and here's a proposal
 to
  address them:
 
  We plan to use three independent repos for our projects:
 
 ... snip
 
  /Static Documentation/: Currently, Mediawiki is read-only. We have ported
  most of the documents from Mediawiki. There few pages which do not
 qualify
  to be placed in the above three repos for example, Presentations  which
 will
  be considered to be placed on the website.

 This is still confising me a little. The presentations from the
 Mediawiki instance have been put in the glusterdocs/presentations/
 directory. If we should put them on the website instead, they should not
 be part of glusterdocs. However, there is currently no page that I can
 find on the website that lists the different presentations. The only
 link that I can find is this one:

   http://gluster.readthedocs.org/en/latest/presentations/

 Is that going to be replaced with an explanation (or pointer) on how to
 get the presentation on the website?

 Thanks,
 Niels


 
  Your thoughts and feedback are the major influences to our constant
 endeavor
  to make the community documentation better, effective, and useful. Please
  revert with your thoughts and feedback on the above proposal outlined by
  29th July 2015.
 
  Regards,
  Humble, Shravan, and Anjana
 
  On 06/22/2015 05:24 PM, Shravan Chandrashekar wrote:
  Hello all,
  
  We would like to finalize on the documentation contribution workflow by
 26th June 2015.
  As we have not yet received any comments/suggestion, we will confirm
 the recommend workflow after 26th June.
  
  
  Kindly provide your suggestion on how we can improve this workflow.
  
  Currently, mediawiki is read-only. We have ported most of the documents
 from mediawiki to the new repository [1].
  If you find any document which is not ported, feel free to raise this
 by opening an issue in [2] or if you would
  like to port your documents, send a pull request.
  
  
  
  [1] https://github.com/gluster/glusterdocs
  [2] https://github.com/gluster/glusterdocs/issues
  
  Regards,
  Shravan
  
  - Original Message -
  From: Humble Devassy Chirammal humble.deva...@gmail.com
  To: gluster-us...@gluster.org List gluster-us...@gluster.org,
 Gluster Devel gluster-devel@gluster.org
  Sent: Wednesday, May 27, 2015 7:48:16 PM
  Subject: [Gluster-devel] GlusterFS Documentation Improvements - An
 Update
  
  
  Hello all,
  
  The GlusterFS documentation team is constantly working to improve the
 quality, findability, and usefulness of its documentation. Our goal is to
 increase community contribution, remove barriers that discourage
 contribution and give you the help you need, when and where you need it. As
 part of this strategy, we’ve just rolled out the revamped GlusterFS
 Documentation: gluster.readthedocs.org
  
  We started by curating content from various sources including
 gluster.org static HTML documentation, various blog posts and the
 Community wiki. We used readthedocs service to host the documentation and
 mkdocs to convert the Markdown source files to HTML pages. We also put our
 thought into classifying the documentation based on their content:
  
  
  
   * Quick Start Guide : A headstart guide for the beginners.
  
  
   * Installation Guide : Step by step instructions to install
 GlusterFS.
  
  
   * Administration Guide : Container for for all administrative
 actions.
  
  
   * Developer Guide : Container for all development related aspects.
  
  
   * Upgrade Guide : Contains guides to upgrade from older versions
 of GlusterFS.
  
  
   * Features : Container for all the features of GlusterFS
 introduced in various versions.
  
  
   * GlusterFS Tools : Contains information about the tools used in
 GlusterFS.
  
  
   * Troubleshooting Guide : Container for basic troubleshooting and
 debugging guides.
  
  
   * Images : Container for images (in .jpg or .png format) that are
 present inline the documentation pages.
  
  Doing so, we gain these benefits:
  
  
  
   * Version based

Re: [Gluster-devel] [Gluster-users] Gluster Docker images are available at docker hub

[Humble Devassy Chirammal]

 Yeah this followed by glusterd restart should help

 But frankly, i was hoping that 'rm' the file isn't a neat way to fix this
 issue

Why is rm not a neat way? Is it because the container deployment tool
needs to
know about gluster internals? But isn't a Dockerfile dealing with details
of the service(s) that is being deployment in a container.


I do think fixing the dockerfile is *not* the correct way. That said, the
use case is not just
containers. This issue can pop up in Ovirt or virtualization environments
as well.
The VM template may have pre configured glusterd in it and the pool created
out of this template
can show the same behaviour.

I believe fixing it in gluster code base would be the right thing to do.


Thanks Atin for the heads up!

 AFAICT we have 2 scenarios:

 1) Non-container scenario, where the current behaviour of glusterd
persisting
 the info in .info file makes sense

 2) Container scenario, where the same image gets used as the base, hence
all
 containers gets the same UUID
 For this we can have an option to tell glusterd that instructs it to
refresh
 the UUID during next start.



--Humble


On Wed, Jul 1, 2015 at 11:32 AM, Krishnan Parthasarathi kpart...@redhat.com
 wrote:


  Yeah this followed by glusterd restart should help
 
  But frankly, i was hoping that 'rm' the file isn't a neat way to fix this
  issue

 Why is rm not a neat way? Is it because the container deployment tool
 needs to
 know about gluster internals? But isn't a Dockerfile dealing with details
 of the service(s) that is being deployment in a container.

  AFAICT we have 2 scenarios:
 
  1) Non-container scenario, where the current behaviour of glusterd
 persisting
  the info in .info file makes sense
 
  2) Container scenario, where the same image gets used as the base, hence
 all
  containers gets the same UUID
  For this we can have an option to tell glusterd that instructs it to
 refresh
  the UUID during next start.
 
  Maybe somethign like presence of a file /var/lib/glusterd/refresh_uuid
 makes
  glusterd refresh the UUID in .info
  and then delete this file, that ways, Dockerfile can touch this file,
 post
  gluster rpm install step and things should
  work as expected ?

 If container deployment needs are different it should should address
 issues like
 above. If we start addressing glusterd's configuration handling for every
 new deployment technology it would quickly become unmaintainable.
 ___
 Gluster-devel mailing list
 Gluster-devel@gluster.org
 http://www.gluster.org/mailman/listinfo/gluster-devel

___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] [Gluster-users] Looking for Fedora Package Maintainers.

[Humble Devassy Chirammal]

Thanks Vishwanath++, Ragavendra++  Saravana for volunteering!


--Humble


On Wed, Jun 24, 2015 at 6:53 PM, Saravanakumar Arumugam sarum...@redhat.com
 wrote:

 humble.deva...@gmail.com mailto:humble.deva...@gmail.com wrote:


 Hi All,

 As we maintain 3 releases ( currently 3.5, 3.6 and 3.7)  of
 GlusterFS and having an average of  one release per week , we need
 more helping hands on this task.

 The responsibility includes building fedora and epel rpms using koji
 build system and deploying  the rpms to download.gluster.org
 http://download.gluster.org [1] after signing and creating repos.

 If any one is interested to help us on maintaining fedora GlusterFS
 packaging, please let us ( kkeithley,  ndevos or myself ) know.


 I'm interested in helping/maintaining of gluster packaging.

 Best Regards,
 Vishwanath


 [1] http://download.gluster.org/pub/gluster/glusterfs/

 --Humble


 Add my name to list of volunteers.

 Raghavendra Talur


 Hi Humble,
 You can count me too for any help related.

 Thanks,
 Saravana


___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel

[Gluster-devel] Looking for Fedora Package Maintainers.

[Humble Devassy Chirammal]

Hi All,

As we maintain 3 releases ( currently 3.5, 3.6 and 3.7)  of GlusterFS and
having an average of  one release per week , we need more helping hands on
this task.

The responsibility includes building fedora and epel rpms using koji build
system and deploying  the rpms to download.gluster.org [1] after signing
and creating repos.

If any one is interested to help us on maintaining fedora GlusterFS
packaging, please let us ( kkeithley,  ndevos or myself )  know.

[1] http://download.gluster.org/pub/gluster/glusterfs/

--Humble
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] glusterfs-server installation fails in F21

[Humble Devassy Chirammal]

Hi Ramesh,

The new rpms ( 3.7.2-3) are available in download.gluster.org with the fix.
Please try the same .

--Humble


On Tue, Jun 23, 2015 at 5:37 PM, Ramesh rnach...@redhat.com wrote:

 Hi,

  glusterfs-server installation fails with the following error in F21.

 ##
 Installing : glusterfs-server-3.7.2-2.fc21.x86_64 1/1
 Error unpacking rpm package glusterfs-server-3.7.2-2.fc21.x86_64
 error: unpacking of archive failed on file
 /var/lib/glusterd/hooks/1/delete/post: cpio: mkdir
 ##

 Regards,
 Ramesh
 ___
 Gluster-devel mailing list
 Gluster-devel@gluster.org
 http://www.gluster.org/mailman/listinfo/gluster-devel

___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel

[Gluster-devel] GlusterFS Documentation Improvements - An Update

[Humble Devassy Chirammal]

Hello all,

The GlusterFS documentation team is constantly working to improve the
quality, findability, and usefulness of its documentation. Our goal is to
increase community contribution, remove barriers that discourage
contribution and give you the help you need, when and where you need it. As
part of this strategy, we’ve just rolled out the revamped GlusterFS
Documentation: gluster.readthedocs.org

We started by curating content from various sources including gluster.org
static HTML documentation, various blog posts and the Community wiki. We
used readthedocs service to host the documentation and mkdocs to convert
the Markdown source files to HTML pages. We also put our thought into
classifying the documentation based on their content:


   - Quick Start Guide : A headstart guide for the beginners.


   - Installation Guide : Step by step instructions to install GlusterFS.


   - Administration Guide : Container for for all administrative actions.


   - Developer Guide : Container for all development related aspects.


   - Upgrade Guide : Contains guides to upgrade from older versions of
   GlusterFS.


   - Features : Container for all the features of GlusterFS introduced in
   various versions.


   - GlusterFS Tools : Contains information about the tools used in
   GlusterFS.


   - Troubleshooting Guide : Container for basic troubleshooting and
   debugging guides.


   - Images : Container for images (in .jpg or .png format) that are
   present inline the documentation pages.


Doing so, we gain these benefits:


   - Version based browsable documentation


   - More targeted content


   - Less duplication


   - Faster updates


Whats changing for community members?

A very simplified contribution workflow.

- How to Contribute?

Contributing to the documentation requires a github account. To edit on
github, fork the repository (see top-right of the screen, under your
username). You will then be able to make changes easily. Once done, you can
create a pull request and get the changes reviewed and merged into the
official repository.
With this simplified workflow, the documentation is no longer maintained in
gluster/glusterfs/docs directory but it has a new elevated status in the
form of a new project: gluster/glusterdocs (
https://github.com/gluster/glusterdocs) and currently this project is being
maintained by Anjana Sriram, Shravan and Humble.

- What to Contribute

Really, anything that you think has value to the GlusterFS developer
community. While reading the docs you might find something incorrect or
outdated. Fix it! Or maybe you have an idea for a tutorial, or for a topic
that isn’t covered to your satisfaction. Create a new page and write it up!

Whats Next?

*Since the GlusterFS documentation has a new face-lift, MediaWiki will no
longer be editable but will only be READ ONLY view mode. Hence, all the
work-in-progress design notes which were maintained on MediaWiki will be
ported to the GitHub repository and placed in Feature Plans folder. So,
when you want to upload your work in progess documents you must do a pull
request after the changes are made. This outlines the change in workflow as
compared to MediaWiki.*

A proposal:

Another way to maintain work-in-progress documents in Google docs (or any
other colloborative editing tool) and link them as an index entry in
Feature Plans page on GitHub. This can be an excellent way to track a
document through multiple rounds of collaborative editing in real time.



Stay tuned for a more detailed information about the new contribution
workflow, which will be posted on the new documentation website (i.e.
gluster.readthedocs.org)

We love to hear your feedback on this. Any suggestions/comments regarding
this would help !

--Humble
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel

[Gluster-devel] Gluster Docker images are available at docker hub

[Humble Devassy Chirammal]

Hi All,


Docker images of GlusterFS 3.6 for Fedora ( 21) and CentOS  (7) are now
available at docker hub ( https://registry.hub.docker.com/u/gluster/ ).
These images can be used to deploy GlusterFS  containers.

The blog entry at planet.gluster.org [1] have details about how these
images can be used.

Please let me know if you have any comments/feedback/questions.

[1] Building GlusterFS in a docker container @ planet.gluster.org
[2] http://humblec.com/building-glusterfs-in-a-docker-container/

--Humble
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] GlusterFS 3.7.0beta1 released

[Humble Devassy Chirammal]

Hi All,


GlusterFS 3.7 beta1 RPMs for RHEL, CentOS, ( except el5) and Fedora are
available at download.gluster.org [1].

[1]http://download.gluster.org/pub/gluster/glusterfs/qa-releases/3.7.0beta1/

el5 rpms will be available soon.


--Humble


On Wed, Apr 29, 2015 at 4:39 PM, Vijay Bellur vbel...@redhat.com wrote:

 Hi All,

 Just pushed tag v3.7.0beta1 to glusterfs.git. A tarball of 3.7.0beta1 is
 now available at [1]. RPM and other packages will appear in
 download.gluster.org when the respective packages are ready.

 Important features available in beta1 include:

 - bitrot
 - tiering
 - inode quotas
 - sharding
 - glusterfind
 - multi-threaded epoll
 - trash
 - netgroups style authentication for nfs exports
 - snapshot scheduling
 - cli support for NFS Ganesha
 - Cloning volumes from snapshots

 I suspect that I might have missed a few from the list here. Please chime
 in with your favorite feature if I have missed including it here :).

 List of known bugs for 3.7.0 is being tracked at [2]. Testing feedback and
 patches would be very welcome!

 Thanks,
 Vijay

 [1]
 http://download.gluster.org/pub/gluster/glusterfs/qa-releases/3.7.0beta1/

 [2] https://bugzilla.redhat.com/show_bug.cgi?id=glusterfs-3.7.0



 ___
 Gluster-devel mailing list
 Gluster-devel@gluster.org
 http://www.gluster.org/mailman/listinfo/gluster-devel

___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] glusterfs package requires libgfdb.so

[Humble Devassy Chirammal]

Hi Satheesaran,

The libgfdb was moved to glusterfs-server package via
http://review.gluster.org/#/c/9983

As per commit,  libgfdb is only used by processes that run on Gluster
servers. There is
no need to have this library (and its sqlite dependency) on any system
that installs a glusterfs package.




--Humble


On Mon, Apr 6, 2015 at 12:32 PM, SATHEESARAN sasun...@redhat.com wrote:

 Hi All,

 I have encountered this issue with the latest nightly build of
 glusterfs-3.7

 Here is the problem with package dependency.
 To install glusterfs-fuse dependency goes like this:
 glusterfs-fuse -- glusterfs -- libgfdb.so

 To install glusterfs-api(libgfapi) the dependency goes like this:
 glusterfs-api -- glusterfs -- libgfdb.so

 So, I was unable to install client-only-packages (without glusterfs-server
 )
 When you install glusterfs-fuse or libgfapi, it requires libgfdb.so and
 installation is not possible.

 glusterfs-server is the package that provides - libgfdb.so
 You can't expect anyone to install glusterfs-server package on client-side.

 I have raised bug[1] for this issue
 Any thoughts ?

 [1] - https://bugzilla.redhat.com/show_bug.cgi?id=1208452

 -- Satheesaran

 ___
 Gluster-devel mailing list
 Gluster-devel@gluster.org
 http://www.gluster.org/mailman/listinfo/gluster-devel

___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel

[Gluster-devel] Fwd: [Gluster-users] Gluster Conference at NMAMIT, Nitte on April 11th 2015.

[Humble Devassy Chirammal]

Hi All,

We are conducting a Gluster Conference at NMAMIT, Nitte ( Mangalore) on
April 11th 2015.

We are expecting Engineering/MCA students and faculties from nearby
colleges to attend the conference.

The conference will mainly focus on Open Source Software Defined Storage
with GlusterFS as an example. The conference will have a
deep dive into GlusterFS followed by a workshop on GlusterFS Development.
The conference will be a great opportunity for the students
and the faculties to interact with Gluster community, and exchanges
ideas/thoughts.

Please find the tentative schedule,

Event Schedule:
~~~

-
Inauguration: 9.30 AM - 10.00 AM
-
-
Keynote Session : Introduction to Opensource
-
Speaker : Niels De Vos
Time: 10 AM - 10.45 AM
Duration: 45 mins
This session will give a introduction to Open Source. It will focus on
what's, why's and how's
Open Source, the advantages of Open Source and how important open Source
has become in
the current software era. The talk will give information on the different
tools used to
develop/collaborate/review/maintain/test open source software.

~~~
Tea/Coffee/Snacks Break 15 mins
~~~

-
Technical Talk  : Software Defined Storage : GlusterFS as an example
-
Speaker : Dan Lambright
Time: 11 AM - 11.45 AM
Duration: 45 mins
This talk would cover system storage as whole and different types of
storage 
storage protocols. It would emphasis on Software Defined Storage and how
disruptive it has
become, with its advantages and how open source software defined storage is
the most disruptive,
and hence the most desired. It would showcase of GluterFS as an example for
Open Source
Software Defined Storge


--
Lightening Talk : Quality of Service in Storage Systems
--
Speakers: Karthik U.S and Sukumar Poojary [1]
Time: 11.45 AM - 12.15 PM
Duration: 30 mins

--
Lightening Talk : Deduplicaiton in Storage Systems
--
Speakers: Ewen Pinto and Srinivas Billava [1]
Time: 12.15 PM - 12.45 PM
Duration: 30 mins


~
Lunch Break : 12.45 PM - 1.45 PM
~


-
Technical Talk  : Introduction to GlusterFS(Internals)
-
Speaker : Kaleb Keithley
Time: 2.00 PM - 3.00 PM
Duration: 1hr
GlusterFS is an open source, distributed file system capable of scaling to
several petabytes
and handling thousands of clients. GlusterFS clusters together storage
building blocks over Infiniband RDMA or TCP/IP interconnect, aggregating
disk and memory resources
and managing data in a single global namespace. GlusterFS is based on a
stackable user space design
and can deliver exceptional performance for diverse workloads.
This talk will provide an overview of GlusterFS and its features. We will
also talk about internal
of GlusterFS.
This will be a prequel session to GlusterFS Development Workshop that
follows.

~~~
Tea/Coffee/Snacks Break 15 mins
~~~

-
Technical Talk  : GlusterFS Development Workshop
-
Speaker : Joseph Elwin Fernandes  Niels De Vos
Time: 3.15 PM -5.45 PM
Duration: 2.30 hr
1) GlusterFS Development workflow.
2) Trying out GlusterFS, by adding a new xlator(GlusterFS Module)!
3) Setting up GlusterFS and testing the newly added xlator.
4) Submitting a patch and review process.


[1]

Lightening Talk Speaker:

1) Karthik U.S, Student of MCA (4th Sem), NMAMIT, Nitte, India.

2) Sukumar Poojary, Student of MCA (4th Sem), NMAMIT, Nitte, India.

3) Ewen Pinto, Student of MCA (6th Sem), NMAMIT, Nitte, India.

4) Srinivas Billava, Student of MCA (6th Sem), NMAMIT, Nitte, India.


Please let us know if anyone would like to contribute to the event w.r.t
sharing talks/workshop.

-- 
Cheers,
Humble
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] Updated best way to retrigger jobs in Jenkins

[Humble Devassy Chirammal]

Thanks Justin for the wiki page!

Yeah, most of us do a 'commit message' change too. :)

--Humble


On Thu, Mar 26, 2015 at 10:48 PM, Justin Clift jus...@gluster.org wrote:

 Hi us :),

 Just added a page to the wiki, showing how to retrigger a
 failed job in Jenkins:


 http://www.gluster.org/community/documentation/index.php/Retrigger_jobs_in_Jenkins

 Personally I used to use a different, less convenient method.
 This new way on the wiki seems to be much easier and as
 effective.

 Better suggestions welcome of course. :)

 Regards and best wishes,

 Justin Clift

 --
 GlusterFS - http://www.gluster.org

 An open source, distributed file system scaling to several
 petabytes, and handling thousands of clients.

 My personal twitter: twitter.com/realjustinclift

 ___
 Gluster-devel mailing list
 Gluster-devel@gluster.org
 http://www.gluster.org/mailman/listinfo/gluster-devel

___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] How can we prevent GlusterFS packaging installation/update issues in future?

[Humble Devassy Chirammal]

Hi Neils,


My guess is that we need to announce packaging changes very clearly.
Maybe it makes sense to have a very low-traffic packag...@gluster.org
mailinglist where all packagers from all distributions are subscribed?


+1 , its better to have a ML on packaging and discuss about the
changes/concerns/issues in this area.

--Humble


On Thu, Feb 19, 2015 at 2:30 PM, Niels de Vos nde...@redhat.com wrote:

 Hey Pranith!

 Thanks for putting this topic on my radar. Uncommunicated packaging
 changes have indeed been a pain for non-RPM distributions on several
 occasions. We should try to inform other packagers about required
 changes in the packaging scripts or upgrade/installation process better.

 On Thu, Feb 19, 2015 at 12:26:33PM +0530, Pranith Kumar Karampuri wrote:
  https://bugzilla.redhat.com/show_bug.cgi?id=1113778
  https://bugzilla.redhat.com/show_bug.cgi?id=1191176
 
  How can we make the process of giving good packages for things other than
  RPMs?

 My guess is that we need to announce packaging changes very clearly.
 Maybe it makes sense to have a very low-traffic packag...@gluster.org
 mailinglist where all packagers from all distributions are subscribed?

 I've added all packagers that I could track on CC, and am interested in
 their preferences and ideas.

 Thanks,
 Niels

___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] glusterfs-3.6.3beta1 released

[Humble Devassy Chirammal]

glusterfs-3.6.3beta1 has been released and can be found here.
http://download.gluster.org/pub/gluster/glusterfs/qa-releases/3.6.3beta1/
http://download.gluster.org/pub/gluster/glusterfs/qa-releases/3.6.2beta2/


The above url is getting redirected to 3.6.2 beta2 location.

Use below url in that situation :)

http://download.gluster.org/pub/gluster/glusterfs/qa-releases/3.6.3beta1/


--Humble


On Fri, Feb 13, 2015 at 3:57 PM, Raghavendra Bhat rab...@redhat.com wrote:

  Hi

 glusterfs-3.6.3beta1 has been released and can be found here.
 http://download.gluster.org/pub/gluster/glusterfs/qa-releases/3.6.3beta1/
 http://download.gluster.org/pub/gluster/glusterfs/qa-releases/3.6.2beta2/

 This beta release supposedly fixes the bugs listed below since 3.6.2 was
 made available. Thanks to all who submitted the patches, reviewed the
 changes.

 1138897 - NetBSD port
 1184527 - Some newly created folders have root ownership although created
 by unprivileged user
 1181977 - gluster vol clear
 1159471 - rename operation leads to core dump
 1173528 - Change in volume heal info command output
 1186119 - tar on a gluster directory gives message file changed as we
 read it even though no updates to file in progress
 1183716 - Force replace
 1178590 - Enable quota(default) leads to heal directory's xattr failed.
 1182490 - Internal ec xattrs are allowed to be modified
 1187547 - self-heal-algorithm with option full doesn't heal sparse
 files correctly
 1174170 - Glusterfs outputs a lot of warnings and errors when quota is
 enabled
 1186119 - tar on a gluster directory gives message file changed as we
 read it even though no updates to file in progress

 Regards,
 Raghavendra Bhat


 ___
 Gluster-devel mailing list
 Gluster-devel@gluster.org
 http://www.gluster.org/mailman/listinfo/gluster-devel


___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] Inclusion of /var/log/messages in log archive in regression.sh

[Humble Devassy Chirammal]

And I think that including
everything from /var/log/messages is too much.


only if regression fails we capture messages file, I dont think its a big
overhead.

 But, I also did not check
how big /var/log/messages is on a Jenkins slave

Capturing last/active messages file should be fine.

--Humble


On Thu, Dec 11, 2014 at 4:25 PM, Niels de Vos nde...@redhat.com wrote:

 On Thu, Dec 11, 2014 at 03:45:28PM +0530, Humble Devassy Chirammal wrote:
  
 
  I suggest to use 'logger -s' to add a marker that a regression test has
  been started in /var/log/messages, and only copy the contents from after
  the last marker into the archive
  
 
  I doubt we need a marker, because its 'not' always we need to look at
  'messages' file to see  whether its a  system specific issue.

 But how many lines should get gathered? And I think that including
 everything from /var/log/messages is too much. But, I also did not check
 how big /var/log/messages is on a Jenkins slave...

 Niels

 
  --Humble
 
 
  On Thu, Dec 11, 2014 at 3:38 PM, Niels de Vos nde...@redhat.com wrote:
 
   On Thu, Dec 11, 2014 at 11:05:21AM +0530, Humble Devassy Chirammal
 wrote:
Hi Atin,
   
Have a check at current version of regression.sh here:
   
   
  
 https://forge.gluster.org/gluster-patch-acceptance-tests/gluster-patch-acceptance-tests/blobs/master/regression.sh
   
It should be a small patch near to line 109.
  
   I suggest to use 'logger -s' to add a marker that a regression test has
   been started in /var/log/messages, and only copy the contents from
 after
   the last marker into the archive.
  
   Would that make sense?
  
   Thanks,
   Niels
  
   
--Humble
   
--Humble
   
   
On Thu, Dec 11, 2014 at 9:32 AM, Atin Mukherjee amukh...@redhat.com
 
   wrote:
   
 Hi Justin,

 The current regression.sh code doesn't capture /var/log/messages
 which
 means whether the system ran out of memory or not can not be
 justified
 looking at the the log archive. I strongly believe we should
 capture
 this message as part of archiving the log.

 Would you be able to do this change and apply it in Rackspace?

 ~Atin
 ___
 Gluster-devel mailing list
 Gluster-devel@gluster.org
 http://supercolony.gluster.org/mailman/listinfo/gluster-devel

  
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://supercolony.gluster.org/mailman/listinfo/gluster-devel
  
  

___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://supercolony.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] Gluster commands bash-completion

[Humble Devassy Chirammal]

May be a glusterfs-extra-utils rpm ?

--Humble


On Wed, Dec 10, 2014 at 4:14 PM, Lalatendu Mohanty lmoha...@redhat.com
wrote:

 On 12/10/2014 04:00 PM, Kaleb KEITHLEY wrote:

 On 12/10/2014 01:21 AM, Atin Mukherjee wrote:

 Folks,

 Although we have gluster commands bash-completion supported, its not
 enabled by default, we need to run an explicit make install under
 /extras/command-completion

 I am just wondering why can't we make it the bash completion default
 such that all our gluster commands become more user friendly and easy to
 use.


 I agree. We should install it by default.

 Perhaps it should be in a separate RPM package?

 I'd guess thought that the Debian and Ubuntu community would not want a
 separate package.

 --

 Kaleb


 Yup, I too agree that it should be installed by default. What about making
 it part of glusterfs RPM?

 -Lala

 ___
 Gluster-devel mailing list
 Gluster-devel@gluster.org
 http://supercolony.gluster.org/mailman/listinfo/gluster-devel

___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://supercolony.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] Inclusion of /var/log/messages in log archive in regression.sh

[Humble Devassy Chirammal]

Hi Atin,

Have a check at current version of regression.sh here:

https://forge.gluster.org/gluster-patch-acceptance-tests/gluster-patch-acceptance-tests/blobs/master/regression.sh

It should be a small patch near to line 109.

--Humble

--Humble


On Thu, Dec 11, 2014 at 9:32 AM, Atin Mukherjee amukh...@redhat.com wrote:

 Hi Justin,

 The current regression.sh code doesn't capture /var/log/messages which
 means whether the system ran out of memory or not can not be justified
 looking at the the log archive. I strongly believe we should capture
 this message as part of archiving the log.

 Would you be able to do this change and apply it in Rackspace?

 ~Atin
 ___
 Gluster-devel mailing list
 Gluster-devel@gluster.org
 http://supercolony.gluster.org/mailman/listinfo/gluster-devel

___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://supercolony.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] With what code/tree should the regression tests be run?

[Humble Devassy Chirammal]

I do believe (a) looks to be the correct way to go.

--Humble



--Humble


On Sat, Nov 15, 2014 at 4:52 PM, Niels de Vos nde...@redhat.com wrote:

 On Sat, Nov 15, 2014 at 11:46:46AM +0530, RAGHAVENDRA TALUR wrote:
  I could not reply to this thread yesterday.
  Earlier, test system used to take care of the rebase.
  However, it worked here only after I did a manual
  rebase on my machine and updated gerrit.

 Indeed, and I have noticed that too. I remember being able to just
 resubmit the failed regression tests, and the change would be rebased on
 top of HEAD of the branch. To me, that also looks a safer way of going
 things, (relatively) old patches can be tested easier that way.

 I suspect that this change came with the triggered regression testing,
 but I have not checked that. Do others have an opionion on with what
 code the regression tests should be executed? Currently I am aware of
 two possible ways:

 a. checkout the HEAD of the branch and cherry-pick the change on top
 b. checkout the change (use the tree from the time the change was
posted)

 (b) seems to be the current way, my preference would go to (a).

 Please voice your opinions. Thanks,
 Niels
 ___
 Gluster-devel mailing list
 Gluster-devel@gluster.org
 http://supercolony.gluster.org/mailman/listinfo/gluster-devel

___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://supercolony.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] Glusterfs backlogs

[Humble Devassy Chirammal]

Hi Atin,

FMPOV, 2 weeks time looks to be good, at the same time, please give
importance for the product version it is reported. If they are into our
running stable or near versions, we can be some more flexible.

--Humble

--Humble


On Thu, Nov 13, 2014 at 4:31 PM, Atin Mukherjee amukh...@redhat.com wrote:

 Folks,

 While I was looking into glusterd backlogs I could see there are few BZs
 which were marked as needinfo on the reporter as the information was
 not sufficient enough for further analysis and the reporter hasn't
 gotten back with the required details.

 Ideally we should close these bugs saying inadequate information,
 however I am just wondering should we set a timeline for the waiting
 period like 1 or 2 weeks if not more and then close all such instances
 to reduce the count.

 What do you guys think?

 ~Atin
 ___
 Gluster-devel mailing list
 Gluster-devel@gluster.org
 http://supercolony.gluster.org/mailman/listinfo/gluster-devel

___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://supercolony.gluster.org/mailman/listinfo/gluster-devel

[Gluster-devel] [commercial ] Openings in Red Hat.

[Humble Devassy Chirammal]

Hi All,

The Red Hat Storage Engineering team is seeking someone with extensive
systems programming experience to join us as a Principal/Senior/Software
Engineer. In this role, you will work as part of a team responsible for
developing GlusterFS. You'll conduct system analysis, development and
review and repair legacy code, as well as provide assistance to testers
by developing unit test framework and support personnel to determine
system problems. We'll need you to have a solid technical background,
preferably in client or server architecture and algorithm development,
as well as good interpersonal skills. We love the open source community,
so if you're already contributing to any open source projects, please
upload your code samples or links along with your resume. We also
encourage you to join our storage product community.

Red Hat Storage is a scale-out NAS storage solution. The work profile
would involve developing and maintaining components of a distributed
file system called GlusterFS.
The job profile requires extensive knowledge of C, Linux System
programming, Networking, Algorithms, Analytics and Data Structures.

If you are interested, please reach out to me @ hchir...@redhat.com

--Humble
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://supercolony.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] Please vote for Dockit for #dockerhackday on Twitter

[Humble Devassy Chirammal]

Thanks Justin for the support!!

If  some one is not seeing  buttons for FB like/g+1/tweet on hackathon page
, please disable pop up blockers or open in a different browser :)

--Humble


On Wed, Nov 5, 2014 at 1:44 AM, Justin Clift jus...@gluster.org wrote:

 Hi all,

 Our very own Humble Chirammal's Dockit project is an entry in the 2nd
 Docker Global Hack Day.  Please vote for it on Twitter:

   My #dockerhackday vote is for dockit by Humble Chirammal and
@hiSaifi. @docker

 :)

 Regards and best wishes,

 Justin Clift

 --
 GlusterFS - http://www.gluster.org

 An open source, distributed file system scaling to several
 petabytes, and handling thousands of clients.

 My personal twitter: twitter.com/realjustinclift
 ___
 Gluster-devel mailing list
 Gluster-devel@gluster.org
 http://supercolony.gluster.org/mailman/listinfo/gluster-devel

___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://supercolony.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] build failures in regressions

[Humble Devassy Chirammal]

I am Just cross-checking whether this patch
http://review.gluster.org/#/c/9016/ has any impact here .

--Humble


On Tue, Nov 4, 2014 at 3:51 PM, Justin Clift jus...@gluster.org wrote:

 On Tue, 04 Nov 2014 12:57:52 +0530
 Pranith Kumar Karampuri pkara...@redhat.com wrote:
  hi,
  Does anyone know why the following errors are happening on regression:
  You can check
  http://build.gluster.org/job/rackspace-regression-2GB/735/consoleFull
  for full log.
 
 
 /home/jenkins/root/workspace/rackspace-regression-2GB/rpc/xdr/src/msg-nfs3.h:20:22:
  error: nlm4-xdr.h: No such file or
  directory
 /home/jenkins/root/workspace/rackspace-regression-2GB/rpc/xdr/src/msg-nfs3.h:21:22:
  error: acl3-xdr.h: No such file or directory In file included
  from
 /home/jenkins/root/workspace/rackspace-regression-2GB/rpc/xdr/src/msg-nfs3.c:22:
 /home/jenkins/root/workspace/rackspace-regression-2GB/rpc/xdr/src/msg-nfs3.h:180:
  error: expected declaration specifiers or ‘...’ before
  ‘nlm4_testargs’
 /home/jenkins/root/workspace/rackspace-regression-2GB/rpc/xdr/src/msg-nfs3.h:183:
  error: expected declaration specifiers or ‘...’ before ‘nlm4_testres’

 Unsure.  Perhaps a missing dependency on the slave VM?  Just tested
 this out on a different slave VM, and that had the same problem.
 (at least it's consistent)

 Looking at this failure on the NetBSD 6.x Rackspace VM, it fails in
 the same area of code (rpc/xdr/src/).  No idea if it's related, as
 it's for a different patch set... but it's an unusual co-incidence
 if not. ;)

   http://build.gluster.org/job/netbsd6-smoke/1288/console

 + Justin

 --
 GlusterFS - http://www.gluster.org

 An open source, distributed file system scaling to several
 petabytes, and handling thousands of clients.

 My personal twitter: twitter.com/realjustinclift
 ___
 Gluster-devel mailing list
 Gluster-devel@gluster.org
 http://supercolony.gluster.org/mailman/listinfo/gluster-devel

___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://supercolony.gluster.org/mailman/listinfo/gluster-devel

[Gluster-devel] Req# Vote for Dockit @ Docker Global Hackathon

[Humble Devassy Chirammal]

The  Docker GlusterFS integration project, dockit is part of Docker
Global Hackathon and this is the time to cast your vote against DOCKIT .

You can cast your vote by Facebook like, Tweet or g+1  after searching
dockit project @

https://www.docker.com/community/globalhackday



--Humble
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://supercolony.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] [Gluster-users] Dependency issue while installing glusterfs-3.6beta with vdsm

[Humble Devassy Chirammal]

Rebuilding related packages looks to be a solution , however it may not be
possible for each and every release builds of GlusterFS. lets discuss it in
community meeting and act.

--Humble
http://humblec.com

On Wed, Oct 29, 2014 at 1:03 AM, Niels de Vos nde...@redhat.com wrote:

 On Tue, Oct 28, 2014 at 05:52:38PM +0100, Anders Blomdell wrote:
  On 2014-10-28 17:30, Niels de Vos wrote:
   On Tue, Oct 28, 2014 at 08:42:00AM -0400, Kaleb S. KEITHLEY wrote:
   On 10/28/2014 07:48 AM, Darshan Narayana Murthy wrote:
   Hi,
   Installation of glusterfs-3.6beta with vdsm
 (vdsm-4.14.8.1-0.fc19.x86_64) fails on
   f19  f20 because of dependency issues with qemu packages.
  
   I installed vdsm-4.14.8.1-0.fc19.x86_64 which installs
 glusterfs-3.5.2-1.fc19.x86_64
   as dependency. Now when I try to update glusterfs by downloading
 rpms from :
  
 http://download.gluster.org/pub/gluster/glusterfs/qa-releases/3.6.0beta3/Fedora/fedora-19/
   It fails with following error:
  
   Error: Package: 2:qemu-system-lm32-1.4.2-15.fc19.x86_64 (@updates)
  Requires: libgfapi.so.0()(64bit)
  Removing: glusterfs-api-3.5.2-1.fc19.x86_64 (@updates)
  libgfapi.so.0()(64bit)
  Updated By: glusterfs-api-3.6.0-0.5.beta3.fc19.x86_64
 (/glusterfs-api-3.6.0-0.5.beta3.fc19.x86_64)
 ~libgfapi.so.7()(64bit)
  Available: glusterfs-api-3.4.0-0.5.beta2.fc19.x86_64
 (fedora)
  libgfapi.so.0()(64bit)
  
   Full output at: http://ur1.ca/ikvk8
  
   For having snapshot and geo-rep management through ovirt, we
 need glusterfs-3.6 to be
   installed with vdsm, which is currently failing.
  
   Can you please provide your suggestions to resolve this issue.
  
   Hi,
  
   Starting in 3.6 we have bumped the SO_VERSION of libgfapi.
  
   You need to install glusterfs-api-devel-3.6.0... first and build vdsm.
  
   But  we are (or were) not planning to release glusterfs-3.6.0 on
 f19 and
   f20...
  
   Off hand I don't believe there's anything in glusterfs-api-3.6.0 that
 vdsm
   needs. vdsm with glusterfs-3.5.x on f19 and f20 should be okay.
  
   Is there something new in vdsm-4-14 that really needs glusterfs-3.6?
 If so
   we can revisit whether we release 3.6 to fedora 19 and 20.
  
   The chain of dependencies is like this:
  
  vdsm - qemu - libgfapi.so.0
  
   I think a rebuild of QEMU should be sufficient. I'm planning to put
   glusterfs-3.6 and rebuilds of related packages in a Fedora COPR. This
   would make it possible for Fedora users to move to 3.6 before they
   switch to Fedora 22.
  AFAICT the only difference between libgfapi.so.0 and libgfapi.so.7 are
  two added synbols (glfs_get_volfile, glfs_h_access) and __THROW on
  functions. Wouldn't it be possible to provide a compatibilty
 libgfapi.so.0
  to ease migration?

 That is possible, sure. I think that rebuilding related packages is just
 easier, there are only a few needed. Users that would like to run 3.6
 before it is made available with Fedora 22 need to add a repository for
 the glusterfs-3.6 packages anyway, using the same repository to provide
 related packages is simple enough.

 But, if there is a strong interest in having a -compat package, we can
 discuss that during tomorrows (Wednesdays) meeting.

 Thanks,
 Niels
 ___
 Gluster-devel mailing list
 Gluster-devel@gluster.org
 http://supercolony.gluster.org/mailman/listinfo/gluster-devel

___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://supercolony.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] warning: bogus date in %changelog

[Humble Devassy Chirammal]

It is something we should fix. If there is an update of the .spec
needed, a correction like this can get included. Otherwise just follow
the normal process for a bugfix (file a bug, post a patch).


Yep, this is fixed in master (http://review.gluster.org/#/c/8116/) .
We have to include it in 3.6 branch. May be with logrotate spec file patch?

--Humble

--Humble
http://humblec.com

On Wed, Oct 29, 2014 at 1:22 AM, Niels de Vos nde...@redhat.com wrote:

 On Wed, Oct 29, 2014 at 01:01:28AM +0530, Lalatendu Mohanty wrote:
  On 10/28/2014 11:32 PM, Anders Blomdell wrote:
  Does the following warning:
 warning: bogus date in %changelog: Thu Jun 29 2014 Humble Chirammal 
 hchir...@redhat.com
  warrant a bug report/fix as below (based on date of commit 8d8abc19)?
 Or should I just leave it as is?
  
  
  diff --git a/glusterfs.spec.in b/glusterfs.spec.in
  index f373b45..5ad4956 100644
  --- a/glusterfs.spec.in
  +++ b/glusterfs.spec.in
  @@ -1042,7 +1042,7 @@ fi
* Wed Sep 24 2014 Balamurugan Arumugam barum...@redhat.com
- remove /sbin/ldconfig as interpreter (#1145992)
  -* Thu Jun 29 2014 Humble Chirammal hchir...@redhat.com
  +* Thu Jun 19 2014 Humble Chirammal hchir...@redhat.com
- Added dynamic loading of fuse module with glusterfs-fuse package
 installation in el5.
* Fri Jun 27 2014 Kaleb S. KEITHLEY kkeit...@redhat.com
  
  
  /Anders
  I checked master branch and I can see the date and day is correct in
  glusterfs.spec.in as below. Where do you see wrong change log i.e. Thu
 Jun
  29 2014 Humble Chirammal hchir...@redhat.com?
 
  * Thu Jun 19 2014 Humble Chirammal hchir...@redhat.com
  - Added dynamic loading of fuse module with glusterfs-fuse package
  installation in el5.

 That seems to come from commit 8d8abc19 in release-3.6:

 commit 8d8abc19b0500b725f92164c096b64b3c37cd6b0
 Author: Humble Chirammal hchir...@redhat.com
 Date:   Thu Jun 19 16:51:57 2014 +0530

 Autoload fuse module in centos5/el5 versions.

 This patch dynamically load 'fuse' module with the installation
 of glusterfs-fuse package in centos/el5 distributions.

 Change-Id: I4988a025bd18716fd6d355431196540e140224b3
 BUG: 1108669
 Signed-off-by: Humble Chirammal hchir...@redhat.com
 Reviewed-on: http://review.gluster.org/8116
 Reviewed-by: Niels de Vos nde...@redhat.com
 Reviewed-by: Lalatendu Mohanty lmoha...@redhat.com
 Tested-by: Gluster Build System jenk...@build.gluster.com


 It is something we should fix. If there is an update of the .spec
 needed, a correction like this can get included. Otherwise just follow
 the normal process for a bugfix (file a bug, post a patch).

 Thanks,
 Niels
 ___
 Gluster-devel mailing list
 Gluster-devel@gluster.org
 http://supercolony.gluster.org/mailman/listinfo/gluster-devel

___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://supercolony.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] [Gluster-users] GlusterFest Test Week

[Humble Devassy Chirammal]

Hi Justin,

We are working on releasing RPMs for 3.6.0beta1  release, but it will take
some time. We will notify the list once the rpms are available.

--Humble

On Mon, Sep 22, 2014 at 3:27 PM, Justin Clift jus...@gluster.org wrote:

 On 21/09/2014, at 7:47 PM, Vijay Bellur wrote:
  On 09/18/2014 05:42 PM, Humble Devassy Chirammal wrote:
  Greetings,
 
  As decided in our last GlusterFS meeting and the 3.6 planning schedule,
  we shall conduct GlusterFS 3.6 test days  starting from next week.
  This time we intend testing one component and functionality per day.
 
  GlusterFS 3.6.0beta1 is now available to kick start the test week [1].
 As we find issues and more patches do get merged in over the test week, I
 will be triggering further beta releases.


 We're going to need RPMs... and probably .deb's too.

 + Justin

 --
 GlusterFS - http://www.gluster.org

 An open source, distributed file system scaling to several
 petabytes, and handling thousands of clients.

 My personal twitter: twitter.com/realjustinclift


___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://supercolony.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] Who's who ?

[Humble Devassy Chirammal]

Good thinking. :)

Thanks :)

 For new columns which may be useful, these ones spring to mind:

 * Twitter username - many people have them these days
 * A free form text description - eg I'm Justin, I'm into databases,
storage, and developing embedded human augmentation systems. ;)
 * Some kind of thumbnail photo - probably as the first column on the left

Maybe also a LinkedIn column (?), though I hesitate to encourage LinkedIn
these days... ;)

Please go ahead. :)  , I do second whatever helps in one way or the other.
I see people are already added blog/url column  in the same page.

--Humble

On Fri, Sep 12, 2014 at 12:48 PM, Justin Clift jus...@gluster.org wrote:

 On 12/09/2014, at 7:13 AM, Humble Devassy Chirammal wrote:
 snip
  Some of you may have noticed our new Who is Who (
 http://www.gluster.org/community/documentation/index.php/Who_is_Who)
 page  in gluster.org. The idea here is to gather information about our
 gluster community members, so that that it would be easy for all to reach
 out to one another.  We are assembling the information we need for a good
 'Who's Who' page. Please add details about yourself. You may also add any
 new columns which you think may be useful (such as a column for social
 networking profile, blog).

 Good thinking. :)

 For new columns which may be useful, these ones spring to mind:

  * Twitter username - many people have them these days
  * A free form text description - eg I'm Justin, I'm into databases,
 storage, and developing embedded human augmentation systems. ;)
  * Some kind of thumbnail photo - probably as the first column on the left

 Maybe also a LinkedIn column (?), though I hesitate to encourage LinkedIn
 these days... ;)

 + Justin

 --
 GlusterFS - http://www.gluster.org

 An open source, distributed file system scaling to several
 petabytes, and handling thousands of clients.

 My personal twitter: twitter.com/realjustinclift


___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://supercolony.gluster.org/mailman/listinfo/gluster-devel

[Gluster-devel] GlusterFS 3.6 Test Day Preparations

[Humble Devassy Chirammal]

Hi All,

As part of GlusterFs 3.6 release, we are planning to hold GlusterFs 3.6
TEST days starting from next week. All the listed  3.6 feature's (
http://www.gluster.org/community/documentation/index.php/Planning36) page
have to be updated to have a clear picture on what exactly the feature
provides, user experience..etc. The most important part is updating the
HOW TO TEST section in each feature page. Feature page and HOW TO TEST
section will be used heavily for testing the feature, so the component
owners are requested to spend some time and update this page, so that the
test days will be more productive.

--Humble
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://supercolony.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] patches missing in git even after gerrit says they are merged

[Humble Devassy Chirammal]

Below patches  were in status of 'submitted , merge  pending' when gerrit
went wrong yesterday.

http://review.gluster.org/#/c/8459/
http://review.gluster.org/#/c/8466/
http://review.gluster.org/#/c/8507/

Possibly we have to merge those in repo again.

--Humble


On Fri, Aug 22, 2014 at 10:12 AM, Sachin Pandit span...@redhat.com wrote:

 Hi,

 In gerrit, the status of http://review.gluster.org/#/c/8507/ is merged.
 But I dont see the changes in git as Pranith mentioned.

 ~ Sachin.

 - Original Message -
 From: Pranith Kumar Karampuri pkara...@redhat.com
 To: Vijay Bellur vbel...@redhat.com
 Cc: Gluster Devel gluster-devel@gluster.org
 Sent: Thursday, August 21, 2014 10:05:42 PM
 Subject: [Gluster-devel] patches missing in git even after gerrit says
 they are merged

 hi Vijay,
 http://review.gluster.org/#/c/8466/ is one such candidate. CCed
 gluster-devel so that others can also verify that their patches are in.

 Pranith
 ___
 Gluster-devel mailing list
 Gluster-devel@gluster.org
 http://supercolony.gluster.org/mailman/listinfo/gluster-devel
 ___
 Gluster-devel mailing list
 Gluster-devel@gluster.org
 http://supercolony.gluster.org/mailman/listinfo/gluster-devel

___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://supercolony.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] update-link-count-parent POSIX xlator parameter

[Humble Devassy Chirammal]

Hi Prasanth,

Its worth to have in our GlusterFS source doc . Can you send a patch on
this ?

--Humble


On Thu, Aug 21, 2014 at 10:34 AM, Prashanth Pai p...@redhat.com wrote:

 Hi,

 I recently came across this when I was looking for various ways to convert
 GFID to Path[1].
 I have tested build-pgfid option for basic sanity. It's documented in
 the commit msg of change[2]. Found one small issue[3]. There could be
 others.
 Users should be aware that these xattrs generated only for newly created
 dirs/files and are not built for already existing dirs/files.

 [1]:
 https://github.com/prashanthpai/sof-object-listing/blob/master/changelog/gfid-to-path.md
 [2]: http://review.gluster.org/5951
 [3]: http://review.gluster.org/8352

 Regards,
  -Prashanth Pai

 - Original Message -
 From: Harshavardhana har...@harshavardhana.net
 To: Ben England bengl...@redhat.com
 Cc: gluster-devel gluster-devel@gluster.org
 Sent: Thursday, August 21, 2014 2:57:25 AM
 Subject: Re: [Gluster-devel] update-link-count-parent POSIX xlator
 parameter

 On Wed, Aug 20, 2014 at 1:55 PM, Ben England bengl...@redhat.com wrote:
  What is update-link-count-parent POSIX xlator parameter for?  Is it ever
 set by anyone and why?  It appears to be off by default.  Didn't see this
 documented, but the log message in posix.c says:  update-link-count-parent
 is enabled. Thus for each file an extended attribute representing the
 number of hardlinks for that file within the same parent directory is
 set.  Why would this be necessary?
 

 It was supposed to be used by Quota or it uses it internally i am not
 sure for ancestry paths and gfid to path conversion - AFAIK

 # gluster volume set volname build-pgfid on

 Enables this feature. Never tested it personally.

 --
 Religious confuse piety with mere ritual, the virtuous confuse
 regulation with outcomes
 ___
 Gluster-devel mailing list
 Gluster-devel@gluster.org
 http://supercolony.gluster.org/mailman/listinfo/gluster-devel
 ___
 Gluster-devel mailing list
 Gluster-devel@gluster.org
 http://supercolony.gluster.org/mailman/listinfo/gluster-devel

___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://supercolony.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] [Gluster-users] glusterfs-3.4.5 RPMs now available

[Humble Devassy Chirammal]

Hi Chad,

The issue appears to be fixed.

I enabled el6 repo from download.gluster.org in my rhel6 system  and its
working.

Can you please try again ?

--Humble





On Fri, Jul 25, 2014 at 4:06 AM, Chad Feller fel...@unr.edu wrote:

 On Fri, Jul 25, 2014 at 02:18:01AM +0530, Lalatendu Mohanty wrote:
  On 07/23/2014 10:48 PM, Kaleb KEITHLEY wrote:
  On 07/23/2014 01:08 PM, Gluster Build System wrote:
  
  
  SRC:
  
 http://bits.gluster.org/pub/gluster/glusterfs/src/glusterfs-3.4.5.tar.gz
  
  This release is made off jenkins-release-85
  
  Release Notes for 3.4.5 GA
  
  GlusterFS 3.4.5 consists entirely of bug fixes.
  
  The following changes are included in 3.4.5:
  
  * 2b78933 cluster/dht: Don't do extra unref in dht-migration checks
  
  * 33b6134 doc: Fix peer probe deficiencies
  
  * ecc2194 fuse: fix memory leak in fuse_getxattr()
  
  * b3bf2cf performance/quick-read: Check for iobuf and iobref before
 unref.
  
  * e311014 nfs: prevent assertion error with MOUNT over UDP
  
 
  RPMs for el5-7 (RHEL, CentOS, etc.), Fedora (19,20,21,22) are available
 at
  download.gluster.org [1].
 
  [1] http://download.gluster.org/pub/gluster/glusterfs/3.4/LATEST/
 
  Thanks,
  Lala

 Hi,

 There seems to be a small problem insomuch as I'm seeing this on all my
 RHEL6 boxes when attempting to yum update:

 ...
 (6/23): glusterfs-3.4.5-1.el6.x86_64.rpm   | 984 kB
 00:00

 http://download.gluster.org/pub/gluster/glusterfs/3.4/LATEST/EPEL.repo/epel-6Server/x86_64/glusterfs-3.4.5-1.el6.x86_64.rpm
 :
 [Errno -1] Package does not match intended download. Suggestion: run yum
 --enablerepo=glusterfs-epel clean metadata
 Trying other mirror.
 (7/23): glusterfs-cli-3.4.5-1.el6.x86_64.rpm   | 106 kB
 00:00

 http://download.gluster.org/pub/gluster/glusterfs/3.4/LATEST/EPEL.repo/epel-6Server/x86_64/glusterfs-cli-3.4.5-1.el6.x86_64.rpm
 :
 [Errno -1] Package does not match intended download. Suggestion: run yum
 --enablerepo=glusterfs-epel clean metadata
 Trying other mirror.
 (8/23): glusterfs-fuse-3.4.5-1.el6.x86_64.rpm  |  89 kB
 00:00

 http://download.gluster.org/pub/gluster/glusterfs/3.4/LATEST/EPEL.repo/epel-6Server/x86_64/glusterfs-fuse-3.4.5-1.el6.x86_64.rpm
 :
 [Errno -1] Package does not match intended download. Suggestion: run yum
 --enablerepo=glusterfs-epel clean metadata
 Trying other mirror.
 (9/23): glusterfs-libs-3.4.5-1.el6.x86_64.rpm  | 222 kB
 00:00

 http://download.gluster.org/pub/gluster/glusterfs/3.4/LATEST/EPEL.repo/epel-6Server/x86_64/glusterfs-libs-3.4.5-1.el6.x86_64.rpm
 :
 [Errno -1] Package does not match intended download. Suggestion: run yum
 --enablerepo=glusterfs-epel clean metadata
 Trying other mirror.
 (10/23): glusterfs-server-3.4.5-1.el6.x86_64.rpm   | 492 kB
 00:00

 http://download.gluster.org/pub/gluster/glusterfs/3.4/LATEST/EPEL.repo/epel-6Server/x86_64/glusterfs-server-3.4.5-1.el6.x86_64.rpm
 :
 [Errno -1] Package does not match intended download. Suggestion: run yum
 --enablerepo=glusterfs-epel clean metadata
 Trying other mirror.
 ...

 Across all my GlusterFS servers. I'm assuming this is a repo-side
 problem on download.gluster.org?  (And yes I tried both yum clean
 metadata and yum clean all.)

 Thanks,

 -Chad
 ___
 Gluster-users mailing list
 gluster-us...@gluster.org
 http://supercolony.gluster.org/mailman/listinfo/gluster-users

___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://supercolony.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] [Gluster-users] glusterfs-3.4.5 RPMs now available

[Humble Devassy Chirammal]

Hi Chad/Lala,

This error mostly pop up  when the metadata of actual file does not match
the one provided by the repo metdata files. so I believe createrepo fixed
it.

--Humble



On Fri, Jul 25, 2014 at 8:40 PM, Lalatendu Mohanty lmoha...@redhat.com
wrote:

 On 07/25/2014 07:50 PM, Chad Feller wrote:

 On Fri, Jul 25, 2014 at 01:27:20PM +0530, Humble Devassy Chirammal wrote:

 Hi Chad,
 The issue appears to be fixed.
 I enabled el6 repo from [1]download.gluster.org in my rhel6 system
  and
 its working.
 Can you please try again ?
 --Humble

 Hi Humble,

 I noticed that it is working as of this morning on my Fedora 20 and
 RHEL6 boxes.

  Thanks Humble, Chad.

 Yup, I think there was some issue with repo metadata. I had recreated the
 repo , after you reported the issue and that fixed it.

 Thanks,
 Lala

___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://supercolony.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] Static analysis, cpp-check, clang-analyze, coverity, etc., of community glusterfs source

[Humble Devassy Chirammal]

Hi Kaleb,

Nice initiative !! Thanks for this  single window system.

--Humble


On Thu, Jul 24, 2014 at 6:27 PM, Kaleb S. KEITHLEY kkeit...@redhat.com
wrote:


 We now have daily runs of various static source code analysis tools on the
 glusterfs sources. There are daily analyses of the master, release-3.6, and
 release-3.5 branches.

 Results are posted at http://download.gluster.org/
 pub/gluster/glusterfs/static-analysis/

 If you're interested in contributing to Gluster, but don't know where to
 start, look here for some easy (and hard) bugs to fix.

 To fix a bug, start by opening a BZ at https://bugzilla.redhat.com/
 enter_bug.cgi?product=GlusterFS

 Submit the fix in gerrit, instructions are at http://www.gluster.org/
 community/documentation/index.php/Development_Work_Flow

 --

 Kaleb
 ___
 Gluster-devel mailing list
 Gluster-devel@gluster.org
 http://supercolony.gluster.org/mailman/listinfo/gluster-devel

___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://supercolony.gluster.org/mailman/listinfo/gluster-devel

[Gluster-devel] libgfapi + qemu compatibility job

[Humble Devassy Chirammal]

Hi All,

The libgfapi qemu compatibility check  is active on review.gluster.org  via
GlusterBuildSystem2 ,(rhs-client34.lab.eng.blr.redhat.com . The review
votes are skipped for 'success'  and -1 has set for failure.

Please let us know if you have any questions.

--Humble
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://supercolony.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] Is gerrit/jenkins integration sick?

[Humble Devassy Chirammal]

Hi Anders,

Looks to be an issue generated when GlusterBuildSystem2 tries to connect
review.gluster.org , I am trying to sort this out.

--Humble


On Tue, Jul 15, 2014 at 4:14 PM, Anders Blomdell 
anders.blomd...@control.lth.se wrote:

 I'm getting

 http://review.gluster.org/#/c/8291/:

   Patch Set 5:

   Build Successful

   http://rhs-client34.lab.eng.blr.redhat.com:8080/job/libgfapi-qemu/322/
 : SUCCESS (skipped)

 http://review.gluster.org/#/c/8299/:

   Patch Set 6: Verified-1

   Build Failed

   http://rhs-client34.lab.eng.blr.redhat.com:8080/job/libgfapi-qemu/323/
 : FAILURE


 How do I debug these?

 /Anders

 --
 Anders Blomdell  Email: anders.blomd...@control.lth.se
 Department of Automatic Control
 Lund University  Phone:+46 46 222 4625
 P.O. Box 118 Fax:  +46 46 138118
 SE-221 00 Lund, Sweden

 ___
 Gluster-devel mailing list
 Gluster-devel@gluster.org
 http://supercolony.gluster.org/mailman/listinfo/gluster-devel

___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://supercolony.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] libgfapi + qemu compatibility job

[Humble Devassy Chirammal]

Yes, its not possible to monitor from outside RH network. We are planning
to move this to one of the public servers. Till then please report the
issues , if any . I will take care of it..

--Humble


On Tue, Jul 15, 2014 at 4:11 PM, Kaushal M kshlms...@gmail.com wrote:

 That machine is not accessible from the outside the Red Hat internal
 network. How would users who are not on the internal network be able
 to look at the jobs?

 ~kaushal

 On Tue, Jul 15, 2014 at 3:54 PM, Humble Devassy Chirammal
 humble.deva...@gmail.com wrote:
  Hi All,
 
  The libgfapi qemu compatibility check  is active on review.gluster.org
  via
  GlusterBuildSystem2 ,(rhs-client34.lab.eng.blr.redhat.com . The review
 votes
  are skipped for 'success'  and -1 has set for failure.
 
  Please let us know if you have any questions.
 
  --Humble
 
  ___
  Gluster-devel mailing list
  Gluster-devel@gluster.org
  http://supercolony.gluster.org/mailman/listinfo/gluster-devel
 

___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://supercolony.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] Update on setting and maintaining a trackable status for bugs

[Humble Devassy Chirammal]

Hi,

Refer # http://www.gluster.org/community/documentation/index.php/Bug_triage
for more information on bug triaging process.

--Humble


On Sat, Jul 12, 2014 at 1:40 AM, Niels de Vos nde...@redhat.com wrote:

 Hi all,

 we (sub-maintainers and component owners) will be trying to enforce
 a more trackable status of the various bugs that we have and get
 reported. In order to get everyone on one line, we will follow
 a documented life-cycle for the bugs:
 -
 http://www.gluster.org/community/documentation/index.php/Bug_report_life_cycle

 The life-cycle will help developers and bug reporters understanding
 where in the process a certain fix is. It makes it easier to find the
 package versions that should solve the reported issues. With this, we
 hope to get more verifications of fixes from the bug reporters and other
 community users.

 With help from some scripts, I have been checking and correcting the
 status of many bugs this evening. Now, most¹ bugs that have:

 1. patches posted, should be in POST
 2. have all their patches merged, should be in MODIFIED
 3. have patches merged and a beta release contains those, ON_QA
 4. where all patches have been included in a final release, CLOSED

 So, don't be surprised to see many bug changes. This is intended and
 should get us in a better position to really start a continued triaging
 process for new bug reports. All details on how/when/who the triaging
 will be done is not clear yet. Any volunteers that would like to be part
 of the triaging and help with initial debugging and data gathering
 should contact us (reply to this email on the list would work).

 Have a good weekend,
 Niels

 ¹ Bug 1091833 is the last one I checked today, continuing an other time.
 ___
 Gluster-devel mailing list
 Gluster-devel@gluster.org
 http://supercolony.gluster.org/mailman/listinfo/gluster-devel

___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://supercolony.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] [Gluster-users] GlusterFS libgfapi

[Humble Devassy Chirammal]

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 vbel...@redhat.com wrote:

 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 is relatively well documented [1]. Do let us know if you
 need more than what is available there.

 api/examples does contain a sample implementation in C. You can also look
 up that for reference.

 Regards,
 Vijay

 [1] https://github.com/gluster/glusterfs/blob/master/api/src/glfs.h

 ___
 Gluster-devel mailing list
 Gluster-devel@gluster.org
 http://supercolony.gluster.org/mailman/listinfo/gluster-devel

___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://supercolony.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] Build glusterfs from source code on sqeezy

[Humble Devassy Chirammal]

Also navigate http://download.gluster.org/pub/gluster/glusterfs/3.4/3.4.2/


On Tue, Jun 24, 2014 at 11:23 AM, Humble Devassy Chirammal 
humble.deva...@gmail.com wrote:

 Hi,

 You can fetch sources from
 http://bits.gluster.org/pub/gluster/glusterfs/src/

 --Humble


 On Tue, Jun 24, 2014 at 4:57 AM, Cary Tsai f4l...@gmail.com wrote:

 Need to compile and build glusterfs 3.4.2 from source on
 debian 6.0.6 32-bit environment.
 [Indeed I only need glusterrfs-client]

 Could not find the source from the download site,
 1. should I download it from github.com?
 2. I download it from github and in INSTALL, it says
 run ./configure, but there is no ./configure
 so how do I built glusterfs?
 Do I look at the wrong place?
 Thanks for your help.



 ___
 Gluster-devel mailing list
 Gluster-devel@gluster.org
 http://supercolony.gluster.org/mailman/listinfo/gluster-devel



___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://supercolony.gluster.org/mailman/listinfo/gluster-devel