14:00:14 #startmeeting neutron_upgrades 14:00:16 Meeting started Thu Jun 7 14:00:14 2018 UTC and is due to finish in 60 minutes. The chair is lujinluo. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:17 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:20 The meeting name has been set to 'neutron_upgrades' 14:00:29 o/ 14:00:57 ok, i will wait for a while for people to join me. 14:01:06 o/ 14:01:19 Hi Luo-san 14:01:24 Hi njohnston 14:01:24 hi njohnston ! so happy that i am not alone! 14:01:26 hi TuanVu 14:01:33 o/ 14:01:40 hello mlavalle :) 14:01:42 :-) 14:01:49 Hi mlavalle 14:01:53 ok, i think we have gather enough peopl 14:02:02 we do not have any AIs from last wee 14:02:06 *week 14:02:07 Hi lujinluo, TuanVu, njohnston 14:02:14 so let's jump to OVO 14:02:18 #topic OVO 14:02:47 https://review.openstack.org/#/q/topic:bp/adopt-oslo-versioned-objects-for-db+(status:open+) 14:03:09 https://review.openstack.org/#/c/549168/ the first one is about Router OVO 14:03:30 but it just got updated around 30 mins ago. Zuul has not said anything yet 14:04:16 hungpv: do you have any specific updates? or shall we wait for the result of Zuul first? 14:04:31 yes, I took some comments from you 14:04:49 the only one I can think of right now 14:05:29 https://review.openstack.org/#/c/549168/10/neutron/db/l3_db.py 14:05:46 L444-445 14:06:06 with context.session.begin(subtransactions=True): 14:06:09 context.session.refresh(router) 14:06:20 * mlavalle would like to say a couple of things in the Open Agenda section of the meeting 14:06:35 I wanted to replace it with something like router.refresh() 14:06:45 is it correct though? 14:06:58 is 'router' now an OVO object? 14:07:08 yes, it is 14:07:23 then you should use router.update() to update changed fields 14:07:32 ok, i see 14:07:52 so can you comeback tomorrow anfd give me your comments on it? 14:08:16 yes, and i also saw some other places need to be addressed. will review tmr 14:08:39 thank you 14:08:47 so that's all from me 14:08:59 ok, next one is https://review.openstack.org/#/c/565358/ 14:09:13 some of us have rebased it a couple of times 14:09:30 yeah, because my network patch is based on it 14:09:52 but every time it fails fullstack test 14:10:08 i will debug it tmr. it seems related to the changes made by the patch 14:10:26 that's great! 14:10:31 thank you in advance, Luo 14:11:18 next is https://review.openstack.org/#/c/507772/ 14:11:43 latest update is in my newest comment 14:11:57 it looks pretty green now, thanks to your help, Luo-san :) 14:12:04 i saw you have already updated the patch! 14:12:19 yeah, as your suggestion 14:12:37 however, there are still 2 failed Tempest Tests 14:12:43 and fullstack test 14:12:52 looks like there's problem with network mtu 14:13:08 it seems the remaining issues are the ones mentioned by slawek last week 14:13:17 anyway good to know you made progress! 14:13:37 thanks :) 14:14:15 ok, i will check the mtu issue tmr as well. hopefully we can find something useful 14:14:27 that's awesome! 14:14:53 your suggestion have been helping me a lot so far 14:15:02 good to know :) 14:15:17 we do not have any other updates from the remaining patches 14:15:28 #topic open discussion 14:15:48 mlavalle: you mentioned you have something to share? 14:15:56 yeah 14:16:05 please 14:16:14 I have two points: 14:16:32 1) This bug was filed a couple of days ago https://bugs.launchpad.net/neutron/+bug/1775220 14:16:33 Launchpad bug 1775220 in neutron "Unit test neutron.tests.unit.objects.test_ports.PortBindingLevelDbObjectTestCase. test_get_objects_queries_constant fails often" [High,Confirmed] - Assigned to Miguel Lavalle (minsel) 14:17:04 We are finding that this test fails sometimes 14:17:12 re-checking takes care of it 14:17:45 I assigned it to myself to not loose track of it 14:17:59 Would any of you help fixing it? 14:18:30 i think this is the test case that bothered you for a long time TuanVu 14:18:59 could you take a look at it, if possible? i think you might be familiar with it. i will also help for sure 14:19:00 hmm ... let me see 14:20:05 honestly, I didn't know how to fix it. It was a great thank to the patch from Ihar 14:20:36 ok, i will check it then. mlavalle 14:20:43 thanks! 14:21:05 second thing is in regards to https://review.openstack.org/#/c/414251/ 14:21:30 Yesterday I sent this message to the ML: http://lists.openstack.org/pipermail/openstack-dev/2018-June/131252.html 14:21:55 I don't want 414251 to break other projects 14:22:07 so I sent the mail and talking to many of them directly 14:22:38 What I wanted to say here is that you should expect 414251 to merge towards the end of next week 14:22:50 I know one of your patches depends on it 14:22:59 understood. yes, the portbinding one 14:23:21 it would be better if you rebased that patch on top of https://review.openstack.org/#/c/571041 14:23:55 This one pluralizes the names of port_binding and the binding attribute in the Port OVO 14:24:10 which lujinluo reocmmended me to do in one of her reviews ;-) 14:24:30 haha, got it. 14:24:36 will do it in next week 14:24:41 cool 14:24:51 that's all I had for today ;-) 14:25:01 good. 14:25:02 I have one minor question. I was looking at some of the changes in my area that need to be made, and some of them are implementing join functionality, for example http://git.openstack.org/cgit/openstack/neutron/tree/neutron/plugins/ml2/drivers/l2pop/db.py#n77 - I was wondering if there were examples of how others have handled this sort of thing. 14:25:46 njohnston: unfortunately we have not figured out a general way to handle joins 14:26:07 that's why they have been pushed away for so long 14:26:29 njohnston: any suggestions? 14:27:25 yeah, any suggestions would be welcomed 14:28:10 we discussed it once, and it may end up to be case-by-case by overriding get_object in each OVO objects. but we have tried any out yet 14:28:21 I have only flights of fancy as of yet, I will see if I can dig in to it sometime soon and get a real sense of how the data is being massaged. 14:28:40 cool 14:28:53 cool, thanks. Very often that's how one gets to be an expert on something 14:29:01 That is my hope :-) 14:29:04 asking a questions and having to dig deeper 14:29:28 i am memo-ing this ^ 14:30:03 The first expert on something most likely started that way 14:30:41 i have one announcement. i am taking PTO from June 13th to June 25th. So i will not be able to chair the next two weekly meetings 14:30:56 shall we cancel them or maybe someone else would like to chair? 14:31:02 I could help out 14:31:10 thank you! njohnston 14:31:10 I have experience chairing meetings 14:31:12 great njohnston! 14:31:25 we love you! 14:31:42 have fun lujinluo 14:31:53 Am I remembering correctly I need to be on the list of chairs in order to be able to use the startmeeting command? 14:32:06 not exactly i think 14:32:33 i used to help Ihar chair meetings while i was not listed as chairs at that moment 14:33:33 ok good :-) 14:33:34 mlavalle: correct? (asking for double check 14:33:59 I think that's the case 14:34:10 if you start the meeting, you are the chair 14:34:57 so basically anyone can start the meeting 14:35:02 yes 14:35:07 cool! 14:35:18 then thank you for the next two weeks! njohnston 14:35:26 Happy to help 14:35:34 Enjoy your vacation! 14:35:41 thank you! 14:35:54 does anyone have anything else? 14:36:13 none from me 14:36:57 ok then. let's call it a day 14:37:01 nope 14:37:07 #endmeeting