Tuesday, 2019-01-15

*** yamamoto has quit IRC00:03
*** yamamoto has joined #openstack-meeting00:05
*** markvoelker has quit IRC00:06
*** mriedem_away has quit IRC00:07
*** yamamoto has quit IRC00:07
*** ttsiouts has joined #openstack-meeting00:08
*** jbadiapa has quit IRC00:10
*** yamamoto has joined #openstack-meeting00:11
*** yamamoto has quit IRC00:13
*** _alastor_ has quit IRC00:14
*** yamamoto has joined #openstack-meeting00:14
*** yamamoto has quit IRC00:16
*** macza has quit IRC00:18
*** ttsiouts has quit IRC00:26
*** ttsiouts has joined #openstack-meeting00:27
*** yamamoto has joined #openstack-meeting00:27
*** _alastor_ has joined #openstack-meeting00:30
*** yamamoto has quit IRC00:31
*** ttsiouts has quit IRC00:32
*** _alastor_ has quit IRC00:39
*** _alastor_ has joined #openstack-meeting00:40
*** _alastor_ has quit IRC00:45
*** zaneb has joined #openstack-meeting00:46
*** mattw4 has quit IRC00:54
*** enriquetaso has quit IRC00:55
*** _alastor_ has joined #openstack-meeting01:03
*** bbowen has quit IRC01:12
*** yamamoto has joined #openstack-meeting01:15
*** _alastor_ has quit IRC01:18
*** whoami-rajat has joined #openstack-meeting01:20
*** yamamoto has quit IRC01:21
*** bbowen has joined #openstack-meeting01:25
*** Liang__ has joined #openstack-meeting01:28
*** markvoelker has joined #openstack-meeting01:35
*** markvoelker has quit IRC01:40
*** hongbin has joined #openstack-meeting01:57
*** hongbin has quit IRC01:59
*** hongbin has joined #openstack-meeting02:04
*** ekcs has quit IRC02:06
*** macza has joined #openstack-meeting02:06
*** macza has quit IRC02:11
*** erlon_ has quit IRC02:11
*** TxGirlGeek has quit IRC02:23
*** yamamoto has joined #openstack-meeting02:32
*** Liang__ has quit IRC02:36
*** yamamoto has quit IRC02:37
*** Liang__ has joined #openstack-meeting02:39
*** njohnston has quit IRC02:40
*** bbowen has quit IRC02:40
*** iyamahat_ has quit IRC02:44
*** yamahata has quit IRC02:45
*** mhen has quit IRC02:53
*** mhen has joined #openstack-meeting02:54
*** apetrich has quit IRC03:16
*** TxGirlGeek has joined #openstack-meeting03:18
*** yamamoto has joined #openstack-meeting03:30
*** diablo_rojo has quit IRC03:45
*** tpatil has joined #openstack-meeting03:49
*** TxGirlGeek has quit IRC03:51
*** tashiromt has joined #openstack-meeting03:56
*** sagara has joined #openstack-meeting04:01
tpatilDoes anyone know whether samP will join masakari meeting or not?04:02
tpatilIn his absence, let me start the meeting first04:03
tpatil#startmeeting Masakari04:03
openstackMeeting started Tue Jan 15 04:03:28 2019 UTC and is due to finish in 60 minutes.  The chair is tpatil. Information about MeetBot at http://wiki.debian.org/MeetBot.04:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.04:03
*** openstack changes topic to " (Meeting topic: Masakari)"04:03
openstackThe meeting name has been set to 'masakari'04:03
tpatilHi Masakari Team04:03
tpatilHi tashiromt04:04
tpatil#topic Critical bugs04:05
*** openstack changes topic to "Critical bugs (Meeting topic: Masakari)"04:05
tpatil#link https://bugs.launchpad.net/masakari/+bug/181174204:05
openstackLaunchpad bug 1811742 in masakari "nova client call to disabled_reason method accepts service_uuid for api_version 2.53" [Critical,Confirmed]04:05
*** igordc has quit IRC04:05
tpatilLucas has proposed a patch to fix above bug: https://review.openstack.org/#/c/627097/04:05
tpatil#link https://bugs.launchpad.net/masakari/+bug/180923004:06
openstackLaunchpad bug 1809230 in masakari "tox -e cover returns "error: option --coverage not recognized"" [High,In progress] - Assigned to Neha Alhat (nehaalhat)04:06
tpatilI have approved this patch : https://review.openstack.org/#/c/629759/04:07
tpatilNeed another one +2 and worflow04:07
tpatilMoving to next topic04:09
tpatil#topic Stein Work Items04:09
*** openstack changes topic to "Stein Work Items (Meeting topic: Masakari)"04:09
tpatilNotification implementation04:09
tpatilSome of the unit tests are failing on gate jobs. Shilpa will upload a new PS to fix this issue soon04:10
*** _alastor_ has joined #openstack-meeting04:11
tpatilAfter the unit test issue is fixed we should start reviewing all patches04:12
tpatil#link https://review.openstack.org/#/q/status:open+project:openstack/masakari+branch:master+topic:bp/notifications-in-masakari04:12
tpatil2. Add functional tests in masakari04:13
tpatilSomeone needs to work on this. I will talk with Shilpa to see if she can take up this task.04:14
*** _alastor_ has quit IRC04:16
tpatilThat's all from my end04:18
tpatiltashiromt: Do you have any topic for discussion?04:18
tashiromti dont have any topic today. thank you04:19
tpatillet's end this meeting early then04:19
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"04:20
openstackMeeting ended Tue Jan 15 04:20:02 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)04:20
openstackMinutes:        http://eavesdrop.openstack.org/meetings/masakari/2019/masakari.2019-01-15-04.03.html04:20
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/masakari/2019/masakari.2019-01-15-04.03.txt04:20
openstackLog:            http://eavesdrop.openstack.org/meetings/masakari/2019/masakari.2019-01-15-04.03.log.html04:20
*** tpatil has left #openstack-meeting04:22
*** hongbin has quit IRC04:25
*** radeks has joined #openstack-meeting04:33
*** yamamoto has quit IRC04:34
*** vishalmanchanda has joined #openstack-meeting04:40
*** sagara has quit IRC04:52
*** SWDevAngel has quit IRC05:15
*** ekcs has joined #openstack-meeting05:24
*** iyamahat has joined #openstack-meeting05:29
*** yamamoto has joined #openstack-meeting05:42
*** Bhujay has joined #openstack-meeting05:43
*** Bhujay has quit IRC05:44
*** Bhujay has joined #openstack-meeting05:45
*** Bhujay has quit IRC05:46
*** Bhujay has joined #openstack-meeting05:46
*** ekcs has quit IRC05:47
*** markvoelker has joined #openstack-meeting05:48
*** yamamoto has quit IRC05:49
*** lbragstad has quit IRC05:56
*** markvoelker has quit IRC05:59
*** dkushwaha has joined #openstack-meeting06:32
*** brault has quit IRC06:33
*** yamahata has joined #openstack-meeting06:36
*** diablo_rojo has joined #openstack-meeting06:46
*** rcernin has quit IRC06:59
*** Bhujay has quit IRC07:01
*** yamamoto has joined #openstack-meeting07:08
*** Bhujay has joined #openstack-meeting07:10
*** Bhujay has quit IRC07:11
*** Bhujay has joined #openstack-meeting07:11
*** yamamoto has quit IRC07:13
*** tetsuro has joined #openstack-meeting07:14
*** jbadiapa has joined #openstack-meeting07:15
*** tetsuro has quit IRC07:16
*** hadai has joined #openstack-meeting07:17
*** iyamahat has quit IRC07:20
*** bhagyashris has joined #openstack-meeting07:25
*** e0ne has joined #openstack-meeting07:30
*** kopecmartin|off is now known as kopecmartin07:35
*** tetsuro has joined #openstack-meeting07:47
*** tpatil has joined #openstack-meeting07:47
*** apetrich has joined #openstack-meeting07:48
*** tetsuro has quit IRC07:52
*** tetsuro has joined #openstack-meeting07:54
*** tetsuro has quit IRC07:55
*** phuoc has joined #openstack-meeting07:57
dkushwaha#startmeeting tacker08:01
openstackMeeting started Tue Jan 15 08:01:23 2019 UTC and is due to finish in 60 minutes.  The chair is dkushwaha. Information about MeetBot at http://wiki.debian.org/MeetBot.08:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.08:01
*** openstack changes topic to " (Meeting topic: tacker)"08:01
openstackThe meeting name has been set to 'tacker'08:01
dkushwaha#topic Roll Call08:01
*** openstack changes topic to "Roll Call (Meeting topic: tacker)"08:01
dkushwahawho is here for weekly meeting?08:02
dkushwahahi bhagyashris08:02
bhagyashrisHi dkushwaha08:03
dkushwahahello phuoc08:03
phuochi dkushwaha, bhagyashris :)08:04
*** e0ne has quit IRC08:04
dkushwahaseems no more member available today08:06
*** tetsuro has joined #openstack-meeting08:06
dkushwahaok lets start08:06
dkushwaha#chair phuoc08:06
openstackCurrent chairs: dkushwaha phuoc08:06
dkushwaha#topic Stein PTG08:07
*** openstack changes topic to "Stein PTG (Meeting topic: tacker)"08:07
*** tetsuro has quit IRC08:07
dkushwahaI got mail to book room for PTG, which will be held just after summit08:07
dkushwahaphuoc, bhagyashris Do you have plan to join sumit/PTG?08:08
*** radeks has quit IRC08:08
bhagyashrisdkushwaha: yes08:08
dkushwahabhagyashris, sounds good08:08
phuocdkushwaha, I will graduate next month and get a job08:09
dkushwahaphuoc, that great :)08:09
phuocI hope that company has financial support for me :)08:09
phuocdkushwaha, thank you :)08:09
dkushwahaphuoc, cool. And best wishes for your new journey :)08:10
dkushwahaOk so i will request room for PTG08:10
phuocthat would be great08:11
dkushwahamoving ahead..08:11
dkushwaha#topic VNF monitoring using Mistral08:11
*** openstack changes topic to "VNF monitoring using Mistral (Meeting topic: tacker)"08:11
dkushwaha#link https://review.openstack.org/#/c/486924/08:11
dkushwahaI have just uploaded the new patch, but still getting some error.08:12
phuocI will spend time to look at it08:12
dkushwahaphuoc, after detecting that VNF is dead, while deleting mistral current  workflow, it giving error like: coud not get endpoint service catalog is empty.08:14
dkushwahaI will try to fix it by today itself08:15
dkushwahain the mean while it will be great if you can look into patch08:15
phuocdkushwaha, sure I will do it08:15
dkushwahamoving next..08:16
dkushwaha#topic force-delete resources08:16
*** openstack changes topic to "force-delete resources (Meeting topic: tacker)"08:16
dkushwahaphuoc, bhagyashris https://review.openstack.org/#/c/602528/08:17
dkushwahaplease have a look on that08:18
bhagyashrisdkushwaha: sure08:18
dkushwahai am supposing to merge specs soon which are under implementation08:19
phuocit looks fine to me, so we can update some minor issues08:20
bhagyashrisdkushwaha: is the --force parameter will be passed in request body or in request URL? if it's in the request body the that should be describe in REST API Impact section08:21
dkushwahabhagyashris, that will go in body section08:22
dkushwahabhagyashris, I will update the spec08:23
bhagyashrisdkushwaha: IMO, irespective of of passing --force in request body or in request url the REST API IMpact is there so it should be describe i REST API Impact section08:23
bhagyashrisdkushwaha: ok.08:23
dkushwahamoving next..08:23
dkushwaha#topic vdu_autoheal08:23
*** openstack changes topic to "vdu_autoheal (Meeting topic: tacker)"08:23
dkushwaha#link https://review.openstack.org/#/c/612595/08:24
dkushwahabhagyashris, do you have something to talk?08:24
bhagyashrisdkushwaha: I have implemented your review comments please take look at it08:25
dkushwahaI could not review in last week. I will review & test this patch.08:25
bhagyashrisphuoc:  has reviewed patch and got +2 from him08:26
bhagyashrisdkushwaha:  Thank you :)08:26
phuocI tested this patch, LGTM :)08:26
dkushwahabhagyashris, phuoc thanks for your great effort. Ok i will check and if ok, I will merge it by tomorrow08:27
*** nnsingh has joined #openstack-meeting08:27
bhagyashrisdkushwaha: Thank you :)08:27
dkushwahamoving next..08:28
bhagyashrisphuoc:  Thank you for review :)08:28
dkushwahaphuoc, do you have something to talk ?08:28
phuocabout this patch, https://review.openstack.org/#/c/620680/08:28
phuocI think we need an update in networking-sfc08:29
phuocand if we want to support NSH, we also need to update ovs too08:29
phuocdkushwaha, if you are interested in problem in NSH, I will inform you via email :)08:30
dkushwahaphuoc, yea, I am much interested, please notify me08:30
phuocone guy send me a patch in ovs to support NSH08:30
phuochi nnsingh08:32
dkushwahannsingh, hi08:32
nnsinghreservation-vnfm implementation patch is up for community review https://review.openstack.org/#/c/622888/.08:32
nnsinghplease look into it.08:33
phuocnnsingh, you should add blazar client in requirement08:35
phuocsuch as https://github.com/openstack/tacker/blob/master/requirements.txt#L3908:35
*** ralonsoh has joined #openstack-meeting08:36
nnsinghalready added blazar client in requirement.txt08:36
nnsinghBlazar client is only used for functional testing in tacker08:37
nnsinghthat's why added that in test-requirements08:37
dkushwahabhagyashris, do you mind to have a look into that as it seems issue with init_monitoring08:37
*** yamamoto has joined #openstack-meeting08:39
dkushwahannsingh, Post meeting, I will check and ping you after that08:39
nnsinghdkushwaha: ok thank you08:40
bhagyashrisdkushwaha: you mean there issue in patch https://review.openstack.org/#/c/614964/08:40
dkushwahabhagyashris, not that, but only that test case is breaking this time08:41
bhagyashrisdkushwaha: ok I will check08:42
*** iyamahat has joined #openstack-meeting08:42
dkushwahabhagyashris, thanks08:42
dkushwaha#topic Open Discussion08:42
*** openstack changes topic to "Open Discussion (Meeting topic: tacker)"08:42
bhagyashrisThank you for reviewing the patch https://review.openstack.org/#/c/614964/08:43
dkushwahaphuoc, Have you tried VNFFG on multi-site?08:43
bhagyashrisI  have checked release doc and saw:  queens and pike stables branches are also maintained so should we cherry for those stable branches as well08:43
dkushwahathere was a mail regarding VNFFG on multi-site08:44
phuocdkushwaha, I tried with tricircle08:44
*** yamamoto has quit IRC08:44
dkushwahaphuoc, is that working?08:44
phuocI used devstack, I can create a chain08:45
phuocbut when I test functionality, it doesn't work08:45
phuocsorry, I need to go out, see you guys08:46
dkushwahaphuoc, ok, bye08:47
dkushwahabhagyashris, nnsingh do we have something else to talk?08:47
bhagyashrisdkushwaha: yes regarding the change https://review.openstack.org/#/c/61496408:48
bhagyashrisdkushwaha: should we cherry pick that for stable queens and pike08:48
bhagyashrisdkushwaha: as those branches are currently maintained08:49
dkushwahabhagyashris, +1. That should be08:49
bhagyashrisdkushwaha:  ok i will do that for bot the branches08:49
bhagyashrisThank you :)08:50
dkushwahaok, Thanks Folks08:50
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"08:50
openstackMeeting ended Tue Jan 15 08:50:45 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)08:50
openstackMinutes:        http://eavesdrop.openstack.org/meetings/tacker/2019/tacker.2019-01-15-08.01.html08:50
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/tacker/2019/tacker.2019-01-15-08.01.txt08:50
openstackLog:            http://eavesdrop.openstack.org/meetings/tacker/2019/tacker.2019-01-15-08.01.log.html08:50
*** tpatil has quit IRC08:52
*** _alastor_ has joined #openstack-meeting08:53
*** _alastor_ has quit IRC08:58
*** tetsuro has joined #openstack-meeting09:01
*** tetsuro has quit IRC09:02
*** liushuai has joined #openstack-meeting09:08
jiaopengju#startmeeting karbor09:09
openstackMeeting started Tue Jan 15 09:09:08 2019 UTC and is due to finish in 60 minutes.  The chair is jiaopengju. Information about MeetBot at http://wiki.debian.org/MeetBot.09:09
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.09:09
*** openstack changes topic to " (Meeting topic: karbor)"09:09
openstackThe meeting name has been set to 'karbor'09:09
*** Liang__ has quit IRC09:09
jiaopengjuhi, guys, it’s karbor weekly meeting time09:09
jiaopengjuhi liushuai09:09
jiaopengjuwe will start the first topic09:10
jiaopengju#topic 1.2.0 version releases09:10
*** openstack changes topic to "1.2.0 version releases (Meeting topic: karbor)"09:10
jiaopengjuI have submitted a patch about python-karborclient to release the v1.2.0 and it has been merged09:11
jiaopengjuAnd will push patches about karbor and karbor-dashboard in few days09:11
jiaopengjuWe have achieved our Stein milestone2 goals09:12
jiaopengjuBut still some issues about cross-keystone backup and resotre09:12
*** Liang__ has joined #openstack-meeting09:13
liushuaiGot it09:13
jiaopengjuFor example the restore about local vms(image boot), we still need do some dev and more tests about it09:16
jiaopengjuAlso the muti nodes about operation engine, you can do more tests about it09:17
*** hadai has quit IRC09:17
liushuaiyes, we need more tests09:18
jiaopengjuthe operation engine module is not product ready09:18
jiaopengjuThe main tasks before Stein version release, are 1. cross-keystone backup and restore 2. Mutli nodes about operation engine optimization. Please focus on them09:20
jiaopengju#topic Open Discussion09:21
*** openstack changes topic to "Open Discussion (Meeting topic: karbor)"09:21
jiaopengjuliushuai, do you have some topic to disscuss?09:21
jiaopengjuOk, I will end the meeting soon. If someone have topics to disscuss, please ping me in karbor irc channel09:22
jiaopengjuthank you09:23
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"09:23
openstackMeeting ended Tue Jan 15 09:23:18 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)09:23
openstackMinutes:        http://eavesdrop.openstack.org/meetings/karbor/2019/karbor.2019-01-15-09.09.html09:23
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/karbor/2019/karbor.2019-01-15-09.09.txt09:23
openstackLog:            http://eavesdrop.openstack.org/meetings/karbor/2019/karbor.2019-01-15-09.09.log.html09:23
*** liushuai has quit IRC09:25
*** diablo_rojo has quit IRC09:26
*** pcaruana has joined #openstack-meeting09:30
*** ttsiouts has joined #openstack-meeting09:36
*** Liang__ has quit IRC09:37
*** e0ne has joined #openstack-meeting09:38
*** jungleboyj has quit IRC09:39
*** jungleboyj has joined #openstack-meeting09:42
*** bhagyashris has quit IRC09:52
*** masahito has joined #openstack-meeting09:57
*** davidsha has joined #openstack-meeting10:00
*** yamamoto has joined #openstack-meeting10:09
*** yamamoto has quit IRC10:12
*** yamamoto has joined #openstack-meeting10:12
*** lpetrut has joined #openstack-meeting10:39
*** masahito has quit IRC10:47
*** electrofelix has joined #openstack-meeting10:48
*** macza has joined #openstack-meeting10:50
*** brault has joined #openstack-meeting10:54
*** apetrich has quit IRC10:54
*** macza has quit IRC10:54
*** dkushwaha has left #openstack-meeting11:02
*** apetrich has joined #openstack-meeting11:07
*** phuoc has left #openstack-meeting11:12
*** erlon_ has joined #openstack-meeting11:15
*** masahito has joined #openstack-meeting11:31
*** ttsiouts has quit IRC11:37
*** ttsiouts has joined #openstack-meeting11:37
*** arne_wiebalck_ has joined #openstack-meeting11:41
*** ttsiouts has quit IRC11:42
*** apetrich has quit IRC11:44
*** tashiromt has quit IRC11:49
*** apetrich has joined #openstack-meeting12:01
*** arne_wiebalck_ has quit IRC12:16
*** ttsiouts has joined #openstack-meeting12:18
*** radeks has joined #openstack-meeting12:31
*** raildo has joined #openstack-meeting12:34
*** Luzi has joined #openstack-meeting12:41
*** _alastor_ has joined #openstack-meeting12:43
*** _alastor_ has quit IRC12:48
*** gyee has joined #openstack-meeting12:53
*** bbowen has joined #openstack-meeting12:59
*** radeks has quit IRC13:00
*** radeks has joined #openstack-meeting13:01
*** eharney has joined #openstack-meeting13:24
*** radeks has quit IRC13:29
*** gyee has quit IRC13:34
*** rubasov has joined #openstack-meeting13:45
*** enriquetaso has joined #openstack-meeting13:53
*** lajoskatona has joined #openstack-meeting13:54
*** tidwellr has joined #openstack-meeting13:56
*** njohnston has joined #openstack-meeting13:56
*** raildo has quit IRC13:56
*** mlavalle has joined #openstack-meeting13:59
*** boden has joined #openstack-meeting13:59
mlavalle#startmeeting networking14:00
openstackMeeting started Tue Jan 15 14:00:09 2019 UTC and is due to finish in 60 minutes.  The chair is mlavalle. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** openstack changes topic to " (Meeting topic: networking)"14:00
openstackThe meeting name has been set to 'networking'14:00
mlavalleAs usual, today's agenda is in the team's wiki: https://wiki.openstack.org/wiki/Network/Meetings14:02
mlavalle#topic Announcements14:02
*** openstack changes topic to "Announcements (Meeting topic: networking)"14:02
*** arne_wiebalck_ has joined #openstack-meeting14:02
mlavalleThe next milestone is Stein-3, March 4 - 8. That's a little less than a couple of months ago14:03
*** raildo has joined #openstack-meeting14:03
mlavallePlease also remember that there is an OpenStack Foundation directors election going on14:03
mlavalleDeadline to cast votes is this coming Friday 18th14:04
*** sadasu has joined #openstack-meeting14:04
mlavalleMany of you should have received individual emails compelling you to vote14:04
mlavalleAny other announcements?14:04
amotokiregarding Stein-2, we are planning to cut beta releases for stadium projects as we have no beta releases corresponding to neutron stein b1.14:05
amotokiIt would help distributor packaging a lot.14:05
mlavalleamotoki: yeah, great that we are going to do this14:05
amotokiA question is whether we need another neutron stein beta release (b2) along with the above stadium project initial beta.14:05
amotokiwhat do you think?14:05
mlavalleI would say that to be on the safe side, let's do it14:05
mlavallethat way we are 100% sure they are in synch14:06
amotokiperhaps it is better to release them together :)14:06
amotokithanks, I will prepare it tomorrow.14:06
mlavallethank you!14:06
*** efried1 has joined #openstack-meeting14:06
amotokithat's all from me14:07
*** apetrich has quit IRC14:07
*** Liang__ has joined #openstack-meeting14:07
mlavalle#topic Blueprints14:07
*** openstack changes topic to "Blueprints (Meeting topic: networking)"14:07
mlavalleI have roled over the blueprints we are working on to Stein-3: https://launchpad.net/neutron/+milestone/stein-314:08
*** masahito has quit IRC14:08
mlavalleI have a few questions with some blueprints we were tracking during Stein-2:14:08
bcafarellate o/14:08
mlavalleamotoki: can we condier this one done in Stein-2: https://blueprints.launchpad.net/neutron/+spec/neutron-policy-in-code?14:09
mlavalleor should it be rolled over to Stein-314:09
amotokimlavalle: I would like to roll over to Stein-314:09
amotokias neutron-fwaas polcy-in-code hasn't landed yet.14:09
amotokiit is blocked by oslo.privsep now.14:09
mlavalleamotoki: done14:10
*** efried has quit IRC14:10
*** efried1 is now known as efried14:10
*** mriedem has joined #openstack-meeting14:10
mlavalleI don't see hongbin on-line, but I am asking the same question in regards to https://blueprints.launchpad.net/neutron/+spec/ryu-framework-maintenace-transition14:10
mlavalleI'm going to assume he will read the logs and will respond later on14:11
mlavalleDoes anyone else want to comment on an on-going blueprint?14:12
amotokimlavalle: hi thinks it is completed per his response in IRC http://eavesdrop.openstack.org/irclogs/%23openstack-neutron/%23openstack-neutron.2019-01-14.log.html#t2019-01-14T23:57:1014:12
mlavalleamotoki: ahh, cool. Thanks14:12
*** mmethot has joined #openstack-meeting14:12
njohnstonFor bulk port creation speedup, I have just one change outstanding - https://review.openstack.org/#/c/624815/ - that I am still having some issues with.  Did you ever get a chance to look at that mlavalle?14:12
*** apetrich has joined #openstack-meeting14:12
mlavallenjohnston: no, sorry for that. I will take a look today14:13
njohnstonThank you very much mlavalle14:13
mlavalleWe are having a little trouble reviewing code for https://blueprints.launchpad.net/neutron/+spec/port-mirroring-sriov-vf14:14
mlavalleapparently the only active core reviewer in the TaaS project is yamamoto and he was travelling abroad last week14:15
mlavalleI am going to ping him to discuss alternatives14:15
*** psachin has joined #openstack-meeting14:15
mlavalleand probably will ask the technical committee for guidance as to how to proceed14:16
mlavalle#topic Community goals14:17
*** openstack changes topic to "Community goals (Meeting topic: networking)"14:17
mlavalleWe already talked about policy in code14:17
mlavalleanything to be said on Python 3 or pre-upgrade chacks?14:18
mlavalleok, I take that as a no14:19
njohnstonWe'll probably get a better readout on poython3 at the CI meeting in a couple of hours14:19
slaweqpre-upgrade checkes are done IMHO14:19
mlavalleThat's great. thanks14:20
mlavalle#topic Bugs14:20
-amotoki- (1) pending main policy-in-code patches: neutron-fwaas and vmware-nsx14:20
*** openstack changes topic to "Bugs (Meeting topic: networking)"14:20
-amotoki- (2) policy doc reference: dynamic-routing, sfc, bgpvpn, vmware-nsx14:20
-amotoki- note that vmware-nsx is optional of cource. other follow-up can be handled as bugs.14:20
amotokire: policy-in-code, I see two items to complete the blueprint.14:20
slaweqand about python3 we are now a bit blocked because of some other CI issues14:20
amotokiregarding the upgrade check, is anyone interested in implementing actual checks?14:20
slaweqamotoki: I'm not aware of any14:21
amotokiyeah, me too. one thing in my mind is to check fwaas v1 in service_plugins config and alert it.14:21
slaweqamotoki: good idea14:22
slaweqI can do that :)14:22
lajoskatonaamotoki: is there a kind of list what kind of checks to do?14:22
amotokilajoskatona: on what?14:22
lajoskatonaamotoki: upgrade checks14:22
amotokilajoskatona: that's the only one in my mind :p14:23
slaweqlajoskatona: there isn't any list, community goal was to implement CLI tool and "framework" to such checks14:23
amotokiwe can collect potential checks somewhere (etherpad?)14:23
mlavalle yeah, I was about to suggest14:23
lajoskatonaslaweq: ah, ok,14:23
slaweqnow if You have something which You would like to be checked during upgrade, it can be added as separate patch14:23
mlavalleI can send a message to the ML with an etherpad and see if we collect ideas14:24
lajoskatonamlavalle: ++14:24
*** lbragstad has joined #openstack-meeting14:24
mlavalle#action mlavalle to send message to the ML to collect upgrade checks proposals14:24
mlavalleok, moving on14:25
mlavalleLast week, boden was our bugs deputy and he sent yesterday his report to the ML:  http://lists.openstack.org/pipermail/openstack-discuss/2019-January/001704.html14:25
mlavalleI went over the bugs yesterday14:26
mlavalleThis one is high priority: https://bugs.launchpad.net/neutron/+bug/181112614:26
openstackLaunchpad bug 1811126 in neutron "DHCPAgentOVSTestCase.test_stale_metadata_proxy_killed fails with RuntimeError: Stale metadata proxy didn't get killed" [High,Triaged]14:26
mlavalleit's a gate failure14:26
mlavalleslaweq: you are not working on it, are you?14:27
slaweqmlavalle: no14:27
mlavalleok, if no volunteer steps up to the plate, I'll take it14:27
slaweqmlavalle: I can add it to my list but not for this week probably14:27
slaweqI don't think it's most urgent issue which we currently have in CI :)14:27
mlavalleslaweq: yeah, I agree. I just wanted to highlight it in case someone volunteers14:28
mlavalleMost of the rest have owners and I will work on the RFEs this week14:29
mlavalleboden: if you are around, is there anything else you want to highlight?14:30
*** arne_wiebalck_ has quit IRC14:30
mlavalleok, he is probably trying to get his child out of the door to go to school14:31
mlavalleThis week our bugs deputy is njohnston14:31
mlavalleso we are in good hands14:31
mlavalleok, let's move on14:32
mlavalle#topic neutron-lib14:32
*** openstack changes topic to "neutron-lib (Meeting topic: networking)"14:32
mlavalleboden might not be back yet. But before leaving he mentioned to me that the only point we wants to bring up is that he is getting ready for a new release of neutron-lib this week14:33
mlavalleI think we were able to merge the patches he was targeting last week14:34
mlavalle#topic CLI / SDK14:35
*** openstack changes topic to "CLI / SDK (Meeting topic: networking)"14:35
amotokiI have nothing to report here14:35
mlavalleamotoki: I have a question in regards to this RFE: https://bugs.launchpad.net/neutron/+bug/181135214:35
openstackLaunchpad bug 1811352 in neutron "[RFE] Include neutron CLI floatingip port-forwarding support" [Undecided,New]14:35
mlavalleThis should be implemented for openstack client, right?14:36
bcafarelon neutron-lib I think boden was asking for opinions on https://review.openstack.org/#/c/621000/ recently14:36
amotokiIMHO it is better to implement it in OSC14:36
mlavallebcafarel: thanks!14:36
mlavalleamotoki: yeah, that's what I thought. I'll clarify in the RFE14:36
*** masahito has joined #openstack-meeting14:37
amotokiwe support some *neutron* features in neutronclient OSC plugin, but it makes the bar difficult, so I would suggest to go to opensatcksdk and OSC first.14:37
amotokiI will comment it to the bug later.14:37
lajoskatonaamotoki, mlavalle: in that case, if we implement in osc, it can be backported?14:37
mlavallethanks amotoki14:37
amotokilajoskatona: i don't think so as it is a feature14:38
lajoskatonaamotoki: the reported reported for Rocky14:38
amotokilajoskatona: do you mean the server side supports it in rocky?14:38
lajoskatonaso it must be clear for him/her that it will be done on master14:38
lajoskatonaamotoki: no, if I understand well the CLI support for FIP port forwarding14:39
lajoskatonaamotoki: I read again, and perhaps the question is not for rocky, sorry....14:40
mlavallecool, thanks14:40
mlavalle#topic On demand agenda14:40
*** openstack changes topic to "On demand agenda (Meeting topic: networking)"14:40
mlavalleslaweq: you added a topic to the agenda14:40
mlavallethe stage is yours14:40
slaweqthx mlavalle14:40
slaweqI recently found interesting topic on ML14:41
slaweqand I wanted to ask people what do You think about doing something like that in Neutron14:41
slaweqIMO it would be useful to have such possibility to set priorities for some patches and review them first14:41
slaweqespecially when we are close to release deadline or we have some critical gate failures14:42
njohnstonI've been following that ML thread as well; it does seem like it wouldn't be too much overhead.14:42
slaweqhere is example of dashboard with such priorities for cinder: https://tiny.cc/CinderPriorities14:43
njohnstonAnd it's not like all patches would need to be prioritized; only those that deviate from the median urgency level.14:43
slaweqnjohnston: yes, I agree14:43
amotokigenerally I agree it sounds useful. what I am not sure is how we use it.14:43
slaweqamotoki: I was thinking about something like this cinder dashboard14:44
slaweqwhere You can find what patches are most important to review14:44
bodenseems logical as long as we are all on the same page about which/when patches get prioritized14:44
mlavallewho has the right to set priority?14:44
amotokislaweq: do you have a handy link?14:44
slaweqamotoki: link to what?14:44
slaweqmlavalle: it might be configured in gerrit who can set this priorities14:44
amotokihttps://review.openstack.org/#/q/project:openstack/cinder+status:open explains me a lot :)14:45
slaweqit migth be only You or drivers team14:45
mlavalleslaweq: and do you know what convention other teams have adopted?14:45
slaweqI don't think there is any general convention as for now14:45
*** rossella_s has quit IRC14:46
lajoskatonamlavalle: nova for example has an etherpad with a list of patches to review that given week14:46
mlavallethe other question I have is: is there a sense among the team that we are not revieiwing important patches in a timely manner?14:46
mlavallein other words, do we have a problem to fix?14:47
lajoskatonait works like a FIFO, the top items are reviewed and the next batch goes to top next week14:47
lajoskatonaor similar14:47
slaweqmlavalle: I don't think we have problem to fix here, I just though that maybe it could be useful improvement :)14:47
slaweqand wanted to ask for opinions14:47
mlavalleIn principle, I like the idea of the new tool in Gerrit, but do we actually need it?14:47
mlavallein seems low overhead, but there is going to be some overhead anyways14:48
njohnstonWe don't need it, but it might help.  For example, we could put a +2 priority on gate-fix changes, and that would raise awareness of them without a ML message/14:48
lajoskatonanjohnston +14:49
*** masahito has quit IRC14:49
mlavalleok, here's what I propose. Let's find out how other teams are handling it and we revisit next week. does that work?14:50
slaweqso IMO lets think about it for a while and maybe get back to it on next meeting if more people will have some thoughts about it14:50
slaweqYou were faster14:50
mlavallethanks for bringing this up slaweq!14:50
mlavalleanything else we should discuss today?14:51
mlavalleok, thanks for attending14:52
mlavalleHave a great week!14:52
*** boden has left #openstack-meeting14:52
*** artom has quit IRC14:52
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"14:52
openstackMeeting ended Tue Jan 15 14:52:26 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:52
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking/2019/networking.2019-01-15-14.00.html14:52
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking/2019/networking.2019-01-15-14.00.txt14:52
openstackLog:            http://eavesdrop.openstack.org/meetings/networking/2019/networking.2019-01-15-14.00.log.html14:52
*** sadasu has quit IRC14:52
amotokithnx all!14:52
*** tidwellr has left #openstack-meeting14:52
*** artom has joined #openstack-meeting14:56
smcginnisslaweq, amotoki: Was this the link you were looking for? https://tiny.cc/CinderPriorities14:56
slaweqsmcginnis: yes, thx14:56
amotokismcginnis: yes. i saw it somewhere but failed to find it14:57
smcginnisI've added it to the cinder channel topic to make it convenient for folks there. In case you ever need to go looking for it again. :)14:58
*** arne_wiebalck_ has joined #openstack-meeting14:59
*** rossella_s has joined #openstack-meeting14:59
*** arne_wiebalck_ has quit IRC14:59
*** artom has quit IRC15:00
ralonsoh#startmeeting neutron_qos15:00
openstackMeeting started Tue Jan 15 15:00:42 2019 UTC and is due to finish in 60 minutes.  The chair is ralonsoh. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: neutron_qos)"15:00
*** artom has joined #openstack-meeting15:00
openstackThe meeting name has been set to 'neutron_qos'15:00
ralonsohHello everybody15:01
*** a-pugachev has joined #openstack-meeting15:01
ralonsohlet's start15:02
ralonsoh#topic RFEs15:02
*** openstack changes topic to "RFEs (Meeting topic: neutron_qos)"15:02
ralonsoh#link https://bugs.launchpad.net/neutron/+bug/157898915:02
openstackLaunchpad bug 1578989 in neutron "[RFE] Strict minimum bandwidth support (egress)" [Wishlist,In progress] - Assigned to Bence Romsics (bence-romsics)15:02
ralonsohLet me write first the links15:02
*** Bhujay has quit IRC15:02
ralonsoh#link https://review.openstack.org/#/q/status:open+project:openstack/neutron+branch:master+topic:minimum-bandwidth-allocation-placement-api15:02
ralonsoh#link https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:master+topic:bp/bandwidth-resource-provider15:02
ralonsoh#link https://review.openstack.org/#/q/topic:minimum-bandwidth-allocation-placement-api+(status:open+OR+status:merged)+project:openstack/tempest15:02
ralonsohfor nova, neutron and tempest15:02
ralonsohrubasov, lajoskatona please, updates?15:02
rubasovyes we have some15:02
rubasovif anybody is interested about this: https://etherpad.openstack.org/p/bandwidth-way-forward15:03
rubasovfeel free to join on Friday15:03
rubasovthe topics are mostly about the nova side of the feature15:03
mlavallerubasov: that doesn't affect our plans, right?15:04
rubasovbut depending on directions taken it may have a few consequences on neutron work too15:04
mlavalleI mean Neutron plans15:04
rubasovmlavalle: not too deeply iiuc15:04
mlavalleyes, that's my understanding15:04
rubasovthere may be a need to control a neutron extension standalone15:05
rubasovbut not sure right now15:05
ralonsohwhat's the problem with bward compatibility with SRIOV ports?15:06
rubasovralonsoh: basically that what we had before (guarantee on dataplane but not in placement) allowed an inconsistent resource view15:07
rubasovand now if we want to enforce the consistency of the resource view it's harder to not break what we had in neutron only15:07
lajoskatonaralonsoh: here I think it is summarized quite well by gibi: https://etherpad.openstack.org/p/bandwidth-way-forward15:07
rubasovnot impossible but significantly harder15:07
ralonsohbut you mean if you update the controller to newer version15:07
rubasovralonsoh: yes15:08
ralonsohbut I though that kind of updates were going to be send by neutron-server during the start process15:08
ralonsohthe ml2 mech driver should be in charge of, during the boot process, to read the current status and update the current BW available15:09
ralonsohin this case, to read the already assigned BW and update the placement DB15:10
rubasovone problem for example: what do we do if we already overallocated the guaranteed min bw on host when we upgrade to a control that supports guarantee in placement too?15:10
ralonsohrubasov, good question15:10
rubasovs/control/control plane/15:10
ralonsohthat's easy: you update placement DB and set available BW to negative number15:11
rubasovralonsoh: :-)15:11
rubasovralonsoh: I don't think placement allows a negative inventory15:11
ralonsohOr in this case, placement or neutron-server should raise an exception15:12
ralonsohif you want placement enforcement AND you over provisioned a host, this is your fault15:12
ralonsoh(administrator fault)15:12
rubasovthat's definitely one option, but that's the case where we would break backwards compatibility15:13
rubasovsince this was working to some extent before (on the api at least)15:13
ralonsohwell, IMO, this is not breaking backwards compatibility15:13
mlavalleso in this context backs compatibility means the previous status quo15:13
rubasovI also hope this will be the general consensus of the friday meeting15:14
ralonsohrubasov, you are right, I'll join this meeting15:14
mlavalleralonsoh: yeah, there is a bit of nomencalture wiggle room here15:14
rubasovyou're welcome15:14
rubasovit'll be a hangouts call15:15
ralonsohis this the biggest architectural problem you have now with this feature?15:15
rubasovone of them, I think all currrent problems are listed in the etherpad15:15
rubasovthe other is: if the nova support is not complete in stein can we still turn it on somehow, so people can get to try it15:16
rubasovlikely server boot and stop will work, but migrate may not in stein15:17
ralonsohbut you almost have the APIs between nova and neutron working15:18
rubasovyes, I think the neutron part is much more sure to get completed in stein15:18
rubasovand the apis between them too15:18
*** ttsiouts has quit IRC15:19
ralonsohso far, all placement resources are correctly passed between projects15:19
ralonsohand in Nova there are some "corner cases" to be handle15:19
*** ttsiouts has joined #openstack-meeting15:19
rubasovthat's a good summary15:20
ralonsohregarding to neutron/tempest patches15:20
rubasovI have some fresh code15:20
rubasovthis patch series15:20
rubasovis now getting close to be able to correct transient errors of the placement sync process15:21
rubasovif you have time please review the agent extension patches15:21
* mlavalle added it to his pile15:21
ralonsohand this one too: https://review.openstack.org/#/c/588319/15:22
rubasovsoon we'll also try lajoskatona's end-to-end test against this patch series15:22
ralonsohthis one is mandatory15:22
rubasovralonsoh: yes, that's also reviewable15:22
lajoskatonayeah, to see if the tempest scenario really works :-)15:22
rubasovthe agent extension has its neutron and neutron-lib side of course15:22
ralonsohsure, on the depends-on15:23
rubasovlajoskatona: do you have some patches to add?15:23
*** Liang__ has quit IRC15:23
*** ttsiouts has quit IRC15:24
lajoskatonayeah, I think nothing special, the tempest part is under review15:24
rubasovthen that's all from me now15:24
*** efried has quit IRC15:24
lajoskatonaI have to clear it with tempest folks, how they expect the patches15:24
lajoskatonayeah, I think so, on Friday we will see how to continue15:25
*** efried has joined #openstack-meeting15:25
rubasovone more bit15:25
rubasovthere's a mail thread about the friday meeting15:25
rubasovif there's any change in the plans (I hope not anymore) it'll be advertised there15:26
ralonsohsomething else?15:26
ralonsohOK, thanks guys! Of course in https://etherpad.openstack.org/p/neutron_qos_meeting_chair we have the links.15:27
ralonsohnext one15:27
ralonsoh#link https://bugs.launchpad.net/neutron/+bug/156096315:27
openstackLaunchpad bug 1560963 in neutron "[RFE] Minimum bandwidth support (egress)" [Wishlist,In progress] - Assigned to Rodolfo Alonso (rodolfo-alonso-hernandez)15:27
ralonsoh#link https://review.openstack.org/#/q/topic:bug/1560963+(status:open)15:27
ralonsohTwo parts:15:27
*** hongbin has joined #openstack-meeting15:28
*** ttsiouts has joined #openstack-meeting15:28
ralonsohfirst the non-tunneled traffic: https://review.openstack.org/#/c/406841/15:28
ralonsohsecond one: the rest of the patches15:28
ralonsoh(the last patch is still not upstream)15:28
ralonsohreviews are welcome15:28
mlavalleso they are ready for reviews then15:29
ralonsohall of them. The pyroute2 patches are failing because a missing patch in neutron-lib15:29
ralonsohand that's all for this one15:30
ralonsohnext one15:30
ralonsoh#link https://bugs.launchpad.net/neutron/+bug/179692515:30
openstackLaunchpad bug 1796925 in neutron "[RFE] port forwarding floating IP QoS" [Wishlist,New] - Assigned to LIU Yulong (dragon889)15:30
*** TxGirlGeek has joined #openstack-meeting15:30
ralonsohthe RFE was approved15:30
ralonsohwaiting for the spec/patches15:30
ralonsohI don't see LIU here15:31
mlavalleslaweq: do you have a meeting with liyyulong today?15:31
slaweqmlavalle: tomorow morning my time15:31
*** _alastor_ has joined #openstack-meeting15:31
mlavalleslaweq: would you ask him about this RFE?15:31
ralonsohthank you15:32
ralonsohnext one15:32
openstackLaunchpad bug 1727578 in neutron "[RFE]Support apply qos policy in VPN service" [Wishlist,Triaged]15:32
ralonsoh#link https://bugs.launchpad.net/neutron/+bug/172757815:32
ralonsohwe have the spec15:32
ralonsoh#link https://review.openstack.org/#/c/531074/15:33
ralonsohbut there is no progress on this one15:33
mlavalleI thought he had re-started working on it15:33
ralonsohthat's perfect15:33
mlavallein late December15:33
mlavallethat's waht we reported internally15:34
ralonsohso we'll see updates soon (maybe)15:34
ralonsohOk, no more approved or active RFEs15:34
mlavallehe finsihed most of what he's been doing in Ocatvia15:34
ralonsohAm I missing any other one?15:35
mlavallehang on15:35
mlavalleI'll re-start this one this week: https://review.openstack.org/#/c/613820/15:36
ralonsoh#link https://bugs.launchpad.net/neutron/+bug/177762715:36
openstackLaunchpad bug 1777627 in neutron "RFE: QoS – rule's management (set,delete, show…) requires <qos-policy> parameter in addition to <rule-id>" [Wishlist,In progress] - Assigned to Miguel Lavalle (minsel)15:36
ralonsohany update on the patch?15:36
*** efried has quit IRC15:36
mlavalleI need to deploy it in my dev system and address the comments15:37
*** efried has joined #openstack-meeting15:37
mlavalleshouldn't be too difficult15:37
mlavallerebasing + deploying + working on comments15:37
ralonsohadded to my review pile and to the etherpad (https://etherpad.openstack.org/p/neutron_qos_meeting_chair)15:38
ralonsohok, let's move on15:38
ralonsoh#topic Bugs15:39
*** openstack changes topic to "Bugs (Meeting topic: neutron_qos)"15:39
ralonsoh#link https://bugs.launchpad.net/neutron/+bug/181002515:39
openstackLaunchpad bug 1810025 in neutron "L2 agent do not clear QoS rules after restart" [Medium,In progress] - Assigned to Chengqian Liu (liuchengqian90)15:39
ralonsohpatch: https://review.openstack.org/#/c/627779/15:39
*** efried has quit IRC15:40
ralonsohthere is one small concern about using a class member15:40
ralonsohbut the patch looks good15:40
ralonsohreviews are welcome15:40
ralonsohnext one15:41
ralonsoh#link https://bugs.launchpad.net/neutron/+bug/180949715:41
openstackLaunchpad bug 1809497 in neutron "_get_filterid_for_ip can generate an UnboundLocalError" [High,Confirmed]15:41
ralonsohis anyone here reviewing this one?15:41
ralonsohif not, I'll take a look at this one tomorrow15:41
slaweqI think I did patch for it15:41
slaweqbut I wasn't aware of bug report so I didn't link it15:42
ralonsohOK, so this was the problem15:42
ralonsohcan you update the patch link?15:42
mlavalleso, let's link it15:42
slaweqmlavalle: yep, I'm doing it right now15:43
ralonsohperfect, thanks15:43
ralonsohnext one15:43
ralonsoh#link https://bugs.launchpad.net/neutron/+bug/178400615:43
openstackLaunchpad bug 1784006 in neutron "Instances miss neutron QoS on their ports after unrescue and soft reboot" [Medium,Confirmed] - Assigned to Miguel Lavalle (minsel)15:43
*** mjturek has joined #openstack-meeting15:44
ralonsohmlavalle, ?15:44
*** Luzi has quit IRC15:44
mlavalledidn't make progress here15:44
ralonsohno problem15:44
ralonsohlast one15:45
ralonsoh#link https://bugs.launchpad.net/neutron/+bug/178518915:45
openstackLaunchpad bug 1785189 in neutron "Floatingip and router bandwidth speed limit failure" [Undecided,In progress] - Assigned to Brian Haley (brian-haley)15:45
ralonsohpatch: https://review.openstack.org/#/c/596637/15:45
ralonsohwaiting for Lu replies15:46
ralonsohmlavalle, if next time (in two weeks) there are no updates, I can take it15:46
ralonsohI don't have more bugs in my list15:47
ralonsohAm I missing something?15:47
ralonsohok, next section15:48
ralonsoh#topic Open Discussion15:48
*** openstack changes topic to "Open Discussion (Meeting topic: neutron_qos)"15:48
ralonsohplease, any update/comment?15:48
ralonsoh3 2 115:49
ralonsohthank you all for attending15:49
rubasovthank you guys15:49
ralonsohsee you in two weeks (and this friday)15:49
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"15:50
openstackMeeting ended Tue Jan 15 15:49:59 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:50
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_qos/2019/neutron_qos.2019-01-15-15.00.html15:50
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_qos/2019/neutron_qos.2019-01-15-15.00.txt15:50
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_qos/2019/neutron_qos.2019-01-15-15.00.log.html15:50
*** lajoskatona has left #openstack-meeting15:50
*** efried has joined #openstack-meeting15:53
*** radeks has joined #openstack-meeting15:57
slaweq#startmeeting neutron_ci16:00
openstackMeeting started Tue Jan 15 16:00:30 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
slaweqsorry, I had phone call16:03
slaweqok, lets start16:03
slaweq#topic Actions from previous meetings16:03
*** openstack changes topic to "Actions from previous meetings (Meeting topic: neutron_ci)"16:03
slaweqfirst one is:16:03
slaweqmlavalle will continue debugging trunk tests failures in multinode dvr env16:03
mlavalleI've been working on that16:03
*** radeks has quit IRC16:04
mlavalleI took a little detour after you pinged this past friday16:04
mlavalleI think you read my comments in the ssh bug16:04
slaweqmlavalle: You are talking about this one https://bugs.launchpad.net/neutron/+bug/1811515 right?16:05
openstackLaunchpad bug 1811515 in neutron "SSH to FIP fails in CI jobs" [Critical,Confirmed]16:05
slaweqyes, I read it16:05
mlavalleso I decided to contnue debugging the trunk test case further16:06
slaweqbut this bug is not related to trunk test only16:06
slaweqit happens in many tests currently16:06
mlavalleI know16:06
mlavalleI just assumed that you were going to contnue debugging with a focus on the puroute2 failure16:07
slaweqyes, I'm trying that16:07
slaweqand ralonsoh is helping me too16:07
mlavalleor you want me to stop working on the trunk case and focus on this one?16:07
slaweqI think we should first fix this issue with many tests failing16:08
slaweqand then we can focus on trunk port issue again16:09
slaweqbecause currently I think that this issue with (probably) pyroute2 is blocking everything16:09
mlavalleok, how can I help?16:09
slaweqI don't know16:11
slaweqif You have any ideas how to debug what exactly happens in pyroute lib, that would be great16:11
*** e0ne has quit IRC16:11
slaweqI couldn't reproduce this issue on my local devstack16:11
mlavalleslaweq: ok, I'll try to take a stab16:12
slaweqand debugging in gate what's going on in lib installed from pypi is impossible16:12
slaweqat least I don't know about any way how to do it16:12
slaweqso if anyone have any ideas about how to fix/debug this issue, that would be great16:13
*** eharney has quit IRC16:14
slaweqmriedem asked for e-r query for that bug as it happens a lot in CI16:14
slaweqso I will do it today or tomorrow16:14
slawequnless there is anyone else who want to do it16:14
slaweq#action slaweq to make e-r query for bug 181151516:15
openstackbug 1811515 in neutron "SSH to FIP fails in CI jobs" [Critical,Confirmed] https://launchpad.net/bugs/181151516:15
slaweqok, so I think we can move to the next action then16:15
slaweqslaweq to debug problems with ssh to vm in tempest tests16:16
slaweqand this is basically related to the same bug which we already discussed16:16
slaweqany questions/something to add?16:17
slaweqor can we move on?16:17
mriedemi'm trying to get a good e-r query on that bug,16:17
mriedembut i can't find anything that gets 100% failed jobs16:18
mriedemso those errors in the l3 agent log must also show up quite a bit in successful jobs16:18
slaweqmriedem: problem is that this error in logs is not causing failures always16:18
slaweqyes, in some cases this error appears e.g. during remove router or something like that and tests are fine16:19
slaweqbut sometimes it happens in adding interface or configuring some ip address in namespace and then test or some tests fails16:19
*** munimeha1 has joined #openstack-meeting16:20
mriedemcould any post-failure logging could be added to tempest to help identify the fault?16:20
mriedemlike, is there something about the router or floating ip resource that would indicate it's broken?16:20
slaweqI don't know, basically if it's broken connectivity to FIP is not working16:21
haleybperhaps sometimes the floating ip status is ERROR?  guess it depends on when the failure happens16:22
slaweqhaleyb: maybe but I didn't check that16:23
haleybi also wonder if router status is ACTIVE?16:25
slaweqhaleyb: IMHO it will depend on place where failure happens16:26
slaweqthere is no one strict pattern for that IMHO16:26
haleybslaweq: right.  i know we made the l3-agent better at recovering and retrying things on failure, but status might not reflect that exactly16:28
slaweqmriedem: isn't query like http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%5C%22OSError%3A%20%5BErrno%209%5D%20Bad%20file%20descriptor%5C%22%20AND%20build_status%3A%5C%22FAILURE%5C%22 enough?16:28
mriedemwe normally avoid explicitly adding build_status in the queries16:30
slaweqahh, ok16:30
slaweqso it might be hard16:30
mriedembecause if that error message shows up a lot in non-failure jobs, we could be saying failed jobs are a result of this bug, which they might not be16:30
*** a-pugachev has quit IRC16:30
mriedemi.e. it's not good to have errors in the logs if there aren't real errors :)16:30
slaweqmriedem: I know but in this case it is real error16:31
mriedemwhich is why i was suggesting maybe adding some post-failure logging if possible to try and identify this case16:31
slaweqit looks that it is some race condition16:31
*** a-pugachev has joined #openstack-meeting16:32
slaweqmriedem: I can take a look at some of such failures if there will be some same pattern for all of them but I'm affraid that it will be hard16:33
slaweqanything else mriedem or can we move on?16:35
*** dklyle has joined #openstack-meeting16:35
mriedemhas anyone identified when this started failing?16:35
mriedemto see if new dependencies are being used which might cause a regression? or change to neutron?16:35
mriedemseems like it started around jan 9?16:35
mriedemanyway, you can move on16:36
mriedem^ seems like a good suspect16:36
slaweqI don't think so as it's failing in completly different module16:37
mriedemprivsep is related in the failures i'm seeing though16:37
slaweqyes, it is in module which uses privsep, but different one16:37
mriedemwas jan 916:39
mriedemnew privsep release16:39
mriedemanyway, i'll dump notes in the bug report16:39
slaweqmriedem: ok, thx16:39
hongbinwe could revert those suspitous commits and recheck a few times , which might be able to locate the error16:40
slaweqmriedem: it might be that this new privsep version raised one more issue in our code16:40
slaweqhongbin: yes, good point16:40
slaweqI will do it just after the meeting16:40
slaweq#action slaweq to check if oslo.privsep < 1.31.0 will help to workaround issue with SSH to FIP16:41
slaweqok, lets move on to the next topics then16:41
slaweqdo You agree?16:41
mlavallemriedem: thanks for the inouts. We'll look at it16:42
mlavalleslaweq: yes, let's move on16:42
slaweqyes, thx mriedem for all help with this one16:42
slaweqslaweq: ok, thx16:42
slaweq#topic Python 316:42
*** openstack changes topic to "Python 3 (Meeting topic: neutron_ci)"16:42
slaweqEtherpad: https://etherpad.openstack.org/p/neutron_ci_python316:42
slaweqI don't have anythin new in fact here16:43
slaweqwe have few patches to convert jobs to python3 (and zuulv3) but all of them are stuck in gate for last week16:43
slaweqdo You have anything to add here?16:43
*** ttsiouts has quit IRC16:44
njohnstonFrom a python3 perspective, since tempest has switched to python3 by default do the remaining tempest jobs derive that by default?16:44
*** ttsiouts has joined #openstack-meeting16:44
slaweqnjohnston: tempest switched to py3? Do You have link to patch?16:45
njohnstonHmm, I thought I remembered seeing that on the ML while I was out on vacation, but perhaps I dreamed it because I can't find it in the ML archives now16:46
njohnstonso never mind :-)16:46
bcafarelI remember something similar too16:46
slaweqI remember only about devstack switch16:46
njohnstonperhaps that is what I am thinking of16:47
slaweq^^ is it what You were thinking of?16:47
bcafarelaaah yes I think it is16:47
bcafarel(well at least for me)16:47
*** iyamahat has quit IRC16:47
njohnstonyes that was it16:48
slaweqok, so it's about change in devstack16:48
slaweqwe still need to configure our jobs to be run on python3 :)16:49
*** yamahata has quit IRC16:49
*** ttsiouts has quit IRC16:50
slaweqok, lets move on then16:50
slaweq#topic Grafana16:50
*** openstack changes topic to "Grafana (Meeting topic: neutron_ci)"16:50
slaweq#link: http://grafana.openstack.org/dashboard/db/neutron-failure-rate16:50
bcafarelanother quick py3 item for functional tests, I saw one green func/py3 result recently, but the string exception thingy still happens most of the time :/ so we are close but not there yet16:51
slaweqbcafarel: yes, I wanted to take a look at it again but I didn't have time yet16:51
bcafarelI think we are at the point where it passes depending on the generated log and moon phase :)16:52
bcafarelas in a few additional lines trigger the string exception16:52
slaweqbcafarel: yeah, moon phase might be key here ;)16:52
slaweqspeaking about grafana, it doesn't look good, especially in tempest and scenario jobs but this is related to our main issue which we have currently and which was already discussed16:53
mlavalleso let's not spend time on this16:53
slaweqother than that I think it's not bad with fullstack/functional/other jobs16:53
mlavalleunless you want to highlight something else16:53
slaweqin fact I don't have anything else for today's meeting16:54
mlavalleok so before we leave16:54
mlavallelet's agree on a set of marching orders16:54
slaweqwe have 1 main issue which we need to solve and than we will be able to continue work on other things16:54
mlavalle1) slaweq to propose reverts16:54
slaweqbut it will be DNM patch at least for now16:55
slaweqjust to test if that helps or not16:55
mlavalleI know16:55
*** yamamoto has quit IRC16:55
mlavalle2) recheck reverts to see if we get evidence of fixing the problem16:56
mlavalledo you agree with Matts perception that it started showing up around Jan 9?16:56
slaweqmore or less16:57
slaweqI see some failures on 6th also16:57
slaweqbut then there wasn't any hits16:57
slaweqand I know that we reverted change which bumped privsep lib16:57
mlavalleare there jobs where you see the problem more frequently?16:57
slaweqso it might be related and fit to this timeline :)16:57
slaweqI think that it's most often in neutron-tempest-dvr and neutron-tempest-linuxbridge jobs16:58
slaweqthis neutron-tempest-dvr for sure16:58
slaweqand IIRC it's running python 3 already16:59
mlavalleslaweq: would you post a few examples in the bug?16:59
slaweqbut I don't think it's the reason16:59
slaweqfew examples of failures? yes I can16:59
slaweq#action slaweq to post more examples of failiures in bug 181151517:00
openstackbug 1811515 in neutron "SSH to FIP fails in CI jobs" [Critical,Confirmed] https://launchpad.net/bugs/181151517:00
mlavalleslaweq: before you leave for good tonight, please ping me so we synch up17:00
slaweqmlavalle: ok17:00
slaweqI will17:00
slaweqwe need to finish now17:00
slaweqthx for attending17:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"17:00
openstackMeeting ended Tue Jan 15 17:00:24 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_ci/2019/neutron_ci.2019-01-15-16.00.html17:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_ci/2019/neutron_ci.2019-01-15-16.00.txt17:00
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_ci/2019/neutron_ci.2019-01-15-16.00.log.html17:00
*** njohnston has left #openstack-meeting17:00
*** mlavalle has left #openstack-meeting17:01
clarkbslaweq I was going to say thank you for debugging all the gate failures!17:02
slaweqclarkb: thx, that's my job :)17:04
*** a-pugachev has quit IRC17:06
*** iyamahat has joined #openstack-meeting17:06
*** macza has joined #openstack-meeting17:08
*** davidsha has quit IRC17:10
*** eharney has joined #openstack-meeting17:13
*** macza_ has joined #openstack-meeting17:13
*** e0ne has joined #openstack-meeting17:13
*** macza has quit IRC17:14
clarkbslaweq: when all of this is sorted out we should probably take a moment to see if we can improve our ability to catch these bugs early before they merge17:19
*** arne_wiebalck_ has joined #openstack-meeting17:19
*** arne_wiebalck_ has quit IRC17:19
clarkbI'm happy to help with that if there are infra or zuul things that will help17:19
*** lbragstad has quit IRC17:22
*** yamahata has joined #openstack-meeting17:24
*** lbragstad has joined #openstack-meeting17:26
*** e0ne has quit IRC17:28
*** lbragstad has quit IRC17:33
*** lbragstad has joined #openstack-meeting17:33
*** mattw4 has joined #openstack-meeting17:36
*** ekcs has joined #openstack-meeting17:37
*** ekcs has quit IRC17:37
*** jamesmcarthur has joined #openstack-meeting17:40
*** yamamoto has joined #openstack-meeting17:45
*** ttsiouts has joined #openstack-meeting17:47
*** yamamoto has quit IRC17:48
*** yamamoto has joined #openstack-meeting17:48
*** yamamoto has quit IRC17:48
*** yamamoto has joined #openstack-meeting17:53
*** lbragstad is now known as lbragstad_lunch17:58
*** pcaruana has quit IRC18:01
*** yamamoto has quit IRC18:01
*** psachin has quit IRC18:03
*** TxGirlGeek has quit IRC18:04
*** igordc has joined #openstack-meeting18:05
*** TxGirlGeek has joined #openstack-meeting18:07
*** yamamoto has joined #openstack-meeting18:07
*** diablo_rojo has joined #openstack-meeting18:12
*** wwriverrat has joined #openstack-meeting18:12
*** anteaya has joined #openstack-meeting18:13
*** brault has quit IRC18:14
*** brault has joined #openstack-meeting18:15
*** jamesmcarthur has quit IRC18:18
*** yamamoto has quit IRC18:19
*** jamesmcarthur has joined #openstack-meeting18:19
*** jamesmcarthur has quit IRC18:20
*** brault has quit IRC18:20
*** jamesmcarthur has joined #openstack-meeting18:21
*** efried has quit IRC18:21
*** yamamoto has joined #openstack-meeting18:23
*** efried has joined #openstack-meeting18:26
*** yamamoto has quit IRC18:32
*** yamamoto has joined #openstack-meeting18:33
*** yamamoto has quit IRC18:36
*** yamamoto has joined #openstack-meeting18:37
*** ralonsoh has quit IRC18:38
*** yamamoto has quit IRC18:45
*** yamamoto has joined #openstack-meeting18:45
*** kopecmartin is now known as kopecmartin|off18:52
*** lbragstad_lunch is now known as lbragstad18:52
*** eharney has quit IRC18:54
*** Shrews has joined #openstack-meeting18:55
*** yamamoto has quit IRC18:59
*** jamesmcarthur has quit IRC19:00
clarkbHello it is meeting time if I got my days right19:01
*** jamesmcarthur has joined #openstack-meeting19:01
clarkbSorry I'm slightly distracted by gerrit war build publishing but we'll get started19:01
clarkbanyone else here for the infra meeting?19:01
clarkb#startmeeting infra19:01
openstackMeeting started Tue Jan 15 19:01:48 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
gary_perkinso/ Hi!19:02
fungii'm around, just multi-tasking19:02
clarkb#link https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting#Agenda_for_next_meeting19:03
clarkbI've undistracted myselc19:03
clarkb#topic Announcements19:03
*** openstack changes topic to "Announcements (Meeting topic: infra)"19:03
clarkbFirst announcement is that fungi and I are in meetings next week and won't be able to pay attention to this meeting19:04
fungiand i'm on vacation the week after19:04
clarkbWe'll need a volunteer to chair the meeting. I should be able to chair the week after though19:04
clarkbThe other announcement (which I added after the email went out) is that openstack board election is happening now19:04
clarkbdon't forget to vote and if you didn't get a ballot but expected one please reach out and we'll see what is going on19:05
fungior do like the major networks and play reruns from 2012 ci program meetings19:05
*** yamamoto has joined #openstack-meeting19:05
clarkb#topic Actions from last meeting19:06
*** openstack changes topic to "Actions from last meeting (Meeting topic: infra)"19:06
clarkb#link http://eavesdrop.openstack.org/meetings/infra/2019/infra.2019-01-08-19.01.txt minutes from last meeting19:06
clarkbOne action was recorded and that was corvus to update the dns server documentation19:06
clarkbfungi: ^ I think you were involved in that too19:06
corvusi did not do it19:06
clarkbcorvus: fungi: is there a change that has merged or needs review yet?19:06
corvusi have not forgotten, but omg so many things19:07
fungioh, yeah i just wasn't entirely sure what needed to go in there19:07
*** e0ne has joined #openstack-meeting19:07
fungii guess it's stripping out the puppetish bits19:07
clarkb#topic Specs approval19:08
*** openstack changes topic to "Specs approval (Meeting topic: infra)"19:08
clarkbI actually pulled the anomoly detection change off the list hee due to the omg so many things problem19:08
clarkbare there any urgent spec related items we should consider before moving on though?19:08
*** yamamoto has quit IRC19:09
*** eharney has joined #openstack-meeting19:09
clarkbsounds like no19:09
clarkb#topic Priority Efforts19:10
*** openstack changes topic to "Priority Efforts (Meeting topic: infra)"19:10
clarkb#topic Update Configuration Management19:10
*** openstack changes topic to "Update Configuration Management (Meeting topic: infra)"19:10
clarkbThis is where many of the omg things have happened19:10
clarkbin the last week we've started to build out a real docker image publishing and promotion pipeline19:10
clarkbcorvus: mordred ^ what should we all know about that?19:10
*** lbragstad has quit IRC19:10
fungiit's amazing. i'm reviewing more of it while i type this19:10
corvusi'm going to move it to zuul-jobs today19:11
*** lbragstad has joined #openstack-meeting19:11
mordredyah - it's the best.19:11
clarkbup to and including the bazel memory problems :)19:11
corvusand then write up a ml post about it and send it to openstack-discuss (so that openstack folks know they can use it), openstack-infra (so that we can use it for the container stuff), and zuul-discuss (so that the world knows about the promote pattern and the new roles)19:11
corvusso i guess, probably 3 ml posts :)19:12
fungibut maybe you can copy between them some19:12
clarkbOn the puppet 4 side of things cmurphy has a change up to flip one server over then another to flip all the servers over to puppet 4. I have unfortunately not had time to look at that as gerrit updates have distracted me. However I think this is also exciting and we should get around to review those changes topic:puppet-419:13
corvusi sure hope so19:13
mordredI expect three custom written posts19:13
mordredclarkb: ++19:13
clarkbcmurphy: also in writing that last statement I realize that maybe we want to do an ubuntu server to puppet-4 then a centos7 server then the rest (since those are slightly different)19:13
clarkbcmurphy: I can leave a note in review after the meeting too19:14
mordredclarkb: good point19:15
clarkbare there any other changes or topics within this space we should be aware of or reviewing?19:15
*** yamamoto has joined #openstack-meeting19:16
clarkbsounds like no. We'll focus on rolling out the mat for puppet-4 and docker then19:17
fungithe storyboard container stuff mordred started, maybe?19:17
clarkbdid that get picked up again?19:17
mordredI'd like to change approaches there19:17
mordredI guess it's worth talking about ...19:17
clarkbgo for it19:17
mordredwith the work we've done on gitea - and now on gerrit and the other things ...19:17
mordredI believe the pbrx approach is the wrong approach19:18
mordredI want to make a bindep builder image that we publish that can be used in other multi-stage dockerfiles19:18
mordredand then make dockerfiles for storyboard and zuul and friends19:18
clarkbthe benefit there is being able to more completely control what goes into the final image?19:18
mordredthere's too much surrounding toolchain that understand working with dockerfiles - I don't thnik we get enough benefit from pbrx19:18
fungiis this because of the non-python bits?19:19
mordredclarkb: that and just not being super different/weird - it lets people more easily rebuild images from source in places that assume source repos have dockerfiles19:19
fungi(javascript, images, css...)19:19
mordrednot really ... those are actually fairly decently handled19:19
clarkbI do like the idea of a consistent process for gerrit and storyboard and grafana and zuul19:19
mordredit's just that it's divergent tooling for not enough benefit19:19
mordredclarkb: ++19:19
mordredthat's the real key19:20
mordredanywho - I'll try to get a bindep image cranked up RSN19:20
*** lbragstad has quit IRC19:20
corvuswe'll end with a nice collection of dockerfiles, and docker-compose files19:20
corvusmight make local testing easier, but i've learned never to lead with that promise :)19:21
*** lbragstad has joined #openstack-meeting19:21
clarkb#topic Storyboard19:21
*** openstack changes topic to "Storyboard (Meeting topic: infra)"19:21
clarkbseems like that was a good lead into this topic19:21
clarkbfungi: still fighting openid?19:22
fungiif fighting is defined as caught up in start-of-year paperwork then sure ;)19:22
fungiat least since last week, the server is up as storyboard-dev01.opendev.org and it's serving a storyboard-dev.openstack.org vhost successfully, but logging in leads to exceptions in the oauth module19:23
fungisomething about an invalid redirect (on returning from the provider)19:23
fungiruled out dns not being canonical, and ssl snakeoil cert not having a matching cn for the site name19:24
clarkbfungi: maybe you can share the ip addr? I may have time to take a look at that when waiting for puppet runs later today19:24
fungiit's in dns already as storyboard-dev01.opendev.org19:24
clarkbset it up in /etc/hosts and see what firefox browser debuger says19:24
clarkboh perfect19:24
fungiso just copy one of those addresses into your /etc/hosts19:24
fungiand yeah, that's how i was testing19:24
fungii think next steps are to 1. compare pip freeze between the old and new servers, 2. try to sidexside diff the http parameters in the urls for a working and failing redirect19:25
clarkbya I was thinking I'd work on 2.19:25
fungione other note, they're both sharing the same trove instance at the moment, not sure if that could be causing an issue but i wouldn't be surprised if writes from one were wonky/colliding in the other at times19:26
fungibut that seems unlikely to be what's surfacing this particular oauth/openid exception19:26
clarkbgood to know though19:27
clarkbany other storyboard topics before we talk opendev?19:27
fungithe stestr switch landed19:27
fungiother than that, nothing i'm aware of19:28
clarkb#topic OpenDev19:28
*** openstack changes topic to "OpenDev (Meeting topic: infra)"19:28
clarkbsome of the omg things happened in opendev land too19:28
* diablo_rojo missed my window to mention https://review.openstack.org/#/c/555397/19:28
clarkbdiablo_rojo: looks like it needs a recehck?19:29
clarkb(or maybe debugging)19:29
clarkb#link https://opendev.org/walkthrough.html k8s walkthrough19:29
clarkbif you missed it corvus recordred the k8s walkthrough we did last wee and you can find it at ^19:29
diablo_rojoYeah was roing to do a little of both.19:29
clarkbAdditionally I cleaned out all the old dns servers and we are now running on opendev.org name servers \o/19:30
clarkbThere are discussions around hosting zuul.opendev.org to enable some zuul multitenancy on our instance starting up. Let us know if you are interested in this (in particular zuul itself would like a tenant as would kata)19:30
clarkbOther than that I think the big next item is making a decision on cert management for the new domain. ianw if you get a chance can you get that spec rebased?19:32
clarkbhttps://review.openstack.org/#/c/587283/ specifically19:32
clarkbAny other opendev topics to bring up before we move on?19:33
fungisigns point to no19:34
clarkb#topic General Topics19:34
*** openstack changes topic to "General Topics (Meeting topic: infra)"19:34
ianwclarkb: yep, i think a POC would be great there and will try to get something going ...19:34
clarkbianw: thanks!19:35
* Shrews shakes fungi for more wisdom19:35
fungiShrews: outlook cloudy?19:35
clarkbOk I sent email about the PTG. Gave a rough outline of what I thought I'd ask for and didn't hear any dissent19:35
clarkbI've got to get that in by Sunday so I'll probably just go ahead and do it hwne I'm waiting for puppet to run one of these times19:35
clarkbto tl;dr Infra would like a room for ~2 days and ~10 people. I know this is all handwavy at this point and I'm sure our planners understand (right diablo_rojo ?)19:36
clarkbI expect we'll be able to use that time to work on config managemnt updates and opendev work19:36
diablo_rojoYep :) We get it. get as close as you can and we can refine later.19:37
clarkbOnce we get a bit closer to the event I'll spin up a planning document (probably etherpad) where we can dig into details19:37
*** lpetrut has quit IRC19:38
clarkbany other thoughts about the PTG?19:38
fungilooking forward to seeing folks in a place i can get to with a direct flight for a change ;)19:38
clarkbfungi: I don't think I have a direct flight (but thats an airline thing not total lack of availability)19:39
corvusit's hub-hub for me19:39
clarkbDenver is beginning tofeel like the unofficial train depot for openstack though19:39
fungiliving where i do, i limit my flight choices to airlines which are willing to land planes here19:39
corvusthey have a nice train depot19:39
clarkb#topic Open Discussion19:40
*** openstack changes topic to "Open Discussion (Meeting topic: infra)"19:40
clarkbmay as well open it open to other items. We have time19:40
* mordred is driving to denver again19:40
fungimordred: a cattle drive?19:40
mordredfungi: yes. except with no cattle - or gasoline!19:40
clarkbmordred: I was thinking about that too and trying to make a family trip out of it. That makes sense with 3 day conference but not 8 day marathon though19:40
clarkbso we'll just do road trip nearer to home in the summer instead19:40
mordredclarkb: ++19:41
mordredclarkb: your family has more moving parts than mine does19:41
clarkbhttps://review.openstack.org/#/c/631052/1 should fix the gerrit war publishing more and I've cleaned up the extra file copies from the last publish19:41
clarkbif anyone has a quick moment to review that19:41
mordredhttps://review.openstack.org/#/c/631047/ <-- I left out a gerrit plugin earlier19:41
*** a-pugachev has joined #openstack-meeting19:42
*** yamamoto has quit IRC19:42
mordredoh - also ..19:42
*** yamamoto has joined #openstack-meeting19:42
mordreddrumroll please ...19:42
mordredputs all the new artifact/log copying into the base job!19:42
fungii was just looking at that one19:42
*** a-pugachev has quit IRC19:42
mordredand is ready to land19:42
clarkbI'll let fungi review it then :)19:43
fungi(mainly trying to make sure this matches what has been done in base-test)19:43
clarkbmordred: my super secret plan was trying to somehow make transporting the smoker work out then we could do an infra bbq :)19:43
mordredthere's still a couple of patches to get artifact publication finished19:43
clarkbmordred: reality is that smoker probably wasn't going to fit in with luggage anyway19:43
mordredclarkb: I am in favor of that plan19:43
corvusi could probably check my flowerpot smoker19:43
fungiclarkb: i expect denver will have no shortage of bbq19:43
clarkbfungi: ya and late april weather may not work out with being in a park19:44
clarkbI just like sitting around outside with fire and beer :)19:44
anteayaand mosquitos19:44
mordredit's not a smoker ... but there's this: https://www.gozney.com/products/home-ovens/roccbox/19:44
corvusfire smoke repells mosquitos19:44
mordredcorvus: ++19:45
anteayaindeed, the magic of the combination19:45
mordredI'll be driving through new mexico - could bring a bunch of piñon wood19:45
mordred(for the mosquitos - not for the pizza oven)19:45
*** ttsiouts has quit IRC19:45
anteayaI hope someday to smell what that wood smells like19:46
*** ttsiouts has joined #openstack-meeting19:46
*** electrofelix has quit IRC19:46
clarkbconsidering discussion is mostly around wood smoke I'm going to call it a meeting and give you ~13 minutes for lunch/dinner/braekfast19:47
clarkbthanks everyone!19:47
mordredanteaya: imagine "pine" ... but more new mexican19:47
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"19:47
openstackMeeting ended Tue Jan 15 19:47:24 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:47
openstackMinutes:        http://eavesdrop.openstack.org/meetings/infra/2019/infra.2019-01-15-19.01.html19:47
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/infra/2019/infra.2019-01-15-19.01.txt19:47
openstackLog:            http://eavesdrop.openstack.org/meetings/infra/2019/infra.2019-01-15-19.01.log.html19:47
*** Shrews has left #openstack-meeting19:47
anteayamordred: that sounds lovely19:47
mordredanteaya: https://en.wikipedia.org/wiki/Pinyon_pine fwiw19:48
anteayamordred: when are they going to create digital scratch and sniffs19:48
mordredanteaya: as soon as they do - the advertising people will figure out how to abuse it19:49
anteayano doubt19:49
clarkbI'm 100% wood here19:50
clarkbapple wood19:50
anteayadoes apple wood keep flies away clarkb?19:51
*** ttsiouts has quit IRC19:51
clarkbanteaya: we don't really have fly or mosquitto problems here. It does not keep wasps away19:51
anteayaclarkb: ah a good point to know19:52
*** armstrong has joined #openstack-meeting19:53
*** whoami-rajat has quit IRC20:00
*** erlon_ has quit IRC20:05
*** brault has joined #openstack-meeting20:06
*** brault has quit IRC20:11
*** njohnston has joined #openstack-meeting20:27
*** rfolco has quit IRC20:28
*** yamamoto has quit IRC20:28
*** jamesmcarthur has quit IRC20:35
*** jamesmcarthur has joined #openstack-meeting20:37
*** jamesmcarthur has quit IRC20:45
*** jamesmcarthur has joined #openstack-meeting20:46
*** yamamoto has joined #openstack-meeting20:49
*** armstrong has quit IRC21:02
*** yamamoto has quit IRC21:02
*** armstrong has joined #openstack-meeting21:05
*** bbowen has quit IRC21:09
*** eharney has quit IRC21:15
*** yamamoto has joined #openstack-meeting21:17
*** whoami-rajat has joined #openstack-meeting21:18
*** yamamoto has quit IRC21:20
*** a-pugachev has joined #openstack-meeting21:20
*** jamesmcarthur has quit IRC21:31
*** jamesmcarthur has joined #openstack-meeting21:33
*** jamesmcarthur has quit IRC21:38
efried#startmeeting test21:39
openstackMeeting started Tue Jan 15 21:39:20 2019 UTC and is due to finish in 60 minutes.  The chair is efried. Information about MeetBot at http://wiki.debian.org/MeetBot.21:39
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:39
*** openstack changes topic to " (Meeting topic: test)"21:39
openstackThe meeting name has been set to 'test'21:39
efriedhello world21:40
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"21:40
*** jamesmcarthur has joined #openstack-meeting21:40
openstackMeeting ended Tue Jan 15 21:40:39 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:40
openstackMinutes:        http://eavesdrop.openstack.org/meetings/test/2019/test.2019-01-15-21.39.html21:40
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/test/2019/test.2019-01-15-21.39.txt21:40
openstackLog:            http://eavesdrop.openstack.org/meetings/test/2019/test.2019-01-15-21.39.log.html21:40
*** jamesmcarthur has quit IRC21:42
*** jamesmcarthur has joined #openstack-meeting21:43
*** yamamoto has joined #openstack-meeting21:52
*** yamamoto has quit IRC21:52
*** a-pugachev has quit IRC21:58
*** raildo has quit IRC21:58
*** yamamoto has joined #openstack-meeting22:05
*** imacdonn has quit IRC22:06
*** imacdonn has joined #openstack-meeting22:07
*** jamesmcarthur has quit IRC22:09
*** armstrong has quit IRC22:11
*** yamamoto has quit IRC22:14
*** armstrong has joined #openstack-meeting22:14
*** jamesmcarthur has joined #openstack-meeting22:15
*** mhen has quit IRC22:21
*** mhen has joined #openstack-meeting22:23
*** yamamoto has joined #openstack-meeting22:23
*** jamesmcarthur has quit IRC22:24
*** jamesmcarthur has joined #openstack-meeting22:25
*** armstrong has quit IRC22:25
*** jamesmcarthur has quit IRC22:30
*** jamesmcarthur has joined #openstack-meeting22:32
*** lpetrut has joined #openstack-meeting22:34
*** jamesmcarthur has quit IRC22:34
*** lpetrut has quit IRC22:38
*** jamesmcarthur has joined #openstack-meeting22:38
*** yamamoto has quit IRC22:40
*** jamesmcarthur has quit IRC22:41
*** yamamoto has joined #openstack-meeting22:41
*** jamesmcarthur has joined #openstack-meeting22:43
*** yamamoto has quit IRC22:44
*** brault has joined #openstack-meeting22:45
*** brault has quit IRC22:45
*** rcernin has joined #openstack-meeting22:46
*** boxest has joined #openstack-meeting22:49
*** brault has joined #openstack-meeting23:00
*** hongbin has quit IRC23:01
*** brault has quit IRC23:05
*** efried1 has joined #openstack-meeting23:06
*** efried has quit IRC23:06
*** efried1 is now known as efried23:06
*** yamamoto has joined #openstack-meeting23:08
*** yamamoto has quit IRC23:08
*** jamesmcarthur has quit IRC23:13
*** jamesmcarthur has joined #openstack-meeting23:14
*** munimeha1 has quit IRC23:14
*** ijw has joined #openstack-meeting23:21
*** efried has quit IRC23:22
*** efried has joined #openstack-meeting23:22
*** e0ne has quit IRC23:24
*** jamesmcarthur has quit IRC23:33
*** jamesmcarthur has joined #openstack-meeting23:34
*** jamesmcarthur has quit IRC23:40
*** rossella_s has quit IRC23:45
*** rossella_s has joined #openstack-meeting23:46
*** whoami-rajat has quit IRC23:47
*** yamamoto has joined #openstack-meeting23:51
*** a-pugachev has joined #openstack-meeting23:54
*** yamamoto has quit IRC23:58

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