14:00:45 #startmeeting neutron_upgrades 14:00:45 Meeting started Thu Jun 21 14:00:45 2018 UTC and is due to finish in 60 minutes. The chair is njohnston. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:47 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:49 The meeting name has been set to 'neutron_upgrades' 14:01:15 Hello all 14:01:32 Hi Nate 14:01:58 #topic Action Items 14:02:09 #info njohnston review https://review.openstack.org/#/c/507772/ 14:02:30 I did not have much time to take a look at https://review.openstack.org/#/c/507772/, but it looks like there has been a quickening pace of reviews and some good feedback. 14:02:46 yes 14:03:03 I think there is a good amount of interest in it. 14:03:35 So I think the prospects for that change are good. 14:03:35 yeah, I'm trying to solve all the concerns from reviewers 14:04:00 Let me know if you need any assistance. 14:04:23 thank you, Nate. Please feel free to add your opinion on that patch if you have any 14:04:34 Will do, thanks. :-) 14:04:41 #info Update meeting agenda https://wiki.openstack.org/wiki/Meetings/Neutron-Upgrades-Subteam 14:04:42 thank you in advance :) 14:04:50 I don't have edit privileges on the wiki. I will check with lujinluo when she gets back to see how she wants to approach this. 14:04:58 #action njohnston to check with lujinluo on upgrades meeting wiki 14:05:14 I think that concludes the action items from last time 14:05:24 and so on to the main show 14:05:26 #topic OVO 14:05:35 #link https://review.openstack.org/#/q/topic:bp/adopt-oslo-versioned-objects-for-db+(status:open+) List of outstanding changes 14:06:01 We just discussed https://review.openstack.org/#/c/507772/ so we can skip it 14:06:08 #link https://review.openstack.org/#/c/565358/ objects: don't refetch a non-list object field if it's None - Ihar Hrachyshka 14:06:23 This still looks solid. It needs some core attention. I will reach out directly to additional reviewers. 14:06:32 that's great 14:06:53 #action njohnston to reach out to core reviewers for https://review.openstack.org/#/c/565358/ 14:07:04 #link https://review.openstack.org/#/c/549168/ Use Router OVO in l3_db.py - Van Hung Pham 14:07:16 This one is seeing major problems with tests. 14:08:38 OK, no update from the author on that 14:08:48 #link https://review.openstack.org/#/c/562489 ipam_backend_mixin: Service Type model to OVO - Vu Cong Tuan 14:08:56 This one has been sitting since April, I think it is ripe for revival but some comments need to be addressed. 14:09:14 I don't know if the author is still attending to it. Do you know, TuanVu? 14:09:16 yeah, I'm trying to apply your suggestion 14:09:30 Ah, never mind, I just realized you are the author :-) 14:09:49 hopefully you've received my email 14:10:08 Yes I did! Let me talk about that in a later section. 14:10:17 it would be great if there's example about mentioned implementation 14:10:23 awesome! 14:10:27 thank you very much! 14:10:35 #link https://review.openstack.org/#/c/561834 ipam_backend_mixin: Segments model to OVO - Vu Cong Tuan 14:11:34 Any thoughts on that one, TuanVu? 14:11:45 this one is the same 14:12:00 I'll work on it after Service Type OVO patch 14:12:07 sounds good 14:12:25 #topic OVO Joins 14:12:40 OK, so I have had discussions with a number of people in the community. 14:12:54 The problem is that a SQL join performs multiple functions 14:13:54 It can join an element in one table with an element in another table based on a common field 14:14:18 Or it can locate N elements that exist only in both of 2 tables (inner join) 14:14:44 ok 14:14:46 Or it can elements in table 1, and then optionally enrich them with data from table 2 if it exists (outer join) 14:15:48 What I noticed is that in the existing OVO code there are places where it looks like complex SQL Alchemy including joins has just been forklifted into the object 14:16:37 yeah 14:16:52 #link https://git.openstack.org/cgit/openstack/neutron/tree/neutron/objects/ports.py#n472 Example query with join and filter in an OVO 14:17:24 So is that the pattern we should be following, so that we retain the assumptions inherent in what a 'join' is? 14:18:03 I will keep investigating, and hope to return a recommendation, including an example implementation change, next week. 14:18:08 It's a complex question :-) 14:18:28 awesome explanation :) 14:18:32 thank you very much 14:18:37 it sounds great! 14:18:48 I appreciate your vote of confidence :-) 14:19:20 #topic Open Discussion 14:19:29 Anything else to talk about? 14:19:58 nothing else from me 14:20:13 OK. Thanks very much TuanVu! 14:20:31 lujinluo will be back next week, so it will be a return to normal order :-) 14:21:03 I hope so 14:21:17 btw, Luo is leaving Fujitsu 14:21:21 Oh, also the position of Neutron liaison to the Oslo team was vacated, and I volunteered to take it on. 14:21:45 Oh? I wish her the best with her new endeavor! 14:21:59 yeah, me too 14:22:06 The important question: do you know if she will be continuing in the OpenStack community? 14:22:27 regarding to your volunteer, it's great! 14:22:35 I'm not sure 14:22:47 we can talk about that next week, I think 14:22:51 We'll have to ask her all the questions next week, indeed. 14:22:56 yeah 14:23:15 OK, I think that is everything for today. More than half an hour back to you! Have a lovely day. 14:23:17 #endmeeting