Re: Release 3.12: Readiness for release (request attention)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 





On Tue, Aug 29, 2017 at 3:03 AM, Shyam Ranganathan <srangana@xxxxxxxxxx> wrote:
On 08/25/2017 04:48 PM, Shyam Ranganathan wrote:
Hi,

Here is a status of 3.12 from a release readiness perspective.

Most importantly, if there are any known blockers for the release, please shout out ASAP. Final release tagging would be slated (around) 30th Aug, 2017

1) YELLOW: Release notes are in, but need a review by feature owners (and others based on interest). 

See [1] for release notes, and if there are edits submit the same for review, using the issue # for the feature as the github issue reference, or the release tracker bug as the BUG ID [2].

Calling out again, to review the release notes.


Where to i submit changes?

My review is here:

For Subdir:

Limitations:
There are no throttling or QoS support for this feature. The feature will just provide the namespace isolation for the different clients.
Known Issues:
Once we cross more than 1000s of subdirs in 'auth.allow' option, the performance of reconnect / authentication would be impacted.

For statfs():

Limitations:
TBD
Known Issues:
TBD

Remove these 2 lines in section! This is not an exposed option for user for now, and also we don't have any known limitations as of now.



2) YELLOW: Glusto status: Better than master! see [3]. If we get more runs in, then we can decide if there are blockers or not, this is not a release gating run yet.

Post the fix to the issue found in [3] glusto tests went further and have failed elsewhere. The run details are here: https://ci.centos.org/view/Gluster/job/gluster_glusto/377/console


6) RED: Upgrade from 3.8 and 3.10 to 3.12 as stated in the (older) upgrade guides [6]

Tested the upgrade from 3.10.5 to 3.12 RC0, and we are good here. This task is done.


- Are there any new upgrade related issues (geo-rep, snapshots, anything to consider)? Would like maintainers attention on this if there are any further things to call-out

- Any help here is appreciated! This is not at risk, as I should be able to complete the same, but help is appreciated.

7) RED: At least get in a couple of gbench [7] (Gluster bench marking runs) in for replicated and dispersed volumes (action on me)

Still pending


Shyam

[1] Release notes: https://github.com/gluster/glusterfs/blob/release-3.12/doc/release-notes/3.12.0.md

[2] Release tracker: https://bugzilla.redhat.com/show_bug.cgi?id=glusterfs-3.12.0

[3] glusto 3.12 status: http://lists.gluster.org/pipermail/gluster-devel/2017-August/053529.html

[4] fstat status since branching: https://fstat.gluster.org/summary?start_date=2017-07-20&end_date=2017-08-26&branch=release-3.12

[5] 3.12 gerrit dashboard: https://review.gluster.org/#/projects/glusterfs,dashboards/dashboard:3-12-dashboard

[6] Older upgrade guide: https://gluster.readthedocs.io/en/latest/Upgrade-Guide/upgrade_to_3.10/

[7] gbench test: https://github.com/gluster/gbench/blob/master/bench-tests/bt-0000-0001/GlusterBench.py

"Releases are made better together"

--
Amar Tumballi (amarts)
_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxxx
http://lists.gluster.org/mailman/listinfo/gluster-devel

[Index of Archives]     [Gluster Users]     [Ceph Users]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux