18:01:02 #startmeeting trove 18:01:02 Meeting started Wed Apr 2 18:01:02 2014 UTC and is due to finish in 60 minutes. The chair is SlickNik. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:01:03 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 18:01:04 o/ 18:01:05 The meeting name has been set to 'trove' 18:01:18 0/ 18:01:22 o/ 18:01:23 o/ 18:01:25 oh I was too early :) 18:01:27 o/ 18:01:32 Gonna give folks a couple of minutes to trickle in. 18:01:41 o/ 18:01:43 imsplitbit: the last meeting ran late 18:01:50 #link https://wiki.openstack.org/wiki/Meetings/TroveMeeting 18:02:00 Pretty light agenda today. 18:02:02 o/ 18:02:32 o/ 18:02:36 sup yall 18:02:40 #link http://eavesdrop.openstack.org/meetings/trove/2014/trove.2014-03-26-18.01.html 18:02:52 #topic Action Items 18:03:07 None here from last week, so moving on. 18:03:16 SlickNik: That was fast 18:03:17 o/ 18:03:43 Get cwied 18:03:47 o/ 18:03:51 grapex: lol, feel free to add anything if you'd like. 18:03:59 Get/hey 18:04:00 o/ 18:04:03 #topic Icehouse RC1 cut and Juno branch open 18:04:04 * grapex hisses and moves back into the shadows 18:04:04 o/ 18:04:13 lol grapex 18:04:23 Cwied/cweid 18:04:24 yay! 18:04:27 horray, now we can do more code, Juno is opened =) 18:04:33 So we cut the RC1 last night. 18:04:39 so that means we can start reviving all the reviews that were -2'ed in the great culling? 18:04:42 I am confused 18:04:51 kevinconway: Exactly! 18:04:53 kevinbenton, yes 18:04:55 yay more bugs…I mean features 18:04:58 kevinconway, yes =) 18:05:09 This means two things, really. 18:05:43 1. As kevinconway said (and all of you know) we can start getting the Juno patches moving. 18:06:05 On approved blueprints.. 18:06:14 Yay! 18:06:16 juice, bugs also 18:06:17 :) 18:06:20 2. Also if you guys find a bug with the icehouse release that's critical and a potential show stopper, please file it ASAP and let us know about it. 18:06:28 And bugs 18:06:35 In case we need a fix, and need to cut an RC2. 18:06:52 o/ 18:07:06 But if no critical bugs are found, this RC1 is what's going to be released as the IceHouse milestone release for trove. 18:07:39 (There's a branch on github called milestone-proposed, if you want to test it out from sources) 18:08:02 right, we need to search for critical bugs, and review more patches that holds since feature freeze happend 18:08:31 cweid: still confused? 18:08:43 Any questions regarding this? 18:08:53 cweid: ^^ 18:08:57 sorry 18:09:00 cweid: cweid cweid cweid 18:09:02 was not paying attention 18:09:19 reading... 18:09:23 Did you mention branching? 18:09:29 Did I? 18:10:14 Not you cweid: slicknik. When you say cut does that mean a branch of our git repo? 18:10:27 juice: we don't do anything differently wrt branching for any of the new Juno patches we want to land. If any fixes need to be backported, they will need to be checked into a different branch. 18:11:01 K 18:11:07 Ok I am on the same page. 18:11:09 juice: cut was just referring to the release. It's OpenStack release speak. 18:11:33 i.e. tagging the branch as milestone-proposed, and creating a tarball for the RC 18:11:43 Ah a tag. Thanks 18:11:55 np, let's move on. 18:12:03 #topic ATL Dev summit topics. 18:12:15 #link http://summit.openstack.org/ 18:12:26 I would like to submit a user talk. 18:12:42 Please get your sessions in soon. 18:13:02 #link http://summit.openstack.org/cfp/details/150 18:13:20 at least now we have one session submitted 18:13:22 cweid: sweet. 18:13:25 it's mine 18:13:42 do we plan to vote for sessions ? 18:13:44 denis_makogon: Hopefully we'll have more than 1 session. 18:13:56 SlickNik, yeah, it's only the beggining 18:14:15 denis_makogon: There are no votes for design sessions 18:15:33 The PTL and cores, with contributor feedback usually decide what makes sense from a roadmap perspective, and what would be the best use of design summit time. 18:15:49 Just a reminder to get your proposals in. 18:15:50 sorry, was dropped of 18:16:15 I think hub_cap was planning on starting some reviews end of this week/beginning of next. 18:16:36 So it would be good to have that info in there, even if it's just a placeholder for now, with details to follow. 18:17:16 Any questions? Anything you want to add grapex? 18:17:21 what about discuss all proposed sessions at one of the meeting, near the summit 18:17:52 SlickNik: Not much at the moment, but we'll try to get more submissions in from Rax soon 18:18:18 denis_makogon: There are usually a lot of sessions, and I want to be respectful of people's time in the meetings. You can definitely bring it up in the IRC channel if you'd like. 18:19:03 Okay, let's move on. 18:19:15 #topic Open Discussion 18:19:18 SlickNik, i think we should do that, like we do the BP meeting 18:19:20 o/ 18:19:37 what do you think about https://blueprints.launchpad.net/trove/+spec/cross-region-backup-migration? 18:19:37 go for it kevinconway 18:19:43 oops 18:19:46 so if you were at the mid-cycle… SIGN THE GPG KEYS! 18:19:48 ill go after kevinconway 18:20:16 can you please explain what is that key signing party ? 18:20:36 basically when we meet in person we can swap key signatures 18:20:41 * SlickNik has been slacking off on this and hopes to get it done today, now that RC1 is cut. 18:20:43 then you can go back and sign the keys of people you know 18:21:28 so yeah, please sign 'em keys when you get a chance! 18:21:47 And thanks to the folks who have already done so. 18:22:02 esmute, you had something? 18:22:04 so, then signer will have key signed by the people who he met ? 18:22:07 yes 18:22:19 working on a way to migrate backups from one region to another 18:22:21 #link https://blueprints.launchpad.net/trove/+spec/cross-region-backup-migration 18:22:39 denis_makogon_: http://en.wikipedia.org/wiki/Key_signing_party 18:22:56 i was thinking of overloading the create() to take a location_Ref to create a backup 18:23:15 SlickNik, ah, thanks, a lot 18:23:48 trove manager will taken fetch and push the backup (using the exisiting streaming operation read/save) to its own storage 18:24:01 taken = then 18:24:10 denis_makogon_ became poetic .. with emotional gestures 18:24:17 esmute: you might want to add that to the bp-meeting agenda. 18:24:31 esmute: Yeah, it looks interesting 18:24:32 ok 18:24:48 i know many people hasnt had a chance to look at it... we can talk more aobut it next meeting 18:24:50 esmute: https://wiki.openstack.org/wiki/Meetings/TroveMeeting at the bottom of the page. 18:25:11 esmute, region means OS region ? 18:25:22 denis_makogon_: yes. 18:26:01 esmute, i really looks interesting, how do you plan to mention region ? 18:26:06 esmute, through params ? 18:26:34 the idea is to move backups that have already been created in one region to another 18:27:01 a good use case is if an user wanted to migrate his/her DB to a different region 18:27:10 esmute, i think there are several options, one is "move", another is "replicate" 18:27:45 esmute / denis_makogon_: Let's give folks time to go through the bp, and wiki page. 18:28:04 esmute, as i remember Swift could work as single service through multiple regions, and replicate it's data through the nodes 18:28:05 We can discuss the finer points during our bp review meeting as well. 18:28:24 SlickNik, of course, just thinking too loud =) 18:28:34 denis_makogon_: we can talk more in the #openstack-trove 18:28:44 or feel free to put comments the BP :-) 18:28:45 esmute, definitely 18:29:23 Thanks guys. 18:29:33 esmute, lets first commulate requirements and use cases, and of course possibilities 18:29:52 SlickNik, are we done with agenda ? 18:29:53 Anything else for the open items? 18:30:00 going, going.... 18:30:05 i think nope =) 18:30:10 #endmeeting