Community Meeting 2017 02 01

Gluster Community Meeting

• Date : 2017-02-01
• Host : kshlm
• Logs :
  • Minutes: https://meetbot.fedoraproject.org/gluster-meeting/2017-02-01/community_meeting_2017-02-01.2017-02-01-15.00.html
  • Minutes (text): https://meetbot.fedoraproject.org/gluster-meeting/2017-02-01/community_meeting_2017-02-01.2017-02-01-15.00.txt
  • Log: https://meetbot.fedoraproject.org/gluster-meeting/2017-02-01/community_meeting_2017-02-01.2017-02-01-15.00.log.html

General information

• Location : #gluster-meeting on Freenode (webchat)
• Time :
  • 15:00 UTC
  • or in your local shell/terminal: date -d "15:00 UTC"

NOTE: Instructions for meeting hosts are at the end of this page.

Topics of Discussion

The meeting is an open floor, open for discussion of any topic entered below.

• Policy on reverting patches that are found to cause spurious test failures (jdarcy)
  • One change got merged (driven by downstream pressure), that caused test failures for all future patches, and held up merges
  • Two proposals for addressing such issues
    • Revert said patches
    • Also revoke commit permissions for habitual offenders
  • Reverting bad patches is good.
    • Infra support is required for making this easier
    • jdarcy will reach out to nigelb to make this possible
  • Revoking commit permissions needs to have a much larger discussion only on that
  • JoeJulian suggested a gfapi based test harness for per xlator testing
• 3.10 TODO nag in the community meeting
  • There are a few TODOs that contributors are not responding to, need some urgency here
  • Reviews, release-notes, backport requests, among possibly others
  • Just want to shout out in the meeting on this!
  • Swapping reviews could help
    • But most reviews happen within a component, so reviews generally cannot be swapped
      • We should encourage cross component reviews
  • Contributors need to be educated that doing this is important
    • Most of the discussions in IRC and mailing-lists don't seem to reach contributors
      • Probably due to a lot of noise
    • Maintainers need to take up the responsibility of educating their teams that upstream contribution isn't only submitting patches
  • Immediate actions for 3.10
    • Someone in bangalore will physically call on developers to get stuff done

Next edition's meeting host

• kshlm

Updates

NOTE : Updates will not be discussed during meetings. Any important or noteworthy update will be announced at the end of the meeting

Action Items from the last meeting

• rastar will start a conversation on gluster-devel about 3.10 blocker test bugs. [update] sent today on feb 1st

Releases

GlusterFS 4.0

• Tracker bug : https://bugzilla.redhat.com/showdependencytree.cgi?id=glusterfs-4.0
• Roadmap : https://www.gluster.org/community/roadmap/4.0/
• Updates:
  • GD2
    • https://lists.gluster.org/pipermail/gluster-devel/2017-February/052016.html
    • Volfile fetch supported now

GlusterFS 3.10

• Maintainers : shyam, kkeithley, rtalur
• Next release : 3.10.0
  • Target date: February 21, 2017 (this has slipped to accommodate brick multiplexing feature)
• Release tracker : https://github.com/gluster/glusterfs/milestone/1
• Updates:
  • In the process of preparing release-notes to release beta1
  • beta1 target date is currently 1st Feb, 2017, and we are tracking a day by day slip on this
  • Expect a possible 1 more day delay as we still are not getting healthy responses from contributors on various activities
  • Please try and prioritize 3.10 work

GlusterFS 3.9

• Maintainers : pranithk, aravindavk, dblack
• Current release : 3.9.1
• Next release : 3.9.2
  • Release date : 20 February 2017 (if 3.10 hasn't shipped by then)
• Tracker bug : https://bugzilla.redhat.com/show_bug.cgi?id=glusterfs-3.9.2
• Open bugs : https://bugzilla.redhat.com/showdependencytree.cgi?maxdepth=2&id=glusterfs-3.9.2&hide_resolved=1
• Roadmap : https://www.gluster.org/community/roadmap/3.9/
• Updates:
  • Add updates here

GlusterFS 3.8

• Maintainers : ndevos, jiffin
• Current release : 3.8.8
• Next release : 3.8.9
  • Release date : 10 February 2017
• Tracker bug : https://bugzilla.redhat.com/show_bug.cgi?id=glusterfs-3.8.9
• Open bugs : https://bugzilla.redhat.com/showdependencytree.cgi?maxdepth=2&id=glusterfs-3.8.9&hide_resolved=1
• Updates:
  • Release still on track, no other updates

GlusterFS 3.7

• Maintainers : kshlm, samikshan
• Current release : 3.7.20
• Next release : EOL
• Updates:
  • The final GlusterFS-3.7 release v3.7.20 has been made
    • https://lists.gluster.org/pipermail/gluster-devel/2017-January/052010.html

Related projects and efforts

Community Infra

• No updates

Samba

• No updates

Ganesha

• Ganesha 2.4.2 tagged. packages on download.gluster.org and Launchpad

Containers

• No updates

Testing

• No updates

Others

• No updates

Announcements

New announcements

• storhaug is now packaged in Fedora, coming soon in CentOS Storage SIG. Storhaug is the general purpose HA solution for Ganesha and Samba fronting Gluster volumes.
• glusterfs-coreutils packages are now available for Debian and Ubuntu. Packages on download.gluster.org and Launchpad respectively. Packages have been available in Fedora and CentOS Storage SIG for some time already.
• ndevos is going to speak at IDI2017: http://www.incontrodevops.it/program-idi2017/
• Gluster has a stand at FOSDEM 2017, with several developers hanging around

Regular announcements

• If you're attending any event/conference please add the event and yourselves to Gluster attendance of events: http://www.gluster.org/events (replaces https://public.pad.fsfe.org/p/gluster-events)
• Put (even minor) interesting topics/updates on https://bit.ly/gluster-community-meetings

---

• Instructions to hosts
  • start with #startmeeting Gluster community weekly meeting
  • use #topic, #action, #info and #agreed commands to make notes in the minutes
  • end the meeting with #endmeeting
  • when done, paste the links to the logs in this etherpad
  • archive this etherpad, copy the etherpad contents as is (ie. markdown) and create a new wiki with the markdown content and name it "Community Meeting YYYY-MM-DD"
  • create the next weeks agenda by copying the template (in markdown)
  • update the gluster-users and gluster-dev mailing lists with the meeting minutes, and also share the link to next weeks agenda