<div dir="ltr"><h2 class="gmail-part" id="gmail-meeting-date-09202017-sept-20th" style="box-sizing:border-box;font-family:-apple-system,BlinkMacSystemFont,"Segoe UI",Roboto,"Helvetica Neue",Helvetica,Arial,sans-serif,"Apple Color Emoji","Segoe UI Emoji","Segoe UI Symbol";line-height:1.25;color:rgb(51,51,51);margin-top:24px;margin-bottom:16px;padding-bottom:0.3em;border-bottom:1px solid rgb(238,238,238);letter-spacing:0.35px">Meeting date: 09/20/2017 (Sept 20th)</h2><h3 class="gmail-part" id="gmail-bj-link" style="box-sizing:border-box;font-family:-apple-system,BlinkMacSystemFont,"Segoe UI",Roboto,"Helvetica Neue",Helvetica,Arial,sans-serif,"Apple Color Emoji","Segoe UI Emoji","Segoe UI Symbol";line-height:1.25;color:rgb(51,51,51);margin-top:24px;margin-bottom:16px;font-size:1.25em;letter-spacing:0.35px"><a class="gmail-anchor gmail-hidden-xs" href="https://hackmd.io/MYTgzADARgplCGBaA7DArMxAWAZvATIiFhJgCYarBQCMCYIQA===?both#bj-link" title="bj-link" style="box-sizing:border-box;background-color:transparent;color:rgb(51,122,183);text-decoration-line:none;float:left;padding-right:4px;line-height:1"><span class="gmail-octicon gmail-octicon-link" style="box-sizing:border-box;font-weight:normal;font-stretch:normal;font-size:16px;line-height:1;font-family:octicons;display:inline-block;color:rgb(0,0,0);vertical-align:middle"></span></a>BJ Link</h3><ul class="gmail-part" style="box-sizing:border-box;margin-top:0px;margin-bottom:16px;padding-left:2em;color:rgb(51,51,51);font-family:-apple-system,BlinkMacSystemFont,"Segoe UI",Roboto,"Helvetica Neue",Helvetica,Arial,sans-serif,"Apple Color Emoji","Segoe UI Emoji","Segoe UI Symbol";font-size:16px;letter-spacing:0.35px"><li class="gmail-" style="box-sizing:border-box">Bridge: <a href="https://bluejeans.com/205933580" target="_blank" style="box-sizing:border-box;background-color:transparent;color:rgb(51,122,183);text-decoration-line:none">https://bluejeans.com/205933580</a></li><li class="gmail-" style="box-sizing:border-box;margin-top:0.25em">Download/Watch : <a href="https://bluejeans.com/s/mgtCo" target="_blank" style="box-sizing:border-box;background-color:transparent;color:rgb(51,122,183);text-decoration-line:none">https://bluejeans.com/s/mgtCo</a></li></ul><h3 class="gmail-part" id="gmail-attendance" style="box-sizing:border-box;font-family:-apple-system,BlinkMacSystemFont,"Segoe UI",Roboto,"Helvetica Neue",Helvetica,Arial,sans-serif,"Apple Color Emoji","Segoe UI Emoji","Segoe UI Symbol";line-height:1.25;color:rgb(51,51,51);margin-top:24px;margin-bottom:16px;font-size:1.25em;letter-spacing:0.35px"><a class="gmail-anchor gmail-hidden-xs" href="https://hackmd.io/MYTgzADARgplCGBaA7DArMxAWAZvATIiFhJgCYarBQCMCYIQA===?both#attendance" title="attendance" style="box-sizing:border-box;background-color:transparent;color:rgb(51,122,183);text-decoration-line:none;float:left;padding-right:4px;line-height:1"><span class="gmail-octicon gmail-octicon-link" style="box-sizing:border-box;font-weight:normal;font-stretch:normal;font-size:16px;line-height:1;font-family:octicons;display:inline-block;color:rgb(0,0,0);vertical-align:middle"></span></a>Attendance</h3><ul class="gmail-part" style="box-sizing:border-box;margin-top:0px;margin-bottom:16px;padding-left:2em;color:rgb(51,51,51);font-family:-apple-system,BlinkMacSystemFont,"Segoe UI",Roboto,"Helvetica Neue",Helvetica,Arial,sans-serif,"Apple Color Emoji","Segoe UI Emoji","Segoe UI Symbol";font-size:16px;letter-spacing:0.35px"><li class="gmail-" style="box-sizing:border-box">[Sorry Note] mscherer, kshlm, atinm, amye</li><li class="gmail-" style="box-sizing:border-box;margin-top:0.25em">Amar, Rafi, Nigel, Milind, Nithya, Kaleb, Shyam, Xavi, Ravi, raghug, vbellur, Kotresh</li></ul><h3 class="gmail-part" id="gmail-agenda" style="box-sizing:border-box;font-family:-apple-system,BlinkMacSystemFont,"Segoe UI",Roboto,"Helvetica Neue",Helvetica,Arial,sans-serif,"Apple Color Emoji","Segoe UI Emoji","Segoe UI Symbol";line-height:1.25;color:rgb(51,51,51);margin-top:24px;margin-bottom:16px;font-size:1.25em;letter-spacing:0.35px"><a class="gmail-anchor gmail-hidden-xs" href="https://hackmd.io/MYTgzADARgplCGBaA7DArMxAWAZvATIiFhJgCYarBQCMCYIQA===?both#agenda" title="agenda" style="box-sizing:border-box;background-color:transparent;color:rgb(51,122,183);text-decoration-line:none;float:left;padding-right:4px;line-height:1"><span class="gmail-octicon gmail-octicon-link" style="box-sizing:border-box;font-weight:normal;font-stretch:normal;font-size:16px;line-height:1;font-family:octicons;display:inline-block;color:rgb(0,0,0);vertical-align:middle"></span></a>Agenda</h3><ul class="gmail-part" style="box-sizing:border-box;margin-top:0px;margin-bottom:16px;padding-left:2em;color:rgb(51,51,51);font-family:-apple-system,BlinkMacSystemFont,"Segoe UI",Roboto,"Helvetica Neue",Helvetica,Arial,sans-serif,"Apple Color Emoji","Segoe UI Emoji","Segoe UI Symbol";font-size:16px;letter-spacing:0.35px"><li class="gmail-" style="box-sizing:border-box"><p style="box-sizing:border-box;margin:16px 0px">AI from previous week</p><ul style="box-sizing:border-box;margin-top:0px;margin-bottom:0px;padding-left:2em"><li class="gmail-" style="box-sizing:border-box">[Nigel] Changes to ‘Submit Type’ - <span style="box-sizing:border-box;font-weight:700">DONE on 2017-09-20 02:20 UTC</span></li><li class="gmail-" style="box-sizing:border-box;margin-top:0.25em">[Amye] Email sent out with hotel information around Gluster Summit, if you didn’t get it, ping me or ask around. – amye</li></ul></li><li class="gmail-" style="box-sizing:border-box;margin-top:0.25em"><p style="box-sizing:border-box;margin:16px 0px">Note: Archive old meeting notes to wiki so the hackmd is lighter.</p><ul style="box-sizing:border-box;margin-top:0px;margin-bottom:0px;padding-left:2em"><li class="gmail-" style="box-sizing:border-box">[Amar] Can we archive it in our website somewhere, so we know where to search for old meeting minutes?</li></ul></li><li class="gmail-" style="box-sizing:border-box;margin-top:0.25em"><p style="box-sizing:border-box;margin:16px 0px">What are we doing with regression failure emails? (netbsd/netbsd-brick-mux?)</p><ul style="box-sizing:border-box;margin-top:0px;margin-bottom:0px;padding-left:2em"><li class="gmail-" style="box-sizing:border-box">You should all be getting emails from failures onto maintainers@</li></ul><ul style="box-sizing:border-box;margin-top:0px;margin-bottom:0px;padding-left:2em"><li class="gmail-" style="box-sizing:border-box">[Atin] brick mux regression was on centos. volume status clients command is broken. Root cause availble. We have reverted the new test introduced in volume-status.t. regression is back to normal.</li><li class="gmail-" style="box-sizing:border-box;margin-top:0.25em">[Atin] netbsd regression multiple test failures. Please look into it if it falls into your components.<ul style="box-sizing:border-box;margin-top:0px;margin-bottom:0px;padding-left:2em"><li class="gmail-" style="box-sizing:border-box">tests/basic/distribute/rebal-all-nodes-migrate.t</li><li class="gmail-" style="box-sizing:border-box;margin-top:0.25em">tests/features/delay-gen.t</li><li class="gmail-" style="box-sizing:border-box;margin-top:0.25em">tests/bitrot/bug-1373520.t (generated core)</li></ul></li><li class="gmail-" style="box-sizing:border-box;margin-top:0.25em">Let’s have a rotating group of people who look at failures.<ul style="box-sizing:border-box;margin-top:0px;margin-bottom:0px;padding-left:2em"><li class="gmail-" style="box-sizing:border-box">[shyam] Do they look at only releases or master? Preferably only release branches, because master is overwhelming.</li><li class="gmail-" style="box-sizing:border-box;margin-top:0.25em">[nigel] We should probably have one person look at all the branches and especially master. A lot of our test runs are triggered periodically against master. This person’s job would be chase down the failures, find the right component, and get the fix pushed as soon as possible for centos-regression, netbsd-regression, regression with multiplex, and glusto tests.</li></ul></li></ul></li><li class="gmail-" style="box-sizing:border-box;margin-top:0.25em"><p style="box-sizing:border-box;margin:16px 0px">Release roadmap</p><ul style="box-sizing:border-box;margin-top:0px;margin-bottom:0px;padding-left:2em"><li class="gmail-" style="box-sizing:border-box">Clarifications on <a href="https://www.gluster.org/release-schedule/" target="_blank" style="box-sizing:border-box;background-color:transparent;color:rgb(51,122,183);text-decoration-line:none">3.13 (STM), 4.0 (STM), 4.1 (LTM)</a><ul style="box-sizing:border-box;margin-top:0px;margin-bottom:0px;padding-left:2em"><li class="gmail-" style="box-sizing:border-box">Current calendar is 2 months between 3.13 and 4.0.</li><li class="gmail-" style="box-sizing:border-box;margin-top:0.25em">[Amar] No features for 3.13 proposed yet. Nothing proposed yet</li><li class="gmail-" style="box-sizing:border-box;margin-top:0.25em">[Shyam] 3.13 may be a sneak peak into 4.0 as features for 4.0 land at the time of branching.</li><li class="gmail-" style="box-sizing:border-box;margin-top:0.25em">We should plan to take in Gfproxy into 3.13. If we can get it in early, we can stabilize messaging around Gfproxy. Poornima’s latest patch passes regression.</li><li class="gmail-" style="box-sizing:border-box;margin-top:0.25em">Poornima has updated github issue with latest status.</li><li class="gmail-" style="box-sizing:border-box;margin-top:0.25em">Amar is considering error codes for 3.13 since there’s 2 months as well. At least an early version given nothing changes from user point of view. Not committing given large code change and review effort.</li><li class="gmail-" style="box-sizing:border-box;margin-top:0.25em">Rafi: Halo can be taken in. Amar: Halo is already in. Rafi: Looking at the patches that FB has in their branch specific to Halo replication. This is already in and can be highlighted as a feature to 3.13. (Already landed in 3.11).</li><li class="gmail-" style="box-sizing:border-box;margin-top:0.25em">Kotresh: Also useful to have a use-case defined for Halo replication vs geo-replication. Vijay: When Halo is available, we will need to update our documentation for different types of replications we provide.</li><li class="gmail-" style="box-sizing:border-box;margin-top:0.25em">4.0 is slated for January 2018. Early Jan but worst case late Jan. Features are already planned. We have to discuss how to get them in early and what support those developers will need. During the summit, we need to do an off-hand check with maintainers about what they need. Possibly Thursday night?</li></ul></li><li class="gmail-" style="box-sizing:border-box;margin-top:0.25em">Expectations from maintainers:<ul style="box-sizing:border-box;margin-top:0px;margin-bottom:0px;padding-left:2em"><li class="gmail-" style="box-sizing:border-box"><span style="box-sizing:border-box;font-weight:700">Scope clarity</span>: 4.0 milestone on Gihub has 50 features listed. When you mark an issue for 4.0 milestone, send an email with link to issue. There’s 50-ish features. We’re 5 months away from the release. Can we ship them all? Would be nice for maintainers to look at their components to see what can happen. If we can’t ship them, then please remove them from the milestone, so we’re clear what can make it.</li><li class="gmail-" style="box-sizing:border-box;margin-top:0.25em"><span style="box-sizing:border-box;font-weight:700">Status of features</span>: Good to have status update on big features so we know what’s going on.</li><li class="gmail-" style="box-sizing:border-box;margin-top:0.25em"><span style="box-sizing:border-box;font-weight:700">What help do you/others need</span>: As we get nearer to the release, Shyam picks reviews that are connected to major features and chase down reviews for it. Please help with this process and if you’re being chased, help with prioritizing reviews as well.</li></ul></li></ul></li><li class="gmail-" style="box-sizing:border-box;margin-top:0.25em"><p style="box-sizing:border-box;margin:16px 0px">Improving Quality of releases</p><ul style="box-sizing:border-box;margin-top:0px;margin-bottom:0px;padding-left:2em"><li class="gmail-" style="box-sizing:border-box"><span style="box-sizing:border-box;font-weight:700">Baseline and do better on coverage reports</span>: As we add more code, we want our coverage to improve. We’d like maintainers to look at their component and improve their coverage. Or at the very least not decrease coverage. We want to target this for 4.0. As pre-requisite for release.</li><li class="gmail-" style="box-sizing:border-box;margin-top:0.25em"><span style="box-sizing:border-box;font-weight:700">Same as above for <a href="https://download.gluster.org/pub/gluster/glusterfs/static-analysis/master/glusterfs-coverity/" target="_blank" style="box-sizing:border-box;background-color:transparent;color:rgb(51,122,183);text-decoration-line:none">coverity</a></span>: Let’s set baseline and bring down the number of issues. We have 848 coverity failures at the moment, how do we set targets to bring it down. We need to set baselines at release time and assign ownership for components which need to improve. Release team will send out reminders about this focus and provide call outs as a release gate.</li><li class="gmail-" style="box-sizing:border-box;margin-top:0.25em"><span style="box-sizing:border-box;font-weight:700">New features, plan to address regression tests and coverage are needed</span>: We’re adding a bunch of new features. We cannot have tests as hindsight. When these features land, we need healthy test coverage. We should <em style="box-sizing:border-box">plan</em> for higher coverage of new features as they land and at least before branching.</li></ul></li><li class="gmail-" style="box-sizing:border-box;margin-top:0.25em"><p style="box-sizing:border-box;margin:16px 0px">Additional release owners for 3.13 and 4.0</p><ul style="box-sizing:border-box;margin-top:0px;margin-bottom:0px;padding-left:2em"><li class="gmail-" style="box-sizing:border-box">[Amar] Can help in follow ups</li><li class="gmail-" style="box-sizing:border-box;margin-top:0.25em">Anyone interested can contact Shyam</li></ul></li><li class="gmail-" style="box-sizing:border-box;margin-top:0.25em"><p style="box-sizing:border-box;margin:16px 0px">How are we tracking changes in 3.8-fb branch? Should maintainers see whats useful? or should we followup with FB on when it would be sent to ‘master’?</p><ul style="box-sizing:border-box;margin-top:0px;margin-bottom:0px;padding-left:2em"><li class="gmail-" style="box-sizing:border-box">[Ravi] What is facebook’s stragety for contributing patches to master?</li><li class="gmail-" style="box-sizing:border-box;margin-top:0.25em">FB has completed upstreaming it’s patches to release-3.8-fb. About 98%. They’re keep to get these patches into master. Since they’re not keen to carry these patches in their fork. They intend to do an accelerated forward port to master around December. At this point, we will maintainers to review their patches and accepting.</li><li class="gmail-" style="box-sizing:border-box;margin-top:0.25em">Around 3.10 we called this out, there are patches in 3-8-fb branch. If you could monitor it and port patches into master, that would be good. These are fixes that would be good to have for us too. Retain the change-Id so that we track that the patches are ported.</li><li class="gmail-" style="box-sizing:border-box;margin-top:0.25em">If the fix is the same, but we take a different approach, what do we do? Like every project, let’s do the change and invite them to comment. Some of the Halo fixes, the patch description doesn’t help understand what it’s trying to fix. Email/add them to patches. If they don’t respond, we’ll talk to FB during the fortnightly sync ups.</li><li class="gmail-" style="box-sizing:border-box;margin-top:0.25em">4.0 branching is around early December. We will be busy around the same time. FB only has time around early December, we cannot change that.</li></ul></li><li class="gmail-" style="box-sizing:border-box;margin-top:0.25em"><p style="box-sizing:border-box;margin:16px 0px">Gluster 4.0</p><ul style="box-sizing:border-box;margin-top:0px;margin-bottom:0px;padding-left:2em"><li class="gmail-" style="box-sizing:border-box">GD2 -<ul style="box-sizing:border-box;margin-top:0px;margin-bottom:0px;padding-left:2em"><li class="gmail-" style="box-sizing:border-box">Need maintainers to help with options changes.</li><li class="gmail-" style="box-sizing:border-box;margin-top:0.25em">Currently you can create a volume, start a volume and mount a client in glusterd.</li><li class="gmail-" style="box-sizing:border-box;margin-top:0.25em">The framework for making it generic with volumegen and volumeset isn’t complete yet. That will land later this month. That’s where they need maintainer help. GlusterD will not maintain it’s own options table. All translators which provide options need change with new flags and default values.</li><li class="gmail-" style="box-sizing:border-box;margin-top:0.25em">After volumegen patch gets in, we’ll move to georep and other plugins. Aravinda has send a patch to change the way georep configs are written. Working towards getting snapshot and quota team to talk to glusterd2 team so they can have plans for these changes.</li></ul></li><li class="gmail-" style="box-sizing:border-box;margin-top:0.25em">Protocol changes.<ul style="box-sizing:border-box;margin-top:0px;margin-bottom:0px;padding-left:2em"><li class="gmail-" style="box-sizing:border-box">[Amar] From this month onwards, few members of team will spend at least one day on Gluster 4.0 activities per week, in the BLR office.</li><li class="gmail-" style="box-sizing:border-box;margin-top:0.25em">Mostly working on protocol changes next week.</li></ul></li><li class="gmail-" style="box-sizing:border-box;margin-top:0.25em">Monitoring<ul style="box-sizing:border-box;margin-top:0px;margin-bottom:0px;padding-left:2em"><li class="gmail-" style="box-sizing:border-box">initial patches sent for review</li><li class="gmail-" style="box-sizing:border-box;margin-top:0.25em">Will be broken into multiple patches, will need help.</li></ul></li><li class="gmail-" style="box-sizing:border-box;margin-top:0.25em">GFProxy -<ul style="box-sizing:border-box;margin-top:0px;margin-bottom:0px;padding-left:2em"><li class="gmail-" style="box-sizing:border-box">updated status available at <a href="https://github.com/gluster/glusterfs/issues/242" target="_blank" style="box-sizing:border-box;background-color:transparent;color:rgb(51,122,183);text-decoration-line:none">https://github.com/gluster/glusterfs/issues/242</a></li></ul></li><li class="gmail-" style="box-sizing:border-box;margin-top:0.25em">Error codes -<ul style="box-sizing:border-box;margin-top:0px;margin-bottom:0px;padding-left:2em"><li class="gmail-" style="box-sizing:border-box">Initial changes are in, needs a lot of reviews<ul style="box-sizing:border-box;margin-top:0px;margin-bottom:0px;padding-left:2em"><li class="gmail-" style="box-sizing:border-box"><a href="https://github.com/gluster/glusterfs/issues/280" target="_blank" style="box-sizing:border-box;background-color:transparent;color:rgb(51,122,183);text-decoration-line:none">https://github.com/gluster/glusterfs/issues/280</a></li></ul></li><li class="gmail-" style="box-sizing:border-box;margin-top:0.25em">Part of hackathon at Bangalore for later weeks.</li></ul></li><li class="gmail-" style="box-sizing:border-box;margin-top:0.25em">RIO<ul style="box-sizing:border-box;margin-top:0px;margin-bottom:0px;padding-left:2em"><li class="gmail-" style="box-sizing:border-box">[Shyam] Update mail in progress, should hit the lists by this week</li></ul></li></ul></li><li class="gmail-" style="box-sizing:border-box;margin-top:0.25em"><p style="box-sizing:border-box;margin:16px 0px">Round Table</p><ul style="box-sizing:border-box;margin-top:0px;margin-bottom:0px;padding-left:2em"><li class="gmail-" style="box-sizing:border-box">[Nithya] Upstream gluster documentation work, need help from all<ul style="box-sizing:border-box;margin-top:0px;margin-bottom:0px;padding-left:2em"><li class="gmail-" style="box-sizing:border-box">[Vijay / Shyam / Amar] Very critical, please extend help.</li></ul></li><li class="gmail-" style="box-sizing:border-box;margin-top:0.25em">[Shyam] Release retrospective for 3.12, please do talk about things that can be improved</li><li class="gmail-" style="box-sizing:border-box;margin-top:0.25em">[Vijay] Welcome Xavier as full time Gluster contributor. Glad to have you onboard in Red Hat Gluster team.</li><li class="gmail-" style="box-sizing:border-box;margin-top:0.25em">[Vijay] FOSDEM, DevConf discussion are on, will hear more in the future on this</li></ul></li></ul><div><br></div>-- <br><div class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div>Amar Tumballi (amarts)<br></div></div></div></div></div>
</div>