12:00:49 #startmeeting 12:00:49 Meeting started Wed Aug 5 12:00:49 2015 UTC. The chair is rafi. Information about MeetBot at http://wiki.debian.org/MeetBot. 12:00:49 Useful Commands: #action #agreed #halp #info #idea #link #topic. 12:01:10 #info agenda is at https://public.pad.fsfe.org/p/gluster-community-meetings 12:01:32 #topic Roll Call 12:01:39 * spot is here 12:01:40 * overclk is here 12:01:40 * anoopcs is here 12:01:41 * kdhananjay is here 12:01:43 * shyam will start attending 20-25 minutes into the meeting 12:01:44 * poornimag is here 12:01:46 * ndevos _o/ 12:01:49 #chair kdhananjay ndevos 12:01:49 Current chairs: kdhananjay ndevos rafi 12:01:50 * atinm is here 12:01:53 * skoduri is here 12:01:54 * jiffin is here 12:01:59 * rjoseph is here 12:02:05 * msvbhat is here but will come back again in 10 minutes with Tea 12:02:08 * rafi is here 12:02:14 * kkeithley is here 12:02:35 * kshlm is here! 12:02:39 Has the meeting started? 12:02:39 * ira is here. 12:02:46 kshlm, it has 12:03:26 * rtalur is here 12:03:41 we have pretty good number of attendees ;) 12:03:51 and three on chair ;) 12:03:52 * tigert is in 12:03:58 moving on 12:04:14 #topic action items from last week 12:04:29 * kotreshhr is here 12:04:35 * raghu is here 12:04:44 * obnox is here 12:04:51 #info tigert summarize options for integrating a calendar on the website, call for feedback 12:05:13 tigert: are you around ? 12:05:13 * pranithk is here 12:05:20 * hagarth in now.. around for next 25 minutes 12:05:24 * meghanam is here 12:05:26 tigert: do you want to update on this ? 12:05:56 I have been looking at the options now that I am back from vacation, but its in progress 12:06:13 tigert: cool, 12:06:16 so I intend to post a mail about what I have found and asking for more ideas once I have some more thouhts gathered in my head 12:06:18 tigert: are you preparing an email with some options/suggestions? 12:06:30 so I am, but did not make it for todays meeting yet 12:06:48 tigert: so let's carry forward this for next meeting 12:06:50 okay, sounds good, thanks! 12:06:59 I guess -infra is the correct place for that discussion? 12:07:02 yeah 12:07:05 rafi: +1 12:07:08 #action tigert summarize options for integrating a calendar on the website, call for feedback 12:07:15 next one 12:07:17 infra sounds good, 12:07:20 (it's nice to be back, everyone :) 12:07:37 #info hagarth and raghu to prepare release-schedule 12:07:47 tigert: +1 :) 12:08:24 rafi: A mail has been sent to gluster-devel. Based on the feedback, gluster.org will be updated 12:08:49 raghu: cool 12:08:51 raghu: link to the mail in the archives? 12:09:17 #link - http://www.gluster.org/pipermail/gluster-devel/2015-August/046336.html 12:09:19 ndevos, I think it just hit the mailbox few minutes back 12:09:58 thanks hagarth! 12:10:01 #action based on the feed back from the mail sent bu raghu , gluster.org need to update 12:10:09 *by 12:10:33 moving into next topic 12:10:52 #topic overclk to create a feature page about lockdep in couple of week's time 12:11:00 overclk: Any update on this? 12:11:06 kdhananjay: that's done. https://github.com/gluster/glusterfs-specs 12:11:19 kdhananjay, https://github.com/gluster/glusterfs-specs/blob/master/Feature%20Planning/GlusterFS%204.0/lockdep.md 12:11:32 thanks hchiramm for merging the pull request. 12:11:46 overclk, yw 12:12:04 As of now I've just mentioned myself in the owner list. 12:12:07 overclk, finally! 12:12:11 #link feature page is at https://github.com/gluster/glusterfs-specs/blob/master/Feature%20Planning/GlusterFS%204.0/lockdep.md 12:12:15 kshlm: oh yeh! 12:12:40 hchiramm: was glusterfs-specs not supposed to be a gerrit repo? 12:12:45 IIRC, few others were interested too. raghu, krishnan_p ? 12:12:52 I thougt we would use that for commenting on specs? 12:13:20 overclk: yes. I am interested. 12:13:39 ndevos: yes, that is right 12:13:50 raghu: okies. I'll probably do the needful. Go through the feature page anyway... 12:14:04 overclk: sure. 12:14:22 * ndevos wonders how we can comment on a spec that has been merged alread? 12:14:28 ndevos, however we can have it in gluster-specs as a scratch page . 12:14:46 hchiramm: sure, but this gets really confusing :-( 12:14:54 hchiramm: yes, this is confusing 12:15:09 we can use the same gerrit we have 12:15:22 a new project should be enough 12:15:24 rtalur, yes, we need to setup a project in gerrit for the same 12:15:38 then keep tracking the patches.. its not there yet.. 12:15:58 action item on me, if you would help with it 12:16:05 rtalur, sure 12:16:20 kdhananjay: You can add that action item on me. 12:16:27 #action rtalur setup a new project gerrit specs in review.gluster.org 12:16:46 Moving on ... 12:16:54 #topic hagarth to do 3.7.3 announcement on the gluster blog and social media 12:17:09 * rafi is searching on https://www.facebook.com/GlusterInc 12:17:33 hagarth: do you want to add anything ? 12:17:34 I don't think it has been announced yet 12:17:56 rafi: will work on kshlm for this one 12:18:00 there's email on gluster-users about 3.7.3 released 12:18:04 s/on/with/ 12:18:11 hagarth: sure 12:18:26 kkeithley, I meant social media 12:18:45 #action hagarth and kshlm will announce 3.7.3 release on the gluster blog and social media 12:19:08 Just to note, bind-insecure is the default with 3.7.3 and needs to be mentioned in the release announcements. 12:19:12 hagarth: Don't wait for my blog/mail as we are waiting for some info from a user who raised a data corruption bug on ec which is not re-creatable. Xavi and I decided we will wait a day 12:19:26 pranithk: ok 12:19:34 I couldn't add this to the release-notes as I didn't know about it then. 12:20:05 #info 3.7.3 defaults to bind-insecure/allow-insecure, which causes some issues with older clients/servers. 12:21:06 kshlm: hagarth : any thing more on this 12:21:20 rafi: nothing more here from me 12:21:24 rafi, No more. 12:21:34 then moving on to next topic 12:21:36 #topic pranithk to write up a post announcing EC's production readiness. 12:22:09 pranithk just said he 12:22:13 rafi: ^^ 12:22:18 's still waiting 12:22:28 pranithk: Based on your comment above, do we add this as an action item on you for next week? 12:22:36 kdhananjay: yes please 12:22:50 #action pranithk to write up a post announcing EC's production readiness. 12:23:16 pranithk: great 12:23:19 moving on 12:23:21 #topic rtalur to send update mailing list with a DiSTAF how-to and start discussion on enhancements to DiSTAF. 12:23:45 rtalur: I couldn't see a mail regarding this on gluster-devel, 12:23:53 rtalur not here, probably carry on for next week 12:24:00 poornimag: ok 12:24:21 #action rtalur to send update mailing list with a DiSTAF how-to and start discussion on enhancements to DiSTAF. 12:24:51 we will discuss this topic next week 12:24:55 next topic 12:25:03 #topic kshlm to test the new jenkins slave in ci.gluster.org - did some tests, but misc did most of the testing. I'll continue this week. 12:25:16 oops :P 12:25:18 and the last one :) 12:25:23 Well I already answered it :) 12:25:32 Sorry about that, kshlm. :) 12:25:44 Moving on... 12:25:56 #topic Glusterfs 3.7 12:26:52 kshlm: Do you want to take over? 12:26:54 I've created a tracker for 3.7.4 12:27:19 The current plan is to do the release in the last week of August, following on from the discussion from last week about monthly releases. 12:27:22 That's all. 12:27:24 kshlm: do we have target milestones for 3.7.4 in bugzilla now? 12:27:46 hagarth, Nope! I forgot about this. 12:27:48 yes, but they're at the end of the list of Target Milestones 12:28:00 kkeithley: ok cool! 12:28:03 hagarth: we dont use milestones, unless it gets documented in the workflow 12:28:04 right where you'd _not_ expect to find them 12:28:12 ndevos: ah ok 12:28:21 I set them, for myself 12:28:30 also, open bugs: https://bugzilla.redhat.com/showdependencytree.cgi?id=glusterfs-3.7.4&maxdepth=1&hide_resolved=0 12:29:24 I need to prune that list. Some of the bugs there have already been fixed according the comments in them. 12:29:59 kshlm: and poke the assignees to send patches, or fix the status of the bugs 12:30:16 ndevos, I plan to the same. 12:31:11 #info developers/assignees of the bug should update the bug properly 12:31:54 #info we need a clean list of tracker bug that are targeted for glusterfs-3.7.4 12:32:09 any thing more on 3.7.4 12:32:11 if an assignee thinks the bz doesn't belong to them, what should they do? reset the assignee and remove Triaged? 12:32:27 and they don't know who it should be assigned to? 12:33:06 kkeithley: that would be a good idea 12:33:47 kkeithley: so that we can discuss about this bug in bug traige meeting and take decision whether we need to consider for release tag 12:33:53 for any weird status' of bugs, you can also set needinfo to bugs@gluster.org , it will get picked up during the next triage meeting then 12:34:38 #info not sure where a bug belongs, set a needinfo to bugs@gluster.org and the next triage meeting will check it out 12:35:06 kshlm: any thing more on topic 3.7 ? 12:36:01 possibly not. 12:36:10 Moving on 12:36:25 #topic GlusterFS 3.6 12:36:50 raghu`: Anything to talk about here? 12:36:53 Not much from me. I am planning to make 3.6.5 next week (atleast by end of next week). 12:37:32 kdhananjay: Backports are welcome. I have some backports from Vijaykumar. They are quota related patches. 12:37:56 request more backports from other components as well 12:38:38 raghu`: yeah, the resolve-gids might be good to get backported by then 12:38:59 ndevos: sure. It seems the patch has been accepted in master. 12:39:11 #info backport all the patches that need to get in for 3.6.5 within 1 weeks 12:40:08 raghu`: ah, I didnt see that yet, I'll have to do a pull request for the docs too then 12:40:19 #info tentative date for next release of glusterfs-3.6.5 will be Aug 14 12:41:02 any thing else ? 12:41:13 rafi: there are also a discussion going on about the release schedule. 12:41:54 rafi: If the feedback as to make releases as proposed in the mail, then probably 3.6.5 might happen bit later. 12:42:01 raghu`, I want to get BZ 1248298 backported to 3.6, will send the backport soon 12:42:17 atinm: sure. 12:42:27 raghu`: no problem, let's stick on release-schedule plan 12:42:39 rafi: sure. 12:42:45 raghu`: I just put a tentative date ;) 12:43:12 rafi: ok 12:43:36 It'll be good to have a release while I'm there. Then we can go over the packaging process with the new packaging "volunteers". ;-) 12:44:07 we still have some volunteers, right? 12:44:11 kkeithley: sounds good 12:44:36 kkeithley: when are you planning come ? 12:44:52 kkeithley: then we can schedule accordingly :) 12:45:17 kkeithley: Yep, I'm one of thew volunteer :) 12:45:24 I'll be in the office on the 17th. 12:45:25 s/thew/the 12:45:52 ok 12:46:18 kkeithley, yes.. 12:46:28 we will schedule a meeting once u r here 12:46:51 sure 12:47:10 so that's decided 12:47:20 let's move to next topic 12:47:44 #topic GlusterFS-3.5 12:48:09 ndevos: come out from the chair and speak up 12:48:14 ndevos: :) 12:48:23 the main change that I'd like to see in 3.5.6 is the gfapi cleanup from poornimag 12:48:31 there is a request for backporting set of patches for 3.5, but its still not backported to 3.6, we will have to backport it to 3.6 and then 3.5? 12:48:43 yes, that would be best 12:49:05 it should at least get posted for release-3.6 when the patches are done for 3.5 12:49:28 ok, and should it be released? before 3.5 releases? 12:49:47 no, that is not a hard requirement, it is a nice to have 12:50:24 ndevos: poornimag: Are these the glfs fini changes? 12:50:33 AFAIC the main thing is to have it posted to the main branch. 12:50:36 3.5 can have patches merged before 3.6, but the next 3.6.x should have those changes too 12:50:40 ok, So ~10 patchsets haven't tried the backport yet, will update the bz with findings by 7th 12:50:49 pranithk: yes 12:51:00 poornimag: do you want me to add an action item for backporting the glfs_fini ? 12:51:10 poornimag: wow, even more patches than I thought, thanks for looking into it! 12:51:19 poornimag: Okay I need to backport my patches which uncovered bugs in fini path... in snapshot etc. 12:51:39 yes, pranithk: ok 12:52:36 AFAIC the main thing is to have it posted to the main branch. After that the backports and releases on the branches can happen when they get done, when it's convenient. 12:52:53 convenient for a release 12:53:12 and as ndevos said, it's "nice to have" them happen 3.7 -> 3.6 -> 3.5 12:53:15 #info glfs_fini backport will be a blocker for 3.5.6 12:53:16 kkeithley, then probably i ll try for 3.5 before 3.6 12:53:44 rafi, yet to decide if it should be a blocker:) 12:54:17 #topic GlusterFS - 4.0 12:54:35 poornimag: I think it would be better to backport those changes to release-3.6 as well 12:54:38 poornimag: we'll just delay 3.5.6 until its ready :) 12:54:39 jdarcy : are you around ? 12:55:04 * shyam will announce DHT2 related work efforts and repository for Gl4.0 this week (on the devel list) 12:55:05 raghu, ndevos, alright 12:55:29 #action shyam will announce DHT2 related work efforts and repository for Gl4.0 this week 12:56:04 Jeff is on (P/F)TO to the best of my knowledge, could still be in the meeting though :) 12:56:27 krishnan_p: do you have any thing to add about Glusterd-2 12:57:14 alright , we can move on to last topic 12:57:20 #topic open floor 12:57:25 what about 3.8 12:57:28 ? 12:57:48 poornimag: it is not there in agenda 12:58:01 * kkeithley thinks that's her point! 12:58:09 yes:) 12:58:13 maybe add it to the agenda 12:58:23 poornimag: let's discuss in open floor 12:58:30 poornimag: kkeithley ; ;) 12:58:46 add it to the agenda for next week 12:58:57 kkeithley: sure, 12:59:20 and discuss now in open floor? 12:59:29 We have been having some discussions on upstream testing using DiSTAF, myself or rtalur will send out a notification soon 12:59:30 #action rafi need to add a new topic for GlusterFS 3.8 13:00:02 I want to do some prototype of the enhancements planned before sending out the mail 13:00:46 #agreed to use DiSTAF for upstream pre release testing 13:01:54 any thing more to discuss 13:02:05 rafi: I added about documentation... 13:02:15 * msvbhat has nothing else to discuss 13:02:26 rafi: Per release documentation. Users are landing on 3.2 documentation from google itseems. How can we make this better 13:03:18 pranithk: I think hchiramm is working on adding redirects from the old wiki to the new docs? 13:03:37 ndevos: I will work with him in that case. Thanks 13:03:47 #info REMINDER to put (even minor) interesting topics on https://public.pad.fsfe.org/p/gluster-weekly-news 13:04:12 #info REMINDER to announce Gluster attendance of events: https://public.pad.fsfe.org/p/gluster-events 13:04:22 OK, anything more? 13:04:30 I guess not. 13:04:53 we were 5 minutes later than scheduled time, sorry guys 13:04:59 OK everyone, thanks for attending. 13:05:00 #endmeeting