Skip to content

Community Meeting 2017 01 04

Kaushal M edited this page Jan 4, 2017 · 1 revision

Gluster Community Meeting

General information

  • Location : #gluster-meeting on Freenode (webchat)
  • Time : For meetings 30th March (2016) and later
    • 12:00 UTC
    • or in your local shell/terminal: date -d "12: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.

Open floor

  • STM and backports [Shyam]
    • I see that a lot of patches are being backported to the STM release (i.e 3.9). I assumed that we backport only those that users ask for as they try out the STM to give us feedback. Would like to discuss this in the meeting today.
    • [shyam] STM is not for production, so shouldn't be getting backports until a user asks
    • [everyone else] STM is a stable release. So it should get backports. (Though its only for 3 months)
  • A common location for testing-tools [Shweta]
    • QE tests being ported upstream with Glusto use some custom tools
    • They need to be provided from a well known location owned by the community
    • Currently, one tool (arequal) is being hosted in copr at https://copr.fedorainfracloud.org/coprs/nigelbabu/arequal/
    • Most of the tools have upstream packages, with the exceptions being arequal and smallfiles
    • arequal is gluster specific, so needn't be provided by distributions
    • smallfiles is useful enough to be packaged in distributions
  • Developer workflow problems [nigelb]
    • The Facebook contribution has highlighted that our current workflow is non-ideal. This is also obvious at every release.
    • The tests need to run faster or needs to be less intermittent.
    • I'm happy to help in terms on infra, but I'd love pointers from people who've sped this up in the past (rtalur's setup?).
    • Regression tests take 4+ hours to run, fail intermittently, frustrate devs, bad for newcomers
    • Need to cut down time patches spend waiting on regression runs
    • Can speed up by running tests in parallel on multiple machines
      • Still, intermittent failures frustrate
    • Do away with per patch/review regression tests altogether. Run regression tests periodically on each branch
      • Intermittent failures need to be fixed for this to work
    • Get rid of noisy tests, which are about half the tests, and run the remaining in parallel per patch
      • Run the noisy tests periodically
    • For now, try to get parallel runs working. Will help figure out and fix intermittent failure faster, and get data for noisy tests.
    • To speed up fixes to intermittent failures, bugs will be filed based on fstat.gluster.org stats, every 2 weeks.

Next weeks 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 last week

  • Discuss participation in the meetings in January.
    • Carryover to January

Releases

GlusterFS 4.0

GlusterFS 3.10

GlusterFS 3.9

GlusterFS 3.8

GlusterFS 3.7

Related projects and efforts

Community Infra

  • The Gerrit OS upgrade didn't go through during the holidays. We'll be schduling it this month at an appropriate weekend.
  • fstat also shows branch names now so you know if a failure happens only in one specific branch. It only does this for new jobs, not for old ones. (If there is demand, I'll add it for old ones)
  • When a NetBSD jobs is aborted, the machine will now be automatically restarted.
  • We've addded an additional machine for netbsd smoke since the queue was getting quite long with just one machine.

Samba

  • None

Ganesha

  • None

Containers

  • None

Testing

  • None

Others

Announcements

New announcements

  • None

Regular announcements


  • 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
Clone this wiki locally