15:02:42 #startmeeting Weekly GlusterFS Community Meeting 15:02:42 Meeting started Wed Jun 4 15:02:42 2014 UTC. The chair is JustinClift. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:02:42 Useful Commands: #action #agreed #halp #info #idea #link #topic. 15:02:49 #topic Roll Call 15:02:50 * kkeithley_ is here 15:02:55 * hagarth is here 15:03:19 * ndevos is here 15:03:43 where is the agenda today? 15:03:56 * lalatenduM is here 15:03:57 ndevos: fsfe etherpad i think 15:03:59 https://public.pad.fsfe.org/p/gluster-community-meetings 15:04:00 Title: FSFE Etherpad: public instance (at public.pad.fsfe.org) 15:04:06 thanks! 15:04:09 kkeithley_: Thx :) 15:04:29 #topic Action items from last meeting 15:04:38 "JustinClift to email gluster-devel and gluster-users, to get people testing 3.4.4 beta. We want positive confirmation it's good before releasing." 15:04:41 Done 15:04:55 Ben Turner has been testing 3.4.4. Positive results. 15:05:10 * JustinClift guesses we're good to proceed with 3.4.4 final 15:05:19 "pranithk to email gluster-devel, starting a mail thread about "sub-maintainers to publish and curate easy to solve bugs for more community involvement". We want a plan of action as the result, and we'll take it from there." 15:05:40 Is that Pranith's "Initiative to increase developer paritcipation" thread? 15:05:42 JustinClift: I sent a mail 15:05:51 so what are the next steps for this? 15:05:58 JustinClift: I also talked to 3 guys in the team who want to help out with some bugs 15:06:08 Cool. 15:06:09 I think we should have a permanent link on gluster.org 15:06:19 JustinClift: I think we should reach out to the professor from China 15:06:20 which talks about EasyFix bugs 15:06:31 Good idea 15:06:37 hagarth: It would be nice if you sent the mail IMO 15:06:40 send* 15:06:53 pranithk: will do that 15:06:53 hagarth: yes 15:06:55 * lpabon here 15:06:55 hagarth: It seems he developed some new modules 15:07:00 Do we have page(s) on the website/wiki discussing it yet? 15:07:08 JustinClift: about what? 15:07:10 If not, yeah, getting that added would be cool 15:07:25 JustinClift: He is still with 3.2.7 15:07:28 pranithk: And yeah, I remember scanning that email about the prof in China 15:07:43 pranithk: What kind of reaching out do you feel we should do? 15:08:09 JustinClift: We should ask him to contribute to upstream by sending patches of what he developed... 15:08:16 hagarth: Can you please create an action item about the sending of the email :) 15:08:19 JustinClift: We can then rebase it on master... 15:08:19 pranithk, ndevos: do we have bugs tagged EasyFix ready? 15:08:35 hagarth: ndevos tagged one 15:08:56 #action hagarth to send an email to professor in ihep.ac.cn 15:08:56 hagarth: I've started to tag some, lalatenduM already assigned on to himself, and vikhyat took one too 15:08:57 pranithk: Cool. Do you want me to do it, or are you ok to do it, or ? 15:09:07 Heh, hagarth to do it :) 15:09:27 it would be nice to create a short URL for EasyFix bugs and link it from gluster.org developer page 15:09:32 k, we need to get the info on the website too 15:09:33 I can help out to triage easy fix bugs 15:09:51 raghug: cool 15:09:52 Who would be a good person to create that page on the website? 15:09:59 * JustinClift wonders if Eco 15:10:15 JustinClift: should it be somebody who is a regular to the weekly meetings? 15:10:33 hagarth: Probably a better idea 15:10:58 hagarth: Do we need it to be someone regular? 15:11:09 hagarth: We just need a url with a list of bugs? 15:11:20 pranithk: no, we need to add it to the gluster.org page 15:11:32 #link https://bugzilla.redhat.com/buglist.cgi?bug_status=NEW&keywords=EasyFix&keywords_type=allwords&product=GlusterFS&query_format=advanced 15:11:33 Title: Bug List (at bugzilla.redhat.com) 15:11:37 or, maybe 15:11:48 hagarth: What is it that we are going to add? just link would be good enough? which is just a one off? 15:11:54 ndevos: http://goo.gl/Es1r22 15:11:55 #link http://red.ht/1x7dJ8H 15:11:56 Title: Bug List (at goo.gl) 15:11:56 Sure. We need a page to explain that link and what EasyFix is about though 15:11:57 Title: Bug List (at red.ht) 15:12:10 JustinClift: Ah! 15:12:11 hagarth: use bit.ly, it makes a nice red.ht link :) 15:12:13 Unless we add it to the existing Develop page? 15:12:44 ndevos: goo.gl gives you interesting statistics :) 15:12:54 hagarth: bit.ly too! 15:12:56 JustinClift: I think we can add it to the existing developer page 15:12:59 ndevos: ah ok! 15:13:00 By "Develop" I'm meaning I know there's a page on the wiki with info for developers. It would probably be appropriate there. 15:13:05 hagarth: Yeah 15:13:09 k. 15:13:28 #action pranithk to add information about EasyFix to the existing Developer page 15:13:32 ;) 15:13:37 cool ;) 15:13:46 hagarth: but, I dont remeber how to get them :D 15:13:54 "hagarth to start discussion on showcasing Gluster users and developers" 15:14:04 I don't know the status of this 15:14:09 JustinClift: I know ;) 15:14:23 ;) 15:14:27 we need to add a page with details of prominent Gluster users and developers 15:14:40 I am wondering if it is better to add when staging.gluster.org becomes live 15:14:57 depends on the timeframe? 15:15:21 ndevos: right, we have an agenda item for the timeframe of staging.gluster.org 15:15:21 hagarth: Do we have the list of users / developers to put on the site? 15:15:36 CentOS! 15:15:44 JustinClift: We can pull that out easily 15:16:01 hagarth: Lets get that pulled out and ready then 15:16:12 hagarth: We can format it for the existing site fairly easily 15:16:27 And then we'll just update it for the new site when that's closer to ready 15:16:49 JustinClift: sounds good 15:16:51 ndevos: No idea about timeframe atm 15:16:56 hagarth: AI it ;) 15:17:18 #action JustinClift to ask Eco when new site is targetted for roll out 15:17:47 #action hagarth to work with the team for adding a web page on details of prominent community members 15:17:59 We should also update the front page of gluster.org to point to this new users/developers page 15:18:21 That'll help brand new people see the list early on 15:18:29 JustinClift: who can do that? 15:18:56 _Probably_ anyone with WordPress admin access to gluster.org 15:19:06 I'm not sure though 15:19:25 ndevos pointed out a bug in the template (missing 3.5.x links) the other day. I haven't yet looked into that. 15:19:26 JustinClift: we can possibly take this discussion to gluster-infra 15:19:30 Good idea 15:19:44 the shadow^h^h^h^h^h^hjohnmark knows 15:20:25 #action JustinClift to start the discussion on gluster-infra about updating links on the main gluster.org website. re 3.5.x links in template & the new Prominent Gluster Users page 15:20:31 (that's a long AI) 15:20:44 "JustinClift to ask Eco if he has time/inclination to do a "Who Wrote GlusterFS 3.5" (using gitdm, etc) in similar vein to the Linux version" 15:21:09 Ahhh... Emailed Eco about this earlier today. My fault for not looking at my AI's earlier on. ;) 15:21:20 Will report back next week 15:21:48 #action JustinClift to report back if Eco will do the Who Wrote GlusterFS 3.5 page 15:21:55 "JustinClift to update the rackspace build scripts to enable --debug" 15:21:56 Done 15:22:05 I'm still working on the slaves though. :/ 15:22:32 I seem to have killed slave0 and slave 1 today. Working through that today. 15:22:39 "JustinClift to discuss with hagarth + Mgmt if a new approach to prioritisation is needed" 15:22:54 Not done. 15:23:03 hagarth: Do you have time to discuss after this meeting? 15:23:15 JustinClift: maybe later this week? 15:23:45 hagarth: k. Can you send me a meeting invite? 15:24:03 Anything after about 12:00 (midday) UK time will be ok. :) 15:24:34 "JustinClift to stir up beta testers for 3.5.1 beta. eg mailing lists, private email, etc" 15:24:59 Several people/places are telling me they're working on it. "Results soon" 15:25:16 "could be next week" though is what that seems to mean. 15:25:27 If Ben Turner can get results back to us faster, that would be good. 15:25:29 Thoughts? 15:25:52 sooner than later would be good 15:26:07 We need a new community leader to organize Gluster Test Days 15:26:22 there is one issue with the beta that I know of, I've added that to the 3.5.1 topic in the agenda 15:26:43 kkeithley_: +1 15:26:57 k 15:27:04 "JustinClift to get the Westford lab mac mini doing nightly GlusterFS build tests happening (cron). Failure emails to gluster-devel I guess" 15:27:21 I haven't touched this yet. Punting it to next week 15:27:29 #action JustinClift to get the Westford lab mac mini doing nightly GlusterFS build tests happening (cron). Failure emails to gluster-devel I guess 15:27:36 #topic 3.4.4 15:28:03 kkeithley_: With the positive feedback from Ben Turner, do you reckon releasing 3.4.4 final is a go? 15:28:09 * ndevos needs to leave in some minutes, please post 3.5.1 notes in the meeting minutes 15:28:27 Lets do 3.5.1 first then 15:28:29 #topic 3.5.1 15:28:53 ndevos: Are you ok to a 3.5.1beta2 using the new patches (once they're merged)? 15:29:00 We'll ask people to test that instead? 15:29:31 yes, if http://review.gluster.org/7963 gets merged soon, I can do a beta2 this week 15:29:32 Title: Gerrit Code Review (at review.gluster.org) 15:29:38 probably Friday 15:30:12 ndevos: wait 15:30:22 * ndevos waits 15:30:27 ndevos: We found an important gfid problem when geo-replication is in place 15:30:43 ndevos: It is present in 3.5 as well as far as I can remember 15:30:50 pranithk: which problem is this? 15:30:52 Ahhh. 15:30:59 hagarth: http://review.gluster.org/7978 15:31:00 Title: Gerrit Code Review (at review.gluster.org) 15:31:10 pranithk: hmm, okay and that can get hit easily? 15:31:13 ndevos: VERY easily 15:31:27 ndevos: I didn't know how this was never hit :-( 15:31:55 * JustinClift just emailed gluster-devel and gluster-users asking for reviewers for those two 15:32:01 pranithk: yeah, would be good to have this in 3.5.1 15:32:24 pranithk: if there are no bugs against the glusterfs-3.5.1 blocker, I'm likely not (very) aware of the issue 15:32:27 hagarth: Would be must have IMO 15:32:37 If we get those two reviewed, then 3.5.1 beta2 is ready to go? 15:32:37 ndevos: We found it only today 15:32:41 pranithk: yeah 15:32:44 pranithk: can you file a new bug and add glusterfs-3.5.1 in the 'blocks' field? 15:32:52 ndevos: Will do 15:33:14 pranithk: thanks! 15:33:36 prk. Well feedback for 3.5.1 beta1 is no longer relevant 15:33:53 prk? 15:33:59 Typo ;) 15:34:06 (ignore that bit) 15:34:26 We'll seek testers for 3.5.1 beta2 once the new patches are incorporated. 15:34:32 JustinClift: cool 15:35:43 That all for 3.5.1 topic? 15:35:50 * JustinClift suspects so 15:35:55 k, back to 3.4.4 15:36:12 kkeithley_: 3.4.4 final. When's good? 15:36:34 topic? 15:36:47 #topic 3.4.4 (again) 15:36:52 kkeithley_: 3.4.4 final. When's good? :) 15:36:54 okay, thanks guys, I'm dropping off, cya! 15:37:01 ndevos: Thanks :) 15:37:29 #topic 3.4.4 15:37:36 I can push the buttons if everyone is happy. 15:37:58 +1 15:38:10 Any objections? 15:38:27 +1 15:38:46 #action kkeithley_ to release 3.4.4 15:39:17 #action ndevos to release 3.5.1 beta2 when the required patches are merged 15:39:25 (hopefully friday or early next week) 15:39:55 #topic Other items 15:40:07 "Website progress update?" 15:40:15 * JustinClift was hoping Eco would be here 15:40:31 But no. Next item... 15:40:36 "Port Maintainers" 15:40:39 Who's is this? 15:40:55 JustinClift: What is port maintainers? 15:41:00 * hagarth added that 15:41:11 JustinClift: before we get to port maintainers 15:41:23 I would like to discuss website progress update 15:41:27 I'm here in BLR and will walk through community packaging with Humble and lala tomorrow or Friday so that they can take over that task from me 15:41:28 * kkeithley_ wonders is his internet connection is failing 15:41:30 Btw everyone, please put your names into the wiki name box thing. I can't tell who belongs to which colour ;) 15:41:44 hagarth: Cool 15:41:52 kkeithley_: Sure 15:42:09 I think the community needs to be informed about the schedule for updating the website 15:42:15 hagarth: Agree 15:42:26 * Humble : kkeithley_ :) 15:42:28 It's been assigned to Eco for ages. 15:42:49 JustinClift: how do we gather status on that one? 15:42:58 He wasn't around for a while, but came back recently and got this working after some initial repo problems 15:43:10 I've emailed him to ask for an ETA 15:43:34 If we don't see good progres though, I'm inclined to put someone else in charge of the task 15:43:46 JustinClift: I am facing a lot of queries on the website and would be good to have some answers for those queries :| 15:43:50 :) 15:44:26 hagarth: Lets discuss tomorrow, after we've heard back from Eco 15:44:33 JustinClift: sure, sounds good 15:44:58 #action JustinClift and hagarth to discuss website schedule tomorrow/friday, after progress report from Eco 15:45:16 Next item? 15:45:35 sure 15:45:36 "Port maintainers" 15:45:42 hagarth: Go for it 15:46:01 I brought about the topic of adding maintainers for various ports (NetBSD, Mac OS etc.) a few weeks back 15:46:09 I have some updates on that one 15:46:16 #action kshlm to report on forge alternatives 15:46:25 ^^^ Just before I forgot ;) 15:46:32 Cool 15:46:36 kkeithley_, cool :) 15:46:40 Please share the updates 15:46:45 any one know whether the dynamic blog listing/pulling will work with staging.gluster.org? 15:46:56 Emmanuel, Harsha and Dennis have agreed to be official maintainers for NetBSD and Mac OS respectively 15:47:06 Excellent 15:47:19 I will send out a note on the mailing lists tomorrow 15:47:35 If we have some volunteers for FreeBSD, please let me know. 15:47:36 Humble: The new website is statically generated. But it could be cronjobbed (or similar) to pick up new content I guess 15:48:02 GlusterFS doesn't work on FreeBSD any more does it? 15:48:25 JustinClift, yeah, I read the new one is static, so the query :) 15:48:37 Missing functions in the kernel or something? (same ones as the OSX prob from memory) 15:48:38 we had someone who did a port to FreeBSD as a GSOC project last year. 15:48:43 JustinClift: it used to work on FreeBSD, need more testing though. 15:48:52 I tried to get him to submit it as a patch but he ran out of time. 15:49:08 k. So we need someone to pick that up and run with it 15:49:17 Lets ask on the mailing lists/twitter/etc 15:49:24 I need to do that, or point someone who has time at the repo where it lives. 15:49:31 JustinClift: sure, sounds good. 15:49:39 kkeithley_: would we be able to reach that developer? 15:49:55 not sure, but I have a link to his github repo with the work 15:49:59 #action kkeithley_ to give JustinClift the details of where the FreeBSD port code lives 15:50:05 I'll dig it up and share it 15:50:31 #action JustinClift to canvas for people to pick up the FreeBSD port code and get it merged/working with master 15:50:35 kkeithley_: Tx 15:51:19 #action hagarth to email gluster-users and gluster-devel with the details of the new Port Maintainers 15:51:40 Anyone else have items for the agenda? 15:51:56 3 15:51:59 2 15:52:00 JustinClift: hang on 15:52:04 :) 15:52:05 #topic 3.6 15:52:11 Go for it 15:52:18 we have 2 more weeks for feature freeze of GlusterFS 3.6 15:52:34 Good point. Can you send a reminder to gluster-devel about that? 15:52:48 JustinClift: will do. I don't foresee more extensions :) 15:53:04 let us ship 3.6 with the content that we have on Jun 21st. 15:53:45 Sounds like a plan :) 15:54:34 lalatenduM: thanks for putting together the ToC for operations guide 15:54:41 #action hagarth to email gluster-devel, reminding them that 3.6.1 feature freeze is in 2 weeks 15:54:57 we need to figure out how we can make the operations guide real 15:55:11 JustinClift: s/3.6.1/3.6.0/ ;) 15:55:18 Gah 15:55:20 hagarth, u r the inspiration :) 15:55:30 #action hagarth to email gluster-devel, reminding them that 3.6.0 feature freeze is in 2 weeks 15:55:50 lalatenduM: it is easy to inspire, harder to make it real :) 15:56:29 hagarth, :), yeah long way to go 15:56:57 lalatenduM: maybe we should track progress in this meeting 15:57:08 hagarth, yes we should 15:57:09 lalatenduM++ hagarth++ on op.guide :) 15:57:30 one more discussion point 15:57:36 raghug: and I are finding leak after leak in gfid-access 15:57:54 yeah, just found one 15:58:11 * JustinClift wonders if that's where the reported huge mem usage of glusterfs is coming from 15:58:16 (serveral reports on mailing list) 15:58:16 hagarth: We need to see why valgrind is not able to launch bricks and run properly 15:58:17 I intend sending out a monthly statistics of patches sent, patches reviewed etc. on gluster-devel 15:58:26 pranithk: absolutely 15:58:30 JustinClift: Oh yes! 50GB one 15:58:37 f.a.r.k. 15:58:44 would the statistics be of interest? 15:58:47 hagarth, good idea 15:59:10 devs should get recognized for their hard work 15:59:16 pranithk raghug: Do you reckon we can get fixes for this into 3.5.2 ? 15:59:25 JustinClift: Simple fixes 15:59:27 JustinClift: yes 15:59:31 Whew 15:59:32 lalatenduM: absolutely, all community contributors need to be recognized :) 15:59:33 JustinClift: I guess we must! 15:59:51 we probably have to review gfid-access once 16:00:00 raghug: Agreed 16:00:04 raghug: +1 16:00:07 not sure I want to extend 3.4, but do these leaks exist there too? 16:00:10 #action ndevos to check with pranithk and raghug whether the fixes for the gfid memory leaks are ready for 3.5.2 16:00:15 kkeithley_: no 16:00:19 kkeithley_: Very good point. 16:00:21 Cool 16:00:23 kkeithley_: It is introduced in 3.5 16:00:30 okay 16:01:25 lalatenduM: For the "devs should get recognised", there's an item we're looking into now for creating a "Who wrote GlusterFS 3.5?" page, similar to the Linux one here: 16:01:40 https://www.google.co.jp/search?client=opera&q=who+wrote+linux+3.5&sourceid=opera&ie=UTF-8&oe=UTF-8 16:01:42 Title: who wrote linux 3.5 - Google 検索 (at www.google.co.jp) 16:01:46 Gah. Wrong link 16:01:49 https://lwn.net/Articles/507986/ 16:01:51 Title: Who wrote 3.5 [LWN.net] (at lwn.net) 16:02:10 Anyway, we'll get that done. Other ideas are appreciated too. :) 16:02:21 We're out of time everyone. 16:02:26 No other items? 16:02:33 3 16:02:34 no more from me 16:02:38 Cool 16:02:45 #endmeeting