15:10:44 <JustinClift> #startmeeting Weekly Gluster Community Meeting
15:10:44 <zodbot> Meeting started Wed Jun 25 15:10:44 2014 UTC.  The chair is JustinClift. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:10:44 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
15:10:56 <JustinClift> k, roll call.  Who's here? :)
15:10:56 * ndevos \o/
15:11:11 * kkeithley is here
15:11:13 * jdarcy is.
15:11:16 * xavih is here
15:11:46 * semiosis here
15:11:49 * Eco_ present
15:11:59 <JustinClift> Cool
15:12:04 <JustinClift> Etherpad URL: https://public.pad.fsfe.org/p/gluster-community-meetings
15:12:05 <glusterbot> Title: FSFE Etherpad: public instance (at public.pad.fsfe.org)
15:12:17 <JustinClift> #topic Agenda items from last meeting
15:12:38 * shyam is here
15:12:45 <JustinClift> Hmmmm, no hagarth here yet
15:12:51 * dlambrig here
15:12:56 <JustinClift> We'll skip his until he gets here
15:13:09 <JustinClift> So, non-hagarth agenda items for the moment
15:13:18 <JustinClift> "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:13:20 <ndevos> hagarth mentioned he'll join a little later
15:13:26 <JustinClift> ndevos: Yeah
15:13:41 * JustinClift hasn't started this discussion yet
15:14:14 <JustinClift> Although we heard back from Rodrigo Gonzalez, who's interested in helping make the Prominent Gluster Users page
15:14:27 * JustinClift just needs to follow up with him about it
15:14:48 <JustinClift> We need to assemble the list of known users and get him looking for the so-far-unknown ones
15:15:05 <JustinClift> #action JustinClift to follow up with Rodrigo Gonzalez about the Prominent Users page
15:15:18 <JustinClift> #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:15:25 <JustinClift> "JustinClift to get the Westford lab mac mini doing nightly GlusterFS build tests happening (cron). Failure emails to gluster-devel I guess"
15:15:47 <JustinClift> Haven't yet gotten this happening. Upgrading it first, and still looking into putting it on the DMZ
15:16:05 <JustinClift> So, it'll prob be 3+ weeks
15:16:16 <JustinClift> "JustinClift to look into the "other Mac Mini's" we might have lying around"
15:16:33 <JustinClift> Did this.  They'll all ancient and low spec machines.  We'll use the one in the Westford lab instead
15:16:58 <JustinClift> "JustinClift to canvas for people to pick up the FreeBSD port code and get it merged/working with master"
15:17:04 <JustinClift> Complete
15:17:04 <kkeithley> Three weeks to get it in the DMZ? good luck with that
15:17:19 <JustinClift> kkeithley: Yeah, I'm not sure.  :/
15:17:23 * lpabon here
15:17:44 <JustinClift> Thanks to Harsha, the FreeBSD port exploded in a good way over the weekend
15:17:51 <kkeithley> I'm not trying to be flip, just setting reasonable expectations.
15:17:58 <JustinClift> :)
15:18:27 <Eco_> kkeithley, we'll compromise...two weeks  ;)
15:18:28 <JustinClift> Harsha updated Mike Ma's code to work on master.  We put a tarball online on download.gluster.org, and announced it in FreeBSD places
15:18:38 <JustinClift> (eg freebsd-fs mailing list and their forums)
15:19:05 <JustinClift> The FreeBSD people filled my inbox with tweets about it, and the FreeNAS people picked it up and made a port for it
15:19:05 <ndevos> very cool!
15:19:22 <JustinClift> Looks like _substantial_ interest there
15:19:41 <pranithk> JustinClift: good good. Good job sir!
15:19:42 <kkeithley> what are we doing to get it merged into master?
15:19:42 <JustinClift> We should have a FreeBSD slave node for Rackspace set up by the end of this week too
15:19:56 <vbellur> JustinClift: updated my AIs on the etherpad
15:20:18 <JustinClift> kkeithley: We need reviewers for Harsha CR in Gerrit: http://review.gluster.org/#/c/8141/
15:20:19 <glusterbot> Title: Gerrit Code Review (at review.gluster.org)
15:20:22 <JustinClift> vbellur: Thanks. :)
15:20:40 <JustinClift> #action JustinClift to add freebsd slave node to Jenkins
15:21:03 <JustinClift> kkeithley: Any interest in reviewing Harsha's CR?
15:21:11 <kkeithley> sure
15:21:15 <JustinClift> Tx :)
15:21:37 <JustinClift> #action kkeithley to review Harsha's FreeBSD CR in Gerrit http://review.gluster.org/#/c/8141/
15:21:38 <glusterbot> Title: Gerrit Code Review (at review.gluster.org)
15:21:43 <JustinClift> Moving on...
15:22:01 <JustinClift> "hagarth to email gluster-users and gluster-devel with the details of the new Port Maintainers by tomorrow"
15:22:06 <JustinClift> Done. :)
15:22:18 <JustinClift> We made a blog post abt it too
15:22:30 <JustinClift> "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:22:41 <JustinClift> Not started.  Going to push this back a few weeks
15:23:03 <JustinClift> "pranithk to add information about EasyFix to the existing Developer page (not urgent though)"
15:23:15 <JustinClift> Hmmm, I think that was non-urgent.  eg pushed back a few weeks
15:23:29 <JustinClift> "hagarth to send out an email on abandon policy for gerrit patches"
15:23:48 <JustinClift> hagarth: With that, is it a "this week" thing or should we push it back a few weeks?
15:24:04 <JustinClift> vbellur: ^^^
15:24:27 <hagarth> JustinClift: a week should do
15:24:32 <JustinClift> np
15:24:43 <JustinClift> #action hagarth to send out an email on abandon policy for gerrit patches
15:24:52 <JustinClift> "hagarth to start upstream discussion on what to do with old bugs"
15:24:57 <JustinClift> Same?
15:25:13 <hagarth> 2 weeks for this would help
15:25:18 <JustinClift> np
15:25:58 <JustinClift> #action JustinClift to scan old meetings for pushed back items that are now due
15:25:58 <JustinClift> "kkeithley to send a reminder on gluster-devel asking to update the 3.4 tracker bug"
15:26:01 <JustinClift> Done
15:26:06 <JustinClift> http://supercolony.gluster.org/pipermail/gluster-devel/2014-June/041152.html
15:26:07 <glusterbot> Title: [Gluster-devel] Fixes for glusterfs-3.4.5? (at supercolony.gluster.org)
15:26:11 <JustinClift> "hchiramm_ to make blog post about 3.4.4-2 when the rpms are on download.gluster.org"
15:26:17 <JustinClift> Done. http://www.gluster.org/2014/06/glusterfs-3-4-4-2-is-available-now/
15:26:23 <JustinClift> "JustinClift to email Pranith to get an update on the 3.5.x show stoppers"
15:26:44 <pranithk> JustinClift: He did I sent a reply. I got some patches merged
15:27:08 <JustinClift> Done.  1 major known one left to investigate, though new testing on 3.5.1 release hasn't been done and we may find more soon.
15:27:12 <JustinClift> pranithk: Thanks. :)
15:27:22 <JustinClift> "ndevos to devise 3.5.1 release timeline upon his return"
15:27:42 <ndevos> has been released!
15:27:43 <JustinClift> I'd say "done" since it's been released
15:27:58 <JustinClift> "JustinClift will email gluster-devel and gluster-users about the 3.6 Feature Freeze date being pushed out"
15:28:04 <JustinClift> Done. http://supercolony.gluster.org/pipermail/gluster-devel/2014-June/041155.html
15:28:05 <glusterbot> Title: [Gluster-devel] GlusterFS 3.6 Feature Freeze date pushed back 2 weeks (at supercolony.gluster.org)
15:28:10 <JustinClift> "hagarth to update Planning36 page with new dates"
15:28:21 <JustinClift> Complete. http://www.gluster.org/community/documentation/index.php/Planning36
15:28:23 <glusterbot> Title: Planning36 - GlusterDocumentation (at www.gluster.org)
15:28:35 <hagarth> right
15:28:35 <JustinClift> "hagarth will get initial functional leaderboard online"
15:28:40 <JustinClift> Still in progress :)
15:28:46 <hagarth> JustinClift: yes :)
15:28:49 <JustinClift> hagarth: How's that looking? :)
15:29:01 <JustinClift> ETA of 1 week, 2 weeks, ?
15:29:11 <hagarth> JustinClift: let us shoot for this week
15:29:16 <JustinClift> Cool. :0
15:29:23 <JustinClift> #action hagarth will get initial functional leaderboard online
15:29:25 <JustinClift> :)
15:29:35 <ndevos> does it include IRC stats?
15:29:44 <ndevos> should I bump mine a little?
15:29:49 <JustinClift> ?
15:30:26 <JustinClift> hagarth: ^
15:30:30 <ndevos> wasnt the leaderboard about patch/email/.. statistics? or am I confusing things?
15:30:31 <JustinClift> ndevos: What's yours?
15:30:52 <JustinClift> Yeah, I don't think IRC has been part of its scope
15:31:00 <hagarth> ndevos: yes, IRC is not in scope as yet
15:31:01 <JustinClift> We could add it later on, after the first version is online though
15:31:12 <JustinClift> Depending on effort, etc
15:31:13 <hagarth> ndevos: am still looking at patches/code review stats
15:31:14 * ndevos stays quiet then
15:31:18 <JustinClift> np :)
15:31:23 <JustinClift> "JustinClift to get initial GlusterFS Consultants and Support Companies page online"
15:31:34 <JustinClift> Not done.  Supposed to be yesterday
15:31:38 <JustinClift> I'll get it done this week
15:31:46 <JustinClift> #action JustinClift to get initial GlusterFS Consultants and Support Companies page online
15:31:53 <JustinClift> "JustinClift to set up autobuild test for NetBSD in Jenkins"
15:31:57 <JustinClift> In progress
15:32:25 <JustinClift> Emmanuel Dreyfus has been doing most of the work in last 2 days
15:32:30 <JustinClift> (and tonnes more prior)
15:32:42 <JustinClift> Hopefully it'll be fully funtional this week
15:32:57 <JustinClift> #action JustinClift to get autobuild test for NetBSD functional in Jenkins
15:33:10 <JustinClift> k, Moving on
15:33:14 <JustinClift> #topic 3.4
15:33:23 <JustinClift> 3.4.4-2 was released
15:33:30 <JustinClift> Thanks to kkeithley and the guys :)
15:33:52 <JustinClift> We already have requests for patches for 3.4.5
15:33:53 <pranithk> JustinClift: We may have to do one more release, based on some mail on gluster-users? Are we going to?
15:34:06 * JustinClift thinks "yes"
15:34:07 <kkeithley> not my doing. Humble did it
15:34:12 <JustinClift> Cool
15:34:20 <JustinClift> hchiramm__: Thanks for 3.4.4-2 :)
15:34:42 <semiosis> can we just make a 3.4.5 instead of these patch packages?
15:35:11 <JustinClift> Yeah, from memory 3.4.5 will include the patch from 3.4.4-2, and some version of the memory leak fixing patch reported on gluster-users
15:35:21 <kkeithley> yes, that's the plan. But one week was too short for 3.4.4->3.4.5
15:35:44 <JustinClift> k
15:35:48 <JustinClift> kkeithley: What's a good ETA?
15:35:57 <kkeithley> and yes, 3.4.5 will have the 3.4.4-2 patch
15:36:12 * JustinClift just checked, and the memory leak patch has been merged into release-3.4 already: http://review.gluster.org/#/c/8164/
15:36:14 <glusterbot> Title: Gerrit Code Review (at review.gluster.org)
15:36:20 * JustinClift hasn't checked his email this morning yet
15:36:47 <JustinClift> kkeithley: ETA?
15:36:51 <kkeithley> Can we say beta around mid-July? I'm on PTO from 12-20 July
15:37:11 <pranithk> kkeithley: Can't humble do it?
15:37:19 * JustinClift was just wondering that
15:37:56 <JustinClift> Seems like a long delay for a patch that (in theory) should just fix a memory leak (compared to 3.4.4-2)
15:38:03 <JustinClift> If we can get Humble to do it, then great
15:38:09 <JustinClift> Otherwise, yeah, mid July :)
15:38:10 <kkeithley> Is that all we want in it?
15:38:21 <JustinClift> That's all we know so far
15:38:40 <ndevos> wow, 3.4 is amazingly stable then!
15:38:48 <kkeithley> Only a (select) few can do the merges. If we feel good/certain that there won't be more "must have" fixes.
15:39:01 <kkeithley> I could tag and to a beta release now as far as that goes
15:39:06 <kkeithley> tag and do
15:39:08 <semiosis> +1
15:39:09 <JustinClift> Ahhh
15:39:10 <hagarth> kkeithley: +1 for that
15:39:32 <JustinClift> Ok, lets do that.  Leave the beta one out there for a few weeks to see what else crops up?
15:39:38 <semiosis> if there's more must haves, then 3.4.6
15:40:05 <JustinClift> semiosis: +1
15:40:13 <JustinClift> k
15:40:29 <ndevos> I agree with semiosis, release early and often, fix known bugs when we can
15:40:31 <JustinClift> #action kkeithly to build and tag a beta release for 3.4.5
15:40:42 <JustinClift> Yeah
15:40:46 <ndevos> (well, not too often)
15:40:50 <JustinClift> ;)
15:40:51 <kkeithley> I'll have to work smarter, not harder, to get my real work in between all these community releases of 3.4 ;-)
15:41:08 <JustinClift> kkeithley: Should we get Humble to do it instead?
15:41:10 <JustinClift> eg spread load
15:41:33 <pranithk> kkeithley: Agree with you. I guess we need more people who should be able to do the releases.
15:41:40 <kkeithley> tag and release build is 5 minutes. Packaging takes a bit longer
15:41:43 <ndevos> humble and lala can build the RPMs, I do not think they can (or should?) merge patches
15:41:55 <JustinClift> k
15:42:07 <kkeithley> 3.4.4-2 packages for Fedora haven't even made it into updates yet
15:42:13 <JustinClift> Heh
15:42:35 <JustinClift> kkeithley: The patches we're discussing for 3.4.5 are already in release-3.4 branch aren't they?
15:42:39 <kkeithley> well, sorry, they won't. red herring
15:42:58 <JustinClift> ?
15:43:04 <kkeithley> you're getting me all excited.
15:43:10 <JustinClift> Oh boy!
15:43:41 <JustinClift> k, just trying to work out the steps forward here
15:43:46 <kkeithley> I'll tag a beta and push the Release button for 3.4.5. Humble and Lala can build rpms for download.gluster.org when they have time
15:43:53 <JustinClift> k, lets do that :)
15:44:24 <JustinClift> #action hchiramm__ and Lala to build 3.4.5 beta1 rpms for download.gluster.org
15:45:09 <JustinClift> Moving on
15:45:12 <JustinClift> #topic 3.5
15:45:27 <pranithk> ndevos: where is 3.5.2 tracker bug?
15:45:28 <JustinClift> Thanks ndevos for the 3.5.1 release :)
15:45:34 <kkeithley> sorry, delayed response. Yes, I think the patches for 3.4.5 are already all merged
15:45:41 <JustinClift> kkeithley: :)
15:46:10 <ndevos> pranithk: there is a glusterfs-3.5.2 alias, enter that as a BZ# in bugzilla
15:46:21 <JustinClift> Cool
15:46:25 * JustinClift should remember that
15:46:45 <JustinClift> https://bugzilla.redhat.com/show_bug.cgi?id=glusterfs-3.5.2
15:46:47 <glusterbot> Bug glusterfs: could not be retrieved: InvalidBugId
15:46:53 <JustinClift> Bah.
15:46:57 <JustinClift> It worked in a browser
15:47:01 <ndevos> ah, yes, glusterbot doesnt like it
15:47:17 <JustinClift> 9 items already on its list
15:47:20 <pranithk> ndevos: This is nice :-). Easy to remember too :-)
15:47:29 <JustinClift> ndevos: Any idea for an ETA of it?
15:47:36 <ndevos> JustinClift: no
15:47:50 <JustinClift> k, we'll just keep and eye on it and figure it out as it goes I guess
15:48:05 <JustinClift> ndevos: Is there special attention we need to pay to any of the items?
15:48:19 <JustinClift> eg get attention for them via mailing list/blog/etc ?
15:48:21 <ndevos> yeah, see when most bugs have a patch, and if we can release with some patches missing and move those bugs to 3.5.3
15:48:52 <ndevos> nothing special to mention now, or at least nothing that I can remember atm
15:48:57 <JustinClift> np
15:48:58 <pranithk> ndevos: +1.
15:49:04 <JustinClift> Moving on... :)
15:49:23 <ndevos> oh, and I'll cut patches off earlier now, no last minute additions ;)
15:49:30 <JustinClift> ;)
15:49:33 <JustinClift> #topic 3.6
15:49:57 <JustinClift> New Feature Freeze date is 5th July
15:50:00 <pranithk> ndevos: :-)
15:50:04 <JustinClift> That's not far away
15:50:17 <JustinClift> Are there any items people have for 3.6 for this meeting?
15:50:39 <jdarcy> I'm hoping to get heterogeneous-brick support and improved SSL through the review gauntlet by then.
15:50:46 <JustinClift> Cool. :)
15:51:03 <jdarcy> Biggest challenge is probably finishing review of Xavi's patches.
15:51:04 <JustinClift> Are you getting decent response through the mailing list requests for review?
15:51:16 <ndevos> I really hope IPv6 works easily in 3.6 out of the box, but I doubt I find time to look at that
15:51:40 <pranithk> ndevos: Someone sent a mail on gluster-devel for that. Did you get a chance to check that?
15:51:41 <jdarcy> JustinClift: At least there's some activity now, so at least they're not dying by starvation.
15:51:42 <JustinClift> ndevos: Someone submitted a patch for that via mailing list
15:52:05 <JustinClift> jdarcy: It's a good idea to blog about it too.  Yep, even for review requests. ;)
15:52:13 <pranithk> ndevos: apparently it is a regression.
15:52:14 <ndevos> pranithk, JustinClift: yes, I've seen that, butdid not have any time for lookng into it
15:52:15 <JustinClift> "anything that works to get attention"
15:52:43 <jdarcy> I think we need to remind people that reviewing stuff early avoids a big pile-up at the end, where turnaround time even for an indentation change is in the hours.
15:52:48 <JustinClift> ndevos: Do you have time to get that mailing list submitted patch, and stuff it into a Gerrit CR?
15:53:07 <JustinClift> ndevos: If not, I can find it and do it
15:53:15 <JustinClift> (as long as it applies cleanly)
15:53:33 <ndevos> JustinClift: I thought the 'patch' was a revert of a change... but really, its way low on my todo
15:54:06 <JustinClift> #action jdarcy to sent reminder to gluster-devel, to remind people that reviewing stuff early avoids a big pile-up at the end
15:54:09 <JustinClift> ;)
15:54:26 <JustinClift> ndevos: k, I'll look for the mailing list message and try to figure it out
15:54:42 <pranithk> jdarcy: Actually dht has no documentation except for your blogs. May be we should also write a .md for it? I can do that if you can guide me. This way I learn a bit about dht as well?
15:54:52 <ndevos> JustinClift: yes please, I really have no idea when I would be able to try it out
15:54:58 <JustinClift> #action JustinClift to look into the IPv6 restoring patch
15:54:59 <jdarcy> Also merge conflicts.  I think my 3.6 patches will even hit those among themselves.
15:55:23 <JustinClift> ndevos: It'll give me a practical reason for learning IPv6
15:55:36 <JustinClift> jdarcy: Can't be helped though? ;
15:55:37 <raghug> pranithk: Nithya was also interested in it. We can sync about it later
15:55:38 <JustinClift> ;)
15:55:44 <ndevos> JustinClift: document your results please :)
15:55:55 <JustinClift> Of course
15:56:18 <jdarcy> JustinClift: Well, I do wonder if there's a way to allow a *pure* rebase change (no manual patchups) to go in without having to re-run regression.
15:56:18 <JustinClift> #action pranithk & Nithya to write documentation for dht
15:56:24 <pranithk> raghug: I would still like jdarcy's advice.
15:56:50 <raghug> pranithk: I know. I was just mentioning other people who might be interested :)
15:56:50 <pranithk> jdarcy: please ack that you will help :-)
15:57:16 * jdarcy is trying to re-establish context.  Help for what?
15:57:18 <JustinClift> #action jdarcy to help pranithk and Nithya with their dht documentation
15:57:25 <jdarcy> Ah, OK.  Sure.
15:57:29 <JustinClift> Fixed that for ya ;)
15:57:32 <pranithk> jdarcy: Great! :-)
15:57:38 <pranithk> JustinClift: Good job :-)
15:57:57 <JustinClift> Anything else for this item?
15:58:13 <JustinClift> Moving on...
15:58:16 <JustinClift> #topic Leaderboard
15:58:30 <ndevos> can we add IRC stats?
15:58:43 <JustinClift> ndevos: We could after the first version is done
15:58:50 <JustinClift> Let's not add features before then
15:58:59 * JustinClift doesn't want to cause push-out of first version ;)
15:59:35 <ndevos> if hagarth needs help with gerrit review stats, I could maybe find some small timeslots to do some work
15:59:40 <JustinClift> hagarth: Do you have an idea what the URL will be for the first version?
16:00:58 <JustinClift> Heh
16:01:01 <JustinClift> Moving on
16:01:17 <JustinClift> #topic Regression Testing
16:01:34 <JustinClift> Pranith's patches seem to have helped a lot
16:01:42 <JustinClift> There aren't as many failures as there used to be
16:01:52 <jdarcy> A lot of spam in the console logs, though.
16:02:05 <JustinClift> Manu and I are adding NetBSD support
16:02:07 <jdarcy> Can we redirect stderr for the "losetup -d" lines to /dev/null?
16:02:23 <JustinClift> jdarcy: Sure.  I wasn't sure what needs to be adjusted
16:02:42 <JustinClift> I have some temporary code in there too, to show return codes from the ssh and git commands
16:03:00 * JustinClift intends on using that to auto-retry the git and ssh connection failures, so it doesn't cause test failure
16:03:32 <JustinClift> #action JustinClift to redirect stderr lines for the regression testing (losetup -d) to /dev/null
16:03:40 <jdarcy> pranithk's umount changes helped a lot too, I think.
16:03:52 <pranithk> jdarcy: your idea ;-)
16:04:10 <jdarcy> pranithk: You're too modest.  I just tweaked it.
16:04:18 <JustinClift> Yep, things are in a better state now thanks to pranithk's work and the work of lots of other guys :)
16:04:29 <JustinClift> Are there other suggestions we should look at?
16:04:31 <jdarcy> Including Crocodile Dundee.  ;)
16:04:36 <JustinClift> Ahh yeah
16:04:50 <JustinClift> It's not high on my priority list, but I'll get that done this week
16:05:03 <JustinClift> #action JustinClift to get new cleanup patch finished and merged
16:05:13 <pranithk> JustinClift: one thing I wanted to ask
16:05:15 <JustinClift> Sure
16:05:33 <pranithk> JustinClift: What should we do if we want to run some tests once in lets say 2-3 days or weekly?
16:05:51 <pranithk> JustinClift: Very long running tests. IOzone/dbench etc
16:05:54 <JustinClift> pranithk: At the moment, I'm not sure
16:06:01 <JustinClift> lpabon: Any idea how to do that?
16:06:04 <purpleidea> pranithk: bennyturns might be helpful there....
16:06:10 <JustinClift> Good thinking
16:06:23 <purpleidea> pranithk: also, so might BAGL
16:06:36 <purpleidea> but less likely
16:06:48 <pranithk> purpleidea: But we want these automated just like the regression tests...
16:06:49 <JustinClift> Err... what's a BAGL?  /me saw the term recently but no idea what BAGL is
16:07:03 <Eco_> Big Auld Gluster Lab
16:07:06 <purpleidea> JustinClift: i'll tell you offline
16:07:08 <JustinClift> Ahhh
16:07:24 <pranithk> we want these automated just like the regression tests
16:07:33 <purpleidea> pranithk: right, so bennyturns (in#gluster) has something up and running with jenkins i think. separate system
16:07:45 <pranithk> purpleidea: Now you are talking :-)
16:07:51 <JustinClift> #action JustinClift to find out if there's a way to run regression tests on a timed basis.  Google, lpabon and bennyturns as info sources
16:08:26 <JustinClift> Maybe that should be pranithk or purpleidea to do that action item?
16:08:40 <purpleidea> JustinClift: pranithk
16:08:45 <pranithk> JustinClift: yes, lets get the ball rolling. We shall see what we will find
16:09:05 <JustinClift> #action pranithk to look into the timed Jenkins jobs item as well
16:09:09 <pranithk> JustinClift: I think rabhat also wanted to help here. I will speak to him as well
16:09:10 <JustinClift> k, moving on
16:09:15 <JustinClift> We're 2 minutes to time
16:09:25 <JustinClift> #topic Other Agenda items
16:09:30 <JustinClift> "Puppet-Gluster+BTRFS available for testing"
16:09:34 <JustinClift> purpleidea: That's yours I guess? :)
16:09:41 <purpleidea> yeah that's me... paste the link :)
16:09:54 <JustinClift> https://github.com/purpleidea/puppet-gluster/tree/feat/btrfs
16:09:56 <glusterbot> Title: purpleidea/puppet-gluster at feat/btrfs · GitHub (at github.com)
16:10:25 <purpleidea> testing appreciated ^^ if anyone is interested. in other news, if there are performance improvements like i did for xfs, let me know and i'll bake those in too
16:11:07 <JustinClift> On a related note, I should be able to set up a Fedora 2x slave vm soon (not this week though), and hook it into jenkins.  That'll let us try btrfs
16:11:19 <JustinClift> purpleidea: Cool :0
16:11:21 <JustinClift> :)
16:11:32 <pranithk> JustinClift: That will also give too many regression failures. More work :-D
16:11:33 <purpleidea> F20 has new btrfs patches to support this work!
16:11:35 <JustinClift> purpleidea: Can you email gluster-devel and gluster-users with that info?
16:11:44 <purpleidea> yeah
16:11:57 <JustinClift> pranithk: Yeah, that's the trade off
16:12:04 <JustinClift> purpleidea: Have you blogged about it?
16:12:31 <JustinClift> #action purpleidea to email gluster-devel and gluster-users about his btrfs work in puppet-gluster
16:12:46 <jdarcy> That reminds me, I want to do some tests on F2FS.
16:12:49 <JustinClift> k, it's time guys
16:12:49 <purpleidea> JustinClift: no, i haven't even tested it... i'm trying to "outsource the testing" to the community...
16:13:02 <kkeithley> Eco_: if you have super powers for getting hardware into the DC DMZ, can you see if you can knock loose INC0157311.
16:13:07 <JustinClift> purpleidea: k, blog about it as well, asking for testing, etc
16:13:10 <pranithk> purpleidea: you bad boy :-)
16:13:16 <purpleidea> pranithk: ;)
16:13:24 <purpleidea> less testing == more time for coding/features
16:13:37 <Eco_> kkeithley, i have no such powers...infra team cares as little for me as anyone else  ;)
16:13:43 <jdarcy> Oh BTW, it looks like new blog posts aren't getting syndicated to gluster.org.  Is that still in JMW's lap?
16:13:45 <purpleidea> jdarcy: i can add puppet-gluster support for f2fs if you want
16:13:48 <JustinClift> kkeithley: I'm thinking we escalate via Ric?
16:14:06 <kkeithley> Eco_: oh, you tease. After you said you could get the Mac Mini in there in two weeks. ;-)
16:14:11 <JustinClift> jdarcy: Ahh.  Can you let me know which ones you want syndicated?
16:14:14 <Eco_> kkeithley, ah  lol
16:14:30 <jdarcy> JustinClift: Will do.
16:14:33 <JustinClift> jdarcy: There are some I see as "pending" in the wordpress interface, and wasn't sure I should hit "publish" on
16:14:47 <JustinClift> k, that's all guys
16:14:50 <JustinClift> #endmeeting