18:00:28 #startmeeting trove 18:00:28 Meeting started Wed Oct 5 18:00:28 2016 UTC and is due to finish in 60 minutes. The chair is amrith. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:00:29 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 18:00:31 The meeting name has been set to 'trove' 18:00:56 o/ 18:01:00 o/ 18:01:03 anyone here for trove meeting say aye! 18:01:07 hello vgnbkr aliadil_ 18:01:22 hi amrith 18:01:23 o/ 18:01:42 hi spilla 18:01:49 hi amrith 18:01:51 lets give folks a couple of minutes 18:01:57 this may be a short meeting 18:02:43 o/ 18:02:49 hi peter 18:02:59 I don't have much for the meeting today 18:02:59 hi amrith 18:03:07 there were no action items from last time 18:03:11 hi amrith 18:03:13 that's ok by me :) 18:03:19 #topic Newton release schedule 18:03:22 hi johnma 18:03:30 tomorrow the newton release will be cut 18:03:46 there is one translation for dashboard that came in too late 18:03:52 it'll make the next release for newton 18:04:03 don't have anything further to add about that 18:04:37 #topic Open Discussion 18:05:17 an email went out to all PTL's asking to confirm whether our respective teams would participate in the PTG in Atlanta. 18:05:23 I confirmed that Trove would attend. 18:05:35 we now have an idea of the room allocations for Barcelona. 18:05:52 #link https://docs.google.com/spreadsheets/d/1TQ-RSlbiBBEclkonIbfUP7R1ExZSJylF1uiEKV2G_Cw/pubhtml?gid=1107826458&single=true 18:06:04 I was about to ask about barcelona summit. thanks amrith 18:06:05 you'll see the rooms that we have ... (they are marked Trove) 18:07:21 we need to make our schedule for the design session, I'll be working on that. An etherpad is at https://etherpad.openstack.org/p/trove-barcelona-design-summit-sessions 18:07:25 please propose topics there. 18:07:53 Some of us have presentations at Barcelona that we have to prepare for. 18:07:59 I know that johnma and I have one 18:08:08 dougshelley66 has some 18:08:12 not sure who else 18:08:42 That's about all I had for Open Discussion 18:09:02 We have several large change sets that are still in need of reviews 18:09:14 Emily has a presentation 18:09:31 I've been working on a couple; get rid of trove-integration and redstack, and one I've been workign with along with vgnbkr on API versioning. 18:09:42 mvandijk_ has a couple 18:09:50 vgnbkr has some specs that are in need of review 18:10:11 I am testing Matt's changes and Petr's right now. hopefully will be done before end of day today 18:10:11 thx dougshelley66 yes. forgot that one. 18:10:28 Petr's related to postgresql 18:10:37 johnma, thanks for the comments and change on trove-image-builder 18:10:51 I'm trying to get the next one behind that (dsvm tests) and having some challenges. 18:12:19 that's all I've got. 18:12:40 I remember discussion about this at the last summit but... what about supporting multiple versions of the same datastore? Running both mysql 5.5 and 5.6. 18:13:05 I think we concluded storing different versions of config for the different datastore would be a challenging task. 18:13:55 trevormc, I don't know that anyone has signed up to do that (for ocata) 18:14:00 I may be wrong 18:14:04 but I don't think so 18:14:19 dougshelley66, is that on your list? 18:14:36 amrith not presently 18:14:40 thx 18:15:11 #action [amrith] publish the ocata plan/list of things 18:15:21 I have a list, I have to publish it ... 18:16:01 trevormc, you'd asked earlier about projects to work on. here's one that has been around for a while and is in need of an owner. 18:16:04 Get rid of schema downgrade code https://bugs.launchpad.net/trove/+bug/1434103 18:16:06 Launchpad bug 1434103 in OpenStack DBaaS (Trove) "SQL schema downgrades are no longer supported" [Medium,Triaged] - Assigned to Nikhil Manchanda (slicknik) 18:16:29 There has been discussion about this off and on, but we never did conclude one way or the other. 18:16:32 that I can recall. 18:16:50 Does anyone have strong objections to this project? 18:18:40 amrith: Ok I will work on getting rid of the schema downgrade code, seems like there are implementations I can use as a reference. 18:19:10 yes 18:19:21 peterstac, johnma, ... others ... OK with this? 18:19:54 amrith: I am sorry but I got disconnected in between. So I missed the earlier messages 18:20:19 >> trevormc, you'd asked earlier about projects to work on. here's one that has been around for a while and is in need of an owner. 18:20:24 >> Get rid of schema downgrade code https://bugs.launchpad.net/trove/+bug/1434103 18:20:26 Launchpad bug 1434103 in OpenStack DBaaS (Trove) "SQL schema downgrades are no longer supported" [Medium,Triaged] - Assigned to Trevor McCasland (twm2016) 18:20:34 >> There has been discussion about this off and on, but we never did conclude one way or the other. 18:20:39 >> that I can recall. 18:20:43 >> Does anyone have strong objections to this project? 18:21:11 * amrith waits for johnma 18:21:55 I am fine with trevormc looking at this. 18:21:59 I'm ok with that 18:22:28 Maybe it can be done in two steps - right now we have checks that insist there's a downgrade path 18:22:45 so even though we don't care any more, we still have to add it to new changes 18:23:02 maybe we can get rid of that first, and then rip out the rest? 18:23:44 sounds good, thx peterstac, johnma. 18:23:59 #action [trevormc] to look at Get rid of schema downgrade code https://bugs.launchpad.net/trove/+bug/1434103 18:24:00 Launchpad bug 1434103 in OpenStack DBaaS (Trove) "SQL schema downgrades are no longer supported" [Medium,Triaged] - Assigned to Trevor McCasland (twm2016) 18:24:16 There is one other review that may be worth talking about 18:24:18 #link https://review.openstack.org/#/c/379317/ 18:24:30 This review tries to deal with hacking rule H301 18:24:34 history: 18:24:53 this was discussed a long time ago 18:25:03 2014-10-22 to be precise 18:25:12 and the feeling then was overwhelmingly negative to the change 18:25:29 18:46:47 Yes (3): AJaeger_, SushilKM_, SlickNik 18:46:48 Indifferent (1): iccha1 18:46:49 No (9): schang, tomblank, robertmyers, amrith, vgnbkr, amcrn, cp16net, grapex_, dougshelley66 18:25:37 The cast of characters is now very different 18:25:48 so I'd like to at least see what the sense of the team is 18:26:08 The change would make many changes (as you can see from the review) 18:26:30 and generally be a nusiance to merge as it juggles import lines 18:26:30 My only point would be if we decide to do it, it has to go in now 18:26:42 otherwise we'll spend too much time rebasing 18:26:48 i agree 18:27:29 i've seen the following here today, johnma peterstac vgnbkr spilla aliadil_ dougshelley66 trevormc 18:27:33 what do y'all think? 18:27:52 my vote is -1 18:28:21 Unless someone can explain to me how this would make the product more correct or easier to understand, let's concentrate on useful things. 18:28:35 vgnbkr, that sounds like +1? :) 18:29:03 so +1 is yes and -1 is no? 18:29:17 oh, ok. 18:29:22 let's make this a regular vote 18:29:27 But what do yes and no mean? The question was "what do you think"? 18:29:47 yes to merge no is not to merge 18:30:22 Then how would my comment above be taken as a yes/+1? 18:30:47 I like hacking rules so I would vote yes, but the importance is low so I move my vote to Indifferent. That's how I feel about it. 18:31:00 #startvote Should we go ahead with this project of H301. Yes, No, Maybe 18:31:00 Unable to parse vote topic and options. 18:31:16 I'm indifferent too (but I'm almost finished reviewing it nontheless) 18:31:23 #vote Maybe 18:31:37 #startvote Should we go ahead with this project of H301 Yes, No, Maybe 18:31:38 Unable to parse vote topic and options. 18:31:44 #vote maybe 18:31:54 well, I can't seem to get the vote to work 18:32:01 Should we go ahead with this project? 18:32:03 Yes, 18:32:04 No, 18:32:06 Maybe? 18:32:19 No 18:32:37 Maybe 18:32:40 amrith: no 18:32:43 Maybe 18:32:48 No (I don't see any value) 18:34:43 Ok, sounds like no one is saying Yes 18:35:12 so I am inclined to say no 18:36:37 #decided I will update the review and say we are not doing this. 18:37:15 #agreed [amrith] update https://review.openstack.org/#/c/379317 with the decision to not take this change 18:37:57 does anyone else have anything they'd like to discuss 18:38:51 I just wanted to bring attention to this review: https://review.openstack.org/#/c/340022/ 18:38:58 hearing none, ... time to adjourn? 18:39:31 this is someone from my org and he has asked for help getting this patch merged, I left a review and told him to add unit tests. 18:40:16 it seems like it is marked with WF-1 now ... 18:40:48 my concern with this change from the beginning was that the bug started to address one issue, then pivoted around and ended up somewhere totally different. 18:40:50 It's a lot of patchsets for a one-line commit message too 18:41:04 Yeah he needs to add the unit tests.. he also said he will update his commit message. 18:41:06 and I have no idea what it is really intending to do 18:41:13 that was one of my comments to him (or maybe more). 18:41:34 That's what i thought, if you have questions I can send them to him. Contacting him is tricky since he works in international times. 18:41:41 see my comment August 26 at 1:15pm 18:42:01 Hi 18:42:09 There he is! 18:42:10 hi ShaikApsar 18:42:35 and as peterstac says, a single line commit message leaves a lot to the reviewer to try and figure out 18:43:00 i'm trying to to fix the Client' object has no attribute 'tenants' 18:43:18 i will update the commit with more details 18:44:06 what would be great is to know how this impacts you, and what you have to do (or not do) to have this problem. 18:44:08 amrith: you suggested few changes for the patch with respect context.auth_token 18:44:58 Amrith did you see my comment on the bug in launchpad? I had to enable the ceilometer plugin to get the error to appear. 18:46:04 trevormc, no. I tuned out of this review a while ago with newton getting out of the door and it being clear that this wasn't in newton 18:48:15 in any event ShaikApsar trevormc this review is now sitting with a WF-1. How about you respin it and then we see what it is about? 18:48:19 does that make sense? 18:48:48 yes 18:48:53 ok, thx 18:48:57 anything else ... 18:48:58 Yes amrith, just trying to get it on the radar again. I will be looking forward to the next patch. 18:49:17 as soon as it has no WF -1's it will be on the radar ... 18:49:56 motion to adjourn? ... 18:50:01 ... anyone ... 18:50:31 seconded :) 18:50:36 thanks peterstac 18:50:39 #endmeeting