14:00:23 #startmeeting neutron_upgrades 14:00:29 Meeting started Thu Jul 6 14:00:23 2017 UTC and is due to finish in 60 minutes. The chair is ihrachys. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:31 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:34 The meeting name has been set to 'neutron_upgrades' 14:01:16 o/ lujinluo 14:01:27 o/ ihrachys 14:01:57 waiting for Manjeet 14:02:08 sure 14:02:12 he was going to join :) 14:03:40 hmmm 14:03:58 ok le'ts wait till :05:00 and then run it anyway. 14:04:05 ok 14:05:29 no luck it seems... ok, let's do one real quick 14:05:36 #topic Actions from prev meeting 14:05:50 manjeets_, o/ 14:05:54 Hi 14:05:55 we just started 14:05:56 manjeets_, o/ 14:06:04 we are going thru action items 14:06:07 first is manjeetsb to clarify if Shashank is going to complete port binding level OVO patch 14:06:15 that's re https://review.openstack.org/#/c/382037 14:06:38 last time we talked he said he'll able to spend some time 14:06:45 on it 14:06:53 it's not in shape for a month, we should probably take it over 14:07:23 ok 14:07:38 last he did update on june5th 14:07:57 I think I reviewed it in the past. I will take over, it shouldn't be far from completion. 14:08:09 #action ihrachys to take over port binding level OVO 14:08:18 next was manjeetsb to have a look at LIKE support patch and respin 14:08:44 I did that, found a issue with current patch 14:08:44 that's re https://review.openstack.org/#/c/419152/ 14:10:04 ok. I see some tiny comments from mlavalle there 14:10:31 I assume you will respin 14:10:33 yes I'll address those 14:10:42 next was ihrachys to respin endpoints OVO patch: https://review.openstack.org/#/c/367810 14:10:46 I did, and the patch is merged 14:10:54 next was manjeets to respin network dhcp agent binding patch: https://review.openstack.org/#/c/370452 14:11:28 there is a comment from Kevin about adding lazy load 14:11:33 sounds legit 14:11:46 i'll look into it 14:12:24 ok those were all AIs we had 14:12:29 #topic OVO patches 14:12:40 https://review.openstack.org/#/q/status:open+project:openstack/neutron+branch:master+topic:bp/adopt-oslo-versioned-objects-for-db 14:13:31 first is port binding OVO: https://review.openstack.org/#/c/407868/55 14:13:49 eh, the latest is this: https://review.openstack.org/#/c/407868/ 14:14:33 i fixed some dvr related failures, but still have some unfixed. will continue this week 14:14:51 there is also some question from Rodolfo ther 14:14:56 but I am not sure I get it 14:15:11 yeah, i forgot to address some of her/his comments 14:15:24 i will reply after i fix the rest of the dvr failures first 14:15:30 ok 14:16:03 next is router OVO: https://review.openstack.org/#/c/307964/ 14:16:06 Kevin asked to split 14:16:23 yes, im splitting them into 3 14:16:28 ++ 14:16:36 router, routerport and floatingip respectively 14:17:57 should be able to push them before next weekly meeting 14:18:01 there is also related patch for relationship loading at https://review.openstack.org/#/c/466237/ 14:18:18 I admit I don't fully grasp why we need all those refreshes :) 14:19:30 is it so that router reflects the latest state when pushed into notifications? 14:20:22 yes. otherwise router.router_port is not updated after modifications 14:20:46 *router.attached_ports 14:21:33 ok 14:21:40 there is also a question from Kevin at https://review.openstack.org/#/c/466237/8/neutron/plugins/ml2/plugin.py 14:22:29 would it make more sence to refresh port in a place where a new ip is added and not in binding code? 14:24:07 i will look into that 14:25:24 ok next in line is https://review.openstack.org/#/c/396718/ (ipallocation integration) 14:25:30 and it has +2 from Kevin already 14:25:35 time for me to chime in I guess 14:25:44 #action ihrachys to review ipallocation patch: https://review.openstack.org/#/c/396718/ 14:26:42 next two are just qos todos tackled: https://review.openstack.org/#/c/468837/ and https://review.openstack.org/#/c/468406/ 14:26:44 both with +2s 14:26:52 I will review them right after the meeting 14:27:06 #action ihrachys to review qos binding OVO objects 14:27:56 next is subnet: https://review.openstack.org/#/c/321001/ 14:28:02 and I see James started working on it, nice 14:28:16 there are some issues it seems, but great we started making progress there 14:29:06 next is dvr mac address: https://review.openstack.org/#/c/304873/ 14:29:22 we were trying to make it pass several times, there is some json encoding issue lingering 14:29:29 I need to get back to it this week 14:29:43 #action ihrachys to get back to dvr mac address OVO and fix the json failure 14:30:19 next is manjeets_'s CLI for data migration: https://review.openstack.org/#/c/432494/ 14:30:30 I admit I haven't had a change to look at latest 14:30:42 #action ihrachys to review CLI patch for data migration 14:31:06 since we are on data migration patch, i want to bring this up again https://review.openstack.org/#/c/288271/ 14:31:27 it is related to data migration patch as we discussed last time 14:32:00 oh right. It fell thru cracks. 14:33:12 lujinluo, do you have in mind how it would work with data migration? 14:34:52 honestly no, because I have not reviewed data migration patch closely. but in my understand data migration patch helps migrate data in the backend and this is what the patch requires 14:35:00 I mean, assuming you run old code in cluster on some nodes, this old code won't fill in the indexes for us? 14:35:59 oh it's autoincrement 14:36:12 so for new records created by old code, those will still be filled in 14:36:29 it's just for existing records that you need to fill it in 14:37:33 yes 14:37:38 ofc there is no guarantee that no old node will create a binding while you number existing records 14:38:06 but it should get a number then; though the picked number may be in conflict with what's in your migration code 14:38:18 in which case, I believe, you will receive an error? 14:38:26 yes, an exception 14:40:16 ok I need to think about out of this venue. but I guess we should be able to deal with it, maybe even moving the numbering to expand phase. 14:40:48 that would be better if we do not need to depend on data migratin patch 14:40:52 autoincrement may give us the needed backwards compatibility for schema 14:41:35 #action ihrachys to have a close look at how to implement binding_index for dhcp agent bindings without contract: https://review.openstack.org/#/c/288271 14:41:53 thanks 14:41:56 I am sorry I can't give immediate reply 14:42:07 not a problem ;) 14:42:41 ok. I look at other patches in the queue, and they are all in merge conflict. perhaps we have enough work to do already and we can revisit those next week. 14:43:23 and it seems most of them are router/fip related anyway, and they will depend on the split lujinluo is going to do for the patch introducing the objects 14:43:51 ack, will work harder next week, XD 14:43:59 :) 14:44:02 thanks! 14:44:42 #topic Open discussion 14:44:58 anything to discuss? 14:45:04 none from me 14:45:08 the new time is ok for you folks? 14:45:19 yes! thanks for doing this!! 14:45:25 ok cool. 14:45:26 how about manjeets_ ? 14:45:28 it is okay I will get habit of getting 1 hour early 14:45:36 thanks manjeets_ for sacrifice ;) 14:45:41 manjeets_, thank you! 14:45:55 ihrachys, I wanted to do that but now I have some reason to do it so its good for me 14:46:10 ok, if nothing else, let's close the meeting and make sure we land stuff ;) 14:46:17 thanks !! 14:46:18 #endmeeting