12:00:44 <ndevos> #startmeeting
12:00:44 <zodbot> Meeting started Wed Feb  4 12:00:44 2015 UTC.  The chair is ndevos. Information about MeetBot at http://wiki.debian.org/MeetBot.
12:00:44 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
12:01:01 <ndevos> welcome all, todays agenda is at https://public.pad.fsfe.org/p/gluster-community-meetings
12:01:07 <ndevos> #topic Roll Call
12:01:16 * kkeithley_ is here
12:01:22 * msvbhat is present
12:01:35 * lalatenduM is lurking :)
12:01:35 * raghu is here
12:01:38 * jdarcy in da house
12:02:02 * kshlm is here
12:02:09 * krishnan_p is here
12:02:23 * ndevos pokes hchiramm
12:02:38 * hchiramm is here :)
12:02:47 * hagarth partially available
12:02:59 <ndevos> great, lets get started then
12:03:09 <ndevos> #topic Items from last week
12:03:14 <ndevos> #topic hchiramm will try to fix the duplicate syndication of posts from ndevos
12:03:26 <ndevos> hchiramm: anything to report?
12:03:44 <hchiramm> ndevos, u were abt to publish an article right ?
12:03:45 <hchiramm> :P
12:04:00 <ndevos> uh, was I?
12:04:12 <hchiramm> yeah, to check the duplication happens ?
12:04:24 <ndevos> #action ndevos should publish an article on his blog
12:04:26 <lalatenduM> ndevos, may be your Fosdem experience :)
12:04:40 <ndevos> lalatenduM: yeah, I'll think of something :)
12:04:50 <ndevos> #topic ndevos, lalatenduM, kkeithley and Humble to propose a long term solution to the packaging problem in CentOS/RHEL
12:05:02 <lalatenduM> yeah this is pending for long
12:05:06 <hchiramm> ndevos, this AI is yet to happen
12:05:11 <jdarcy> "The packaging problem"?
12:05:18 <lalatenduM> jdarcy, yes
12:05:27 <hchiramm> even-though we tackled last reported issues
12:05:29 <lalatenduM> may be we will use epoch
12:05:35 <hchiramm> we need a long term well defined solution
12:05:42 <ndevos> jdarcy: like RHEL packages break gluster community packages dependencies / conflicts / ....
12:05:49 <jdarcy> OK, thx.
12:05:53 <hchiramm> lets start discussion on this in a mail thread
12:06:02 <lalatenduM> hchiramm, yup
12:06:21 <ndevos> anyway, I think lalatenduM is getting it addressed through the CentOS Storage SIG packages?
12:06:36 <lalatenduM> ndevos, yes and no :)
12:06:44 <hchiramm> ndevos, I dont think CentOS storage SIG will help
12:06:54 <hchiramm> we need downstream and upstream co-ordination on this
12:07:03 <lalatenduM> we need mechanism where community pkgs always ahead of RHSS
12:07:29 <ndevos> yes, and who wants to start that discussion on the list, lalatenduM, hchiramm?
12:07:35 <hchiramm> I can start
12:08:07 <ndevos> #action hchiramm will start a discussion on the mailinglist about the RHEL/Community packaging issues and solutions
12:08:21 <ndevos> #topic hagarth to open a feature page for (k)vm hyperconvergence
12:08:30 <ndevos> hagarth: any news on this?
12:09:16 <ndevos> at FOSDEM there was a talk about it,  but unfortunately I missed it: https://fosdem.org/2015/schedule/event/hyperconvergence/
12:10:02 <ndevos> I hope that Frederico publishes his slides so that we can point to them in the feature page
12:10:28 <ndevos> #idea include a link to Fredericos slides from https://fosdem.org/2015/schedule/event/hyperconvergence/ in the feature page
12:11:00 * ndevos assumes hagarth is busy...
12:11:04 <ndevos> #topic spot to investigate repetitive posts on social networking sites
12:11:13 <ndevos> spot: are you there?
12:11:44 <ndevos> or, did anyone notice any new issues with it?
12:11:51 <hchiramm> not me
12:11:56 <lalatenduM> not me
12:12:05 <ndevos> hagarth proposed to disable automatic posting, maybe that has been done?
12:12:15 <lalatenduM> spot might be in infra.next
12:12:44 <hchiramm> ndevos, not sure
12:12:44 <ndevos> okay, we'll keep it on the list for next week
12:12:50 <ndevos> #topic spot will send out an email with upcoming Gluster events and meetups
12:13:04 <lalatenduM> I saw a blog about it
12:13:11 <lalatenduM> not sure it was spot or hagarth
12:13:28 <ndevos> ah, yes, hagarth posted something on the blog
12:13:44 <ndevos> http://blog.gluster.org/2015/01/glusterfs-events-over-the-next-10-days/
12:14:28 <ndevos> but, an email to the announce list would be nice too...
12:14:40 <ndevos> and, as a reminder, please keep updating https://public.pad.fsfe.org/p/gluster-events
12:15:05 <ndevos> #topic spot to reach out to community about website messaging
12:15:33 <ndevos> anyone noticed a discussion about getting a new slogan?
12:16:20 <ndevos> ... does not look like it :-/
12:16:24 <lalatenduM> nope
12:16:29 <lalatenduM> I have not seen it
12:16:33 <hchiramm> no..
12:16:36 <jimjag> ndevos: where would it have been held?
12:16:48 * jimjag means the discussion
12:16:53 <hchiramm> mailing list
12:17:02 <hchiramm> gluster-users
12:17:02 <lalatenduM> gluster-users may be
12:17:14 <ndevos> jimjag: I guess on the mailinglists, but a blog post and twitter or something would be possible too
12:17:18 * jimjag did not notice it then
12:18:18 <ndevos> okay, last week and this one is pretty hectic for many of us, visiting FOSDEM and DevConf.cz - maybe it gets done next week
12:18:29 <ndevos> #topic hagarth to carry forward discussion on automated builds for various platforms in gluster-infra ML
12:18:49 <ndevos> he marked it as TBD, so I dont need to ask :)
12:19:16 <ndevos> but, if there is someone who would like to take that action item on, we'd all very much appreciate it
12:19:43 <ndevos> #topic Gluster 3.6
12:19:54 <ndevos> raghu: floor is yours!
12:20:21 <raghu> I have renviewed and pushed some patches of afr and ec
12:20:33 <raghu> I am planning to make 3.6.3beta1 by the end of this week
12:20:54 <hchiramm> :P
12:21:04 * jimjag w00t!
12:21:15 <raghu> some patches have been reviewed which I am going to merge soon. And some patches need +1
12:21:23 <hchiramm> do we have any feedback about 3.6.2 release ?
12:21:59 <hchiramm> I see some mails in MLs though
12:22:11 <raghu> hchiramm: there was a post in gluster-users about annoying log message. The patch has been sent to 3.6 for review
12:22:22 <raghu> I am going to merge them once they pass regression tests
12:22:26 <ndevos> raghu: any users reporting bugs against 3.6.2?
12:23:22 * lalatenduM : Another 3.6 build!! runs to hide
12:23:41 <raghu> There was a bug today in which the user had formatted the backend xfs....and after bringing up glusterd was not starting. I am looking at the logs that have been attached.
12:23:51 <hchiramm> [Gluster-devel] gluster 3.6.2 ls issues
12:24:12 <ndevos> https://bugzilla.redhat.com/showdependencytree.cgi?id=glusterfs-3.6.3&maxdepth=1&hide_resolved=1 seems to be the list of bugs that would be addressed in 3.6.3, right?
12:24:41 <raghu> ndevos: yeah.
12:24:56 <gothos> o/
12:25:08 <jdarcy> http://cdn.meme.am/instances/250x250/58805874.jpg
12:25:11 <ndevos> raghu: some of those are still in NEW/ASSIGNED/POST, when you merge patches, you need to change the status manually :-/
12:25:22 <hchiramm> jdarcy++ :P
12:25:44 <raghu> ndevos: yeah. I am going to do it soon.
12:25:53 <ndevos> raghu: okay, thanks!
12:26:15 <hchiramm> thanks raghu
12:26:17 <msvbhat> jdarcy: You missed "Brace yourself"
12:26:21 <msvbhat> :)
12:26:27 <jdarcy> msvbhat: Heh.
12:26:36 <ndevos> raghu: ah, that reminds me, did 3.6.0...3.6.2 bugs get closed?
12:27:05 <lalatenduM> jdarcy, awesome pic :), you should tweet it
12:27:23 <lalatenduM> msvbhat, good point :)
12:27:33 <raghu> ndevos: I had moved them to modified state. I am going to close them now
12:27:45 <hchiramm> may be we need one saying "3.6.2" is released
12:28:09 <kkeithley_> There was email+blogpost about 3.6.2 release
12:28:20 <ndevos> raghu: okay, thanks - let me know if you need assistance with that, I've done it for 3.5.x in some semi-automate way
12:28:21 <kkeithley_> On raghu's behalf
12:28:23 <hchiramm> yep .. kkeithley++
12:28:58 <ndevos> raghu: anything else on 3.6?
12:29:03 <raghu> ndevos: The semi-automate way would be great. Otherwise I have to manually close each bug
12:29:16 <ndevos> #action raghu will close older 3.6 bugs
12:29:17 <raghu> ndevos: nothing more.
12:29:29 <ndevos> raghu: sure, I'll send you something by mail
12:29:39 <raghu> ndevos: great :)
12:29:48 <ndevos> #action raghu creates 3.6.3beta1 later this week
12:30:02 <ndevos> #topic Gluster 3.5
12:30:19 <ndevos> 3.5.4 is in the works
12:30:33 <ndevos> https://bugzilla.redhat.com/showdependencytree.cgi?id=glusterfs-3.5.4&maxdepth=1&hide_resolved=1 has a list of bugs that should get fixed with the release
12:31:09 <ndevos> there are some others that should get fixed too, but those are "nice to have"
12:31:34 <ndevos> post patches, get them reviewed and I'll merge them :)
12:32:02 <ndevos> there is no schedule for the release yet, maybe by the end of next week, but surely not before
12:32:17 <ndevos> questions on 3.5?
12:32:51 * ndevos assumes thats a "no"
12:32:58 <ndevos> #topic Gluster 3.4
12:33:04 <ndevos> kkeithley_: ?
12:33:05 <kkeithley_> no change in status
12:33:20 <ndevos> remind me on the status please?
12:33:23 <kkeithley_> besides memory leak I haven't looked at other bugs to see if fixes have been posted
12:33:36 <ndevos> ah, right
12:34:02 <hchiramm> kkeithley_, Is 3.4.7 going to be the last 3.4 series ? :)
12:34:15 <kkeithley_> perhaps. depends on when 3.7.0 ships ;-P
12:34:26 <lalatenduM> lets keep them coming ;)
12:34:50 <lalatenduM> and hchiramm has volunteered to build them as long as required :)
12:35:22 <hchiramm> :)
12:35:46 <ndevos> kkeithley_: something else to add, or shall we move to the next topic?
12:35:52 <kkeithley_> no, nothing
12:36:09 <ndevos> #topic Gluster.next - 3.7
12:36:28 <ndevos> who kept track of the 3.7 progress?
12:36:37 * ndevos did not really
12:37:18 <ndevos> I think feature proposal/documentation is ending before next weeks meeting (10 Feb.)
12:37:53 <ndevos> so, if there are features in the works that are non-trivial, they should get added to the 3.7 planning page in the wiki
12:38:08 <ndevos> http://www.gluster.org/community/documentation/index.php/Planning37
12:38:58 <ndevos> if nobody wants to add something to the topic now, send an email to the list and start a discussion there :)
12:39:05 <ndevos> #topic Gluster.next - 4.0
12:39:28 <ndevos> jdarcy: I think you sent something about a meeting for Friday?
12:39:34 <jdarcy> Yes,I did.
12:39:43 <jdarcy> I hope to see some of you there.  :)
12:40:10 <ndevos> http://www.gluster.org/pipermail/gluster-users/2015-February/020464.html
12:40:36 <ndevos> jdarcy: anythin you want to mention about 4.0 here?
12:41:25 <jdarcy> Wouldn't want to spoil the main event.
12:41:33 <ndevos> ok :)
12:41:51 <ndevos> #topic Other agenda items
12:42:15 <ndevos> #topic Upcoming talks at conferences
12:42:43 <ndevos> so, devconf.cz is happening on Friday-Sunday this week, and there are some related Gluster talks
12:43:01 <ndevos> you should be able to find them in the schedule under "storage"
12:43:36 <ndevos> the talks are streamed and recorded, there is a youtube account that has all of them
12:43:58 <ndevos> #topic GSOC 2015
12:44:21 <kshlm> I'm up
12:44:38 <ndevos> go for it :)
12:44:42 <kshlm> As I mentioned last week, GSOC org registrations open on Feb 9th.
12:45:18 <kshlm> I asked for help and hagarth suggested that I get JustinClift and spot to help.
12:45:54 <kshlm> I've contacted them (this monday btw), but haven't heard back yet.
12:46:11 <kshlm> In the meantime, I sent out a mail on the mailing lists asking for ideas and mentors.
12:46:24 <ndevos> yeah, I guess those three are pretty occupied this week...
12:46:27 <kshlm> This is a pre req for becoming a GSOC org.
12:47:21 <kshlm> If anyone else has any experience with GSOC, please lend a hand.
12:47:38 <ndevos> how many projects/mentors/<whatever> would you need?
12:47:55 <kshlm> We'd need 1 admin.
12:48:11 <kshlm> The admin needs to file the proposal on behalf of the organization.
12:48:26 <kshlm> We need at least one mentor per idea we list.
12:48:50 <kshlm> But we need to get an admin first, to take care of the organization registration.
12:48:51 <lalatenduM> kshlm, I would suggest you to be the admin, are you interested?
12:49:06 <kkeithley_> I did it two years ago for Mike Ma's FreeBSD port. I'd like to see other people step up to be mentors.
12:49:18 <kshlm> I don't think I'll have much time to be an admin.
12:49:31 <kshlm> I'm willing to be a mentor though.
12:49:48 <lalatenduM> hmm, so wee need to look for an admin
12:49:53 <lalatenduM> anyone interested?
12:50:11 <ndevos> kshlm: maybe you can get in touch with people you think could do the admin bit, and ask them if they are interested?
12:50:17 <ndevos> 9 Feb is getting close...
12:50:34 <kshlm> The registration window is 9th-20th. So we still have time.
12:51:00 <hchiramm> may be JustinClift ?
12:51:05 <ndevos> right, but it would be nice to have sooner than later
12:51:08 <kshlm> I'd prefer the admin to be someone with more experience handling community stuff.
12:51:20 <hchiramm> kshlm, we can check with JustinClift
12:51:34 <kshlm> Yup
12:51:37 <lalatenduM> also spot
12:52:03 <lalatenduM> either of them
12:52:10 <kshlm> I contacted them, but neither of them seem to be available this week.
12:52:23 <kshlm> I'll ping them again.
12:52:48 <lalatenduM> kkeithley_, ndevos, do you know if spot is coming to devconf?
12:52:57 <lalatenduM> and JustinClift
12:52:57 <ndevos> okay, thanks, and please keep us updated
12:53:04 <kkeithley_> I'm pretty sure he's here
12:53:15 <kshlm> I will do that. In the meantime please add to the ideas list.
12:53:15 <ndevos> lalatenduM: JustinClift isnt, I think, no idea about spot
12:53:54 <ndevos> lets move to the next item on the agenda
12:53:58 <ndevos> #topic Small file performance
12:54:15 <ndevos> uhm, I'm not sure we need to discuss that here?
12:54:28 <ndevos> but, maybe someone has a status update?
12:55:07 <ndevos> ok, ... not then
12:55:12 <ndevos> #topic liburcu installation on jenkins slaves
12:55:30 <kshlm> That's me again.
12:55:36 <ndevos> :)
12:55:47 <kshlm> I need someone the infra team to install liburcu on the jenkins slave.
12:56:04 <ndevos> I know JustinClift installed packages on them before
12:56:09 <kshlm> Alternatively, I can do it myself, it given access.
12:56:14 <kshlm> s/it/if/
12:56:50 <kshlm> I want to send changes I'm doing for review, but I need the installations done before that.
12:57:04 <ndevos> well, I dont know where the profile of a slave is kept - there would be some config management, I think
12:57:33 <ndevos> misc and JustinClift are your best bet
12:57:55 <kshlm> Ok.
12:58:30 <ndevos> you can just post your patches, and accept the failures - retrigger the tests when liburcu is installed?
12:58:48 <ndevos> that at least makes it possible to review them and get some feedback
12:59:07 <kshlm> I currently have it on Github, and have some people reviewing it there.
12:59:53 <ndevos> okay, maybe sent out the link for the repo on the -devel list (if not done so already)?
13:00:39 <kshlm> I think I'll do that.
13:01:05 <kshlm> In the meantime, I'll keep pestering the infra-team.
13:01:31 <ndevos> yes, and ping JustinClift on irc, twitter, phone - whatever :)
13:02:32 <ndevos> #endmeeting