<div dir="ltr"><div>Lots of people at Vault this week!</div><div><br></div><div>Last month's newsletter included a list of all of the Gluster related talks, so if you're here, come by the Red Hat booth and say hi!</div><div><br></div><div><br></div><div>New things:</div><div>3.7.11 Released: <a href="https://www.gluster.org/pipermail/gluster-devel/2016-April/049155.html">https://www.gluster.org/pipermail/gluster-devel/2016-April/049155.html</a></div><div><br></div><div>We've got a new Events (<a href="https://www.gluster.org/events/">https://www.gluster.org/events/</a>) page to replace the publicpad.</div><div>(<a href="https://public.pad.fsfe.org/p/gluster-events">https://public.pad.fsfe.org/p/gluster-events</a>) - Feel free to add a PR updating the markdown page with your event!</div><div><br></div><div>Highlights from this past month's mailing lists:</div><div><br></div><div>++ gluster-users ++</div><div><br></div><div>Taira Hajime announced <a href="https://www.gluster.org/pipermail/gluster-users/2016-April/026193.html">https://www.gluster.org/pipermail/gluster-users/2016-April/026193.html</a> the general availability of Glubix 1.4 with support for Zabbix Server 3.0</div><div><br></div><div>Rajesh suggested using “--mode=script” option in order to enable non interactive use of gluster snapshot delete. More at <a href="https://www.gluster.org/pipermail/gluster-users/2016-April/026178.html">https://www.gluster.org/pipermail/gluster-users/2016-April/026178.html</a></div><div><br></div><div>The 3.7.10 release continued to create conversations <a href="https://www.gluster.org/pipermail/gluster-users/2016-April/026157.html">https://www.gluster.org/pipermail/gluster-users/2016-April/026157.html</a> on the list <a href="https://www.gluster.org/pipermail/gluster-users/2016-April/026164.html">https://www.gluster.org/pipermail/gluster-users/2016-April/026164.html</a></div><div><br></div><div>Raghavendra Talur picked up a conversation thread on GlusterFS on HPC cluster at <a href="https://www.gluster.org/pipermail/gluster-users/2016-March/025595.html">https://www.gluster.org/pipermail/gluster-users/2016-March/025595.html</a> as this has been requested earlier</div><div><br></div><div>++ gluster-devel ++</div><div><br></div><div>Atin discussed <a href="https://www.gluster.org/pipermail/gluster-devel/2016-March/048926.html">https://www.gluster.org/pipermail/gluster-devel/2016-March/048926.html</a> the topic of brick port allocation by GlusterD and proposed a patch which adopts an approach similar to snapd</div><div><br></div><div>With the 3.8 release process being more firm about the need to have well written features pages, there appear to be a subset of features which are now “at risk” <a href="https://www.gluster.org/pipermail/gluster-devel/2016-April/049063.html">https://www.gluster.org/pipermail/gluster-devel/2016-April/049063.html</a> While 30Apr is the date by which this needs to be completed, both Niels and Amye urge feature owners to work on squaring things away.</div><div><br></div><div>Jiffin reminded the feature owners about adding tests to the DiSTAF <a href="https://www.gluster.org/pipermail/gluster-devel/2016-April/049104.html">https://www.gluster.org/pipermail/gluster-devel/2016-April/049104.html</a> With the framework having additional maintainers and more active development <a href="https://www.gluster.org/pipermail/gluster-infra/2016-April/002075.html">https://www.gluster.org/pipermail/gluster-infra/2016-April/002075.html</a> inclusion of test cases by 30Apr is a requirement for consideration of 3.8 release feature completion</div><div><br></div><div>The location of the DiSTAF tests received a fair amount of conversation <a href="https://www.gluster.org/pipermail/gluster-devel/2016-April/049057.html">https://www.gluster.org/pipermail/gluster-devel/2016-April/049057.html</a> intending to ensure that helper libraries and tests are appropriately located to help packaging and wider adoption of the framework itself.</div><div><br></div><div>Karthik Subrahmanya provided an update <a href="https://www.gluster.org/pipermail/gluster-devel/2016-April/049029.html">https://www.gluster.org/pipermail/gluster-devel/2016-April/049029.html</a> on his work on the WORM feature. Along with filing a bug I have filed a bug in RHBZ #1326308 which now blocks the 3.8 release</div><div><br></div><div>Kaushal provided additional context around the 3.7.10 release <a href="https://www.gluster.org/pipermail/gluster-devel/2016-April/049017.html">https://www.gluster.org/pipermail/gluster-devel/2016-April/049017.html</a> mentioning in detail the regression (which was also present in 3.7.9)</div><div><br></div><div>Vijay had asked for additional detail about coherence issues in context of the SELinux client support in GlusterFS design <a href="https://github.com/gluster/glusterfs-specs/blob/master/accepted/SELinux-client-support.md">https://github.com/gluster/glusterfs-specs/blob/master/accepted/SELinux-client-support.md</a> which Manikandan had put up for review. Manikandan explained <a href="https://www.gluster.org/pipermail/gluster-devel/2016-April/049099.html">https://www.gluster.org/pipermail/gluster-devel/2016-April/049099.html</a> that the work continues on invalidating the xattrs through the Upcall Infrastructure which would handle the coherence issues.</div><div><br></div><div><a href="https://github.com/gluster/glusterfs-specs/blob/master/under_review/quota-enhancements.md">https://github.com/gluster/glusterfs-specs/blob/master/under_review/quota-enhancements.md</a> is a design document posted by Manikandan <a href="https://www.gluster.org/pipermail/gluster-devel/2016-April/049077.html">https://www.gluster.org/pipermail/gluster-devel/2016-April/049077.html</a> intended to improve the quota enable/disable processes. A patch is also under review <a href="http://review.gluster.org/#/c/12952/">http://review.gluster.org/#/c/12952/</a></div><div>++ gluster-maintainers ++</div><div><br></div><div>Amye announced <a href="https://www.gluster.org/pipermail/maintainers/2016-March/000520.html">https://www.gluster.org/pipermail/maintainers/2016-March/000520.html</a> that week of 28Mar would have the Jenkins infrastructure moved from iWeb hosting to Red Hat’s data centers. Since this has potential impact on 3.7.10 release, the announcement was intended to seek agreement and make the necessary changes. Michael Scherer reported back <a href="https://www.gluster.org/pipermail/gluster-infra/2016-March/002045.html">https://www.gluster.org/pipermail/gluster-infra/2016-March/002045.html</a> that the migration was completed without hassles</div><div><br></div><div>Niels alerted the maintainers <a href="https://www.gluster.org/pipermail/maintainers/2016-March/000526.html">https://www.gluster.org/pipermail/maintainers/2016-March/000526.html</a> about not merging patches with topic ‘rfc’ in Gerrit. He mentioned that without a bug to track the changes it is difficult to build a query which lists all the changes against the particular feature</div><div><br></div><div>Atin's note <<a href="https://www.gluster.org/pipermail/maintainers/2016-April/000549.html">https://www.gluster.org/pipermail/maintainers/2016-April/000549.html</a>> about a regression around GlusterD failing to restart when volume has snapshots spawned an entire thread to the feasibility of the 3.7.10 release. Subsequently, a decision was arrived at to work towards a 3.7.11 addresses this topic. More at <<a href="https://www.gluster.org/pipermail/maintainers/2016-April/000589.html">https://www.gluster.org/pipermail/maintainers/2016-April/000589.html</a>></div><div><br></div><div>Small kerfuffle around a recent change which caused failures to build artifacts was discussed at <a href="https://www.gluster.org/pipermail/maintainers/2016-April/000562.html">https://www.gluster.org/pipermail/maintainers/2016-April/000562.html</a> the issue arose from the failures being not reported back to gerrit. Since the report, it has been addressed and things are back to normal</div><div><br></div><div>The 3.7 release has not been without drama. Kaushal reported another set of regressions, this time with management encryption enabled, daemons such as NFS etc would not start. More at <a href="https://www.gluster.org/pipermail/maintainers/2016-April/000604.html">https://www.gluster.org/pipermail/maintainers/2016-April/000604.html</a> and this is where the 3.7.11 release dates received some amount of serious consideration and planning</div><div><br></div><div>Pranith’s intent to include the multi-threaded self-heal patch in a 3.7.12 release <a href="https://www.gluster.org/pipermail/maintainers/2016-April/000628.html">https://www.gluster.org/pipermail/maintainers/2016-April/000628.html</a> received a good amount of discussion with Niels highlighting the concern around back-porting this to a 3.7 release because potential undiscovered issues are something which is expected for new features and thus contain a risk.</div><div><br></div><div>Gluster Top 5 Contributors in the last 30 days:</div><div><br></div><div>Niels de Vos, Vijaykumar M , Pranith Kumar K, Atin Mukherjee, Sakshi Bansal </div><div><br></div><div>Upcoming CFPs:</div><div><br></div><div>LISA:(<a href="https://www.usenix.org/conference/lisa16/call-for-participation">https://www.usenix.org/conference/lisa16/call-for-participation</a>) April 25th</div><div>LinuxCon North America: (<a href="http://events.linuxfoundation.org/events/linuxcon-north-america/program/cfp">http://events.linuxfoundation.org/events/linuxcon-north-america/program/cfp</a>) April 26th</div><div>LinuxCon Japan: (<a href="http://events.linuxfoundation.org/events/linuxcon-japan/program/cfp">http://events.linuxfoundation.org/events/linuxcon-japan/program/cfp</a>) May 6</div><div>LinuxCon Europe (<a href="http://events.linuxfoundation.org/events/linuxcon-europe/program/cfp">http://events.linuxfoundation.org/events/linuxcon-europe/program/cfp</a>): June 17</div><div><br></div><div><br></div>-- <br><div class="gmail_signature"><div dir="ltr">Amye Scavarda | <a href="mailto:amye@redhat.com" target="_blank">amye@redhat.com</a> | Gluster Community Lead</div></div>
</div>