15:06:10 #startmeeting Community Meeting 2017-08-02 15:06:10 Meeting started Wed Aug 2 15:06:10 2017 UTC. The chair is kshlm. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:06:10 Useful Commands: #action #agreed #halp #info #idea #link #topic. 15:06:10 The meeting name has been set to 'community_meeting_2017-08-02' 15:06:20 Thanks for coming in everybody. 15:06:51 We have no topics for discussion currently, so I'll move on to AI updates 15:07:09 #topic ndevos will check with Eric Harney about the Openstack Gluster efforts 15:07:24 ndevos, I see updates on this! 15:07:39 Any thing else you want to add on this? 15:07:40 yes, I've had some emails and got replies from the OpenStack devs 15:08:14 next step is to find volunteers to maintain the Gluster volume driver in Cinder and the CI testing of that 15:08:37 I'll reach out to the gluster-users about that later, maybe on Friday, maybe early next week 15:09:04 * loadtheacc is here 15:09:11 ndevos, Thanks for taking this this far. 15:09:22 sure, np 15:09:45 From what I read, all we need is that we setup a CI job. Is it just that? 15:09:55 * kshlm say hey loadtheacc 15:10:49 Seems like it. 15:11:11 not only CI, also a Cinder maintainer 15:11:11 ndevos, I'll wait for your mail for more information. 15:11:32 . 15:11:42 maintenance should be very limited, the CI job is the most involved task 15:11:59 I'm hoping maintainer of just the glusterfs Cinder bits. 15:12:13 yes, only for the Gluster volume part of Cinder 15:12:55 any volunteers can expect support from different Gluster developers, so I dont expect that to be difficult 15:13:01 I would think so as well. I think it would need a Openstack environment for that. 15:13:30 well, some experience with OpenStack would be good for sure :) 15:13:38 I'd probably be willing to volunteer for that. I'll need to look at the scope first, but I should be able to squeeze that in. 15:14:03 JoeJulian, Cool! 15:14:15 but I do not see a problem of having a user with little development experience to be a maintainer, but ultimately that is an upstream Cinder decision 15:14:57 JoeJulian: it would be awesome if you can, I'll CC you on the email when I send a call-for-volunteers 15:15:06 +1 15:15:13 ndevos, Right. We'll wait for your email then. 15:15:20 ndevos++ 15:15:20 kshlm: Karma for devos changed to 1 (for the f26 release cycle): https://badges.fedoraproject.org/tags/cookie/any 15:15:48 ndevos, I'll move on if there's nothing else you want to add. 15:15:55 thats all, thanks 15:16:20 #topic JoeJulian to invite Harsha to next meeting to discuss Minio 15:16:49 JoeJulian, I don't have any context on this, can you fill us in on why this AI is on you? 15:16:56 I have not done that. $dayjob has consumed every moment I've had for the last couple of weeks. 15:17:54 Ok. You can take your time. :) 15:18:11 I'm still curious though. What was the context for this? 15:18:15 There was conversation about adding gfapi backend to minio, iirc. 15:18:29 It was 3 weeks ago. I'd have to go back to the meeting log. 15:18:52 we want to have an S3 service for Gluster, minio would be one option 15:18:58 Ah. A possible object frontend for gluster. 15:19:26 That would mean more work on go-gfapi. Sounds interesting to me. 15:19:29 I'd be a little surprised if AB didn't still have a soft spot for us. 15:21:21 Hope so. 15:22:44 JoeJulian, Hope we have this conversation soon. 15:22:58 I'll move on to the next topic if there's nothing else to add. 15:23:15 nothing more 15:23:26 Thanks. 15:23:41 #topic shyam will edit release pages and milestones to reflect 4.0 is STM 15:24:02 I remember seeing 4.0 as STM somewhere on Github. 15:24:07 But now can't seem to find it. 15:24:22 The Release project doesn't mention it as such. 15:24:44 wasn't that a topic of last week's maintainer meeting? 15:24:52 thus in the minutes 15:25:17 Hmm, was it from the maintainers meeting? 15:25:30 Then why did it land in the AIs here? 15:25:32 thought it was. I could be wrong 15:26:02 Anyways, I think shyam has done part of it. 15:26:35 I found the changes on the milestones page. https://github.com/gluster/glusterfs/milestones?direction=asc&sort=due_date&state=open 15:26:47 https://www.gluster.org/community/release-schedule/# still says LTM 15:27:24 Should be an easy change. I can send a PR for that. 15:28:30 I sent a PR two days ago for http://gluster.readthedocs.io/en/latest/Install-Guide/Community_Packages/ 15:28:41 but it hasn't been pulled 15:29:21 shyam has sent a PR https://github.com/gluster/glusterweb/pull/146 15:29:49 kkeithley, I don't see any other PRs on the repo. 15:30:10 Oh wait. That will be on the glusterdocs repo. 15:30:36 PRs on glusterdocs are being merged mainly by ppai. 15:30:54 yup 15:31:06 but I don't see my PR either 15:31:14 He's been a little busy with GD2. I'll prod him when I see him tomorrow. 15:31:55 Looks like ppai got to it already https://github.com/gluster/glusterdocs/pull/247 15:32:27 nope, that's old. I just resent. Perhaps I didn't push all the buttons 15:33:39 I'll let ppai know anyways, to expect a PR from you. 15:33:58 thanks 15:34:08 Any other topics or AIs to discuss? 15:34:19 I'm assuming this AI is done for now. 15:34:50 (The remaining AI is not scheduled to be done by either amar or nigel soon) 15:36:09 Any updates that we want to discuss? 15:36:36 I sent an update on GD2 earlier today https://lists.gluster.org/pipermail/gluster-devel/2017-August/053432.html 15:37:07 I'm happy to discuss some more about that here. 15:38:58 No takers? 15:39:51 What about releases? 15:40:23 3.10.5 is up for tagging this week. 15:41:04 And 3.12 rc0 is also targetted for later this week. 15:42:02 And that's all the things we had on the meeting pad for this week. 15:42:23 kshlm, I can merge that PR into glusterweb, didn't get the ping. 15:42:57 amye, Cool. That would complete shyam's AI. 15:43:49 Anyone have any last thing to add before I end the meeting? 15:43:50 Done 15:44:03 * kshlm will end the meeting in 30 seconds. 15:44:07 amye, Thanks. 15:44:44 Wow. The website updates fast. 15:45:17 I'm ending the meeting. 15:45:25 Thanks for coming in today everyone. 15:45:30 See you next time. 15:45:32 #endmeeting