Re: [Gluster-devel] [Gluster-users] Announcing release 3.11 : Scope, schedule and feature tracking

2017-04-26 Thread Shyam 

On 04/26/2017 03:53 AM, Soumya Koduri wrote:

Hi Shyam,

On 04/25/2017 07:38 PM, Shyam wrote:

On 04/25/2017 07:40 AM, Pranith Kumar Karampuri wrote:



On Thu, Apr 13, 2017 at 8:17 PM, Shyam > wrote:

On 02/28/2017 10:17 AM, Shyam wrote:
1) Halo - Initial Cut (@pranith)


Sorry for the delay in response. Due to some other work engagements, I
couldn't spend time on this, I think I can get this done if there is one
week grace period, by 5thMay. Or I can get this done for 3.12.0. Do let
me know what you think.


Let us backport this to 3.11 post branching, that way the schedule is
kept as is. It would help to stick to the schedule if this gets
backported by, May-05th.

Considering this request, any other features that needs a few more days
to be completed, can target this date by when (post branching) we need
the backport of the feature to 3.11 branch.


If that is the case, can [1] be considered for 3.11 as well. I hadn't
proposed it earlier as I wasn't sure if it shall be ready on time. I now
have initial prototype working. I will submit subsequent patches for any
additional changes or testscript.


Ok, accepted. Added to the release lane as well. This would be another 
possible backport at the end of a week post branching (May-05)




Thanks,
Soumya

[1] https://github.com/gluster/glusterfs/issues/174



Thanks,
Shyam
___
Gluster-users mailing list
gluster-us...@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-users

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

Re: [Gluster-devel] [Gluster-users] Announcing release 3.11 : Scope, schedule and feature tracking

2017-04-26 Thread Soumya Koduri 

Hi Shyam,

On 04/25/2017 07:38 PM, Shyam wrote:

On 04/25/2017 07:40 AM, Pranith Kumar Karampuri wrote:



On Thu, Apr 13, 2017 at 8:17 PM, Shyam > wrote:

On 02/28/2017 10:17 AM, Shyam wrote:
1) Halo - Initial Cut (@pranith)


Sorry for the delay in response. Due to some other work engagements, I
couldn't spend time on this, I think I can get this done if there is one
week grace period, by 5thMay. Or I can get this done for 3.12.0. Do let
me know what you think.


Let us backport this to 3.11 post branching, that way the schedule is
kept as is. It would help to stick to the schedule if this gets
backported by, May-05th.

Considering this request, any other features that needs a few more days
to be completed, can target this date by when (post branching) we need
the backport of the feature to 3.11 branch.


If that is the case, can [1] be considered for 3.11 as well. I hadn't 
proposed it earlier as I wasn't sure if it shall be ready on time. I now 
have initial prototype working. I will submit subsequent patches for any 
additional changes or testscript.


Thanks,
Soumya

[1] https://github.com/gluster/glusterfs/issues/174



Thanks,
Shyam
___
Gluster-users mailing list
gluster-us...@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-users

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

Re: [Gluster-devel] [Gluster-users] Announcing release 3.11 : Scope, schedule and feature tracking

2017-04-25 Thread Serkan Çoban 
How this affect CPU usage? Does it read whole file and calculates a
hash after it is being written?
Will this patch land in 3.10.x?

On Tue, Apr 25, 2017 at 10:32 AM, Kotresh Hiremath Ravishankar
 wrote:
