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

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)
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 at gluster.org
> http://lists.gluster.org/mailman/listinfo/gluster-devel

On Thu, Apr 13, 2017 at 8:17 PM, Shyam <srangana at 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).
>
https://github.com/gluster/glusterfs/issues/158 will get into 3.11. This
feature enhances the existing get-state cli implementation to add few more
parameters like client details, brick consumption to the output file so
that these new attributes can be considered by tendrl project.

>
>
>> *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)
> 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-Februa
>> ry/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-Decemb
>> er/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 at gluster.org
>> http://lists.gluster.org/mailman/listinfo/gluster-devel
>>
> _______________________________________________
> Gluster-devel mailing list
> Gluster-devel at gluster.org
> http://lists.gluster.org/mailman/listinfo/gluster-devel
>


-- 

ATin Mukherjee

Associate Manager, RHGS Development

Red Hat

<https://www.redhat.com>

amukherj at redhat.com    M: +919739491377
<http://redhatemailsignature-marketing.itos.redhat.com/>     IM: IRC:
atinm, twitter: @mukherjee_atin
<https://red.ht/sig>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.gluster.org/pipermail/gluster-users/attachments/20170413/b337093d/attachment.html>

----- Original Message -----
> From: "Shyam" <srangana at redhat.com>
> To: "Gluster Devel" <gluster-devel at gluster.org>
> Cc: gluster-users at gluster.org
> Sent: Thursday, April 13, 2017 8:17:34 PM
> Subject: Re: [Gluster-devel] Announcing release 3.11 : Scope, schedule and
feature tracking
> 
> 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)
> 3) Negative lookup (@poornima)
Issue: https://github.com/gluster/glusterfs/issues/82
Bug: https://bugzilla.redhat.com/show_bug.cgi?id=1442569
Patch: https://review.gluster.org/#/c/16952/
This feature is targeted for 3.11 as an experimental feature and mostly for
SMB users only.
> 4) Parallel Readdirp - More changes to default settings. (@poornima, @du)
I think we should let it be optional for another release,
until it stabilizes. However, for this release we would like to make it
production feature (not experimental). I have raised the issue for
the same: https://github.com/gluster/glusterfs/issues/166

Also for 3.11, one more item would be to make the md-cache improvements
production feature, it is experimental currently. Issue for the same:
https://github.com/gluster/glusterfs/issues/167

Will add the release notes for all these features in the issues. I do not have
permissions to add labels though.

Thanks,
Poornima
> 
> > [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 at gluster.org
> > http://lists.gluster.org/mailman/listinfo/gluster-devel
> _______________________________________________
> Gluster-devel mailing list
> Gluster-devel at gluster.org
> http://lists.gluster.org/mailman/listinfo/gluster-devel
>

On Thu, Apr 13, 2017 at 8:17 PM, Shyam <srangana at 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, 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 at gluster.org
>> http://lists.gluster.org/mailman/listinfo/gluster-devel
>
> _______________________________________________
> Gluster-devel mailing list
> Gluster-devel at gluster.org
> http://lists.gluster.org/mailman/listinfo/gluster-devel

On Thu, Apr 13, 2017 at 8:17 PM, Shyam <srangana at 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, 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)
>
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.

> 2) IPv6 support (@kaushal)
> 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-Februa
>> ry/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-Decemb
>> er/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 at gluster.org
>> http://lists.gluster.org/mailman/listinfo/gluster-devel
>>
> _______________________________________________
> Gluster-devel mailing list
> Gluster-devel at gluster.org
> http://lists.gluster.org/mailman/listinfo/gluster-devel
>


-- 
Pranith
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.gluster.org/pipermail/gluster-users/attachments/20170425/a9e5bf43/attachment.html>