[Gluster-devel] Spurious termination of fuse invalidation notifier thread

Hi Xavi/Kaleb/Pranith, During few of our older conversations (like [1], but not only one), some of you had reported that the thread which writes invalidation notifications (of inodes, entries) to /dev/fuse terminates spuriously. Csaba tried to reproduce the issue, but without success. It would

Re: [Gluster-devel] Checklist for perf xlator components for upstream release

- Original Message - > From: "Pranith Kumar Karampuri" > To: "Raghavendra Gowdappa" > Cc: "Gluster Devel" > Sent: Friday, September 2, 2016 11:42:06 PM > Subject: Checklist for perf xlator components for upstream

Re: [Gluster-devel] Checklist for gfapi for upstream release

Again inode/fd leaks and memory consumption should be one of the tests (just as fuse-bridge) - Original Message - > From: "Pranith Kumar Karampuri" > To: "Niels de Vos" , "Shyam Ranganathan" > > Cc: "Gluster Devel"

Re: [Gluster-devel] Checklist for FUSE bridge component for upstream release

Checking for inode/fd leaks should be top priority. We have seen a bunch of high memory consumption issues recently. [1] is first step towards that. [1] http://review.gluster.org/15318 - Original Message - > From: "Pranith Kumar Karampuri" > To: "Niels de Vos"

Re: [Gluster-devel] Checklist for RPC for upstream release

Thanks Pranith. I'll let you know by early next week. - Original Message - > From: "Pranith Kumar Karampuri" > To: "Raghavendra Gowdappa" > Cc: "Gluster Devel" > Sent: Saturday, September 3, 2016 12:20:03 AM >

Re: [Gluster-devel] Checklist for glusterd component for upstream release

We will provide the tests by early next week. On Saturday 3 September 2016, Pranith Kumar Karampuri wrote: > hi, > Did you get a chance to decide on the tests that need to be done > before doing a release for glusterd component? Could you let me know who > will be

[Gluster-devel] Anyone wants to maintain Mac-OSX port of gluster?

hi, As per MAINTAINERS file this port doesn't have maintainer. If you want to take up the responsibility of maintaining the port please let us know how you want to go about doing it and what should be the checklist of things that should be done before every release upstream. It is extremely

[Gluster-devel] Anyone wants to maintain FreeBSD port of gluster?

hi, As per MAINTAINERS file this port doesn't have maintainer. If you want to take up the responsibility of maintaining the port please let us know how you want to go about doing it and what should be the checklist of things that should be done before every release upstream. It is extremely

[Gluster-devel] Checklist for glusterfs packaging/build for upstream release

hi, In the past we have had issues where some of the functionality didn't work on debian/ubuntu because 'glfsheal' binary was not packaged. What do you guys as packaging/build maintainers on different distros suggest that we do to make sure we catch such mistakes before the releases are

[Gluster-devel] Checklist for GlusterFS Hadoop HCFS plugin for upstream release

hi Jay, Are there any tests that are done before releasing glusterfs upstream to make sure the plugin is stable? Could you let us know the process, so that we can add it to https://public.pad.fsfe.org/p/gluster-component-release-checklist -- Pranith

Re: [Gluster-devel] Checklist for smb integration testing for 3.9

Thanks Raghavendra, once you guys are done, please update that you guys are done with the checklist. On Sat, Sep 3, 2016 at 12:57 AM, Raghavendra Talur wrote: > I have edited the etherpad with some tests. Please review and add other > things you recommend. > > Thanks, >

[Gluster-devel] Checklist for gluster-swift for upstream release

hi, Did you get a chance to decide on the gluster-swift integration tests that need to be run before doing an upstream gluster release? Could you let me know who will be providing with the list? I can update it at https://public.pad.fsfe.org/p/ gluster-component-release-checklist

[Gluster-devel] Checklist for Wireshark dissectors

Niels, Does wireshark also handle new fops like seek, compond, getactivelk, setactivelk FOPS? What are the other things that you check before the release? We can update more at https://public.pad.fsfe.org/p/gluster-component-release-checklist -- Pranith

[Gluster-devel] Checklist for ganesha FSAL plugin integration testing for 3.9

hi, Did you get a chance to decide on the nfs-ganesha integrations tests that need to be run before doing an upstream gluster release? Could you let me know who will be providing with the list? I can update it at https://public.pad.fsfe.org/p/ gluster-component-release-checklist --

[Gluster-devel] Checklist for eventsapi component for upstream release

hi Aravinda, I think the existing tests should be good enough to test this functionality but I could be wrong. May be we should update https://public.pad.fsfe.org/p/gluster-component-release-checklist if we need anymore things to be added. -- Aravinda & Pranith

[Gluster-devel] Checklist for snapshot component for upstream release

hi, Did you get a chance to decide on the tests that need to be done before doing a release for snapshot component? Could you let me know who will be providing with the list? I can update it at https://public.pad.fsfe.org/p/ gluster-component-release-checklist -- Aravinda & Pranith

[Gluster-devel] Checklist for RPC for upstream release

hi, I think this should be covered as part of other component testing, but if you think any more tests need to be added, please let us know. I can update it at https://public.pad.fsfe.org/p/gluster-component-release-checklist -- Aravinda & Pranith

[Gluster-devel] Checklist for glusterd component for upstream release