> Hi
>
> https://github.com/gluster/glusterfs/issues/188 is merged in master
> and needs to go in 3.11
>
> Thanks and Regards,
> Kotresh H R
>
> - Original Message -
>> From: "Kaushal M" 
>> To: "Shyam" 
>> Cc: gluster-us...@gluster.org, "Gluster Devel" 
>> Sent: Thursday, April 20, 2017 12:16:39 PM
>> Subject: Re: [Gluster-devel] Announcing release 3.11 : Scope, schedule and 
>> feature tracking
>>
>> On Thu, Apr 13, 2017 at 8:17 PM, Shyam  wrote:
>> > On 02/28/2017 10:17 AM, Shyam wrote:
>> >>
>> >> Hi,
>> >>
>> >> With release 3.10 shipped [1], it is time to set the dates for release
>> >> 3.11 (and subsequently 4.0).
>> >>
>> >> This mail has the following sections, so please read or revisit as needed,
>> >>   - Release 3.11 dates (the schedule)
>> >>   - 3.11 focus areas
>> >
>> >
>> > Pinging the list on the above 2 items.
>> >
>> >> *Release 3.11 dates:*
>> >> Based on our release schedule [2], 3.11 would be 3 months from the 3.10
>> >> release and would be a Short Term Maintenance (STM) release.
>> >>
>> >> This puts 3.11 schedule as (working from the release date backwards):
>> >> - Release: May 30th, 2017
>> >> - Branching: April 27th, 2017
>> >
>> >
>> > Branching is about 2 weeks away, other than the initial set of overflow
>> > features from 3.10 nothing else has been raised on the lists and in github
>> > as requests for 3.11.
>> >
>> > So, a reminder to folks who are working on features, to raise the relevant
>> > github issue for the same, and post it to devel list for consideration in
>> > 3.11 (also this helps tracking and ensuring we are waiting for the right
>> > things at the time of branching).
>> >
>> >>
>> >> *3.11 focus areas:*
>> >> As maintainers of gluster, we want to harden testing around the various
>> >> gluster features in this release. Towards this the focus area for this
>> >> release are,
>> >>
>> >> 1) Testing improvements in Gluster
>> >>   - Primary focus would be to get automated test cases to determine
>> >> release health, rather than repeating a manual exercise every 3 months
>> >>   - Further, we would also attempt to focus on maturing Glusto[7] for
>> >> this, and other needs (as much as possible)
>> >>
>> >> 2) Merge all (or as much as possible) Facebook patches into master, and
>> >> hence into release 3.11
>> >>   - Facebook has (as announced earlier [3]) started posting their
>> >> patches mainline, and this needs some attention to make it into master
>> >>
>> >
>> > Further to the above, we are also considering the following features for
>> > this release, request feature owners to let us know if these are actively
>> > being worked on and if these will make the branching dates. (calling out
>> > folks that I think are the current feature owners for the same)
>> >
>> > 1) Halo - Initial Cut (@pranith)
>> > 2) IPv6 support (@kaushal)
>>
>> This is under review at https://review.gluster.org/16228 . The patch
>> mostly looks fine.
>>
>> The only issue is that it currently depends and links with an internal
>> FB fork of tirpc (mainly for some helper functions and utilities).
>> This makes it hard for the community to make actual use of  and test,
>> the IPv6 features/fixes introduced by the change.
>>
>> If the change were refactored the use publicly available versions of
>> tirpc or ntirpc, I'm OK for it to be merged. I did try it out myself.
>> While I was able to build it against available versions of tirpc, I
>> wasn't able to get it working correctly.
>>
>> > 3) Negative lookup (@poornima)
>> > 4) Parallel Readdirp - More changes to default settings. (@poornima, @du)
>> >
>> >
>> >> [1] 3.10 release announcement:
>> >> http://lists.gluster.org/pipermail/gluster-devel/2017-February/052188.html
>> >>
>> >> [2] Gluster release schedule:
>> >> https://www.gluster.org/community/release-schedule/
>> >>
>> >> [3] Mail regarding facebook patches:
>> >> http://lists.gluster.org/pipermail/gluster-devel/2016-December/051784.html
>> >>
>> >> [4] Release scope: https://github.com/gluster/glusterfs/projects/1
>> >>
>> >> [5] glusterfs github issues: https://github.com/gluster/glusterfs/issues
>> >>
>> >> [6] github issues for features and major fixes:
>> >> https://hackmd.io/s/BkgH8sdtg#
>> >>
>> >> [7] Glusto tests: https://github.com/gluster/glusto-tests
>> >> ___
>> >> 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] [Gluster-users] Announcing release 3.11 : Scope, schedule and feature tracking

2017-04-25 Thread Kotresh Hiremath Ravishankar 
Hi Serkan,

Even though bitrot is not enabled, versioning was being done.
As part of it, on every fresh lookup, getxattr calls were
made to find weather object is bad, to get it's current version
and signature. So a find on gluster mount sometimes would cause
high cpu utilization. 

Since this is an RFE, it would be available from 3.11 and would not
be back ported to 3.10.x


Thanks and Regards,
Kotresh H R

