Re: [Gluster-devel] [Gluster-Maintainers] Release 3.12: Status of features (Require responses!)

[Shyam Ranganathan]

On 07/23/2017 01:01 PM, Amar Tumballi wrote:

Responses inline.

On Sat, Jul 22, 2017 at 1:36 AM, Shyam > wrote:




- posix: provide option to handle 'statfs()' properly when more than
1 brick is exported from 1 node
   - https://github.com/gluster/glusterfs/issues/241

   - @amarts patch is still awaiting reviews, should this be tracked
as an exception?

Please consider it as an required bug fix. (This needn't have a release 
note mention in features, but needs a mention in bugs section).


Ok, done. Should we close the github issue and open a bug report instead?



Also if I get the feature completed /reviewed this week in master, can 
we get in fuse subdir mount  [11] patches backported? This will be by 
default not available, and hence shouldn't be an issue IMO. More on it 
is discussed in mailing-list [12]


Ok, added to the 3.12 scope, against exceptions for backports.




- Provide support for clearing translator specific inode contex /
forgetting inode (for supportability)
   - https://github.com/gluster/glusterfs/issues/249


Push out to 4.0


Already done.




- rpc-clnt reconnect timer
   - https://github.com/gluster/glusterfs/issues/152


Can be pushed to 4.0


Already done.



- bug: read-only xlator doesn't implement fallocate
   - https://github.com/gluster/glusterfs/issues/187


Can we treat it as bug and take in a backport sometime before RC1?


Ok done. We possibly need to settle on bug vs issue on this as well (as 
the one above).





Thanking in advance for all the responses, so help cleanup and chase
the right reviews and features for the release.

Shyam & Jiffin

Thanks for all the great work in summarising the tasks.

[11] - https://github.com/gluster/glusterfs/issues/175
[12] - 
http://lists.gluster.org/pipermail/gluster-devel/2017-July/053359.html


[1] Review focus:
https://review.gluster.org/#/q/starredby:srangana%2540redhat.com




--
Amar Tumballi (amarts)

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

Re: [Gluster-devel] [Gluster-Maintainers] Release 3.12: Status of features (Require responses!)

[Shyam Ranganathan]

On 07/25/2017 02:56 AM, Amar Tumballi wrote:



Further changes:
   - No new milestone assigned, IOW not moved to 4.0 by default,
hence contributors working on these features would need to rekindle
conversations on including the same in 4.0 on the ML or on the issue
itself.


I would like us to push the changes for 'tiering' which Hari was working 
on as an experimental enhancements (They seem to be feature enhancements 
in glusterd to enable extra options for add-brick and remove-brick). 
Mainly because with glusterfs 4.0 we will have glusterd2, and all those 
efforts would be gone. By the looks of it, most of the patches are not 
causing any regression failures at least.


I would recommend to mark them experimental features of 3.12 branch.

Any feedback? Left to release branch maintainers I guess.


Considering the fact that glusterd2 would be a the way forward in 4.0, 
the patches that you mention are good candidates to get into 3.12, as 
this is possibly the last release where we should be working on glusterd 
related major feature changes.


The patch in question looks to be: https://review.gluster.org/#/c/17693/ 
(experimental) and https://review.gluster.org/#/c/15503/ (in master with 
a merge conflict).


@hari, can you address the patch merge issue on master, and also 
@glusterd team, can we get this reviewed in time?


Are there other patches that are in line for the same?

Shyam


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

Re: [Gluster-devel] [Gluster-Maintainers] Release 3.12: Status of features (Require responses!)

[Shyam Ranganathan]

On 07/24/2017 09:56 PM, Pranith Kumar Karampuri wrote:
On Sat, Jul 22, 2017 at 1:36 AM, Shyam > wrote:


- Implement parallel writes feature on EC volume
   - https://github.com/gluster/glusterfs/issues/251



Looks like it will take one more week after this, what do you suggest?


One more week post the stated RC0 date? (3.12 release branch RC0 on 31st 
July)


If so I would drop this from 3.12 and add this to the queue for 4.0



- Cache last stripe of an EC volume while write is going on
   - https://github.com/gluster/glusterfs/issues/256



Looks like it will take 2 more week after this, what do you suggest?



This one is for 4.0 considering the time it would take to make it to 3.12.

HTH,
Shyam

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

Re: [Gluster-devel] Release 3.12: Status of features (Require responses!)

[Shyam Ranganathan]

On 07/24/2017 06:54 AM, Kotresh Hiremath Ravishankar wrote:

- gfid-path by default
   - https://github.com/gluster/glusterfs/issues/139




Following patches needs to be merged. It would be back ported to 3.12 branch
Once it is merged.

https://review.gluster.org/#/c/17744/ 

https://review.gluster.org/#/c/17785/ 


https://review.gluster.org/#/c/17839/


I just merged the last patch, that had the required review and 
regression scores.


Request the backports as needed to 3.12



And on the part of enabling it by default. I have requested for a 
performance testing.

Once that is done, one more patch to enable it by default.


Thanks, will try to incorporate this into 3.12 performance regression 
testing that I may do.


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

Re: [Gluster-devel] [Gluster-Maintainers] Release 3.12: Status of features (Require responses!)

[Shyam Ranganathan]

On 07/24/2017 03:56 AM, Niels de Vos wrote:

- Decide what to do with glfs_ipc() in libgfapi
   -https://github.com/gluster/glusterfs/issues/269
   - @nixpanic I assume there is more than just test case disabling for this,
is this expected to happen by 3.12?

https://review.gluster.org/17854  has been posted against the master
branch. Once it is merged, it should be backported to the release-3.12
branch. This also makes it unnecessary to revert/fixup the glfs_ipc()
function that has symbol version 4.0.


Merged the backport as well. This is done, thanks.

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

[Gluster-devel] Coverity covscan for 2017-07-28-b5fa5ae0 (master branch)

[staticanalysis]

GlusterFS Coverity covscan results are available from
http://download.gluster.org/pub/gluster/glusterfs/static-analysis/master/glusterfs-coverity/2017-07-28-b5fa5ae0
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-devel