Thursday, 2018-06-28

*** felipemonteiro_ has joined #openstack-meeting-500:12
*** felipemonteiro_ has quit IRC00:26
*** yamahata has quit IRC01:07
*** ricolin has joined #openstack-meeting-502:17
*** roman_g has quit IRC03:06
*** slaweq has quit IRC03:53
*** yamahata has joined #openstack-meeting-504:08
*** slaweq has joined #openstack-meeting-504:11
*** slaweq has quit IRC04:16
*** nguyenhai has left #openstack-meeting-504:31
*** slaweq has joined #openstack-meeting-505:11
*** slaweq has quit IRC05:15
*** slaweq has joined #openstack-meeting-506:11
*** slaweq has quit IRC06:15
*** slaweq has joined #openstack-meeting-506:44
*** slaweq has quit IRC06:48
*** slaweq has joined #openstack-meeting-506:54
*** hoangcx has joined #openstack-meeting-508:08
*** hoangcx has left #openstack-meeting-508:08
*** roman_g has joined #openstack-meeting-508:22
*** derekh has joined #openstack-meeting-508:40
*** sgrasley has quit IRC09:11
*** sgrasley has joined #openstack-meeting-509:17
*** skazi has quit IRC10:34
*** skazi has joined #openstack-meeting-512:23
*** mjturek has joined #openstack-meeting-513:01
*** lujinluo has joined #openstack-meeting-513:38
*** jgu has joined #openstack-meeting-513:45
*** hongbin has joined #openstack-meeting-513:50
*** jgu has quit IRC13:50
*** njohnston has joined #openstack-meeting-513:54
*** TuanVu has joined #openstack-meeting-513:54
*** TuanVu has quit IRC13:56
*** TuanVu has joined #openstack-meeting-513:59
lujinluo#startmeeting neutron_upgrades14:00
openstackMeeting started Thu Jun 28 14:00:18 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
lujinluoHi all! Long time no see14:00
TuanVuHi Luo :D14:01
TuanVugreat to see you14:01
njohnstonWelcome back!14:01
lujinluoThanks njohnston for taking over the duties for the past two weeks14:01
njohnstonI am happy to have been of service.14:01
*** GregWaines has joined #openstack-meeting-514:02
lujinluoI read the logs of the past two meetings, it seems we have some AIs? njohnston14:02
*** annp_ has joined #openstack-meeting-514:02
njohnstonYes, 1 moment14:02
njohnston(I have to look them up)14:02
lujinluosure14:03
njohnstonSo first one was to get core reviewers for https://review.openstack.org/#/c/565358/14:04
njohnstonI did reach out to a couple people14:04
njohnstonso now it just needs to pass gate consistently14:05
lujinluoyeah, it is waiting for final check now14:05
lujinluoseems to get merged pretty soon14:05
lujinluothanks!14:05
*** hungpv has joined #openstack-meeting-514:05
njohnstonand second one we can check now, which is that the wiki page for this meeting seems quite out of date (refrences Pike in the future tense)14:06
lujinluoyes, i am aware of that too. #link https://wiki.openstack.org/wiki/Meetings/Neutron-Upgrades-Subteam there are too much out-of-date info14:06
lujinluobut i am curious why you said you do not have right to edit it njohnston ?14:06
njohnstonI thought about updating it, but I did not feel I should without talking to you first, lujinluo.14:07
njohnstonI had an issue with my openstack id, which I have since sorted out14:07
lujinluoi see. i thought it was some technical issues. but you are more than welcome to update it! njohnston14:07
njohnstonI think that was all :-)14:08
lujinluoi will try to put the latest info tmr, but it would also be appreciated if you would help me with it too14:08
lujinluoas one person may miss something :-)14:08
TuanVuI'll also have a look14:09
lujinluothanks TuanVu !14:09
TuanVuso if you push a new patch, please add me as well14:09
TuanVuI'll try my best :)14:09
lujinluowiki page does not involve any patches14:09
lujinluoanyone is free to edit after logging to openstack id14:09
TuanVuoh, thanks for this info14:10
TuanVuthank you, Luo14:10
lujinluoyeah, then let us jump to the ovo patches first14:10
lujinluo#topic OVO14:10
*** openstack changes topic to "OVO (Meeting topic: neutron_upgrades)"14:10
lujinluo#link https://review.openstack.org/#/q/status:open+project:openstack/neutron+branch:master+topic:bp/adopt-oslo-versioned-objects-for-db14:10
lujinluo#link https://review.openstack.org/#/c/549168/ Router OVO14:11
lujinluoit is still pretty red14:11
lujinluohungpv: are you still trying to solve all the failures?14:11
lujinluowell, i think the author is not at the meeting right now.14:13
lujinluomaybe we should move to the next patch first14:13
lujinluo#link https://review.openstack.org/#/c/565358/  objects: don't refetch a non-list object field if it's None14:14
lujinluothis patch is so ready to go. hopefully we can see it merged within today :)14:14
njohnstonanother one waiting for the gate14:14
*** hungpv_ has joined #openstack-meeting-514:14
*** hungpv has quit IRC14:15
lujinluonjohnston: yeah, the gate seems to be slow14:15
lujinluo#link https://review.openstack.org/#/c/507772/ Network OVO14:16
lujinluoTuanVu: so I followed the recent comments about renamed type14:17
*** TuanVu has quit IRC14:17
lujinluoto make sure i am not missing anything. the status is that we have not figured a way to deal with it, right?14:17
lujinluoIhar's suggestion is to add a compatible layer14:17
lujinluoi have not had time to review the latest codes14:18
lujinluooops, Tuan is offline now..?14:18
njohnstonI think that one is nearly ready to merge, slaweq just has a couple of notes14:18
lujinluohow about the issues mentioned by boden?14:19
*** TuanVu has joined #openstack-meeting-514:19
TuanVusorry, there was something wrong with network connection14:19
TuanVuI'll provide answer for Slawek's comment soon14:19
lujinluoTuanVu: how about vmware-nsx's failures?14:19
lujinluoresulted from renames types14:20
TuanVuregarding to problem with vmware, as Ihar's comment, these changes are legit14:20
TuanVuboden will check more and provide update later14:20
TuanVufrom vmware side14:20
*** GregWaines has quit IRC14:21
lujinluoi might be missing something here, but it looks to me Ihar's opinion is that we should change something on OVO side, to avoid those failures on customers' side. no?14:21
lujinluoconsumers i mean14:22
lujinluonjohnston: i would like to hear your opinion14:23
TuanVuthat's what he means by providing compatibility layer14:23
TuanVubut I think it makes the problem to be more complicated14:23
TuanVuwhy not doing the "right" thing right away instead of making a layer to mix between "right" and "not right"?14:25
njohnstonIt does make the change a bit more complicated, no doubt.  The alternative is to make this change and then to lok through all networking projects and propose changes to each of them that will follow suit with this change.  I think the compatibility layer is more graceful.14:25
TuanVuthanks for the comment, Nate14:26
*** hungpv_ has quit IRC14:26
njohnstonSince you cannot dictate that another project changes something to match your change, either you do it yourself, or you make it so that they can keep functioning until they can make the needed change.14:26
TuanVuhmm14:27
njohnstonLet's recheck the vmware-nsx test patch and see what the issues it sees are14:27
lujinluoyes, agree with njohnston . but i think what i am missing here is that is this compatibility layer included in the patch already or not?14:27
TuanVuso compatibility layer is a great option14:28
TuanVunot yet, Luo-san14:28
lujinluowhich seems to me we do not have the compatibility layer yet14:28
TuanVuyeah14:28
TuanVuyou're correct14:28
lujinluonjohnston: good point. we shall recheck vmware-nsx and then see if boden has any updates14:29
njohnstonI just sent a recheck to https://review.openstack.org/574797/14:29
njohnstonwhich is the vmware-nsx test patch14:29
njohnstonshall we note an #action on this?14:30
lujinluo#action to see the latest result of https://review.openstack.org/574797/14:30
lujinluo#action lujinluo to check if bode has any updates on vmware-nsx side14:30
lujinluolet's move to next two patches14:31
lujinluo#link https://review.openstack.org/#/c/561834/ https://review.openstack.org/#/c/562489/14:31
lujinluothese two are recently reviewed by manjeet14:31
lujinluoTuanVu: you may not have had time to work on them yet14:31
lujinluooh, and one of them is reviewed by nate14:32
*** jgu has joined #openstack-meeting-514:32
lujinluo#link https://review.openstack.org/#/c/544206/ portbinding OVO14:33
*** MarkBaker has quit IRC14:33
TuanVuin last week IRC meeting, Nate had provided some suggestion for doing "join"14:33
lujinluoyeah, i was planning to have that discussion on open discussion part14:33
lujinluoi have some questions regarding that14:33
TuanVuhowever, as far as I remember, the details (eg: maybe a patch with example) haven't been decided yet14:33
lujinluonjohnston: yeah, so i think i did not fully understand what dan suggested14:34
lujinluois he suggesting we should do 'joins' in a general way or we do them case-by-case?14:35
*** annp_ has quit IRC14:35
*** jgu has left #openstack-meeting-514:35
njohnstonIt seems to me that his suggestion works well for a specific type of join, where we are taking data from one object and adding a few fields from a second object14:35
lujinluoi see. i think we have other joins dealing with 3 tables14:36
njohnstonAfter looking at how the code works in Nova, it did not look to me like it would provide other functions that joins have, like "show me only the records that are in both table 1 and table 2"14:36
lujinluocan his suggestion work on that situation as well?14:36
njohnstonNot as well.14:36
njohnstonSo I think it is probably better to just rehome the joins into the objects.  This has already been done in a number of places, for example: https://git.openstack.org/cgit/openstack/neutron/tree/neutron/objects/ports.py#n20014:37
njohnstonor https://git.openstack.org/cgit/openstack/neutron/tree/neutron/objects/router.py#n14714:37
njohnstonjust a couple examples among many14:38
lujinluoyes, we did that before14:38
lujinluoit is kind of a historical reason as we could not find a good solution at that time14:38
njohnstonI don't think there is a good solution unless you have deep knowledge of the transaction in question.14:39
lujinluobut last time when we had the discussion about whether we should continue doing that, Ihar said we should still try to find more ovo-like solutions and i agreed14:39
lujinluobut if we still could not find it, i do not oppose the idea of moving joins into objects14:39
njohnstonI don't think we should hold up change based on this14:40
lujinluoalthough i do think that is the last we want to do14:40
*** MarkBaker has joined #openstack-meeting-514:40
lujinluoyes, i agree.14:40
njohnstonI don't want to delay the neutron upgrade core deliverable, which is what OVO is a means to, just based on the purity of OVO14:41
lujinluoyeah, i understand that.14:41
lujinluothen let's just move joins to objects14:41
njohnstonOnce we get to the seamless upgrade that the OVO transition promises us, then we can revisit this.  Maybe we will have had a better idea in the meantime. :-)14:41
lujinluohopefully :)14:42
njohnstonJust my own personal opinion :-)14:42
lujinluosure, i do not want to block the delivery of ovo either.14:42
lujinluolet's add TODOs when moving joins then14:43
lujinluoto remind us of the debts!14:43
TuanVuthank you, Nate and Luo for the discussion14:43
TuanVuI got it14:43
lujinluook, let's move to the next one14:44
lujinluo#line https://review.openstack.org/#/c/544206/ portbinding ovo14:44
lujinluothis one is on me14:44
lujinluoi will rebase and address manjeet's comments tmr14:44
lujinluobut i still need to wait for Migeuls' patch as well14:45
lujinluobut if you feel like doing more reviews, welcome!14:45
lujinluothe rest of the patches are not touched yet14:45
lujinluo#open discussion14:45
lujinluo#topic open discussion14:46
*** openstack changes topic to "open discussion (Meeting topic: neutron_upgrades)"14:46
lujinluo(vacation ruined my brain14:46
lujinluoi have one thing that i would like to share14:46
lujinluoas some of you might have already know, i am leaving my current employeer14:47
lujinluoi have hand over most of my community and in-house duties to my colleagues, but i will continue working on neutron ovo14:47
TuanVuthat's awesome, Luo :)14:48
TuanVuI'm very glad to know that14:48
lujinluosince i am going back to school to pursue a higher education, i will spend as much time as i can on ovo as i used to14:48
njohnstonI hope it is a fantastic new adventure for you! Glad you will still be in the community.14:48
lujinluobut if at some point of time in the future that i think i will not be spending that efforts, i will let you and Miguel know14:49
lujinluook, that is all about what i want to share!14:49
lujinluodoes anyone have anything else?14:50
TuanVualthough it's sad to see you leave Fujitsu but at the same time, I'm very happy to know that you're about to have a new great adventure14:50
lujinluothank you! TuanVu and njohnston14:50
TuanVu:)14:50
TuanVuregarding to Network OVO patch14:51
TuanVucompatibility layer14:51
TuanVuI don't understand what Ihar means by "'port_security' property that returns 'security' value"14:51
TuanVuand also "az_hints as string instead of a list of strings"14:52
njohnstonI did not go back and research those references, but I assumed he was listing examples of previous measures taken for compatibility shim reasons.14:53
TuanVuyeah, I mean I'm not sure how to build the layer for the conversion14:53
lujinluoi have not looked at the codes yet, but i think it is similar to the methods of from_db_object(), where you switching port_security in ovo and security in db14:54
njohnstonso right now vmware-nsx calls some function and expects to get back from that the data provided by sql alchemy, right?14:55
njohnstonso keep that function and the arguents the same, and have the function call whatever OVO methods accomplish the same result14:55
njohnstonthat way the vmware-nsx code does not need to change14:55
njohnstonYou may want to mark that it is being left for compatibility reasons in a comment14:56
njohnstonThe same tactic has been used as functionality is migrated from neutron into neutron-lib14:56
TuanVuthank you very much, Nate and Luo14:57
TuanVuI will dig more14:57
TuanVuif there's any other concern, I'll let both of you know :)14:57
lujinluono problem14:57
lujinluook i guess that's all for today14:58
lujinluothank you guys!14:58
njohnstonkeep asking questions; you're really close to it TuanVu!14:58
njohnstonThanks all14:58
lujinluosee you next week14:58
TuanVuthanks a lot, Nate :)14:58
TuanVusee you guys soon :)14:58
lujinluo#endmeeting14:58
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"14:58
openstackMeeting ended Thu Jun 28 14:58:33 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:58
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_upgrades/2018/neutron_upgrades.2018-06-28-14.00.html14:58
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_upgrades/2018/neutron_upgrades.2018-06-28-14.00.txt14:58
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_upgrades/2018/neutron_upgrades.2018-06-28-14.00.log.html14:58
*** lujinluo has quit IRC14:58
*** TuanVu has quit IRC15:03
*** MarkBaker has quit IRC15:08
*** yamamoto has quit IRC15:12
*** yamamoto has joined #openstack-meeting-515:12
*** njohnston has left #openstack-meeting-515:19
*** MarkBaker has joined #openstack-meeting-515:21
*** slaweq has quit IRC16:06
*** slaweq has joined #openstack-meeting-516:25
*** yamahata has quit IRC16:54
*** derekh has quit IRC17:00
*** yamahata has joined #openstack-meeting-517:13
*** ricolin has quit IRC17:25
*** mjturek has quit IRC17:57
*** mjturek has joined #openstack-meeting-518:10
*** mjturek has quit IRC18:15
*** mjturek has joined #openstack-meeting-518:16
*** jgu has joined #openstack-meeting-519:07
*** jgu has quit IRC19:17
*** mjturek has quit IRC20:12
*** mjturek has joined #openstack-meeting-520:30
*** mjturek has quit IRC21:25
*** jgu has joined #openstack-meeting-521:38
*** jgu has joined #openstack-meeting-521:39
*** sgrasley has quit IRC21:51
*** sgrasley has joined #openstack-meeting-521:51
*** sgrasley has quit IRC21:54
*** mjturek has joined #openstack-meeting-521:58
*** mjturek has quit IRC22:01
*** hongbin has quit IRC22:16
*** jgu has quit IRC23:01

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