12:02:15 #startmeeting Weekly GlusterFS Community Meeting 12:02:15 Meeting started Wed Sep 17 12:02:15 2014 UTC. The chair is JustinClift. Information about MeetBot at http://wiki.debian.org/MeetBot. 12:02:15 Useful Commands: #action #agreed #halp #info #idea #link #topic. 12:02:24 Who's around? :) 12:03:37 Haalllooooooo ? 12:04:03 * msvbhat is pesent 12:04:21 * davemc is here 12:04:21 msvbhat: Thx. I was thinking I got the time wrong 12:04:28 * hagarth is here 12:04:33 * kkeithley is here 12:04:36 JustinClift: :) 12:04:37 * davemc is multitasking 12:04:47 Cool 12:04:56 Etherpad: https://public.pad.fsfe.org/p/gluster-community-meetings 12:05:38 #topic Action items from previous meetings 12:05:47 "davemc to get the GlusterFS Consultants and Support Company's page online by the end of this week" 12:05:52 davemc: How's that looking? 12:06:13 not done. I'm trying to figure out how te site works without blowing it up 12:06:22 hopefully soon, though 12:07:14 davemc: k. Engage people in the osas channels on RH irc, as the main authors hang out there :) 12:07:38 davemc: Even stuff like "what do I need to type to make this next bit work? or "what's this mean?"" 12:07:52 yessir 12:07:54 "kkeithley to chase pranithk about https://bugzilla.redhat.com/show_bug.cgi?id=1127140" 12:07:55 Bug 1127140: unspecified, unspecified, 3.4.6, gluster-bugs, NEW , memory leak 12:08:08 I think it PEBKAC 12:08:33 I did chase him. 12:08:41 davemc: PEBKAC is fine. Engage ppl there, and we'll walk you through it :) 12:09:12 He and Poornima a working on the Denali release and prob won't have time to investigate 'til after that. 3.4.6beta2 is on hold until then 12:09:19 kkeithley: Np 12:09:30 Yeah, there's a bunch of patches which are outstanding for things atm 12:09:40 "lalatenduM to create blog post about GlusterFS 3.4.6beta1 rpms being available on the download server" 12:09:43 Done 12:09:46 "JustinClift and lalatenduM to ensure lalatenduM has a blog account" 12:09:47 Done 12:09:52 "ndevos and hagarth to discuss the outstanding 3.5.3 blocker BZ's, and which ones to move to 3.5.4" 12:09:55 ndevos: ? 12:10:11 not yet 12:10:45 ETA? 12:11:01 _Realistic_ eta? (just saying) :) 12:11:12 eta: by next week's meeting 12:12:00 #action ndevos and hagarth to discuss on gluster-devel (by 24th Sept) the outstanding 3.5.3 blocker BZ's, and which ones to move to 3.5.4 12:12:18 #action davemc to get the GlusterFS Consultants and Support Company's page online 12:12:34 "JustinClift to ping David Robinson (Corvid Tech) to see if they will have time to test 3.6 beta" 12:12:49 Email them. David's travelling, but will try to do so. 12:12:56 "hagarth, JustinClift and davemc to sync up on 3.6.0 launch plan offline" 12:13:03 We have a meeting scheduled for later on today. 12:13:07 "kkeithley to put 3.6.0 beta / rc on the Longevity Cluster" 12:13:14 How's that go? :) 12:13:24 I didn't do that 12:13:35 Yeah, it kind of needs beta to be released first eh? 12:13:42 Lets wait for that to happen... 12:13:56 I was kinda thinking that was a "could we do it" and the answer is "yes we can". 12:14:09 Right, when there's something worth running 12:14:13 like a beta 12:14:14 Yeah 12:14:18 k, moving 12:14:19 on 12:14:23 #topic 3.4 12:14:40 How's this looking? 12:15:34 There are a _lot_ of open CR's on the release-3.4 branch atm: kkeithley to put 3.6.0 beta / rc on the Longevity Cluster 12:16:09 http://review.gluster.org/#/q/status:open+project:glusterfs+branch:release-3.4,n,z 12:16:15 Bad cut-n-paste ;) 12:16:16 There are some fixes for dht IIRC 12:16:17 mostly they seem to be dht fixes 12:16:23 Yeah 12:16:31 yes. I'll get those merged today if they have +2 12:16:32 i can help with reviews once the regression run is clean 12:16:56 kkeithley: There's something wrong with at least one of them, that's causing the ones dependant on it to fail regression testing 12:16:59 * jdarcy sneaks in and sits in the back. 12:17:09 * JustinClift throws popcorn at jdarcy 12:17:30 maybe we should trigger regression runs again? 12:17:52 hagarth: I've done it a few times for some of them. I don't suppose it'd hurt to try again. 12:17:56 Sorry for being late, but which patches are we talking about? 12:18:03 jdarcy: http://review.gluster.org/#/q/status:open+project:glusterfs+branch:release-3.4,n,z 12:18:08 Thanks. 12:18:11 Outstanding dht from for release-3.4 12:18:46 I guess this is mostly just blocked on those, and - if the retriggered regression tests don't all pass - we'll just need to wait for them to be fixed 12:19:01 It's probably less urgent than the Denali and our upstream 3.6.0 stuff though 12:19:12 3.4.x is generally fairly stable... 12:19:51 JustinClift: some of these fixes would make 3.4.x more robust .. would be good to have them in soon. 12:19:56 #action JustinClift to retrigger regression runs for the failed release-3.4 CR's 12:19:57 except for the client-side memory leak 12:20:13 it's stable except for the client-side memory leak 12:20:37 hagarth: Yeah, I'm not saying they wouldn't help. I'm just wondering if we're hitting resourcing problems (Raghavendra G's time), so maybe having to delay 12:21:07 JustinClift: right, I will check with Raghavendra G to see when he can take a re-look at this. 12:21:10 kkeithley: No-one that's experiencing the client-side memory leak has the time/skill to diagnose it though. :/ 12:21:16 hagarth: AI that :) 12:21:18 Looks like http://review.gluster.org/#/c/8671/1 was the first to fail. It's a faithful reproduction of the version on master, so not clear how it might be interacting with 3.4-specific code. 12:21:51 It's in 3.5 also 12:21:55 #action hagarth to work with Raghavendra G on dht bug fixes for 3.4.x 12:22:06 jdarcy: http://review.gluster.org/#/c/8671 passed didn't it ? 12:22:20 Well, that's Pranith and Poornima, and they're busy on Denali 12:22:58 jdarcy: You're meaning http://review.gluster.org/#/c/8672/ I guess 12:23:01 Oh, right. It's the next one, which is (gulp) a port of mine. 12:23:10 * JustinClift throws more popcorn 12:23:30 Anyway, lets let Raghavendra G have at it first, and take it from there 12:23:38 Moving on.... 12:23:44 The client-side leak is in 3.5. also 12:23:44 #topic 3.5 12:24:19 kkeithley: Does that help us get someont to investigate/debug it? 12:25:09 jdarcy: btw https://public.pad.fsfe.org/p/gluster-community-meetings 12:25:12 JustinClift: let us check with R G 12:25:44 k, is anyone around atm that knows the status of 3.5.4? 12:26:00 hagarth: Guessing that's the AI from earlier for yourself and ndevos... 12:26:00 JustinClift: nope, ndevos is busy this week 12:26:08 k, lets move on. :) 12:26:09 3.5.2 12:26:25 Niels is out for training this week (Ceph!) 12:26:25 Yeah, typo there 12:26:54 Awesome. We'll need to have a brainwashing session when he gets back, to return him to the good side of the force... :p 12:27:07 #topic 3.6 12:27:18 hagarth: This is your baby. How's this looking? 12:27:26 JustinClift: looking very good! 12:27:45 we have quite a lot of good fixes merged in 3.6 now 12:27:46 The list here seems to be shrinking: http://review.gluster.org/#/q/status:open+project:glusterfs+branch:release-3.6,n,z 12:27:58 i am planning to have a beta release out this week 12:28:19 me and hchiramm__ have been planning logistics for a test week over the next week 12:28:38 hchiramm__: if you are around, can you please share some updates about the test week? 12:28:40 Cool. :) 12:28:49 hagarth, sure 12:29:03 planning to start from next monday 12:29:06 hchiramm__: oops, never noticed your alter ego 12:29:10 :) 12:29:38 Cool. Is that Planning36 page accurate still then? 12:29:42 http://www.gluster.org/community/documentation/index.php/Planning36 12:29:46 http://www.gluster.org/community/documentation/index.php/3.6_test_day 12:29:50 JustinClift, ^^^ 12:30:10 Cool. Can you please link to the test page from the planning page? 12:30:11 gathering the required information on above URL .. 12:30:20 JustinClift, will do.. 12:30:32 And probably also worth emailing gluster-users and gluster-devel, letting them know about it 12:30:39 We've been pretty quiet about it so far 12:30:42 yep.. will be doing it soon.. 12:30:56 JustinClift: mostly accurate, apart from the test weekend dates. We will decide on a GA date based on the feedback we get during the test week. 12:31:23 still need some update from component owners on "HOW TO TEST " section on feature pages 12:31:26 #action Humble to email gluster-devel and gluster-users about the upcoming test day, and including thest 3.6_test_day page 12:31:51 Humble: Cool. Please chase the component owners to get it done 12:31:52 :) 12:32:02 hagarth, if u can help here :) 12:32:08 k, is there anything else for 3.6 we need to cover? 12:32:13 Humble: happy to help with the chasing :) 12:32:16 hagarth++ thanks ! 12:32:31 Moving on.... 12:32:35 #topic Other items to discuss 12:32:40 Anyone have stuff? 12:33:02 k, I think we're good. :) 12:33:04 #endmeeting