12:00:03 <atinm> #startmeeting Gluster community weekly meeting 12:00:03 <zodbot> Meeting started Wed Feb 24 12:00:03 2016 UTC. The chair is atinm. Information about MeetBot at http://wiki.debian.org/MeetBot. 12:00:03 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic. 12:00:03 <zodbot> The meeting name has been set to 'gluster_community_weekly_meeting' 12:00:10 <atinm> Hello everyone 12:00:18 <atinm> its time for this week's community meeting 12:00:31 <atinm> #info agenda is @ https://public.pad.fsfe.org/p/gluster-community-meetings 12:01:29 * skoduri is here 12:01:30 <atinm> I am not a channel operator and its not allowing me to set topic 12:01:39 <atinm> anyone knows how to overcome that ? 12:02:07 <ndevos> kkeithley can change the topic, but I dont think you need to do that now? 12:02:23 * Saravanakmr is here 12:02:39 <ggarg> ggarg is here 12:02:42 <atinm> but when I say /TOPIC roll call its complaining about you are not a channel operator 12:02:47 <lpabon> o/ 12:02:59 <atinm> #TOPIC roll call 12:03:09 * hchiramm_ is here 12:03:10 <ndevos> noCAPS? 12:03:13 <atinm> does the above work? 12:03:14 <lpabon> o/ 12:03:18 <atinm> #topic roll call 12:03:19 * overclk is here 12:03:23 * msvbhat joins the meeting 12:03:28 <lpabon> o/ .. again 12:03:35 <josferna> o/ o/ 12:03:41 <ndevos> yes, it should work, the #topic is a zodbot command, not an IRC-channel onw 12:03:45 <ndevos> *one 12:03:49 * ndevos _o/ 12:03:50 <atinm> ndevos, cool 12:04:06 * kshlm o/ 12:04:15 * msvbhat _o/ 12:04:24 <atinm> Allright, so lets move on 12:04:40 <atinm> #topic last week's action items 12:04:55 <atinm> ndevos to send out a reminder to the maintainers about more actively enforcing backports of bugfixes 12:05:18 <atinm> ndevos, any updates on this? 12:05:20 <ndevos> yes, I've phrased it in my mind, but did not write the email yet 12:05:37 <atinm> ndevos, so can we expect it to land in by this week? 12:06:02 <ndevos> I really hope so! 12:06:07 <atinm> #action ndevos to send out a reminder to the maintainers about more actively enforcing backports of bugfixes 12:06:36 <atinm> Next one is on kshlm & csim and I can see the update as not done, so carrying forward the AI 12:06:43 <atinm> #action kshlm & csim to set up faux/pseudo user email for gerrit, bugzilla, github 12:07:04 <atinm> Moving on 12:07:05 <atinm> kkeithley to send a mail about using sanity checker tools in the codebase in two weeks. 12:07:13 * aravindavk joined now 12:07:17 <atinm> do we have kkeithley today? 12:07:21 <kshlm> I think that was 2 weeks, 2 weeks ago. 12:07:51 <atinm> #action kkeithley to send a mail about using sanity checker tools in the codebase 12:08:14 <atinm> Next one is about the missing release notes for 3.7 and I can see kshlm has sent a patch 12:08:23 <atinm> #info missing release notes for 3.7 patch : kshlm to update missing release-notes for 3.7 12:08:26 <atinm> oops 12:08:39 <kshlm> Yeah. I'll merge once the +1s are given. 12:08:41 <atinm> #info missing release notes for 3.7 patch - https://review.gluster.org/13509 12:08:49 <kshlm> I need to update amye about it though. 12:09:04 <kshlm> She'll update the website to point to the correct notes. 12:09:18 <atinm> #action kshlm to update amye to update the website with latest release notes 12:09:52 <atinm> kshlm to open 3.7.9 tracker (and close 3.7.8 if still open) 12:10:03 <atinm> I can see that's also done, thanks kshlm ! 12:10:05 <kshlm> Done. 12:10:14 * kshlm is on a roll this week! 12:10:29 <atinm> yes you are kshlm ! 12:10:40 <atinm> kshlm to ping rabhat for an update on 3.6.9 12:10:50 <atinm> this is also done but did you get a reply from him? 12:10:56 <atinm> kshlm, ^^ 12:11:02 <kshlm> I think I got it. 12:11:15 <kshlm> Did he, or did he not send out an email on this? 12:11:35 <atinm> so what's the update on it? is 3.6.9 on track? 12:11:37 <kshlm> Nope. 12:11:56 <kshlm> I sent a mail on the maintainers list directed at him. 12:12:07 <atinm> Ok 12:12:19 <atinm> So in case you didn't see a reply could you follow up on it? 12:12:26 <kshlm> He replied saying he was having troubles merging. We solved it. 12:12:34 <kshlm> But I don't have an update after that. 12:12:40 <kshlm> I'll bump that thread again. 12:12:48 <atinm> #action kshlm to follow up with rabhat about 3.6.9 updates 12:13:03 <atinm> And that concludes the last week's AI 12:13:12 <atinm> Moving to GlusterFS 3.7 12:13:25 <atinm> #info release manager for 3.7.9 will be raghug 12:13:47 <atinm> do we have Raghavendra G (raghug) today? 12:13:52 <kshlm> I have an update on this. 12:14:02 <atinm> go ahead please! 12:14:38 <kshlm> raghug informed that he cannot take up release mainatainer role right now, as he's busy with other tasks for the next 2 weeks. 12:14:44 <kshlm> So we need a new manager. 12:15:05 <kshlm> He did say he'd go round trying to get someone else to volunteer. 12:15:24 <atinm> Ok 12:15:28 <kshlm> Since he's not here now, any volunteers? 12:15:43 <atinm> Ideally a mail in maintainers list would help! 12:15:46 <ndevos> someone should send an email to the maintainets list? 12:16:00 <kshlm> Okay. I asked him to do that. 12:16:20 <kshlm> But I'll do it right away. 12:16:28 <atinm> #raghug/kshlm to follow up on maintainers list for a replacement of 3.7.9 release manager 12:16:43 <atinm> #action raghug/kshlm to follow up on maintainers list for a replacement of 3.7.9 release manager 12:17:49 <atinm> This is broadcast, given that we have a 3.7.9 trackers all blocker bugs should be tagged against it to ensure that your patches go in with it 12:18:06 <atinm> Anything else from 3.7.9 front? 12:18:38 <atinm> I take it as no 12:18:42 <atinm> Moving to next one 12:18:45 <atinm> #topic GlusterFS 3.6 12:19:18 <atinm> since raghug is not here can we skip this and move forward? 12:19:38 <atinm> as usual backports are welcome!! 12:20:06 <kshlm> atinm, You're confusing raghug and rabhat 12:20:17 <atinm> kshlm, huh!!!! 12:20:19 * ndevos can understand that 12:20:22 <atinm> kshlm, my bad 12:20:37 <atinm> we did that last time as well :( 12:21:02 <atinm> anyways, moving forward 12:21:07 <atinm> #topic GlusterFS 3.5 12:21:15 <atinm> over to you, ndevos :) 12:21:34 <ndevos> tracker for 3.5.9 is available, and people can send backports for 3.5 bugs too 12:21:55 <ndevos> I did not announce the 3.5.8 release yet, not sure if packages are available 12:22:14 <ndevos> I think kkeithley did some packaging, but I did not see a confirmation on the packaging mailinglist 12:22:27 <atinm> #info 3.5.8 release announcement is yet to be done 12:22:42 <ndevos> will need to check that, and announce later this week 12:22:44 <atinm> ndevos, can you just follow up with kkeithley ? 12:22:50 <atinm> ndevos, cool 12:22:52 <ndevos> yeah :) 12:23:14 <atinm> #action ndevos to announce 3.5.8 availability later this week 12:23:14 <ndevos> nothing more for 3.5, unless someone has questions? 12:24:15 <atinm> I take that as No from others 12:24:31 <atinm> #topic GlusterFS 3.8 & GlusterFS 4.0 12:24:46 <atinm> do we have hagarth around? 12:25:03 <atinm> any representative for 3.8? 12:25:26 <ndevos> maybe me? 12:25:36 <atinm> sure ndevos, go ahead! 12:26:03 <ndevos> I'll be thinking about requirements and a mile-stone kinda schedule for the features we want in 12:26:27 <ndevos> things like, "by date ... the feature page should be ready" and such 12:26:32 <jdarcy> 3.8 proposed features -> https://www.gluster.org/community/roadmap/3.8/ 12:26:32 * atinm completely forgot about ndevos been the release manager for 3.8, so apologies! 12:26:44 <jdarcy> Whole lotta TBD on the feature pages. Let's fix that. 12:27:17 <ndevos> exactly, way too much TBD, anything that will not be in real visible progress will get dropped from 3.8 12:27:21 <jdarcy> For those that *do* have feature-page patches, let's get some reviews in. 12:28:33 <ndevos> I'll be spending some time on 3.8 planning/checking/.. next week, updates will follow on the usual mailinglist(s) 12:29:03 <atinm> lpabon, just wondering why is heketi in 3.8 schedule? 12:29:32 <lpabon> atinm, i'm not sure 12:29:34 <atinm> lpabon, isn't it we already have in place 12:29:37 <lpabon> it has its own schedule 12:29:54 <aravindavk> ndevos: REST API and Eventing projects are not in the list. Can I add? 12:30:07 <ndevos> I think we want to announce some features when we release 3.8, maybe Heketi needs some promoting? 12:30:22 <ndevos> aravindavk: yes, please add them! 12:30:29 <lpabon> ndevos, atinm yes, that is true 12:30:38 <lpabon> it needs some promotion 12:31:04 <atinm> ndevos, lpabon : ok 12:31:29 <aravindavk> ndevos: ok 12:31:54 <atinm> #action aravindavk to add Gluster Eventing & REST API support in 3.8 roadmap 12:32:28 <atinm> is anything else on 3.8 side otherwise over to jdarcy for 4.0? 12:32:51 <msvbhat> ndevos: I know distaf isn't a feature. But should I add it there? 12:32:57 <jdarcy> Having lots of meetings in BLR this week to catch up on design issues and such. 12:33:03 <aravindavk> ndevos: atinm can I add glustertool to the list? 12:33:05 <msvbhat> To make sure that people start writing cases in it? 12:33:33 <ndevos> msvbhat: yes, we will require all features to provide distaf test-cases, it definitely needs to be very visible 12:33:39 <atinm> msvbhat, distaf should be definitely in IMO 12:33:39 <jdarcy> I think we made some good progress on GlusterD2 stuff yesterday, maybe atinm can say more. 12:34:20 <atinm> jdarcy, yup, let's wait for 3.8 discussion to finish, I think we still have some open questions from aravindavk & msvbhat 12:34:24 <msvbhat> ndevos: atinm: Okay, Then I will try and add it there. How do I add? By sending PR? 12:34:42 <atinm> msvbhat, yes 12:34:51 <ndevos> msvbhat: yes, the link for updating is on the bottom of the page 12:34:51 <msvbhat> Cool, Will do it 12:35:16 <atinm> aravindavk, regarding glustertool I do think that will be a good adds-on 12:35:43 <atinm> So with that lets move to GlusterFS 4.0 12:35:58 <ndevos> aravindavk: add anything you think should be mentioned as a new 3.8 thing, even if it works with older releases 12:36:17 <aravindavk> ndevos: cool. thanks 12:36:30 <atinm> As jdarcy pointed out that we have had some design discussions around and we'll be coming with a detailed write up about the flexi volgen, plugins 12:37:08 <atinm> Also atinm / ggarg would be writing about how we have done etcd bootstrapping in GD2 12:37:14 <jdarcy> Today's fun topic was client-side caching, which is making good progress. 12:37:44 <atinm> so community can expect some mails from GD2 team before we meet for the next meeting 12:38:48 <atinm> overclk, any updates on DHT2? 12:39:03 <josferna> jdarcy, more details on client-side cache ? 12:39:13 <overclk> atinm, nothing as such. 12:39:31 <overclk> probably tomorrow we'll meet with jdarcy on dht2. 12:39:46 <atinm> overclk, ok 12:39:56 <jdarcy> Yep, DHT2 and NSR discussions are coming up in the next couple of days, should be some updates after that. 12:40:31 * msvbhat brb 12:40:31 <jdarcy> Also, not really a 4.0 thing, but we'll be having a chat about distaf, vagrant, and general next-gen testing infra. 12:40:32 <atinm> jdarcy, ok 12:41:25 <ndevos> oh, and as a reminder, we can run distaf/vagrant/.. in the CentOS CI (Jenkins), which has many physical servers 12:41:35 <jdarcy> Indeed. 12:41:55 <atinm> Also we'd need some volunteer for brick multiplexing which is sort of a must in 4.0? 12:42:02 <ndevos> msvbhat is the main contact for that, but anyone in the Gluster community can request an account 12:43:03 <jdarcy> The lack of anyone to work on brick multiplexing is one of my biggest 4.0 concerns right now. 12:43:54 <atinm> jdarcy, right 12:44:10 <atinm> aravindavk, you have anything on Eventing side? 12:45:02 <atinm> #info Eventing design : http://review.gluster.org/#/c/13115/ 12:45:21 <atinm> lpabon, would you be able to look at the updated design? 12:45:42 <lpabon> atinm, Yes, I will make sure I reply back by friday 12:45:49 <atinm> lpabon, thanks! 12:45:53 <lpabon> np 12:45:56 * kshlm will be AFK for ~5 minutes 12:46:02 <atinm> #action lpabon to review Eventing design 12:46:06 <msvbhat> ndevos: Yeah, As I said, I'm in the process of creating Jenkins job. Will update once done 12:46:25 <atinm> Anything else in 4.0? 12:46:31 <ndevos> msvbhat: yes, thanks! 12:46:59 <aravindavk> atinm: not much progress on POC last week, updated the design which is under review 12:47:15 <atinm> jdarcy, anything which I missed out from 4.0? 12:47:26 <jdarcy> Nothing I can think of, but my brain is fried. 12:47:31 * msvbhat skips rest of the meeting 12:47:33 <atinm> jdarcy, ;) 12:47:38 <atinm> Moving on then 12:47:47 <atinm> #topic Open Floor 12:47:58 <atinm> however there is nothing for today! 12:48:11 <kkeithley> did anyone ever build 3.6.8 for Debian? kshlm? 12:48:33 <josferna> can we talk about the WORM retention proposal that was sent today by karthikfff ? 12:48:36 <kkeithley> s/for Debian/packages for Debian/ 12:49:01 <josferna> can ppl review the patch and design ? 12:49:09 <atinm> kkeithley, we had a community user complaining about urcu related failures and then I believe his problem got resolved with the updated package, isn't it? 12:49:38 <kkeithley> atinm: Debian Wheezy, IIRC 12:50:32 <kkeithley> not an issue for Jessie or Sid 12:51:01 <atinm> kkeithley, right, and its for 3.7.6 12:51:06 <kkeithley> s/3.6.8/3.5.8/ 12:51:26 <ndevos> josferna: please move the design to the glusterfs-specs repository where we can add comments on it 12:51:31 <kkeithley> did anyone build 3.5.8 packages for Debian? 12:51:49 <josferna> ndevos, Yep will do that 12:53:38 <atinm> kkeithley, I think kshlm is afk for some time, probably you can catch him offline? 12:53:54 <atinm> So anything else on the open floor? 12:54:29 <kkeithley> yes, 3.7.x urcu on Debian Wheezy is solved. 12:55:22 <atinm> I take it as No 12:55:34 <atinm> So coming to next week's moderator 12:55:47 <atinm> Any volunteers? 12:56:39 <atinm> or else I will have to pick names alphabetically ;) 12:56:51 <josferna> atinm, are the best :) A for Atin 12:57:20 <atinm> josferna, nopes, my turn is over :) 12:57:37 <kkeithley> E for Elwin 12:57:45 <atinm> so let me go in a different way this time and pick josferna as the moderator for next meeting 12:57:56 <kkeithley> lol 12:58:03 <josferna> atinm, I am new for this stuff 12:58:12 <josferna> yet to learn from u guys 12:58:14 <kkeithley> you can handle it 12:58:14 <josferna> ;) 12:58:31 <atinm> josferna, there is no rocket science here :) 12:58:36 <atinm> so that's a deal 12:58:38 <josferna> atinm, ok 12:58:45 <josferna> atinm, I will do it guide me 12:58:47 <josferna> :) 12:58:55 <atinm> josferna, you are the moderator for next week 12:59:00 <josferna> cool 13:00:44 <josferna> bye 13:00:45 <atinm> #info If you're attending any event/conference please add the event and yourselves to Gluster attendance of events: https://public.pad.fsfe.org/p/gluster-events 13:00:46 <atinm> #info Put (even minor) interesting topics on https://public.pad.fsfe.org/p/gluster-weekly-news 13:00:46 <atinm> #info Use the following etherpad for backport requests https://public.pad.fsfe.org/p/gluster-backport-requests 13:00:46 <atinm> so we are on time and that concludes today's discussion! 13:00:46 <atinm> anything else we'd need to discuss? 13:01:02 <atinm> I take it as no 13:01:05 <ndevos> thanks atinm! 13:01:07 <atinm> thanks everyone for attending 13:01:15 <josferna> atinm, thanks atinm ! 13:01:15 <atinm> #endmeeting