- Original Message -
> From: "Serkan Çoban" <cobanser...@gmail.com>
> To: "Kotresh Hiremath Ravishankar" <khire...@redhat.com>
> Cc: "Shyam" <srang...@redhat.com>, "Gluster Users" 
> <gluster-us...@gluster.org>, "Gluster Devel"
> <gluster-devel@gluster.org>
> Sent: Tuesday, April 25, 2017 1:25:39 PM
> Subject: Re: [Gluster-users] [Gluster-devel] Announcing release 3.11 : Scope, 
> schedule and feature tracking
> 
> How this affect CPU usage? Does it read whole file and calculates a
> hash after it is being written?
> Will this patch land in 3.10.x?
> 
> On Tue, Apr 25, 2017 at 10:32 AM, Kotresh Hiremath Ravishankar
> <khire...@redhat.com> wrote:
> > Hi
> >
> > https://github.com/gluster/glusterfs/issues/188 is merged in master
> > and needs to go in 3.11
> >
> > Thanks and Regards,
> > Kotresh H R
> >
> > - Original Message -
> >> From: "Kaushal M" <kshlms...@gmail.com>
> >> To: "Shyam" <srang...@redhat.com>
> >> Cc: gluster-us...@gluster.org, "Gluster Devel" <gluster-devel@gluster.org>
> >> Sent: Thursday, April 20, 2017 12:16:39 PM
> >> Subject: Re: [Gluster-devel] Announcing release 3.11 : Scope, schedule and
> >> feature tracking
> >>
> >> On Thu, Apr 13, 2017 at 8:17 PM, Shyam <srang...@redhat.com> wrote:
> >> > On 02/28/2017 10:17 AM, Shyam wrote:
> >> >>
> >> >> Hi,
> >> >>
> >> >> With release 3.10 shipped [1], it is time to set the dates for release
> >> >> 3.11 (and subsequently 4.0).
> >> >>
> >> >> This mail has the following sections, so please read or revisit as
> >> >> needed,
> >> >>   - Release 3.11 dates (the schedule)
> >> >>   - 3.11 focus areas
> >> >
> >> >
> >> > Pinging the list on the above 2 items.
> >> >
> >> >> *Release 3.11 dates:*
> >> >> Based on our release schedule [2], 3.11 would be 3 months from the 3.10
> >> >> release and would be a Short Term Maintenance (STM) release.
> >> >>
> >> >> This puts 3.11 schedule as (working from the release date backwards):
> >> >> - Release: May 30th, 2017
> >> >> - Branching: April 27th, 2017
> >> >
> >> >
> >> > Branching is about 2 weeks away, other than the initial set of overflow
> >> > features from 3.10 nothing else has been raised on the lists and in
> >> > github
> >> > as requests for 3.11.
> >> >
> >> > So, a reminder to folks who are working on features, to raise the
> >> > relevant
> >> > github issue for the same, and post it to devel list for consideration
> >> > in
> >> > 3.11 (also this helps tracking and ensuring we are waiting for the right
> >> > things at the time of branching).
> >> >
> >> >>
> >> >> *3.11 focus areas:*
> >> >> As maintainers of gluster, we want to harden testing around the various
> >> >> gluster features in this release. Towards this the focus area for this
> >> >> release are,
> >> >>
> >> >> 1) Testing improvements in Gluster
> >> >>   - Primary focus would be to get automated test cases to determine
> >> >> release health, rather than repeating a manual exercise every 3 months
> >> >>   - Further, we would also attempt to focus on maturing Glusto[7] for
> >> >> this, and other needs (as much as possible)
> >> >>
> >> >> 2) Merge all (or as much as possible) Facebook patches into master, and
> >> >> hence into release 3.11
> >> >>   - Facebook has (as announced earlier [3]) started posting their
> >> >> patches mainline, and this needs some attention to make it into master
> >> >>
> >> >
> >> > Further to the above, we are also considering the following features for
> >> > this release, re

Re: [Gluster-devel] [Gluster-users] Announcing release 3.11 : Scope, schedule and feature tracking

2017-03-03 Thread Ravishankar N 

On 03/03/2017 07:23 PM, Shyam wrote:

On 03/03/2017 06:44 AM, Prashanth Pai wrote:



On 02/28/2017 08:47 PM, Shyam wrote:

We should be transitioning to using github for feature reporting and
tracking, more fully from this release. So once again, if there exists
any confusion on that front, reach out to the lists for clarification.


I see that there was a discussion on this on the maintainers ML [1]. If
it is not too late or if I may cast vote as a non-maintainer, I prefer
to have bugzilla  for tracking bugs and the users ML for queries. I see
many 'issues' on the github page which are mostly candidates for
gluster-users ML.


