Tuesday, 2018-10-09

*** mjturek has quit IRC00:04
*** jamesmcarthur has joined #openstack-meeting00:12
*** jamesmcarthur has quit IRC00:16
*** yamamoto has quit IRC00:22
*** longkb has joined #openstack-meeting00:30
*** ykatabam has joined #openstack-meeting00:36
*** yamamoto has joined #openstack-meeting00:50
*** armstrong has joined #openstack-meeting00:59
*** tdasilva has quit IRC00:59
*** lyarwood has quit IRC00:59
*** armstrong has quit IRC01:02
*** hongbin has joined #openstack-meeting01:08
*** slaweq has joined #openstack-meeting01:11
*** slaweq has quit IRC01:15
*** slagle has joined #openstack-meeting01:20
*** Arsenick has quit IRC01:28
*** Arsenick has joined #openstack-meeting01:28
*** d0ugal has quit IRC01:48
*** longkb has quit IRC01:49
*** longkb has joined #openstack-meeting01:50
*** d0ugal has joined #openstack-meeting01:51
*** iyamahat__ has quit IRC01:55
*** yamamoto has quit IRC01:56
*** mhen has quit IRC01:58
*** mhen has joined #openstack-meeting02:00
*** bobh has joined #openstack-meeting02:14
*** apetrich has quit IRC02:15
*** nguyenhai_ has quit IRC02:18
*** longkb has quit IRC02:23
*** longkb has joined #openstack-meeting02:24
*** yamamoto has joined #openstack-meeting02:24
*** psachin has joined #openstack-meeting02:40
*** armax has joined #openstack-meeting02:43
*** lbragstad has joined #openstack-meeting02:43
*** tetsuro has joined #openstack-meeting02:52
*** psachin has quit IRC03:10
*** armax has quit IRC03:12
*** armax has joined #openstack-meeting03:13
*** samP has joined #openstack-meeting03:15
*** bobh has quit IRC03:23
*** armax has quit IRC03:30
*** psachin has joined #openstack-meeting03:44
*** tpatil has joined #openstack-meeting03:45
*** lbragstad has quit IRC03:46
*** lbragstad has joined #openstack-meeting03:48
*** lbragstad has quit IRC03:58
*** tetsuro has quit IRC03:58
samPHi all for masakari04:00
tpatilHi04:00
samP#startmeeting masakari04:00
*** hongbin has quit IRC04:00
openstackMeeting started Tue Oct  9 04:00:39 2018 UTC and is due to finish in 60 minutes.  The chair is samP. Information about MeetBot at http://wiki.debian.org/MeetBot.04:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.04:00
*** openstack changes topic to " (Meeting topic: masakari)"04:00
openstackThe meeting name has been set to 'masakari'04:00
samPtpatil: Hi04:00
samPsorry for long absence04:01
samPI look into past meetings,04:02
samPfollowing patches to stable/queens are merged04:02
tpatilQuick update: some of the patches are merged which are back ported into the stable/rocky04:02
samP#link : https://review.openstack.org/#/c/590735/04:02
tpatil#link : https://review.openstack.org/#/c/562973/04:02
samP#link : https://review.openstack.org/#/c/591557/04:02
tpatil#link : https://review.openstack.org/#/c/599479/04:02
samPabout 599479, I abandoned it, cause it was too early04:04
samPI guess now it is oK04:04
tpatilsamP: correct04:06
tpatilThe above two patches back ported into the stable/rocky branch should be merged04:06
samPit seems that we have a merge conflict for 59947904:09
samPI will fix that and merge04:09
samPtpatil: Thanks, I will review them04:09
samPOnce we merge them, I will propose release for new version for stable/queens, stable/rocky04:10
samPAny other patches/bugs need to discuss?04:10
tpatilNo04:11
tpatilOne observation: Bug fixes are not mentioned in the release notes. I will check this issue.04:13
samPtpatil: Thanks, you were mentioned it earlier also.04:13
samP#topic Stein Work Items04:14
*** openstack changes topic to "Stein Work Items (Meeting topic: masakari)"04:14
samP#link https://etherpad.openstack.org/p/masakari-ptg-stein04:14
samPAny updates on work items?04:14
tpatilNotification implementation : It's in progress.04:15
samPtpatil: great.04:15
tpatilFor apis, notifications are in progress. I hope it should be up for review in the next week04:16
samPI will ping hoangcx about Proactive HA.04:16
samPtpatil: great, thanks04:16
tpatilI want to discuss about host/instance/process notifications. During execution of workflow for each of these notifications, I'm planning to emit notification/event information which will help operator to understand the current progress of the notification04:17
tpatilright now, operator get only status info, i.e. running04:17
tpatilShould this data be added as events/notifications?04:18
tpatilif we decide to add it as events, we may need to add few tables to store this info04:18
samPI think it useful for operators. I dont have exact idea about what tables we need to store this info.04:20
samPCan you share some details later about what to store04:21
tpatilfor e.g. host notifications, it execute a workflow which contains more than one task. In each task, we can emit useful details to give operator some meaningful information. Like how many instances will be evacuated and what is the current progress, like evacuating 1 out of 10 instances, something like that.04:22
tpatilTo store this info, we will need to add few db tables if we decide to emit as a event rather than notifications. As you know notifications data is not stored in masakari db. It depends on the oslo_messaging_notifications driver04:25
tpatilI think it should be stored as an event rather than notifications.04:26
*** e0ne has joined #openstack-meeting04:27
*** e0ne has quit IRC04:27
samPtpatil: OK understand04:28
samPtpatil: #link https://review.openstack.org/#/c/473057/04:29
samPThis is the original spec for this feature04:30
tpatilthe above event notification info will be stored as per the driver you have configured in oslo_messaging_notifications section04:30
samPIt is possible to add those info to this spec?04:30
samPIn case of adding info to above spec, the spec needs to re-propose to stein04:32
tpatilbefore amending above specs, I wanted to discuss this point whether we should club both these details into one. i..e API changes + workflow execution04:33
samPtpatil: no objection to put those 2 changes together.04:35
tpatilThe above specs addresses changes to the API which emit notifications. Operator can subscribe to such notifications and process it separately outside masakari if need be04:35
samPtpatil: correct04:36
tpatilIMO, workflow execution details should be part of masakari db and for that we need another spec04:37
tpatilif you agree, I will submit a new specs for it04:37
*** pcaruana has joined #openstack-meeting04:38
samPtpatil: no problem. In that case separate spec would be better.04:40
tpatilsamP: Ok04:40
tpatilAdd functional tests in openstacksdk04:41
samPtpatil: Please submit a new spec for db changes.04:41
tpatilsamP: Ok04:41
tpatilShould the functional tests reside in masakari repo or openstacksdk repo?04:42
tpatilin ether pad, you also have mentioned about adding functional tests04:42
samPI think functional test would be in openstacksdk repo. However, we need to discuss this with sdk team04:44
samPtpatil: What I mentioned in etherpad was functional test for maskari, which is kind of same as what you proposed.04:45
samPplus some scenarios for host, process, vm failures.04:46
samPI am considering to implement those with eris.04:46
tpatilin that case, I think it's better to write functional test in masakari repo itself. what do you think?04:47
tpatilWe have already started writing functional tests in openstacksdk but it's possible to move it to masakari repo with minimal changes04:48
samPtpatil: Other projects have there functional tests in own repo, right?04:49
tpatilYes, but it doesn't call RestFul apis using it's own python client libraries04:51
tpatilIf we decide to write functional tests in masakari repo itself using openstacksdk interface, it possible to test both openstacksdk code and masakari RestFul APIs04:52
samPOn sdk side they have API validation tests..(just looking at them)04:52
samPtpatil: right.04:52
tpatilso we need to decide whether functional tests should be written in openstacksdk or masakari repo04:53
*** tetsuro has joined #openstack-meeting04:54
samPNow, it seems to me that those functional test should stay in masakari repo.04:54
tpatilthe only catch is if you are modifying openstacksdk code, then the functional tests won't run on the actual changes of sdk code but the previous openstacksdk lib released. Also, you will need to import openstacksdk lib in masakari  which doesn't seems to be correct04:57
samPtpatil: thatz what I am worry about04:58
samPgive me some time to think about this. I will share my thoughts in email04:58
tpatilwe should make sure that there are no duplicate functional tests in masakari and openstacksdk04:59
samPWe can decide on our next meeting, where to put the functional tests04:59
samPtimes up!05:00
tpatilok05:00
samPlets discuss further on email or IRC05:00
samPthank you all!05:00
samP#endmeeting05:00
tpatilSure05:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"05:00
openstackMeeting ended Tue Oct  9 05:00:33 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)05:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/masakari/2018/masakari.2018-10-09-04.00.html05:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/masakari/2018/masakari.2018-10-09-04.00.txt05:00
openstackLog:            http://eavesdrop.openstack.org/meetings/masakari/2018/masakari.2018-10-09-04.00.log.html05:00
*** e0ne has joined #openstack-meeting05:04
*** e0ne has quit IRC05:04
*** slaweq has joined #openstack-meeting05:11
*** diablo_rojo has joined #openstack-meeting05:14
*** jbadiapa has quit IRC05:14
*** slaweq has quit IRC05:15
*** janki has joined #openstack-meeting05:25
*** apetrich has joined #openstack-meeting05:32
*** tetsuro has quit IRC05:34
*** diablo_rojo has quit IRC05:36
*** iyamahat has joined #openstack-meeting05:44
*** Luzi has joined #openstack-meeting05:48
*** tpatil has quit IRC06:25
*** tetsuro has joined #openstack-meeting06:32
*** ttsiouts has joined #openstack-meeting06:34
*** aojea has joined #openstack-meeting06:35
*** jbadiapa has joined #openstack-meeting06:36
*** kopecmartin|off is now known as kopecmartin|ruck06:38
*** jiaopengju has joined #openstack-meeting06:39
*** slaweq has joined #openstack-meeting06:58
*** rcernin has quit IRC07:08
*** ykatabam has quit IRC07:08
*** Emine has joined #openstack-meeting07:22
*** ralonsoh has joined #openstack-meeting07:24
*** electrofelix has joined #openstack-meeting07:25
*** ttsiouts has quit IRC07:30
*** ttsiouts has joined #openstack-meeting07:31
*** ttsiouts has quit IRC07:35
*** ttsiouts has joined #openstack-meeting07:36
*** ttsiouts has quit IRC07:38
*** ttsiouts has joined #openstack-meeting07:38
*** tetsuro has quit IRC07:39
*** belmoreira has joined #openstack-meeting07:40
*** priteau has joined #openstack-meeting07:48
*** priteau has quit IRC07:50
*** ttsiouts has quit IRC07:52
*** joxyuki has joined #openstack-meeting08:00
*** ttsiouts has joined #openstack-meeting08:09
*** dkushwaha has joined #openstack-meeting08:10
*** rossella_s has quit IRC08:10
*** e0ne has joined #openstack-meeting08:11
dkushwaha#startmeeting tacker08:12
openstackMeeting started Tue Oct  9 08:12:00 2018 UTC and is due to finish in 60 minutes.  The chair is dkushwaha. Information about MeetBot at http://wiki.debian.org/MeetBot.08:12
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.08:12
*** openstack changes topic to " (Meeting topic: tacker)"08:12
openstackThe meeting name has been set to 'tacker'08:12
dkushwahaWho is here for Tacker meeting?08:12
joxyukio/08:12
dkushwaha#topic Roll Call08:12
*** openstack changes topic to "Roll Call (Meeting topic: tacker)"08:12
dkushwahahi joxyuki08:12
joxyukihi, dkushwaha08:13
*** rossella_s has joined #openstack-meeting08:14
joxyukiwow, no others???08:15
dkushwahajoxyuki, seems so08:15
*** janki is now known as janki|lunch08:16
dkushwahaI was away from work more than a week due to some holidays and family member health issue.08:17
dkushwahaSo i could not work during that time. And just joined office right now.08:17
*** e0ne has quit IRC08:17
dkushwahajoxyuki, do you have something to discuss?08:18
*** e0ne has joined #openstack-meeting08:18
dkushwahaotherwise we can skip todayś meeting, and will be available on Tacker channel for any discussion.08:20
joxyukidkushwaha, no. I and my colleague are working on https://review.openstack.org/#/c/561840/ and https://review.openstack.org/#/c/603558/.08:20
joxyukiWe are going to upload patch soon.08:20
dkushwahajoxyuki, great08:20
joxyukiok,08:21
joxyukilet's do so08:21
dkushwahaI will review them, and I have so many pending items so resume my work from now08:22
dkushwahajoxyuki, ok, so closing this meeting for now.08:23
joxyukiyea, I hope you will make great progress08:23
joxyukigood luck08:23
dkushwahaThanks08:23
dkushwaha#endmeeting08:23
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"08:23
openstackMeeting ended Tue Oct  9 08:23:37 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)08:23
openstackMinutes:        http://eavesdrop.openstack.org/meetings/tacker/2018/tacker.2018-10-09-08.12.html08:23
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/tacker/2018/tacker.2018-10-09-08.12.txt08:23
*** joxyuki has left #openstack-meeting08:23
openstackLog:            http://eavesdrop.openstack.org/meetings/tacker/2018/tacker.2018-10-09-08.12.log.html08:23
*** e0ne has quit IRC08:26
*** tetsuro has joined #openstack-meeting08:26
*** phuoc has joined #openstack-meeting08:26
*** rossella_s has quit IRC08:37
*** rossella_s has joined #openstack-meeting08:38
*** priteau has joined #openstack-meeting08:45
*** psachin has quit IRC08:54
*** lbragstad has joined #openstack-meeting08:56
*** belmorei_ has joined #openstack-meeting08:57
*** belmoreira has quit IRC08:57
jiaopengju#startmeeting karbor09:14
openstackMeeting started Tue Oct  9 09:14:01 2018 UTC and is due to finish in 60 minutes.  The chair is jiaopengju. Information about MeetBot at http://wiki.debian.org/MeetBot.09:14
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.09:14
*** openstack changes topic to " (Meeting topic: karbor)"09:14
openstackThe meeting name has been set to 'karbor'09:14
jiaopengjuhi, anyone has something to discuss?09:15
jiaopengjuwho is here for Karbor weekly meeting?09:16
jiaopengjuSo we can skip the meeting today. If you have something to discuss but missing the meeting, please feel free to discuss it on Karbor IRC channel.09:20
jiaopengjuThanks09:20
jiaopengju#endmeeting09:20
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"09:20
openstackMeeting ended Tue Oct  9 09:20:38 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)09:20
openstackMinutes:        http://eavesdrop.openstack.org/meetings/karbor/2018/karbor.2018-10-09-09.14.html09:20
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/karbor/2018/karbor.2018-10-09-09.14.txt09:20
openstackLog:            http://eavesdrop.openstack.org/meetings/karbor/2018/karbor.2018-10-09-09.14.log.html09:20
*** a-pugachev has joined #openstack-meeting09:22
*** dkushwaha has left #openstack-meeting09:36
*** imacdonn has quit IRC09:39
*** jiapei has joined #openstack-meeting09:40
*** vabada has quit IRC09:46
*** jamesmcarthur has joined #openstack-meeting09:48
*** jamesmcarthur has quit IRC09:52
*** imacdonn has joined #openstack-meeting09:52
*** vabada has joined #openstack-meeting09:57
*** janki|lunch is now known as janki10:02
*** rossella_s has quit IRC10:09
*** rossella_s has joined #openstack-meeting10:10
*** yamamoto has quit IRC10:12
*** yamamoto has joined #openstack-meeting10:13
*** yamamoto has quit IRC10:13
*** yamamoto has joined #openstack-meeting10:14
*** lbragstad has quit IRC10:16
*** markvoelker has joined #openstack-meeting10:25
*** yamamoto has quit IRC10:25
*** yamamoto has joined #openstack-meeting10:26
*** yamamoto has quit IRC10:30
*** tetsuro has quit IRC10:35
*** tetsuro has joined #openstack-meeting10:40
*** ttsiouts has quit IRC10:44
*** rossella_s has quit IRC10:46
*** rossella_s has joined #openstack-meeting10:49
*** armax has joined #openstack-meeting10:53
*** markvoelker has quit IRC10:58
*** ttsiouts has joined #openstack-meeting11:01
*** rossella_s has quit IRC11:04
*** rossella_s has joined #openstack-meeting11:05
*** ttsiouts has quit IRC11:09
*** ttsiouts has joined #openstack-meeting11:13
*** yamamoto has joined #openstack-meeting11:15
*** erlon_ has joined #openstack-meeting11:16
*** longkb has quit IRC11:17
*** slagle has quit IRC11:22
*** armax has quit IRC11:27
*** yamamoto has quit IRC11:49
*** yamamoto has joined #openstack-meeting11:50
*** yamamoto has quit IRC11:50
*** yamamoto has joined #openstack-meeting11:50
*** markvoelker has joined #openstack-meeting11:51
*** rossella_s has quit IRC11:56
*** rossella_s has joined #openstack-meeting12:00
*** jesusaur has quit IRC12:01
*** ttsiouts has quit IRC12:01
*** ttsiouts has joined #openstack-meeting12:02
*** jesusaur has joined #openstack-meeting12:06
*** tetsuro has quit IRC12:07
*** ttsiouts has quit IRC12:10
*** tpsilva has joined #openstack-meeting12:14
*** ttsiouts has joined #openstack-meeting12:22
*** raildo has joined #openstack-meeting12:22
*** yamamoto has quit IRC12:23
*** yamamoto has joined #openstack-meeting12:24
*** yamamoto has quit IRC12:29
*** yamamoto has joined #openstack-meeting12:34
*** apetrich has quit IRC12:35
*** apetrich has joined #openstack-meeting12:42
*** njohnston has joined #openstack-meeting12:46
*** lpetrut has joined #openstack-meeting12:58
*** dustins has joined #openstack-meeting13:02
*** longkb has joined #openstack-meeting13:07
*** ociuhandu has joined #openstack-meeting13:07
*** ijw has joined #openstack-meeting13:09
*** ijw has quit IRC13:12
*** ijw has joined #openstack-meeting13:12
*** bobh has joined #openstack-meeting13:13
*** ttsiouts has quit IRC13:13
*** cloudrancher has quit IRC13:16
*** yamamoto has quit IRC13:17
*** yamamoto has joined #openstack-meeting13:17
*** cloudrancher has joined #openstack-meeting13:17
*** mriedem has joined #openstack-meeting13:19
*** janki has quit IRC13:23
*** aojeagarcia has joined #openstack-meeting13:25
*** mahatic has quit IRC13:26
*** mahatic has joined #openstack-meeting13:27
*** lbragstad has joined #openstack-meeting13:28
*** aojea has quit IRC13:28
*** longkb has quit IRC13:29
*** davidsha has joined #openstack-meeting13:37
*** ttsiouts has joined #openstack-meeting13:37
*** longkb has joined #openstack-meeting13:40
*** awaugama has joined #openstack-meeting13:42
*** liuyulong has joined #openstack-meeting13:43
*** hongbin has joined #openstack-meeting13:48
*** rubasov has joined #openstack-meeting13:48
*** tidwellr has joined #openstack-meeting13:52
*** ttsiouts has quit IRC13:52
*** annp_ has joined #openstack-meeting13:56
*** mjturek has joined #openstack-meeting13:56
*** mlavalle has joined #openstack-meeting13:57
*** felipemonteiro has joined #openstack-meeting13:58
*** boden has joined #openstack-meeting13:58
*** lajoskatona has joined #openstack-meeting13:59
mlavalle#startmeeting networking14:00
openstackMeeting started Tue Oct  9 14:00:06 2018 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
mlavalleHi there!14:00
*** eharney has joined #openstack-meeting14:00
hongbino/14:00
lajoskatonaHi14:00
tidwellrhi14:00
longkbhi o/14:00
bodenhowdy14:01
rubasovo/14:01
njohnstono/14:01
slaweqhi14:02
amotokio/14:02
haleybhi14:02
*** ttsiouts has joined #openstack-meeting14:02
mlavalleok, let's get going14:03
annp_hi14:03
mlavalle#topic Annoucements14:03
*** openstack changes topic to "Annoucements (Meeting topic: networking)"14:03
*** beagles is now known as beagles_cough14:03
*** beagles_cough is now known as beagles14:03
mlavalleWe are a little less of two weeks away from the Stein-1 milestone, October 22 - 2614:04
mlavalleLast week week I proposed the addition of bcafarel to the stable branches core team: http://lists.openstack.org/pipermail/openstack-dev/2018-October/135343.html14:04
bcafarelo/14:05
njohnston+114:05
mlavalleToday marks one week of that nomination, with only positive feedback14:05
mlavalleso he should have +2 powers in stable branches any time now14:05
annp_+114:05
*** Luzi has quit IRC14:05
mlavallebcafarel: THanks for stepping up to the plate!14:05
*** raildo has quit IRC14:06
amotokiI sometimes review stable branches but have less crossing with bcafarel so far.... thanks for stepping up14:06
amotoki*in stable reviews14:06
bcafarelthanks mlavalle amotoki, I will keep up with your expectations14:06
*** raildo has joined #openstack-meeting14:07
mlavalleFinally, yesterday the Neutron performance team held its first biweekly meeting:14:07
mlavalle#link  http://eavesdrop.openstack.org/meetings/neutron_performance/2018/neutron_performance.2018-10-08-16.00.log.html14:07
njohnstond'oh!  Sorry I missed it - was off on holiday.14:08
mlavalleit takes place every two weeks at 1600 UTC. everybody is invited to chip in14:08
* haleyb missed it too14:08
*** mpeterson has joined #openstack-meeting14:08
-amotoki- tries to check logs14:08
mlavalleany other announcements to share with the team?14:08
amotokire: the stable branches, I would like to discuss a new stable/ocata release before EM in the open discussion section of this meeting.14:08
-amotoki- forgot to add it to the agenda though :(14:09
mlavalleamotoki: great, haleyb and I had a chat about that a few days ago. We were waiting for bcafarel to join the team14:10
mlavallevery timely!14:10
mlavalle#topic Blueprints14:10
*** openstack changes topic to "Blueprints (Meeting topic: networking)"14:10
*** ttsiouts has quit IRC14:11
mlavalleThese are the blueprints we are targeting for Stein-1:14:11
mlavalle#link https://launchpad.net/neutron/+milestone/stein-114:11
mlavalleDoes anybody have any blueprints updates?14:11
mlavalleI have a couple of quick updates14:13
mlavalleFirst, last Friday the drivers team approved this rfe: https://bugs.launchpad.net/neutron/+bug/179477114:13
openstackLaunchpad bug 1794771 in neutron "SRIOV trunk port - multiple vlans on same VF" [Wishlist,Triaged]14:13
*** mugsie has joined #openstack-meeting14:13
mlavalleI am going to create a blueprint for it, so we can track the effort in our weekly meeting14:14
mlavalleI also started this past weekend implementing https://bugs.launchpad.net/neutron/+bug/177762714:14
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)14:14
mlavalleHere's the first patch: https://review.openstack.org/#/c/608473/14:15
mlavalleI will also create a blueprint for it14:15
amotokiI resumed mine (policy-in-code) today. last week was too busy week to catch up many internal stuffs during my late summer vacation.... and this Monday was a holiday here. I will post an updated version tomorrow. Thank you all for the review comments14:15
mlavallebcafarel: the drivers also approved this past Friday https://bugs.launchpad.net/neutron/+bug/178959214:16
openstackLaunchpad bug 1789592 in neutron "[RFE] Add native OVSDB implementation for OvsdbMonitor" [Wishlist,Triaged]14:16
*** yamamoto has quit IRC14:16
mlavalledo you plan to implement it?14:16
njohnstonI have a few patches in-flight for bulk port operations, I hope to get new PSes up today to address comments14:16
bcafarelI saw it in last meeting summary yes14:16
mlavallebcafarel: ok, great14:16
*** yamamoto has joined #openstack-meeting14:17
bcafarelmlavalle: I plan to work on it, but if anyone wants to take it, I do not mind :)14:17
mlavalleamotoki, njohnston thanks for the updates14:17
tidwellrI have https://review.openstack.org/#/c/608357 which migrates neutron-dynamic-routing from Ryu to os-ken14:17
*** ttsiouts has joined #openstack-meeting14:17
mlavalletidwellr: ah nice!14:17
mlavallethat's a good exercise14:17
mlavalleThanks!14:18
amotokinice, but don't we need to coordinate the timing to switch from ryu to os-ken in the neutron stadium?14:18
*** eharney has quit IRC14:18
mlavalleamotoki: let's talk about that in the os-ken section14:18
amotokisure14:18
mlavalleany toher updates?14:19
mlavalleother^^^14:19
mlavalleok, let's move on14:19
mlavalle#topic Community goals14:20
*** openstack changes topic to "Community goals (Meeting topic: networking)"14:20
* mlavalle notes that amotoki already updated on policy in code14:20
slaweqI started working on update check with noop check first14:20
slaweqhttps://review.openstack.org/#/c/608444/14:20
*** yamamoto has quit IRC14:21
slaweqbasically it's working, only problem is that new lib oslo_upgradecheck is not released in stable version yet14:21
mlavallenice, great progress!14:21
mlavallethanks14:21
slaweqwhen this will be done, we can add some real checks to it14:22
slaweqbut community goal is to have this tool with at least noop check, so should be good :)14:22
amotokiuntil stable release, we might use the latest commit by specifying the oslo repo in required-projects in zuul.yaml.14:22
slaweqamotoki: yes, but still it fails on requirements check as it's not in openstack/requirements yet14:22
slaweqI sent email about that on the weekend and mriedem adviced me to wait a bit for release of this lib14:23
slaweqso I think we have some time still and can wait14:23
njohnstonLooking at the zuul job definitions it looks like it is not going to be too difficult to move all of our zuul jobs to python 3; just need to make sure that the USE_PYTHON3 variable is true in most cases.  That is something that should be easy to add to the .zuul.yaml file.14:24
mlavalleso, essentially, we are ahead of the game, great!14:24
amotokinjohnston: yeah, it is true for devstack related jobs14:24
mlavallethanks njohnston14:25
njohnston But in the process of talking about that in the neutron CI meeting, it came up that our governance standards also direct us to test on whatever the most recent LTS release is as of the start of the cycle; for Stein this is ubuntu Bionic.  Bionic is already being tested by the openstack-tox-py36 job, since it ships with python3.6, so that objective can be achieved by changing the nodeset fo rthe zuul jobs to "ubuntu-bion14:25
njohnstonic".14:25
mlavalleok, let's move on14:25
mlavalle#topic Starter Approved RFEs14:26
*** openstack changes topic to "Starter Approved RFEs (Meeting topic: networking)"14:26
mlavalleI want to point out that we have a couple of approved RFEs that are considered low hanging fruit for new contributors:14:26
mlavallehttps://bugs.launchpad.net/neutron/+bug/174519214:27
openstackLaunchpad bug 1745192 in neutron "Can't create a vlan transparent network in mixed driver environment" [Wishlist,Confirmed] - Assigned to Pawel Rusak (rusakp)14:27
mlavalleThis one one taken over back in June, but I didn't see any progress all summer lomng14:27
mlavalleslaweq: did rusakp reach out to you again?14:27
slaweqmlavalle: not in last few months14:28
mlavalleok, let's hold for a couple of weeks. if we don't see any progress, we can un-assign it14:28
mlavallealso this past Friday the drivers approved: https://bugs.launchpad.net/neutron/+bug/179290114:28
openstackLaunchpad bug 1792901 in neutron "[RFE] subnet pool can not delete prefixes" [Wishlist,Triaged]14:28
mlavalleit's unassigned and tidwellr has offered to provide guidance14:29
tidwellrdo we need someone to jump in and finish this off?14:29
mlavallenot in a hurry. do you want it?14:30
tidwellrI'm happy to take a look14:30
mlavallefeel free14:30
tidwellralrighty then14:31
mlavallebcafarel: we can also advertise in this section: https://bugs.launchpad.net/neutron/+bug/178959214:31
openstackLaunchpad bug 1789592 in neutron "[RFE] Add native OVSDB implementation for OvsdbMonitor" [Wishlist,Triaged]14:31
mlavallefor a few weeks. If nobody shows up, you can implement it14:31
mlavalleok, let's move on14:32
mlavalle#topic Bugs14:32
*** openstack changes topic to "Bugs (Meeting topic: networking)"14:32
mlavalleLast week our deputy was Swami14:32
mlavalleI don't see him around though14:33
mlavalleand didn't see a summary from him14:33
*** eharney has joined #openstack-meeting14:33
mlavalleThis is what was reported over the past few days: https://bugs.launchpad.net/neutron/+bugs?orderby=-datecreated&start=014:34
mlavalleI see a lot of undecided there14:34
mlavalleThe only critical one is https://bugs.launchpad.net/neutron/+bug/179587014:35
openstackLaunchpad bug 1795870 in neutron "Trunk scenario test test_trunk_subport_lifecycle fails from time to time" [High,Confirmed]14:35
slaweqmlavalle: some of them are from this week and I didn't check them yet14:35
slaweqbut I will do it14:35
mlavalleslaweq: is this the one I am supposed to take over?^^^^14:35
mlavalleyou didn't ping me14:35
slaweqmlavalle: yes14:36
slaweqahh, I forgot :/14:36
slaweqI created bug and forgot to ping You later14:36
slaweqsorry14:36
mlavalleno problem14:36
mlavalleI just assigned it to me14:36
slaweqthx mlavalle14:36
mlavalleso don't yell at me during the CI meeting ;-)14:36
mlavalleok, any other bugs we should discuss today?14:37
amotokii also have new bug mails last week. I can share efforts to check them.14:37
slaweqmlavalle: of course :)14:37
mlavalleamotoki: thanks!14:38
mlavallewell, as hinted by slaweq earlier, he is our deputy this week14:38
mlavalleThanks!14:38
slaweqyep14:38
slaweqand this time I remember about that ;)14:39
mlavalleLOL14:39
mlavalle#topic neutron-lib14:39
*** openstack changes topic to "neutron-lib (Meeting topic: networking)"14:39
mlavalleboden: you are up14:39
bodenhi14:39
bodenthe only real thing I want to mention (again) is that moving forward I'll only be posting neutron-lib consumption patches to those projects who opted in14:40
bodenhere's the topic I was using for those opt-in patches for ref https://review.openstack.org/#/q/topic:neutron-lib-current-optin14:40
mlavalleyeap, don't be afraid to remind us constantky14:40
bodennot much else exciting to mention from me14:41
mlavallegood progress!14:41
mlavallesfc is as I expected :-(14:42
bodenTaaS as well... and they asked about opting in14:42
bodenguess lack of reviewers14:42
mlavalleand with tap as a service, we probably need to enable some people with +2 powers14:42
mlavalleI'll talk to munimeha1, since he is actively working on it14:43
mlavalleand will loop yamamoto in14:43
bodenmlavalle if you think that's the right thing to do... my main concern is that this is a testament from the project opting in that they can review the  consumption patches14:43
bodenbut we can see14:43
bodenyou know me... I will complain if things go south ;)14:43
mlavalleI know :-)14:43
mlavalleanything else here?14:44
bodennot from me14:44
amotokineutron-lib consumption patches and project activeness are separate things though they are tightly coupled....14:44
bodenamotoki very tight14:45
mlavalle#topic CLI / SDK14:45
*** openstack changes topic to "CLI / SDK (Meeting topic: networking)"14:45
mlavalleany updates on this topic?14:45
amotokinothing from me this week14:45
*** phuoc has left #openstack-meeting14:45
mlavalleack14:45
mlavalle#topic os-ken14:46
*** openstack changes topic to "os-ken (Meeting topic: networking)"14:46
mlavallehongbin: you are up14:46
hongbinhi14:46
hongbini want to mention a few things14:46
hongbin1. the storyboard of os-ken is created14:46
hongbin#link https://storyboard.openstack.org/#!/project/openstack/os-ken14:46
hongbinfor os-ken, we will use storyboard to track BPs, bugs, etc.14:47
hongbin2. os-ken 0.1.0 is release14:47
hongbin#link https://review.openstack.org/#/c/607010/14:47
hongbinthis is the initial release of os-ken, the version start with "0" means it is in beta status14:48
hongbin3. i am requesting to add os-ken to the global requirement14:48
hongbin#link https://review.openstack.org/#/c/609018/14:48
hongbinafter that, neutron and stadium project will be able to consume this library and do some initial testing14:49
hongbinthat is all i want to share, any question for that?14:49
amotokiwhat is the recommended process if we receive bugs in neutron launchpad related to os-ken/ryu?14:49
*** bobh has quit IRC14:49
hongbinmlavalle: you have an answer for amotoki 's question?14:50
mlavallethe idea is that we track os-ken bugs in storyboard14:50
mlavalleso if we receive them in launchpad, we should transfer them to storyboard14:51
njohnstonI would copy the text into a storyboard story, then mark the LP bug 'invalid' and provide a link to the storyboard story.  I don't know how to reflect critical/high/medium/low/wishlist status in storyboard.14:51
amotokii think the way is to create a new story on storyboard, leave a comment in launchpad and keep it open till it is fixed in os-ken .14:51
amotokiper ML discussion, storyboard has no priority mechanism in its design.14:52
slaweqamotoki: I don't think we need to keep it open in launchpad until bug is fixed14:52
mlavalleI think this is a good approach, amotoki....14:52
amotokislaweq: I think it depends on situations. if it affects neutron behaviors, it is worth opend.14:52
amotokis/opend/opened/14:53
slaweqyes, in such case it can14:53
njohnston+114:53
mlavallecorrect, but in principle, let's close it in Launchpad14:53
slaweqshould we then link related os-ken patch to this lp bug also?14:53
mlavalleslaweq: yes14:53
slaweqe.g. as "related-bug", right?14:54
mlavalleyes14:54
slaweqok14:54
amotoki+114:54
mlavalleactually, I'll add a summary of this discussion to our bugs triaging policy14:54
slaweqalso please note that You can link patch to story/task from storyboard so we should require that too in such patches for os-ken14:54
slaweq(just to mention :))14:54
mlavallewe can refine it thorugh your firandly reviews14:54
mlavallefriendly reviews^^^14:55
*** munimeha1 has joined #openstack-meeting14:55
mlavalleok, let's move on14:55
mlavalle#topic On demand agenda14:55
*** openstack changes topic to "On demand agenda (Meeting topic: networking)"14:55
mlavalleamotoki: let's talk about ocata14:55
amotokithe time left is limted. I would like to share our situation.14:56
amotokias you may know, we introduced a new way to maintain stable branches.14:56
amotokiIt is called as "extended maintenance" (EM).14:56
amotokiWe won't cut a release after entering to the EM phase.14:56
*** lpetrut has quit IRC14:56
amotokiWe have several commits after the last release of stable/ocata.14:56
*** bobh has joined #openstack-meeting14:56
amotokinova team is thinking to cut a new release for stable/ocata: http://lists.openstack.org/pipermail/openstack-dev/2018-October/135483.html14:57
*** yamamoto has joined #openstack-meeting14:57
amotokiI think the neutron team is in the same situation.14:57
mlavallethat message is what triggered my chat with haleyb14:57
mlavalleand yes, we agree14:57
amotokiwe also have several open stable/ocata patches.14:57
amotokiI think it is better to visit pending reviews and then cut a release14:58
haleybwe need to merge or abandon, then cut, then go EM14:58
haleybwe had the same idea14:58
amotokihaleyb: we don't need to abandon open reviews.14:58
amotokibecause EM does not mean EOL14:59
haleybamotoki: ok, maybe i'm just thinking of some that have been sitting a while14:59
mlavalleI think we are more or less in the same page14:59
mlavallewe ran out of time15:00
mlavalle#endmeeting15:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"15:00
amotokiyeah, let's look thru open reviews.15:00
openstackMeeting ended Tue Oct  9 15:00:23 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking/2018/networking.2018-10-09-14.00.html15:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking/2018/networking.2018-10-09-14.00.txt15:00
openstackLog:            http://eavesdrop.openstack.org/meetings/networking/2018/networking.2018-10-09-14.00.log.html15:00
*** boden has left #openstack-meeting15:00
*** tidwellr has left #openstack-meeting15:00
mlavalleamotoki: thanks for bringing this topic up! very timely15:00
slaweq#startmeeting neutron_qos15:00
openstackMeeting started Tue Oct  9 15:00:59 2018 UTC and is due to finish in 60 minutes.  The chair is slaweq. Information about MeetBot at http://wiki.debian.org/MeetBot.15:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:01
*** openstack changes topic to " (Meeting topic: neutron_qos)"15:01
openstackThe meeting name has been set to 'neutron_qos'15:01
njohnstono/15:01
mlavalleo/15:01
ralonsohhi15:01
slaweqlets start next one :)15:01
hongbino/15:01
rubasovo/15:01
lajoskatonao/15:01
slaweqwelcome back ralonsoh!15:01
*** bobh has quit IRC15:01
slaweqand welcome all of You too :)15:01
slaweq#topic RFEs15:02
*** openstack changes topic to "RFEs (Meeting topic: neutron_qos)"15:02
slaweqfirst one (as always) is:15:02
slaweq#link https://bugs.launchpad.net/neutron/+bug/156096315:02
openstackLaunchpad bug 1560963 in neutron "[RFE] Minimum bandwidth support (egress)" [Wishlist,In progress]15:02
slaweqand there is still no any progress on that one15:02
*** jbadiapa has quit IRC15:02
slaweqnext on the list is:15:03
slaweq#link https://bugs.launchpad.net/neutron/+bug/172757815:03
openstackLaunchpad bug 1727578 in neutron "[RFE]Support apply qos policy in VPN service" [Wishlist,Triaged]15:03
mlavalleI folowed up on this one15:03
slaweqThere was some update on patch but it's not WIP15:03
slaweqpatch #link https://review.openstack.org/#/c/558986/15:03
slaweqthx mlavalle :)15:04
mlavallezhaobo is definitely going to continue working on it15:04
slaweqthat's very good :)15:04
mlavallehe is currently working on a feature for Octavia15:04
mlavallebut he is commited to finish this blueprint this cycle15:05
mlavalleit is in his goals sheet with his employer15:05
mlavallewhich is also min ;-)15:05
mlavallemine^^^15:05
slaweqgreat to hear that, thx mlavalle for update on this :)15:05
slaweqand are You his manager maybe? :)15:06
mlavallelet's just be a little patient over the next few weeks15:06
mlavalleuntil he is done with his Octavia work15:06
mlavalleI'm not his manager15:06
mlavallebut I'm his techincal lead15:06
mlavalleso, yes, I can influence15:06
slaweqgood, that also can help us ;)15:06
slaweqthx for update, I will just keep mentioning this on our meetings to not forget about it :)15:07
mlavallesure15:07
mlavallenp15:07
slaweqok, next one15:08
slaweq#link https://bugs.launchpad.net/neutron/+bug/175704415:08
openstackLaunchpad bug 1757044 in neutron "[RFE] neutron L3 router gateway IP QoS" [Wishlist,In progress] - Assigned to LIU Yulong (dragon889)15:08
slaweqpatches have good progress IMO, but I didn't review them yet recently:15:08
slaweq#link https://review.openstack.org/#/c/424468/ - server side patch15:08
slaweq#link https://review.openstack.org/#/c/568526/ - agent side patch15:09
slaweqanyone wants to add something about this one maybe?15:11
slaweqor can we move forward?15:11
mlavallelet's move forward15:11
mlavallejust review them when you have a chance15:11
*** bobh has joined #openstack-meeting15:11
slaweqok, next one15:11
slaweq#link https://bugs.launchpad.net/neutron/+bug/177762715:12
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:12
* mlavalle looks at himself15:12
slaweqit's Yours mlavalle :)15:12
mlavalleI pushed the neutron-lib patch:15:12
mlavallehttps://review.openstack.org/#/c/608473/15:12
mlavalleit is esentially in its final form15:12
mlavallebut Michel Peterson left some comments about the position of the } in the resource attribute map15:13
*** jamesmcarthur has joined #openstack-meeting15:13
mlavalleI'll fix those later today and it will be good to go as far as I can tell15:13
*** armax has joined #openstack-meeting15:14
slaweqok, added to my review queue then15:14
mlavalleNext step for this week, is a patch with entry points for the qos plugin in Neutron15:14
ralonsohI'll review it today15:14
mlavalleand that will wrap this RFE15:14
slaweqbut some neutron patch will be necessary also? or not?15:15
mlavalleYes, that's what I meant ^^^^15:15
slaweqahh, sorry15:15
mlavalleabout the patch for the QoS plugin15:15
slaweqI missed one line somehow :)15:16
mlavallewe need to retrieve the policy id15:16
mlavalleand redirect the call to the current API15:16
slaweqok, so we should be good with this one soon, thx mlavalle :)15:16
slaweqok, moving one15:17
slaweq*moving on15:18
slaweqlast rfe on the list:15:18
slaweq#link https://bugs.launchpad.net/neutron/+bug/157898915:18
openstackLaunchpad bug 1578989 in neutron "[RFE] Strict minimum bandwidth support (egress)" [Wishlist,In progress] - Assigned to Lajos Katona (lajos-katona)15:18
lajoskatonaYes, we are on it15:18
slaweqlajoskatona: rubasov any updates?15:18
lajoskatonaWe try to move the neutron side patches one-by-one through the review15:18
rubasovI was on vacation for more than a week so I'll let lajoskatona give an update15:18
lajoskatonaActually I tried to fix the comments for the agent heartbeat patches, as those are at the bottom, so I feel that we have some progress15:19
slaweqI was reviewing some of Your patches today15:20
lajoskatonaOn the other side for the pathces which are not for rubasov's patches, I tried to do the same :-)15:20
lajoskatonaThanks for everybody for the reviews15:20
lajoskatonayeah, thanks I hope we are moving toward the final version with them15:21
lajoskatonaOtherwise we try to do some preparation for the Berlin summit demo, but with that not too much progress15:21
lajoskatonaThat's all I think15:21
ralonsohgood job, BTW15:21
slaweqok, thx for updates15:22
mlavalleI'll review the series at some point this week15:22
slaweqand thx a lot for all Your work on this15:22
lajoskatonaralonsoh: thanks15:22
mlavallethanks for the update and the hard work15:22
lajoskatonamlavalle: thanks15:22
*** longkb has quit IRC15:22
slaweqbtw. lajoskatona, I'm now looking at api test results in https://review.openstack.org/#/c/584927/15:23
slaweqand now I understand why You wanted this neutron patch to be depends on neutron-tempest-plugin patch15:23
slaweqbut I think that we don't need test test_rule_create_fail_for_direction_ingress at all now15:23
slaweqas we will support creation of ingress min_bw_limit_rule now15:24
lajoskatonaslaweq: ok, so as tempest is branchless, I should skip that, or delete?15:24
slaweqso maybe the easiest way would be to propose separate patch with removal of this tes15:24
slaweq*test15:24
slaweqand then all other should go smooth15:24
ralonsohagree15:24
slaweqahh, so You want to have it still running for stable branches15:25
lajoskatonaslaweq: then I create a patch for deleting the test, make the neutron patch depend on that and hope for the best?15:25
lajoskatonaslaweq:  I don't want, but now we run the same tempest, or not?15:26
slaweqpersonally I think that this can be removed from tempest api tests15:26
lajoskatonaok, I push a patch with the deletion15:26
slaweqif we want to have it in stable branches, we can add it maybe to fullstack tests there - mlavalle what do You think about that?15:26
*** tssurya has joined #openstack-meeting15:26
mlavalleyesh, fullstack is a good approach15:27
lajoskatonaYou mean to have fullstack test for it on stab;e branches?15:28
lajoskatonaI mean for this test: test_rule_create_fail_for_direction_ingress?15:28
slaweqlajoskatona: yes, basically on master we don't need it as we would always skip it, so we can remove if from there and move to fullstack but only for stable branches where it should raise this expetion as it's now15:29
slaweqso it would be 2 patches: 1 to remove this test from neutron_tempest_plugin and later patch with adding it to fullstack in stable/rocky15:29
slaweqand then some cherry-picks to stable/queens and stable/pike also15:30
lajoskatonaslaweq: ok, I create a note for it for my tasklist :-)15:30
slaweqlajoskatona: thx :)15:30
slaweqI can help You with that if You want15:30
mlavalleslaweq likes fullstack tests a lot15:31
lajoskatonaslaweq:thanks15:31
slaweqmlavalle: LOL15:31
slaweqespecially debugging it :)15:31
*** eharney_ has joined #openstack-meeting15:31
slaweqok, lets move on15:31
slaweq#topic Bugs15:31
*** openstack changes topic to "Bugs (Meeting topic: neutron_qos)"15:31
slaweqfirst one:15:32
slaweq#link https://bugs.launchpad.net/neutron/+bug/178400615:32
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:32
slaweqmlavalle: any updates?15:32
mlavalleI didn't have to to work on this one15:32
mlavalletime^^^^15:32
mlavalleI'll try again this week15:32
*** ttsiouts has quit IRC15:33
slaweqsure15:33
slaweqnext one:15:33
slaweq#link https://bugs.launchpad.net/neutron/+bug/177905215:33
openstackLaunchpad bug 1779052 in neutron "Quality of Service (QoS) in Neutron (documentation) - only different types rules can be combined in QoS policy" [Low,In progress] - Assigned to Slawek Kaplonski (slaweq)15:33
*** ttsiouts has joined #openstack-meeting15:33
slaweqthere is patch https://review.openstack.org/#/c/581941/ still no any response from patch owner, I updated this PS today15:34
*** eharney has quit IRC15:34
slaweqnext one15:34
slaweq#link https://bugs.launchpad.net/neutron/+bug/177616015:35
openstackLaunchpad bug 1776160 in neutron "'burst' does not take effect for neutron egress qos bindlimit by ovs" [Undecided,New]15:35
slaweqI wanted to check it but I still didn't have time15:35
slaweqif someone wants to play with it, feel free :)15:35
slaweqand the last one on my list:15:36
slaweq#link https://bugs.launchpad.net/neutron/+bug/178518915:36
openstackLaunchpad bug 1785189 in neutron "Floatingip and router bandwidth speed limit failure" [Undecided,In progress] - Assigned to Brian Haley (brian-haley)15:36
slaweqPatch is proposed: https://review.openstack.org/#/c/596637/15:36
mlavalleThere is a comment from liuyulong that has been unaddressed for several weeks now15:37
slaweqhave one +2 but also some -1 - there are some questions with no answers there, I think we can review it and wait few more weeks for update from owner of patch15:37
*** armstrong has joined #openstack-meeting15:37
liuyulongyep15:37
*** ttsiouts has quit IRC15:38
*** ianychoi has quit IRC15:39
*** armax has quit IRC15:39
slaweqand that's all from my side15:39
slaweqdo You have anything else You want to talk?15:39
liuyulongGive me one minute, thanks.15:39
slaweq#topic Open Discussion15:39
*** openstack changes topic to "Open Discussion (Meeting topic: neutron_qos)"15:39
slaweqsure liuyulong, go on :)15:39
liuyulongIt's bout the port forwarding floating IP QoS.15:39
liuyulongSince the port_forwarding l3 agent extension handle it's own floating IPs, I think we can add these IPs to L3 (fip_qos) QoS extension procedure.15:40
slaweqit sounds like new RFE for me :)15:41
liuyulongI'll add a LP bug for it.15:41
mlavalleok15:41
mlavallewe can review it soon15:41
liuyulongLet all floating IPs can be limited under the QoS policy.15:42
liuyulongThanks15:43
*** munimeha1 has quit IRC15:43
slaweqok, let's create lp bug for that and discuss there15:43
slaweqthx for bringing this up liuyulong :)15:43
liuyulongslaweq, you are welcome. : )15:44
*** diablo_rojo has joined #openstack-meeting15:44
slaweqok, anything else?15:44
mlavallenot from me15:44
slaweqif not, I will give You back about 15 minutes :)15:44
liuyulongno from me15:44
lajoskatonabye15:45
slaweqok, so thx for attending15:45
*** lajoskatona has left #openstack-meeting15:45
slaweq#endmeeting15:45
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"15:45
openstackMeeting ended Tue Oct  9 15:45:10 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:45
ralonsohthanks, bye15:45
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_qos/2018/neutron_qos.2018-10-09-15.00.html15:45
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_qos/2018/neutron_qos.2018-10-09-15.00.txt15:45
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_qos/2018/neutron_qos.2018-10-09-15.00.log.html15:45
mlavalleo/15:45
rubasovbye15:45
*** aojeagarcia has quit IRC15:46
*** janki has joined #openstack-meeting15:52
*** a-pugachev has quit IRC15:55
*** macza has joined #openstack-meeting15:59
slaweq#startmeeting neutron_ci16:00
openstackMeeting started Tue Oct  9 16:00:47 2018 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
slaweqwelcome (again) :)16:00
mlavalleo/16:00
njohnstono/16:01
slaweq#topic Actions from previous meetings16:01
*** openstack changes topic to "Actions from previous meetings (Meeting topic: neutron_ci)"16:01
slaweqnjohnston Reduce to a single fullstack job named 'neutron-fullstack' that calls python3 in tox.ini and runs on bionic nodeset16:01
njohnstonso for that I hijacked bcafarel's change https://review.openstack.org/#/c/604749/16:02
njohnstonI am tinkering with it to figure out the issues with neutron-fullstack job16:03
*** belmorei_ has quit IRC16:03
slaweqwhat issue exactly?16:04
njohnstonhttp://logs.openstack.org/49/604749/3/check/neutron-fullstack/612006a/job-output.txt.gz#_2018-10-04_01_32_01_50310316:05
slaweqbut do we need still compile ovs on those tests?16:06
njohnstonlooks like it is trying to compile OVS16:06
njohnstonI don't think so - that is not a change I introduced16:06
slaweqI know16:06
slaweqIIRC we had something like that because of some missing patch(es) in Ubuntu ovs package16:06
*** ircuser-1 has quit IRC16:07
slaweqhttps://github.com/openstack/neutron/blob/master/neutron/tests/contrib/gate_hook.sh#L8216:07
slaweqit's here16:07
njohnstonah!16:07
slaweqmaybe we should check if this commit is already included in version provided by Bionic/Xenial and then get rid of this16:08
njohnstonagreed16:08
mlavallethat's a good point16:08
njohnstonI can look into that16:08
slaweqthx njohnston :)16:08
njohnston#action njohnston look into fullstack compilation of ovs still needed on bionic16:09
njohnstonthanks for a great memory slaweq!16:09
slaweqyw njohnston :)16:09
slaweqok, lets move to the next one16:09
slaweqnjohnston Ask the infra team for what ubuntu release Stein will be supported16:09
njohnstonthe answer is: bionic16:10
mlavallevery good email summary on that one16:10
slaweqyes, thx njohnston16:10
njohnstonI didn't send out that email to all, so let me summarize it here.16:10
*** belmoreira has joined #openstack-meeting16:10
njohnstonI brought this up to the TC, noting the point that we should be moving on to bionic based on our governance documents16:11
njohnstonGiven how zuulv3 has pushed the onus of CI job definition maintenance to the project teams, I asked if the TC would be announcing this change or otherwise managing it16:11
njohnstonThis prompted a bit of discussion; the conclusion of which was that the TC doesn't have a ready answer - yet16:12
njohnston#link http://eavesdrop.openstack.org/irclogs/%23openstack-tc/%23openstack-tc.2018-10-03.log.html#t2018-10-03T16:46:2116:12
slaweqok then, so what if e.g. we will switch all our jobs to bionic but other projects will still run xenial at the end of Stein? is it possible?16:13
slaweqshould we just go on and try to switch all our jobs or should we wait for some more "global" action plan?16:13
njohnstonThe TC will need to mitigate that risk.  They are still smarting after the last time this happened, and everyone was running xenial except Trove, which was back on trusty.  So they know the danger, better than we do.16:13
njohnstonI think we should go ahead andm switch our jobs16:14
mlavalleyes16:14
mlavallewe do our bit16:14
mlavalleand let the TC worry about the global picture16:14
mlavallewe can warn them in the ML16:14
mlavallewhen we are about to do it16:15
slaweqso maybe we can try first to clone our jobs to experimental queue and use them with Stein there and see how it will looks like16:15
slaweqwhat You think about it?16:15
mlavallereasonable16:15
njohnstonnote that we already have tests running on bionic - you can't test on py36 without bionic, so the openstack-toc-py36 job is already there16:15
slaweqyes, but I think more about all scenario/tempest/grenade jobs16:16
njohnstonbut yes, that is a reasonable plan, especially with complicated things like scenario tests16:16
slaweqand btw. what about grenade? should it run Rocky on Bionic and upgrade to Stein?16:16
slaweqdo You know maybe?16:16
njohnstonright, because we're not dealing with 100%pass vs 100% fail, we're dealing with fluctuations in fail trends a lot of the time16:16
njohnstonthe QA team is working on grenade because of the python3 challenge, so I think we can wait for the fruits of their labor16:17
njohnstonI don't know the specific answer, but if I am not mistaken the QA PTL is on the TC16:17
njohnstonso it should not escape notice16:18
slaweqyes, he is16:18
slaweqgmann is QA PTL IIRC16:18
njohnstonyep16:18
mlavalleyes16:18
slaweqok then16:18
slaweqso I think we should now create copies of our scenario/tempest/fullstack/functional jobs running on Bionic in experimental queue, right?16:18
njohnstonyes16:19
slaweqand then we will see what issues we have so we will be able to plan this work somehow16:19
njohnston+116:19
*** felipemonteiro has quit IRC16:19
slaweqI can do this first step then :)16:19
slaweqok?16:20
mlavalleyes16:20
slaweqthx mlavalle :)16:20
njohnstonI am grateful, thanks16:20
slaweq#action slaweq will create scenario/tempest/fullstack/functional jobs running on Bionic in experimental queue16:20
slaweqok, then move on16:20
slaweqnjohnston to check and add missing jobs to grafana dashboard16:20
njohnstonhttps://review.openstack.org/#/c/607586/ merged16:21
slaweqthx njohnston :)16:21
slaweqok, next one16:21
slaweq* slaweq to prepare etherpad with list of jobs to move to Bionic16:21
slaweqI start doing this today:16:21
slaweqhttps://etherpad.openstack.org/p/neutron-ci-bionic16:22
slaweqbut as I will do those experimental jobs I will also update this etherpad16:22
njohnstonsounds good16:22
*** ralonsoh has quit IRC16:22
slaweqnext was:16:23
slaweq* slaweq will report bug about failing trunk scenario test16:23
slaweqDone: https://bugs.launchpad.net/neutron/+bug/179587016:23
openstackLaunchpad bug 1795870 in neutron "Trunk scenario test test_trunk_subport_lifecycle fails from time to time" [High,Confirmed] - Assigned to Miguel Lavalle (minsel)16:23
slaweqsorry mlavalle that I forgot to ping You with this :)16:23
mlavallenp16:23
slaweqand the last one:16:24
mlavalleI'll work on it next16:24
slaweq* mlavalle will check failing trunk scenario test16:24
slaweqI guess it's not done, right? :P16:24
mlavalleyes16:24
slaweq#action mlavalle will check failing trunk scenario test16:24
slaweqI will add it for next week then16:24
slaweqthx mlavalle16:24
slaweqok, so that was all from last week16:24
slaweqnext topic16:25
slaweq#topic Grafana16:25
*** openstack changes topic to "Grafana (Meeting topic: neutron_ci)"16:25
slaweqhttp://grafana.openstack.org/dashboard/db/neutron-failure-rate16:25
*** diablo_rojo has quit IRC16:25
slaweqlooking at grafana it looks that we are generally quite good16:26
slaweqdo You want to talk about something specific?16:26
njohnstonneutron-grenade-dvr-multinode falling fast in the check queue \o/16:26
mlavallethere's been a slow down of activity over the past few days16:27
slaweqnjohnston: about this grenade job I want to talk a bit later :)16:27
slaweqmlavalle: yes, it looks that there wasn't anything in gate recently, most work in check queue16:27
mlavallemaybe also a bit of the Columbus Day holiday in the US16:28
njohnston+116:28
slaweqmight be16:28
slaweqbut basically it looks quite good in overall16:29
mlavalle\o/16:29
slaweqso lets talk about some specific jobs issues16:29
slaweq(which are already well known)16:29
slaweq#topic fullstack/functional16:29
*** openstack changes topic to "fullstack/functional (Meeting topic: neutron_ci)"16:29
slaweqI don't know why but I think we are again more often hit with issue like in https://bugs.launchpad.net/neutron/+bug/1687027  in functional tests16:30
openstackLaunchpad bug 1687027 in neutron "test_walk_versions tests fail with "IndexError: tuple index out of range" after timeout" [High,Confirmed] - Assigned to Miguel Lavalle (minsel)16:30
slaweqI saw it couple of times during this week16:30
slaweqe.g. http://logs.openstack.org/periodic/git.openstack.org/openstack/neutron/master/neutron-functional/e56b690/logs/testr_results.html.gz16:30
slaweqit's periodic job from today16:31
mlavalleshould I prioritize this one over the previous one?16:32
slaweqdid You saw it also recently?16:32
mlavalleI ahven't seen it16:32
mlavallelately16:32
slaweqmlavalle: I think that this issue with trunk tests is more important16:33
slaweqthis one is IMO stricly test only issue16:33
mlavalleyes, that's also my impression16:33
slaweqand trunk tests issue - we don't know, maybe it's "real" bug16:33
slaweqI will try to find few minutes to maybe reproduce this one16:34
slaweqif I will find something, I will let You know on next meeting :)16:34
mlavalleok16:35
slaweq#action slaweq will try to reproduce and triage https://bugs.launchpad.net/neutron/+bug/168702716:35
openstackLaunchpad bug 1687027 in neutron "test_walk_versions tests fail with "IndexError: tuple index out of range" after timeout" [High,Confirmed] - Assigned to Miguel Lavalle (minsel)16:35
slaweqspeaking about scenario jobs,16:35
slaweq#topic Tempest/Scenario16:35
*** openstack changes topic to "Tempest/Scenario (Meeting topic: neutron_ci)"16:35
slaweqmanjeets: any update on https://bugs.launchpad.net/neutron/+bug/1789434 ?16:35
openstackLaunchpad bug 1789434 in neutron "neutron_tempest_plugin.scenario.test_migration.NetworkMigrationFromHA failing 100% times" [High,Confirmed] - Assigned to Manjeet Singh Bhatia (manjeet-s-bhatia)16:35
*** armax has joined #openstack-meeting16:36
slaweqI guess he isn't here16:37
mlavallenope16:37
slaweqok, let's wait one more week and maybe we will have to start working on this16:38
mlavalleyes16:38
slaweqso, lets move on to the next topic16:39
slaweq#topic grenade16:39
*** openstack changes topic to "grenade (Meeting topic: neutron_ci)"16:39
slaweq(my "favorite" one recently)16:39
mlavalleLOL16:39
slaweqI spent about 3 days on debugging https://bugs.launchpad.net/neutron/+bug/179198916:40
openstackLaunchpad bug 1791989 in neutron "grenade-dvr-multinode job fails" [High,Confirmed] - Assigned to Slawek Kaplonski (slaweq)16:40
slaweqand I found nothing :/16:40
slaweqwell, almost nothing16:40
slaweqI have some patch which prints me a lot of informations like, openflow rules, bridges in ovs, namespaces, network config in namespaces, iptables and so on16:41
slaweqand I was comparing it from moment when ping was not working and when it starts working16:41
slaweqand all was the same16:41
slaweqhaleyb proposed some patch to add permanent neighbors in fip and qrouter namespaces: https://review.openstack.org/#/c/608259/16:42
slaweqbut this didn't helps16:42
slaweqso I started ssh to those nodes with running job and I started looking for tcpdump when ping was not working16:42
slaweqand I found that icmp requests are comming to vm's tap device16:43
*** gyee has joined #openstack-meeting16:43
slaweqand vm sends icmp reply but this reply is gone somewhere in br-int16:43
*** mriedem is now known as mriedem_stew16:43
mlavallethat sounds like flows not properly setup maybe16:44
slaweqso today I added another thing to my dnm patch (https://review.openstack.org/#/c/602204/) to flush fdb entries from br-int when ping will not work first time and check then if after this ping will start working16:44
slaweqmlavalle: all flows were the same16:44
slaweqopenflow rules I mean16:44
mlavalleok16:44
slaweqso, I am trying to spot this issue again in my dnm patch again and see if this flush will help or not16:45
slaweqbut since yesterday evening it looks like this job is working fine again16:45
haleyband it eventually starts working, which is why we started looking at arp.  i'll await the testing...16:45
* haleyb is late for the party16:45
slaweqI can't spot it in my DNM patch - ping works every time before in first attempt16:46
*** armax has quit IRC16:46
slaweqand looking at kibana: http://logstash.openstack.org/#/dashboard/file/logstash.json?query=build_name:%5C%22neutron-grenade-dvr-multinode%5C%22%20AND%20build_status:FAILURE%20AND%20message:%5C%22die%2067%20'%5BFail%5D%20Couldn'%5C%5C''t%20ping%20server%5C%2216:47
njohnstondown to only 37% failure - makes me wonder if something was fixed elsewhere and our issue was just a manifestation http://grafana.openstack.org/d/Hj5IHcSmz/neutron-failure-rate?panelId=22&fullscreen&orgId=116:47
*** jbadiapa has joined #openstack-meeting16:47
slaweqit looks that it really didn't happen since yesterday16:47
slaweqnjohnston: yes, that's exactly what I think now16:48
slaweqbut TBH I'm really puzzled with this one :/16:48
slaweqso, any questions/comments about this?16:49
njohnstonwould it be useful to ping infra and ask i fthey fixed anything networking-related?16:49
njohnstonor moved their capacity around - drained all jobs from a cloud, perhaps?16:49
slaweqnjohnston: yes, I can ask them16:49
mlavalleinteresting16:49
njohnstonthats all I can think of16:49
slaweqI think that I can only ask them if they maybe did/fixed something which might be related recently and wait to see how results will go in grafana for next few days16:51
slaweqI was also trying to reproduce it locally on similar 2 nodes dvr env with rocky but I couldn't - all worked fine16:51
*** eharney_ is now known as eharney16:52
slaweqok, I think we can then move on to the next topic16:53
slaweq#topic periodic16:53
*** openstack changes topic to "periodic (Meeting topic: neutron_ci)"16:53
slaweqI just wanted to mention that last week we had issue https://bugs.launchpad.net/neutron/+bug/1795878 which I found after CI meeting so I didn't mention it then :)16:54
openstackLaunchpad bug 1795878 in neutron "Python 2.7 and 3.5 periodic jobs with-oslo-master fails" [High,Fix released] - Assigned to Bernard Cafarelli (bcafarel)16:54
slaweqit's now fixed https://review.openstack.org/60787216:54
mlavallecool16:54
slaweqand that's all related to periodic jobs from me16:55
slaweq#topic Open discussion16:55
*** openstack changes topic to "Open discussion (Meeting topic: neutron_ci)"16:55
slaweqI want also to mention one more thing16:55
slaweqduring the PTG I was on some QA team sessions and they asked us that we should move templest_plugins from neutron stadium projects to separate repos or to neutron_tempest_plugin repo16:56
slaweqmlavalle: which option would be better in Your opinion?16:56
slaweqlist of plugins is on https://docs.openstack.org/tempest/latest/plugin-registry.html16:56
mlavalleI don't have a strong opinion16:57
slaweqme neighter16:57
mlavallewe share a lot of tests with the Stadium, don't we?16:57
slaweqI don't know if a lot16:57
mlavallesince it is testing based on the API16:58
slaweqmaybe we should discuss about it on ML first then?16:58
mlavalleyes, let's ask them16:58
slaweqmlavalle: will You send an email or should I?16:58
njohnston That makes sense, since the stadium projects may not have a uniform way they approach this16:58
mlavalleI suspect many of them may not have man power to handle yet another repo16:59
mlavallelet's see what they say16:59
mlavalleyes, I'll send the message16:59
slaweqok, thx mlavalle16:59
*** iyamahat has quit IRC16:59
slaweq#action mlavalle to send an email about moving tempest plugins from stadium to separate repo17:00
slaweqok, we are out of time17:00
slaweqthx for attending17:00
slaweq#endmeeting17:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"17:00
openstackMeeting ended Tue Oct  9 17:00:15 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:00
mlavalleo/17:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_ci/2018/neutron_ci.2018-10-09-16.00.html17:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_ci/2018/neutron_ci.2018-10-09-16.00.txt17:00
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_ci/2018/neutron_ci.2018-10-09-16.00.log.html17:00
njohnstonthanks all17:00
*** yamamoto has quit IRC17:08
*** yamamoto has joined #openstack-meeting17:08
*** davidsha has quit IRC17:11
*** mlavalle has left #openstack-meeting17:14
*** annp_ has quit IRC17:14
*** janki has quit IRC17:14
*** iyamahat has joined #openstack-meeting17:14
*** iyamahat_ has joined #openstack-meeting17:17
*** sambetts_ is now known as sambetts|afk17:18
*** iyamahat has quit IRC17:20
*** janki has joined #openstack-meeting17:22
*** apetrich has quit IRC17:22
*** jamesmcarthur has quit IRC17:22
*** jamesmcarthur has joined #openstack-meeting17:22
*** cloudrancher has quit IRC17:26
*** cloudrancher has joined #openstack-meeting17:27
*** jamesmcarthur has quit IRC17:27
*** ralonsoh has joined #openstack-meeting17:28
*** yamahata has joined #openstack-meeting17:39
*** tssurya has quit IRC17:39
*** rubasov_ has quit IRC17:40
*** ralonsoh has quit IRC17:40
*** ociuhandu has quit IRC17:45
*** jamesmcarthur has joined #openstack-meeting17:45
*** Swami has joined #openstack-meeting17:49
*** electrofelix has quit IRC17:50
*** armax has joined #openstack-meeting17:58
*** yamamoto has quit IRC18:07
*** yamamoto has joined #openstack-meeting18:07
*** yamamoto has quit IRC18:08
*** yamamoto has joined #openstack-meeting18:09
*** jamesmcarthur has quit IRC18:10
*** jamesmcarthur has joined #openstack-meeting18:10
*** yamamoto has quit IRC18:13
*** armstrong has quit IRC18:24
*** mriedem_stew is now known as mriedem18:31
*** tobiash has joined #openstack-meeting18:35
*** ijw has quit IRC18:37
*** janki has quit IRC18:38
*** Shrews has joined #openstack-meeting18:43
*** armax has quit IRC18:49
*** yamamoto has joined #openstack-meeting18:51
*** eharney has quit IRC18:53
*** ijw has joined #openstack-meeting18:57
fungiwho's around to talk infra shop?18:59
Shrewso/18:59
fungi#startmeeting infra19:00
openstackMeeting started Tue Oct  9 19:00:01 2018 UTC and is due to finish in 60 minutes.  The chair is fungi. Information about MeetBot at http://wiki.debian.org/MeetBot.19:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:00
*** openstack changes topic to " (Meeting topic: infra)"19:00
openstackThe meeting name has been set to 'infra'19:00
fungi#link https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting#Agenda_for_next_meeting19:00
fungii suppose i should take a look at this thing; just a sec ;)19:00
ianwo/19:00
clarkbI'm sort of around too19:00
fungi#topic Announcements19:00
*** openstack changes topic to "Announcements (Meeting topic: infra)"19:00
clarkbI did trim the agenda and add an entry for you earlier today or was that last night?19:00
fungiclarkb: any important announcements?19:00
fungii think it was today, or at least that's when i saw the update notification19:01
clarkbI don'tthink so other than summit is fast approaching and then holidays then its 2019 and wow time flies19:01
clarkbsomething something trusty eol19:01
*** jamesmcarthur has quit IRC19:02
fungiyeah, um, don't forget to book flights/hotel and register if you're planning to go to berlin with us!19:03
ssbarnea_i am here too19:03
*** jamesmcarthur has joined #openstack-meeting19:03
fungi#topic Actions from last meeting19:03
*** openstack changes topic to "Actions from last meeting (Meeting topic: infra)"19:03
fungi#link http://eavesdrop.openstack.org/meetings/infra/2018/infra.2018-09-25-19.01.html Minutes from last meeting19:03
fungii see nothing, so i think we're good19:04
*** weshay has joined #openstack-meeting19:04
fungi#topic Specs approval19:04
*** openstack changes topic to "Specs approval (Meeting topic: infra)"19:04
funginothing mentioned on the agenda up for a council vote19:04
fungii still owe an alternative implementation writeup for the letsencrypt/acme spec19:05
clarkbI think I meant to follow up on the 3rd party ci spec19:05
fungioh, sure we can do that19:05
clarkbbut then the gate fires happened and I was very distracted19:05
ianwyes, unless people's mind has changed due to intervening conferences, etc, i think that's ready19:05
clarkbI've written a note to follow up after the current conference19:06
fungi#link https://review.openstack.org/563849 Direction setting for 3rd Party CI19:06
fungiare we good putting this up for council vote through thursday?19:07
clarkb++19:07
*** eharney has joined #openstack-meeting19:08
fungi#info The "Direction setting for 3rd Party CI" spec is open for council voting until 19:00 UTC Thursday, October 11.19:08
fungiany objections?19:08
fungiif you have any concerns, be sure to comment on the review in the next 48 hours!19:08
*** markvoelker has quit IRC19:09
fungi#topic Priority Efforts - A Task Tracker for OpenStack19:09
*** openstack changes topic to "Priority Efforts - A Task Tracker for OpenStack (Meeting topic: infra)"19:09
*** markvoelker has joined #openstack-meeting19:09
fungii don't really have any storyboard updates this week, and diablo_rojo is in the middle of conducting an upstream institute training in some farflung corner of the world right now19:10
fungioh, we can hyperlink task footers from gerrit if anyone wants to review the corresponding system-config changes:19:10
fungi#link https://review.openstack.org/607699 Hyperlink task footers19:11
fungi(and its parent)19:11
fungialso diablo_rojo has posted an attachments spec she'd appreciate some reviews on:19:11
fungi#link https://review.openstack.org/607377 [WIP] StoryBoard Story Attachments19:11
*** jamesmcarthur has quit IRC19:12
fungiand anyone interested in storyboard, we'll (probably) have our regular weekly meeting tomorrow at 19:00 utc in this same channel19:12
*** AJaeger has joined #openstack-meeting19:12
*** jamesmcarthur has joined #openstack-meeting19:12
fungior find us in #openstack-storyboard any other time19:12
* AJaeger apologies for missing the bell19:12
*** armax has joined #openstack-meeting19:12
fungi#topic Priority Efforts - Update Config Management19:13
*** openstack changes topic to "Priority Efforts - Update Config Management (Meeting topic: infra)"19:13
fungii see a couple of possible subtopics mentioned here with no associated proposer19:13
fungitopic:puppet-4 and topic:update-cfg-mgmt19:13
ssbarnea_fungi - ins't the correct irc channel #storyboard ? --- without openstack prefix?19:14
fungissbarnea_: yep! fingers failed me19:14
fungithanks for the correction19:14
fungii see 20 open changes in the first topic and 11 in the second19:14
fungii guess this bullet item is here to remind us to review these changes19:14
fungithe other possible subtopic on the agenda says "Zuul as CD engine"19:15
fungianyone here who added that?19:15
*** markvoelker has quit IRC19:15
Shrewsmaybe corvus? i think that may have involved containery-things?19:16
fungiokay, well, zuul as a cd engine seems like a great idea. i know we've talked about it and are starting to do it, so...19:16
corvusif i added it, it was a while ago :)19:16
fungicool, so maybe nothing we need to cover on this in the meeting today unless you're aware of something19:17
corvusnot immediately -- i think the next steps from that (coming out of the ptg) are that if we want to have zuul trigger its own config updates, we need to move the entire project-creation process to ansible19:17
*** markvoelker has joined #openstack-meeting19:17
fungithat sounds like what i remember19:17
clarkboh Ihve changes that add the zuulcd user to bridge.o.o which should have the correct topic on them19:18
clarkbwhich is another prestep for that I think19:18
fungiand a sensible choice anyway since part of why we originally started using ansible (before zuul v2.5) was because we'd stretched the nearly nonexistent orchestration facilities of puppet to its breaking point with our new project automation19:19
corvusclarkb: ah yep, thanks19:19
fungi#link https://review.openstack.org/604925 Add zuul user to bridge.openstack.org19:19
fungiit's in topic:update-cfg-mgmt19:20
fungiso, yes!19:20
ianwi plan to also keep exploring the containierisation of graphite.o.o ... which is sort of related because it's all role based and you could see it being part of a CD workflow19:20
fungithat sounds great19:21
fungii similarly have a to do item to try out the "official" mailman3 container image with a mind to that19:21
fungibasically redo my mm3 poc with their container19:21
fungianything else on this for now?19:21
fungiwe have a fullish assortment of general topics waiting, so let's see how many i can plow through in the next 38 minutes19:22
fungi#topic OpenDev19:22
*** openstack changes topic to "OpenDev (Meeting topic: infra)"19:22
fungiwe are opendev. any questions?19:22
fungi;)19:22
fungithere's some nameserver changes still out there which need reviews i guess?19:22
clarkbI completely failed to schedule a meeting with the foundation19:23
fungilooks like those merged19:23
clarkbI think we were somewhat surprised as the zuul interest last week and that consumed our time at sansiblefest19:23
fungioh, except one19:23
fungi#link https://review.openstack.org/605092 Add opendev nameservers19:23
corvusi've lost the thread on opendev nameservers; maybe i can pick them up next week, but if anyone else wants to push forward on them in the interim you're welcome to :)19:23
fungilooks like we got ahead of ourselves with the firewall rules and either need public slave nameservers deployed first or need to do some manual bootstrapping of the hidden master19:24
clarkbI think corvus mentioned there would be manual firewall bootstrapping19:25
fungii'd love to work on moving this forward, but i'm hesitant to commit to anything else for the next few days until i get more caught up19:25
clarkbpuppet will deploy things the axfr's just won't work immediately until a human edits the firewall19:25
fungiwell, for the moment we need some workarounds to get 605092 in that case19:26
fungier, to get 605092 passing integration tests19:26
clarkbah19:26
corvusyeah, i guess that needs to be split into 2 commits19:26
fungido we want to talk about anything else specific to the opendev domain, rebranding, renaming of services, et cetera today?19:28
fungior save that for when clarkb gets a marketing and promotion discussion set up first so we can figure out our initial messaging (as discussed at the ptg)?19:28
corvusi'm good till then19:29
*** jamesmcarthur has quit IRC19:29
fungii consider everyone else's deafening silence as tacit approval19:29
fungi;)19:29
fungi#topic discuss silencing rsync from console logs (ssbarnea)19:29
*** openstack changes topic to "discuss silencing rsync from console logs (ssbarnea) (Meeting topic: infra)"19:29
fungi#link https://review.openstack.org/#/q/topic:quiet-rsync+(status:open+OR+status:merged) silencing rsync from console logs19:30
*** jamesmcarthur has joined #openstack-meeting19:30
ssbarnea_so..., some ansible rsync(s) are quite verbose by default and they spam console logs in some extreme cases where a single command taking ~40% of total console length.19:30
fungihowever, unless we save that somewhere we have no way to diagnose artifact collection failures, right?19:31
ssbarnea_I know for sure that I seen some task doing rsync on ara reports that were huge19:31
fungitripleo does that, for sure19:31
ssbarnea_fungi: --quiet does not hide errors, only success.19:31
fungimaybe openstack-ansible too?19:31
ssbarnea_fungi, i know that here some more places,....19:32
fungissbarnea_: sure, but --quiet also doesn't tell you what files you didn't collect because you put them in the wrong directory or had an overly-picky regex19:32
ssbarnea_fungi: neither non quiet doesn't tell you what you didn't collect.19:33
ssbarnea_and what you collected is visible at the destination anyway.19:33
ssbarnea_i doubt we do have tasks removing them after collection19:33
fungii'm mostly trying to represent the other side in this argument but i don't feel super strongly either way. the changes in question are just for openstack-specific jobs, not other zuul jobs. it's been suggested that we can make the console log less verbose by default with collapseable sections instead. does this address your concerns?19:34
ssbarnea_fungi: we may make the --quiet optional? like enabled by default and disabled for special cases (like a debug build)19:34
*** armax has quit IRC19:35
ssbarnea_can me make a rule (lines/task) of what counts as reasonable usage and what counts as spam? if we spot a task as spammy, we silence it?19:35
*** awaugama has quit IRC19:35
ssbarnea_i think nobody would complain if there are 10-20 lines, but when it goes >100 it starts to become spam.19:35
*** jamesmcarthur has quit IRC19:35
ssbarnea_and while I like ARA, I find its number of files as super-spam.19:36
fungiusually the ones i end up wanting to look at, personally, are docs/website publication job logs because invariably i've screwed up where i put files or how i matched them19:36
AJaegeroh yeah, those are always fun ;(19:36
*** jamesmcarthur has joined #openstack-meeting19:36
fungialso release jobs because of release artifacts being skipped due to incorrect naming19:37
ssbarnea_ideally we should dump list of files to an separate log file and avoid using console, but sadly for us ansible had no such support.19:38
fungiwell, also there's a catch-2219:39
fungisince we need to collect the file containing the list of files?19:39
ssbarnea_i am not sure if the zuul special callback can do some smart filtering for this specific case.19:39
fungisort of a gödel's completeness problem i guess19:39
ssbarnea_if we hack the callback to avoid console output, we still can have the full list captured by ara as json. still not sure how easy is this to implement.19:40
fungiyeah, i'm unfortunately not sure we have the attention of the right people in the meeting today to come to a conclusion on this topic19:41
fungior at least nobody's really speaking up19:41
ssbarnea_fungi: in this case lets move on, we can postpone it.19:42
fungiunless someone has something they want to add on this, i can move on to your next topic19:42
fungithis next topic isn't really phrased as a topic. i'll see what i can come up with19:42
fungi#topic ask.openstack.org with tag #openstack-infra (ssbarnea)19:42
*** openstack changes topic to "ask.openstack.org with tag #openstack-infra (ssbarnea) (Meeting topic: infra)"19:42
fungiso... in the past i and others have alerted people who ask infra questions on the openstack ask site that we don't really do infra support there and directed them to irc or the ml19:43
ianwi think "just drop the logs" when people then think "hey, i've used that before" makes it a hard argument for people to vote on.  but an intermediate thing, like having it logged separately somehow, certainly makes it easier to come at19:43
fungissbarnea_: are you volunteering to be our ask.o.o answerer?19:43
ssbarnea_fungi: yes, I do, we can use a specific topic openstack-infra there.19:44
ssbarnea_the idea is to provide support, but only for things that are specific to us.19:44
fungii have no objection to you seeking out seemingly infra-oriented questions on that site and giving answers... my main concern (having dealt with it for years) is that it's like a cross between a wiki and a blog where answers get outdated and rot and become attractive nuisances19:45
AJaegerwe have so far answered the "common" questions in the infra-manual19:45
fungiyes, at times when i've answered infra-related questions on ask.o.o i've tried to stick to providing hyperlinks to our documentation19:46
ssbarnea_stackoverflow never become obsolete, the wiki or docs are much harder to update. yep hyperlinks are good.19:46
fungibe that infra-manual or tool-specific docs19:46
AJaegerand sometimes we wrote another section for our docs so that we can link next time ;)19:47
ssbarnea_we can just experiment for few weeks and wee if it works or not.19:47
ianwi'm not sure i'd even considered people asking infra questions there.  i can subscribe to that tag, but I think we have long-standing issues knowing that subscriptions on ask.o.o don't quite work properly19:47
fungiso anyway, i see no problem with people who are interested in dealing with ask.o.o curating and answering/updating/combining/closing questions there19:48
fungiif you need moderator access and don't have it yet, let me know and i can figure out how to elevate you to a mod19:48
*** jamesmcarthur has quit IRC19:48
ianwwe need to update it all during the next sprint ... i think most of the puppet has been updated ... and then maybe subscriptions will work better and be easier to follow?19:48
fungibut in general i'm going to focus on answering questions in irc and on mailing lists and getting answers to common questions answered in relevant documentation, as AJaeger mentioned19:49
ssbarnea_is based on osqa or something else? i had prev exp with osqa.19:49
* fungi has no idea what osqa is19:49
ssbarnea_fungi: https://github.com/dzone/osqa19:50
AJaegerfungi, agree with your comments - if there're volunteers like ssbarnea_, let him try it...19:50
fungissbarnea_: ahh, no. see site footer: This site is powered by Askbot. http://askbot.com/19:50
ianwssbarnea_: no it's askbot19:50
fungithe author used to be contracted to help us support it, but he had less and less time to work on that over the years19:51
*** jamesmcarthur has joined #openstack-meeting19:51
ianwssbarnea_: if you'd like to take on upgrades, i'd be happy to liaise with you as i've done a bunch of puppet for xenial update, but the service (and all support bits) needs updating19:51
ianwthere's also a mail out there about issues with it when i looked into it19:52
fungithis site basically came about 1. because we had old spam-filled web forums full of misinformation we wanted to close down and 2. stackoverflow wouldn't give the osf the time of day when they asked about setting up a zone or whatever there to corral the openstack-related questions19:52
ssbarnea_ianw: let me first see if it worth investing in it, without enough users it would be close to useless.19:52
fungi6.5 minutes remaining19:53
fungi#topic Upgrade sprint next week (clarkb)19:53
*** openstack changes topic to "Upgrade sprint next week (clarkb) (Meeting topic: infra)"19:53
fungi"Should be a good time in the cycle to do some upgrades and we need to move off trusty."19:53
fungihe's hopefully getting ready to go on stage right now19:53
ianwssbarnea_: http://lists.openstack.org/pipermail/openstack-dev/2018-April/129078.html for reference19:54
fungiso this is more of a reminder. people who want to help work on upgrading our servers off trusty... let's do that19:54
clarkbya very shortly. I just wanted to see if we could get concerted effort around this next week19:54
fungi#topic Mirror/network issues at mirror.us-west-1.packethost.openstack.org (ssbarnea)19:54
*** openstack changes topic to "Mirror/network issues at mirror.us-west-1.packethost.openstack.org (ssbarnea) (Meeting topic: infra)"19:54
fungiwe _think_ this one is due to hypervisor hosts running out of disk. we don't control them19:55
fungilast night i "preallocated" the rest of the rootfs on this server by writing zeroes to a file until we ran out of space, then deleting it19:55
ssbarnea_fungi: so what can we do to avoid these errors? other than praying19:55
ianwyeah ... although with the sprint, i'm not sure how much heroic effort we want to put into puppet things v container things.  but the container stuff is all green-fields ATM, so we need to design some sort of process around that19:55
fungiwe had two outages yesterday where i found it in a "shutoff" state according to nova before the preallocation was done19:56
fungiit's been up since, so hopefully this has helped19:56
fungiin this case i think it's due to it being a small, dedicated cloud rather than a public cloud provider where they tend to size and track workloads a little more effectively19:56
funginot that we don't see occasional unannounced outages for our control plan servers in large public clouds as well19:57
fungier, control plane19:57
*** stevebaker has quit IRC19:57
fungigoing to go to open discussion for this last topic19:57
fungi#topic Open discussion19:58
*** openstack changes topic to "Open discussion (Meeting topic: infra)"19:58
ianwfungi: speaking of small dedicated clouds, have you heard any more on the armci cloud?19:58
fungiianw: nada19:58
fungisomeone added something here which looks more like a bug report:19:58
*** gouthamr has quit IRC19:58
fungi"logs.openstack.org does not return character encoding for served files, thus confusing browser into rendering logs with garbage due to defaulting to US-ANSI instead of UTF-8. This can avoded by setting 'Content-Type: text/plain; charset=utf-8' instead of current 'Content-Type: text/plain'. Firefox inspect message: The character encoding of the HTML document was not declared. The document will19:58
*** dmellado has quit IRC19:58
fungirender with garbled text in some browser configurations if the document contains characters from outside the US-ASCII range. The character encoding of the page must be declared in the document or in the transfer protocol. job-output.txt.gz"19:58
ssbarnea_it was me19:58
ssbarnea_not sure where I should have raise it19:59
fungi#link https://git.openstack.org/cgit/openstack-infra/puppet-openstackci/tree/templates/logs.vhost.erb19:59
fungithat's the configuration it's using19:59
fungithere's also a logs-dev.vhost.erb we can use to test changes (points to the same docroot)20:00
ssbarnea_fungi: ok, in this case I will make a storyboard for it20:00
fungiand we're out of time20:00
ssbarnea_and try to fix it20:00
fungithanks, ssbarnea_!20:00
fungiand thanks everyone! discussion can continue in #openstack-infra20:00
fungi#endmeeting20:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"20:01
openstackMeeting ended Tue Oct  9 20:00:59 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/infra/2018/infra.2018-10-09-19.00.html20:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/infra/2018/infra.2018-10-09-19.00.txt20:01
openstackLog:            http://eavesdrop.openstack.org/meetings/infra/2018/infra.2018-10-09-19.00.log.html20:01
*** AJaeger has left #openstack-meeting20:01
*** Shrews has left #openstack-meeting20:01
*** tobiash has left #openstack-meeting20:01
*** ijw_ has joined #openstack-meeting20:13
*** ijw has quit IRC20:13
*** pcaruana has quit IRC20:37
*** ijw_ has quit IRC20:41
*** ijw has joined #openstack-meeting20:42
*** erlon_ has quit IRC20:50
*** gouthamr has joined #openstack-meeting20:50
*** ttsiouts has joined #openstack-meeting20:51
*** dmellado has joined #openstack-meeting20:53
*** ttsiouts has quit IRC21:00
*** ttsiouts has joined #openstack-meeting21:00
*** eharney has quit IRC21:05
*** bobh has quit IRC21:08
*** stevebaker has joined #openstack-meeting21:10
*** priteau has quit IRC21:15
*** jamesmcarthur has quit IRC21:16
*** Emine has quit IRC21:17
*** raildo has quit IRC21:18
*** dustins has quit IRC21:24
*** cloudrancher has quit IRC21:26
*** cloudrancher has joined #openstack-meeting21:27
*** armax has joined #openstack-meeting21:34
*** ttsiouts has quit IRC21:39
*** ttsiouts has joined #openstack-meeting21:39
*** bobh has joined #openstack-meeting21:41
*** ttsiouts has quit IRC21:44
*** bobh has quit IRC21:45
*** armax has quit IRC21:54
*** bobh has joined #openstack-meeting21:54
*** rossella_s has quit IRC22:03
*** rossella_s has joined #openstack-meeting22:03
*** bobh has quit IRC22:09
*** slaweq has quit IRC22:17
*** rossella_s has quit IRC22:36
*** ykatabam has joined #openstack-meeting22:39
*** rossella_s has joined #openstack-meeting22:40
*** rcernin has joined #openstack-meeting22:42
*** mriedem has quit IRC22:57
*** hongbin has quit IRC22:58
*** lbragstad has quit IRC23:01
*** slaweq has joined #openstack-meeting23:11
*** efried has quit IRC23:12
*** efried has joined #openstack-meeting23:13
*** slaweq has quit IRC23:16
*** _alastor1 has joined #openstack-meeting23:24
*** yamamoto has quit IRC23:28
*** ijw has quit IRC23:29
*** macza has quit IRC23:32
*** Swami has quit IRC23:43
*** erlon_ has joined #openstack-meeting23:44
*** sambetts|afk has quit IRC23:44
*** sambetts_ has joined #openstack-meeting23:45
*** jamesmcarthur has joined #openstack-meeting23:48
*** yamamoto has joined #openstack-meeting23:55

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