Re: [Gluster-Maintainers] Release 4.1: LTM release targeted for end of May
On 03/26/2018 12:33 AM, Aravinda wrote: >>> Also want to propose that, we include a release >>> of http://github.com/gluster/gluster-health-report with 4.1, and make >>> the project more usable. >> In the theme of including sub-projects that we want to highlight, what >> else should we tag a release for or highlight with 4.1? >> >> @Aravinda, how do you envision releasing this with 4.1? IOW, what >> interop tests and hence sanity can be ensured with 4.1 and how can we >> tag a release that is sane against 4.1? > > Some more changes required to make it work with Gluster 4.x, I will work > on fixing those issues and test scripts. > > I have not yet started with Packaging for Fedora/Ubuntu. As of now > available as `pip install`. Let me know if that is fine with 4.1 release. Aravinda, what issue in the gluster-health-report repo should I track for closure? Thanks, Shyam ___ maintainers mailing list maintainers@gluster.org http://lists.gluster.org/mailman/listinfo/maintainers
Re: [Gluster-Maintainers] Release 4.1: LTM release targeted for end of May
On 03/23/2018 09:18 AM, Niels de Vos wrote: > On Fri, Mar 23, 2018 at 10:17:28AM +0530, Amar Tumballi wrote: >> On Thu, Mar 22, 2018 at 11:34 PM, Shyam Ranganathan >> wrote: >> >>> On 03/21/2018 04:12 AM, Amar Tumballi wrote: Current 4.1 project release lane is empty! I cleaned it up, because I want to hear from all as to what content to add, than add things >>> marked with the 4.1 milestone by default. I would like to see we have sane default values for most of the options, or have group options for many use-cases. >>> >>> Amar, do we have an issue that lists the use-cases and hence the default >>> groups to be provided for the same? >>> >>> >> Considering group options' task is more in glusterd2, the issue is @ >> https://github.com/gluster/glusterd2/issues/614 & >> https://github.com/gluster/glusterd2/issues/454 > > Maybe somehow link those with > https://github.com/gluster/glusterfs/issues/294 ? All done. Updated the 4.1 release board with the GD2 issues and posted a comment linking glusterfs issue with the same. ___ maintainers mailing list maintainers@gluster.org http://lists.gluster.org/mailman/listinfo/maintainers
Re: [Gluster-Maintainers] Release 4.1: LTM release targeted for end of May
On 03/22/2018 11:34 PM, Shyam Ranganathan wrote: On 03/21/2018 04:12 AM, Amar Tumballi wrote: Current 4.1 project release lane is empty! I cleaned it up, because I want to hear from all as to what content to add, than add things marked with the 4.1 milestone by default. I would like to see we have sane default values for most of the options, or have group options for many use-cases. Amar, do we have an issue that lists the use-cases and hence the default groups to be provided for the same? Also want to propose that, we include a release of http://github.com/gluster/gluster-health-report with 4.1, and make the project more usable. In the theme of including sub-projects that we want to highlight, what else should we tag a release for or highlight with 4.1? @Aravinda, how do you envision releasing this with 4.1? IOW, what interop tests and hence sanity can be ensured with 4.1 and how can we tag a release that is sane against 4.1? Some more changes required to make it work with Gluster 4.x, I will work on fixing those issues and test scripts. I have not yet started with Packaging for Fedora/Ubuntu. As of now available as `pip install`. Let me know if that is fine with 4.1 release. Also, we see that some of the patches from FB branch on namespace and throttling are in, so we would like to call that feature out as experimental by then. I would assume we track this against https://github.com/gluster/glusterfs/issues/408 would that be right? ___ maintainers mailing list maintainers@gluster.org http://lists.gluster.org/mailman/listinfo/maintainers -- regards Aravinda VK ___ maintainers mailing list maintainers@gluster.org http://lists.gluster.org/mailman/listinfo/maintainers
Re: [Gluster-Maintainers] Release 4.1: LTM release targeted for end of May
On Fri, Mar 23, 2018 at 10:17:28AM +0530, Amar Tumballi wrote: > On Thu, Mar 22, 2018 at 11:34 PM, Shyam Ranganathan > wrote: > > > On 03/21/2018 04:12 AM, Amar Tumballi wrote: > > > Current 4.1 project release lane is empty! I cleaned it up, because I > > > want to hear from all as to what content to add, than add things > > marked > > > with the 4.1 milestone by default. > > > > > > > > > I would like to see we have sane default values for most of the options, > > > or have group options for many use-cases. > > > > Amar, do we have an issue that lists the use-cases and hence the default > > groups to be provided for the same? > > > > > Considering group options' task is more in glusterd2, the issue is @ > https://github.com/gluster/glusterd2/issues/614 & > https://github.com/gluster/glusterd2/issues/454 Maybe somehow link those with https://github.com/gluster/glusterfs/issues/294 ? Niels ___ maintainers mailing list maintainers@gluster.org http://lists.gluster.org/mailman/listinfo/maintainers
Re: [Gluster-Maintainers] Release 4.1: LTM release targeted for end of May
On Thu, Mar 22, 2018 at 11:34 PM, Shyam Ranganathan wrote: > On 03/21/2018 04:12 AM, Amar Tumballi wrote: > > Current 4.1 project release lane is empty! I cleaned it up, because I > > want to hear from all as to what content to add, than add things > marked > > with the 4.1 milestone by default. > > > > > > I would like to see we have sane default values for most of the options, > > or have group options for many use-cases. > > Amar, do we have an issue that lists the use-cases and hence the default > groups to be provided for the same? > > Considering group options' task is more in glusterd2, the issue is @ https://github.com/gluster/glusterd2/issues/614 & https://github.com/gluster/glusterd2/issues/454 > > > > Also want to propose that, we include a release > > of http://github.com/gluster/gluster-health-report with 4.1, and make > > the project more usable. > > In the theme of including sub-projects that we want to highlight, what > else should we tag a release for or highlight with 4.1? > > @Aravinda, how do you envision releasing this with 4.1? IOW, what > interop tests and hence sanity can be ensured with 4.1 and how can we > tag a release that is sane against 4.1? > > > > > Also, we see that some of the patches from FB branch on namespace and > > throttling are in, so we would like to call that feature out as > > experimental by then. > > I would assume we track this against > https://github.com/gluster/glusterfs/issues/408 would that be right? > Yes, that is right. sorry for missing out the github issues in the first email. -Amar ___ maintainers mailing list maintainers@gluster.org http://lists.gluster.org/mailman/listinfo/maintainers
Re: [Gluster-Maintainers] Release 4.1: LTM release targeted for end of May
On 03/21/2018 04:12 AM, Amar Tumballi wrote: > Current 4.1 project release lane is empty! I cleaned it up, because I > want to hear from all as to what content to add, than add things marked > with the 4.1 milestone by default. > > > I would like to see we have sane default values for most of the options, > or have group options for many use-cases. Amar, do we have an issue that lists the use-cases and hence the default groups to be provided for the same? > > Also want to propose that, we include a release > of http://github.com/gluster/gluster-health-report with 4.1, and make > the project more usable. In the theme of including sub-projects that we want to highlight, what else should we tag a release for or highlight with 4.1? @Aravinda, how do you envision releasing this with 4.1? IOW, what interop tests and hence sanity can be ensured with 4.1 and how can we tag a release that is sane against 4.1? > > Also, we see that some of the patches from FB branch on namespace and > throttling are in, so we would like to call that feature out as > experimental by then. I would assume we track this against https://github.com/gluster/glusterfs/issues/408 would that be right? ___ maintainers mailing list maintainers@gluster.org http://lists.gluster.org/mailman/listinfo/maintainers
Re: [Gluster-Maintainers] Release 4.1: LTM release targeted for end of May
On Tue, Mar 13, 2018 at 7: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 functional and shipping with migration > tools to aid Glusterd to GlusterD2 migrations. > > Other than the above, this is a call out for features that are in the > works for 4.1. Please *post* the github issues to the *devel lists* that > you would like as a part of 4.1, and also mention the current state of > development. > > Further, as we hit end of March, we would make it mandatory for features > to have required spec and doc labels, before the code is merged, so > factor in efforts for the same if not already done. > > Current 4.1 project release lane is empty! I cleaned it up, because I > want to hear from all as to what content to add, than add things marked > with the 4.1 milestone by default. > > I would like to see we have sane default values for most of the options, or have group options for many use-cases. Also want to propose that, we include a release of http://github.com/gluster/gluster-health-report with 4.1, and make the project more usable. Also, we see that some of the patches from FB branch on namespace and throttling are in, so we would like to call that feature out as experimental by then. Regards, Amar > Thanks, > Shyam > P.S: Also any volunteers to shadow/participate/run 4.1 as a release owner? > ___ > maintainers mailing list > maintainers@gluster.org > http://lists.gluster.org/mailman/listinfo/maintainers > -- Amar Tumballi (amarts) ___ maintainers mailing list maintainers@gluster.org http://lists.gluster.org/mailman/listinfo/maintainers
Re: [Gluster-Maintainers] Release 4.1: LTM release targeted for end of May
I would like to turn features.sdfs on by default starting from 4.1. Details can be found in issue: https://github.com/gluster/glusterfs/issues/421 On Fri, Mar 16, 2018 at 1:00 PM, Xavi Hernandez wrote: > On Tue, Mar 13, 2018 at 2:37 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 functional and shipping with migration >> tools to aid Glusterd to GlusterD2 migrations. >> >> Other than the above, this is a call out for features that are in the >> works for 4.1. Please *post* the github issues to the *devel lists* that >> you would like as a part of 4.1, and also mention the current state of >> development. >> > > I would like to propose the transaction framework [1] as an experimental > feature for 4.1. The design [2] is done and I'm currently developing it. > > Xavi > > [1] https://github.com/gluster/glusterfs/issues/342 > [2] https://docs.google.com/document/d/1Zp99bsfLsB51tPen_ > zC8enANvOhX3o451pd5LyEdRSM/edit?usp=sharing > > >> Further, as we hit end of March, we would make it mandatory for features >> to have required spec and doc labels, before the code is merged, so >> factor in efforts for the same if not already done. >> >> Current 4.1 project release lane is empty! I cleaned it up, because I >> want to hear from all as to what content to add, than add things marked >> with the 4.1 milestone by default. >> >> Thanks, >> Shyam >> P.S: Also any volunteers to shadow/participate/run 4.1 as a release owner? >> ___ >> maintainers mailing list >> maintainers@gluster.org >> http://lists.gluster.org/mailman/listinfo/maintainers >> > > > ___ > maintainers mailing list > maintainers@gluster.org > http://lists.gluster.org/mailman/listinfo/maintainers > > ___ maintainers mailing list maintainers@gluster.org http://lists.gluster.org/mailman/listinfo/maintainers
Re: [Gluster-Maintainers] Release 4.1: LTM release targeted for end of May
On Tue, Mar 13, 2018 at 2:37 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 functional and shipping with migration > tools to aid Glusterd to GlusterD2 migrations. > > Other than the above, this is a call out for features that are in the > works for 4.1. Please *post* the github issues to the *devel lists* that > you would like as a part of 4.1, and also mention the current state of > development. > I would like to propose the transaction framework [1] as an experimental feature for 4.1. The design [2] is done and I'm currently developing it. Xavi [1] https://github.com/gluster/glusterfs/issues/342 [2] https://docs.google.com/document/d/1Zp99bsfLsB51tPen_zC8enANvOhX3o451pd5LyEdRSM/edit?usp=sharing > Further, as we hit end of March, we would make it mandatory for features > to have required spec and doc labels, before the code is merged, so > factor in efforts for the same if not already done. > > Current 4.1 project release lane is empty! I cleaned it up, because I > want to hear from all as to what content to add, than add things marked > with the 4.1 milestone by default. > > Thanks, > Shyam > P.S: Also any volunteers to shadow/participate/run 4.1 as a release owner? > ___ > maintainers mailing list > maintainers@gluster.org > http://lists.gluster.org/mailman/listinfo/maintainers > ___ maintainers mailing list maintainers@gluster.org http://lists.gluster.org/mailman/listinfo/maintainers
Re: [Gluster-Maintainers] Release 4.1: LTM release targeted for end of May
On Tue, Mar 13, 2018 at 7: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 functional and shipping with migration > tools to aid Glusterd to GlusterD2 migrations. > > Other than the above, this is a call out for features that are in the > works for 4.1. Please *post* the github issues to the *devel lists* that > you would like as a part of 4.1, and also mention the current state of > development. > > Further, as we hit end of March, we would make it mandatory for features > to have required spec and doc labels, before the code is merged, so > factor in efforts for the same if not already done. > Could you explain the point above further? Is it just the label or the spec/doc that we need merged before the patch is merged? > > Current 4.1 project release lane is empty! I cleaned it up, because I > want to hear from all as to what content to add, than add things marked > with the 4.1 milestone by default. > > Thanks, > Shyam > P.S: Also any volunteers to shadow/participate/run 4.1 as a release owner? > ___ > maintainers mailing list > maintainers@gluster.org > http://lists.gluster.org/mailman/listinfo/maintainers > -- Pranith ___ maintainers mailing list maintainers@gluster.org http://lists.gluster.org/mailman/listinfo/maintainers
