Re: [Gluster-devel] 3.6 Feature Freeze - move to mid next week?
On 07/05/2014 01:54 AM, Justin Clift wrote: On 04/07/2014, at 12:30 PM, Vijay Bellur wrote: Hi All, Given the holiday weekend in US, I feel that it would be appropriate to move the 3.6 feature freeze date to mid next week so that we can have more reviews done & address review comments too. We can still continue to track other milestones as per our release schedule [1]. What do you folks think? How about end of next week? The extra few days could make a positive difference as to what gets in. (?) I think we can give this a shot. Let us move feature freeze to July 12th and not alter other milestones. Thanks, Vijay ___ Gluster-devel mailing list Gluster-devel@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] 3.6 Feature Freeze - move to mid next week?
On 04/07/2014, at 12:30 PM, Vijay Bellur wrote: > Hi All, > > Given the holiday weekend in US, I feel that it would be appropriate to move > the 3.6 feature freeze date to mid next week so that we can have more reviews > done & address review comments too. We can still continue to track other > milestones as per our release schedule [1]. What do you folks think? How about end of next week? The extra few days could make a positive difference as to what gets in. (?) + Justin -- GlusterFS - http://www.gluster.org An open source, distributed file system scaling to several petabytes, and handling thousands of clients. My personal twitter: twitter.com/realjustinclift ___ Gluster-devel mailing list Gluster-devel@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] 3.6 Feature Freeze - move to mid next week?
On 04/07/2014, at 4:14 PM, Jeff Darcy wrote: > ... the gluster.org feature page never got updated to > reflect the real feature set for 3.6 Oops. I can fix that later on today. + Justin -- GlusterFS - http://www.gluster.org An open source, distributed file system scaling to several petabytes, and handling thousands of clients. My personal twitter: twitter.com/realjustinclift ___ Gluster-devel mailing list Gluster-devel@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] 3.6 Feature Freeze - move to mid next week?
On 07/04/2014 11:15 PM, Jeff Darcy wrote: There is an improved implementation of trash in gerrit and can help get more traction with more reviews, rebases etc. I see nine patches for this, all failing verification and all but one inactive since March 10. Given our review rate, is this likely to converge in only a week? I think this re-factoring exercise has starved review attention by lack of rebases and not passing regression tests. Anoop and Jiffin are expected to be active on this next week. If all works well, we can possibly get Trash in. * RDMA Improvements No patches, feature page says work in progress. Don't think there are any major pieces missing to get rdma functional. More testing and bug fixes should be mostly it. Can happen in the interval between feature freeze and code freeze. The feature page specifically mentions co-existence with TCP, and performance. I'm guessing those are addressed by 149, and possibly by 4378. Is that correct? Yes, those address a few issues. I believe there are a few open bugs (don't have bz IDs handy right now) in those areas which need to be sorted out and I am hopeful that we can address them by code freeze. Raghavendra - please fill in here if you have more context on these issues. Thanks, Vijay ___ Gluster-devel mailing list Gluster-devel@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] 3.6 Feature Freeze - move to mid next week?
> There is an improved implementation of trash in gerrit and can help get > more traction with more reviews, rebases etc. I see nine patches for this, all failing verification and all but one inactive since March 10. Given our review rate, is this likely to converge in only a week? > >* RDMA Improvements > > No patches, feature page says work in progress. > > Don't think there are any major pieces missing to get rdma functional. > More testing and bug fixes should be mostly it. Can happen in the > interval between feature freeze and code freeze. The feature page specifically mentions co-existence with TCP, and performance. I'm guessing those are addressed by 149, and possibly by 4378. Is that correct? ___ Gluster-devel mailing list Gluster-devel@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] 3.6 Feature Freeze - move to mid next week?
On 07/04/2014 08:44 PM, Jeff Darcy wrote: Given the holiday weekend in US, I feel that it would be appropriate to move the 3.6 feature freeze date to mid next week so that we can have more reviews done & address review comments too. We can still continue to track other milestones as per our release schedule [1]. What do you folks think? I think the answer depends on what we can expect to change between now and then. Since the gluster.org feature page never got updated to reflect the real feature set for 3.6, I took the list from email sent after the planning meeting. * Better SSL Two out of three patches merged, one still in review. * Data Classification Design barely begun. * Heterogeneous Bricks Patch has CR+1 V+1 but still stalled in review. * Trash Ancient one is still there, probably doesn't even work. There is an improved implementation of trash in gerrit and can help get more traction with more reviews, rebases etc. * Disperse Patches still in very active review. * Persistent AFR Changelog Xattributes Patches merged. * Better Peer Identification Patch still in review (fails verification). * Gluster Volume Snapshot Tons of patches merged, tons more still to come. * AFRv2 Jammed in long ago. * Policy Based Split-Brain Resolver (PBSBR) No patches, feature page still says in design. * RDMA Improvements No patches, feature page says work in progress. Don't think there are any major pieces missing to get rdma functional. More testing and bug fixes should be mostly it. Can happen in the interval between feature freeze and code freeze. * Server-side Barrier Feature Patches merged. Update on a few other nice to have features that have either made the cut or can become available with some effort: * glusterd volume locks - already in * better logging - framework & few xlators have adopted this * Exports Netgroups authentication - Needs some review attention and rebases * Gluster user serviceable snapshots - feature already in * rest-api - Early implementation available, need some more reviews * Object Count & Archipelago - have some code, need a little more effort to make it available. That leaves us with a very short list of items that are likely to change state. * Better SSL * Heterogeneous Bricks * Disperse * Better Peer Identification Of those, I think only disperse is likely to benefit from an extension. The others just need people to step up and finish reviewing them, which could happen today if there were sufficient will. The real question is what to do about disperse. Some might argue that it's already complete enough to go in, so long as its limitations are documented appropriately. Others might argue that it's still months away from being usable (especially wrt performance). In a way it doesn't matter, because either way a few days won't make a difference. We just need to make a collective decision based on its current state (or close to it). If we need to wait a few days before people can come together for that, so be it. My inclination with respect to disperse/ec is to get it into the code base and mature it there (mostly from a performance perspective). Better peer identification, trash and subset of the features in above lists can benefit by a few days extension. So it seems worthwhile for me to push out feature freeze till mid next week. -Vijay ___ Gluster-devel mailing list Gluster-devel@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] 3.6 Feature Freeze - move to mid next week?
- Original Message - > From: "Jeff Darcy" > To: "Vijay Bellur" > Cc: "Gluster Devel" > Sent: Friday, July 4, 2014 10:14:32 AM > Subject: Re: [Gluster-devel] 3.6 Feature Freeze - move to mid next week? > > > Given the holiday weekend in US, I feel that it would be appropriate > > to move the 3.6 feature freeze date to mid next week so that we can > > have more reviews done & address review comments too. We can still > > continue to track other milestones as per our release schedule [1]. > > What do you folks think? > > I think the answer depends on what we can expect to change between now > and then. Since the gluster.org feature page never got updated to > reflect the real feature set for 3.6, I took the list from email sent > after the planning meeting. > > * Better SSL > Two out of three patches merged, one still in review. > > * Data Classification > Design barely begun. > > * Heterogeneous Bricks > Patch has CR+1 V+1 but still stalled in review. > > * Trash > Ancient one is still there, probably doesn't even work. > > * Disperse > Patches still in very active review. > > * Persistent AFR Changelog Xattributes > Patches merged. > > * Better Peer Identification > Patch still in review (fails verification). > > * Gluster Volume Snapshot > Tons of patches merged, tons more still to come. > > * AFRv2 > Jammed in long ago. > > * Policy Based Split-Brain Resolver (PBSBR) > No patches, feature page still says in design. > > * RDMA Improvements > No patches, feature page says work in progress. > > * Server-side Barrier Feature > Patches merged. > > > That leaves us with a very short list of items that are likely to change > state. > > * Better SSL > > * Heterogeneous Bricks > > * Disperse > > * Better Peer Identification > > Of those, I think only disperse is likely to benefit from an extension. > The others just need people to step up and finish reviewing them, which > could happen today if there were sufficient will. The real question is > what to do about disperse. Some might argue that it's already complete > enough to go in, so long as its limitations are documented > appropriately. Others might argue that it's still months away from > being usable (especially wrt performance). In a way it doesn't matter, > because either way a few days won't make a difference. We just need to > make a collective decision based on its current state (or close to it). > If we need to wait a few days before people can come together for that, > so be it. The reliability and performance of the erasure code translator is probably not at a level where we could guarantee the feature is bug free and "ready". However the feature could be added to the gluster code base for people to begin to experiment with, as suggested we would need to document limitations. The idea being the more hands get on the code, the more bugs found, the more suggestions made for improvements, deeper integration, etc. I do not believe the erasure code translator is called "disperse" any longer. > ___ > Gluster-devel mailing list > Gluster-devel@gluster.org > http://supercolony.gluster.org/mailman/listinfo/gluster-devel > ___ Gluster-devel mailing list Gluster-devel@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] 3.6 Feature Freeze - move to mid next week?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2014-07-04 17:14, Jeff Darcy wrote: >> Given the holiday weekend in US, I feel that it would be appropriate >> to move the 3.6 feature freeze date to mid next week so that we can >> have more reviews done & address review comments too. We can still >> continue to track other milestones as per our release schedule [1]. >> What do you folks think? > > I think the answer depends on what we can expect to change between now > and then. Since the gluster.org feature page never got updated to > reflect the real feature set for 3.6, I took the list from email sent > after the planning meeting. > > * Better SSL > Two out of three patches merged, one still in review. > > * Data Classification > Design barely begun. > > * Heterogeneous Bricks > Patch has CR+1 V+1 but still stalled in review. > > * Trash > Ancient one is still there, probably doesn't even work. > > * Disperse > Patches still in very active review. > > * Persistent AFR Changelog Xattributes > Patches merged. > > * Better Peer Identification > Patch still in review (fails verification). > > * Gluster Volume Snapshot > Tons of patches merged, tons more still to come. > > * AFRv2 > Jammed in long ago. > > * Policy Based Split-Brain Resolver (PBSBR) > No patches, feature page still says in design. > > * RDMA Improvements > No patches, feature page says work in progress. > > * Server-side Barrier Feature > Patches merged. > > > That leaves us with a very short list of items that are likely to change > state. > > * Better SSL > > * Heterogeneous Bricks > > * Disperse > > * Better Peer Identification > > Of those, I think only disperse is likely to benefit from an extension. > The others just need people to step up and finish reviewing them, which > could happen today if there were sufficient will. The real question is > what to do about disperse. Some might argue that it's already complete > enough to go in, so long as its limitations are documented > appropriately. Others might argue that it's still months away from > being usable (especially wrt performance). In a way it doesn't matter, > because either way a few days won't make a difference. We just need to > make a collective decision based on its current state (or close to it). > If we need to wait a few days before people can come together for that, > so be it. OK, this probably answered my earlier question, since there is no IPv6 on this list (stated somewhere to depend on 'Better Peer Identification'), i.e. I should stick to 3.5.1 and only apply patches to address my needs and then check what needs to be done when 3.6.0 is out. /Anders - -- Anders Blomdell Email: anders.blomd...@control.lth.se Department of Automatic Control Lund University Phone:+46 46 222 4625 P.O. Box 118 Fax: +46 46 138118 SE-221 00 Lund, Sweden -BEGIN PGP SIGNATURE- Version: GnuPG v1 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJTtsZ3AAoJENZYyvaDG8NcJPMH/j1P/DN4lerQHtxOLjS7b6MM dNw12blXOIioFbGv/Sh7EYQm5A0Db4Hk21ngIYQcrZVgab/rVv6pfqvpV97S74sE A1yzTfJSMtshSter4F4VSV7BZrPHq7+hYKEkTNEu4Ugw7+PcGvjMAhfVmgiVqUT4 xTqSzB3IsOPELXIOrlB6AZbA7037UvWyyhxjilH5IRVW8KB2ButP2baP0zXlXMf6 622mn3CK11mp/VrXHyxBgGXUMWpJQ9r1vLEn4COhqhALQJ+0vW8uayzcYMYWz56m etTJKtGTZtPalrt1XrFq2Ny5o1KsG4GXlRIGwoqIHtn2v71Sserl6CZQRA+AVAo= =/oBv -END PGP SIGNATURE- ___ Gluster-devel mailing list Gluster-devel@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] 3.6 Feature Freeze - move to mid next week?
> Given the holiday weekend in US, I feel that it would be appropriate > to move the 3.6 feature freeze date to mid next week so that we can > have more reviews done & address review comments too. We can still > continue to track other milestones as per our release schedule [1]. > What do you folks think? I think the answer depends on what we can expect to change between now and then. Since the gluster.org feature page never got updated to reflect the real feature set for 3.6, I took the list from email sent after the planning meeting. * Better SSL Two out of three patches merged, one still in review. * Data Classification Design barely begun. * Heterogeneous Bricks Patch has CR+1 V+1 but still stalled in review. * Trash Ancient one is still there, probably doesn't even work. * Disperse Patches still in very active review. * Persistent AFR Changelog Xattributes Patches merged. * Better Peer Identification Patch still in review (fails verification). * Gluster Volume Snapshot Tons of patches merged, tons more still to come. * AFRv2 Jammed in long ago. * Policy Based Split-Brain Resolver (PBSBR) No patches, feature page still says in design. * RDMA Improvements No patches, feature page says work in progress. * Server-side Barrier Feature Patches merged. That leaves us with a very short list of items that are likely to change state. * Better SSL * Heterogeneous Bricks * Disperse * Better Peer Identification Of those, I think only disperse is likely to benefit from an extension. The others just need people to step up and finish reviewing them, which could happen today if there were sufficient will. The real question is what to do about disperse. Some might argue that it's already complete enough to go in, so long as its limitations are documented appropriately. Others might argue that it's still months away from being usable (especially wrt performance). In a way it doesn't matter, because either way a few days won't make a difference. We just need to make a collective decision based on its current state (or close to it). If we need to wait a few days before people can come together for that, so be it. ___ Gluster-devel mailing list Gluster-devel@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] 3.6 Feature Freeze - move to mid next week?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2014-07-04 13:30, Vijay Bellur wrote: > Hi All, > > Given the holiday weekend in US, I feel that it would be appropriate > to move the 3.6 feature freeze date to mid next week so that we can > have more reviews done & address review comments too. We can still > continue to track other milestones as per our release schedule [1]. > What do you folks think? Is 'git://git.gluster.org/glusterfs master' the right thing to clone if I'm interested in testing the IPv6 support (and the possible fixes for my outstanding bugs), or should I cherry-pick appropriate bits and apply to 3.5.1 (I'm not planning to go live until some time in september [or later ;-)]) /Anders - -- Anders Blomdell Email: anders.blomd...@control.lth.se Department of Automatic Control Lund University Phone:+46 46 222 4625 P.O. Box 118 Fax: +46 46 138118 SE-221 00 Lund, Sweden -BEGIN PGP SIGNATURE- Version: GnuPG v1 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJTtrpAAAoJENZYyvaDG8Nct0QH/RpdwqrksBkUpuqNb2X+2aPO xZc4FtpmALNi6lM0sUcmGnMPLC9JptcHjw2edr4izrQheqoaFhfCo9Zbar0b+8Yy JVin11u+q6WrA/aVdH/+MhQ38M9lKBV1SUiIGP2FrEW805NbDNGfxj0q8S1mGmQr zgk8SL+cMcGDW7aNSckPj0P39Fa+lwYX3nI9mrQRAHf1mqP6Apl6zCL/kUmu2xgH hjX1cYEI4FleYl9h0L6FaROt4jThngs4S2be4E8Z8U+GmzuxMiCVaLKf2mZAQmEp ZGUBWRp7vDEvHLWZk5NTtiF5Ty1ntaRcBugS94yt/KJUNzJooIdYibh7BJjtPM4= =xyNm -END PGP SIGNATURE- ___ Gluster-devel mailing list Gluster-devel@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-devel
[Gluster-devel] 3.6 Feature Freeze - move to mid next week?
Hi All, Given the holiday weekend in US, I feel that it would be appropriate to move the 3.6 feature freeze date to mid next week so that we can have more reviews done & address review comments too. We can still continue to track other milestones as per our release schedule [1]. What do you folks think? Cheers, Vijay [1] http://www.gluster.org/community/documentation/index.php/Planning36 ___ Gluster-devel mailing list Gluster-devel@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-devel
