12:01:01 #startmeeting 12:01:01 Meeting started Wed Feb 25 12:01:01 2015 UTC. The chair is ndevos. Information about MeetBot at http://wiki.debian.org/MeetBot. 12:01:01 Useful Commands: #action #agreed #halp #info #idea #link #topic. 12:01:06 #info agenda: https://public.pad.fsfe.org/p/gluster-community-meetings 12:01:11 #topic Roll Call 12:01:16 Hello all! 12:01:29 * jdarcy is present. 12:01:29 * JustinClift waves 12:01:40 * hagarth is here 12:01:41 * tigert is here 12:01:50 * lalatenduM is here 12:01:55 Gah 12:01:59 * shaunm is present 12:01:59 * kshlm here 12:02:04 Just saw our Jenkins queue 12:02:05 hchiramm: PING!? 12:02:22 ndevos, pong :) 12:02:36 * soumya_ is here 12:02:37 JustinClift, feature freeze rush :) 12:02:38 telmich: are you here too? 12:02:47 kshlm: And several slaves down 12:02:56 JustinClift: yes, be prepared to see breakage :) 12:02:58 * JustinClift will spin up a bunch more slaves this week 12:03:11 JMW will just have to deal with the bill later ;) 12:03:13 JustinClift: *BSD ones too? 12:03:18 * raghu is here 12:03:31 ndevos: That's a Manu thing, but is probably a good idea 12:03:45 #topic Action Items from last week(s) 12:03:59 #info subtopic: ndevos should publish an article on his blog 12:04:00 ndevos: I had the idea when I woke up of creating a "setup new slave vm" script, like your reboot script. I think it'd work. 12:04:01 DONE! 12:04:18 * JustinClift keeps quiet about it until open discussion 12:04:26 thanks JustinClift :) 12:04:33 #info subtopic: hchiramm will try to fix the duplicate syndication of posts from ndevos 12:04:54 hchiramm: at least on twitter there was duplication, not sure if that happened on the blog too? 12:04:57 ndevos, I noticed ur posts were duplicated in blog.gluster.org 12:04:57 * lalatenduM is amazed to many members here for the meeting :) 12:05:06 to see* 12:05:20 hchiramm: okay, plan of action? 12:05:38 ndevos, I will check from backend 12:05:57 #action hchiramm will check the blog duplication backend 12:05:58 hchiramm: please also involve spot 12:06:02 lalatenduM: web needs fixing:) 12:06:12 he has also been working on avoiding duplication 12:06:17 hagarth, oh..ok 12:06:20 #action hchiramm will check the blog duplication backend - together with spot 12:06:22 thanks for the pointer.. 12:06:28 * msvbhat arrives late 12:06:34 #info subtopic: hchiramm will share the outcome of the non-mailinglist packagng discussions on the mailinglist (including the Board) 12:06:38 tigert, :) 12:06:53 hchiramm: syndicated the feed twice? 12:07:14 http://blog.gluster.org/ tigert 12:07:18 if u see the footer 12:07:29 "from the blog" 12:07:39 it shows 2 entries for ndevos 's post. 12:08:03 tigert, hchiramm: please continue looking into that after the meeting :) 12:08:04 Hmmm, it also has "2014" instead of 2015 in the footer 12:08:14 * JustinClift should be able to fix that right away (the date) 12:08:24 * ndevos reminds JustinClift of what he said before 12:08:30 not sure why its happening .. its not getting duplicated for everyone . but ndevos :) 12:08:47 hchiramm: back to the CURRENT TOPIC? 12:08:51 Heh 12:08:56 ndevos, go ahead :) 12:09:04 hchiramm: packaging discussion? 12:09:27 a solution was almost carved , but hagarth has a different thought on the same 12:09:41 so yet to conclude the final solution.. 12:09:55 ndevos, ^^^ 12:09:56 yeah , the discussion is still on going 12:10:03 lets carry it forward 12:10:11 oh, yes, our nice solution was pulled into a different direction... we'll continue with that sometime next week, I think 12:10:21 ndevos: mea culpa? 12:10:42 * JustinClift has been ignoring the thread 12:10:43 ndevos, :) 12:10:43 #info packaging discussion between upstream/downstream and potential conflicts in the future is still ongoing 12:10:59 hagarth, almost :) j/k 12:11:01 JustinClift, :/ 12:11:28 hagarth: we'll see if we can do something with your idea, it actually requires some thought 12:11:46 #info subtopic: hagarth to open a feature page for (k)vm hyperconvergence 12:11:53 hagarth: done? 12:11:56 ndevos: WIP - http://www.gluster.org/community/documentation/index.php/Features/Ovirt_Hyperconvergence#Current_status 12:12:10 wow, you impresse me! 12:12:20 thanks :) 12:12:26 #info subtopic: ndevos will contact spot about open standing action items on the weekly agenda 12:12:36 ndevos: thanks, have got plenty of details to fill in nevertheless ;) 12:12:36 also done, but I did not get a reply :-/ 12:12:55 and spot does not seem to be in this meeting either... 12:13:11 he is likely timezone challenged :P 12:13:36 tigert: maybe, but responding to emails can be done days before the meeting 12:13:44 What about container (rather than VM) hyperconvergence? 12:13:45 true 12:14:13 jdarcy: I do not think the oVirt people are much into containers at the moment ;) 12:14:18 jdarcy: overlay xlator underway for that 12:14:35 hagarth: Cool. Is there a feature page for it? 12:14:43 ndevos, they got the support in ovirt I believe 12:14:44 hagarth: Also, *who* is working on it? 12:14:50 hagarth: oh, interesting, who's writing the feature page and -devel email announcement for that? 12:15:00 jdarcy: not yet, right now it is only in my head 12:15:23 "underway" might have been an overstatement? 12:15:43 ndevos: yes, felt like using over and under in the same sentence ;) 12:15:53 hehe 12:16:06 I think we should get that on a roadmap people can see. 12:16:09 will post more details once i have a bit more clarity 12:16:18 jdarcy: +1 12:16:31 It's something a lot of people might find interesting, and for once there's some real usefulness behind it too. 12:16:59 * hagarth notices xlators/cluster/overlay in his local repo 12:17:00 #action hagarth will post more details about an overlay xlator (container targetted) when he has a bit more clarity 12:17:55 #action hagarth to post his surprise find of xlators/cluster/overlay code early 12:18:09 #info subtopic: hagarth to carry forward discussion on automated builds for various platforms in gluster-infra ML 12:18:39 hagarth: some progress here? 12:18:46 ndevos: not yet done 12:18:46 ndevos: will aim it for this week 12:19:00 okat, we'll ask you next week about it again 12:19:11 #info subtopic: ndevos should send out a reminder about Maintainer responsibilities to the -devel list 12:19:25 oh, I'm a slacker, that still needs to get sent out 12:19:37 #info subtopic: telmich will send an email to the gluster-users list about Gluster support in QEMU on Debian/Ubuntu 12:19:43 not sure if telmich is here? 12:20:22 telmich is one of the interested users that would like to see QEMU in debian/ubuntu support gfapi connections 12:20:38 did anyone notice an email conversation about that? 12:20:59 ... sounds like a collective "no" 12:21:08 #info subtopic: jimjag to engage the board, asking for their direction and input for both 3.7, and 4.0 releases 12:21:32 JustinClift: jimjag isnt around, was there any feedback on the board list? 12:21:33 There was an email about it 12:21:39 1 sec 12:21:40 Looking 12:21:44 JustinClift: any responses to that? 12:21:53 No 12:21:58 And TBH, it was a crap email he sent 12:22:10 We need to do better 12:22:16 * JustinClift will engage the board instead 12:22:40 #action JustinClift will engage the board re: 3.7 and 4.0 12:22:55 okay, thanks 12:23:04 #topic GlusterFS 3.6 12:23:20 raghu: you have a few precious minutes :) 12:23:49 I have merged few patches. There are some patches which need review and some patches have to pass regression 12:23:54 I am waiting for them 12:24:16 Want to make a beta2 next week. 12:25:19 raghu: el5 builds are broken atm, something has changed in the (centos?) distribution causing the packages to get build with lvm2 suppor 12:25:23 t 12:25:31 and, lvm2-devel is not available on el5 :-/ 12:25:49 * lalatenduM saw that too 12:25:50 ndevos: is librcu available on el5? 12:25:56 hagarth: no, not yet 12:25:57 hagarth, nope 12:26:14 hagarth: kshlm might become maintainer for userspace-rcu on el5 12:26:26 but, that is not a 3.6 issue 12:26:38 ndevos: Changes in our .spec file, so it's nor correctly detecting things? 12:26:41 * lalatenduM got that while building the master branch 12:26:44 (on el5) 12:26:59 JustinClift: no changes on our side, it must be something in the distro 12:27:02 ndevos: ok, cool 12:27:22 lalatenduM: can you test a 3.6 build too? that should have the same lvm2-devel package issye 12:27:25 *issue 12:27:34 ndevos: k. We may have to change our .spec file to work around it tho ;) 12:27:55 JustinClift: we have those workarounds, but detecting of the el5 distro started to fail recently 12:28:04 :( 12:28:06 ndevos, I am re-checking lvm2-devel on el5, there might be soem mistake from me 12:28:34 lalatenduM: no, lvm2-devel is not available on el5 - the detection seems to have broken 12:28:48 ndevos: I can wait more for making beta2 if you think this issue has to be resolved before making beta2 12:29:01 raghu: so, I guess we need to fix the el5 builds before you can ... - yes that 12:29:13 ndevos: sure 12:29:19 ndevos, lets wait for some time , will let you know 12:29:52 #agreed 3.6 does not build on el5 anymore, that needs to be fixed before beta2 is made 12:30:10 raghu: anything else you want to mention? 12:30:37 ndevos: nope. Covered everything :) 12:30:53 raghu: ok, thanks! 12:31:00 #topic GlusterFS 3.5.4 12:31:11 that is more or less the same as with 3.6 12:31:18 ndevos: ok 12:31:28 sudden build issues on el5 :-/ 12:31:42 but, more patches have been merged as well 12:31:53 hagarth: ok - to what? 12:31:53 I am getting a new issue "configure: error: python does not have ctypes support" on el5 12:32:07 note - Gluster WP admin account has been created for tigert 12:32:28 lalatenduM: right, same detection, I guess -> move it out of the meeting? 12:32:40 yeah 12:32:40 ndevos: ok to 3.5.4 status 12:32:55 hagarth: ah, ok :) 12:33:10 anything else for 3.5? 12:33:29 #topic GlusterFS 3.4 12:33:52 kkeithley isnt there, he's in a different timezone this week... 12:34:23 I did not get a status update from him, so I expect that there is no plan to release 3.4.7 any time soon 12:34:40 I wonder if we'll need a 3.4.7 since 3.7 is going to be out soon 12:35:00 once that is out, 3.4 will not be supported anymore 12:35:02 how "soon" would 3.7 get out? 12:35:11 ndevos: 2 months from now 12:35:48 #info when 3.7 gets released, 3.4 will not be supported anymore 12:36:18 We should get a 3.4.7 out, because we know there will be stragglers 12:36:30 JustinClift: yeah, agree with that 12:36:31 Might as well keep it stable for them until they nearly drop dead of age ;) 12:36:42 #info maybe there is no need for a 3.4.7 release if 3.7 gets released in 2 months? 12:36:45 NO 3.4.8 THO 12:36:50 ;) 12:37:10 well, 3.4.7 is waiting for a long time already, there does not seem to be something extremely urgent 12:37:10 Also no 3.8 unless it's OVER MY DEAD BODY. 12:37:47 #topic GlusterFS.next 12:37:52 * jdarcy realizes that counts as an incentive for some people. 12:37:53 * JustinClift can pretty clearly see a 3.8 poltergeist, getting ready to hover over jdarcy :p 12:37:59 #info subtopic: GLusterFS 3.7 12:38:00 :D 12:38:03 jdarcy: that's a good topic for discussion in the offline GlusterFS summit 12:38:17 3.7 feature freeze targeted for this weekend 12:38:31 there are plenty of patches to be reviewed 12:38:33 With the way our regression testing stuff is going, I have my doubts 12:38:40 any help with reviews would be more than welcome 12:38:49 any help with Jenkins also would be very welcome! 12:39:01 * JustinClift is spinning up 20x new slaves atm 12:39:06 hagarth: now its time to point to your etherpad ;) 12:39:20 Yay JustinClift!! 12:39:26 https://public.pad.fsfe.org/p/review-for-glusterfs-3.7 12:39:33 JustinClift: the main bottleneck is the smoke and *BSD tests... 12:39:39 contains the list of feature patches that need review 12:39:48 Our regression tests on master take ~2 hours each though, and they're failing from spurious errors 75% of the time 12:39:51 Ahhh 12:40:05 I suspect that we might slip feature freeze by a few days 12:40:19 but I don't expect that to have any impact on the GA date for 3.7.0 12:40:36 hagarth: or, hand out exceptions per feature? get them merged in waves? 12:40:50 ndevos: yes, we'll need to grant exceptions 12:41:02 some features are nearly there and I would hate to miss them in 3.7.0 12:41:33 hagarth: We may need to get the smoke tests off of master 12:41:37 any volunteers to help with reviews of features in the etherpad by friday? 12:41:46 * JustinClift will look at setting up some smoketestslaves or something 12:42:11 JustinClift: more slaves for smoketests would be awesome 12:42:11 "java" process on build.gluster.org is running at 500+% cpu 12:42:26 I'm not sure it's going to handle many new slaves after all :( 12:42:43 JustinClift: IMHO any slave should be able to run smoke tests - but I have no idea how to set that up 12:42:45 Will discuss after meeting 12:42:52 Yeah, I'll look into it 12:42:53 JustinClift: ok 12:42:55 Might not be hard 12:43:07 I suppose I could take the last resource (me) away from 4.0 to review 7000 lines of code only submitted for review two days ago. 12:43:29 jdarcy: thanks, that would be appreciated! 12:43:30 I almost feel sorry for the authors, considering the mood that puts me in. 12:43:43 I was going to mention that could be a very quick review :) 12:43:53 jdarcy: I *hate* huge patches :-/ 12:44:04 we have plenty of learnings from 3.7 which probably need to be discussed as part of a retrospective 12:44:09 In other words *why the fuck do people keep their code private so long*? 12:44:09 3.7 should be stable about 3.7.5 then... ;) 12:44:17 That's not open source. That's dump and run. 12:44:26 jdarcy: no clue 12:44:58 Sorry, I'll stop ranting. 12:45:01 * ndevos tries hard to convince people to post patches in small chunks, and get those merged early and build upon that 12:45:25 hagarth: anything else for 3.7? 12:45:25 ndevos: maybe we should send an email on the lists to remind folks about this "best practice" 12:45:44 * kshlm agrees with ndevos. 12:45:56 ndevos: nothing more, I will be buried in reviews for 3.7 for a while now 12:45:57 hagarth: something like that would be good - or recommended practices to get your code merged quicker 12:46:11 thanks hagarth 12:46:25 #info subtopic: GlusterFS 4.0 12:46:43 We're having a meeting tomorrow morning for that. 12:46:56 Meeting tomorrow 11:00 UTC: http://www.gluster.org/pipermail/gluster-devel/2015-February/043960.html 12:47:35 jdarcy: if thats all you have for now, we'll discuss more tomorrow? 12:47:43 Little progress has been reported to me from others (who are all busy on other things). For my own part, I've been trying to refactor some of my patches to support server-side AFR/EC as well as NSR. 12:47:57 jdarcy: Have we had a direct chat to the dev's that submitted the 7k lines of code, about how it's not a very good approach? They *could* just need some firm guidance.. 12:48:15 I got some interesting results from that, which I'll be reporting tomorrow. 12:48:26 Cool :) 12:48:35 JustinClift: Yes, I'll be conveying that message to the authors directly. ;) 12:48:39 :) 12:50:10 jdarcy: more on 4.0, or continue in tomorrows meeting? 12:50:20 Nothing more for 4.0 12:50:27 jdarcy: thanks :) 12:50:31 #topic Other Agenda items 12:50:51 #info subtopic Upcoming Events 12:51:05 reminder to update https://public.pad.fsfe.org/p/gluster-events 12:51:19 #info subtopic: GSOC 2015 12:51:37 kshlm: got a status update on this? 12:52:07 JustinClift: or you? 12:52:15 Yup. 12:52:16 ndevos, its kshlm 12:52:28 I submitted the org application, with the help of spot. 12:52:33 Now we wait. 12:52:43 how much ? 12:52:55 Imean when is the result expected? 12:53:01 announcement* 12:53:05 In the meantime, can we get more volunteers for mentors. 12:53:19 lalatenduM, I think a couple of weeks. 12:53:21 ok 12:53:24 Give me 1 sec. 12:53:39 kshlm: Keeping pinging gluster devel mailing list about it 12:53:52 kshlm: And a few blog posts wouldn't hurt either ;) 12:54:11 I'm terrible at blogs. 12:54:37 lalatenduM, The student applications open on Mar16, so the org decisions should be out by then. 12:54:49 kshlm, cool 12:54:56 kshlm: You're fine at blogs. We can get proof readers for you too 12:55:01 kshlm: okay, nice, anything else? 12:55:13 Nothing else. 12:55:20 thanks! 12:55:27 #info subtopic: Website practical plans 12:55:34 tigert: you're up! 12:55:46 woot! 12:55:48 Mail thread for reference: http://www.gluster.org/pipermail/gluster-infra/2015-February/000772.html 12:56:17 Debloper, ^^^^ 12:56:20 o/ 12:56:20 tigert, Debloper is the person who sent that mail to gluster-infra 12:56:36 Debloper++ for the blog :) 12:56:38 so Debloper made a nice summary of the website issues and what we should do in the blog 12:56:38 I'd let tigert go first, please 12:56:43 indeed Debloper++ 12:56:45 thanks, lalatenduM :) 12:57:22 I'm on prototyping some ideas, will be able to show something shortly to gather feedback. 12:57:25 and I think, since we should keep this short, is to mostly agree to meet and try lay down some plan to proceed in practice 12:57:37 tigert++ 12:57:39 or maybe have an etherpad or such for this 12:57:49 so we can discuss this, the mailing list works too of course 12:58:16 * Debloper thinks it'd be better to try something more full duplex for ideation 12:58:28 why not IRC, devel channel? 12:58:31 but one thought I and davemc had when we discussed the site issues during a meeting 12:58:41 (then take the notes on etherpad) 12:58:41 an irc channel might work too, but lets not split things up too much 12:58:52 IRC is ok for ideation <-- as long as the results go on the mailing list 12:59:10 * hagarth needs to drop off now, ttyl folks 12:59:15 so the idea is a gluster "shop" 12:59:19 hagarth: _o/ 12:59:21 tigert: start with a mailinglist discussion, and summarize it in an etherpad with an IRC meeting to finalize it? 12:59:40 tigert: please, do send me all the resources & historic discussions that I might have missed (as mail?) 12:59:52 like a phone shop or applestore or whatever - front room is the sales and showcase where you get started, 13:00:16 and there is your "Pitch" 13:00:23 and instructions to get started 13:00:32 now with docs shaunm will be helping us with his experience 13:00:34 As long as it's not following the Gnome approach, should be ok 13:00:39 ndevos: mailing list discussion is there, next is IRC fire-chat & then takeaway the bullet point actions 13:00:55 tigert: yes, I like that idea. let's catch up sometimes. 13:01:10 behind the front room is the "genius bar" where the community lives, where you get more in depth stuff, and get involved 13:01:15 but yeah 13:01:25 let's not take too much meeting footage (unless it's okay) 13:01:34 tigert Debloper: Any interest in having the discussion on gluster-users as well as gluster-infra? eg to engage the end user audience 13:01:38 should we have an irc meeting to sync? 13:01:50 well, we're running over time now - this was the last item on the agenda :) 13:01:56 we could of course move the discussion to gluster-users 13:01:57 yeah 13:02:03 JustinClift: I'm not familiar with the mailing list policies, but i don't know why should there be any problem 13:02:17 in fact, I'd agree to early user testing the staged revamp 13:02:20 ndevos: lets close the official one and we can chat about this last item off record? 13:02:43 * JustinClift nods 13:02:47 tigert: I suggest to create a proposal together with Debloper and whoever will work with you 13:03:00 ndevos: agreed 13:03:08 send that proposal to the -users list and get their opinion 13:03:21 ndevos: ack 13:03:22 maybe have a irc meeting with interested users too 13:03:28 o/ 13:03:42 we'll do that 13:03:54 now, when you want to discuss that proposal, is really up to you :) 13:04:01 * krishnan_p needs to drop off now if he wishes to reach home in one piece 13:04:04 yeah 13:04:05 :) 13:04:13 krishnan_p: Good luck :D 13:04:18 we'll finish teh meeting now, and you can start your own meeting after that 13:04:22 JustinClift, thanks :) 13:04:37 ndevos: cool, I'll catch up with tigert & we'll get back with update on this. 13:05:10 Debloper: yeah, sounds good, but please discuss in this channel and do a #startmeeting to get some logs for it 13:05:14 #endmeeting