09:10:33 #startmeeting ptl_sync 09:10:34 Meeting started Tue Dec 2 09:10:33 2014 UTC and is due to finish in 60 minutes. The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot. 09:10:35 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 09:10:37 The meeting name has been set to 'ptl_sync' 09:11:08 Let's wait for John or Angus :) 09:11:13 Works for me 09:11:16 I'm just lurking really 09:11:22 I see this as a John meeting now 09:16:21 johnthetubaguy: o/ 09:16:35 ttx: hey, sorry, bit late out the shower this morning 09:16:50 No pb 09:16:51 #topic Nova 09:17:07 #link https://launchpad.net/nova/+milestone/kilo-1 09:17:11 Two weeks to milestone 09:17:24 yeah, I didn't do the pushing out of stuff thats not in review yet 09:17:28 I should do that this morning 09:17:33 Time to push back the stuff obviously not started, at least 09:17:44 I think some of the stuff marked as in review is actually implemented 09:17:47 https://blueprints.launchpad.net/nova/+spec/hyper-v-host-power-actions for example 09:17:51 * ttx checks 09:18:06 mikal: yeah, I plan to do a sweep, people tend not to update there blueprints much 09:18:35 or anti-affinity-on-migration 09:18:55 well, if our system was fully integrated, they wouldn't need to 09:19:18 vmware-spbm-support might be completed too 09:19:29 ttx: agreed 09:19:44 about the middle statement, need to check the others 09:20:08 protip: I use http://status.openstack.org/release/ to spot them 09:20:24 blueprints that have all green dots have all the linked reviews in 09:20:38 that doesn't mean they are complete, but they are generally good candidates 09:20:54 ttx: not see that one before, neat 09:21:20 The report actually fetches reviews that are linked from the blueprint whiteboard and gets status from them 09:22:05 so it relies on a weak association (gerrit adding a note to the whiteboard) 09:22:13 but it's better than nothing 09:22:34 johnthetubaguy: https://blueprints.launchpad.net/nova/+spec/log-request-id-mappings is interesting. The outstanding review at the end is an unapproved spec, I think that one shouldn't be approved? 09:23:05 mikal: its not approved, as such 09:23:30 Oh, pending approval 09:23:35 The "approver" being set confused me 09:23:38 remember that the blueprint page is now more of an external communication tool, so deferring a BP to k2 is just saying "that's where it looks like it will land". We can move the BP back to k1 if it suddenly makes progress 09:23:54 mikal: I don't reset that one when I un approve, takes too long 09:24:03 Fair enough 09:24:09 ttx: yeah, agreed 09:24:29 We should definitely unassign milestones for the unapproved specs then 09:24:35 "this is our best guess at what's coming in the short term" 09:24:36 Which is ttx's script, yes? 09:24:54 mikal: they mosty are, its the ones that got into kilo, somehow, that mess things up :( 09:25:08 mikal: well, sometimes you're pretty sure the spec will make it, so you still want to track it as a milestone objective 09:25:28 (we mark them as blocked) 09:25:41 (but don't think that's the case for this one) 09:25:46 Another one is https://blueprints.launchpad.net/nova/+spec/nova-pagination -- most recent review is a spec, is marked approved. 09:25:50 (I read the right field this time) 09:25:55 ttx: I keep wondering about doing that for stuff related to priority blueprints, so its easier to track the spec reviews, but not done that 09:26:15 mikal: not done my friday updating of specs yet 09:26:17 yes, sounds like a good way to track "priority blueprints" 09:26:30 lets them emerge from noise 09:27:19 johnthetubaguy: I'll let you update the list off-sync 09:27:46 yeah, meant to do that yesterday, but I am slammed right now :( 09:28:03 For the meeting today, remember it's a cross-project meeting and we announce it the day before now... so if you have topics to discuss, you should post them beforehand 09:28:19 directly on https://wiki.openstack.org/wiki/Meetings/CrossProjectMeeting 09:28:33 we'll discuss "Convergence on specs process" today 09:28:43 which you proposed last week 09:29:02 yeah… not done the ground work for that, but I can add some links to nova things 09:29:30 johnthetubaguy: anything else ? 09:29:38 ttx: nothing from me 09:29:43 johnthetubaguy: ok, ttyl! 09:29:52 asalkeld: still around ? 09:29:55 hi 09:30:00 mikal: thanks for lurking! 09:30:01 sorry i missed 09:30:05 asalkeld: np 09:30:08 #topic Heat 09:30:10 ttx: NP, although I feel I said too much 09:30:24 mikal: you should improve your lurking. 09:30:46 https://launchpad.net/heat/+milestone/kilo-1 09:31:02 2 weeks to go, this looks in relatively good shape 09:31:09 yeah 09:31:17 All started, most done or in review 09:31:17 2 to follow up on 09:31:26 the "started" ones 09:31:52 the patches are in review, i'll try see what is going on with those 09:31:53 yes, you should basically defer them to k2 once you're convinced they won't make it in k1 09:32:03 ok, makes sense 09:32:19 as I told John before, the idea is to use those pages to communicate when things are likely to land 09:32:27 sure 09:32:29 mostly to people external to your project 09:32:40 our best guess 09:33:02 yeah, i'll ping the author of those 2 bp's and see what's happening 09:33:17 we are doing a bug cleanup today 09:33:24 asalkeld: nice 09:33:33 so we are having quite a bit of bug changes 09:33:44 No other questions from me, did you have any ? 09:33:45 trying to figure out what is happening with old bugs 09:33:57 ttx, no all good from my pov 09:34:12 asalkeld: awesome, thanks for your time! 09:34:16 np 13:00:19 ttx: knock, knock ... ready when you are 13:01:04 eglynn: o/ 13:01:10 #topic Ceilometer 13:01:15 #link https://launchpad.net/ceilometer/+milestone/kilo-1 13:01:21 further progress on the kilo-1 roster 13:01:26 ... but still a couple of BPs blocked on specs landing 13:01:31 nice progress 13:01:40 I'm most concerned about instance-autorestart 13:01:51 since there hasn't been much recent traction on the reviews 13:01:58 I've emailed the author 13:02:00 well, two more weeks 13:02:07 (she doesn't normally hang out on IRC) 13:02:10 yeap 13:02:17 Once you're reasonably sure it won't make it, just move it to the k2 roster 13:02:33 yeap, will do 13:02:43 The two Blocked are waiting for spec to be approved, right? 13:02:56 yep 13:03:03 there are enough stake-holders in the other blocked spec (RBAC) to ensure it'll land, IMO 13:03:04 Is that likely to happen soon? 13:03:24 yeah, the rbac one is mostly a question of careful scoping 13:03:30 ok 13:03:36 careful speccing :) 13:03:55 (it currently includes some language about keystone v3 domains which are unused in the actual implementation) 13:04:00 Looks like you're in great shape, no other question from me 13:04:06 cool 13:04:14 2014.2.1 due out this week also 13:04:26 yes, we'll mention it during the meeting today 13:04:27 #link https://launchpad.net/ceilometer/+milestone/2014.2.1 13:04:52 so... 5 backports you'd like to include in it ? 13:05:11 yeap, I've a 5 freeze exceptions requested, but happy to go with just the landed backported if necessary 13:05:21 landed *backport 13:05:23 landed *backports 13:05:28 ok, I suspect they are all on apevec radar ? 13:05:48 yeap, on the etherpad, spoke to him about it this morning 13:06:24 ok great 13:06:28 Other questions ? 13:06:38 nope, nothing else from me 13:06:47 eglynn: ok, have a great day then 13:06:53 cool, thanks for your time! 13:06:55 SergeyLukjanov: ready when you are 13:07:02 ttx, ready 13:07:05 ttx, hi 13:07:09 #topic Sahara 13:07:22 #link https://launchpad.net/sahara/+milestone/kilo-1 13:07:23 https://launchpad.net/sahara/+milestone/kilo-1 13:07:32 nice green 13:07:53 ttx, mostly all of the features are now in review/gating state 13:08:10 checking for some completion 13:08:36 event-log might be completed already ? 13:09:01 https://blueprints.launchpad.net/sahara/+spec/indirect-vm-access is implemented, but spec isn't completely approved 13:09:17 exceptions-improvement might be completed too 13:09:19 event-log will be most probably postponed to kilo-2, too many patch sets to review 13:09:25 oh ok 13:09:43 exceptions-improvement already implemented 13:10:12 SergeyLukjanov: ok 13:10:23 my script ran a few minutes ago :) 13:10:32 ttx, :) 13:10:37 Your buglist looks a bit wide 13:10:43 like, too many unassigned things 13:10:55 Are they all bugs you intend to fix before k1 ? 13:11:30 ttx, I think nope, need to bug scrub them 13:11:42 there are some very low prio or on-going things 13:11:48 ok 13:11:53 For the meeting today, remember it's a cross-project meeting and we announce it the day before now... so if you have topics to discuss, you should post them beforehand 13:12:01 directly on https://wiki.openstack.org/wiki/Meetings/CrossProjectMeeting 13:12:10 That's all I had. Questions ? 13:12:15 ttx, yup, thanks for the reminder 13:12:43 ttx, I have a small note - we're migrating to the data-processing endpoint type 13:12:49 (from data_processing) 13:12:53 for consistency 13:13:04 #info migrating to the data-processing endpoint type (from data_processing) for consistency 13:13:21 that's all from my side 13:13:35 does that break existing users ? 13:13:55 ttx, nope, client has backward compat handler 13:14:05 ok 13:14:13 SergeyLukjanov: thx! 13:14:15 ttx, tempest and devstack are configurable 13:14:18 ttx, thx! 13:14:23 dhellmann: ready when you are 13:14:33 ttx: hi! 13:14:38 #topic Oslo 13:14:40 o/ 13:14:55 https://launchpad.net/oslo/+milestone/kilo-1 13:15:10 https://launchpad.net/oslo/+milestone/next-kilo 13:15:38 a couple of those for k1 are going to need to move to k2, but we have a review sprint on the 4th so I'd like to wait and see how far we get then before I move them 13:15:51 certainly that one that's blocked can move now 13:15:52 ok 13:16:52 dhellmann: for the oslo.rootwrap release, do I need to do anything ? 13:17:03 I'm fine running the script if you walk me through it 13:17:11 you wrote the script! :-) 13:17:17 ah. Hm. 13:17:19 heh 13:17:27 there is some extra things to do though iirc 13:17:33 I can do it, if you're busy, but I thought I'd check with you before 13:17:43 oh, yeah, the new release notes script 13:17:49 yes, that; 13:18:09 oslo-incubator/tools/release_notes.sh 13:18:26 ok, will try to run that today 13:18:31 http://git.openstack.org/cgit/openstack/oslo-incubator/tree/tools/release_notes.sh 13:18:34 will ping you if I have issues 13:18:44 that generates most of the body of the email you'd send to -dev 13:18:49 sure, let me know if you run into trouble 13:19:04 it's usually a good thing to get more people to run your scripts :) 13:19:05 I'll take it off of my list 13:19:10 definitely 13:19:20 will try to do it today, otherwise first thing tomorrow. Will that work ? 13:19:25 bnemec found some issues with my release process directions (I forgot about having to auth with launchpad) 13:19:54 today or tomorrow is fine. I would wait until next week if you can't do it tomorrow, but that depends on whether you're available for the weekend to solve problems. 13:20:06 ok 13:20:37 That's all I had... question on your side ? 13:20:44 +s 13:20:52 I'm approving some specs, and discovering that the filenames don't match blueprint names 13:21:11 how hard is it to check for that sort of thing in the gate? if I wrote a script, are there credentials for the jenkins user? 13:21:58 hmm, Gerrit has, since it runs a number of bug/blueprint updates 13:22:04 not sure about Jenkins those days 13:22:14 actually, I wonder if I could run a query without authenticating 13:22:15 there was one for sure 13:22:24 you probably could. 13:22:26 I just need to know if a blueprint exists matching the filename, I don't have to change it 13:22:31 ok, I'll experiment with that 13:22:47 anonymous is a lot simpler 13:23:00 do you have any rootwrap reviews you want us to prioritize for the sprint? 13:23:10 no, the roster is pretty empty 13:23:28 the next stage is to get neutron to use the new daemon mode stuff 13:23:38 ok, good. I'm looking forward to seeing how far we can get with clearing out our backlog 13:23:45 ah, is there a bp for that work? 13:24:11 the guy who was working on it moved to something else 13:24:17 figures 13:24:19 someone else proposed to take it over 13:24:30 (in neutron) 13:24:36 let me check if there is a spec for it 13:25:26 Blueprint would be https://blueprints.launchpad.net/neutron/+spec/rootwrap-daemon-mode 13:25:38 Yuriy moved on, Miguel proposed to take it over 13:27:05 * dhellmann nods 13:27:06 (Miguel Angel Ajo Pelayo) 13:27:16 can't find spec 13:27:58 hmm 13:28:02 https://review.openstack.org/#/c/93889/ 13:28:26 actually in better shape than I thought 13:29:02 I think there is potential in future oslo.rootwrap to include some of the client code, as it will be a bit common among consumers 13:29:17 makes sense 13:29:18 but I'd like to let neutron shape it 13:29:50 so that would be the next step for oslo.rootwrap, but today it's blocked 13:30:04 anything else ? 13:30:21 nothing from me this week 13:30:39 shouldn't "tooz adoption" be "Implemented" now ? 13:30:51 was that done? 13:30:56 feels like all things merged 13:31:07 at least the two reviews linked in the bp 13:31:09 the repo needs to be renamed I think 13:31:30 ah! ok 13:32:09 I added a work item and set the status to "slow progress" to nudge jd__ 13:32:31 we might actually be waiting for infra to schedule downtime, and if that's true I'll set it to blocked 13:32:43 or "needs infra" 13:32:53 which is like the best use ever for this status 13:33:04 haha, yeah, updated 13:33:14 ok, have a good day! 13:33:22 you, too! 15:05:49 ttx: Here and at the ready sir. 15:06:32 mestery: o/ 15:06:36 #topic Neutron 15:07:06 https://launchpad.net/neutron/+milestone/kilo-1 15:07:21 so.. only 4 ? 15:07:44 YEs, it looks very low I know 15:07:56 We have been reviewing some huge BPs this cycle, and most are landing for Kilo-2 15:08:03 The refactoring is taking a lot of review time in the specs process 15:08:25 ok, nothing will just get spec-approved and fasttracked in ? 15:08:33 The team is spending the time up front to make sure things go smoothly 15:08:44 There may be a few yet, I'm talking to some folks today/tomorrow 15:08:49 The flavors stuff may 15:08:56 well, I won't mind a peak at k2, that would change from the usual x3 peak 15:09:03 And some of the core refactoring will be done next week, so may land yet in Kilo-1 15:09:07 Right 15:09:08 That's our hope 15:09:27 as long as the page reflects what you think will get done, that's good 15:09:42 anyone working on https://bugs.launchpad.net/bugs/1323658 ? 15:09:53 * mestery looks 15:10:20 Not at the moment no, we've worked on this one off and on for a while now. 15:10:21 was rtated critical adn targeted, although it's hardly new 15:10:25 Right 15:10:35 I know me, salv, and armax have spent time on it off and on during Juno 15:10:40 I can priortize this one again 15:11:00 maybe that can be downgraded to high, and removed from milestone until someone is assigned to it ? 15:11:22 ++ 15:11:46 currently it looks as if it's a milestone-critical issue without an assignee :) 15:12:00 which triggers all kind of weird flags 15:12:00 :) 15:12:01 Done 15:12:17 but if it survived the last 6 months it hardly qualifies at critical in my book 15:12:23 ++ 15:12:36 At various times it's been a nova and/or neutron issue. 15:12:56 is there more to do on drop-rpc-compat ? 15:13:07 I see 5 landed changes 15:13:40 Yes, I spoke to russellb today, he has a few patches left, it should land in Kilo-1 though. 15:13:46 ok 15:13:50 that's all I had 15:14:22 remember to file your topics for the cross-project meeting ahead of this sync now that it is cross-project we need to announce agenda with a bit of advance notice 15:14:28 ++ 15:14:33 Thanks for the reminder ttx 15:14:41 page is https://wiki.openstack.org/wiki/Meetings/CrossProjectMeeting 15:14:45 that's all I had 15:14:54 questions on your side ? 15:15:27 oh. How are the new repos coming up ? 15:15:37 They are coming. 15:15:42 We have some new plugin repos approved 15:15:50 And the services ones will be done next week while at the mid-cycle 15:15:55 We have a spec close to approval there 15:15:58 we didn't discuss impact for release management 15:15:59 So we can do the work next week 15:16:20 what release model would that use ? 15:16:47 I remember not panicking reading the original email, so maybe that was covered there 15:16:48 There are notes in the spec on that, let me grab the link, would be good to get your commenst in gerrit 15:16:57 ++ 15:17:03 https://review.openstack.org/#/c/136835/ 15:17:09 ok, will read and comment there 15:17:34 #action ttx to read and comment on split spec https://review.openstack.org/#/c/136835/ 15:17:38 Thanks ttx! 15:17:45 thanks, have a great day ! 15:18:12 nikhil_k: ready when you are 15:18:19 ttx: o/ 15:18:31 #topic Glance 15:18:40 https://launchpad.net/glance/+milestone/kilo-1 15:18:50 All appear to be in review 15:19:00 store-capabilities is missing a priority 15:19:09 I guess that was a recent addition 15:19:17 yep, 4 hours ago 15:19:31 ttx: yeah, was at vacation past few days and could not get a chance to look into it 15:19:42 there may be 1 more 15:19:55 or 2 (small ones) 15:20:03 will take a look at this today/tomorrow 15:20:09 sounds good 15:20:52 Things look in good shape oevrall. Will PM you about security issue when we are done 15:20:58 questions on your side ? 15:21:03 :) 15:21:17 nothing, still catching up 15:22:06 ok then, I won't keep you more 15:25:37 david-lyle: we can talk now if you want, or you can go at your usual time (in 15min) 15:26:02 ttx: now is fine 15:26:08 #topic Horizon 15:26:22 https://launchpad.net/horizon/+milestone/kilo-1 15:26:40 A few undefined/unknown to clear up there 15:26:50 but otherwise looks good 15:26:54 2 weeks from target 15:27:32 yes, most work is on track 15:27:34 instance-details-add-host-server is missing an assignee too 15:27:57 I may just pick that up, it's a fairly small change 15:28:07 ok 15:28:23 was waiting to see if the author of the bp started work 15:28:53 is separate-horizon-from-dashboard still likely to land for kilo-1 ? 15:29:07 trying to anticipate the release artifact impact 15:29:35 I doubt it. More likely early K-2 15:30:05 I'll confirm in the Horizon meeting and move if my inclination is correct 15:30:13 sounds good 15:30:27 horizon_lib would be published a library on Pypi ? 15:30:31 as a* 15:30:53 yes, there is still some contention around naming 15:31:11 which seems to be the main roadblock 15:31:26 ok, so I guess apart from making the release artifact smaller, that shouldn't affect release management that much 15:31:56 no, just adding another dependency really 15:32:04 That's all I had. Questions on your side ? 15:32:47 are you aware of any issues with the icehouse and juno neutron gate jobs? 15:33:06 I can raise in infra as well 15:33:21 hmm, nothing in particular -- which doesn't mean there isn't one. 15:33:35 * ttx gave up on knowing everything a few years ago 15:34:35 david-lyle: anything else ? 15:34:40 no worries, I'll continue to try and track down the cause 15:34:43 no I'm good 15:34:53 david-lyle: ok, have a great day! 15:34:56 thingee: around? 15:35:05 ttx: thanks, you too 15:35:45 ttx: sorry was having connection problems here 15:35:50 #topic Cinder 15:36:04 thingee: np 15:36:09 https://launchpad.net/cinder/+milestone/kilo-1 15:36:17 now tethered to my phone :) 15:36:26 did you get to the bottom of the "not started" stuff ? 15:37:22 only two weeks to go, so I suspect they should at least have started work 15:37:49 especially the brand-new drivers :) 15:38:36 ... 15:40:59 I have sent emails out, but haven't heard back from people. Going to be punting things this week. 15:40:59 Same goes for drivers from people that haven't responded back to my emails. 15:41:00 should be a smaller list the next time we talk 15:41:01 agreed 15:41:02 I've been making a point to tell people this is your only chance for Kilo, so no surprises. 15:41:04 mercy there is a lot :) 15:41:06 we finally got another one merged last week. there are others that are close. 15:41:06 that's it for me. 15:41:26 ok great 15:41:52 thingee: no more questions from me 15:42:06 thingee: have a godo day 15:42:09 good* 15:42:30 you too 15:42:36 evening that is :) 16:49:27 notmyname: ready when you are 16:49:39 ttx: good morning/evening 16:49:42 #topic Swift 16:49:58 I see you put me on the project meeting schedule 16:50:06 about client dev work 16:50:11 what do you want to cover there? 16:50:11 well, you and morganfainberg 16:50:14 right 16:50:21 summary or ....? 16:50:28 I want to discuss the approach, see if there is a trend there 16:50:32 ok 16:50:37 (I think there is) 16:50:40 great. looking forward to it 16:51:04 It's more of a "should other projects also consider it if they find themselves in the same situation" thing 16:51:42 honestly the one thing that concerns me about "openstack-sdk" is the one-tool thing. trying to make one tool that works for all the openstack projects. 16:51:44 ok 16:52:01 planning christmas holiday -- do you plan a swift release before end of year ? 16:52:01 but I want to address that if/when it's a problem 16:52:10 I was just looking at that 16:52:14 or rather January+ 16:52:54 we could either do something the week of the 15th (2 weeks from now) or we could wait until january. we haven't had anything major land, just a lot of smaller fixes 16:52:59 what works best for you? 16:53:37 Should be around that December week. Your call 16:54:17 Early in Jnaury works too. Maybe we can wait one more week and see how it goes , 16:54:19 ? 16:54:59 Just avoid the weeks of the 22 and the 29 16:55:01 :) 16:55:18 ttx: ok, let's propose 2.2.1 RC between dec 11 and 15 and final by the end of the week. does that work? 16:55:31 That works. I should be around on the 22nd if we need to push it then. 16:55:36 ok, great 16:55:45 I'll put it on the agenda for tomorrow's swift meeting 16:55:59 #info proposed plan to do 2.2.1 RC between dec 11 and 15 and final by the end of the week 16:56:07 notmyname: great, thx 16:56:07 anything else? 16:56:11 nothing from me 16:56:19 ok, thanks. 16:56:21 have a great day! 16:56:23 you too 16:56:30 morganfainberg: ready when you are 16:56:51 ttx: mostly here. 16:56:56 :) 16:56:58 #topic Keystone 16:57:05 morganfainberg: turkey issues ? 16:57:15 https://launchpad.net/keystone/+milestone/kilo-1 16:57:27 Post holiday crud issues. Yay family! ;) 16:57:58 token-provider-cleanup -> not started, still on track for dec 18 ? 16:58:02 Token provider cleanup is being punted to k2 16:58:09 ok 16:58:30 the rest looks reasonable 16:58:33 Hm is being merged / has been merged to master with 1-2 outstanding patches. 16:58:45 That are being rebased today. 16:59:07 I'll sweep through and make sure nothing else is missing. 16:59:11 morganfainberg: remember we'll discuss the technique of openstack-sdking your incompatible client changes at the cross-project meeting today at 21:00 16:59:14 (utc) 16:59:20 ++ 16:59:37 nothing else from me 16:59:39 questions ? 16:59:45 Noting else on this end. 16:59:53 alright then 16:59:56 have a good day! 16:59:59 Next week though I will be delegating this to Dolph 17:00:12 that is a fine thing to do 17:00:23 \o/ 17:00:36 Wanted you to have a heads up 17:00:43 eek, i won't be available next tuesday, probably at all 17:00:43 I'll prepare myself 17:00:51 it's fine to skip 17:00:59 Ok I will find someone else or let you know we have a skip 17:01:14 ack 17:01:21 devananda: around ? 17:01:58 ttx: g'morning! 17:02:18 devananda: fine with syncing a bit early ? 17:02:23 sure 17:02:29 #topic Ironic 17:02:32 https://launchpad.net/ironic/+milestone/kilo-1 17:02:43 so.. elephant in the room 17:03:03 new-ironic-state-machine, how is the spec going ? Who will be working on that ? 17:03:28 right now, everyone is 17:03:38 we have a bit of too-many-cooks-spoiling-the-soup going on, IMO 17:04:04 I spent most of yesterday, and will probably spend several hours today, trying to sort this out with the team 17:04:08 ok 17:04:16 we also have several things slated for k2, k3 which depend on this 17:04:20 everything else looks good 17:05:13 getting progress on that is going to be my main focus for a bit 17:05:14 no more questions from me -- did you have any ? 17:05:28 hmm. nope! 17:05:37 just one comment - the new spec2bp is fantastic 17:06:05 the v2 one ? 17:06:11 ya 17:06:17 feel free to +1 it :) 17:06:21 :) 17:06:33 Also remember to file your topics for the cross-project meeting ahead of this sync now that it is cross-project we need to announce agenda with a bit of advance notice 17:07:04 ah, thanks 17:07:06 that's all I had. 17:07:21 (agenda for crossproject lives at https://wiki.openstack.org/wiki/Meetings/CrossProjectMeeting) 17:07:22 i dont think i have any cross-project agenda items, but appreciate the reminder 17:07:35 I just won't be asking for topics during the sync anymore 17:07:46 so just edit the wiki yourself 17:07:52 :) 17:07:58 devananda: have a great day! 17:08:06 SlickNik: ready when you are. 17:09:45 ttx: o/ 17:09:54 #topic Trove 17:10:10 https://launchpad.net/trove/+milestone/kilo-1 17:10:32 I'm working on cleaning up the BPs/bugs targeted to kilo-1 17:10:51 well, that sounds rather reasonable to me already 17:11:20 2 weeks leftr, so next week it will probably be unreasonable to keep in k1 stuff not proposed for review yet 17:11:35 There are a few bugs that I know won't make it that I'd like to move to k2. 17:11:39 Yes, exactly. 17:11:56 the idea being, to use that page to communicate what you think will happen, to the best of your prediction abilities 17:12:59 SlickNik: your status looks good at this point, I don't really have more questions 17:13:05 Questions on your side ? 17:13:23 ttx: None from my side either. 17:13:35 SlickNik: alright then, quick and easy 17:13:41 have a great day! 17:13:57 ttx: Thanks — see you at the cross project meeting! 17:14:04 see you there! 17:14:05 #endmeeting