Thursday, 2018-04-19

*** hoangcx has quit IRC00:14
*** felipemonteiro_ has joined #openstack-meeting-500:40
*** felipemonteiro_ has quit IRC00:46
*** yamahata has quit IRC01:19
*** slaweq has joined #openstack-meeting-501:20
*** slaweq has quit IRC01:25
*** markvoelker_ has joined #openstack-meeting-501:52
*** markvoelker has quit IRC01:53
*** slaweq has joined #openstack-meeting-503:21
*** slaweq has quit IRC03:26
*** yamahata has joined #openstack-meeting-504:11
*** slaweq has joined #openstack-meeting-505:22
*** slaweq has quit IRC05:27
*** ricolin has joined #openstack-meeting-506:24
*** slaweq has joined #openstack-meeting-506:36
*** slaweq_ has joined #openstack-meeting-506:39
*** slaweq has quit IRC06:41
*** dims has quit IRC06:54
*** dims has joined #openstack-meeting-506:56
*** dims has quit IRC07:01
*** dims has joined #openstack-meeting-507:02
*** yamahata has quit IRC07:49
*** radeks has joined #openstack-meeting-508:25
*** derekh has joined #openstack-meeting-508:40
*** ricolin has quit IRC09:25
*** tuanla____ has joined #openstack-meeting-509:34
*** ricolin has joined #openstack-meeting-509:56
*** ricolin has quit IRC09:59
*** ricolin has joined #openstack-meeting-510:17
*** ricolin has quit IRC10:34
*** ricolin has joined #openstack-meeting-510:48
*** ricolin has quit IRC11:17
*** mugsie has quit IRC11:42
*** mugsie has joined #openstack-meeting-511:42
*** mugsie has quit IRC11:42
*** mugsie has joined #openstack-meeting-511:42
*** tuanla____ has quit IRC12:02
*** yamamoto_ has quit IRC12:21
*** yamamoto has joined #openstack-meeting-512:27
*** ricolin has joined #openstack-meeting-512:38
*** mjturek has joined #openstack-meeting-512:48
*** ricolin has quit IRC12:59
*** markvoelker_ has quit IRC13:16
*** markvoelker has joined #openstack-meeting-513:18
*** hoangcx has joined #openstack-meeting-513:36
*** hoangcx_ has joined #openstack-meeting-513:37
*** hoangcx has quit IRC13:41
*** hongbin_ has joined #openstack-meeting-513:46
*** mlavalle has joined #openstack-meeting-513:53
*** lujinluo has joined #openstack-meeting-513:55
*** TuanVu has joined #openstack-meeting-513:58
*** annp_ has joined #openstack-meeting-513:58
lujinluo#startmeeting neutron_upgrades14:00
openstackMeeting started Thu Apr 19 14:00:31 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
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** openstack changes topic to " (Meeting topic: neutron_upgrades)"14:00
openstackThe meeting name has been set to 'neutron_upgrades'14:00
mlavalleo/14:00
lujinluoo/14:00
*** ihar has joined #openstack-meeting-514:01
iharo/14:01
lujinluoFirst thing first. mlavalle has some concerns about this patch, https://review.openstack.org/#/c/556667/14:01
lujinluonot sure if ihar gets time to check the comments already14:01
TuanVuHi mlavalle14:02
TuanVuHi Ihar14:02
mlavalleadmitedly my concern my be unwarranted14:02
TuanVuHi Luo-san14:02
mlavallehey TuanVu14:02
lujinluohey TuanVu !14:02
iharmlavalle: I saw point on more comments needed. agreed.14:02
lujinluobut i agree that, we may need more comments to help future readers14:03
iharI won't be able to get to this patch till Monday though so that's a bummer.14:03
lujinluook, i will try to put some comments but i need your review/double check just in case i misunderstand anything14:04
iharI see there is another comment there not just about comments though14:04
*** hungpv_ has joined #openstack-meeting-514:05
iharmlavalle: I didn't have a chance to think about it. how critical is the weak ref comment? is there a chance for getting this in with the caveat I will follow up on Monday?14:05
mlavalleihar: yeah, as long as we answer to ourselves the question soon and feel comfortable that we are not get in trouble, I am fine14:06
mlavalleso maybe let's revise the patch with comments, get it in14:07
iharok. I will put it in my list to follow up.14:07
mlavalleand then work next week on the weakreference concern14:07
mlavalledoes that work?14:07
iharif lujinluo is able to handle the comments part, sure14:07
mlavalledo you want to do that lujinluo?14:08
lujinluoi can help with the comments but maybe not weakreference14:08
mlavalleI will help. it is a good exercise for you and me lujinluo. We better get very familiar with this piece of coe :-)14:08
iharyeah not weak ref. I will need to take a look into it but seems from the comment it's a legit thing.14:08
iharyes you better are, it's as you said esoteric14:09
lujinluomlavalle: exactly ;)14:09
mlavallecool!14:09
*** yamahata has joined #openstack-meeting-514:10
lujinluo#actionitem mlavalle and lujinluo help with the comments in auto expire fk patch14:10
iharlujinluo: it's #action btw14:10
lujinluothanks, i was wondering why the magic did not happen14:10
mlavalleLOL14:10
lujinluo#action mlavalle and lujinluo help with the comments in auto expire fk patch14:10
lujinluook, anyway.. next one is the auto detect old and new engine facade https://review.openstack.org/#/c/553617/1714:11
lujinluoi understand that we need the former patch before get this one in, but it is worth to mention the status14:12
iharyeah, it's good to go, just need to nudge the base one14:12
*** skazi has quit IRC14:13
lujinluo\o/14:13
lujinluo#topic OVO14:13
*** openstack changes topic to "OVO (Meeting topic: neutron_upgrades)"14:13
lujinluohttps://review.openstack.org/#/q/status:open+project:openstack/neutron+branch:master+topic:bp/adopt-oslo-versioned-objects-for-db14:13
lujinluofirst one is new https://review.openstack.org/#/c/562489/14:14
*** hoangcx_ is now known as hoangcx14:14
iharCI so green, I can't stop being amazed14:14
lujinluoi think TuanVu is trying to tackle joins here14:14
TuanVuyes14:14
TuanVuif there's any concern, please feel free to let me know14:15
lujinluowow, yeah, all green. so good for our eyes14:15
lujinluoihar: i actually have a concern of the way we deal with joins14:15
iharok this patch moved the code but it didn't solve the issue that we pass sqlalchemy queries around14:15
lujinluopreviously we just moved all the methods to object14:15
iharwhich should not be the way we interact with ovo objects14:15
lujinluoyes, i think eventually we need a way to deal with joins14:16
lujinluoi mean, we can rewrite all the joins with get_object and filter in python, but do you prefer if we can have something like join_object()? ihar14:17
iharin this particular case, why not adding a new extra filter called 'service_type' and handle it accordingly in ovo?14:17
lujinluono, i mean. if we do not limit to this particular case14:18
lujinluobecause most of the remaining work is about joins14:18
iharlujinluo: we already have get_object[s] as a common interface. it would be nice if we can stick to it, just expand it for the Subnet class to support a new extra filter for service_type. Then you could just Subnet.get_objects(context, network_id=nid, service_type=service_type) and not care about implementation complexity14:18
iharin general, I would recommend expanding standard interfaces like get_object[s] to support additional filters (of course it requires some if/else branching in their implementations depending on which filters are passed).14:20
iharwe may add custom getters like get_subnets_by_service_type(...) if it seems hard to achieve right now14:20
iharbut we should never have any part of sqlalchemy interfaces / types be exposed (so no queries passed around as arguments, or models returned from ovo methods)14:21
mlavalleis the corllary that at this point you see the OVO interface as stable and the rest of the work should happen underneath?14:21
iharmlavalle: more or less, I think what we have is a good interface that we should try not to expand with custom methods without clear reason.14:21
lujinluook, so you would prefer that we manipulate with get_object(s)14:22
mlavalleihar: that's good insight. thanks14:22
iharthing is, if some other plugin wants to use ovo objects and needs to filter by service_type, what should they do?14:22
iharsupposedly we are moving base interface into neutron-lib and, as per late boden's patch, provide a registry to get objects from14:22
mlavalleyeap14:23
iharbut all the external plugins know about objects received from the registry is that they all have standard methods like get_object[s] or update. there is no way for them to learn that there is get_subnets_by_service_type too.14:23
iharif we implement it the right away with standard interfaces, plugins will be able to transparently request the needed filters without caring about db table structures.14:24
mlavalleexactly14:24
lujinluoyeah, so we have to add extra filters to get_object() not extra methods14:24
iharlujinluo: yes I would prefer get_object[s], and I strongly disagree with passing queries as arguments14:24
lujinluoagree14:24
iharlujinluo: yes, that would be ideal. unless of course we have a good reason for a custom method. (like it's too hard to do it; then we may get back to it later)14:25
iharI left a comment along these lines14:27
lujinluoi see. i was testing a local patch with 3 tables joins14:27
TuanVuthanks for the comment, Ihar14:28
lujinluoso with that being said, i should revise corresponding get_object(s)14:28
iharnow, I don't disagree that making joins work through standard interfaces is quite an undertaking.14:28
*** skazi has joined #openstack-meeting-514:28
iharbut we should try it. maybe once we actually try it, we learn something that would defeat all I just said.14:28
iharbut unless we try on a patch or two, we don't know14:28
lujinluogot it14:29
iharTuanVu: does it make sense?14:29
TuanVuyes, I agree14:29
mlavallein other words, let's force ourselvers to find a good reason to change the current API14:29
lujinluo++14:30
lujinluook, next one  https://review.openstack.org/#/c/507772/14:31
iharI see rebase helped with InvalidRequestError, that's good.14:31
iharstill a failure with query count though.14:32
TuanVuas I mentioned on Gerrit, there's still problem with "duplicated queries" for "networksecuritybindings" and "externalnetworks"14:32
TuanVuyes14:32
iharI don't have a good answer except that I can look into it on Monday14:33
TuanVuthank you in advance, Ihar :)14:33
lujinluoi think i have the same issue with port. so i need to double check tmr or later too14:34
lujinluonext is segment https://review.openstack.org/#/c/559414/14:34
lujinluohongbin has addressed all the comments from ihar14:34
hongbin_o/14:35
lujinluowow, hi hongbin_ i did not expect you would be here14:35
mlavallehe is everywhere14:35
hongbin_^^14:36
lujinluoLOL14:36
mlavalleomnipresent14:36
iharack, +214:36
iharman, this green ci is amazing14:36
lujinluobut i think we need to wait for the fk patch before +w, right?14:36
iharwe can +w whenever we like as long as it's depends-on (which it is)14:37
iharzuul will not merge it until all dependencies are met14:37
lujinluounderstood!14:37
lujinluonext one https://review.openstack.org/#/c/561834/14:37
lujinluoi think it needs some more work wrt joins14:38
TuanVuyes14:38
iharyes it's the same issues as discussed above14:38
TuanVuas above discussion14:38
lujinluook, the next two patches are mine.. and i apologize for not being able to work on them last week14:39
lujinluoi will respin them before our next meeting14:39
iharok. afair we wanted to base port stuff on mlavalle's multiple port bindings rfe implementation14:40
mlavalleyeap14:40
lujinluoyes, but it seems mlavalle 's patch is in merge conflict14:41
iharso it requires quite some work I suspect14:41
mlavallelujinluo: I'll fix it14:41
lujinluothanks, i will rebase once it is ready14:41
mlavalle:-)14:41
lujinluook, that's all for ovo14:41
iharmlavalle: please do! that rfe is one of things I promised to get to done before I move to other places. :)14:41
lujinluo#topic open discussion14:41
*** openstack changes topic to "open discussion (Meeting topic: neutron_upgrades)"14:41
mlavalleihar: thanks. I think we can merge it soon14:42
lujinluoihar: ohh, you just reminded us of some heart-breaking stuff14:42
lujinluotha you are moving to other places ;(14:42
lujinluothat*14:42
iharto the topic of open discussion, I have nothing specific to discuss14:42
mlavalleI just one to mention one thing14:43
lujinluoyes, please14:43
mlavalleThis past Monday I added a topic to the Neutron weekly meeting on OVO backlog14:43
mlavalle#link https://wiki.openstack.org/wiki/Network/Meetings#Blueprints14:43
lujinluothank you!14:44
mlavalleI mentioned it during the meeting and I will continue doing so every week14:44
TuanVuthank you very much, mlavalle14:44
mlavalleso people can see the backlog and help if they have bandwidth14:44
lujinluois it why we are having hongbin_ here ? lol14:44
hungpv_😂14:44
mlavalleno, as I said, hongbin_ is omnipresent14:44
mlavalle\it doesn't have to do with any of my efforts14:45
lujinluoLOL, i see. but this is really appreciated anyway14:45
TuanVuyeah14:45
TuanVuit would be great if there's more people working on remaining OVO parts14:45
iharyeah btw one thing to mention in this venue14:46
iharI already mentioned it passing above but to make sure everyone is on the same page14:46
iharwe merged boden's patch https://review.openstack.org/#/c/553838/ that adds OVO registry14:46
*** markvoelker has quit IRC14:47
ihartl;dr projects (incl. neutron) will register their objects and then other subprojects will be able to get classes from this registry by name.14:47
iharso we get rid of module import dependency between two14:47
lujinluonice14:48
iharit's new thing, not released yet, but I believe boden will follow up with adoption once it is14:48
TuanVuthanks for this info, Ihar14:48
*** markvoelker has joined #openstack-meeting-514:48
lujinluoneed to take closer look to follow14:49
mlavallewe will release neutron-lib next week14:49
iharthis is partially the reason why I am more concerned about custom methods now because we are going big league now, officially exposing ovo as part of neutron interfaces.14:49
mlavalleit will be included in that release14:49
iharand plugins may start catching up to this interface more now14:49
ihar(so far we had just a bunch that use ovo in any capacity)14:50
lujinluoyeah, i will keep that in mind too. need to consider more14:50
iharok that's all I have14:50
lujinluothanks!14:51
mlavalleo/14:51
lujinluodose anyone have anything else?14:51
TuanVuthank you, Ihar :)14:51
lujinluoif not, we can call it a day!14:51
iharit seems like we can indeed14:51
hungpv_Good night you ak14:51
iharo/14:51
lujinluo#endmeeting14:51
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"14:52
openstackMeeting ended Thu Apr 19 14:51:59 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:52
iharhave a nice rest!14:52
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_upgrades/2018/neutron_upgrades.2018-04-19-14.00.html14:52
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_upgrades/2018/neutron_upgrades.2018-04-19-14.00.txt14:52
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_upgrades/2018/neutron_upgrades.2018-04-19-14.00.log.html14:52
TuanVuNone from me14:52
lujinluoyeah, i finally got the command right!14:52
TuanVusee you later, mlavalle, Ihar and Luo-san14:52
TuanVuhaha, congrats, Luo :D14:53
iharlujinluo: you get better and better at it every meeting. I should have passed the batton to you all along.14:53
iharok ciao everyone, have a good evening (or any other daytime you may have)14:53
*** ihar has left #openstack-meeting-514:53
mlavalleTuanVu, lujinluo: good night!14:54
lujinluomlavalle: thank you! have a good day!14:54
*** lujinluo has quit IRC14:55
*** mlavalle has left #openstack-meeting-515:00
*** TuanVu has quit IRC15:06
*** yamamoto has quit IRC15:13
*** yamamoto has joined #openstack-meeting-515:14
*** yamamoto has quit IRC15:19
*** annp_ has quit IRC15:23
*** yamahata has quit IRC15:23
*** ricolin has joined #openstack-meeting-515:25
*** yamamoto has joined #openstack-meeting-515:34
*** yamahata has joined #openstack-meeting-515:56
*** slaweq_ has quit IRC15:59
*** slaweq has joined #openstack-meeting-515:59
*** slaweq has quit IRC16:00
*** slaweq has joined #openstack-meeting-516:00
*** felipemonteiro has joined #openstack-meeting-516:05
*** slaweq has quit IRC16:05
*** radeks has quit IRC16:10
*** hungpv_ has quit IRC16:58
*** derekh has quit IRC17:01
*** yamamoto has quit IRC17:20
*** felipemonteiro_ has joined #openstack-meeting-517:55
*** felipemonteiro has quit IRC17:59
*** slaweq has joined #openstack-meeting-518:01
*** slaweq has quit IRC18:06
*** felipemonteiro__ has joined #openstack-meeting-518:08
*** felipemonteiro_ has quit IRC18:08
*** ricolin has quit IRC18:16
*** pabelanger has quit IRC18:17
*** pabelanger has joined #openstack-meeting-518:17
*** yamamoto has joined #openstack-meeting-518:20
*** yamamoto has quit IRC18:30
*** diman has joined #openstack-meeting-518:37
*** diman has quit IRC18:42
*** felipemonteiro_ has joined #openstack-meeting-519:09
*** felipemonteiro__ has quit IRC19:13
*** slaweq has joined #openstack-meeting-519:30
*** slaweq has quit IRC19:30
*** slaweq has joined #openstack-meeting-519:54
*** slaweq has quit IRC20:54
*** felipemonteiro_ has quit IRC20:54
*** slaweq has joined #openstack-meeting-520:54
*** slaweq has quit IRC20:59
*** yamamoto has joined #openstack-meeting-521:49
*** diman has joined #openstack-meeting-522:38
*** diman has quit IRC22:42
*** slaweq has joined #openstack-meeting-522:55
*** hongbin_ has quit IRC22:57
*** slaweq has quit IRC23:00
*** hoangcx_ has joined #openstack-meeting-523:16
*** hoangcx has quit IRC23:18
*** mjturek has quit IRC23:20
*** hoangcx_ is now known as hoangcx23:22

Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!