15:01:32 <kshlm> #startmeeting Weekly Gluster Community Meeting 09-Mar-2016
15:01:32 <zodbot> Meeting started Wed Mar  9 15:01:32 2016 UTC.  The chair is kshlm. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:01:32 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
15:01:32 <zodbot> The meeting name has been set to 'weekly_gluster_community_meeting_09-mar-2016'
15:01:39 <kshlm> #topic Rollcall
15:01:42 <overclk> Hey kshlm
15:01:50 <kshlm> Raise you're hands if you're here!
15:01:52 * msvbhat is here
15:01:56 * kshlm o/
15:01:58 * overclk is here
15:02:01 <msvbhat> _o/
15:02:27 * aravindavk here
15:02:29 * amye is here
15:02:32 <post-factum> o/
15:02:32 <msvbhat> Someone should have set the topic to change of timing
15:03:18 <kshlm> I announced the change last meeting, and sent an invite in the minutes.
15:03:41 <kshlm> I would have also set the topic, but I'm not a OP.
15:04:08 <kshlm> This is all we have today?
15:04:23 * sankarshan is lurking :)
15:04:33 <kshlm> Let's start. More can join later.
15:04:51 <kshlm> As always, the agenda is at https://public.pad.fsfe.org/p/gluster-community-meetings
15:05:02 <kshlm> #topic Last weeks AIs
15:05:18 <kshlm> #topic kkeithley to send a mail about using sanity checker tools in the codebase
15:05:25 <amye> There, fixed that.
15:05:30 <amye> :D
15:05:43 <kshlm> amye, Thanks!
15:05:59 <kshlm> So kkeithley isn't around, and no mail has been seen on this topic.
15:06:14 <kshlm> I'll carry this forward.
15:06:29 <kshlm> I'll force him to do it next week when he's in Bangalore.
15:06:35 <kshlm> #action kkeithley to send a mail about using sanity checker tools in the codebase
15:07:08 <kshlm> #topic kshlm & csim to set up faux/pseudo user email for gerrit, bugzilla, github
15:07:15 <kshlm> THis isn't done yet.
15:07:50 <kshlm> But csim started a discussion on this as a response to a gerrit-github replication request. We should be continuing forward from that.
15:08:31 <kshlm> #link https://www.gluster.org/pipermail/gluster-infra/2016-March/001962.html
15:08:49 <kshlm> This is csim's post, if anyone wants to chip in please do.
15:09:17 <kshlm> I'll carry over this AI to next week. Now that we finally have some action on this, we should se it resolved soon.
15:09:30 <kshlm> #action kshlm & csim to set up faux/pseudo user email for gerrit, bugzilla, github
15:09:40 <kshlm> #topic kshlm to ping amye to update website to point to correct release
15:09:45 <kshlm> I believe I did this.
15:09:53 <amye> If you did, I missed that email.
15:09:57 <kshlm> amye, Did I?
15:10:11 <kshlm> Now I'm not sure.
15:10:35 <amye> Alright, we'll take it offline.
15:10:39 <kshlm> Yup I did.
15:11:01 <kshlm> Let's take it up after the meeting.
15:11:22 <kshlm> #topic ndevos will send out 3.5.8 announcement after the meeting
15:11:47 <kshlm> He did. But not right after the meeting.
15:11:59 <post-factum> https://www.gluster.org/pipermail/gluster-users/2016-March/025717.html
15:12:09 <kshlm> #link https://www.gluster.org/pipermail/gluster-users/2016-March/025717.html
15:12:14 <kshlm> post-factum, Thanks.
15:12:22 <kshlm> I wonder what ndevos is doing.
15:12:37 <kshlm> I think he had this meeting on his agenda for Bangalore.
15:13:00 <kshlm> #topic kshlm to ask hagarth to provide an update on 3.7.9
15:13:21 <kshlm> Done. And hagarth also sent out an announcement on his plans.
15:13:44 <kshlm> #link https://www.gluster.org/pipermail/gluster-devel/2016-March/048598.html
15:13:59 <kshlm> #topic msvbhat will add a HOWTO for DiSTAF for developers to write tests
15:14:12 <kshlm> msvbhat, I've not seen this yet.
15:14:28 <kshlm> I've also not been following the DiSTAF repo to check if this happened.
15:14:32 <msvbhat> It's not completed yet. I have basic draft with me. But needs lot of updates before pushing
15:14:53 <msvbhat> kshlm: ^^ Please carry this to next week.
15:15:09 <msvbhat> I will complete by next week.
15:15:19 <kshlm> msvbhat, Sure.
15:15:28 <kshlm> #action msvbhat will add a HOWTO for DiSTAF for developers to write tests
15:15:39 <kshlm> #topic msvbhat to mail gluster-devel soliciting opinions on location of DiSTAF tests.
15:15:44 <kshlm> You did this.
15:15:49 <msvbhat> Yes
15:15:50 <sankarshan> msvbhat,  could you point to the draft?
15:15:53 <kshlm> And I've already replied.
15:16:02 <kshlm> sankarshan, draft for the HOWTO?
15:16:06 <sankarshan> yes please
15:16:06 <msvbhat> yes, I saw.
15:16:16 <msvbhat> sankarshan: The HOTO draft?
15:16:21 <msvbhat> *HOTO
15:16:21 <sankarshan> yes please
15:16:39 <kshlm> msvbhat, your 'W' button isn't working :)
15:16:46 <msvbhat> sankarshan: Okay, I will send you later
15:16:48 <post-factum> take mine: "W"
15:16:58 <sankarshan> alright-y. thanks
15:17:01 <msvbhat> :) My mistake. *HOWTO
15:17:03 <kshlm> #link https://www.gluster.org/pipermail/gluster-devel/2016-March/048664.html
15:17:40 <kshlm> msvbhat, Send it out to the community. Not just sankarshan. We'd all like to see the draft as well.
15:18:04 <kshlm> #topic overclk to share notes from DHT2 discussion with jdarcy
15:18:18 <msvbhat> kshlm: Oh, For that I need some time. This is not ready yet
15:18:24 <overclk> kshlm, mostly next week.
15:18:33 <kshlm> overclk, Okay.
15:18:37 <msvbhat> kshlm: I will send in two days then
15:18:41 <kshlm> #action overclk to share notes from DHT2 discussion with jdarcy
15:18:55 <kshlm> #topic jdarcy to share his notes from his Bangalore discussions with the community
15:19:23 <kshlm> This hasn't happened yet. I guess someone needs to prod jdarcy to do this.
15:20:03 <kshlm> #action jdarcy to share his notes from his Bangalore discussions with the community
15:20:15 <kshlm> And I'll ping him to do this.
15:20:31 <kshlm> #action kshlm to ping jdarcy to share his notes
15:20:32 * sankarshan sage nods at "Bangalore" discussions :)
15:20:55 <kshlm> #topic kshlm/atinm to share notes on the GD2 discussions with jdarcy
15:21:21 <kshlm> I was writing all this up before the meeting, thinking I still had an hour left to the meeting.
15:21:44 <amye> Timezones--
15:21:45 <glusterbot> amye: Timezones's karma is now -1
15:21:46 <kshlm> Turned out I'd temporarily forgotten to read my watch.
15:21:59 <sankarshan> this too shall pass
15:22:31 <kshlm> I expect to send complete it and send it out after the meeting. If I don't fall asleep first.
15:22:54 <kshlm> sankarshan, Just like almost all other AIs we have :)
15:23:06 <kshlm> #action kshlm/atinm to share notes on the GD2 discussions with jdarcy
15:23:20 <kshlm> #topic kshlm to start discussion on improving maintainer documentation https://gluster.readthedocs.org/en/latest/Contributors-Guide/Guidelines-For-Maintainers/
15:23:35 <kshlm> I sent out a mail calling for suggestions.
15:24:11 <kshlm> #link https://www.gluster.org/pipermail/maintainers/2016-March/000451.html
15:24:34 <kshlm> There were a couple of replies from overclk and atinm.
15:24:46 <overclk> kshlm, yeh.
15:24:46 <sankarshan> if we are out of topics, I'd like to pose a query
15:24:49 <kshlm> Now we just need someone to send out the pull-requsts.
15:25:15 <overclk> kshlm, does everyone (dis)agree with the suggestions?
15:25:25 <overclk> or do we consider "no reply" == yes :) ?
15:25:32 <kshlm> sankarshan, We still have Glusterfs 3.{5,6,7,8} nad 4.0 to go.
15:25:42 * sankarshan will bide his time
15:25:44 <kshlm> overclk, We should just start assuming that from now on.
15:25:53 <overclk> kshlm, works for me.
15:26:17 <kshlm> overclk, Will you be sending any PRs on this?
15:26:41 <overclk> kshlm, I can do that for the maintainer updation part.
15:26:56 <kshlm> overclk, Go ahead. What ever you can contribute.
15:26:58 <overclk> kshlm, However I haven't fully gone through atinm's comments..
15:27:23 <overclk> kshlm, I'll see what (all) can I accumulate and send a PR.
15:27:32 <kshlm> If you need to discuss anything further on this, we can continue on the mail thread.
15:27:41 <kshlm> #topic GlusterFS 3.7
15:28:01 <kshlm> I'd hoped hagarth would be around today.
15:28:17 <kshlm> This is what we changed times for.
15:28:43 <kshlm> But as mentioned earlier hagarth sent out an announcement calling for the last patches to be merged for 3.7.9
15:29:30 <kshlm> According to the mail he hoped to close .9 yesterday. But that hasn't happened.
15:29:50 <kshlm> Guess he needs to be prodded again.
15:30:53 <post-factum> some movement was around performance bug today
15:31:11 <kshlm> post-factum, Which bug?
15:31:30 <post-factum> kshlm: this one https://bugzilla.redhat.com/show_bug.cgi?id=1309462
15:31:31 <glusterbot> Bug 1309462: low, unspecified, ---, ravishankar, POST , Upgrade from 3.7.6 to 3.7.8 causes massive drop in write performance.  Fresh install of 3.7.8 also has low write performance
15:31:43 <post-factum> related commits has been reviewed
15:31:46 <post-factum> *have
15:32:16 <kshlm> Ah, maybe he's waiting to get them merged.
15:32:39 <post-factum> Status: ASSIGNED → POST
15:32:46 <post-factum> I believe it is almost done
15:33:05 <kshlm> The related commit is still waiting on regression to run.
15:33:22 <kshlm> Or at least didn't have any run yet. I just triggered them.
15:33:36 <overclk> kshlm, also it would be good if http://review.gluster.org/#/c/13630/ would make it to .9
15:33:47 <overclk> it's current running regression..
15:33:51 <kshlm> overclk, Please let hagarth know about it.
15:34:01 <kshlm> It's upto him to make the decision as the release-manager.
15:34:03 <overclk> kshlm, it's already in the tracked.
15:34:51 <kshlm> It would help if you explicitly stated it. Anything in the 3.7.9 tracker which doesn't get it, will be carried forward to the next release.
15:35:24 <overclk> kshlm, will do. thanks!
15:35:27 <kshlm> Let's go onto 3.6
15:35:32 <kshlm> #topic GlusterFS 3.6
15:36:07 <kshlm> So 3.6.9 was announced by rabhat about 5 days back.
15:36:14 <kshlm> #link https://www.gluster.org/pipermail/gluster-devel/2016-March/048584.html
15:36:29 <kshlm> We're now in the 3.6.10 cycle.
15:36:46 <kshlm> I don't know if a tracker has been opened for it yet.
15:37:09 <kshlm> Not yet.
15:37:22 <kshlm> I'll get rabhat to do it.
15:37:51 <kshlm> #action rabhat to open a 3.6.10 tracker and close the .9 tracker, kshlm will ping him to do it.
15:38:08 <kshlm> #topic GlusterFS 3.5
15:38:48 <kshlm> 3.5.8 has been announced.
15:39:23 <kshlm> And ndevos has already closed/cleaned/opened what ever is required.
15:39:45 <kshlm> The 3.5.9 tracker is available at https://bugzilla.redhat.com/show_bug.cgi?id=glusterfs-3.5.9
15:39:46 <glusterbot> Bug glusterfs: could not be retrieved: InvalidBugId
15:39:56 <kshlm> #topic GlusterFS 3.8 and 4.0
15:40:03 <kshlm> Anyone have any update?
15:40:10 <kshlm> s/update/updates/
15:41:02 <overclk> kshlm, nothing from my side on 4.0
15:41:12 <kshlm> I think ndevos will be sharing some information on the 3.8 release plans.
15:41:23 <kshlm> hagarth, Time you showed up!
15:41:29 <aravindavk> kshlm: not much progress from my side too.
15:41:41 <hagarth> kshlm: what's up?
15:41:43 <amye> Heh. hagarth, any update on 3.8 release plans?
15:41:48 <amye> (current topic)
15:41:59 <kshlm> hagarth, what amye said.
15:42:01 <hagarth> amye: ndevos will be providing an update soon
15:42:13 <kshlm> ^ that was what I was saying.
15:42:23 <amye> :D
15:42:30 <hagarth> ok, we have consensus now :D
15:42:38 <kshlm> We don't seem to have any further 3.8/4.0 updates.
15:42:48 <kshlm> So hagarth an update on 3.7.9?
15:43:36 <hagarth> kshlm: still waiting for last 2-3 patches to be merged
15:43:46 <hagarth> some regressions are in progress atm
15:43:54 <hagarth> I will be running some tests after that
15:43:57 <kshlm> hagarth, Cool. Good to know.
15:44:05 <hagarth> if things look good, I plan to tag by end of this week
15:44:12 <kshlm> Thanks.
15:44:43 <kshlm> overclk, You can now find if your change is one among the 2-3 hagarth is tracking.
15:45:01 <msvbhat> I have small question on 3.8 release. Can someone use distaf and provide feedback? And let me know if anything needs to be done before 3.8 relase
15:45:14 <hagarth> overclk: I am tracking a bitrot fix. is that the one?
15:45:31 <hagarth> msvbhat: have you discussed this with ndevos?
15:45:31 <overclk> hagarth, yep.
15:45:40 <overclk> thanks hagarth!
15:45:41 <kshlm> msvbhat, But we don't know how to use it. We don't have a HOWTO. :(
15:46:31 <kshlm> msvbhat, The sooner you we get the HOWTO, the sooner you get your feedback.
15:46:47 <msvbhat> hagarth: few weeks ago, yes. Not now. Probably I will discuss with him tomorrow
15:46:54 <kshlm> hagarth, We'll be catching up with ndevos this week.
15:47:22 <kshlm> I think we're done with the topics for the day.
15:47:23 <msvbhat> kshlm: Ah, yeah. Let me take it up on higher priority :)
15:47:30 <kshlm> sankarshan, You had something to discuss?
15:47:46 <kshlm> Oh, wait.
15:47:57 <kshlm> We need to choose next weeks meeting host.
15:48:04 <kshlm> #topic Next weeks meeting host?
15:48:10 <amye> We're moving the meeting back to the normal time, yes?
15:48:17 <kshlm> I put it on top so that I don't forget, and forgot about it.
15:48:20 <kshlm> amye, yes.
15:48:24 <hagarth> kshlm, msvbhat: ok
15:48:45 <kshlm> I was going to announce it at the end of the meeting.
15:48:58 * sankarshan did have something to put across - does the newsletter require additional individuals to enable a better coverage of topics
15:49:02 <kshlm> So who wants to host next's week at 1200UTC.
15:49:36 <kshlm> Any hosts?
15:49:43 * amye lets the conversation about meeting host go first but yes yes yes I would love more help on the newsletter.
15:50:35 <kshlm> Alright. I'll do it one more time for forgetting to bring this up earlier.
15:50:59 <amye> Heh.
15:51:02 <kshlm> #info kshlm to host next weeks meeting as well.
15:51:26 <kshlm> I'll not advance next weeks meeting without finding a volunteer.
15:51:38 <hagarth> kshlm: let us put a community meeting host calendar somewhere
15:51:56 <kshlm> sankarshan, amye, you guys have the stage.
15:52:05 <kshlm> hagarth, You and atinm had to do this IIRC.
15:52:13 <kshlm> #topic does the newsletter require additional individuals to enable a better coverage of topics
15:52:43 <hagarth> kshlm: I don't remember this AI - but let us see what we can do
15:52:48 <sankarshan> and since amye states that it does and it would be nice, does that mean we need a call for roving reporters?
15:52:52 * kshlm is happy we're doing good on time this week
15:53:26 <amye> Getting more information about 1) upcoming releases and 2) things that we're currently working on, like distaf, etc, would be valuable.
15:53:39 <amye> The next newsletter is set to go out after the march 16th community meeting.
15:54:19 <kshlm> We'll be having updates on the new features in this meeting every week.
15:54:35 <kshlm> Couldn't we collate a months worth of updates for the newsletter?
15:54:36 <sankarshan> alright. i'll try to impress upon msvbhat the way to include distaf and 3.8 etc into one small post
15:55:03 <amye> kshlm, we could, but the updates are things like 'oh yeah, working on that, will get back to you' :D
15:55:15 <sankarshan> (in other words, i might just repurpose that above mentioned draft into a section for newsletter)
15:55:27 <amye> ++
15:55:54 <kshlm> amye, Ah. Okay.
15:55:59 <sankarshan> we should have a release reports kind of section
15:56:07 <sankarshan> somewhat well summarized updates
15:56:20 <amye> I like this idea.
15:56:20 <sankarshan> but ... one section/step at a time i guess
15:56:22 <sankarshan> :D
15:56:34 <kshlm> sankarshan, Absolutely. If we're going to schedule, we should have 3 releases to report on.
15:56:56 <amye> But we'll start small for this one, April will be focusing on Vault and hopefully? a 3.8 release.
15:57:02 <sankarshan> i'll ponder over this and steal/borrow ideas from other community newsletters
15:57:26 <sankarshan> and that is all i had.
15:57:38 <sankarshan> thanks for enabling this misc business discussion
15:57:52 <amye> Excellent.
15:57:54 <kshlm> sankarshan, So you're happy with borrowing msvbhats draft for now?
15:58:16 <sankarshan> kshlm,  i'll take a look at it and see what we can do with it.
15:58:27 <sankarshan> we haven't had a look-see yet ;)
15:58:48 <kshlm> Okay.
15:59:06 <kshlm> Let us know when you need more reporters.
15:59:22 <sankarshan> starting yesterday
15:59:33 <kshlm> :)
15:59:39 <amye> I can put out a call on the -devel list.
15:59:54 <sankarshan> amye,  that be fantastic to have
15:59:57 <amye> So that folks who weren't here can weigh in, I'm sure there are things that I'm missing.
16:00:09 <kshlm> So if there are no more topics to discuss, I'll be doing the weekly announcements and ending the meeting.
16:00:28 <amye> Thank you kshlm
16:00:30 <kshlm> #topic Announcements/Reminders
16:00:33 <kshlm> If you're attending any event/conference please add the event and yourselves to Gluster attendance of events: https://public.pad.fsfe.org/p/gluster-events
16:00:33 <kshlm> Put (even minor) interesting topics on https://public.pad.fsfe.org/p/gluster-weekly-news
16:00:33 <kshlm> Use the following etherpad for backport requests  https://public.pad.fsfe.org/p/gluster-backport-requests
16:00:37 <hagarth> kshlm++ thank you!
16:00:52 <kshlm> IMPORTANT: Next weeks meeting 16/Mar/2016 will be held at 1200UTC.
16:01:03 <kshlm> Thanks for attending this weeks meeting everyone.
16:01:10 <kshlm> #endmeeting