Skip to content

Latest commit

 

History

History
129 lines (82 loc) · 4.43 KB

2022-04-26-Community_Meeting.md

File metadata and controls

129 lines (82 loc) · 4.43 KB

Gluster Community Meeting - 26/04/2022

Previous Meeting minutes:

Date/Time: Check the community calendar

Bridge


Attendance

Name (#gluster-dev alias) - company

  • Chetan More - Red Hat
  • Pranith Kumar K - PhonePe
  • Nikhil Ladha - Red Hat
  • Amar Tumballi - Kadalu
  • Rakshitha Kamath - Red Hat
  • Harshita Shree - Red Hat

Community

  • Project metrics:
Metrics Value (Last meeting)
Coverity 18(27)
Clang Scan 64(80)
Test coverage 71.1(71.1)
Gluster User Queries in last 14 days 4
Total Github issues 198(203)
  • Any release updates?

    • Release updates

      • 9.x will receive updates once in 6 month
      • 10.x will receive update once in 3 month

      [Shwetha] Next tentative dates:

      • 9.x : Week of 20th Aug
      • 10.x : Week of 15th May
    • [Amar] Can the community agree to make a immediate release if we fix a CVE/Crash bug? The release can just have tarball from glusterfs community, and users who are impacted can work on getting their own rpm/deb packages if needed in that cases (if release team feels its too much of work). But not making a release (of at least a tarball) for CVEs and crash fixes is not a good thing for the project IMO.
  • Blocker issues across the project?

    • None
  • Notable thread from mailing list / User stories

    • None

Conferences / Meetups

Storage Developer Conference Global(SDC)
Storage Developer Conference EMEA
  • Date: June 14,2022
  • check link for more information
  • Registeration will open at end of April 2022.
Red Hat Summit 2022
  • Date: May 10-11,2022
  • check link for more information

GlusterFS - v11.0 and beyond

Developer focus

  • Any design specs to discuss?
    • simple-quota: PR Is merged now. Pranith had some questions.
    • One of them was why changes in DHT for simple-quota.
      • This helped reduce the complexity of Quota feature by reducing the challenge of running a separate daemon process (like quotad). Some 10 lines saved the whole aggregation process as a separate one, thus making management and maintenance simple.

Component status

  • Arbiter - stable/maintained
  • AFR - stable/maintained
  • DHT - stable/maintained
  • EC - stable/maintained
  • DOC - stable/maintained
  • Geo Replication - stable/maintained
  • Glusterd - stable/maintained
  • thin-arbiter - stable/maintained
    • Who is maintaining this? Can we make sure docs are up-to-date for thin-arbiter?

Recent Blog posts / Document updates

  • None

Host

  • Who will host next meeting? Chetan.
    • Host will need to send out the agenda 24hr - 12hrs in advance to mailing list, and also make sure to send the meeting minutes.
    • Host will need to reach out to one user at least who can talk about their usecase, their experience, and their needs.
    • Host needs to send meeting minutes as PR to http://github.com/gluster/community
    • Host has to send the meeting minutes as a mail to the gluster-devel and gluster-users list.

Notetaker

  • Who will take notes from the next meeting?

RoundTable

  • [Amar] Was the training videos/sessions helpful?
    • Yes (answer from few)

Action Items on host

  • Check-in Minutes of meeting for this meeting