Proposing efforts of adding metrics to various perf xlators. Following are links to github issues:
https://github.com/gluster/glusterfs/issues/422
https://github.com/gluster/glusterfs/issues/423
https://github.com/gluster/glusterfs/issues/424
https://github.com/gluster/glusterfs/issues/425
https://github.com/gluster/glusterfs/issues/426
https://github.com/gluster/glusterfs/issues/427
https://github.com/gluster/glusterfs/issues/428
https://github.com/gluster/glusterfs/issues/429
regards,https://github.com/gluster/glusterfs/issues/422
https://github.com/gluster/glusterfs/issues/423
https://github.com/gluster/glusterfs/issues/424
https://github.com/gluster/glusterfs/issues/425
https://github.com/gluster/glusterfs/issues/426
https://github.com/gluster/glusterfs/issues/427
https://github.com/gluster/glusterfs/issues/428
https://github.com/gluster/glusterfs/issues/429
On Wed, Mar 21, 2018 at 10:29 AM, Jiffin Tony Thottan <jthottan@xxxxxxxxxx> wrote:
Hi,
I would like to (rep)propose lease support https://github.com/gluster/glusterfs/issues/350
Current status
Following patches posted :
https://review.gluster.org/#/c/19568/ -- gfapi recall lease
https://review.gluster.org/#/c/12496/ -- test case
https://review.gluster.org/#/c/11721/ -- add lease fop for afr
need to sent a patch for adding lease fop in ec
+ I have patch for bug fixes in current lease implementation
Regards,
Jiffin
On Tuesday 13 March 2018 07: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.
Thanks,
Shyam
P.S: Also any volunteers to shadow/participate/run 4.1 as a release owner?
_______________________________________________ Gluster-devel mailing list
Gluster-devel@xxxxxxxxxxx
http://lists.gluster.org/mailman/listinfo/gluster-devel
_______________________________________________
maintainers mailing list
maintainers@xxxxxxxxxxx
http://lists.gluster.org/mailman/listinfo/maintainers
_______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx http://lists.gluster.org/mailman/listinfo/gluster-devel