hi, Did you get a chance to decide on the tests that need to be done before doing a release for glusterd component? Could you let me know who will be providing with the list? I think just the cases that cover the infra part should be good enough. Component based commands should come in

[Gluster-devel] Checklist for gfapi for upstream release

hi, I think most of this testing will be covered in nfsv4, smb testing. But I could be wrong. Could you let me know who will be providing with the list if you think there are more tests that need to be run? I can update it at https://public.pad.fsfe.org/p/

[Gluster-devel] Checklist for Upcall component for upstream release

hi, Did you get a chance to decide on the tests that need to be done before doing a release for Upcall component? Could you let me know who will be providing with the list? I can update it at https://public.pad.fsfe.org/p/ gluster-component-release-checklist -- Aravinda & Pranith

[Gluster-devel] Checklist for Quota+Marker component for upstream release

hi, Did you get a chance to decide on the tests that need to be done before doing a release for Quota+Marker component? I can update it at https://public.pad.fsfe.org/p/ gluster-component-release-checklist -- Aravinda & Pranith ___

[Gluster-devel] Checklist for FUSE bridge component for upstream release

hi, Did you get a chance to decide on the tests that need to be done before doing a release for FUSE bridge component? Could you let me know who will be providing with the list? I can update it at https://public.pad.fsfe.org/p/ gluster-component-release-checklist -- Aravinda & Pranith

Re: [Gluster-devel] Checklist for Bitrot component for upstream release

On Fri, Sep 2, 2016 at 11:39 PM, Pranith Kumar Karampuri < pkara...@redhat.com> wrote: > hi, > Did you get a chance to decide on the tests that need to be done > before doing a release for Bitrot component? Could you let me know who will > be providing with the list? > > I can update it

Re: [Gluster-devel] Checklist for perf xlator components for upstream release

On Fri, Sep 2, 2016 at 11:42 PM, Pranith Kumar Karampuri < pkara...@redhat.com> wrote: > hi Raghavendra, >I feel running https://github.com/avati/perf- > test/blob/master/perf-test.sh is good enough for testing these. Do you > feel anything more needs to be done before the release? > > I

Re: [Gluster-devel] Checklist for DHT component for upstream release

On Fri, Sep 2, 2016 at 11:31 PM, Pranith Kumar Karampuri < pkara...@redhat.com> wrote: > hi, > Did you get a chance to decide on the tests that need to be done > before doing a release for DHT component? Could you let me know who will be > providing with the list? > > I can update it at

Re: [Gluster-devel] Checklist for georep family of components for upstream release

On Fri, Sep 2, 2016 at 11:36 PM, Pranith Kumar Karampuri < pkara...@redhat.com> wrote: > hi, > Did you get a chance to decide on the tests that need to be > done before doing a release for georep family of components? Could you let > me know who will be providing with the list? > > I

Re: [Gluster-devel] Checklist for tier component for upstream release

On Fri, Sep 2, 2016 at 11:52 PM, Pranith Kumar Karampuri < pkara...@redhat.com> wrote: > hi, >Did you get a chance to decide on the tests that need to be > done before doing a release for Tier component? Could you let me know who > will be providing with the list? > > I can update

[Gluster-devel] Checklist for tier component for upstream release

hi, Did you get a chance to decide on the tests that need to be done before doing a release for Tier component? Could you let me know who will be providing with the list? I can update it at https://public.pad.fsfe.org/p/ gluster-component-release-checklist -- Pranith

[Gluster-devel] Checklist for perf xlator components for upstream release

hi Raghavendra, I feel running https://github.com/avati/perf-test/blob/master/perf-test.sh is good enough for testing these. Do you feel anything more needs to be done before the release? I can update it at https://public.pad.fsfe.org/p/gluster-component-release-checklist -- Pranith

[Gluster-devel] Checklist for Bitrot component for upstream release

hi, Did you get a chance to decide on the tests that need to be done before doing a release for Bitrot component? Could you let me know who will be providing with the list? I can update it at https://public.pad.fsfe.org/p/ gluster-component-release-checklist -- Pranith

[Gluster-devel] Checklist for georep family of components for upstream release

hi, Did you get a chance to decide on the tests that need to be done before doing a release for georep family of components? Could you let me know who will be providing with the list? I think changelog, marker, georep are the features that should come under this bucket right? Are

Re: [Gluster-devel] Fix master and 3.9 regression

Both changes have regression runs in progress [1][2]. As they should be fixing the failures being seen, I'd like to see the runs completed. If the current runs fail, we can decide what to to do. ~kaushal [1] https://build.gluster.org/job/centos6-regression/496/ [2]

[Gluster-devel] Fix master and 3.9 regression

Hi, Currently the master and 3.9 regression is broken. This is because we do not have regression run just before merge(rebase). Patches http://review.gluster.org/#/c/15385/ and http://review.gluster.org/#/c/15386 fixes the same, Is it possible to merge these patches at the earliest, as they

[Gluster-devel] Release-3.9 branch created

Hi, Release 3.9 branch created yesterday. Thanks to all who contributed features and bug fixes for 3.9. Please backport non feature patches to Release-3.9 as well. Next steps: - Release-3.9 branch stabilization for GA - Tests coverage for the features - RC builds for testing - Documentation