18:00:49 #startmeeting trove 18:00:50 Meeting started Wed Sep 24 18:00:49 2014 UTC and is due to finish in 60 minutes. The chair is SlickNik. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:00:51 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 18:00:53 The meeting name has been set to 'trove' 18:01:02 Giving folks a couple of minutes to trickle in 18:01:05 o/ 18:01:37 ./ 18:01:48 o/ 18:01:55 Agenda at: 18:01:57 #link https://wiki.openstack.org/wiki/Meetings/TroveMeeting#Agenda_for_Sep_24 18:02:55 hello 18:03:26 hi coolsvap — welcome 18:03:43 hello all 18:04:07 #topic Juno RC1 18:04:17 o/ 18:04:18 o/ 18:04:25 #link https://bugs.launchpad.net/trove/+milestone/juno-rc1 18:04:30 o/ 18:05:02 We're looking at tagging the Juno RC1 for trove next week. 18:05:06 o/ 18:05:19 o/ 18:05:57 oS 18:05:59 SlickNik, there are two bp's targeted for rc1, is that correct? I thought we are now down to bug fixes? no? 18:05:59 SlickNik: as a part of that process, we'll need to re-tag the client due to https://github.com/openstack/python-troveclient/commit/4c122dca77e619e8f9490bf612a30b3e77f75c82 18:07:07 amrith: Yes, we're tracking bugfixes now, we need to get these merged by next week. 18:07:28 amrith: After that, only release critical bugfixes will make it to Juno. 18:07:42 So we all need to work on reviewing these bugfixes to get them in. 18:08:05 amcrn: gotcha. I'll take a look at pushing a new version of the trove-client out. 18:08:06 SlickNik, i need a moment in the bug fix topic 18:08:20 so to be clear, I wasn't reviewing the ones tagged with bp's. do I understand you right in saying that the two bp's are still for juno? 18:09:09 o/ 18:10:22 amrith: Right we shouldn't be reviewing any BPs right now — only bugs. 18:10:31 ok, thx 18:11:13 All BPs in the pipeline should merge into Kilo, once that branch opens after the final Juno RC has been tagged. 18:11:14 o/ 18:12:01 So as a team we need to look at the bug list at: https://bugs.launchpad.net/trove/+milestone/juno-rc1 18:12:11 and work on getting those merged as a top priority. 18:12:45 whats the date for rc1? 18:13:15 SlickNik, I think the bug #1366939 needs a different fix 18:13:16 Launchpad bug 1366939 in trove-integration "Cannot kick-start non-MySQL due to validation-rules.json" [High,Fix committed] https://launchpad.net/bugs/1366939 18:13:48 iccha2: Sometime next week — I still need to finalize that with ttx. 18:14:10 mat-lowery, do you think the same? 18:15:03 I'm trying to understand what's wrong with the existing fix. Do you know? I haven't looked at it yet. 18:15:12 coolsvap: That fix is in trove-integration which isn't part of the integrated release and we can fix even after RC1. 18:15:34 coolsvap: If you think it isn't fixed, please put the relevant info in the bug, and reopen it. 18:15:54 SlickNik, okay sorry to interrupt, I was not aware 18:16:07 coolsvap: no problem. 18:16:32 Any other questions/clarifications on Juno RC1? 18:16:36 btw wrt that bug i made it so that you dont need to look up the version uuid any more 18:16:50 so SlickNik, will we have an RC2, or do we decide that next week? 18:17:00 johnma: good question. 18:17:33 We will have an RC2, if we need one: i.e. only if we feel that there is a bugfix that is critical and needs to be part of Juno. 18:17:54 If not RC1 becomes our final juno RC. 18:18:06 and the branch opens for checkins to kilo. 18:18:33 #link https://wiki.openstack.org/wiki/Juno_Release_Schedule 18:18:45 ^ Explains the timing a little better. 18:18:47 sounds like a plan. Thanks SlickNik 18:20:19 Any other clarifications? If not, let's get these bugs and reviews knocked out this week! :) 18:21:07 Also, _please_ ping me if you come across a bug that you believe is critical and warrants a fix in RC1 — so that we can triage appropriately. 18:21:12 o/ 18:21:59 #topic Kilo Design Summit 18:22:21 #link http://ttx.re/kilo-design-summit.html 18:22:49 So I've been talking to the organizing folks about the Kilo design summit. 18:23:30 And across the board, it seems like folks will have fewer session slots. 18:23:45 because of space / time constraints. 18:24:10 For Trove we will have 4 design summit session slots. 18:24:28 SlickNik, how long is each one? 40 min? 18:24:30 And a half day space for our "contributors meetup" 18:24:46 dougshelley66: Yes, 40 minutes, I believe. 18:24:48 SlickNik: is that code for an argument that lasts several hours? 18:25:16 kevinconway: I don't think so — although I'm sure I can find pod space for that if folks are interested :P 18:26:08 Another thing to note is that we're coming up with design summit suggestions using Etherpad this time. 18:26:20 Instead of the web tool we had last time. 18:26:30 So that it can be a bit more collaborative. 18:27:02 I'll set up an etherpad with some structure by end of this week, and will send out a link so that folks can propose design sessions. 18:27:47 It'll be linked from https://wiki.openstack.org/wiki/Summit/Planning 18:27:52 #link https://wiki.openstack.org/wiki/Summit/Planning 18:28:03 So keep an eye out on that. 18:28:44 Some projects have already started doing this, so you can get a glimpse of how it's going for them if you look on that page. 18:32:19 #link https://etherpad.openstack.org/p/kilo-trove-summit-topics 18:33:13 ^^ Use this to propose what you'd like to see as a design summit session. 18:34:29 Any questions regarding the design summit? 18:35:23 . 18:35:37 #topic Open Discussion 18:35:55 i have one 18:36:05 amrith: go for it 18:36:07 friday at summit 18:36:18 I've heard that a bunch of people will be leaving early on friday 18:36:27 are we going to have anything on friday? 18:36:32 could we avoid it? 18:37:27 amrith: So Friday is the contributors' meetup — we have a half day space with an open agenda. 18:37:38 which half? 18:38:02 not sure yet, ttx is figuring out the schedule. But I'm pushing for the earlier half. :) 18:38:21 ok, that'd be good because I hear that several are leaving in the latter half. 18:38:28 not me, I'm told I stay till Sunday 18:39:02 Hopefully we can cover most of the important topics during the sessions itself. 18:39:53 If we need more time, I'm going to see if we can get some space and call for an impromptu session or two the day before (Wed) — kind of like we did at ATL. 18:40:11 ok, thx SlickNik 18:40:51 Not a problem! 18:40:59 ANy other questions / comments? 18:41:16 If not, I have one. :) 18:41:20 will marshmallows also be a central theme for this conference? 18:41:35 *context?* 18:42:02 kevinconway: I hope not — those conversations take wayy long :) 18:42:49 So we've got a new kid on the block who's going to be working with us on Trove. 18:43:04 o/ (sorry for being late) 18:43:16 denis is the new kid? 18:43:21 ;) 18:43:21 that's what i was asking 18:43:25 edmondk: meet the rest of the Trove team — Trove team meet edmondk :) 18:43:28 great timing denis_makogon 18:43:30 Hello 18:43:35 lol @ denis_makogon 18:43:45 hi edmondk 18:43:52 Hello Edmond, welcome to the team 18:43:56 edmondk, welcome! 18:43:57 Thank you 18:44:00 * georgelorch waves 18:44:03 edmondk, hi =) 18:44:42 o~ 18:45:37 He's still getting up to speed with OpenStack and the process, and sit a couple of rows down from where I do. 18:46:33 Hope to start making contributions as soon as possible. Trying to figure out the process this week. 18:47:20 Okay, anything else - anyone? 18:47:21 feel free to ping us with any question you have 18:47:29 will do 18:47:34 nice! 18:47:37 thanks 18:47:51 #endmeeting