Re: [Gluster-devel] [Gluster-Maintainers] Proposal to change the version numbers of Gluster project

On Wed, Mar 14, 2018 at 9:48 PM, Atin Mukherjee wrote: > > > On Thu, Mar 15, 2018 at 9:45 AM, Vijay Bellur wrote: > >> >> >> On Wed, Mar 14, 2018 at 5:40 PM, Shyam Ranganathan >> wrote: >> >>> On 03/14/2018 07:04 PM, Joe Julian wrote: >>> > >>> > >>> > On 03/14/2018 02:25 PM, Vijay Bellur wrote

Re: [Gluster-devel] [Gluster-Maintainers] Release 4.1: LTM release targeted for end of May

On Wed, Mar 14, 2018 at 8:27 PM, Amye Scavarda wrote: > Responding on the architects question: > > On Tue, Mar 13, 2018 at 9:57 PM, Pranith Kumar Karampuri < > pkara...@redhat.com> wrote: > >> >> >> On Tue, Mar 13, 2018 at 4:26 PM, Pranith Kumar Karampuri < >> pkara...@redhat.com> wrote: >> >>> >

[Gluster-devel] More proxy cleanup coming

Hi, So now we have a new proxy (yes, I am almost as proud of it as the firewall), I need to move the old service on the old proxy to the new one. It will imply some time of unavailability, because DNS has latency to propagate, and we need DNS in place for letsencrypt before deploying. And we still

[Gluster-devel] Coverity covscan for 2018-03-15-34671430 (master branch)

GlusterFS Coverity covscan results are available from http://download.gluster.org/pub/gluster/glusterfs/static-analysis/master/glusterfs-coverity/2018-03-15-34671430 ___ Gluster-devel mailing list Gluster-devel@gluster.org http://lists.gluster.org/mailman

[Gluster-devel] Coverity covscan for 2018-03-15-34671430 (master branch)

GlusterFS Coverity covscan results are available from http://download.gluster.org/pub/gluster/glusterfs/static-analysis/master/glusterfs-coverity/2018-03-15-34671430 ___ Gluster-devel mailing list Gluster-devel@gluster.org http://lists.gluster.org/mailman

[Gluster-devel] Coverity covscan for 2018-03-15-34671430 (master branch)

GlusterFS Coverity covscan results are available from http://download.gluster.org/pub/gluster/glusterfs/static-analysis/master/glusterfs-coverity/2018-03-15-34671430 ___ Gluster-devel mailing list Gluster-devel@gluster.org http://lists.gluster.org/mailman

Re: [Gluster-devel] Release 4.1: LTM release targeted for end of May

Hi, Would like to propose Cloudsync Xlator(for Archival use-case) for 4.1. (github issue-id #387). Initial patch (under review) is posted here: https://review.gluster.org/#/c/18532/. Spec file: https://review.gluster.org/#/c/18854/ Thanks, Susant On Thu, Mar 15, 2018 at 4:05 PM, Ravishankar

Re: [Gluster-devel] [Gluster-Maintainers] Proposal to change the version numbers of Gluster project

On 03/15/2018 12:48 AM, Atin Mukherjee wrote: > > > On Thu, Mar 15, 2018 at 9:45 AM, Vijay Bellur > wrote: > > > > On Wed, Mar 14, 2018 at 5:40 PM, Shyam Ranganathan > mailto:srang...@redhat.com>> wrote: > > On 03/14/2018 07:04 PM, Joe Julian wrote:

Re: [Gluster-devel] Release 4.1: LTM release targeted for end of May

On 03/13/2018 07:07 AM, Shyam Ranganathan wrote: Hi, As we wind down on 4.0 activities (waiting on docs to hit the site, and packages to be available in CentOS repositories before announcing the release), it is time to start preparing for the 4.1 release. 4.1 is where we have GD2 fully functi

Re: [Gluster-devel] ./tests/basic/mount-nfs-auth.t spews out warnings

I assume we build with --enable-gnfs turned on. Unlikely that its not, but just pointing it out as initially I ran into some failures due to gNFS server not coming due to lake of relevant libraries. On Thu, Mar 15, 2018 at 3:46 PM, Raghavendra Gowdappa wrote: > Providing more links to failure: >

Re: [Gluster-devel] ./tests/basic/mount-nfs-auth.t spews out warnings

Providing more links to failure: https://build.gluster.org/job/experimental-periodic/227/console https://build.gluster.org/job/regression-test-burn-in/3836/console On Thu, Mar 15, 2018 at 3:39 PM, Raghavendra Gowdappa wrote: > I can reproduce the failure even without my patch on master. Looks l

Re: [Gluster-devel] ./tests/basic/mount-nfs-auth.t spews out warnings

I can reproduce the failure even without my patch on master. Looks like this test resulted in failures earlier too. [1] http://lists.gluster.org/pipermail/gluster-devel/2015-May/044932.html [2] See mail to gluster-maintainers with subj: "Build failed in Jenkins: regression-test-burn-in #3836" Usu

[Gluster-devel] gluster-ant is now admin on synced repos

Hello, If there's a repo that's synced from Gerrit to Github, gluster-ant is now admin on those repos. This is so that when issues are closed via commit message, it is closed by the right user (the bot). Rather than the Infra person who set that repo up. As always, please file a bug if you notice