+1 to that


Ok, there is some confusion here I think ;)

So,
- github issues is for features *only*
- Issues are *not* for bugs or a substitute for ML posts/discussions
- The proposal in maintainers for the same (i.e [1]) did not go 
through, and hence was never proposed to the devel and users groups


So to make this clear in github, this [2] commit is put up for review 
(and now merged and live, check [3]), that will clarify this for users 
coming into github to file issues. If users still do file issues 
beyond this information, we can politely redirect them to the ML or BZ 
and close the issue.


Further, thanks to folks who still have been responding to queries 
over github issues (which has increased in frequency in the recent past).


HTH 


Yes, this makes sense! Thanks Shyam.



and thanks for the shout out,
Shyam

[1] 
http://lists.gluster.org/pipermail/maintainers/2017-February/002195.html 



[2] Review on github issue template: 
https://review.gluster.org/#/c/16795/2/.github/ISSUE_TEMPLATE


[3] New issue in glusterfs github view: 
https://github.com/gluster/glusterfs/issues/new



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

Re: [Gluster-devel] [Gluster-users] Announcing release 3.11 : Scope, schedule and feature tracking

2017-03-03 Thread Shyam 

On 03/03/2017 06:44 AM, Prashanth Pai wrote:



On 02/28/2017 08:47 PM, Shyam wrote:

We should be transitioning to using github for feature reporting and
tracking, more fully from this release. So once again, if there exists
any confusion on that front, reach out to the lists for clarification.


I see that there was a discussion on this on the maintainers ML [1]. If
it is not too late or if I may cast vote as a non-maintainer, I prefer
to have bugzilla  for tracking bugs and the users ML for queries. I see
many 'issues' on the github page which are mostly candidates for
gluster-users ML.


+1 to that


Ok, there is some confusion here I think ;)

So,
- github issues is for features *only*
- Issues are *not* for bugs or a substitute for ML posts/discussions
- The proposal in maintainers for the same (i.e [1]) did not go through, 
and hence was never proposed to the devel and users groups


So to make this clear in github, this [2] commit is put up for review 
(and now merged and live, check [3]), that will clarify this for users 
coming into github to file issues. If users still do file issues beyond 
this information, we can politely redirect them to the ML or BZ and 
close the issue.


Further, thanks to folks who still have been responding to queries over 
github issues (which has increased in frequency in the recent past).


HTH and thanks for the shout out,
Shyam


[1] http://lists.gluster.org/pipermail/maintainers/2017-February/002195.html


[2] Review on github issue template: 
https://review.gluster.org/#/c/16795/2/.github/ISSUE_TEMPLATE


[3] New issue in glusterfs github view: 
https://github.com/gluster/glusterfs/issues/new

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

Re: [Gluster-devel] [Gluster-users] Announcing release 3.11 : Scope, schedule and feature tracking

2017-03-03 Thread Prashanth Pai 

> On 02/28/2017 08:47 PM, Shyam wrote:
> > We should be transitioning to using github for feature reporting and
> > tracking, more fully from this release. So once again, if there exists
> > any confusion on that front, reach out to the lists for clarification.
> 
> I see that there was a discussion on this on the maintainers ML [1]. If
> it is not too late or if I may cast vote as a non-maintainer, I prefer
> to have bugzilla  for tracking bugs and the users ML for queries. I see
> many 'issues' on the github page which are mostly candidates for
> gluster-users ML.

+1 to that

> 
> Regards,
> 
> Ravi
> 
> 
> [1] http://lists.gluster.org/pipermail/maintainers/2017-February/002195.html
> 
> ___
> 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] [Gluster-users] Announcing release 3.11 : Scope, schedule and feature tracking

2017-03-03 Thread Ravishankar N 

On 02/28/2017 08:47 PM, Shyam wrote:
We should be transitioning to using github for feature reporting and 
tracking, more fully from this release. So once again, if there exists 
any confusion on that front, reach out to the lists for clarification.


I see that there was a discussion on this on the maintainers ML [1]. If 
it is not too late or if I may cast vote as a non-maintainer, I prefer 
to have bugzilla  for tracking bugs and the users ML for queries. I see 
many 'issues' on the github page which are mostly candidates for 
gluster-users ML.


Regards,

Ravi


[1] http://lists.gluster.org/pipermail/maintainers/2017-February/002195.html

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