Tuesday, 2019-07-23

*** mattw4 has quit IRC00:00
*** _hemna has joined #openstack-meeting00:05
*** jamesmcarthur has joined #openstack-meeting00:05
*** gyee has quit IRC00:07
*** iyamahat has quit IRC00:14
*** jamesmcarthur has quit IRC00:15
*** Liang__ has joined #openstack-meeting00:50
*** hongbin has joined #openstack-meeting00:55
*** igordc has quit IRC00:55
*** _hemna has quit IRC00:55
*** lhinds has quit IRC00:57
*** eharney has quit IRC00:57
*** lhinds has joined #openstack-meeting00:58
*** TxGirlGeek has joined #openstack-meeting00:58
*** bbowen has quit IRC01:02
*** bbowen has joined #openstack-meeting01:02
*** ayoung has quit IRC01:11
*** enriquetaso has quit IRC01:17
*** ricolin has joined #openstack-meeting01:19
*** jamesmcarthur has joined #openstack-meeting01:24
*** TxGirlGeek has quit IRC01:32
*** jamesmcarthur_ has joined #openstack-meeting01:32
*** jamesmcarthur has quit IRC01:34
*** yamamoto has quit IRC01:34
*** mhen has quit IRC01:41
*** rbudden has joined #openstack-meeting01:42
*** whoami-rajat has joined #openstack-meeting01:43
*** baojg has joined #openstack-meeting01:45
*** _erlon_ has quit IRC01:46
*** TxGirlGeek has joined #openstack-meeting01:50
*** TxGirlGeek has quit IRC01:54
*** tetsuro has joined #openstack-meeting01:58
*** yamamoto has joined #openstack-meeting01:58
*** rbudden has quit IRC01:59
*** tetsuro has quit IRC02:17
*** yamamoto has quit IRC02:17
*** tetsuro has joined #openstack-meeting02:18
*** yamamoto has joined #openstack-meeting02:21
*** jamesmcarthur_ has quit IRC02:35
*** ayoung has joined #openstack-meeting03:14
*** artom has quit IRC03:15
*** psachin has joined #openstack-meeting03:28
*** artom has joined #openstack-meeting03:32
*** iyamahat has joined #openstack-meeting03:44
*** hongbin has quit IRC03:45
*** hongbin has joined #openstack-meeting03:50
*** hongbin has quit IRC03:50
*** dviroel has quit IRC03:52
*** nitinuikey has joined #openstack-meeting03:59
*** imsurit has joined #openstack-meeting04:08
*** tetsuro has quit IRC04:09
*** rcernin has quit IRC04:13
*** rcernin has joined #openstack-meeting04:14
*** rcernin has quit IRC04:20
*** pcaruana has joined #openstack-meeting04:43
*** nitinuikey has quit IRC04:58
*** links has joined #openstack-meeting05:04
*** tetsuro has joined #openstack-meeting05:05
*** Luzi has joined #openstack-meeting05:05
*** jraju__ has joined #openstack-meeting05:08
*** tetsuro has quit IRC05:08
*** links has quit IRC05:09
*** jraju__ has quit IRC05:10
*** TxGirlGeek has joined #openstack-meeting05:16
*** Lucas_Gray has joined #openstack-meeting05:31
*** armax has quit IRC05:34
*** notmyname has quit IRC05:41
*** notmyname has joined #openstack-meeting05:42
*** TxGirlGeek has quit IRC05:43
*** jamesmcarthur has joined #openstack-meeting05:55
*** jamesmcarthur has quit IRC05:56
*** igordc has joined #openstack-meeting06:08
*** dkushwaha has joined #openstack-meeting06:09
*** Lucas_Gray has quit IRC06:09
*** jamesmcarthur has joined #openstack-meeting06:09
*** Lucas_Gray has joined #openstack-meeting06:10
*** jhesketh has quit IRC06:11
*** jhesketh has joined #openstack-meeting06:11
*** jamesmcarthur has quit IRC06:13
*** igordc has quit IRC06:15
*** jamesmcarthur has joined #openstack-meeting06:16
*** apetrich has quit IRC06:20
*** hyunsik_m has quit IRC06:27
*** diablo_rojo has joined #openstack-meeting06:27
*** jamesmcarthur_ has joined #openstack-meeting06:28
*** jamesmca_ has joined #openstack-meeting06:31
*** diablo_rojo has quit IRC06:32
*** jamesmcarthur has quit IRC06:32
*** jamesmcarthur_ has quit IRC06:35
*** jamesmca_ has quit IRC06:38
*** Lucas_Gray has quit IRC06:39
*** e0ne has joined #openstack-meeting06:40
*** e0ne has quit IRC06:41
*** Lucas_Gray has joined #openstack-meeting06:43
*** jamesmcarthur has joined #openstack-meeting06:43
*** ttsiouts has joined #openstack-meeting06:48
*** jamesmcarthur has quit IRC06:51
*** jamesmcarthur has joined #openstack-meeting06:53
*** dkushwaha has quit IRC06:54
*** dmacpher has joined #openstack-meeting06:58
*** yamamoto has quit IRC07:05
*** yamamoto has joined #openstack-meeting07:06
*** Nobuhiko0723 has joined #openstack-meeting07:07
*** slaweq has joined #openstack-meeting07:07
*** tesseract has joined #openstack-meeting07:09
*** imsurit_ofc has joined #openstack-meeting07:10
*** imsurit has quit IRC07:12
*** imsurit_ofc is now known as imsurit07:12
*** hyunsikyang__ has joined #openstack-meeting07:19
*** zbr_ has joined #openstack-meeting07:20
*** irclogbot_0 has quit IRC07:20
*** kaisers has quit IRC07:20
*** kaisers has joined #openstack-meeting07:21
*** irclogbot_2 has joined #openstack-meeting07:21
*** dansmith has quit IRC07:23
*** zbr has quit IRC07:23
*** hyunsikyang has quit IRC07:23
*** dansmith has joined #openstack-meeting07:24
*** jamesmcarthur has quit IRC07:24
*** beagles has quit IRC07:26
*** dkushwaha has joined #openstack-meeting07:28
*** ttsiouts has quit IRC07:42
*** ttsiouts has joined #openstack-meeting07:43
*** ttsiouts has quit IRC07:48
*** bhagyashris has joined #openstack-meeting07:54
*** tpatil has joined #openstack-meeting07:55
*** apetrich has joined #openstack-meeting07:57
*** priteau has joined #openstack-meeting08:00
*** nitinuikey has joined #openstack-meeting08:01
*** joxyuki has joined #openstack-meeting08:03
dkushwaha#startmeeting tacker08:04
openstackMeeting started Tue Jul 23 08:04:22 2019 UTC and is due to finish in 60 minutes.  The chair is dkushwaha. Information about MeetBot at http://wiki.debian.org/MeetBot.08:04
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.08:04
*** openstack changes topic to " (Meeting topic: tacker)"08:04
openstackThe meeting name has been set to 'tacker'08:04
*** nnsingh has joined #openstack-meeting08:04
dkushwaha#topic Roll Call08:05
*** openstack changes topic to "Roll Call (Meeting topic: tacker)"08:05
dkushwahawho is here for Tacker weekly meeting ?08:05
*** shubham_potale has joined #openstack-meeting08:05
nnsinghHi Dharmendra08:05
dkushwahahello all08:06
dkushwahalets start..08:07
dkushwaha#chair joxyuki08:08
openstackCurrent chairs: dkushwaha joxyuki08:08
dkushwaha#topic BP08:08
*** openstack changes topic to "BP (Meeting topic: tacker)"08:08
dkushwahaI have done on  force delete BP from my side08:10
dkushwaha#link https://review.opendev.org/#/c/626854/08:10
dkushwaha#link https://review.opendev.org/#/c/666496/08:10
dkushwahaplease help on review08:11
dkushwahaI have started another BP i.e Connection points auto heal08:12
dkushwaha#link https://blueprints.launchpad.net/tacker/+spec/cp-auto-heal08:12
dkushwahahope to come with initial patch in this week08:12
joxyukiIs scope of this BP respawn action or auto-heal action?08:13
dkushwahajoxyuki, we needs to auto-heal connection point08:14
joxyukiyea, the title mentions auto-heal but in its description you mentions re-spawn. which is target?08:15
tpatilIn VDU auto healing, connection points are recreated08:16
*** takahashi-tsc has joined #openstack-meeting08:17
*** imsurit has quit IRC08:18
tpatil#link : https://github.com/openstack/tacker/blob/master/tacker/vnfm/policy_actions/vdu_autoheal/vdu_autoheal.py#L5108:18
dkushwahajoxyuki, once VNF re-spawned, existing CP couldn't be cleaned, so a new interface get attached, here my approach is to clean existing interface and attached new one with same ip08:18
joxyukigot it, that's nice :)08:19
*** yamamoto has quit IRC08:20
dkushwahatpatil, how it restore existing one ?08:20
tpatildkushwaha: based on Mac address08:20
tpatilin the above code, you will see that heat will delete those hot resources and create a new ones.08:21
dkushwahatpatil, with the same ip. right?08:21
*** ttsiouts has joined #openstack-meeting08:22
dkushwahatpatil, aah, then I needs to recheck/re-define the scope of my BP.08:23
dkushwahatpatil, thanks for input.08:23
dkushwahaother than this, I target to fix this bug, in this week. https://bugs.launchpad.net/tacker/+bug/183350508:25
openstackLaunchpad bug 1833505 in tacker "VNF scale failed for non-admin tenants" [Critical,New] - Assigned to dharmendra (dharmendra-kushwaha)08:25
*** ralonsoh has joined #openstack-meeting08:26
dkushwahathis is all in my TODO for this week.08:27
tpatil# link : https://review.opendev.org/#/c/626854/3/tackerclient/osc/v1/nfvo/ns.py, python-tackerclient is deprecated so is it ok to add new options to the existing commands?08:27
*** asmita_s has joined #openstack-meeting08:28
*** tssurya has joined #openstack-meeting08:28
dkushwahatpatil, I thinks yes, and it it was what we agreed in spec too https://review.opendev.org/#/c/602528/08:29
*** tpatil has quit IRC08:34
*** asmita_s has quit IRC08:34
*** asmita_s has joined #openstack-meeting08:35
*** tpatil has joined #openstack-meeting08:35
tpatilVNF packages support for VNF onboarding08:35
tpatil#link : https://review.opendev.org/#/c/582930/08:36
tpatilTo implement this spec, we need to make several changes to Tosca-parser library to implement tosca definition 1.2 version validation code as a new extension08:36
tpatilwe are planning to propose tosca-parser patch by early next week08:36
tpatilAlso, we will start pushing patches in tacker in first week of August08:37
*** panda has quit IRC08:38
dkushwahatpatil, sounds good08:38
*** panda has joined #openstack-meeting08:38
tpatilThat's all update from my side08:38
dkushwahaOnce we will have some initial code patches, I will merge the spec08:39
tpatildkushwaha: Ok, Thanks08:40
dkushwahamoving next..08:41
dkushwaha#topic Open Discussion08:41
*** openstack changes topic to "Open Discussion (Meeting topic: tacker)"08:41
joxyukiI push a new spec and WIP code patch.08:43
joxyukithis is remaining work of reservation-vnfm08:43
joxyukikindly request you to review them from the spec.08:44
*** asmita_s has quit IRC08:44
*** e0ne has joined #openstack-meeting08:46
dkushwaha joxyuki is this update param_values for reservation part only?08:47
joxyukidkushwaha: no, this feature can be used for more general use cases.08:47
joxyukiall parameterized values can be updated, not only reservation-metadata.08:48
dkushwahajoxyuki, I see.08:49
dkushwahaI will review the spec, don't have any question for now08:50
*** yamamoto has joined #openstack-meeting08:50
dkushwahaDo we have something to talk now? otherwise we can close this meeting.08:53
takahashi-tscSorry for late... and I have a request.08:53
takahashi-tscMy team member said that manual scaling using CLI is failed... Would someone review following bug and patch?08:54
openstackLaunchpad bug 1834548 in python-tackerclient "osc command's scale is failed" [Undecided,New] - Assigned to Hiroya Nakaya (nakkay)08:54
dkushwahatakahashi-tsc, I missed this patch, will review it08:56
takahashi-tscOops, the patch's topic branch is wrong...08:56
takahashi-tscThank you! And I will review patches. Sorry for not doing activities.08:58
dkushwahatakahashi-tsc, np. That will be great if you help on review09:00
*** priteau has quit IRC09:00
dkushwahatime up09:00
joxyukimy presentation at Shanghai. please check it and vote to it if you want.09:00
dkushwahajoxyuki, already voted from my side09:01
dkushwahatime up folks, Closing this meeting09:01
*** Lucas_Gray has quit IRC09:01
dkushwahathanks all for joining09:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"09:02
openstackMeeting ended Tue Jul 23 09:02:05 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)09:02
openstackMinutes:        http://eavesdrop.openstack.org/meetings/tacker/2019/tacker.2019-07-23-08.04.html09:02
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/tacker/2019/tacker.2019-07-23-08.04.txt09:02
openstackLog:            http://eavesdrop.openstack.org/meetings/tacker/2019/tacker.2019-07-23-08.04.log.html09:02
*** nitinuikey has quit IRC09:02
*** priteau has joined #openstack-meeting09:02
*** yamamoto has quit IRC09:02
*** joxyuki has left #openstack-meeting09:03
*** takahashi-tsc has quit IRC09:05
*** tpatil has quit IRC09:08
*** _hemna has joined #openstack-meeting09:12
*** Lucas_Gray has joined #openstack-meeting09:12
*** _hemna has quit IRC09:16
*** Lucas_Gray has quit IRC09:18
*** Liang__ has quit IRC09:19
*** Lucas_Gray has joined #openstack-meeting09:19
*** psachin has quit IRC09:20
*** dkushwaha has quit IRC09:31
*** ociuhandu has joined #openstack-meeting09:31
*** psachin has joined #openstack-meeting09:35
*** apetrich has quit IRC09:36
*** Nobuhiko0723 has quit IRC09:42
*** ociuhandu has quit IRC09:48
*** ociuhandu has joined #openstack-meeting09:50
*** bhagyashris has quit IRC09:54
*** iyamahat has quit IRC10:04
*** ttsiouts has quit IRC10:11
*** ttsiouts has joined #openstack-meeting10:12
*** kopecmartin|off is now known as kopecmartin10:12
*** ttsiouts has quit IRC10:16
*** lpetrut has joined #openstack-meeting10:21
*** brinzhang_ has joined #openstack-meeting10:26
*** yamamoto has joined #openstack-meeting10:27
*** yamamoto has quit IRC10:28
*** yamamoto has joined #openstack-meeting10:28
*** brinzhang has quit IRC10:30
*** ricolin_ has joined #openstack-meeting10:34
*** bbowen has quit IRC10:37
*** ricolin has quit IRC10:37
*** yamamoto has quit IRC10:48
*** apetrich has joined #openstack-meeting10:53
*** Lucas_Gray has quit IRC10:54
*** yamamoto has joined #openstack-meeting10:57
*** yamamoto has quit IRC11:02
*** yamamoto has joined #openstack-meeting11:05
*** jaypipes has joined #openstack-meeting11:14
*** ttsiouts has joined #openstack-meeting11:30
*** raildo has joined #openstack-meeting11:35
*** b3nt_pin has joined #openstack-meeting11:35
*** carloss has joined #openstack-meeting11:47
*** bbowen has joined #openstack-meeting11:55
*** markvoelker has quit IRC11:58
*** eharney has joined #openstack-meeting12:01
*** yamamoto has quit IRC12:03
*** ricolin_ is now known as ricolin12:05
*** yamamoto has joined #openstack-meeting12:08
*** pfallenop has joined #openstack-meeting12:12
*** dviroel has joined #openstack-meeting12:14
*** markvoelker has joined #openstack-meeting12:16
*** ttsiouts has quit IRC12:17
*** ttsiouts has joined #openstack-meeting12:17
*** pfallenop has quit IRC12:20
*** ttsiouts has quit IRC12:22
*** electrofelix has joined #openstack-meeting12:36
*** mriedem has joined #openstack-meeting12:38
*** enriquetaso has joined #openstack-meeting12:57
*** njohnston has joined #openstack-meeting12:59
*** apetrich has quit IRC13:07
*** jamesmcarthur has joined #openstack-meeting13:08
*** ttsiouts has joined #openstack-meeting13:17
*** jamesmcarthur has quit IRC13:18
*** mriedem has quit IRC13:38
*** jamesmcarthur has joined #openstack-meeting13:39
*** Luzi has quit IRC13:51
*** yamamoto has quit IRC13:53
*** ttsiouts has quit IRC13:53
*** yamamoto has joined #openstack-meeting13:54
*** ttsiouts has joined #openstack-meeting13:54
*** lajoskatona has joined #openstack-meeting13:56
*** yamamoto has quit IRC13:58
*** jamesmcarthur has quit IRC13:58
*** ttsiouts has quit IRC13:58
*** ttsiouts has joined #openstack-meeting13:58
*** lbragstad has joined #openstack-meeting14:00
*** tssurya has quit IRC14:13
*** belmoreira has joined #openstack-meeting14:14
*** baojg has quit IRC14:18
*** baojg has joined #openstack-meeting14:19
*** gyee has joined #openstack-meeting14:23
*** apetrich has joined #openstack-meeting14:26
*** mriedem has joined #openstack-meeting14:36
*** yamamoto has joined #openstack-meeting14:37
*** lbragstad has quit IRC14:40
*** dosaboy has joined #openstack-meeting14:41
*** lbragstad has joined #openstack-meeting14:43
*** yamamoto has quit IRC14:43
*** _hemna has joined #openstack-meeting14:47
*** _hemna has quit IRC14:52
*** TxGirlGeek has joined #openstack-meeting14:52
*** armax has joined #openstack-meeting15:05
*** lseki has joined #openstack-meeting15:06
*** lajoskatona has left #openstack-meeting15:08
*** pfallenop has joined #openstack-meeting15:09
*** enriquetaso has quit IRC15:09
*** enriquetaso has joined #openstack-meeting15:09
*** enriquetaso has quit IRC15:14
*** pfallenop has quit IRC15:16
*** trident has quit IRC15:18
*** belmoreira has quit IRC15:18
*** _hemna has joined #openstack-meeting15:18
*** trident has joined #openstack-meeting15:20
*** dmacpher has quit IRC15:23
*** e0ne has quit IRC15:39
*** david-lyle is now known as dklyle15:40
*** zaneb has quit IRC15:43
*** trident has quit IRC15:52
*** _hemna has quit IRC15:53
*** ttsiouts has quit IRC15:54
*** ttsiouts has joined #openstack-meeting15:55
*** trident has joined #openstack-meeting15:55
*** ttsiouts_ has joined #openstack-meeting15:57
*** ttsiouts has quit IRC15:57
*** mlavalle has joined #openstack-meeting15:59
*** ttsiouts_ has quit IRC15:59
slaweq#startmeeting neutron_ci16:00
openstackMeeting started Tue Jul 23 16:00:26 2019 UTC and is due to finish in 60 minutes.  The chair is slaweq. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
*** openstack changes topic to " (Meeting topic: neutron_ci)"16:00
openstackThe meeting name has been set to 'neutron_ci'16:00
*** e0ne has joined #openstack-meeting16:01
slaweqI know that njohnston is quite busy with internal stuff now, haleyb and bcafarel are on PTO16:02
slaweqso lets start16:02
slaweqfirst of all:16:02
slaweq#link http://grafana.openstack.org/dashboard/db/neutron-failure-rate16:02
slaweqand now lets go16:02
slaweq#topic Actions from previous meetings16:02
*** openstack changes topic to "Actions from previous meetings (Meeting topic: neutron_ci)"16:02
slaweqfirst one:16:02
slaweqmlavalle to continue debugging neutron-tempest-plugin-dvr-multinode-scenario issues16:02
mlavalleI did, although I changed my approach16:03
mlavallesince the merging of  https://review.opendev.org/#/c/667547/, the frequency of test_connectivity_through_2_routers has decreased significantly16:03
mlavalleit still fails sometimes but many of those failures may be due to the slowness in metadata / nova we discussed yesterday16:04
*** cheng1 has quit IRC16:04
mlavalleso I did an analysis of the failures over the past 7 days of all the tests16:04
mlavalleand came up with a ranking16:05
mlavallePlease see note #5 in16:05
openstackLaunchpad bug 1830763 in neutron "Debug neutron-tempest-plugin-dvr-multinode-scenario failures" [High,Confirmed] - Assigned to Miguel Lavalle (minsel)16:05
mlavalleAs you can see, the biggest offenders are test_qos_basic_and_update and the routers migrations16:06
*** mattw4 has joined #openstack-meeting16:06
mlavalledigging into test_qos_basic_and_update, please read note #616:07
mlavallemost of the failures happen after updating the QoS policy / rule16:07
*** enriquetaso has joined #openstack-meeting16:07
*** tesseract has quit IRC16:07
mlavallein other words, at that point we already have connectivity and the routers / dvr seem to be working fine16:08
slaweqok, so we have couple of different issues there16:08
*** cheng1 has joined #openstack-meeting16:08
slaweqbecause issue with failing to get instance-id from metadata also happens quite often in various tests16:08
*** pfallenop has joined #openstack-meeting16:10
* mlavalle waiting for the rest of the comment16:10
slaweqmlavalle: that's all from my side16:11
ralonsohmlavalle, I would like to see why the qos_check os failing16:11
slaweqI just wanted to say that we have few different issues16:11
ralonsohis failing16:11
ralonsohI'll review the logs16:11
slaweqcan we than report it as 3 different bugs:16:11
slaweq1. already created bug - left it related to ssh and metadata issues,16:12
mlavalleyeah, I wanted someone (really thinking ralonsoh) to check the failures in QoS16:12
slaweq2. qos test issue16:12
slaweq3. router migrations problems16:12
mlavalleI don't think this QoS failure is purely due to dvr16:12
mlavalleit must be the combination16:12
mlavalleso if ralonsoh takes care of that one16:12
ralonsohI can take QoS (2)16:12
mlavalleI will take care of bug 3 as described by slaweq16:12
openstackbug 3 in mono (Ubuntu) "Custom information for each translation team" [Undecided,Fix committed] https://launchpad.net/bugs/316:12
mlavalleralonsoh: would you file bug 2?16:13
slaweqthx guys16:13
slaweqI can take a look once again on the issue with metadata16:14
mlavalleif you do, I'll post there the Kibana search that you need to see all the occurrences16:14
slaweqthis one is IMO clearly related to dvr as I didn't saw it on any other jobs16:14
mlavalleralonsoh: ^^^^16:14
mlavalleok, I achieved what I wanted with my report today16:15
slaweqthx mlavalle for update and for working on this16:15
slaweqmlavalle: will You also report bug 2 as new one?16:16
mlavalleI will16:16
slaweqthx a lot16:16
slaweq#action mlavalle to report bug with router migrations16:16
mlavalleand assign to me16:16
slaweq#action ralonsoh to report bug with qos scenario test failures16:16
slaweq#action slaweq to take a look at issue with dvr and metadata: https://bugs.launchpad.net/neutron/+bug/183076316:17
openstackLaunchpad bug 1830763 in neutron "Debug neutron-tempest-plugin-dvr-multinode-scenario failures" [High,Confirmed] - Assigned to Miguel Lavalle (minsel)16:17
slaweqok, I think we are good here and can move on16:17
slaweqralonsoh to try a patch to resuce the number of workers in FT16:17
ralonsohslaweq, and I didn't have time, sorry16:18
* mlavalle will have to drop off at 30 minutes after the hour16:18
ralonsohmy bad, I'll do this tomorrow morning16:18
ralonsohbut I'll need help, because I really don't know where to modify this16:18
slaweqralonsoh: sure, no problem16:18
ralonsohin the neutron/tox.ini file?16:18
ralonsohin the zuul FT definition?16:19
*** lpetrut has quit IRC16:19
*** iyamahat has joined #openstack-meeting16:19
slaweqralonsoh: I think that it should be defined in tox.ini16:19
slaweqbut I'm not 100% sure now16:19
ralonsohslaweq, that was my initial though16:19
*** enriquetaso has quit IRC16:19
ralonsohI'll try it tomorrow16:19
slaweqok, thx16:20
slaweq#action ralonsoh to try a patch to resuce the number of workers in FT16:20
slaweqso, next one16:20
slaweqralonsoh to report a bug and investigate failed test neutron.tests.fullstack.test_qos.TestMinBwQoSOvs.test_bw_limit_qos_port_removed16:20
ralonsohin my list too, and no time16:20
ralonsohsorry again16:20
ralonsohreally, I dind't have time last week16:21
slaweqralonsoh: no problem at all :)16:22
slaweqit's not very urgent16:22
slaweq#action ralonsoh to report a bug and investigate failed test neutron.tests.fullstack.test_qos.TestMinBwQoSOvs.test_bw_limit_qos_port_removed16:22
slaweqbut please at least report a bug, that we have it tracked16:22
slaweqmaybe someone else will take a look16:23
slaweqok, and last one16:23
slaweqslaweq to open bug about slow neutron-tempest-with-uwsgi job16:23
slaweqI opened bug https://bugs.launchpad.net/neutron/+bug/183755216:23
openstackLaunchpad bug 1837552 in neutron "neutron-tempest-with-uwsgi job finish with timeout very often" [Medium,Confirmed]16:23
slaweqand I wrote there my initial findings16:23
slaweqbasically there is some issue with neutron API IMO but I'm not sure what's going on there exactly16:24
ralonsohslaweq, I saw that most of the time the test failing is the vrrp one16:25
ralonsohlet me find the name16:25
slaweqralonsoh: but in which job?16:25
ralonsohhmmm, not in tempest.... osrry16:26
*** baojg has quit IRC16:26
slaweqin this tempest job, it is like at some point all tests are failing due to timeouts connecting to neutron API16:27
slaweqin apache logs I see HTTP 500 for each request related to neutron16:27
slaweqbut in neutron logs I didn't saw any error16:27
slaweqso I'm a bit confused with that16:27
slaweqif I will have some time, I will try to investigate it16:27
slaweqbut I didn't assign myself to this bug for now, maybe there will be someone else who will wants to look into this16:28
* mlavalle drops off for another meeting o/16:29
slaweqsee You mlavalle16:29
slaweqok, I think we can move on16:29
slaweqnext topic16:29
slaweq#topic Stadium projects16:29
*** openstack changes topic to "Stadium projects (Meeting topic: neutron_ci)"16:29
slaweqPython 3 migration16:29
slaweqStadium projects etherpad: https://etherpad.openstack.org/p/neutron_stadium_python3_status16:29
slaweqI have only short update about this one16:29
slaweqlast job in fwaas repo is switched to zuulv3 and python316:29
slaweqso we are good with this one16:29
slaweqwe still have some work to do in16:30
slaweqnetworking-bagpipe, networking-midonet, networking-odl and python-neutronclient16:30
slaweqand that would be all16:30
slaweqwe have patches or at least volunteers for all of them except midonet16:31
slaweqso I think we are quite good with this16:31
slaweqnext part is:16:31
slaweqtempest-plugins migration16:31
ralonsohslaweq, cool, we still support neutron-client16:31
slaweqand I don't have any updates here16:31
slaweqralonsoh: sure, we are still supporting neutronclient16:31
slaweqit's deprecated but supported16:31
slaweqand amotoki is taking care of switching it to py316:32
*** mlavalle has left #openstack-meeting16:32
*** rsimai has quit IRC16:32
slaweqany questions/other updates about stadium projects?16:33
slaweqok, lets move on quickly16:33
slaweq#topic Grafana16:33
*** openstack changes topic to "Grafana (Meeting topic: neutron_ci)"16:33
slaweq#link http://grafana.openstack.org/dashboard/db/neutron-failure-rate16:33
*** ricolin has quit IRC16:34
slaweqlooking at integrated tempest jobs, I think we are a bit better now, since we switched some jobs to only run neutron and nova related tests16:34
slaweqeven last week most of those jobs were in quite good shape16:35
slaweqfullstack is also quite good now16:35
slaweqfunctiona test are failing a bit16:36
slaweqbut I think it's mostly related to the issues which we talked about earlier today16:36
slaweqanything else regarding grafana?16:37
slaweqok, lets move on16:38
slaweq#topic fullstack/functional16:38
*** openstack changes topic to "fullstack/functional (Meeting topic: neutron_ci)"16:38
slaweqI have only 2 things related to fullstack tests today16:38
slaweq1. I recently found one "new" issue and reported a bug: https://bugs.launchpad.net/neutron/+bug/183738016:39
openstackLaunchpad bug 1837380 in neutron "Timeout while getting bridge datapath id crashes ova agent" [High,In progress] - Assigned to Slawek Kaplonski (slaweq)16:39
slaweqbasically if some physical bridge is recreated and there will be timeout while getting datapath id, neutron-ovs-agent will crash completly16:40
ralonsohthat means the bridge is created again?16:40
slaweqcorrect ralonsoh16:40
ralonsohmaybe the default datapath_is is not correct16:40
ralonsohthis must be different from the other bridges16:40
ralonsohand should be "something" not null16:41
slaweqralonsoh: please check logs: http://logs.openstack.org/81/671881/1/check/neutron-fullstack/c6b2e08/controller/logs/dsvm-fullstack-logs/TestLegacyL3Agent.test_north_south_traffic/neutron-openvswitch-agent--2019-07-22--07-48-17-892074_log.txt.gz#_2019-07-22_07_49_28_69816:41
slaweqit was timeout while getting datapath_id16:41
ralonsohI see, yes16:41
ralonsoh10 secs to retrieve the datapath16:41
slaweqin fullstack/functional jobs we have seen from time to time e.g. ovsdbapp timeouts and things like that16:41
slaweqso my assumption is that similar issue happend here16:42
slaweqbut this shouldn't cause crash of agent IMO16:42
slaweqbut, as You can see at http://logs.openstack.org/81/671881/1/check/neutron-fullstack/c6b2e08/controller/logs/dsvm-fullstack-logs/TestLegacyL3Agent.test_north_south_traffic/neutron-openvswitch-agent--2019-07-22--07-48-17-892074_log.txt.gz#_2019-07-22_07_49_28_756 it crashes16:42
ralonsohno, of course16:42
slaweqI proposed some patch for that but will need to add some UT for that probably: https://review.opendev.org/67201816:42
ralonsohactually I was talking more about the second error16:43
*** yamamoto has joined #openstack-meeting16:43
slaweqwhich one?16:43
ralonsohthe one related to https://review.opendev.org/#/c/67201816:44
ralonsohI'll review your patch16:44
slaweqyes, this one is related to this crash while getting datapath_id of bridge16:44
slaweqit's one issue16:44
slaweqok, and the other thing which I have for today is16:45
slaweqbut I found this failure only once so far and IMO it may be related to the patch on which it was running16:46
slaweqso I would just keep an eye on those tests :)16:46
slaweqand that's all from my for today16:46
slaweqI think we already talked about all other "hot" issues with tempest and functional tests16:47
slaweqanything else You want to talk about today?16:47
slaweqok, so lets finish a bit earlier today16:48
slaweqthx for attending16:48
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"16:48
openstackMeeting ended Tue Jul 23 16:48:19 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:48
*** yamamoto has quit IRC16:48
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_ci/2019/neutron_ci.2019-07-23-16.00.html16:48
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_ci/2019/neutron_ci.2019-07-23-16.00.txt16:48
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_ci/2019/neutron_ci.2019-07-23-16.00.log.html16:48
*** yamamoto has joined #openstack-meeting16:49
*** armax has quit IRC16:50
*** jaypipes has quit IRC16:54
*** enriquetaso has joined #openstack-meeting16:54
*** trident has quit IRC17:07
*** trident has joined #openstack-meeting17:10
*** yamamoto has quit IRC17:11
*** priteau has quit IRC17:11
*** yamamoto has joined #openstack-meeting17:13
*** ociuhandu has quit IRC17:13
*** lseki has quit IRC17:16
*** yamamoto has quit IRC17:18
*** enriquetaso has quit IRC17:23
*** _erlon_ has joined #openstack-meeting17:25
*** enriquetaso has joined #openstack-meeting17:31
*** armax has joined #openstack-meeting17:32
*** e0ne has quit IRC17:33
*** senrique_ has joined #openstack-meeting17:35
*** ralonsoh has quit IRC17:36
*** enriquetaso has quit IRC17:37
*** iyamahat has quit IRC17:43
*** panda is now known as panda|off17:45
*** _hemna has joined #openstack-meeting17:49
*** Lucas_Gray has joined #openstack-meeting17:58
*** armax has quit IRC18:01
*** Lucas_Gray has quit IRC18:03
*** armax has joined #openstack-meeting18:03
*** Lucas_Gray has joined #openstack-meeting18:05
*** Shrews has joined #openstack-meeting18:14
*** ociuhandu has joined #openstack-meeting18:16
*** psachin has quit IRC18:19
*** Lucas_Gray has quit IRC18:20
*** Lucas_Gray has joined #openstack-meeting18:22
*** _hemna has quit IRC18:22
*** igordc has joined #openstack-meeting18:27
*** ociuhandu has quit IRC18:34
*** senrique__ has joined #openstack-meeting18:34
*** senrique__ is now known as enriquetaso18:34
*** Lucas_Gray has quit IRC18:36
*** Lucas_Gray has joined #openstack-meeting18:36
*** senrique_ has quit IRC18:38
*** e0ne has joined #openstack-meeting18:42
*** mriedem has quit IRC18:42
*** enriquetaso has quit IRC18:49
clarkbanyone else here for the infra meeting?19:00
clarkbwe will get started momentarily19:00
*** igordc has quit IRC19:00
clarkb#startmeeting infra19:01
openstackMeeting started Tue Jul 23 19:01:37 2019 UTC and is due to finish in 60 minutes.  The chair is clarkb. Information about MeetBot at http://wiki.debian.org/MeetBot.19:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:01
*** openstack changes topic to " (Meeting topic: infra)"19:01
openstackThe meeting name has been set to 'infra'19:01
clarkb#link http://lists.openstack.org/pipermail/openstack-infra/2019-July/006425.html19:01
clarkb#topic Announcements19:02
*** openstack changes topic to "Announcements (Meeting topic: infra)"19:02
clarkbThere weren't any recorded on the agenda19:03
clarkb#topic Actions from last meeting19:03
*** openstack changes topic to "Actions from last meeting (Meeting topic: infra)"19:03
clarkb#link http://eavesdrop.openstack.org/meetings/infra/2019/infra.2019-07-16-19.01.txt minutes from last meeting19:03
clarkbmordred: any updates on the github cleanup work?19:03
*** ociuhandu has joined #openstack-meeting19:04
*** dtrainor has quit IRC19:05
mordredclarkb: nope. totally been doing gerrit instead. also, I keep hitting github rate limits and then doing something else19:05
clarkbmordred: we need to convert you into a github app then19:06
clarkb#action mordred clean up openstack-infra github org19:06
clarkb#action mordred create opendevadmin account on github19:06
clarkb#topic Priority Efforts19:07
*** openstack changes topic to "Priority Efforts (Meeting topic: infra)"19:07
clarkb#topic OpenDev19:07
*** openstack changes topic to "OpenDev (Meeting topic: infra)"19:07
clarkbLets start here since a fair bit has gone on with gitea in the last week or so19:08
fungiindeed it has19:08
clarkbWe've discovered that gitea services can cause OOMKiller to be invoked. This often targets git processes for killing. If this happens when gerrit is replicating to gitea we can lose that replication event19:08
fungisynopsis: corrupt git repo or missing objects19:09
clarkbI've put 1GB of swap (via swapfile) on gitea01-05,07-08 and 8GB on gitea06. The reason for the difference in size is 06 was rebuilt with a much larger root disk and has space for the swapfile the others are smaller and don't have much room19:09
*** ociuhandu_ has joined #openstack-meeting19:09
clarkb1GB of swap is not sufficient to avoid these errors19:09
*** ociuhandu has quit IRC19:09
clarkbBut 8GB appears to have been sufficient so we are rebuilding gitea01 to be like gitea06 and will likely roll through all the other backends to do the same thing19:09
clarkbIn this process we've discovered a few deficiencies with how we deploy gitea and manage haproxy fixes for which are all merged now with exception of how to gracefully restart haproxy when haproxy's image updates19:10
fungiold instance/volume deleted, new bfv instance exists now and needs data copied over19:10
clarkbI don't know how to handle that last case and will need to think about it more (and read up on docker-compose)19:10
donnydclarkb: Is there an agenda?19:12
fungiyeah, manuals say sigusr1 is for that19:12
clarkbdonnyd: ya http://lists.openstack.org/pipermail/openstack-infra/2019-July/006425.html19:12
fungiif i'm reading correctly19:12
donnydSorry. I didn't scroll all the way down.19:12
clarkbfungi: ya so will depend on whether or not we can have docker-compose somehow send signals when it restarts stuff19:12
clarkbfungi: we may have to break this out of docker-compose? or accept that iamges don't update often19:12
clarkb(and haproxy restarts are quick)19:12
clarkbneed to do more research19:13
mordredI mean - I think we always have ansible running docker-compose things19:13
mordredso it's reasonable for ansible to  tell docker-compose to send a signal or whatever19:13
Shrewshttp://cavaliercoder.com/blog/restarting-services-in-docker-compose.html  ??19:14
clarkbmordred: right but the image replacement is all a bit automagic in docker compose19:14
* fungi just wrote a handler which does that19:14
mordredclarkb: ah yes - that's an excellent point19:14
clarkbmordred: so either we can hook into that or we stop relying on it and manually break out the steps19:14
mordredwe don't actually want to do this every ansible time- only if the result of pull would cause a restart19:14
fungiyeah, image updates will require more than just sending a signal to the running daemon19:15
corvushappily, haproxy is generally pretty boring and stable19:15
clarkbcorvus: yup (today is an exception and there should be a new image soon but in general that is true)19:15
clarkbI think that is the least urgent item to sort out for impactless updates19:16
clarkbthe urgent ones have all been addressed, thank you19:16
clarkbWe should keep an eye out for unexpected behavior going forward as digging into the problems today was really helpful19:16
*** kopecmartin is now known as kopecmartin|off19:16
clarkbAre there any other opendev related changes we should be aware of?19:17
clarkbSounds like no. Onward19:18
clarkb#topic Update Config Management19:18
*** openstack changes topic to "Update Config Management (Meeting topic: infra)"19:18
clarkbmordred has been working on getting gerrit into docker19:18
clarkbmordred: anything you want to call out for that activity?19:18
mordredyes. I just pushed up a new rev19:18
mordreduhm - mainly it's definitely ready for review now19:19
mordredand clarkb just found a good pile of gotcha for 2.1319:19
mordredso review is much appreciated19:19
clarkb#link https://review.opendev.org/671457 Gerrit docker image builds ready for review19:19
corvusi think when that's in place https://review.opendev.org/630406 is going to show us any problems with it19:19
mordredthe general idea is making a 2.13 image that works pretty much just like our current 2.13 install19:19
corvusthere's currently a problem with the last image we built (6mo ago); i doubt it's fixed, but we'll be able to iterate then19:19
mordredcorvus: agree - although there are a few things, like heapSize, that we'll want to thikn about?19:20
mordredcorvus: ++19:20
corvusand by "problem" i mean things like file ownership, paths, etc19:20
mordredmost of the things should pretty immediately break19:20
corvusmordred: heapSize is something we can pass in in an env var, right?19:20
mordredit is now :)19:20
corvus(so we can have a test and prod value)19:20
mordredwe WILL be losing the ability to set those things in gerrit.config unless we make things more complex19:21
clarkbmordred: could we run an image that ran the gerrit init script?19:21
mordrednot really - it forks gerrit into the background19:21
clarkbright but aren't there docker images that know how to manage that?19:22
mordredI mean - we COULD - but I'd rather fix this to not be wonky like that19:22
mordredand it's not far off19:22
*** Lucas_Gray has quit IRC19:22
*** whoami-rajat has quit IRC19:22
*** Wryhder has joined #openstack-meeting19:22
*** panda|off has quit IRC19:23
clarkbwe should be able to deploy it on review-dev and be pretty happy with the results before we commit to production too19:23
fungias long as gerrit upstream also doesn't intend it to be wonky like that19:23
fungiotherwise seems a bit sisyphean19:23
*** Wryhder is now known as Lucas_Gray19:23
clarkbI get the sense that gerrit upstream has sort of ignored these problems with their images?19:23
clarkb(I seem to recall it relying on h2 among other things)19:24
fungiwhich i expect is fine as long as they don't intentionally make it worse19:24
corvushrm, i think the upstream images are decently constructed19:24
corvusthey have volumes in the right places, so you don't have to use h219:24
corvusthey don't work for us because we want to be able to patch :)19:24
mordredmost of the stuff going on in the init script is not actually necessary19:25
mordredit elides out pretty quickly once you're making images, because you know where all the things are19:25
mordred(there's a TON of logic for finding where your files might be, for instance)19:25
clarkbit seems like they completely ignore things like java heapsizes though?19:25
*** panda has joined #openstack-meeting19:25
clarkboh maybe not https://github.com/GerritCodeReview/docker-gerrit/blob/master/ubuntu/18/entrypoint.sh#L1619:26
clarkbthey are running the init script19:27
mordredyeah. I mean - we could do that if people want - I just don't think we need to19:27
clarkbMy biggest concern with not doing that is that we might miss important changes to java configs or other settings that happen in the runtime (not gerrit itself) as new versions of gerrit or java come out19:28
clarkbbut you are right that that is less ideal for docker19:28
fungiand maybe an opportunity to collaborate19:28
mordredthere is currently exactly one setting we are setting that results in a java cli option being pulled out by the init script :)19:28
clarkbmordred: we also set the timeout option but that one doesn't make sense with docker19:29
clarkbnot much preexisting cause for worry then19:30
clarkbcurrent approach should be fine19:30
clarkbSounds like that may be it on this topic then?19:33
clarkb#topic Storyboard19:33
*** openstack changes topic to "Storyboard (Meeting topic: infra)"19:33
clarkbfungi: diablo_rojo_phon how are things?19:33
fungiwe had a good session on friday grooming feature requests into our main priorities board19:33
*** Lucas_Gray has quit IRC19:34
diablo_rojo_phonGonna meet this week19:34
fungi#link https://storyboard.openstack.org/#!/board/115 StoryBoard Team Dashboard19:34
diablo_rojo_phonTalk about ptg forum things19:34
*** enriquetaso has joined #openstack-meeting19:35
*** Lucas_Gray has joined #openstack-meeting19:35
diablo_rojo_phonOnboarding maybe.19:35
*** bbowen has quit IRC19:35
fungicurious to see what interest we can drum up in shanghai19:35
fungithat's all i can recall19:36
diablo_rojo_phonYeah that's it for now19:36
clarkb#topic General Topics19:36
*** openstack changes topic to "General Topics (Meeting topic: infra)"19:36
fungioh, i've pushed some changes to get python-storyboardclient testable again19:36
diablo_rojo_phonAside from begging mordred to do some SQL things in hopes of improving search19:37
diablo_rojo_phonThanks fungi!19:37
clarkbfungi: for the wiki upgrade I think last week the suspicion was git submodules19:37
clarkbhave we been able to take that suspicion and make progress with it yet ? (also I know I said I woudl try to help then got sucked into making gitea betterer)19:37
funginope, i had weekend guests and so less time on hand than hoped19:38
clarkbok I'll actually try to take a look this week19:38
corvusi've been working on making progress on the zuul log handling; while we can technically switch to swift log storage at any time, the experience will degrade if we do it now, but could be better if we do it after we add some things to zuul19:38
corvus#link https://zuul-ci.org/docs/zuul/developer/specs/logs.html zuul log handling spec19:38
fungisubmodules or similar (git subtree?) theories are possible avenues of investigation for the mediawiki situation19:39
clarkbcorvus: is the log manifest bit the piece to reduce degradation?19:39
corvusi've pestered mordred and clarkb for reviews of blokers so far.  i think i'm about at the end of that, and with the (yes) zuul-manifest stuff in place, we should be able to see the javascript work in action with the preview builds19:39
corvusyeah, the short version is the manifest lets the web app handle indexes, so we don't have to pre-generate them, and we can also display logs in the web app itself19:40
corvuswhich means we can have javascript do the OSLA bits (which otherwise we would also have to pre-generate)19:40
fungithat sounds like a great approach19:40
clarkbthen we can delete the log server19:40
clarkband there will be much rejoicing19:40
fungisaw some of those changes float by and will try to take a closer look19:41
corvusit'll get interesting once the manifest stuff is in place and i can rebase for it.  hopefully today19:41
clarkbexciting progress19:41
ianwthe kafs mirror servers are out of rotation for now; there are some changes queued in afs-next branch which it would be good for us to test before they are sent to linus19:41
ianwhowever the tree currently doesn't build, but when it does it would be good to put into rotation for a while to confirm.  the fscache issues are unresolved, however19:42
fungii find it awesome that we're testing things before they're sent to linus19:42
fungi(just an aside)19:42
corvusfungi: ++19:42
clarkbianw: good to know, let us know how we can heklp I suppose (reviewing changes to flip around the mirror that is used?)19:43
*** iyamahat has joined #openstack-meeting19:43
corvusianw: does afs-next get patches via mailing list?19:43
fungiseems so, yes19:44
corvus(i've been itching to write an imap driver for zuul; wonder if this would be a practical use)19:44
ianwcorvus: there is a mailing list, but things also pop in and out as dhowells works on things19:44
fungii will *so* review an imap/smtp zuul driver19:44
fungii mean, i guess the smtp reporter is already there? ;)19:45
* corvus read "tree currently doesn't build" and got really confused and sad19:45
clarkbIntel has been doing a bunch of CI for the kernel recently I think19:46
clarkbthat might be another avenue for collaboration potentially19:46
clarkbAs a timecheck we have ~14 minutes left and a couple more items to get through so lets continue on though19:46
clarkbI did want to do a cloud status check in19:46
fungian nntp driver would be cool, but convincing lkml to return their focus on usenet might be an uphill battle19:46
clarkbFortNebula cloud is pretty well stabilized at this point. Thank you donnyd19:47
fungithanks donnyd!!!19:47
clarkbthere may be one or two corner cases that need further invenstigating (ipv6 related maybe?)19:47
donnydyea it seems to be working well atm19:47
clarkbbut overall it is doing great19:47
donnydYea I am not sure why there seem to be just 3 jobs that timeout19:47
fungiwhich three jobs?19:47
donnydHopeful the right storage gear will *actually* show up tomorrow19:48
fungii hear there's a generator backup in the works too19:48
donnydfungi: I will get you the list, but it seems to be fairly consistent19:48
donnydyea, its been sitting outside for 6 weeks19:48
donnydjust got a pad poured and now I am waiting for the gas to be hooked up to it19:49
clarkbmordred: for MOC is there anything we can be doing or is it still in that weird make accounts and get people to trust us situation :)19:49
donnydand my UPS have been refreshed, so they should handle the load till the genny takes over19:49
clarkbI have not heard anything new about the new linaro cloud since we last had this meeting19:49
*** Lucas_Gray has quit IRC19:49
fungihah. i need to get a generator for here. most of my neighbors have them so i'm feeling rather naked (though i need a >=6' platform to support it)19:49
clarkbfungi: is that something you can put on the roof? that should be high enoguh19:50
fungii'd need to reinforce the roof for that19:50
mordredclarkb: lemme check to see if it's been fixed19:50
donnydIs there any other fun experiments we can do with FN?19:50
fungithis experiment isn't enough? (just kidding!)19:51
clarkbdonnyd: I think if we get a serious group together to start working out nested virt issues (another potential avenue for feedback to the kernel) that would be super helpful19:51
fungiyeah, that's been a frequent request19:51
clarkbdonnyd: what we've found in the past is taht debugging those issues requires involvement from all layers of the stack and what we've traditionally lacked is insight into the cloud19:51
donnydyea, I have seen more than one request for it19:51
donnydclarkb: would ssh access to the hypervisors help?19:52
*** Lucas_Gray has joined #openstack-meeting19:52
clarkbjohnsom and kashyap are your workload and kernel people and then if we can get them insight into the hypervisors we may start with balls rolling19:52
fungiif it came with people to ssh in and troubleshoot them ;)19:52
mordredclarkb: MOC still waiting on app credentials to be enabled in their keystone19:52
clarkbdonnyd: I'm not sure they need to ssh in as much as just candid data capture19:52
* mordred pings knikolla ^^19:52
clarkbdonnyd: cpu and microcode version and kernel versions and modules loaded and so on19:52
clarkbmordred: k19:52
donnydsure... this is the only workload this thing is doing... I can make logs public facing without issue19:53
clarkbdonnyd: kashyap would be the best person to engage for what needs are19:53
fungion the cloud providers topic, there's a change posted to switch the main flavor in the lon1 aarch64 cloud to 16 cpus and 16gb ram because of resource demands from kolla arm64 jobs19:53
clarkbfungi: I'm a bit wary of increasing the memory footprint just because but considering it is a different cpu arch incraesing teh cpu count seems reasonable19:53
corvusthe arm jobs require more ram?19:54
fungi#link https://review.opendev.org/671445 Linaro London: use new bigger flavour19:54
fungiclarkb: corvus: these are questions i too have asked19:54
clarkbin defense of the request devstack + tempest does swap now19:54
fungiplease follow up on that change so i'm not the only one ;)19:54
clarkband I'm sure that is part of the slowness, but the fixing should involve figuring out why we've used so much more memory than in the past19:54
clarkbfungi: will do19:54
clarkbreally quickly before we run out of time19:55
clarkbI submitted PTG survery for the opendev infra team and gitea as separate requests19:55
clarkbThat means if you are going to be in shanghai some group of us likely will as well19:55
clarkb#link https://etherpad.openstack.org/p/OpenDev-Shanghai-PTG-2019 Start planning the next PTG19:55
clarkbThat has no content yet but it is there for people to start putting ideas up (I know it is early so no pressure)19:56
* mordred will be in shanghai19:56
fungii'm so scattered i honestly can't recall whether i've filled out the opendev infra survey19:57
clarkbfungi: its for me to fill out and you not to worry about19:57
fungiahh, got i19:57
clarkbfungi: basically our request to the foundation that we want space at the PTG19:57
* fungi gives up on typing again19:57
clarkb#topic Open Discussion19:57
*** openstack changes topic to "Open Discussion (Meeting topic: infra)"19:57
clarkbWe have a couple minutes for anything else that may have been missed19:58
clarkbThank you for yout time and we'll see you next week19:59
fungithanks clarkb!19:59
clarkbmy typing is suffering now too :)19:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"20:00
openstackMeeting ended Tue Jul 23 20:00:05 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/infra/2019/infra.2019-07-23-19.01.html20:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/infra/2019/infra.2019-07-23-19.01.txt20:00
openstackLog:            http://eavesdrop.openstack.org/meetings/infra/2019/infra.2019-07-23-19.01.log.html20:00
*** mriedem has joined #openstack-meeting20:00
*** lbragstad has quit IRC20:01
*** e0ne has quit IRC20:06
*** slaweq has quit IRC20:08
*** dtrainor has joined #openstack-meeting20:09
*** Shrews has left #openstack-meeting20:15
*** iyamahat has quit IRC20:18
*** _hemna has joined #openstack-meeting20:19
*** ociuhandu_ has quit IRC20:32
*** ociuhandu has joined #openstack-meeting20:33
*** Lucas_Gray has quit IRC20:36
*** zaneb has joined #openstack-meeting20:41
*** pcaruana has quit IRC20:50
*** _hemna has quit IRC20:53
*** slaweq has joined #openstack-meeting20:56
*** slaweq has quit IRC21:01
*** oneswig has joined #openstack-meeting21:02
*** ociuhandu has quit IRC21:02
oneswigApologies - no Scientific SIG meeting today, can't get the staff at this point in the summer.21:03
*** bbowen has joined #openstack-meeting21:03
oneswigWe'll endeavour to resume next week.21:04
*** oneswig has quit IRC21:06
*** martial_ has joined #openstack-meeting21:12
*** martial_ is now known as martial21:12
*** iyamahat has joined #openstack-meeting21:20
*** lpetrut has joined #openstack-meeting21:22
*** e0ne has joined #openstack-meeting21:22
*** lpetrut has quit IRC21:22
*** lpetrut has joined #openstack-meeting21:23
*** iyamahat has quit IRC21:26
*** b1airo has joined #openstack-meeting21:30
*** lpetrut has quit IRC21:30
*** ayoung has quit IRC21:31
*** zaneb has quit IRC21:31
*** irclogbot_2 has quit IRC21:32
*** altlogbot_3 has quit IRC21:33
*** altlogbot_1 has joined #openstack-meeting21:34
*** irclogbot_3 has joined #openstack-meeting21:34
*** enriquetaso has quit IRC21:44
*** yamamoto has joined #openstack-meeting21:50
*** e0ne has quit IRC21:50
*** yamamoto has quit IRC21:55
*** irclogbot_3 has quit IRC21:59
*** altlogbot_1 has quit IRC22:01
*** armax has quit IRC22:11
*** altlogbot_1 has joined #openstack-meeting22:22
*** gyee has quit IRC22:23
*** TxGirlGeek has quit IRC22:25
*** altlogbot_1 has quit IRC22:27
*** raildo has quit IRC22:35
*** diablo_rojo has joined #openstack-meeting22:41
*** _hemna has joined #openstack-meeting22:49
*** ayoung has joined #openstack-meeting22:53
*** mriedem has quit IRC22:55
*** armax has joined #openstack-meeting23:04
*** gyee has joined #openstack-meeting23:10
*** altlogbot_1 has joined #openstack-meeting23:14
*** carloss has quit IRC23:16
*** rcernin has joined #openstack-meeting23:16
*** altlogbot_1 has quit IRC23:19
*** _hemna has quit IRC23:24
*** altlogbot_3 has joined #openstack-meeting23:28
*** irclogbot_2 has joined #openstack-meeting23:32
*** igordc has joined #openstack-meeting23:35
*** jamesmcarthur has joined #openstack-meeting23:36
*** b1airo has quit IRC23:39
*** jamesmcarthur has quit IRC23:52
*** diablo_rojo has quit IRC23:54

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