Tuesday, 2019-03-05

*** br7k has joined #openstack-neutron00:02
*** zhanglong has joined #openstack-neutron00:05
*** br7k has quit IRC00:06
sean-k-mooneyo/ just signing of for the day but just tought i would ask why neutron enable N322 in flake8 http://logs.openstack.org/58/640258/4/check/openstack-tox-pep8/37c4c53/job-output.txt.gz#_2019-03-04_21_47_31_73568000:09
*** itlinux has joined #openstack-neutron00:09
sean-k-mooneywe do not use that in nova and i also dont think i would enable it in os-vif as i dont think useing assert_called_once_with is generally good pratice if the arguments the method are invoked with are not relevent00:10
*** itlinux_ has joined #openstack-neutron00:13
sean-k-mooneyassert_called_once is a valid method https://docs.python.org/3/library/unittest.mock.html#unittest.mock.Mock.assert_called_once00:14
sean-k-mooneyso https://github.com/openstack/neutron/blob/master/neutron/hacking/checks.py#L55-L76 apears to be incorrect00:14
*** itlinux has quit IRC00:15
*** wolverineav has joined #openstack-neutron00:16
sean-k-mooneyah its because they only exist for py3.6 on which is what im usingbut i guess they are noops in python 2.7 and 3.5 so asser_called_once_with is the python 2/3 compatiable method https://github.com/testing-cabal/mock/blob/release-0.8-maint/docs/mock.txt#L10400:26
*** openstackgerrit has joined #openstack-neutron00:26
openstackgerritKailun Qin proposed openstack/neutron master: [doc] Add network segment ranges into admin guide  https://review.openstack.org/63911000:26
*** abaindur has quit IRC00:28
*** cshen has joined #openstack-neutron00:29
*** abaindur has joined #openstack-neutron00:31
*** abaindur has quit IRC00:31
*** abaindur has joined #openstack-neutron00:32
*** cshen has quit IRC00:33
*** sapd1 has quit IRC00:42
*** wolverineav has quit IRC00:47
*** cheng1 has joined #openstack-neutron00:48
*** markvoelker has joined #openstack-neutron00:48
*** abaindur has quit IRC00:48
*** abaindur has joined #openstack-neutron00:49
*** cheng1 has quit IRC00:54
eanderssonCan you scale up the dhcp agent?00:55
*** wolverineav has joined #openstack-neutron00:58
*** macza has joined #openstack-neutron00:59
*** ileixe has joined #openstack-neutron01:00
openstackgerritDoug Wiegley proposed openstack/neutron master: Fix a couple of bw burst calc unit tests for macs  https://review.openstack.org/64090801:00
eandersson> Could not release DHCP leases for these IP01:00
eanderssonThis seems to be slowing things down01:01
*** macza has quit IRC01:03
eanderssonIn fact the dhcp-agent looks to be deadlocked01:11
*** br7k has joined #openstack-neutron01:14
*** br7k has quit IRC01:19
*** cheng1 has joined #openstack-neutron01:21
zhanglongchinamobile01:21
zhanglongo sry01:21
*** markvoelker has quit IRC01:22
*** macza has joined #openstack-neutron01:35
eanderssonsean-k-mooney, do you have any advise on tuning something like neutron_num_sync_threads for the dhcp agent?01:35
*** macza has quit IRC01:39
*** ileixe has quit IRC01:40
*** njohnston has quit IRC01:41
*** abaindur has quit IRC01:46
*** dave-mccowan has joined #openstack-neutron01:46
*** gouthamr has quit IRC01:48
*** dmellado has quit IRC01:50
*** ileixe has joined #openstack-neutron01:51
*** ileixe has quit IRC01:52
*** sapd1 has joined #openstack-neutron01:52
*** ileixe has joined #openstack-neutron01:53
openstackgerritKailun Qin proposed openstack/neutron master: Support Network Segment Range CRUD as extensions  https://review.openstack.org/62470801:54
openstackgerritKailun Qin proposed openstack/neutron master: Use network segment ranges for segment allocation  https://review.openstack.org/62470901:54
openstackgerritKailun Qin proposed openstack/neutron master: Devstack plugin for network-segment-range api  https://review.openstack.org/63838601:54
*** wolverineav has quit IRC01:57
*** abaindur has joined #openstack-neutron02:00
openstackgerritDoug Wiegley proposed openstack/neutron master: DNM: test ci  https://review.openstack.org/64092002:01
openstackgerritDoug Wiegley proposed openstack/neutron master: Use dynamic lazy mode for fetching security group rules  https://review.openstack.org/63740702:08
*** macza has joined #openstack-neutron02:11
*** hongbin has joined #openstack-neutron02:13
*** macza has quit IRC02:15
*** markvoelker has joined #openstack-neutron02:19
*** br7k has joined #openstack-neutron02:27
*** abaindur has quit IRC02:27
*** ircuser-1 has joined #openstack-neutron02:28
*** abaindur has joined #openstack-neutron02:28
*** zhanglong has quit IRC02:29
*** cshen has joined #openstack-neutron02:29
*** br7k has quit IRC02:31
*** abaindur has quit IRC02:32
*** wolverineav has joined #openstack-neutron02:33
*** cshen has quit IRC02:34
*** s1061123 has quit IRC02:34
*** zhanglong has joined #openstack-neutron02:36
*** s1061123 has joined #openstack-neutron02:37
*** sapd1 has quit IRC02:37
*** zhanglong has quit IRC02:45
openstackgerritZhao Qikun proposed openstack/neutron master: This is a test  https://review.openstack.org/64092702:45
*** gouthamr has joined #openstack-neutron02:50
*** zhanglong has joined #openstack-neutron02:50
*** markvoelker has quit IRC02:51
*** dmellado has joined #openstack-neutron02:55
dougwigeandersson: how many do you have now?02:56
eanderssonWe had it set to default 402:58
eanderssonRaised it to 802:58
eanderssonWe got stuck in some sort of deadlock, but currently believe that it was caused by too high load on the neutron-rpc/api server.02:58
*** wolverineav has quit IRC03:00
eanderssonStill scary as the dhcp-agent had over 1k messages queued in RabbitMQ03:01
*** wolverineav has joined #openstack-neutron03:01
*** wolverineav has quit IRC03:06
*** itlinux_ has quit IRC03:06
*** itlinux has joined #openstack-neutron03:12
dougwigif you can identify the expensive operation, you can deploy more worker nodes. for us, it was api calls, so an additional couple neutron controllers that did nothing but rpc and dhcp did the trick.  they're stateless, so they can do nothing but run those background threads.03:13
*** yamamoto has joined #openstack-neutron03:17
dougwigi'm not sure when we set our api workers to the number of cores and rpc workers to 1, but both are terrible values.  :)03:18
*** dsneddon has quit IRC03:19
*** itlinux has quit IRC03:21
*** itlinux has joined #openstack-neutron03:25
*** wolverineav has joined #openstack-neutron03:31
*** tbachman has quit IRC03:33
*** rkukura has quit IRC03:34
*** dsneddon has joined #openstack-neutron03:35
*** yamamoto has quit IRC03:35
*** yamamoto has joined #openstack-neutron03:35
*** cheng1 has quit IRC03:37
*** dsneddon has quit IRC03:40
*** dave-mccowan has quit IRC03:42
openstackgerritMerged openstack/neutron-fwaas master: add python 3.7 unit test job  https://review.openstack.org/63825903:46
*** zhanglong has quit IRC03:47
*** markvoelker has joined #openstack-neutron03:48
openstackgerritYushiro FURUKAWA proposed openstack/neutron-fwaas master: Migrate to stestr as unit tests runner  https://review.openstack.org/50552604:02
openstackgerritYushiro FURUKAWA proposed openstack/neutron-fwaas master: Update mailinglist from dev to discuss  https://review.openstack.org/63241604:03
*** wolverineav has quit IRC04:07
*** ramishra has joined #openstack-neutron04:09
*** dsneddon has joined #openstack-neutron04:15
*** dsneddon has quit IRC04:20
*** markvoelker has quit IRC04:22
*** cshen has joined #openstack-neutron04:30
*** cshen has quit IRC04:34
*** toshiiw has joined #openstack-neutron04:37
*** sridharg has joined #openstack-neutron04:41
openstackgerritMerged openstack/neutron-fwaas master: Remove midonet job  https://review.openstack.org/63485504:47
*** armax has quit IRC04:48
*** br7k has joined #openstack-neutron04:49
*** dsneddon has joined #openstack-neutron04:50
*** br7k has quit IRC04:53
*** dsneddon has quit IRC04:57
*** wolverineav has joined #openstack-neutron05:00
*** wolverineav has quit IRC05:06
*** janki has joined #openstack-neutron05:08
*** hongbin has quit IRC05:09
*** markvoelker has joined #openstack-neutron05:19
*** ratailor has joined #openstack-neutron05:23
*** dsneddon has joined #openstack-neutron05:30
*** cheng1 has joined #openstack-neutron05:31
*** rkukura has joined #openstack-neutron05:36
eanderssondougwig, yea lowered the number to match our physical cores05:37
eanderssonand moved some stuff around05:37
eanderssonlooking a lot better now05:37
eanderssonbut for sure a lot more cpu usage now than before05:37
dougwigyeah, the short-term answer is going to be to throw more boxes at it, unless you start seeing db contention, and then more parallel will start to hurt you.05:38
eanderssonbtw changing the neutron-api vip from rr to least connections made the cpu load a lot more even05:38
dougwigi believe that.  settles out the long-running stuff.05:39
*** dsneddon has quit IRC05:40
eanderssonhopefully the dhcp "deadlock" was related to extreme load05:40
eanderssonwill have to add some extra monitoring to make sure we catch that sooner05:40
*** cheng1 has quit IRC05:48
*** markvoelker has quit IRC05:51
*** pcaruana has joined #openstack-neutron05:52
*** lajoskatona has joined #openstack-neutron05:53
*** cheng1 has joined #openstack-neutron05:58
*** pcaruana has quit IRC06:07
*** dsneddon has joined #openstack-neutron06:10
*** sm806 has quit IRC06:17
*** sm806 has joined #openstack-neutron06:18
*** dims has quit IRC06:24
*** dims has joined #openstack-neutron06:26
*** sm806 has quit IRC06:31
*** sm806 has joined #openstack-neutron06:31
*** gcheresh_ has joined #openstack-neutron06:33
*** itlinux has quit IRC06:34
*** dims has quit IRC06:36
*** dims has joined #openstack-neutron06:37
*** cheng1 has quit IRC06:40
*** jlibosva has joined #openstack-neutron06:46
*** cshen has joined #openstack-neutron06:46
*** ksambor has joined #openstack-neutron06:48
*** markvoelker has joined #openstack-neutron06:48
*** wolverineav has joined #openstack-neutron06:48
*** Luzi has joined #openstack-neutron06:51
*** wolverineav has quit IRC06:53
openstackgerritLIU Yulong proposed openstack/neutron master: More accurate agent restart state transfer  https://review.openstack.org/64079706:57
*** sridharg has quit IRC06:57
*** mosulica has joined #openstack-neutron06:59
*** dayou has quit IRC07:01
*** zhanglong has joined #openstack-neutron07:01
*** dayou has joined #openstack-neutron07:01
*** sridharg has joined #openstack-neutron07:02
*** cheng1 has joined #openstack-neutron07:06
*** ccamposr has joined #openstack-neutron07:10
f0oMorning07:10
*** ccamposr__ has joined #openstack-neutron07:10
*** slaweq has joined #openstack-neutron07:11
*** ccamposr has quit IRC07:14
*** wolverineav has joined #openstack-neutron07:14
*** wolverineav has quit IRC07:14
*** hamdyk has joined #openstack-neutron07:18
*** br7k has joined #openstack-neutron07:21
*** markvoelker has quit IRC07:22
*** aojea has joined #openstack-neutron07:23
*** br7k has quit IRC07:25
*** yamamoto has quit IRC07:34
*** ralonsoh has joined #openstack-neutron07:34
*** yamamoto has joined #openstack-neutron07:36
*** dayou has quit IRC07:37
*** snapiri has joined #openstack-neutron07:57
*** dayou has joined #openstack-neutron07:58
*** abaindur has joined #openstack-neutron07:59
*** abaindur has quit IRC08:04
*** abaindur has joined #openstack-neutron08:04
*** tesseract has joined #openstack-neutron08:09
rubasovmlavalle, slaweq: good morning, I just read the neutron team meeting log from last evening08:14
slaweqhi rubasov08:14
rubasovmlavalle, slaweq: thanks for taking up the min-bw topic on it08:14
slaweqI wanted to ping You :)08:14
rubasovmlavalle, slaweq: I think we only have one change that is still due until ff08:15
rubasovmlavalle, slaweq: this: https://review.openstack.org/57478308:15
*** luksky has joined #openstack-neutron08:16
*** awalende has joined #openstack-neutron08:16
rubasovmlavalle, slaweq: thanks in advance if you can look at it08:16
*** tssurya has joined #openstack-neutron08:16
slaweqrubasov: sure08:16
rubasovmlavalle, slaweq: also let me cross-check with you please08:16
*** sapd1 has joined #openstack-neutron08:16
*** rpittau|afk is now known as rpittau08:16
slaweqrubasov: so all other patches from https://review.openstack.org/#/q/topic:minimum-bandwidth-allocation-placement-api+status:open aren't really needed to have BP done?08:16
rubasovmlavalle, slaweq: we have a feq feature related bugfixes: those have two more weeks, right?08:17
rubasovmlavalle, slaweq: like this: https://review.openstack.org/63871408:17
rubasovmlavalle, slaweq: and what is the deadline for docs? rc1?08:18
*** markvoelker has joined #openstack-neutron08:18
slaweqrubasov: I don't think there is any strict deadline for docs08:18
slaweqmaybe amotoki will know ^^ :)08:18
*** pcaruana has joined #openstack-neutron08:18
rubasovslaweq: because the networking guide patch is still wip08:19
rubasovslaweq: plus lajoskatona has a few more tests on that gerrit topic, but IIUC those also don't have strict deadlines08:19
slaweqok, so the most important for now is this one Your patch08:20
slaweqand other things can land a bit later08:20
slaweqthx for confirmation08:20
rubasovslaweq: yep, that's correct08:20
slaweqI will review this Your patch today08:20
rubasovslaweq: thanks for taking the time08:20
slaweqrubasov: sure, np :)08:21
*** tkajinam has quit IRC08:22
*** pcaruana has quit IRC08:25
*** rubasov has quit IRC08:33
*** br7k has joined #openstack-neutron08:34
*** pcaruana has joined #openstack-neutron08:37
*** br7k has quit IRC08:38
*** pcaruana has quit IRC08:44
*** markvoelker has quit IRC08:51
*** jpena|off is now known as jpena08:52
*** pcaruana has joined #openstack-neutron09:01
*** macza has joined #openstack-neutron09:01
amotokirubasov: slaweq: there is no deadline for the documentation. hopefully it is nice if the doc patch lands till RC-1 (i.e., stein branch cut), but we can backport it even after that.09:01
slaweqamotoki: that's what I though, thx for confirmation :)09:03
*** macza has quit IRC09:05
*** moshele has joined #openstack-neutron09:09
*** toshiiw has quit IRC09:10
*** abaindur has quit IRC09:13
*** panda|ruck|off is now known as panda|ruck|flu09:13
*** lemko has joined #openstack-neutron09:23
*** cheng1 has quit IRC09:34
*** br7k has joined #openstack-neutron09:45
*** markvoelker has joined #openstack-neutron09:48
*** br7k has quit IRC09:49
*** cheng1 has joined #openstack-neutron09:49
*** moshele has quit IRC09:52
*** zhanglong has quit IRC10:03
*** rubasov has joined #openstack-neutron10:05
*** yamamoto has quit IRC10:07
*** cheng1 has quit IRC10:08
openstackgerritMerged openstack/networking-ovn master: Switch released jobs to OVS 2.11  https://review.openstack.org/64080010:14
*** salmankhan has joined #openstack-neutron10:20
*** davidsha has joined #openstack-neutron10:21
*** markvoelker has quit IRC10:22
*** luksky has quit IRC10:22
*** yamamoto has joined #openstack-neutron10:42
*** macza has joined #openstack-neutron10:51
*** macza has quit IRC10:55
*** br7k has joined #openstack-neutron10:56
*** cheng1 has joined #openstack-neutron10:56
*** br7k has quit IRC11:00
*** luksky has joined #openstack-neutron11:02
*** cheng1 has quit IRC11:05
openstackgerritYAMAMOTO Takashi proposed openstack/networking-midonet master: TEST FOR CI DO NOT REVIEW  https://review.openstack.org/19938711:07
openstackgerritYAMAMOTO Takashi proposed openstack/networking-midonet master: DNM Testing legacy jobs on bionic  https://review.openstack.org/63999011:08
openstackgerritLIU Yulong proposed openstack/neutron master: More accurate agent restart state transfer  https://review.openstack.org/64079711:17
*** markvoelker has joined #openstack-neutron11:19
*** janki has quit IRC11:22
slaweqdalvarez: ajo: hi, can You maybe take a look at https://bugs.launchpad.net/networking-ovn/+bug/1818626 when You will have some time?11:27
openstackLaunchpad bug 1818626 in networking-ovn "Functional python 3.5 job is failing on Ubuntu Bionic" [Undecided,New]11:27
slaweqit's not urgent yet but please keep in mind that there is such issue :)11:27
slaweqthx in advance11:27
dalvarezlucasagomes: ^11:29
*** sapd1 has quit IRC11:29
* lucasagomes looks11:29
lucasagomesdalvarez, slaweq oh yeah... we are currently looking for the 3.5 version of Python, perhaps that's not needed ? I mean we can run functional tests with "python3" (be it 3.5, 3.6, 3.7)11:32
* lucasagomes check how other projects are handling it11:32
openstackgerritSlawek Kaplonski proposed openstack/neutron master: Migrate neutron-functional job to zuul v3 syntax  https://review.openstack.org/61974211:43
slaweqlucasagomes: yes, that would be the best option IMO11:45
openstackgerritLucas Alvares Gomes proposed openstack/networking-ovn master: Switch default functional tests to Python3  https://review.openstack.org/64098811:45
lucasagomesslaweq, ^ I will rebase ur testing patch on top of it11:45
slaweqlucasagomes: thx a lot :)11:46
openstackgerritLucas Alvares Gomes proposed openstack/networking-ovn master: DNM Testing legacy jobs on bionic  https://review.openstack.org/63967311:46
* lucasagomes took a note to convert the functional to native zuul11:46
dalvarezlucasagomes++ :)11:46
*** cheng1 has joined #openstack-neutron11:46
*** markvoelker has quit IRC11:51
*** cheng1 has quit IRC11:54
*** diliprenkila has joined #openstack-neutron11:57
*** br7k has joined #openstack-neutron12:04
diliprenkilaHi all, I am running neutron-server on neutron-server (14.0.0.0b1) and neutron-dhcp-agent (14.0.0.0b1) and still they aren't using same rpc version. It seems strange to me. Here is the detailed log https://etherpad.openstack.org/p/5yZ756ncTC12:04
*** br7k has quit IRC12:08
*** ratailor has quit IRC12:13
*** ociuhandu has quit IRC12:14
*** mmethot has quit IRC12:15
*** awalende has quit IRC12:15
*** awalende has joined #openstack-neutron12:16
*** dave-mccowan has joined #openstack-neutron12:19
openstackgerritJavier Peña proposed openstack/networking-sfc master: Fix unit tests on latest neutron  https://review.openstack.org/64099912:31
*** jpena is now known as jpena|lunch12:31
*** boden has joined #openstack-neutron12:32
*** sm806 has quit IRC12:33
*** sm806 has joined #openstack-neutron12:34
*** cshen has quit IRC12:35
*** zhanglong has joined #openstack-neutron12:36
*** cshen has joined #openstack-neutron12:39
*** cheng1 has joined #openstack-neutron12:40
*** mriedem has joined #openstack-neutron12:41
*** yamamoto has quit IRC12:44
fricklerdiliprenkila: check your versions of neutron-lib, iiuc the rpc version is defined there12:44
*** yamamoto has joined #openstack-neutron12:46
*** tosky has joined #openstack-neutron12:48
*** markvoelker has joined #openstack-neutron12:49
*** yamamoto has quit IRC12:52
*** zhanglong has quit IRC12:57
*** yamamoto has joined #openstack-neutron12:58
diliprenkilafrickler: where can i find versions in neutron-lib ?13:00
*** njohnston has joined #openstack-neutron13:01
*** mchlumsky has joined #openstack-neutron13:01
*** mmichelson has joined #openstack-neutron13:03
*** panda|ruck|flu is now known as panda|ruck|lunch13:03
fricklerdiliprenkila: depends on how you installed things, either something like the python-neutron-lib pkg e.g. for UCA or check the output of "pip freeze"13:08
*** yamamoto has quit IRC13:14
*** janki has joined #openstack-neutron13:17
*** cheng1_ has joined #openstack-neutron13:19
*** markvoelker has quit IRC13:21
*** cheng1 has quit IRC13:22
bodenfrickler what are you guys looking for? rpc versioning?13:24
*** br7k has joined #openstack-neutron13:24
*** zhanglong has joined #openstack-neutron13:28
*** br7k has quit IRC13:28
diliprenkilaboden: we are loooking for rpc versioning13:28
bodendiliprenkila I'm no expert, but thought that was defined in the rpc Target creation as per https://github.com/openstack/oslo.messaging/blob/master/oslo_messaging/target.py#L52.  so for neutron that would be something like http://codesearch.openstack.org/?q=%5C.Target%5C(&i=nope&files=.py&repos=neutron13:30
diliprenkilaboden: i have same version of python-neutron-lib on neutron-server and neutron-agents Installed: 1.20.0-0ubuntu1~cloud013:30
bodenbut maybe I'm wrong13:30
*** sm806 has quit IRC13:31
*** sm806 has joined #openstack-neutron13:32
*** oanson has joined #openstack-neutron13:36
*** ivve has joined #openstack-neutron13:38
*** jpena|lunch is now known as jpena13:40
*** diliprenkila has quit IRC13:41
openstackgerritSlawek Kaplonski proposed openstack/neutron master: Fix handling no qos_queues while removing min bw limit rule  https://review.openstack.org/64087413:42
*** sapd1 has joined #openstack-neutron13:43
*** sapd1 has quit IRC13:47
f0oboden: hi, had any chance to look at that bug report from me?13:50
f0oboden: or know any pointers in debugging this>13:50
*** panda|ruck|lunch is now known as panda|ruck|flu13:50
bodenf0o I asked the plugin team to look... I think they will get to it in the next few days13:50
*** mchlumsky has quit IRC13:51
f0oawesome thanks :)13:52
*** mchlumsky has joined #openstack-neutron13:53
*** yamamoto has joined #openstack-neutron13:53
*** ratailor has joined #openstack-neutron13:56
*** cheng1_ has quit IRC13:58
*** yamamoto_ has joined #openstack-neutron14:01
*** yamamoto has quit IRC14:03
*** mmethot has joined #openstack-neutron14:05
haleybslaweq: can you take a look at https://review.openstack.org/#/c/623066/ ?14:08
*** janki has quit IRC14:12
*** janki has joined #openstack-neutron14:12
*** dklyle has joined #openstack-neutron14:13
*** sapd1 has joined #openstack-neutron14:18
*** markvoelker has joined #openstack-neutron14:18
*** zhanglong has quit IRC14:19
*** lemko has quit IRC14:22
slaweqhaleyb: looking14:23
slaweqhaleyb: +214:31
haleybslaweq: thanks!14:31
*** goldyfruit has joined #openstack-neutron14:39
goldyfruitHi guys14:42
goldyfruitI would like to know if there is a side effect of having a big value for agent_boot_time parameter ?14:44
goldyfruitWe are facing flows issue with DVR and increasing agent_boot_time solved our issue14:44
goldyfruitMore information about it: https://bugs.launchpad.net/neutron/+bug/179499114:44
openstackLaunchpad bug 1794991 in neutron "Inconsistent flows with DVR l2pop VxLAN on br-tun" [Undecided,New] - Assigned to Bruca Lock (lockshi)14:44
*** hongbin has joined #openstack-neutron14:47
*** njohnston has quit IRC14:50
*** njohnston has joined #openstack-neutron14:50
*** markvoelker has quit IRC14:52
*** pcaruana has quit IRC14:57
*** munimeha1 has joined #openstack-neutron14:59
*** awalende has quit IRC14:59
*** ratailor has quit IRC15:00
*** awalende has joined #openstack-neutron15:00
*** lajoskatona has quit IRC15:00
*** cheng1 has joined #openstack-neutron15:01
*** Luzi has quit IRC15:02
*** tbachman has joined #openstack-neutron15:02
*** awalende has quit IRC15:04
openstackgerritSlawek Kaplonski proposed openstack/neutron-fwaas master: Add new upgrade check  https://review.openstack.org/63720315:04
*** tbachman_ has joined #openstack-neutron15:05
*** tbachman has quit IRC15:07
*** tbachman_ is now known as tbachman15:07
*** hamdyk has quit IRC15:16
openstackgerritBence Romsics proposed openstack/neutron master: Fail placement sync if _get_rp_by_name() fails  https://review.openstack.org/64103415:22
*** sapd1 has quit IRC15:25
*** mlavalle has joined #openstack-neutron15:25
openstackgerritNate Johnston proposed openstack/networking-bagpipe master: Run pep8 tests under python 3  https://review.openstack.org/64104115:27
*** tbachman has quit IRC15:28
*** openstackgerrit has quit IRC15:28
*** openstackgerrit has joined #openstack-neutron15:32
openstackgerritRoman Safronov proposed openstack/neutron-tempest-plugin master: Add logging of the test steps in NetworkWritableMtuTest  https://review.openstack.org/64082115:32
*** gcheresh_ has quit IRC15:36
bcafarelralonsoh: slaweq: https://review.openstack.org/#/c/640999/ I guess now we can assume OVSAgentBridge to always have 3 parameters now? (in master)15:38
bcafarelnot sure if other stadium projects got impacted by it15:38
slaweqbcafarel: yes15:39
*** sm806 has quit IRC15:39
*** sm806 has joined #openstack-neutron15:40
haleybgoldyfruit: so when you increased agent_boot_time your flows/fdb were always correctly populated?15:40
ralonsohbcafarel, slaweq: you are right, we should not change this API15:40
slaweqralonsoh: or at least check stadium projects which are impacted :/15:41
ralonsohbcafarel, slaweq: I think I should propose a change to make the third parameter a kwarg15:41
ralonsohslaweq, I'll check it now15:41
slaweqralonsoh: http://codesearch.openstack.org/?q=OVSAgentExtensionAPI&i=nope&files=&repos=15:41
openstackgerritMerged openstack/neutron master: Delete port binding level for deleted bindings  https://review.openstack.org/63427615:41
*** cshen has quit IRC15:41
slaweqit looks that also bagpipe and fwaas may be broken because of that15:41
*** pcaruana has joined #openstack-neutron15:42
ralonsohslaweq, fwaas is only mocking it, but bagpipe will need this new parameter15:42
slaweqyes, right :)15:43
slaweqI just looked quickly to projects in which it was found :)15:43
bcafarelhe, was doing the same in another tab :) (and same conclusion)15:43
bcafarelfwaas periodic passed, bagpipe http://logs.openstack.org/periodic/git.openstack.org/openstack/networking-bagpipe/master/openstack-tox-py35-with-neutron-lib-master/e8aa898/testr_results.html.gz15:44
*** alisanhaji has joined #openstack-neutron15:44
openstackgerritLIU Yulong proposed openstack/neutron master: More accurate agent restart state transfer  https://review.openstack.org/64079715:45
openstackgerritKailun Qin proposed openstack/neutron master: [doc] Add network segment ranges into admin guide  https://review.openstack.org/63911015:45
ralonsohbcafarel, slaweq: IMO, we should make this parameter optional15:45
ralonsohbcafarel, slaweq: only qos is using it by calling request_phy_brs()15:46
slaweqralonsoh: yes, that's IMO good idea15:46
* bcafarel reads the original review15:46
*** armax has joined #openstack-neutron15:46
ralonsohslaweq, perfect, thanks!15:46
openstackgerritMerged openstack/networking-ovn master: Run TripleO scenario003 in gate pipeline  https://review.openstack.org/63842215:47
*** markvoelker has joined #openstack-neutron15:48
*** ksambor has quit IRC15:49
bcafarelralonsoh: sounds great :)15:49
openstackgerritNate Johnston proposed openstack/networking-bagpipe master: Migrate bagpipe legacy tempest jobs to zuulv3 and py3  https://review.openstack.org/64105715:50
liuyulonghttps://bugs.launchpad.net/neutron/+bug/181861415:51
openstackLaunchpad bug 1818614 in neutron "Various L3HA functional tests fails often" [Critical,Confirmed]15:51
liuyulonghttps://bugs.launchpad.net/neutron/+bug/181861315:51
openstackLaunchpad bug 1818613 in neutron "Functional qos tests fails often" [Critical,Confirmed]15:51
liuyulongslaweq, I also noticed such issue. IMO, we can mark them as duplicated.15:51
liuyulonghttp://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%20%5C%22line%20690%2C%20in%20wait_until_true%5C%2215:52
openstackgerritDoug Wiegley proposed openstack/networking-sfc master: DNM: ci test  https://review.openstack.org/64105815:52
slaweqliuyulong: hi15:52
liuyulongThe issue was seen since 2019-2-25.15:52
slaweqliuyulong: yes, those are I think duplicates of https://bugs.launchpad.net/neutron/+bug/1818614  and https://bugs.launchpad.net/neutron/+bug/181861315:52
openstackLaunchpad bug 1818614 in neutron "Various L3HA functional tests fails often" [Critical,Confirmed]15:52
*** sri_ has quit IRC15:52
openstackLaunchpad bug 1818613 in neutron "Functional qos tests fails often" [Critical,Confirmed]15:52
*** rubasov has quit IRC15:52
slaweqahh, sorry15:53
slaweqYou pasted those already :)15:53
slaweqif You already reported those issues before, please mark one of them as duplicate of the other and will be fine15:53
liuyulongslaweq, yes, problem are all from that "  File "neutron/common/utils.py", line 690, in wait_until_true"15:53
liuyulongNo, I just checked the LP bug you filed there.15:54
dougwigis someone actively working on them?15:54
slaweqliuyulong: so what duplicates You are then talking about?15:54
slaweqdougwig: are You asking about those 2 functional tests issues?15:54
dougwigyeah, and a similar looking issue with fullstack.15:55
slaweqdougwig: I don't think there is anyone working on them already15:55
liuyulongdougwig, no, I can indeed reproduce it with low problities.15:55
slaweqI have them on list to discuss on CI meeting in few minutes15:55
liuyulongslaweq,  problem are all from that "  File "neutron/common/utils.py", line 690, in wait_until_true"15:55
liuyulongslaweq, this the main reason why I think they are duplicated.15:56
slaweqliuyulong: this is only helper which checks some condition15:56
slaweqthose 2 issues are different15:56
slaweqone is related to l3ha routers and second to ovs and min bw limit qos rules15:56
slaweqliuyulong: You should check what is the predicate given as argument to wait_until_true() there15:57
dougwigliuyulong: that's a generic function that waits from something to be done.  in the case of races or deadlocks, it'd be a common wait point. that doesn't necessarily make them related.15:57
dougwigslaweq: ok, let me add some elastic recheck queries for them, since we're hitting them so often.15:57
slaweqdougwig: sure, thx15:58
slaweqwe are hitting them a lot recently15:58
liuyulongthe root cause may be related to the OVS mechanism, IMO, l3 also needs L2 functionalites.15:59
slaweqliuyulong: but in case of those L3 failures it's always waiting for router to be master15:59
slaweqit's functional tests, so there is no L2 agent involved in that16:00
slaweqI guess it's some issue with keepalived16:00
slaweqbut I may be wrong16:00
*** tbachman has joined #openstack-neutron16:00
openstackgerritRodolfo Alonso Hernandez proposed openstack/neutron master: Make "phys_brs" argument in OVSAgentExtensionAPI optional  https://review.openstack.org/64106416:01
liuyulongLet's make bold assumptions, verify them carefully.16:01
*** cheng1 has quit IRC16:01
liuyulongI will paste some issues I met.16:02
*** mosulica has quit IRC16:07
*** wwriverrat has quit IRC16:08
openstackgerritboden proposed openstack/neutron master: remove neutron.db.api references  https://review.openstack.org/63328316:15
*** wwriverrat_ has joined #openstack-neutron16:17
liuyulonghttp://logs.openstack.org/47/638647/7/check/neutron-functional/ce2f9fd/logs/testr_results.html.gz, this is the mainly issue I met recently. I can reproduce these failure locally with 10-20% probability.16:17
*** markvoelker has quit IRC16:22
bodenmlavalle ping if you get a min... no rush at all16:22
mlavalleboden: after the ci meeting16:23
bodencool16:23
*** liuyulong is now known as liuyulong_zzz16:27
dougwigslaweq: looking through all the various bugs and failures, the common element is applying some kind of feature change to a port and waiting for it to complete (ha, qos, etc.)16:33
dougwighave we had any port related changes in that area in the last bit?16:34
slaweqdougwig: ha is applied not to port but to the router16:34
dougwigrouter, or the router's ports?16:34
dougwigmaybe it's higher level, then.  we do something, expect a change, and never get it.16:35
*** imacdonn has quit IRC16:35
dougwigor they're all just separate and new.16:36
*** imacdonn has joined #openstack-neutron16:36
dougwigbut they all have a similar feel.16:36
*** janki has quit IRC16:41
slaweqdougwig: router16:41
*** luksky has quit IRC16:41
*** ramishra has quit IRC16:41
*** janki has joined #openstack-neutron16:41
slaweqdougwig: can You maybe join openstack-meeting channel? We are discussing about it now16:41
*** rubasov has joined #openstack-neutron16:41
*** tssurya has quit IRC16:45
*** jpena is now known as jpena|brb16:46
openstackgerritDoug Wiegley proposed openstack/networking-sfc master: DNM: ci test  https://review.openstack.org/64105816:48
*** br7k has joined #openstack-neutron16:48
*** ivve has quit IRC16:58
*** macza has joined #openstack-neutron16:58
*** davidsha has quit IRC17:00
slaweqnjohnston: what You wanted to talk about?17:00
njohnstonOK, the one item I wanted to talk about in the neutron-ci meeting is this:17:00
*** wolverineav has joined #openstack-neutron17:00
njohnstonNow that tripleo has shifted to use OVN by default, I think we should make the networking-ovn-tempest-dsvm-ovs-release job voting so our changes do not break them.  I pushed up a change to that effect: https://review.openstack.org/#/c/640812/17:00
njohnstonThe main issue I see is that the failures for the OVN job are high enough to be of concern.  We would need to get those down before we make it voting.  See http://grafana.openstack.org/d/Hj5IHcSmz/neutron-failure-rate?panelId=26&fullscreen&orgId=117:00
njohnstonBut once we do that I wanted to see if there were any objections to moving that job to voting/gating?17:01
slaweqyes, I was thinking about it today even as I saw Your patch17:01
slaweqand I think that we should first try to lower failure rate a bit first17:01
dougwig+117:01
dougwigfirst, we have to stop the bleeding.  :)17:02
slaweqand also this is question to mlavalle - how he see it, in Denver we agreed to add non-voting jobs from stadium17:02
njohnstonYes, I just wanted to raise the change to make sure there were not any concerns except those related to failure rate17:02
slaweqbut IMO for networking-ovn there is no big risk that project will not have community which will fix potential issues17:02
dougwigwhat's our long-term primary plugin going to be?  linuxbridge, ovs, ovn, or other?17:03
slaweqso I'm ok to switch it to be voting job once it will be more stable17:03
slaweqdougwig: that's good question ;)17:03
slaweqdougwig: for now I think it's ovs still (at least for upstream)17:03
slaweqdougwig: but e.g. in TripleO default now is ovn :)17:03
mlavalleyes and we can have a conversation on this in Denver17:04
*** macza_ has joined #openstack-neutron17:04
slaweqmlavalle: sounds good17:04
*** wolverineav has quit IRC17:04
slaweqnjohnston: I think that for now we should focus on stabilizing this job a bit17:04
njohnstonOK, I will leave the proposed change up but I will leave the -W on it17:05
slaweqwill You have some time to take a look at failures and maybe check if there is something what we (or ovn) team can fix?17:05
dougwigi agree. but getting long-term clarity on the bigger plugin picture will also make this an easy decision, as to how many resources we need to devote to it.17:05
slaweqdougwig: default for neutron is now ovs and I think that will not change soon17:06
*** br7k has quit IRC17:06
mlavalleyes17:06
slaweqthat's from U/S perspective :)17:06
dougwigi bring it up because we also support linuxbridge (and a lot of operators like lb), and i'm wondering if ovn is moving in the same direction.17:07
slaweqtbh from what is in u/s I think that linuxbridge isn't developed too much - most of the patches are related to ovs (and sriov sometimes) drivers IMO17:08
*** macza has quit IRC17:08
slaweqlinuxbridge is in kind of "maintenance" mode IMHO - at least it looks like that for me17:08
dougwigmaybe i'm just daydreaming about a set of CI jobs that are just one plugin and one version of python.  :)17:08
slaweqdougwig: yes, You are dreaming :)17:09
dougwigthe maintenance load is high right now.17:09
dougwighaha.17:09
slaweqbut I have that dream too :D17:09
openstackgerritManjeet Singh Bhatia proposed openstack/neutron-tempest-plugin master: add assert to ping test  https://review.openstack.org/64084717:09
slaweqok, I need to go now, sorry guys but my daughers are waiting for me :)17:09
slaweqone last thing I wanted to raise on meeting17:10
slaweqwe have first bug for os-ken: https://storyboard.openstack.org/#!/story/2005142 :)17:10
slaweqit's some issue with pep817:10
slaweqso gate failure in fact17:10
slaweqif someone have some cycles to look at this, would be great :)17:10
slaweqmlavalle: hongbin ^^ :)17:10
mlavalleslaweq: ack17:11
slaweqthx mlavalle17:11
-openstackstatus- NOTICE: Gerrit is being restarted for a configuration change, it will be briefly offline.17:11
slaweqok, see You later17:11
*** jpena|brb is now known as jpena17:12
*** br7k has joined #openstack-neutron17:13
*** armax has quit IRC17:13
openstackgerritElod Illes proposed openstack/networking-odl master: Use latest Oxygen release instead of snapshot  https://review.openstack.org/64108817:14
*** jistr|sick is now known as jistr17:14
openstackgerritsean mooney proposed openstack/neutron master: do not skip ports with unset or invalid ofport  https://review.openstack.org/64025817:16
openstackgerritDoug Wiegley proposed openstack/networking-sfc master: DNM: ci test  https://review.openstack.org/64105817:18
*** br7k has quit IRC17:19
*** markvoelker has joined #openstack-neutron17:19
*** ileixe has quit IRC17:20
*** cshen has joined #openstack-neutron17:21
*** iballou has joined #openstack-neutron17:22
*** yamamoto_ has quit IRC17:22
*** luksky has joined #openstack-neutron17:23
*** yamamoto has joined #openstack-neutron17:24
*** yamamoto has quit IRC17:24
*** yamamoto has joined #openstack-neutron17:25
*** cshen has quit IRC17:26
*** rkukura has quit IRC17:27
*** panda|ruck|flu is now known as panda|ruck|off17:27
*** yamamoto has quit IRC17:29
*** sridharg has quit IRC17:29
*** aojea has quit IRC17:34
*** itlinux has joined #openstack-neutron17:35
openstackgerritNate Johnston proposed openstack/neutron-fwaas master: Migrate to stestr as unit tests runner  https://review.openstack.org/50552617:42
*** tbachman has quit IRC17:44
*** tbachman has joined #openstack-neutron17:44
openstackgerritVivekanandan Narasimhan proposed openstack/networking-odl master: Re-enable support for multiple router-associations to a single bgpvpn for opendaylight  https://review.openstack.org/61443117:48
*** br7k has joined #openstack-neutron17:49
goldyfruithaleyb: yes !17:51
*** rkukura has joined #openstack-neutron17:51
*** markvoelker has quit IRC17:51
*** rpittau is now known as rpittau|afk17:52
*** br7k has quit IRC17:54
openstackgerritboden proposed openstack/neutron master: use payloads for ROUTER_GATEWAY events  https://review.openstack.org/63827417:56
*** br7k has joined #openstack-neutron17:58
sean-k-mooneyotherwiseguy: o/18:00
sean-k-mooneyregarding https://review.openstack.org/#/c/64025818:01
sean-k-mooneyif you add a port to ovs that does not yet exist the ovs-db allowcation will success because we use --no-wait and the ovs-vswithd will rais a dataplane error resulting in -1 for the ofport in the ovsdb untill the corresponding kernel netdev is created18:02
sean-k-mooneyat which point an ofport will be assigned to the port when it is attached to the dataplane18:03
sean-k-mooneythis is then updated in the ovsdb and is detected by the ovs monior18:03
otherwiseguysean-k-mooney: that's really odd. just posted me doing a killall ovs-vswitchd and --nowait port add and it shows [] as ofport (which is what I remember it always doing).18:06
sean-k-mooneyotherwiseguy: try this18:07
sean-k-mooneyubuntu@os-vif-1:/opt/repos/nova$ sudo ovs-vsctl add-br test18:07
sean-k-mooneyubuntu@os-vif-1:/opt/repos/nova$ sudo ovs-vsctl --no-wait add-port test fake-port18:07
sean-k-mooneyubuntu@os-vif-1:/opt/repos/nova$ sudo ovs-vsctl list interface fake-port18:07
sean-k-mooneyit will result in the ofport being -118:07
otherwiseguyofport is has min:0 max:1 which basically means a nullable integer.18:07
otherwiseguythat's because that is an error, though. w/o type=internal, that actually fails to add the port if ovs-vswitchd is up, right?18:08
sean-k-mooneyyes18:09
sean-k-mooneywe are addign the port before it exisit so we expect it the dataplane to rais that error and set the ofport to -118:09
otherwiseguyI mean, it's recoverable if you set stuff up right later, but the neutron code has always relied on the interface actually existing. it goes to a lot of trouble to ignore the port until vswitchd is done plugging it in (if I remember correctly because it tries to do ip commands on it very quickly)18:11
sean-k-mooneyotherwiseguy: this is what actully happens http://paste.openstack.org/show/747300/18:11
*** br7k has quit IRC18:11
sean-k-mooneyotherwiseguy: nova allway plugs the interface before the vm is created18:11
otherwiseguyand non-vm ports?18:12
sean-k-mooneyin the hybrid plug case we create a veth pair that is added to the bridge in non hybridge plug libvirt adds teh port only when it created the tap18:12
sean-k-mooneyotherwiseguy: nova does not create non vm ports so i assume the l3 and dhcp aggents create the veth pair or us ovs internal ports18:13
otherwiseguysean-k-mooney: right, but if we remove the check_ofport, what is to keep them from running ip commands *before* the interfaces exist?18:15
otherwiseguyand failing18:15
* otherwiseguy looks for the wait code18:15
sean-k-mooneyotherwiseguy: im putting in a check to prevent the call to the security group agent when ofport is -1 or []18:15
sean-k-mooneyso when the ovs monitor detect the ofport change it triggers the addtion of the port to the updated list that is passed tread_device_added_or_updated18:17
sean-k-mooneyonsec ill get a link18:17
otherwiseguysean-k-mooney: Ok, I see that the check_ofport method is now separate from the _ovsdb_retry that was added.18:18
otherwiseguywhich just checks on result == []18:18
sean-k-mooneysorry its this line that wires it up https://github.com/openstack/neutron/blob/master/neutron/plugins/ml2/drivers/openvswitch/agent/ovs_neutron_agent.py#L180118:19
otherwiseguyso since _check_ofport isn't part of the retrying/waiting behavior, I'm less worried anyway. :D18:19
sean-k-mooneyhe i basically moved the check to here https://review.openstack.org/#/c/640258/5/neutron/agent/securitygroups_rpc.py@15718:20
sean-k-mooneyif port and (not port.ofport or port.ofport == -1):18:20
sean-k-mooney                    continue18:20
mlavalleslaweq: I read the channel logs with the rubasov feedback. So we are in syncg18:20
sean-k-mooneythat will skip calling the iptables or openflow firewall dirver if the ofport has not been set18:21
sean-k-mooneythe next time process_network_ports is called after the netdev is added the firewall rules will be installed18:21
mlavallerubasov: while we want to merge the networking guide chapter aap, no har deadline there18:21
*** njohnston has quit IRC18:24
*** salmankhan has quit IRC18:26
*** jamesdenton has quit IRC18:27
*** jamesdenton has joined #openstack-neutron18:29
*** ccamposr__ has quit IRC18:31
sean-k-mooneyotherwiseguy: i updated the patch with more context and ill work on moving the check into the firwall driver instead. if you have any other suggestions let me know18:32
*** jpena is now known as jpena|off18:33
*** mriedem has quit IRC18:37
*** wolverineav has joined #openstack-neutron18:38
*** mriedem has joined #openstack-neutron18:39
openstackgerritboden proposed openstack/neutron master: use callback payloads for AGENT OVS_RESTARTED events  https://review.openstack.org/63642118:40
*** itlinux has quit IRC18:42
*** br7k has joined #openstack-neutron18:46
*** itlinux has joined #openstack-neutron18:47
*** markvoelker has joined #openstack-neutron18:48
eandersson> Timeout in RPC method dhcp_ready_on_ports. Waiting for 48 seconds before next attempt. If the server is not down, consider increasing the rpc_response_timeout option as Neutron server(s) may be overloaded and unable to respond quickly enough.18:51
eanderssonWe are seeing this extensively after upgrading to Rocky. We thought it was due to cpu load at first, but after getting the load down. We are still seeing it frequently.18:51
eanderssonWhere are these requests originating from?18:53
dougwighow many rpc_workers do you have running?18:54
*** yamamoto has joined #openstack-neutron18:55
dougwigeandersson: ^^18:55
eandersson20x218:56
eanderssonand 8x2 dhcp threads18:56
dougwigrpc and not api, right?18:56
eandersson16x2 api18:56
dougwigand rabbit isn't getting behind?18:56
eanderssonapi_workers = 1618:57
eanderssonrpc_workers = 2018:57
eanderssonrabbits are almost idle18:57
eanderssonThe only issue we had was a "dhcp-agent" deadlock, but at that point there were 0 messages consumed from the dhcp queues18:58
*** br7k has quit IRC18:58
dougwigwhat's the cpu load on your controllers look like?18:58
dougwigand so you've got 36 or so neutron-server processes running on each controller?18:59
eandersson14-1618:59
eanderssonWe used to have 3618:59
eandersson(with peaks much higher)18:59
dougwigwait, 16+20 should be 36. how can it be fewer?  did you lower those settings?19:00
dougwigare any of the processes dying, due to exceptions or whatever?19:02
eanderssonnova and neutron are both on the same controller in this case19:03
eanderssonno exceptions19:03
dougwigalright, neutron forks one process per defined api and rpc worker, so if the number of those processes don't match what's in your config file for them, that's the first mystery to solve.19:04
eanderssonsorry, I was replying about laod19:04
eanderssonnot the process count on the controller19:04
eanderssonload is at 14-16 now19:04
dougwigoh, 14-16 is the load?19:04
dougwiggotcha.  how many physical cores?19:04
eandersson16 physical (32 with hyperthreading)19:04
eanderssonSo in my opinion the load is perfect at the momenty19:05
dougwigwell, except that rpc processing is starving. :)19:05
dougwighow many hypervisors?19:06
eanderssonbut only dhcp rpcs for some reason?19:07
eandersson~30019:07
*** yamamoto has quit IRC19:07
eanderssonneutron-server has not had a single missed RPC that I can see in the logs.19:08
eanderssonOther agents are also not complaning19:09
eanderssonWe can add another neutron controller I guess to verify that it isn't just load related19:09
dougwigthat is super weird.19:10
dougwigif that's easy, it'd at least rule out load.19:10
*** ivve has joined #openstack-neutron19:12
eanderssonWe are gonna try adding another neutron node19:14
dougwigi feel like that last statement could almost be a team slogan. :)19:16
*** hamdyk has joined #openstack-neutron19:16
eanderssonhaha19:17
*** br7k has joined #openstack-neutron19:20
*** markvoelker has quit IRC19:21
*** cshen has joined #openstack-neutron19:23
*** armax has joined #openstack-neutron19:26
*** sm806 has quit IRC19:27
*** cshen has quit IRC19:27
*** sm806 has joined #openstack-neutron19:27
openstackgerritMerged openstack/networking-ovn master: Switch default functional tests to Python3  https://review.openstack.org/64098819:28
*** cshen has joined #openstack-neutron19:30
*** lajoskatona has joined #openstack-neutron19:31
*** cshen has quit IRC19:34
*** wolverineav has quit IRC19:41
*** wolverineav has joined #openstack-neutron19:42
*** wolverineav has quit IRC19:43
*** wolverineav has joined #openstack-neutron19:43
eanderssonWe added two more neutron-servers and unfortunately still seeing the RPC error19:45
*** wolverineav has quit IRC19:45
*** lajoskatona has left #openstack-neutron19:45
*** wolverineav has joined #openstack-neutron19:46
*** wolverineav has quit IRC19:46
*** wolverineav has joined #openstack-neutron19:46
*** dave-mccowan has quit IRC19:55
eanderssonWe are seeing the following line (when debug is enabled) being super spammy19:55
eandersson> Checking segment: NetworkSegment19:55
*** ceryx has joined #openstack-neutron19:55
eanderssono/ ceryx19:55
ceryxhi!19:55
*** itlinux has quit IRC19:56
eanderssonWith 4 neutron-servers servers we are seeing 44128 checking segment requests over 10 minutes on a single control node.19:57
eanderssonIs there any way we can reduce those?19:58
eanderssonnvm we have only had deubg on for 5 minutes, so it's much higher than that19:58
eandersson11k per minute (times 4)19:59
*** dave-mccowan has joined #openstack-neutron20:02
mlavalleboden: ping20:05
bodenmlavalle howdy20:05
mlavalleboden: sorry, got derailed earlier20:05
bodenmlavalle np... so we discussed targetting some consumption patches.. there are a few that are low hanging fruit20:07
bodenthey have no dependencies20:07
bodenhttps://review.openstack.org/#/c/633283/  https://review.openstack.org/#/c/637004/  https://review.openstack.org/#/c/637304/20:08
bodenthere are some others, but I'm getting them up to date now20:08
*** itlinux has joined #openstack-neutron20:08
mlavalleboden: at first glance, these 3 look fine. I'll take a look at them today20:09
bodenthanks20:09
openstackgerritHamdy Khader proposed openstack/neutron master: Add Smart NIC representor port to integration bridge  https://review.openstack.org/58625220:13
*** goldyfruit has quit IRC20:14
*** itlinux has quit IRC20:15
*** markvoelker has joined #openstack-neutron20:19
*** iballou has quit IRC20:19
*** br7k has quit IRC20:20
*** br7k has joined #openstack-neutron20:21
openstackgerritRodolfo Alonso Hernandez proposed openstack/neutron master: [WIP] Add a more robust method to check OVSDB values in BaseOVSTestCase  https://review.openstack.org/64111720:24
*** br7k has quit IRC20:25
openstackgerritBrian Haley proposed openstack/neutron master: Fix some pylint E128 warnings  https://review.openstack.org/64111920:27
eanderssonAnyone know what would be making check_segment_for_agent (ml2 mech_agent) calls?20:27
eanderssonTrying to figure out who is sending all these rpc requests.20:27
*** igordc has joined #openstack-neutron20:28
*** ralonsoh has quit IRC20:29
*** wolverineav has quit IRC20:31
*** wolverineav has joined #openstack-neutron20:32
slaweqmlavalle: thx for checking channel logs for info from rubasov :) CI meeting was really long today and I later totally forgot about it20:36
*** wolverineav has quit IRC20:37
*** mmichelson has quit IRC20:37
mlavalleslaweq: no problem, daughters have priority much higher than the stupid PTL. I know my place ;-)20:37
slaweqmlavalle: LOL20:37
slaweqI never though about it this way :)20:37
openstackgerritNate Johnston proposed openstack/os-ken master: Fix pep8 errors in os-ken  https://review.openstack.org/64112220:39
mlavalleslaweq: well, that's the way it is. don't even doubt it if you don't want to be slapped by wife20:42
*** br7k has joined #openstack-neutron20:43
slaweqmlavalle: LOL, fortunatelly my wife can't use irc :P20:43
slaweqso she will not read this :D20:43
*** br7k has quit IRC20:47
*** jlibosva has quit IRC20:50
*** markvoelker has quit IRC20:52
dougwigslaweq: looking at that qos patch you posted earlier, at ovs_lib.py, those new methods would very much not enjoy being parallel'ed.  do the fullstack or functional tests run in parallel, against a single OVS ?20:54
*** br7k has joined #openstack-neutron20:55
slaweqdougwig: yes, it runs in parallel generally20:55
slaweqI think that we have 4 workers in gate ci always20:55
slaweqbut each test should work on own bridge/ports20:56
dougwig"should" ?20:56
*** prometheanfire has joined #openstack-neutron20:56
prometheanfirehttp://logs.openstack.org/71/640671/3/check/cross-neutron-py27/0fd85d4/testr_results.html.gz20:56
prometheanfireit looks like updates are causing some issues, I think it's pyroute2/sqlalchemy that are doing it20:57
prometheanfirebut it'd be nice to have another person look as well20:57
prometheanfirehttps://review.openstack.org/640671 is the review20:57
prometheanfiremaybe alembic as well20:58
*** salmankhan has joined #openstack-neutron20:59
slaweqdougwig: IIRC separate bridges are created20:59
slaweqbut I may be wrong or maybe there is some bug in some tests :)20:59
*** wolverineav has joined #openstack-neutron21:02
eanderssonWhat causes >  Provisioning complete for port21:03
eanderssonWe are seeing ~4k per minute21:03
*** pcaruana has quit IRC21:10
*** wolverineav has quit IRC21:11
wwriverrat_Would love to have discussion with anyone willing regarding multi-segment per host support re: http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003467.html21:12
openstackgerritSlawek Kaplonski proposed openstack/neutron master: Store journal log in functional tests results  https://review.openstack.org/64112721:17
dougwigeandersson: i'm guessing that's here: neutron/db/provisioning_blocks.py, which is referenced by dhcp21:18
*** dsneddon has quit IRC21:18
prometheanfireI don't think anyone has done testing with sqlalchemy-1.3.0?21:22
openstackgerritboden proposed openstack/neutron master: use payloads for PORT AFTER_CREATE events  https://review.openstack.org/63446121:26
*** br7k has quit IRC21:27
*** br7k has joined #openstack-neutron21:28
eanderssondougwig, looks related to the DHCP Scheduler21:29
*** wolverineav has joined #openstack-neutron21:29
*** janki has quit IRC21:29
*** cshen has joined #openstack-neutron21:30
eanderssonIs network_auto_schedule required?21:31
*** salmankhan has quit IRC21:32
*** cshen has quit IRC21:34
*** br7k has quit IRC21:34
*** br7k has joined #openstack-neutron21:36
*** numans has quit IRC21:38
*** ivve has quit IRC21:44
*** goldyfruit has joined #openstack-neutron21:45
*** alisanhaji has quit IRC21:46
*** wolverineav has quit IRC21:47
*** br7k has quit IRC21:48
*** wolverineav has joined #openstack-neutron21:48
*** markvoelker has joined #openstack-neutron21:49
*** mchlumsky has quit IRC21:50
*** wolverineav has quit IRC21:53
*** hamdyk has quit IRC21:57
*** goldyfruit has left #openstack-neutron21:58
*** br7k has joined #openstack-neutron22:01
*** br7k has quit IRC22:12
*** wolverineav has joined #openstack-neutron22:12
*** br7k has joined #openstack-neutron22:12
*** br7k has quit IRC22:20
*** markvoelker has quit IRC22:22
mlavalleboden: done with the 3 patches you gave me earlier. Thanks!22:23
bodenmlavalle thanks!22:24
*** br7k has joined #openstack-neutron22:24
*** mvkr has quit IRC22:25
*** boden has quit IRC22:30
*** mmethot has quit IRC22:34
*** sapd1 has joined #openstack-neutron22:36
*** br7k has quit IRC22:39
*** br7k has joined #openstack-neutron22:39
*** wolverineav has quit IRC22:47
*** dsneddon has joined #openstack-neutron22:51
*** munimeha1 has quit IRC22:52
*** tkajinam has joined #openstack-neutron22:54
*** binh_ has quit IRC22:55
*** binh_ has joined #openstack-neutron22:55
*** dsneddon has quit IRC22:56
*** iyamahat has joined #openstack-neutron22:58
*** br7k has quit IRC22:59
*** yamamoto has joined #openstack-neutron23:05
*** iyamahat has quit IRC23:08
*** br7k has joined #openstack-neutron23:09
*** yamamoto has quit IRC23:10
*** igordc has quit IRC23:10
*** br7k has quit IRC23:10
*** dsneddon has joined #openstack-neutron23:10
*** br7k has joined #openstack-neutron23:12
dougwigeandersson: not if you always specify a network for instances.23:14
*** dsneddon has quit IRC23:15
*** br7k has quit IRC23:16
*** markvoelker has joined #openstack-neutron23:19
prometheanfirefor those neutron devs that wish to test with sqlalchemy-1.3.0 I've made a patch to depend on to aid you.  https://review.openstack.org/64115123:20
*** wolverineav has joined #openstack-neutron23:24
*** dsneddon has joined #openstack-neutron23:25
*** wolverineav has quit IRC23:30
*** cshen has joined #openstack-neutron23:30
*** br7k has joined #openstack-neutron23:31
*** cshen has quit IRC23:35
*** br7k has quit IRC23:38
*** wolverineav has joined #openstack-neutron23:38
*** tesseract has quit IRC23:42
*** markvoelker has quit IRC23:52
*** wolverineav has quit IRC23:59
*** wolverineav has joined #openstack-neutron23:59

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