Community Meeting 2017 07 19

Gluster Community Meeting

• Date :2017-07-19
• Host : kshlm
• Logs :
  • Minutes: https://meetbot.fedoraproject.org/gluster-meeting/2017-07-19/community_meeting_2017-07-19.2017-07-19-15.02.html
  • Minutes (text): https://meetbot.fedoraproject.org/gluster-meeting/2017-07-19/community_meeting_2017-07-19.2017-07-19-15.02.txt
  • Log: https://meetbot.fedoraproject.org/gluster-meeting/2017-07-19/community_meeting_2017-07-19.2017-07-19-15.02.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.

• Should we build 3.12 packages for older linux dists, e.g., el6 (in the CentOS Storage SIG)? Probably we should, but want to ask the question just the same. [kkeithley]
  • Currently no problems building 3.12 on EL6 and older distros
  • Plan is to drop EL6 for 4.0
    • Will see what can be done if someone from the community volunteers to build 4.0 for old distros
    • GD2 currently doesn't build on the Go versions in available on EL6/EPEL.
• Is 4.0 STM or LTM? [shyam]
  • 4.0 is even, so should be LTM, but comes after an LTM so should be STM [shyam]
  • Changing the alternating LTM/STM will confuse people [amye]
  • 4.0 brings in a lot of new/fresh features, should be STM.
  • Everyone agrees 4.0 will be STM
  • What about 4.1?
    • Should be an LTM, considering alternating LTM/STM releases.
    • But will not follow odd/even scheme for LTM/STM
      • This has not been said ever
    • 4.1 could be STM and we return to 4.2 as LTM
      • Too long to say a new major relase is stable
    • We should decide after 4.0 is out, based on its stability

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

• ndevos will check with Eric Harney about the Openstack Gluster efforts
  • Skipped for next time
• jdarcy will work with nigelb to make the infra for reverts easier
  • This is done and already used a few weeks ago.
• JoeJulian to invite Harsha to next meeting to discuss Minio
  • Skipped for next time
• The person leading the application specific tests cases should start the survey to collect info on applications used with gluster
  • bulde/amarts originally put in this topic
  • nigelb was also planning on a survey about this
  • bulde and nigelb will be taking up this
  • Will proceed once we can ensure these tests can actually be done
• kshlm to find out who that person is
  • Had this conversation with Shyam, Vijay and Amye on email. No clear answer found.
• nigelb will document the walkthrough given by kkeithley on building packages
  • nigelb and Kaleb had a chat. We're going to automate this. The automation will serve as documentaton. In the event that Kaleb is unavailable, nigelb is able to build packages in the meanwhile.

Releases

GlusterFS 4.0

• Tracker bug : https://bugzilla.redhat.com/showdependencytree.cgi?id=glusterfs-4.0
  • Visit github for issues
• Roadmap : https://www.gluster.org/community/roadmap/4.0/
• Updates:
  • Add updates here

GlusterFS 3.12

• Maintainers: shyam, jiffin
• Release: Aug 30th, 2017
  • Branching: July 17th, 2017
• 3.12 Main focus areas
  • Testing improvements in Gluster
  • Refer below link
• Release Scope: https://github.com/gluster/glusterfs/projects/1
• Updates:
  • Add updates here

Related projects and efforts

Community Infra

• Add updates here

Samba

• Add updates here

Ganesha

• Add updates here

Containers

• Add updates here

Testing

• Add updates here

Others

• Anything that doesn't belong to any above categories, add updates here

Announcements

New announcements

• Add anything you want to announce to the community here

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