Friday, 2016-02-12

*** jckasper has quit IRC00:01
*** jckasper has joined #openstack-neutron-ovn00:01
*** azbiswas has quit IRC00:03
*** azbiswas has joined #openstack-neutron-ovn00:04
*** azbiswas has quit IRC00:04
*** azbiswas has joined #openstack-neutron-ovn00:04
*** azbiswas has quit IRC00:05
*** jckasper has quit IRC00:06
russellbSam-I-Am: thanks for helping debug that!00:10
Sam-I-Amrussellb: no problem00:19
Sam-I-Ami bet that was it though00:19
Sam-I-Ambleh, another failed vagrant00:20
*** salv-orlando has quit IRC00:25
*** aginwala has quit IRC00:29
*** aginwala has joined #openstack-neutron-ovn00:32
*** aginwala has quit IRC00:33
*** aginwala has joined #openstack-neutron-ovn00:33
*** zhouhan has quit IRC00:58
*** dlundquist has joined #openstack-neutron-ovn01:00
*** allan_h has quit IRC01:09
*** aginwala has quit IRC01:10
*** aginwala has joined #openstack-neutron-ovn01:14
*** aginwala has quit IRC01:15
*** aginwala has joined #openstack-neutron-ovn01:15
*** aginwala has quit IRC01:43
*** yamamoto_ has joined #openstack-neutron-ovn01:44
*** aginwala has joined #openstack-neutron-ovn01:50
*** yamamoto_ has quit IRC02:04
*** gangil has quit IRC02:16
*** aginwala has quit IRC02:26
openstackgerritMerged openstack/networking-ovn: DPDK support for OVN  https://review.openstack.org/27510302:30
*** aginwala has joined #openstack-neutron-ovn02:30
*** arosen12 has quit IRC02:46
*** arosen121 has joined #openstack-neutron-ovn02:46
*** yamamoto_ has joined #openstack-neutron-ovn02:51
*** salv-orlando has joined #openstack-neutron-ovn02:53
*** salv-orlando has quit IRC02:55
*** aginwala has quit IRC02:57
*** aginwala has joined #openstack-neutron-ovn03:00
*** aginwala has quit IRC03:02
*** azbiswas has joined #openstack-neutron-ovn03:05
*** gangil has joined #openstack-neutron-ovn03:08
*** gangil has joined #openstack-neutron-ovn03:08
*** arosen121 has quit IRC03:13
*** azbiswas has quit IRC03:13
*** arosen12 has joined #openstack-neutron-ovn03:13
*** jckasper has joined #openstack-neutron-ovn03:27
*** jckasper has quit IRC04:16
*** jckasper has joined #openstack-neutron-ovn04:16
*** jckasper has quit IRC04:19
*** jckasper has joined #openstack-neutron-ovn04:19
*** chandrav has joined #openstack-neutron-ovn04:26
*** jckasper has quit IRC04:37
*** salv-orlando has joined #openstack-neutron-ovn04:37
*** jckasper has joined #openstack-neutron-ovn04:38
*** salv-orlando has quit IRC04:42
*** chandrav has quit IRC05:02
*** chandrav has joined #openstack-neutron-ovn05:06
*** chandrav has quit IRC05:09
*** toor has quit IRC05:09
*** toor has joined #openstack-neutron-ovn05:09
*** chandrav has joined #openstack-neutron-ovn05:10
*** stac has quit IRC05:11
*** stac has joined #openstack-neutron-ovn05:17
*** jckasper has quit IRC05:21
*** jckasper has joined #openstack-neutron-ovn05:21
*** aginwala has joined #openstack-neutron-ovn05:25
*** allan_h has joined #openstack-neutron-ovn05:27
*** jckasper_ has joined #openstack-neutron-ovn05:31
*** jckasper has quit IRC05:32
*** jckasper_ has quit IRC05:38
*** jckasper has joined #openstack-neutron-ovn05:39
*** jckasper has quit IRC05:53
*** chandrav has quit IRC05:53
*** jckasper has joined #openstack-neutron-ovn05:53
*** salv-orlando has joined #openstack-neutron-ovn05:54
*** salv-orlando has quit IRC05:56
*** jckasper has quit IRC05:57
*** aginwala has quit IRC06:01
*** aginwala has joined #openstack-neutron-ovn06:04
*** numans has joined #openstack-neutron-ovn06:09
*** gangil has quit IRC06:13
*** aginwala has quit IRC06:25
*** numans has quit IRC06:26
*** numans has joined #openstack-neutron-ovn06:28
*** aginwala has joined #openstack-neutron-ovn06:35
*** arosen12 has quit IRC06:45
*** numans has quit IRC06:53
*** armax has quit IRC06:54
*** gangil has joined #openstack-neutron-ovn06:56
*** gangil has joined #openstack-neutron-ovn06:56
*** aginwala has quit IRC06:58
*** aginwala has joined #openstack-neutron-ovn07:00
openstackgerritBabu Shanmugam proposed openstack/networking-ovn: Enabling qos support through Logical_Port.options  https://review.openstack.org/26579807:03
*** salv-orlando has joined #openstack-neutron-ovn07:12
*** numans has joined #openstack-neutron-ovn07:15
*** salv-orlando has quit IRC07:23
*** allan_h has quit IRC07:29
*** gangil has quit IRC07:33
*** aginwala has quit IRC08:17
*** salv-orlando has joined #openstack-neutron-ovn08:28
*** aginwala has joined #openstack-neutron-ovn08:31
*** salv-orlando has quit IRC08:35
*** aginwala has quit IRC08:36
*** ig0r_ has quit IRC08:45
*** salv-orlando has joined #openstack-neutron-ovn09:05
*** igordcard has joined #openstack-neutron-ovn09:11
*** aginwala has joined #openstack-neutron-ovn09:14
*** aginwala has quit IRC09:18
*** igordcard has quit IRC09:42
*** salv-orlando has quit IRC09:52
*** salv-orlando has joined #openstack-neutron-ovn10:03
*** ig0r_ has joined #openstack-neutron-ovn10:13
*** openstackgerrit has quit IRC10:32
*** openstackgerrit has joined #openstack-neutron-ovn10:32
*** aginwala has joined #openstack-neutron-ovn10:35
*** aginwala has quit IRC10:40
*** salv-orl_ has joined #openstack-neutron-ovn10:41
*** numans has quit IRC10:42
*** salv-orlando has quit IRC10:45
*** numans has joined #openstack-neutron-ovn11:30
*** numans has quit IRC11:34
*** numans has joined #openstack-neutron-ovn11:36
*** ig0r_ has quit IRC11:48
*** ig0r_ has joined #openstack-neutron-ovn11:49
*** aginwala has joined #openstack-neutron-ovn11:53
*** jckasper has joined #openstack-neutron-ovn11:55
*** aginwala has quit IRC11:58
*** jckasper has quit IRC12:00
*** jckasper has joined #openstack-neutron-ovn12:06
*** chandrav has joined #openstack-neutron-ovn12:08
*** yamamoto_ has quit IRC12:12
*** jckasper has quit IRC12:16
*** jckasper has joined #openstack-neutron-ovn12:16
*** jckasper has quit IRC12:21
*** rtheis has joined #openstack-neutron-ovn12:25
*** aginwala has joined #openstack-neutron-ovn12:35
*** aginwala has quit IRC12:39
*** aginwala has joined #openstack-neutron-ovn12:48
*** aginwala has quit IRC12:53
*** salv-orl_ has quit IRC12:58
*** thumpba has joined #openstack-neutron-ovn13:13
*** thumpba has quit IRC13:14
*** thumpba has joined #openstack-neutron-ovn13:14
*** thumpba has quit IRC13:19
*** aginwala has joined #openstack-neutron-ovn13:40
*** aginwala has quit IRC13:44
Sam-I-Amrussellb: moo13:45
russellbribbit13:45
* russellb testing QoS integration13:47
Sam-I-Amoh boy13:47
Sam-I-Amrussellb: i was trying to disable ovn-controller on the vagrant controller node because nothing really needs it. however, this breaks a lot of the devstack plugin.13:48
russellbso fix it!  :-p13:49
Sam-I-Amseems to me that in a prod environment, there's actually no reason for any ovn stuff on the controller node, including ovs13:49
russellbyep makes sense13:49
russellbjust never tried to configure that13:49
Sam-I-Amhowever, its nice to have ovs on the vagrant controller node to make testing a bit easier13:49
Sam-I-Amin other words, the controller node can see all the network stuffs13:49
openstackgerritRussell Bryant proposed openstack/networking-ovn: Enabling qos support through Logical_Port.options  https://review.openstack.org/26579813:53
Sam-I-Ammestery: ping13:55
mesterySam-I-Am: pong13:55
Sam-I-Ammestery: can you read back a few mins here and let me know what you think?13:55
* mestery reads and scales13:56
Sam-I-Ami'd have to modify devstack to get ovs on a node without any normal ovn bits13:56
mesterySam-I-Am: I am in favor of not running ovn-controller on the control node for devstack, how hard is that turning out to be?13:57
Sam-I-Ammestery: in theory its easy. in practice... not easy.13:57
mesterylol13:57
Sam-I-Amso, here's my thinking...13:57
Sam-I-Amas i mentioned to russell, in a prod environment, the controller node really won't have any interaction with the ovs/ovn networks... in other words, it really doesn't need ovs at all.13:58
* mestery nods13:58
Sam-I-Amwhich is sort of what happens if you disable ovn-controller. ovs isnt deployed, and when it goes to do the provider network bits, it breaks13:58
russellb"when it goes to do the provider network bits"13:59
russellbwhen what does the provider network bits13:59
russellbwhy is devstack doing provider network bits on a node not running ovn-controller?13:59
russellb"because devstack" ?13:59
Sam-I-Ambecause of the vagrant provider setup script that runs on every node to configure br-provider14:00
russellbok, i see14:00
Sam-I-Amyeah, its a holdover from when the controller ran n-cpu14:00
Sam-I-Amreality is, i can probably just pop the eth2 (what used to br-provider) interface on the provider network and "see" all of the stuff on the compute node provider network14:01
mesterySam-I-Am: This is tied to our Vagrant stuff as well right?14:01
Sam-I-Amthe only thing that won't work is your Magic Workaround for accessing private networks14:01
Sam-I-Amwell, wont work from the controller node14:01
russellbwas Mic22's idea, his magic workaround :)14:03
Sam-I-Amlol14:04
Mic22what are you talking about?14:04
russellbMic22: he was referencing the use of an ovs port with type=internal to put your hypervisor on an ovn logical network14:04
russellbMic22: and i'm trying to give you credit for the idea, even though i added it to our docs :)14:05
russellbhe called it my workaround :)14:05
russellbthat's all..14:05
*** chandrav has quit IRC14:07
Mic22I imagined you were talking about this but I don't get how is this related to a provider net14:07
Sam-I-Amso...14:07
Sam-I-Amright now i think most people would run that workaround on the controller node, so they can play with stuff14:08
Sam-I-Amif we remove ovs from the controller node in vagrant, which is supposed to mimic a minimal prod arch, we cant do the hack there.14:08
Sam-I-Amthats really the only reason. outside of that, the controller still has an interface on the same ip network as the provider net and should "see" vms on the provider net just fine14:09
Sam-I-Amjust... not vms on a private net14:09
Mic22the reason why i needed this hack was to have a bunch of bm to proxy traffinc in the vm net14:09
Sam-I-Ammestery russellb so if we want vagrant to lean more toward this minimal prod-like ref arch, we should remove ovs from the controller14:09
Mic22well if you have all your BM inside the same L2 segment you can of course just use a provider network14:10
Mic22and everything would work14:10
Sam-I-Amyeah14:10
Mic22but in a deployment where you have separate providers I don't see how can you achieve the same with provider nets14:11
Sam-I-Amthe vagrant deployment only supports 1 provider net14:12
Sam-I-Amso...14:13
Mic22so yes !14:13
Sam-I-Amaight, i'll chuck ovs from the controller node and see what happens14:13
*** salv-orlando has joined #openstack-neutron-ovn14:13
Mic22it will work even better because you don't have the overhead of tunneling14:13
Sam-I-Amyou can all throw rotten tomatoes at my patch if you dont like it14:14
Mic22not saying this, I was just trying to get your idea. Actually in my deployment on the controller i don't have ovs so i cannot agree more14:15
Sam-I-Amoh, interesting.14:15
Sam-I-Ami'm trying to make vagrant deploy the ref arch14:15
Sam-I-Amat least as close as i can get14:15
Sam-I-Ambecause that'll eventually go into the networking guide as the deployment scenario14:15
Mic22the only problem I encountered is related to SSL for the northd14:16
Mic22but i simply got rid of it14:16
openstackgerritNuman Siddique proposed openstack/networking-ovn: Neutron ovn northbound db sync tool  https://review.openstack.org/27780514:16
Mic22dunno if it can be useful for you but this https://patchwork.ozlabs.org/patch/581435/ patch separate ovn dbs from ovs you can take the scripts out and just run the dbs needed14:17
Mic22i have ovs installed but I'm simply not running it14:17
Sam-I-Amhmmm14:18
*** jckasper has joined #openstack-neutron-ovn14:37
Sam-I-Amrussellb: did you see my crazy e-mail to the dev list?14:46
russellbsure did, via my cell phone last night at least14:46
mesterySam-I-Am: I'm reading now14:49
Sam-I-Amwelp, time to dust off the old resume...14:50
*** jckasper has quit IRC14:50
*** jckasper has joined #openstack-neutron-ovn14:51
mesterylol14:54
*** jckasper has quit IRC14:55
Sam-I-Amvagrant, round 3415:06
*** yamamot__ has joined #openstack-neutron-ovn15:09
*** jckasper has joined #openstack-neutron-ovn15:14
*** jckasper has quit IRC15:20
*** jckasper has joined #openstack-neutron-ovn15:20
openstackgerritRussell Bryant proposed openstack/networking-ovn: doc: Note DPDK support in the features doc.  https://review.openstack.org/27959915:22
*** jckasper has quit IRC15:22
*** jckasper has joined #openstack-neutron-ovn15:22
*** jckasper has quit IRC15:27
openstackgerritNuman Siddique proposed openstack/networking-ovn: Neutron ovn northbound db sync tool  https://review.openstack.org/27780515:27
*** jckasper has joined #openstack-neutron-ovn15:27
openstackgerritRussell Bryant proposed openstack/networking-ovn: doc: Rename doc to "install".  https://review.openstack.org/27960315:28
Sam-I-Amrussellb: hey now15:29
Sam-I-Amam i reading this right?15:29
russellbSam-I-Am: thoughts?15:29
Sam-I-Amubuntu can has packages?15:29
russellbyes15:30
russellbwell15:30
Sam-I-Amin X? or cloud-archive?15:30
russellbno.15:30
russellbwell...15:30
russellbthe packaging stuff is maintained in ovs itself15:30
russellbit has been updated15:30
russellbi'm not sure if it has been built in any distro yet15:30
russellbstep 1 is done though15:30
russellbyou can build ovn packages from the ovs repo :)15:30
Sam-I-Amyeah15:31
russellbwhich means once a version new enough ships in a distro, it should include ovn as well15:31
russellbin theory15:31
russellb(same state as the RHEL/Fedora bits)15:31
Sam-I-Amwell, given how quickly ovn/ovs moves along, it probably makes sense to either a) tell people they need to build locally and optionally create packages for their particular version of a distro or b) produce packages for a handful of versions and stuff them in a repo on ovs.org or whatever. however, with all the kernel deps i'm not sure thats possible.15:33
Sam-I-Amrussellb: did my ovs-dev post make any sense?15:42
*** jckasper has quit IRC15:44
russellbthere are pacakges for the kernel module as well15:44
*** jckasper has joined #openstack-neutron-ovn15:45
russellband to be honest, i haven't digested your post yet15:45
russellbi'm sure it makes sense though :)15:45
Sam-I-Amlol15:45
Sam-I-Ami recommend tums :)15:45
Sam-I-Amdoesnt the kernel package depend on a particular kernel ver?15:45
russellband by "haven't digested" i mean, haven't read15:45
russellbyes15:45
russellbso kind of a pain15:45
Sam-I-Amseems like we should just run with the 'build it locally, heres how you can build packages if you want to roll this on multiple nodes'15:46
russellb++ for now15:46
Sam-I-Ami dont need to reinvent the wheel for packaging... ovs has that licked.15:46
russellbwe want people testing ovs master right now anyway15:46
Sam-I-Amwe'll just need to provide some hints on things like init scripts15:47
* russellb nods15:47
russellbthose are included in the packages at least15:47
Sam-I-Amfor kicks i might try to install ovs from homebrew packages to see what happens15:48
Sam-I-Amsort of... kick off devstack with ovn, but dont have it install ovs... or something.15:48
*** jckasper has quit IRC15:49
openstackgerritRussell Bryant proposed openstack/networking-ovn: Fix several ovsdb verify() issues.  https://review.openstack.org/27961515:49
*** aginwala has joined #openstack-neutron-ovn15:54
*** aginwala has quit IRC15:58
*** jckasper has joined #openstack-neutron-ovn16:00
*** salv-orlando has quit IRC16:01
*** gangil has joined #openstack-neutron-ovn16:02
*** gangil has joined #openstack-neutron-ovn16:02
*** azbiswas has joined #openstack-neutron-ovn16:16
*** gangil has quit IRC16:19
*** gangil1 has joined #openstack-neutron-ovn16:19
*** ig0r_ has quit IRC16:20
*** gangil1 has quit IRC16:20
azbiswasrussellb: I saw that you proposed the fix https://review.openstack.org/#/c/279615/ for DB Integrity Error16:20
russellbazbiswas: yeah, saw a bug report so went ahead and threw up a patch16:21
azbiswasI was testing with a similar patch last night, the DB errors seem to be gone. I did run into RETRYs and sometimes Timeouts16:21
russellbRETRYs would definitely be expected16:21
russellbtimeouts may be worth looking into some more16:21
azbiswasYes that's good16:21
azbiswasBut the timeouts could become a problem16:21
russellbyes16:21
russellbneed to figure out where that's happening exactly16:22
russellbmaybe we have a timeout set too low16:22
azbiswasI was trying to get to the DB corruption with my patch so I was a little bullish in my scenario16:22
russellb:)16:23
azbiswasI was creating upto 200 ports on a provider network16:23
azbiswasLet's say there are M existing ports, the M+1th port results in M+1 DelACLs + (M+1)*C AddACLs where C is the number of security group rules16:24
azbiswasit's a bunch of transactions that may need to retried in case verify returns RETRY16:24
azbiswasI'm not sure if that is resulting in timeout though16:25
russellbare you getting RuntimeError("OVS transaction timed out") ?16:25
russellbor something else?16:25
azbiswas   raise RuntimeError("OVS transaction timed out")16:25
azbiswasRuntimeError: OVS transaction timed out16:25
azbiswas2016-02-12 09:06:31.482 TRACE neutron.api.v2.resource RuntimeError: OVS transaction timed out16:25
russellbyep, ok16:25
russellbthat timeout defaults to 1 minute16:26
azbiswasI'll try out your exact patch and see if that makes a difference16:26
russellbmeans we're taking longer than 1 minute to successfully complete a given transaction ...16:26
azbiswasRight16:26
russellbthat's a lot :/16:26
azbiswasLet me try out your specific patch - mine had a couple of difference16:26
russellbok16:27
azbiswasminor ones16:27
*** gangil has joined #openstack-neutron-ovn16:27
*** gangil has joined #openstack-neutron-ovn16:27
*** gangil has quit IRC16:27
russellbi moved things a little more than necessary16:27
russellbbut addressed some places other than acls16:27
russellbacls seems to be where we're most likely to hit it16:27
*** gangil has joined #openstack-neutron-ovn16:27
*** gangil has joined #openstack-neutron-ovn16:27
russellbbut there were some others16:27
azbiswasright I saw, anyways will update you on the patch16:28
russellbthanks for the help!16:28
azbiswaswhat about the M+1 * C ACLs updates - can that be improved?16:28
russellbprobably.  there's a couple things to that ...16:28
russellbwe may be deleting/adding more than is actually changing.  however, the IDL is supposed to automatically work it down to only things that changed, so the resulting ovsdb transaction should be what we really wanted16:29
russellbi haven't looked at how that's implemented, it could be that we could cut it down in a more efficient way before going into the ovsdb code16:29
russellbif we actually *need* to change that many rows, then that's a different story16:30
russellbthere's a good change we really do need to change that many rows though16:30
russellbthe default security group rules for neutron include "remote_group"16:30
russellbwhich is a little bit painful to implement16:30
azbiswasThe NB ovs db logs show a lot of transactions - these are optimized out as well?16:31
russellbif you have a network with 200 ports16:31
*** numans has quit IRC16:31
russellbwhen you add port 201, you really do need to update the rules for the other 200 ports to allow traffic from port 20116:31
russellbso maybe that's what you're seeing ...16:31
russellbwe've talked a bit about making that more efficient, but haven't identified a clear path forward16:32
russellbzhouhan in particular was looking into that16:32
*** armax has joined #openstack-neutron-ovn16:32
azbiswasIs there a bug filed for that?16:32
russellbgood question ... i don't think so16:32
russellbi think it would require work in OVN16:33
russellbwhen these timeouts occurred, were you doing several operations at once, loading the system?16:33
russellbor do you get to where it takes that long just for 1 operation?16:33
russellb(bbl, getting some lunch)16:37
azbiswasI am running with multiple api workers, but 1 operation (add port to provider network) at a time from the CLI.16:39
azbiswasIt start coughing at around 150 ports16:39
*** allan_h has joined #openstack-neutron-ovn16:41
russellbouch16:52
russellbthat seems pretty bad16:52
russellbazbiswas: would be good to know if it's just neutron-server eating up the CPU, or if other services are eating the CPU as well (ovsdb-server, ovn-northd, ovn-controller, ...)16:53
russellbor it's just some combination of all of them, or what16:53
russellbin any case, sounds like something we should improve16:54
azbiswasYes, I am going to try out your patch and see if that makes a difference. And then figure out where the CPU blockage is.16:54
azbiswasBut either way, the fix is correct16:54
azbiswasit prevents the DB corruption16:54
russellbyay!16:55
azbiswasother problems already existing16:55
azbiswasexisted16:55
russellbwe have a couple of patches that will help the performance of this scenario on the OVN side16:55
russellbpending patches i mean16:55
azbiswasNB improvement?16:55
russellbif it looks like ovn-northd and/or ovn-controller are part of the problem anyway16:55
azbiswasyeah true16:56
azbiswasmaybe i should run it without ovn-controller to eliminate that part16:56
azbiswasthat could be the bottleneck in my simple experiment16:57
azbiswaswill keep you updated - the test will take some time to run16:57
russellbsounds good16:57
*** yamamot__ has quit IRC16:59
*** yamamoto_ has joined #openstack-neutron-ovn17:00
mesterySam-I-Am: Easy one https://review.openstack.org/#/c/279599/17:07
russellbmestery: Easy one https://review.openstack.org/#/c/279603/17:13
russellb:)17:13
Sam-I-Amand we try vagrant again... devstack requirements transient failure i think17:17
*** openstackgerrit has quit IRC17:17
*** openstackgerrit has joined #openstack-neutron-ovn17:17
openstackgerritMerged openstack/networking-ovn: doc: Note DPDK support in the features doc.  https://review.openstack.org/27959917:19
*** aginwala has joined #openstack-neutron-ovn17:25
openstackgerritMerged openstack/networking-ovn: doc: Rename doc to "install".  https://review.openstack.org/27960317:29
*** aginwala has quit IRC17:39
Sam-I-Amrussellb: heres a weird one for ytou18:02
Sam-I-Amrussellb: does plugin.sh run 4 times?18:02
russellbmore than once, at least, yes18:02
russellbit runs at various "stages"18:02
russellbsee the bottom where it figures out what stage we're in and then runs the right stuff18:02
Sam-I-Ami moved my snippet to configure env vars OVN_NB_DB and OVN_SB_DB up into plugin.sh and i get 4 sets of entries18:02
Sam-I-Amand its outside of the main loop... just near the bottom of the script18:03
russellbyep, if it's global, it'll run several times18:03
Sam-I-Amdamn18:03
*** chandrav has joined #openstack-neutron-ovn18:03
Sam-I-Amguess i could move it into the main loop under post-config18:04
Sam-I-Ami forgot its run for the various stack/unstack/post-config stages18:07
Sam-I-Amfor not changing much, this has become one of the more frustrating vagrant/devstack patches18:08
Sam-I-Amsort of hit a lot of logic problems removing ovn-controller and now ovs from the controller node18:08
*** jckasper has quit IRC18:11
*** jckasper has joined #openstack-neutron-ovn18:11
*** aginwala has joined #openstack-neutron-ovn18:12
*** jckasper has quit IRC18:12
*** jckasper has joined #openstack-neutron-ovn18:12
*** terryw is now known as otherwiseguy18:14
*** jckasper has quit IRC18:14
*** jckasper has joined #openstack-neutron-ovn18:15
*** salv-orlando has joined #openstack-neutron-ovn18:16
*** jckasper has quit IRC18:17
*** jckasper has joined #openstack-neutron-ovn18:17
*** aginwala has quit IRC18:24
*** openstack has joined #openstack-neutron-ovn18:25
*** aginwala has joined #openstack-neutron-ovn18:28
azbiswasrussellb: The patch https://review.openstack.org/#/c/279615/ encountered the timeout at the 140 port mark similar to mine. Unfortunately I wasn't monitoring what was going on at that time.18:31
russellbazbiswas: OK, well at least it's reproducible :)18:31
azbiswasI think we should merge it though, since it's not hitting the DB corruption. This is probably a pre-existing condition.18:32
russellbagree18:32
russellbeven if it *did* cause a performance regression, i don't think we have a choice18:32
russellbthis is required18:32
azbiswasI'll see what the update from my folks are - they are trying out the patch in a real scenario.18:33
azbiswasyes - agree this is necessary for correctness18:33
russellbazbiswas: can you comment on the patch with your successful test report?18:34
azbiswasYes doing that now and will provide another update after i talk with my folks.18:34
*** aginwala has quit IRC18:35
*** aginwala has joined #openstack-neutron-ovn18:37
*** openstackgerrit has quit IRC18:47
*** openstackgerrit has joined #openstack-neutron-ovn18:47
*** jckasper has quit IRC18:48
*** jckasper has joined #openstack-neutron-ovn18:48
*** jckasper has quit IRC18:49
*** jckasper has joined #openstack-neutron-ovn18:49
*** jckasper has quit IRC18:51
*** jckasper has joined #openstack-neutron-ovn18:52
openstackgerritRussell Bryant proposed openstack/networking-ovn: doc: Document HOST_IP setting requirement.  https://review.openstack.org/27972318:54
*** jckasper has quit IRC18:54
*** jckasper has joined #openstack-neutron-ovn18:54
*** numans has joined #openstack-neutron-ovn19:07
*** numans has quit IRC19:17
*** aginwala has quit IRC19:22
*** yamamoto_ has quit IRC19:34
*** aginwala has joined #openstack-neutron-ovn19:36
*** azbiswas has quit IRC19:58
*** gangil has quit IRC19:59
*** aginwala has quit IRC20:00
*** aginwala has joined #openstack-neutron-ovn20:02
*** aginwala has quit IRC20:03
*** aginwala has joined #openstack-neutron-ovn20:07
*** aginwala has quit IRC20:12
*** azbiswas has joined #openstack-neutron-ovn20:12
*** aginwala has joined #openstack-neutron-ovn20:13
openstackgerritMerged openstack/networking-ovn: doc: Document HOST_IP setting requirement.  https://review.openstack.org/27972320:42
openstackgerritRussell Bryant proposed openstack/networking-ovn: Enabling qos support through Logical_Port.options  https://review.openstack.org/26579820:46
*** yamamoto_ has joined #openstack-neutron-ovn20:48
*** gangil has joined #openstack-neutron-ovn20:51
*** gangil has joined #openstack-neutron-ovn20:51
*** yamamoto_ has quit IRC20:52
*** aginwala has quit IRC20:57
*** aginwala has joined #openstack-neutron-ovn20:59
*** salv-orlando has quit IRC21:03
azbiswasrussellb: My tests are showing that each port is deleting and re-adding the same set of ACLs for each new port add in that provider network. There is no remote_group in this case.21:08
azbiswasBasically the entire set of ACLs in the DB are getting changed for each port add21:08
azbiswasAm wondering if we can optimize:21:09
azbiswas            txn.add(self._ovn.delete_acl(21:09
azbiswas                    utils.ovn_name(port['network_id']),21:09
azbiswas                    port['id']))21:09
azbiswas            sg_ports_cache = {}21:09
azbiswas            subnet_cache = {}21:09
azbiswas            self._add_acls(context, port, txn,21:09
azbiswas                           sg_ports_cache=sg_ports_cache,21:09
azbiswas                           subnet_cache=subnet_cache)21:09
azbiswasin _update_port_in_ovn21:09
russellbthat's what happens in Python21:11
russellbis that what actually gets sent to ovsdb-server as well?21:11
azbiswasI'll have to investigate that - am noticing the entire DB ACL uuids changing21:11
russellba logical switch has an acls column21:12
russellbwhich is a set of UUIDs21:12
azbiswasright21:12
russellbyou'll always see a new set of UUIDs sent21:12
russellbno way to optimize that really21:12
azbiswaswhat about the actual ACLs themselves21:13
russellbthat's not true, there is, but requires a new ovsdb feature21:13
azbiswasThe ACL table21:13
azbiswasthe uuids in that table seems to completely change as well21:13
azbiswasis that expected?21:14
russellbno21:14
azbiswasI'll write up a script to compare21:14
russellbmy expectation was that if an ACL didn't actually change, it would get excluded from the transaction21:14
russellbi left a comment in the code saying that21:14
russellbif it's not true, then we definitely have room for optimization here!21:15
azbiswasright, that was my thought as well, but let me write the script21:15
azbiswasand see21:15
russellbok :)21:15
*** yamamoto_ has joined #openstack-neutron-ovn21:18
*** yamamoto_ has quit IRC21:22
*** aginwala has quit IRC21:31
*** s3wong has joined #openstack-neutron-ovn21:36
-openstackstatus- NOTICE: The infrastructure team is taking gerrit offline for maintenance this afternoon, beginning at 22:00 utc. We should have it back online around 23:00 utc. http://lists.openstack.org/pipermail/openstack-dev/2016-February/086195.html21:46
*** yamamoto_ has joined #openstack-neutron-ovn21:48
azbiswasrussellb: I ran my script - as I suspected with my eyeball test, all the ACL uuids have changed after 1 port was added21:49
russellbok, sounds like it's not behaving like i expected21:49
russellbi'm leaving now for the weekend though21:50
azbiswascan I take over this investigation21:50
russellbof course :)21:50
russellbwant to file a bug and then assign it to yourself?21:50
azbiswasyes will do21:50
russellbthanks!  have a nice weekend!21:50
azbiswashave a good weekend21:50
*** yamamoto_ has quit IRC21:52
*** aginwala has joined #openstack-neutron-ovn21:54
-openstackstatus- NOTICE: Gerrit is offline for maintenacne until 23:00 utc22:05
*** ChanServ changes topic to "Gerrit is offline for maintenacne until 23:00 utc"22:05
*** rtheis has quit IRC22:30
*** aginwala has quit IRC22:38
*** aginwala has joined #openstack-neutron-ovn22:42
*** yamamoto_ has joined #openstack-neutron-ovn22:48
*** yamamoto_ has quit IRC22:52
*** jckasper has quit IRC23:02
*** jckasper has joined #openstack-neutron-ovn23:03
*** jckasper has quit IRC23:06
*** jckasper has joined #openstack-neutron-ovn23:06
-openstackstatus- NOTICE: Gerrit is offline for maintenance, ETA updated to 23:30 utc23:06
*** ChanServ changes topic to "Gerrit is offline for maintenance, ETA updated to 23:30 utc"23:06
Sam-I-Ammoo?23:09
*** aginwala has quit IRC23:13
*** jckasper has quit IRC23:16
*** allan_h has quit IRC23:16
*** jckasper has joined #openstack-neutron-ovn23:16
*** aginwala has joined #openstack-neutron-ovn23:19
*** jckasper has quit IRC23:21
*** jckasper has joined #openstack-neutron-ovn23:22
*** jckasper has quit IRC23:27
*** jckasper has joined #openstack-neutron-ovn23:28
*** azbiswas has quit IRC23:30
*** azbiswas has joined #openstack-neutron-ovn23:31
*** jckasper has quit IRC23:32
*** yamamoto_ has joined #openstack-neutron-ovn23:33
*** azbiswas has quit IRC23:36
*** yamamoto_ has quit IRC23:37
-openstackstatus- NOTICE: Gerrit is offline for maintenance, ETA updated to 23:59 utc23:41
*** ChanServ changes topic to "Gerrit is offline for maintenance, ETA updated to 23:59 utc"23:41
*** salv-orlando has joined #openstack-neutron-ovn23:44
*** armax has quit IRC23:44
*** armax has joined #openstack-neutron-ovn23:44
*** jckasper has joined #openstack-neutron-ovn23:52
*** jckasper has quit IRC23:53
*** salv-orlando has quit IRC23:53
*** jckasper has joined #openstack-neutron-ovn23:54
*** jckasper has quit IRC23:58

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