15:02:09 #startmeeting Weekly GlusterFS Community Meeting 15:02:09 Meeting started Wed Jun 11 15:02:09 2014 UTC. The chair is JustinClift. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:02:09 Useful Commands: #action #agreed #halp #info #idea #link #topic. 15:02:17 k, who's here? :) 15:02:18 * kkeithley is here 15:02:22 * hagarth too 15:02:27 * JoeJulian is 15:02:32 * ndevos is here, after all 15:02:36 * xavih is here 15:02:50 * Eco_ is here as well 15:03:03 Cool. :) Lets start 15:03:05 * hchiramm_ is here 15:03:14 #topic Agenda items from last week 15:03:24 "hagarth to send an email to professor in ihep.ac.cn" 15:03:28 Punted to next week 15:03:29 * raghug is here 15:03:35 "pranithk to add information about EasyFix to the existing Developer page" 15:03:38 pranithk: ? 15:03:59 JustinClift: Sorry Didn't get time this week will do it on Friday :-( 15:04:09 np. Punted to next week. 15:04:18 "JustinClift to ask Eco when new site is targetted for roll out" 15:04:42 Done. Eco has provided (extensive) task list, but we still need to figure out good target date 15:04:46 JustinClift, DV set a push goal for two weeks, i need to work with you and misc on some of the technical details 15:05:20 Sure. If it's Ruby, I'll point you at misc for that. I don't know Ruby and have no (anti) interest in learning it. ;) 15:05:24 the most daunting tasks at this point are how to get the live feeds (blog, forge, bugs) to work into the static framework 15:05:26 But other stuff, sure 15:05:28 * lalatenduM_ is here 15:05:56 Eco_: I think it'll just need triggering of static rebuild when new content comes in. We'll discuss later 15:06:05 sounds good 15:06:08 "hagarth to work with the team for adding a web page on details of prominent community members" 15:06:13 In progress 15:06:35 hagarth: We did have a Community Member volunteer to help us yesterday with stuff 15:06:47 Eco_, can we have a "News" tab as well ? 15:06:52 It was part of the conversation around the GlusterFS Consultants page. 15:07:29 hchiramm_, the blog post is where most of that would go, is there a need for a seperate news feed as well? 15:07:29 hagarth: Rodrigo Gonzalez 15:08:00 hagarth: We could ask him to look on the Net for any substantial users we don't know about, and to help prepare the list of prominent members 15:08:10 hagarth: It's reasonably likely there are places we don't know about yet 15:08:20 between that, the bugs feed and the forge feed i think thats all the news about Gluster there is? 15:08:28 may be about gluster releases and events ? Eco_ .. 15:08:59 #action JustinClift or hagarth to ask Rodrigo Gonzalez if he'd like to assist with the prominent users page 15:09:09 hagarth1: Ahhh 15:09:25 hchiramm_, we will look into it if there is a need, most likely we will just add those items to one of the existing entries but no reason not to consider a news feed as well 15:09:28 hagarth: Here now? 15:09:38 JustinClift: yes 15:09:45 Eco_, thanks.. 15:09:53 k. We're just covering "hagarth to work with the team for adding a web page on details of prominent community members" 15:10:00 hagarth: We did have a Community Member volunteer to help us yesterday with stuff 15:10:07 hagarth: Rodrigo Gonzalez 15:10:12 hagarth: We could ask him to look on the Net for any substantial users we don't know about, and to help prepare the list of prominent members 15:10:16 hagarth: It's reasonably likely there are places we don't know about yet 15:10:28 hagarth: So I did this: #action JustinClift or hagarth to ask Rodrigo Gonzalez if he'd like to assist with the prominent users page 15:10:34 JustinClift: ok, cool 15:10:44 Cool. Anything else for that item? 15:11:33 k, guess not. Moving on 15:11:35 "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:11:47 * JustinClift completely forgot about that. Moved to next week 15:11:56 #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:12:13 "JustinClift to report back if Eco will do the Who Wrote GlusterFS 3.5 page" 15:12:34 Eco's looking into it. Sample output from git-dm here: http://fpaste.org/108945/ 15:12:36 Title: #108945 Fedora Project Pastebin (at fpaste.org) 15:12:59 DV also showed me ohloh.net last night 15:13:13 http://www.ohloh.net/p/glusterfs/contributors/summary 15:13:46 Ahh. 15:13:57 * JustinClift hasn't looked into the Ohloh contributors page 15:14:06 Wonder how it matches up... 15:14:22 There's github as well, https://github.com/gluster/glusterfs/graphs/contributors 15:14:23 Title: Contributors to gluster/glusterfs · GitHub (at github.com) 15:14:46 Eco_: That git-dm output looks useful. That could definitely be good info source for the Who Wrote GlusterFS 3.5 page. 15:14:53 Just needs to be padded out and commentary added. 15:15:05 stats for 3.5.0 to 3.5.1 can be gathered with: ./extras/who-wrote-glusterfs/who-wrote-glusterfs.sh v3.5.0...v3.5.1beta2 15:15:05 kshlm: Good thinking. :) 15:15:15 potentially all three 15:15:20 Yep 15:15:47 Eco_: So, you're good to get this Who Wrote GlusterFS 3.5 page done too? 15:16:21 JustinClift, with trepidation, yes ;) will need your help sorting out a few of the bits if you dont mind but once i have the data writing the article is simple 15:16:37 Eco: Cool. :) 15:17:03 #action Eco_ will create the Who Wrote GlusterFS 3.5 blog post/page 15:17:10 Eco_: ETA? 15:17:14 this will have to wait until after the site release though since that is my main focus given the short time frame 15:17:26 Sure 15:17:34 Clear priority :) 15:17:35 say three weeks, two weeks for site launch one week to write article 15:17:42 Works for me 15:17:48 k, next item 15:17:57 "JustinClift to get the Westford lab mac mini doing nightly GlusterFS build tests happening (cron). Failure emails to gluster-devel I guess" 15:18:05 Didn't even start this. Moving it to next week 15:18:07 :/ 15:18:16 #action JustinClift to get the Westford lab mac mini doing nightly GlusterFS build tests happening (cron). Failure emails to gluster-devel I guess 15:18:19 those mac minis are very old 15:18:30 G4? 15:18:36 and you will need to get the latest jaguar or whatever cat name mac uses now 15:18:37 Eco_: The one I'm thinking of is um... 2011 or 2012 15:18:39 no, core 2 15:18:55 Mavericks is a cat ? 15:18:56 2011 i think i ordered them 15:19:12 kkeithley, shows how much i keep up with apple products ;) 15:19:20 2011 is still withing support for everything 15:19:33 They should be fine (with appropriate ram upgrade) 15:19:34 yeah just the OS needs to be updated from what is on them 15:19:46 ram should be 2G so would be good to have more 15:19:47 Eco_: Hmmm, when you say "them"... I'm only aware of one 15:19:53 Are there more? 15:19:58 * johnmark listens in 15:19:59 there were three all told 15:20:03 yeah, Mavericks needs more than 2GB 15:20:11 i have one so there should be two left 15:20:25 Interesting. Let's look into this 15:20:39 if not, one may have fallen off a truck at some point during all the moving but that is my recollection 15:20:45 #action JustinClift to look into the "other Mac Mini's" we might have lying around 15:20:51 Eco_: Sure 15:20:53 JustinClift: is the bitergia dashboard interesting? 15:20:57 it pulls from the same repo 15:21:05 johnmark: For Mac Mini? 15:21:17 Ahhh. 15:21:20 heh :) 15:21:21 * pranithk happy to see johnmark :-) 15:21:21 Different topic 15:21:26 sorry, was looking backwards 15:21:26 to get the stats on where the other mac mini is ;) 15:21:30 lol 15:21:35 Eco_: precisely 15:21:38 pranithk: howdy :) 15:22:13 johnmark: Um, guessing you mean for the leaderbaord thing? Yeah, it'll be useful source for the mailing list leaderboard. That's likely all though. 15:22:23 Anyway, this should prob be in "Other Agenda Items" ;) 15:22:26 JustinClift: ok 15:22:36 don't mind me :) 15:22:42 ;) 15:23:07 Eco_ kkeithley: Are either of you near Westford? 15:23:13 not in the slightest 15:23:25 6000 km or so 15:23:27 * JustinClift is thinking "who could install ram upgrade in the Mac Mini?" 15:23:29 k 15:23:45 We'll come to that some other time then :) 15:23:48 JustinClift: kkeithley will be there next week 15:23:51 I'm flying home in about 8 hours 15:24:07 Cool, good to know 15:24:18 kkeithley: woohoo 15:24:19 kkeithley will be the ram installer then most likely ;) 15:24:26 Anyway, moving on... 15:24:29 JustinClift: can we talk about Gluster++ 15:24:32 ? 15:24:42 Now? 15:24:50 JustinClift: not necessarily 15:24:57 JustinClift: just at some point 15:24:58 is that the rewrite in C++? 15:25:00 Can you wait until the end of the meeting? 15:25:02 lol 15:25:03 Or in Apple Swift? 15:25:06 JustinClift: yes. geez... 15:25:15 We have an agenda. ;) 15:25:24 "kkeithley_ to release 3.4.4" 15:25:24 JustinClift: goodie! ok, then 15:25:34 Done. Thanks Kaleb. :) 15:25:47 We should get blog item on the website about it 15:25:56 guys what will we do about the crash seen by Joe? shall we release one more? 15:25:56 * JustinClift looked quickly, didn't see one 15:26:17 by Joe I mean JoeJulian of course 15:26:30 If there are crashes with 3.4.4, then I'm inclined to make a 3.4.5 when a patch becomes available 15:26:41 JustinClift: I have already backported the patch 15:26:43 JustinClift: I already gave +1 on the patch. 15:26:50 Cool 15:27:03 How bad is the crash, and should we release 3.4.5 immediately? 15:27:07 hagarth, yeah saw that, nice :) 15:27:18 JustinClift: the crash is present in all of 3.4.x 15:27:23 JoeJulian: what do you say? 15:27:36 but it would be nice to release 3.4.5 soon for more reasons than one 15:27:38 I think it's pretty severe, so yeah, release the patch. 15:27:39 hagarth: How confident are we that this patch doesn't break things? 15:27:42 just to make sure we are talking abt the same bug https://bugzilla.redhat.com/show_bug.cgi?id=1022510 15:27:44 Bug 1022510: urgent, urgent, ---, rgowdapp, NEW , GlusterFS client crashes during add-brick and rebalance 15:27:48 I'll be testing it in staging tomorrow. 15:27:50 I like a release which has n.n+1.n+2 ;) 15:27:56 eg should we just do 3.4.5 today, or do we beta it first? 15:27:59 hagarth: hehe 15:28:04 Beta it. 15:28:09 JustinClift: I am sure there will be no side effects 15:28:09 k, lets do that 15:28:15 JustinClift: let Joe confirm it and then we can do the release 15:28:15 I'll test it and add my comments. 15:28:26 JoeJulian: thanks 15:28:44 k, can we push out a 3.4.5 beta1 tarball today/tonight? 15:28:57 Which JoeJulian can do the testing of tomorrow 15:29:14 And we'll push out 3.4.5 release after that, depending upon test result? 15:29:29 Feasible approach? 15:29:29 ugh, you guys are making me crazy 15:29:42 Didn't take much effort, that. 15:29:47 kkeithley: what are you worried about? you'll be on a plance 15:29:49 JustinClift: let us leave it to kkeithley to determine the schedule 15:29:51 would a 3.4.4-2 with the patch? 15:30:00 kkeithley: Sure 15:30:07 You're our 3.4.4 guy :) 15:30:12 3.4.x guy 15:30:16 (brain-o) 15:30:18 kkeithley: Didn't you teach humble/lala about releasing rpms? 15:30:33 ... the worst part is, I'm stuck using debs. 15:30:42 pranithk, yup :) 15:30:43 yes, but building rpms isn't the same as doing a 3.4.x release though 15:30:58 kkeithley: hmm... 15:31:13 pranithk, once the tar ball is available we can build rpms out os it 15:31:15 Heh, sounds like you need to educate them on the "doing a release" then too 15:31:17 kkeithley: btw, do you do release notes for 3.4.x? 15:31:19 s/os/of/ 15:31:24 JustinClift: +1 15:31:35 I'm just saying, if the patch is super critical, we can spin rpms with a patch while 3.4.5 is baking 15:31:47 kkeithley: right, hence the -2 15:31:51 kkeithley+1 15:32:01 there was a -2 somewhere? 15:32:06 kkeithley: Sounds like a plan to me 15:32:10 oh, sorry, it's late 15:32:11 kkeithley: sigh... 3.4.4-2 15:32:13 kkeithley: He's meaning the -2 in 3.4.4-2 15:32:15 or something 15:32:15 yes 15:32:18 got it 15:32:27 k, lets do that 15:32:47 JoeJulian: If the test results tomorrow with patch are good 15:32:52 Then kkeithley can make 3.4.4-2 15:32:56 JoeJulian, I believe you would need rpms for CentOS 6 right? 15:33:02 but first we have to finish building 3.4.4-1 rpms for download.gluster.org 15:33:11 lalatenduM_: I guess debs 15:33:13 lalatenduM_: No, debs. :( 15:33:32 * JustinClift is now confused 15:33:33 ohh, who make debs then? 15:33:33 I'm working with semiosis to figure out how that's done. 15:33:42 Ahh 15:33:56 JoeJulian, I thought you use rpm based distro 15:34:06 when did you move to debs 15:34:07 ? 15:34:08 Humble can finish 3.4.4-1 rpm building while I'm flying 15:34:22 k. So we need semiosis to create suitable deb's-with-patch first, which you can then test with 15:34:27 Oh, lets do it this way: 15:34:34 lalatenduM_: I did up until 10 days ago when I changed jobs. 15:34:44 a) JoeJulian will test the patch when he gets the suitable debs 15:35:08 JoeJulian, congratulations for the new job :) 15:35:15 b) We'll spin 3.4.4-2 rpms when patch is confirmed good 15:35:22 (or not, if the results fail) 15:35:35 Makes sense to me. 15:35:40 And the patch will be in 3.4.5, whenever that comes out 15:35:56 (which will therefore go into every other binary type then based on 3.4.5) 15:36:01 k 15:36:26 #action JoeJulian to test extra patch on top of 3.4.4 and report success/failure 15:36:49 #action kkeithley to release 3.4.4-2 (with the extra patch) if JoeJulian's testing succeeds 15:37:00 k, next item 15:37:02 agreed 15:37:11 "ndevos to release 3.5.1 beta2 when the required patches are merged" 15:37:20 Done. 15:37:35 RPMS turned up in the repos today too 15:37:47 thanks Humble (and lalatenduM_ and kkeithley?) 15:37:57 yay! thanks everyone for that! 15:38:04 * JustinClift I did a blog post about it 1 min before this meeting started (super simple one), asking for testers 15:38:05 ndevos, np!! kkeithley++ 15:38:06 Humble, I only watched and cheered him on 15:38:15 kkeithley, :) 15:38:17 kkeithley, ++ :_) 15:38:21 JustinClift: re-tweeted ;) 15:38:27 hagarth: Tx :) 15:38:51 #link http://www.gluster.org/2014/06/glusterfs-3-5-1-beta2-ready-for-testing/ 15:38:55 "JustinClift and hagarth to discuss website schedule tomorrow/friday, after progress report from Eco" 15:39:27 Done. Discussed during meeting about team prioritisation and stuff on Tue. 15:39:35 "kshlm to report on forge alternatives" 15:39:39 kshlm: ? 15:40:12 Nope. I'm trying to get my 3.6 deliverables done. 15:40:26 ok. we need to take this on reather urgently 15:40:43 k. Do we have someone else who can investigate it? 15:41:14 johnmark: by when do we need a read out? 15:41:54 I had formed a list of the alternatives though. Someone can continue from there, https://gist.github.com/kshlm/fd884ae1df1e9b982252 15:41:55 Title: What should be done for GlusterForge? (at gist.github.com) 15:41:55 hagarth: well, because the forge is key to Gluster++, which I wanted to roll out this month, I was hoping we would have stuff identified pretty soon 15:42:02 kshlm: thanks 15:42:19 kshlm: cool, we could take it up from there 15:42:21 I can take it on, and that will be my parting gift to the community :) 15:42:26 johnmark, what is gluster++ ? 15:42:33 johnmark: we will never let you go ;) 15:42:43 hagarth: just when I think I'm out... 15:42:44 heh 15:42:44 kshlm: It's the last item for the Agenda 15:42:52 johnmark, lol 15:42:57 oh. didn't see that. 15:43:13 JustinClift: now? 15:43:14 k, we need to figure out what we're going to do with it 15:43:18 Hmmm, not yet 15:43:21 o 15:43:23 k 15:43:42 #action JustinClift to look into Gitorious alternatives 15:43:44 Fuck it 15:43:46 ;) 15:43:49 ha 15:43:59 * JustinClift always makes the recorded meeting minutes interesting 15:44:02 JustinClift: ok, let's discuss later - just you and me, man 15:44:18 "kkeithley_ to give JustinClift the details of where the FreeBSD port code lives" 15:44:22 All the cool people use gitlab 15:44:24 Done 15:45:01 "JustinClift to canvas for people to pick up the FreeBSD port code and get it merged/working with master" 15:45:20 kkeithley just gave me the info. Will get it done this week 15:45:29 #action JustinClift to canvas for people to pick up the FreeBSD port code and get it merged/working with master 15:45:41 "hagarth to email gluster-users and gluster-devel with the details of the new Port Maintainers" 15:45:48 To be done this week 15:45:55 #action hagarth to email gluster-users and gluster-devel with the details of the new Port Maintainers 15:46:03 "hagarth to email gluster-devel, reminding them that 3.6.0 feature freeze is in 2 weeks" 15:46:09 Done: http://supercolony.gluster.org/pipermail/gluster-devel/2014-June/041032.html 15:46:10 Title: [Gluster-devel] 3.6.0 feature freeze - reminder (at supercolony.gluster.org) 15:46:16 "ndevos to check with pranithk and raghug whether the fixes for the gfid memory leaks are ready for 3.5.2" 15:46:19 ndevos: ? 15:46:37 not sure where that came from? 15:46:59 maybe thats pranithk's? 15:47:02 ndevos: :-) It was there 15:47:10 ndevos: You merged raghug's patch 15:47:15 busted! 15:47:28 :O 15:47:36 ndevos: My patch is still under review :-) 15:47:39 * Eco_ spit takes 15:47:42 ndevos: http://meetbot.fedoraproject.org/gluster-meeting/2014-06-04/gluster-meeting.2014-06-04-15.02.log.html 15:47:44 Title: #gluster-meeting log (at meetbot.fedoraproject.org) 15:47:49 At 16:00:10 15:47:56 So, scroll back up a bit 15:48:28 pranithk: any patches missing to have that fixed? 15:48:29 ndevos: I think raghug's patch was the critical one IMO 15:48:39 pranithk: So, this still needs review for 3.5.1 beta ? 15:48:59 ... sounds like a beta3 will be needed 15:49:03 and, well, 3.5.2 will have some time, if 3.5.1beta2 is ok 15:49:17 JustinClift: I dont think we can fix all bugs in 3.5.1 :) 15:49:25 ndevos: +1 15:49:30 Heh 15:49:34 * JustinClift pulls a sad face 15:49:48 k, it's a 3.5.2 targeted patch then? 15:49:50 JustinClift: :-) I have 3 more patches I wanted to propse for the release 15:50:01 pranithk: For 3.5.1 beta3, or for 3.5.2 ? 15:50:02 JustinClift: I think we will release 3.5.2 pretty soon 15:50:07 Sure 15:50:16 pranithk: only very major issues can make it in 3.5.1, everything else gets pushed to 3.5.2 15:50:22 k, np 15:50:42 ndevos: I feel they are major but we can't delay the release IMO 15:50:47 So, what do do about this item... mark it as done I guess? 15:50:55 JustinClift: Yes I guess 15:51:06 pranithk: what are those patches? 15:51:12 are they related to gfid-access? 15:51:18 raghug: http://review.gluster.org/8015 15:51:19 Title: Gerrit Code Review (at review.gluster.org) 15:51:28 pranithk: okay, sounds good, patch proposal for release-3.5 is open, I'm just merging only the critical ones, if any at all 15:51:44 after 3.5.1 has been released, any sane patch can get in again 15:51:47 raghug: http://review.gluster.org/7981 15:51:48 Title: Gerrit Code Review (at review.gluster.org) 15:52:00 raghug: The gfid-access leak patch... 15:52:12 raghug: I am waiting on kotresh's patch to be merged 15:52:17 Can we let 3.5.1beta2 bake for a bit? I don't like rushing the release just because ndevos is going on holiday. 15:52:21 ok 15:52:29 JustinClift: I think we will have to get the patch reported by Tom also into 3.5.2 :-( 15:52:36 kkeithley: Apparently there are pretty critical bug fixes in it 15:52:39 JustinClift: s/Patch/bug 15:52:55 pranithk: Yeah, that makes sense to me 15:53:06 kkeithley: there was only one real issue with 3.5.1beta1, not sure how long we want to test beta2 15:53:29 kkeithley: So we want to get 3.5.1beta2 confirmed good/bad asap, so we can release 3.5.1 with the critical fixes 15:54:06 k, anyway, I think we're good for this item 15:54:09 kkeithley: also, we don't get much backing of our betas anyway. not sure how much good extra time will do 15:54:12 tbh 15:54:25 er s/backing/baking 15:54:40 johnmark: We do get some testing off-list 15:54:48 johnmark: I think Justin did a fabulous job this time to get good beta testing done. I wanna thank him for that! 15:54:50 JustinClift: good ot know 15:54:56 pranithk: nice! 15:55:01 JustinClift: you get a gold star 15:55:04 pranithk: np. 15:55:18 pranithk: We can likely do better, with a bit more co-ordination 15:55:26 JustinClift: that's awesome 15:55:29 * johnmark is happy 15:55:33 We didn't really make use of social media nor reach out as well as we could have 15:55:34 JustinClift: yes. Over time it should improve :-) 15:55:36 JustinClift: yeah, there's a lot more we can do 15:55:37 But, we'll get it 15:56:19 ok, next 15:56:24 * johnmark has to leave soon 15:56:34 #action JustinClift to think through then wiki-ise what steps we should do for getting more thorough beta testing, and draw up likely list of candidates to ping directly 15:56:39 k 15:56:48 johnmark: k, do the Gluster++ thing now 15:56:51 woohoo 15:57:10 ok, so the reason that the forge decision is so important, is because we're taking a "best of forge" approach to do a software bundle 15:57:33 Cool 15:57:41 Who's the lead for it? 15:57:43 including packaging of things like puppet-gluster, pmux, xavih's xlator 15:57:45 etc. 15:57:59 JustinClift: right now, no one. I guess you could call me the biz guy for this 15:58:04 Cool 15:58:11 but we need individual project owners to take up packaging for their stuff 15:58:27 my understaning is that purpleidea is packaging his puppet stuff 15:58:30 so that should be ok 15:58:47 not sure who would package pmux or the disperse xlator 15:58:54 or anythign else that's valuable 15:59:05 JustinClift: there's also glusterflow, whihc would be pretty interesting 15:59:32 anyway, the idea is to present the packaged goods in some way to show that it's abou tmore than just glusterfs 15:59:32 johnmark: disperse xlator is currently in review to add it to master branch 15:59:48 johnmark: Hmmm, I haven't had time to touch it in ages. Gerald Sternagl did some work on it recently, but it's still very alpha level 15:59:51 xavih: ok, good. but it won't appear in an extual release branch until 3.6 right? 16:00:04 JustinClift: that's fine, as long as it's labeled as such 16:00:04 johnmark: yes 16:00:10 Makes sense 16:00:14 Cool. 16:00:26 xavih: so this would give users the opportunity to use it in conjunction with the 3.5 releases 16:00:28 I've packaged some projects, maybe that helps? 16:00:29 http://copr.fedoraproject.org/coprs/devos/gluster-addons/ 16:00:30 Title: devos/gluster-addons Copr (at copr.fedoraproject.org) 16:00:31 What's the plan/approach to make it happen then? 16:00:36 ndevos: cool! 16:00:36 ndevos: Cool 16:00:46 JustinClift: sounds like ndevos has partially shown the way 16:00:49 ndevos, cool 16:01:04 ndevos == unintentional lead ;) 16:01:33 JustinClift: well, mostly for my own needs :D 16:01:34 lol 16:01:43 ndevos: wouldyou be able to add in a couple more packages? 16:01:51 johnmark: Do you have the list of what you want? 16:01:51 ndevos: because that's a pretty good base to start with 16:02:04 JustinClift: yes, what I just provided - puppet-gluster, pmux, disperse xlator 16:02:18 JustinClift: plus some of the projects ndevos just listed 16:02:28 JustinClift: and glusterflow :) 16:02:35 * hagarth will be dropping off now, so long folks 16:02:40 hagarth: thanks :) 16:02:43 hagarth: Thanks :) 16:02:45 cya hagarth 16:02:49 so... 16:03:08 johnmark: Are you ok to bring it up on gluster-devel, so it can be worked out there? 16:03:16 JustinClift: +1 16:03:18