Tuesday, 2019-04-09

*** Swami has quit IRC00:08
*** gyee has quit IRC00:09
*** ijw has quit IRC00:14
*** ttsiouts has joined #openstack-meeting00:38
*** ttsiouts has quit IRC00:47
*** ttsiouts has joined #openstack-meeting00:48
*** ttsiouts has quit IRC00:52
*** lbragstad has joined #openstack-meeting00:55
*** Liang__ has joined #openstack-meeting00:56
*** ricolin has joined #openstack-meeting01:02
*** igordc has quit IRC01:06
*** jamesmcarthur has quit IRC01:09
*** _alastor_ has joined #openstack-meeting01:27
*** yamahata has quit IRC01:29
*** iyamahat has quit IRC01:32
*** hongbin has joined #openstack-meeting01:33
*** _alastor_ has quit IRC01:40
*** ricolin_ has joined #openstack-meeting01:50
*** ricolin has quit IRC01:50
*** apetrich has quit IRC01:58
*** njohnston has quit IRC02:05
*** lseki has quit IRC02:27
*** Liang__ is now known as LiangFang02:30
*** hongbin has quit IRC02:35
*** whoami-rajat has joined #openstack-meeting02:37
*** diablo_rojo has quit IRC02:37
*** hongbin has joined #openstack-meeting02:38
*** igordc has joined #openstack-meeting02:40
*** boxiang has quit IRC02:42
*** boxiang has joined #openstack-meeting02:42
*** hongbin has quit IRC02:49
*** hongbin has joined #openstack-meeting02:51
*** yamahata has joined #openstack-meeting02:59
*** yamamoto has quit IRC03:40
*** tpatil has joined #openstack-meeting03:50
*** lbragstad has quit IRC03:51
*** yamamoto has joined #openstack-meeting03:55
*** tashiromt has joined #openstack-meeting04:00
samP#startmeeting masakari04:00
openstackMeeting started Tue Apr  9 04:00:21 2019 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
samPHi all for masakari04:00
tpatilHi04:00
tashiromtHi04:00
*** shilpasd has joined #openstack-meeting04:00
samP#topic Stein Release04:00
*** openstack changes topic to "Stein Release (Meeting topic: masakari)"04:01
samP#link https://review.openstack.org/#/c/650362/04:01
samPRelease patch is currently under review.04:01
tpatilDoes masakari-dasboard comes under masakari?04:02
samPtpatil: no, it is a separate project. but it does not follow the release cycle04:03
tpatilHow to ensure to use the correct version of masakari-dasboard with Stein release?04:04
*** hongbin has quit IRC04:05
samPcurrent tag for masakari-dashboard is 0.3.0, which is the tip of the stable/stein branch04:05
samP#link https://github.com/openstack/releases/blob/master/deliverables/stein/masakari-dashboard.yaml04:06
tpatilOK, Got it04:06
tpatilThanks04:06
samPtpatil: np04:06
samP#topic Critical Bugs Patches04:08
*** openstack changes topic to "Critical Bugs Patches (Meeting topic: masakari)"04:08
samPAny bugs or patches need to discuss here?04:08
tpatilLP Bug: https://bugs.launchpad.net/masakari/+bug/181565704:08
openstackLaunchpad bug 1815657 in masakari "python 3 failures - /usr/bin/masakari-wsgi and unit tests" [High,In progress] - Assigned to Shilpa Devharakar (shilpasd)04:08
*** LiangFang has quit IRC04:09
tpatilThe patch is already merged and Corey has back ported this patch to the stable/rocky branch04:09
samPYes, Sorry I miss this.04:10
*** Liang__ has joined #openstack-meeting04:11
tpatilThis fix is included in the Stein release.04:11
tpatilI think we should also merge back ported patch to the stable/rocky branch04:12
tpatil#link : https://review.openstack.org/#/c/641039/04:12
samPtpatil: Do we need to backport https://review.openstack.org/#/c/637711 also?04:12
*** _pewp_ has quit IRC04:12
tpatiland then mark this LP bug as Fix committed04:12
*** _pewp_ has joined #openstack-meeting04:13
tpatilsamP: in stable/Rocky ?04:13
samPtpatil: yep. not sure whether we need it or not04:13
tpatilI don't think so becoz it's only about running jobs on OpenStack CI04:13
*** enriquetaso has quit IRC04:14
tpatilwhere as patch 641039 is fixing issue for running masakari wigs service in py304:14
tpatilso it should be back ported to the stable/rocky branch IMO04:14
*** iyamahat has joined #openstack-meeting04:15
tpatils/wigs/wsgi04:15
samPtpatil: got it.04:15
samPWF+1 to 64103904:15
tpatilsamP: Thanks04:16
samPI will change the LP bug status once it get merged04:17
samPAny other issues?04:17
samP#topic AOB04:18
*** openstack changes topic to "AOB (Meeting topic: masakari)"04:18
samPSince we are in the release week, not much topics to discuss.04:19
samPIf not other topics to discuss, I would like to conclude the today's meeting.04:19
tpatilsamP: No topics from my end for now04:20
samPtpatil: thanks04:21
samPThank you all for attending today's meeting.04:21
samPPlease use #openstack-masakari @freenode IRC or openstack-discuss@lists.openstack.org for further discussions04:22
samPThsnk you04:22
samP#endmeeting04:22
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"04:22
openstackMeeting ended Tue Apr  9 04:22:31 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)04:22
openstackMinutes:        http://eavesdrop.openstack.org/meetings/masakari/2019/masakari.2019-04-09-04.00.html04:22
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/masakari/2019/masakari.2019-04-09-04.00.txt04:22
openstackLog:            http://eavesdrop.openstack.org/meetings/masakari/2019/masakari.2019-04-09-04.00.log.html04:22
*** markvoelker has quit IRC04:31
*** tpatil has left #openstack-meeting04:47
*** tashiromt has quit IRC04:50
*** sidx64 has joined #openstack-meeting05:09
*** Liang__ is now known as LiangFang05:11
*** igordc has quit IRC05:11
*** iyamahat has quit IRC05:23
*** e0ne has joined #openstack-meeting05:25
*** e0ne has quit IRC05:29
*** _alastor_ has joined #openstack-meeting05:33
*** LiangFang has quit IRC05:38
*** Liang__ has joined #openstack-meeting05:43
*** Liang__ is now known as LiangFang05:44
*** _alastor_ has quit IRC05:46
*** LiangFang has quit IRC05:48
*** Liang__ has joined #openstack-meeting05:49
*** imsurit has joined #openstack-meeting05:49
*** Liang__ is now known as LiangFang05:49
*** sridharg has joined #openstack-meeting05:50
*** ricolin_ has quit IRC05:58
*** jbadiapa has joined #openstack-meeting06:01
*** radeks has joined #openstack-meeting06:04
*** kopecmartin|off is now known as kopecmartin06:05
*** rubasov has quit IRC06:18
*** rubasov has joined #openstack-meeting06:21
*** ricolin has joined #openstack-meeting06:22
*** rubasov has quit IRC06:26
*** boxiang has quit IRC06:27
*** radeks has quit IRC06:28
*** radeks has joined #openstack-meeting06:29
*** pcaruana has joined #openstack-meeting06:30
*** markvoelker has joined #openstack-meeting06:32
*** slaweq has joined #openstack-meeting06:47
*** radeks has quit IRC06:55
*** JangwonLee_ has quit IRC07:00
*** markvoelker has quit IRC07:06
*** rubasov has joined #openstack-meeting07:08
*** apetrich has joined #openstack-meeting07:10
*** sidx64 has quit IRC07:13
*** tris has quit IRC07:15
*** sidx64 has joined #openstack-meeting07:15
*** SpamapS has quit IRC07:15
*** mattia_ has quit IRC07:16
*** rsimai has quit IRC07:16
*** rsimai has joined #openstack-meeting07:17
*** slaweq has quit IRC07:17
*** SpamapS has joined #openstack-meeting07:17
*** mattia has joined #openstack-meeting07:17
*** slaweq has joined #openstack-meeting07:17
*** tris has joined #openstack-meeting07:19
*** tssurya has joined #openstack-meeting07:28
*** joxyuki has joined #openstack-meeting07:30
*** boxiang has joined #openstack-meeting07:33
*** JangwonLee has joined #openstack-meeting07:34
*** zhubx has joined #openstack-meeting07:36
*** zhubx has quit IRC07:36
*** boxiang has quit IRC07:37
*** rubasov has left #openstack-meeting07:37
*** boxiang has joined #openstack-meeting07:38
*** N-singh has joined #openstack-meeting07:41
*** sidx64 has quit IRC07:43
*** joxyuki has quit IRC07:44
*** tpatil has joined #openstack-meeting07:45
*** N-singh has quit IRC07:45
*** nsingh has joined #openstack-meeting07:47
*** ralonsoh has joined #openstack-meeting07:48
*** JangwonLee has quit IRC07:48
*** JangwonLee has joined #openstack-meeting07:49
*** hokeeeeun has joined #openstack-meeting07:52
*** hokeen has joined #openstack-meeting07:56
*** lee1 has joined #openstack-meeting07:58
*** ralonsoh has quit IRC07:58
*** lyarwood has quit IRC07:58
*** frickler has quit IRC07:58
*** ralonsoh has joined #openstack-meeting07:58
*** dkushwaha has joined #openstack-meeting07:58
*** nsingh has quit IRC07:59
*** frickler has joined #openstack-meeting07:59
*** hokeeeeun has quit IRC08:00
*** lee1 is now known as lyarwood08:00
dkushwaha#startmeeting tacker08:01
openstackMeeting started Tue Apr  9 08:01:14 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
*** rcernin has quit IRC08: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
*** nsingh has joined #openstack-meeting08:01
dkushwahawho is here for Tacker weekly meeting?08:01
nsinghHi08:01
dkushwahahello nsingh08:02
JangwonLeehi08:02
*** hokeen has quit IRC08:02
*** hokeen has joined #openstack-meeting08:03
*** markvoelker has joined #openstack-meeting08:03
hokeenhi08:03
dkushwahahi JangwonLee hokeen08:03
hyunsikyangHi08:03
dkushwahahello hyunsikyang08:04
*** hjwon has joined #openstack-meeting08:05
dkushwahaok lets start..08:05
*** joxyuki has joined #openstack-meeting08:05
joxyukihi08:05
*** ttsiouts has joined #openstack-meeting08:05
*** shubham_potale has joined #openstack-meeting08:05
dkushwaha#topic announcement08:05
hjwonHi :)08:05
*** openstack changes topic to "announcement (Meeting topic: tacker)"08:05
*** jaewook_oh has joined #openstack-meeting08:06
jaewook_ohhello tacker team08:06
dkushwahaTacker 1.0.0 stable/stein released last week08:06
dkushwaha#link Tacker Stein released: https://docs.openstack.org/releasenotes/tacker/stein.html08:06
dkushwahaThanks to all Team members08:07
dkushwahafor their great support08:07
joxyukithanks dkushwaha and all08:07
*** johnthetubaguy has quit IRC08:08
dkushwaha#announcement Denever-summit08:08
dkushwahaUnfortunately, my U.S. visa could not be approved, so I will not be able to travel for summit08:09
joxyukireally???08:09
hyunsikyangWHY?08:09
hyunsikyangI am so sorry to hear that..08:09
hyunsikyangI think purpose of your visit is so clear... why....I can't understand it.08:10
dkushwahaU.S. embassy rejected my application without any reason. :(08:10
joxyukiit is strange story...08:11
dkushwahajoxyuki, my bad luck08:11
hyunsikyangHummm...08:12
dkushwahaCan somebody present Tacker project-update and project-Onboarding session?? Let me know if somebody intrested08:12
*** e0ne has joined #openstack-meeting08:13
dkushwahaotherwise, I will sent schedule cancellation request to openstack.08:13
joxyukiand PTG?08:13
hyunsikyangI can't attend PTG session.08:14
dkushwahajoxyuki, yea, PTG too.08:14
hyunsikyangI will consider it about summit session.08:15
*** priteau has joined #openstack-meeting08:15
*** nsingh has quit IRC08:15
joxyukido you know this form? https://openstackfoundation.formstack.com/forms/visa_form_denver_summit08:15
*** bhagyashris has joined #openstack-meeting08:16
*** nsingh has joined #openstack-meeting08:16
hyunsikyangWhen is the deadline for cancellation?08:17
dkushwahajoxyuki, yes, I know, and I already requested for that08:17
joxyukiokey...08:17
dkushwahahyunsikyang, might be before 19th april08:17
dkushwahaRegarding PTG, there are two options:08:18
hyunsikyangok. Let's think about it:) joxyuki, will you attend this summit?08:18
*** johanssone has quit IRC08:18
joxyukihyunsikyang, yes08:18
dkushwaha1: those who are going denever, they can start PTG from their(physically), and rest members(if possible) will join them remotely.08:19
*** JangwonLee_ has joined #openstack-meeting08:19
dkushwaha 2: We all can schedule virtual PTG08:19
*** nsingh has quit IRC08:21
hyunsikyangEven we are going to denver, but, we can't attend PTG. So, please count the head without me.08:21
hyunsikyangWho will attend this meeting in this room?08:21
joxyukiI will08:22
*** JangwonLee has quit IRC08:22
hyunsikyangUntil now, only our team(2) and joxyuki are going to this summit.08:23
hyunsikyangI think that vPTG is better.08:23
dkushwahaI suggest, if some members can be available for PTG in denever, then it will be good if we rest member join them remotely.08:24
*** johanssone has joined #openstack-meeting08:24
dkushwahajoxyuki, what you say ?08:24
joxyukiI prefer option 1 as you said.08:25
dkushwahanice, that will be good for project also08:25
joxyukibut if no one other than me can attend it at Devner. We need vPTG.08:25
joxyukiafter PTG at Denver08:26
dkushwahaagree08:26
*** zbr has quit IRC08:28
dkushwahahyunsikyang, could you please start drafting some slides for our sessions, I will help on that08:28
*** sidx64 has joined #openstack-meeting08:28
hyunsikyangOK. I will start it from tomorrow:)08:29
dkushwahahyunsikyang, as the session tpoc is big, but it got selected in 10 minutes sessions, so we needs to keep it in brief, and cover max topics08:30
dkushwaha:%s/tpoc/topic08:30
*** yamamoto has quit IRC08:30
hyunsikyangok. so.. what is the main topic of that session?08:31
hyunsikyangbriefly explan tacker's result ?08:31
hyunsikyangexplain*08:31
hyunsikyangI will make a guideline for that presentation first.08:32
dkushwahahyunsikyang, https://www.openstack.org/summit/denver-2019/summit-schedule/events/23272/a-new-era-for-nfv-with-tacker08:33
hyunsikyangI have read it:)08:33
dkushwahahyunsikyang, we needs to briefly explain Tacker and their scopes and how it integrated with other cross project to leverage VNFs, NSD and VNFFG08:35
hyunsikyangOK:)08:35
dkushwahahyunsikyang, thank. We can further discuss it during ppt creation08:35
dkushwahamoving next...08:36
dkushwaha#topic Bugs08:36
*** openstack changes topic to "Bugs (Meeting topic: tacker)"08:36
*** yamamoto has joined #openstack-meeting08:36
*** markvoelker has quit IRC08:36
*** ttsiouts has quit IRC08:37
*** e0ne has quit IRC08:37
dkushwahaWe comes in Train with 2 bugs in stein.08:37
dkushwaha#link https://bugs.launchpad.net/tacker/+bug/182383508:37
openstackLaunchpad bug 1823835 in tacker "Creating VNFD in Dashboard doesn't work" [High,Triaged] - Assigned to JangwonLee (jangwonlee)08:37
dkushwahahttps://bugs.launchpad.net/tacker/+bug/182386008:37
openstackLaunchpad bug 1823860 in tacker "Failed to create VNF with param values" [Undecided,New]08:37
*** ttsiouts has joined #openstack-meeting08:37
dkushwahaJangwonLee_, hyunsikyang thats for promptly working on https://bugs.launchpad.net/tacker/+bug/182383508:38
openstackLaunchpad bug 1823835 in tacker "Creating VNFD in Dashboard doesn't work" [High,Triaged] - Assigned to JangwonLee (jangwonlee)08:38
hyunsikyangI have some problem with git account. I will update it soon.08:38
dkushwahanp08:39
tpatil1823860: I think this issue is fixed in heat-translator lib08:39
hyunsikyangActually, we found one more error. please look at it.08:39
hyunsikyanghttps://bugs.launchpad.net/tacker/+bug/182385408:39
openstackLaunchpad bug 1823854 in tacker "VNFD is presented in an arbitrary on horizon" [Undecided,New] - Assigned to JangwonLee (jangwonlee)08:39
dkushwahai am working on https://bugs.launchpad.net/tacker/+bug/182386008:39
openstackLaunchpad bug 1823860 in tacker "Failed to create VNF with param values" [Undecided,New]08:39
hyunsikyangwe are working on 1823854 too.08:40
*** ttsiouts has quit IRC08:40
*** ttsiouts has joined #openstack-meeting08:40
tpatil#link : https://review.openstack.org/#/c/627509/08:40
dkushwahanothing else form my side for today meeting.08:40
tpatiltacker will need to wait until this fix is available in heat-translator library08:41
dkushwahatpatil, i see.08:41
tpatildkushwaha: If you need this fix in Stein branch then we will need to request heat team to release a new version and use that version in tacker for stein release08:43
dkushwahatpatil,right, I missed it.08:44
dkushwahatpatil,  Thanks for it, I will request Bob for the same08:44
*** vishalmanchanda has joined #openstack-meeting08:44
dkushwaha#topic OpenDiscussion08:45
*** openstack changes topic to "OpenDiscussion (Meeting topic: tacker)"08:45
*** e0ne has joined #openstack-meeting08:47
dkushwahaDo we have something to discuss, otherwise we can close it for now08:48
hyunsikyangI am done.08:48
dkushwahaTeam, as we already in Train cycle, so please put your stuffs here : https://etherpad.openstack.org/p/tacker-train-grooming08:49
dkushwahawe will used it for further discussions and future references08:49
hyunsikyangok:) thanks dkushwaha08:49
dkushwahaclosing meeting for now.08:50
dkushwahaThanks Folks for joining08:51
dkushwaha#endmeeting08:51
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"08:51
openstackMeeting ended Tue Apr  9 08:51:20 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)08:51
openstackMinutes:        http://eavesdrop.openstack.org/meetings/tacker/2019/tacker.2019-04-09-08.01.html08:51
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/tacker/2019/tacker.2019-04-09-08.01.txt08:51
openstackLog:            http://eavesdrop.openstack.org/meetings/tacker/2019/tacker.2019-04-09-08.01.log.html08:51
*** hokeen has quit IRC08:51
*** tpatil has left #openstack-meeting08:52
*** joxyuki has quit IRC08:55
*** Luzi has joined #openstack-meeting08:56
*** bhagyashris has quit IRC08:57
*** jaewook_oh has quit IRC08:57
*** hjwon has quit IRC09:03
*** iyamahat has joined #openstack-meeting09:08
*** yamamoto has quit IRC09:16
*** e0ne has quit IRC09:25
*** sidx64 has quit IRC09:34
*** electrofelix has joined #openstack-meeting09:41
*** sidx64 has joined #openstack-meeting09:44
*** e0ne has joined #openstack-meeting09:44
*** yamamoto has joined #openstack-meeting09:44
*** Lucas_Gray has joined #openstack-meeting09:45
*** yamamoto has quit IRC09:47
*** LiangFang has quit IRC09:48
*** sidx64 has quit IRC09:51
*** Lucas_Gray has quit IRC09:53
*** sidx64 has joined #openstack-meeting09:54
*** Lucas_Gray has joined #openstack-meeting09:54
*** psachin has joined #openstack-meeting09:59
*** yamamoto has joined #openstack-meeting10:02
*** yamamoto has quit IRC10:08
*** gary_perkins_ has quit IRC10:11
*** gary_perkins has joined #openstack-meeting10:11
*** yamamoto has joined #openstack-meeting10:15
*** yamamoto has quit IRC10:18
*** yamamoto has joined #openstack-meeting10:21
*** yamamoto has quit IRC10:21
*** yamamoto has joined #openstack-meeting10:22
*** yamamoto has quit IRC10:24
*** yamamoto has joined #openstack-meeting10:24
*** ttsiouts has quit IRC10:25
*** ttsiouts has joined #openstack-meeting10:26
*** dkushwaha has quit IRC10:28
*** ttsiouts has quit IRC10:30
*** markvoelker has joined #openstack-meeting10:33
*** bbowen has quit IRC10:36
*** e0ne has quit IRC10:37
*** JangwonLee_ has quit IRC10:38
*** sidx64 has quit IRC10:41
*** e0ne has joined #openstack-meeting10:44
*** tetsuro has quit IRC10:46
*** ttsiouts has joined #openstack-meeting10:46
*** yamamoto has quit IRC11:01
*** yamamoto has joined #openstack-meeting11:03
*** sidx64 has joined #openstack-meeting11:04
*** markvoelker has quit IRC11:07
*** yamamoto has quit IRC11:07
*** zbr has joined #openstack-meeting11:08
*** yamamoto has joined #openstack-meeting11:09
*** yamamoto has quit IRC11:09
*** sidx64 has quit IRC11:15
*** sidx64 has joined #openstack-meeting11:22
*** yamamoto has joined #openstack-meeting11:26
*** sidx64 has quit IRC11:26
*** sidx64 has joined #openstack-meeting11:27
*** e0ne has quit IRC11:30
*** yamamoto has quit IRC11:41
*** rubasov has joined #openstack-meeting11:45
*** imsurit has quit IRC11:46
*** bbowen has joined #openstack-meeting11:50
*** sidx64 has quit IRC11:59
*** yamamoto has joined #openstack-meeting11:59
*** yamamoto has quit IRC11:59
*** ttsiouts has quit IRC12:00
*** ttsiouts has joined #openstack-meeting12:01
*** lseki has joined #openstack-meeting12:14
*** JangwonLee has joined #openstack-meeting12:16
*** jamesmcarthur has joined #openstack-meeting12:17
*** sidx64 has joined #openstack-meeting12:17
*** apetrich has quit IRC12:32
*** Liang__ has joined #openstack-meeting12:34
*** Liang__ is now known as LiangFang12:34
*** jamesmcarthur has quit IRC12:34
*** tetsuro has joined #openstack-meeting12:37
*** apetrich has joined #openstack-meeting12:39
*** tetsuro has quit IRC12:40
*** priteau has quit IRC12:42
*** yamamoto has joined #openstack-meeting12:43
*** apetrich has quit IRC12:45
*** Luzi_ has joined #openstack-meeting12:46
*** lbragstad has joined #openstack-meeting12:49
*** Luzi has quit IRC12:49
*** jamesmcarthur has joined #openstack-meeting12:50
*** e0ne has joined #openstack-meeting12:54
*** apetrich has joined #openstack-meeting12:54
*** jroll has quit IRC12:55
*** JangwonLee has quit IRC12:55
*** jroll has joined #openstack-meeting12:59
*** eharney has joined #openstack-meeting13:00
*** jamesmcarthur has quit IRC13:04
*** sidx64 has quit IRC13:05
*** mjturek has joined #openstack-meeting13:07
*** yamamoto has quit IRC13:10
*** yamamoto has joined #openstack-meeting13:11
*** yamamoto has quit IRC13:11
*** raildo has joined #openstack-meeting13:12
*** Luzi_ has quit IRC13:17
*** awaugama has joined #openstack-meeting13:24
*** enriquetaso has joined #openstack-meeting13:26
*** priteau has joined #openstack-meeting13:28
*** ygbo has joined #openstack-meeting13:29
*** mjturek has quit IRC13:35
*** mjturek has joined #openstack-meeting13:36
*** lpetrut has joined #openstack-meeting13:42
*** tidwellr has joined #openstack-meeting13:42
*** mriedem has joined #openstack-meeting13:43
*** liuyulong|away is now known as liuyulong13:44
*** jrbalderrama has joined #openstack-meeting13:48
*** vishalmanchanda has quit IRC13:50
*** yamamoto has joined #openstack-meeting13:51
*** e0ne has quit IRC13:53
*** Lucas_Gray has quit IRC13:57
*** njohnston has joined #openstack-meeting13:59
*** lajoskatona has joined #openstack-meeting14:00
*** ygbo has quit IRC14:00
*** mlavalle has joined #openstack-meeting14:00
mlavalle#startmeeting networking14:00
openstackMeeting started Tue Apr  9 14:00:29 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
njohnstono/14:00
lajoskatonao/14:00
bcafarel\o14:00
rubasovo/14:00
tidwellr\o/14:00
mlavalleWelcome everybody!14:01
*** Lucas_Gray has joined #openstack-meeting14:01
haleybhi14:01
mlavalleLet's get going14:02
*** shintaro has joined #openstack-meeting14:02
mlavalle#topic Announcements14:02
*** openstack changes topic to "Announcements (Meeting topic: networking)"14:02
*** yamamoto has quit IRC14:02
*** elod has joined #openstack-meeting14:02
mlavallePer https://releases.openstack.org/stein/schedule.html, this is the week the community releases Stein14:03
slaweqhi14:03
mlavallewe had a last minute small hicup last week with some of the bulk port creation code14:03
mlavallebut we merged the fix on time, so everything is good14:04
*** davidsha_ has joined #openstack-meeting14:04
haleybmlavalle: so do we need to push a tag for stable/stein ?14:04
njohnston\o/ thanks ralonsoh14:04
*** ygbo has joined #openstack-meeting14:04
*** priteau has quit IRC14:04
*** lpetrut has quit IRC14:04
mlavallehaleyb: I'll ask and ping you14:05
bcafarelhmm we merged a few commits since rc114:05
haleybmlavalle: ack.  i just pushed reviews to tag rocky/queens/pike - https://review.openstack.org/#/c/651234/ https://review.openstack.org/#/c/651235/ https://review.openstack.org/#/c/651236/ - think pike will need an update14:05
*** ygbo has quit IRC14:06
*** ttsiouts has quit IRC14:06
mlavalleWith that, we should focus on the PTG14:06
*** ygbo has joined #openstack-meeting14:06
amotokihi14:06
*** ttsiouts has joined #openstack-meeting14:07
davidsha_o/14:07
mlavalleI remind the team that we are collecting topics in the etherpad: https://etherpad.openstack.org/p/openstack-networking-train-ptg14:07
njohnstonyes just 3 weeks and a day until the PTG starts if I'm not mistaken14:07
liuyulongyes, recently stable branches have backported many patches.14:07
amotoki(after looking at the log) perhaps we need to cut a stable/stein update release soon after the stein release.14:08
mlavalleamotoki: yeah that's what I think we are going to do14:08
*** ttsiouts has quit IRC14:09
*** ttsiouts has joined #openstack-meeting14:09
mlavalleThis week I am going to start organizing the topics in the PTG etherpad in sessions14:09
amotokisounds good14:09
mlavalleso we have an agenda for the PTG14:09
mlavalleand I see we have 16 people confirmed to attend our social event on May 3rd. So it is going to be a fun dinner \o/14:10
amotokiregarding the stable branches, I also remind http://lists.openstack.org/pipermail/openstack-discuss/2019-April/004594.html (pike extended maintenance).14:10
mlavalleamotoki: I added a topic to the on demand agenda to talk about that14:11
amotokiwe still do not mark ocata as EM. Pike is a newcommer14:11
amotokilet's discuss it later or in the next meeting :)14:11
mlavalleany other announcements?14:12
mlavalle#topic Blueprints14:12
*** openstack changes topic to "Blueprints (Meeting topic: networking)"14:12
mlavalleThe only thing that I want to mention in regards to blueprints is the openflow based DVR effort14:13
mlavallehttps://blueprints.launchpad.net/neutron/+spec/openflow-based-dvr14:14
mlavalleThis is the only blueprint that we targeted for Stein that we didn't complete14:14
mlavalleThe plan that we have discused in the L3 subteam meetings is to merge this as early as possible in TRain14:14
mlavalleso we have time to debug it14:15
mlavalleHere's the series of patches: https://review.openstack.org/#/q/topic:openflow-based-dvr+(status:open+OR+status:merged)14:15
mlavallePlease help reviewing14:16
mlavalleI know tidwellr is already working on it. Thanks14:16
slaweqI have one question about it14:16
slaweqhttps://bugs.launchpad.net/neutron/+bug/1705536 is marked as rfe-postponed14:16
openstackLaunchpad bug 1705536 in neutron "[RFE] L3-agent agent-mode dvr bridge." [Wishlist,Triaged]14:16
slaweqshould it be changed to approved?14:17
mlavalleslaweq: done14:17
slaweqthx mlavalle :)14:18
slaweqI wasn't sure if that was already discussed or not yet. Now it's clear :)14:18
davidsha_I think that might need to be reworded from Agent_Mode to Agent_Backend14:18
davidsha_I'll do that now14:19
mlavalleThe other RFE that is approved and will start showing up in our reviews screen is https://bugs.launchpad.net/neutron/+bug/176473814:19
openstackLaunchpad bug 1764738 in neutron "routed provider networks limit to one host" [Wishlist,In progress] - Assigned to David Bingham (wwriverrat)14:19
amotokiin my understanding rfe-postponed RFEs are approved but we fail to find persons who work on.... if we have volunteers we can move them to rfe-approved.14:19
mlavalleamotoki: yeap, we have people actively working on it14:19
mlavallegoing back to 1764738, here's the wip patch: https://review.openstack.org/#/c/62311514:20
mlavalleit would be good if the team takes a look at it so we can have a fruitful discussion about it in Denver14:20
slaweqamotoki: ok, thx. I didn't know that :)14:21
*** raildo has quit IRC14:22
mlavalleThis week also I will attend the StarlingX networking meeting. I know they are planning to propose blueprints for Train. So I'll make sure they add them to the PTG etherpad14:22
*** raildo has joined #openstack-meeting14:22
mlavalleany other blueprints we should discuss today?14:23
amotokimlavalle: is there any handy link? or can I find it in the openstack meeting page?14:24
mlavalleamotoki: link for what?14:24
amotokimlavalle: starlingX meeting14:24
mlavallehang on14:24
mlavalleamotoki: https://wiki.openstack.org/wiki/Starlingx/Meetings#0615am_PDT_.2F_1415_UTC_-_Networking_Team_Call_.28Bi-weekly.2914:25
amotokithanks14:25
mlavalleit's a high bandwidth meeting in zoom14:25
amotokiI still need to watch zoom log..14:25
mlavallecool14:26
mlavalle#topic Community goals14:26
*** openstack changes topic to "Community goals (Meeting topic: networking)"14:26
njohnstonFor python3 looking at the stadium jobs I plan on getting back to that once the stadium tempest plugin transition is done14:28
*** bobh has joined #openstack-meeting14:28
mlavallethanks njohnston14:28
njohnstonI haven't followed the ML discussions; are the community goals for T set?14:29
mlavallethere was also an update in the ML on community goals for Train14:29
mlavallehttp://lists.openstack.org/pipermail/openstack-discuss/2019-April/004517.html14:29
mlavallenjohnston: you read my mind ;-)14:29
*** jgriffit2 has quit IRC14:29
*** boden has joined #openstack-meeting14:30
amotokiregarding the community goals, we've done the WSGI goal, but we haven't switched to neutron-api with WSGI by default. we can make it as default in Train.14:30
-amotoki- is looking for the mailing list link14:30
mlavalleso it seems the community is talking about docs in PDF and IPv6 support for Train14:30
slaweqamotoki: we should IMO first promote wsgi based ci jobs to be working in check and gate queues14:30
njohnstonIsn't WSGI by default a deployer decision that would be done in TripleO or something like that?14:31
amotokislaweq: totally agree14:31
njohnstonslaweq++14:31
slaweqfor now it is only in experimental queue14:31
*** e0ne has joined #openstack-meeting14:31
amotokineutron is the only project which hasn't switched it to WSGI in devstack14:31
mlavalleyeah, I think we should switch it14:32
amotokiit would be a good follow-up :)14:32
bodensorry I just joined, but are we expecting any hits to plugin projects as part of this?14:32
mlavalleboden: just in the initial conversation14:32
mlavallenothing is imminent yet14:32
bcafarelsounds like a great goal for neutron train14:32
amotokieventlet dependencies might affect plugin projects. we can validate the impact in train14:33
bodenack IMO it would be nice to give plugin teams a heads up so we can make sure the transisiton is smooth14:33
mlavalleboden: good feedback. Thanks!14:34
mlavallewe can even talk about it in Denver, while boden and other representatives of out of tree plugins are present14:34
mlavalleis that fair?14:34
slaweqmlavalle++14:34
amotoki+114:34
boden+114:35
mlavalleboden: do you want to add the topic to the etherpad?14:35
bodenmlavalle sure14:35
mlavallecool14:35
mlavallemoving on14:35
mlavalle#topic Bugs14:35
*** openstack changes topic to "Bugs (Meeting topic: networking)"14:35
mlavalleour deputy last week was bcafarel14:36
mlavallehere's the report: http://lists.openstack.org/pipermail/openstack-discuss/2019-April/004696.html14:36
bcafarelsmall update the in progress review for midonet failure was merged too (https://review.openstack.org/#/c/650599/)14:37
mlavalleso all the critial and high priority bugs have merged fixes, right?14:37
bcafarelmlavalle: indeed, all good for these sections!14:38
mlavalleso the two medium priority bugs lack owners14:39
mlavallehttps://bugs.launchpad.net/neutron/+bug/182259114:41
openstackLaunchpad bug 1822591 in neutron "neutron-keepalived-state-change doesnt reap zombies if rootwrap-daemon is used" [Medium,Confirmed]14:41
mlavallethis one seems to be l3 ha dvr related14:41
mlavalleadding the tag14:41
bcafarelmlavalle: these zombies also happen on other agents (I tried with dhcp agent)14:42
*** igordc has joined #openstack-meeting14:42
mlavallebcafarel: ack14:43
bcafarelapparently this behaviour appeared recently14:43
mlavallehttps://bugs.launchpad.net/neutron/+bug/182329714:43
openstackLaunchpad bug 1823297 in neutron "create of segment range for vlan network type fails with error 500" [Low,Fix released] - Assigned to Slawek Kaplonski (slaweq)14:43
mlavalleI approved the fix for this one yesterday14:43
mlavallethanks slaweq14:43
slaweqthis one was easy :)14:43
mlavallebcafarel: anything else you wnat to highlight?14:43
liuyulonghttps://review.openstack.org/#/q/topic:bug/1811352+(status:open+OR+status:merged), I started the port forwarding OSC patches.14:44
bcafareljust a general reminder (I had forgotten), os-ken is in the list of projects using storyboard :)14:44
liuyulonghttps://bugs.launchpad.net/neutron/+bug/181135214:44
openstackLaunchpad bug 1811352 in neutron "[RFE] Include neutron CLI floatingip port-forwarding support" [Wishlist,In progress] - Assigned to LIU Yulong (dragon889)14:44
mlavalleliuyulong: Thanks!14:44
liuyulongWe've been missing this for too long.14:45
bcafarelso remember to redirect reporters there if you see open launchad bugs (thanks slaweq for reminding me)14:45
mlavallebcafarel: thanks for the reminder14:45
haleybliuyulong: i am reviewing the osc change, will have comments soon14:45
mlavallethe deputy for this week is slaweq14:45
liuyulonghaleyb, cool14:45
mlavalleand next week it will be hongbin14:45
*** _erlon_ has joined #openstack-meeting14:46
slaweqok14:46
mlavalleI want to point out that this week we lost a member of the bugs deputy rotation14:46
mlavalleso I adjusted the schedule last night14:46
slaweqI already started it this week :)14:46
*** jgriffith has joined #openstack-meeting14:47
*** shintaro has quit IRC14:47
bcafarelah that's why I saw your name on recent bugs this week :)14:47
*** jamesmcarthur has joined #openstack-meeting14:47
slaweqbcafarel: yep :)14:47
mlavalleso for most of you, your duty week is going to be one week earlier than originally schedule14:47
mlavalleso pleae take a look and reconfirm your duty week14:47
mlavalle#topic neutron-lib14:48
*** openstack changes topic to "neutron-lib (Meeting topic: networking)"14:48
mlavalleboden: you are up14:48
bodenhi14:48
*** lpetrut has joined #openstack-meeting14:48
bodenso for the most part I think we are waiting for Stein to officially go out the door before doing too much14:49
bodenonce it does IMO it'd be nice to cut a new neutron-lib as there are some patches to consume14:49
bodenalso I will refresh a number of consumption patches I've been holding off on14:49
mlavalleboden: let's plan to do that next week14:49
bodenok14:50
bodenand that's about it14:50
mlavallecool14:50
mlavallethanks for the update14:50
mlavalle#topic On demand agenda14:50
*** openstack changes topic to "On demand agenda (Meeting topic: networking)"14:50
mlavalleBack in January, we sent this message to the ML: http://lists.openstack.org/pipermail/openstack-discuss/2019-January/001383.html14:51
*** ijw has joined #openstack-meeting14:51
mlavallesmcginnis in the release team wanted to clarify that: "A stable branch enters extended maintenance after 18 months of initial release. It is not up to the project team to decide that"14:51
slaweqso we are "bit late" with Ocata :)14:52
bcafarelwe did the release mostly in time :)14:52
mlavalleand actually that conversation with me reminded him of sending http://lists.openstack.org/pipermail/openstack-discuss/2019-April/004594.html14:52
amotokiI am not sure what "extended maintenance phase" means in general.14:53
bcafarelhttps://review.openstack.org/#/c/650467/ will tag all last ocata releases as ocata-em (there will be another one soon for pike I suppose)14:53
amotokiEM is a decision of each project team per document.14:53
mlavallebcafarel: yes, he agrees on that. we did a good job. he was just concerned with clarifyin the semantics14:53
mlavalleamotoki: staying in EM is a decision of the project14:54
mlavallebut we get to EM at the 18 months mark regardless14:54
amotokimlavalle: ah, I see. EM or EOL is up to the project.14:54
bcafarelyep14:54
elodhi, was eavesdropping so far :) for some detail about EM: https://governance.openstack.org/tc/resolutions/20180301-stable-branch-eol.html#end-of-life14:54
elodthis is the resolution about Extended Maintenance from last year14:55
amotokiwe seem to miss tagging on ocata in time. we need to tag last pike stable releases in time.14:55
mlavallewe can maintain a stable branch in EM as long as we are willing to actively work on it14:56
*** lbragstad has quit IRC14:56
elodalso, smcginnis created a general patch for ocata: https://review.openstack.org/#/c/650467/14:56
mlavallebut if nobody is working on it, then it is time to EOL14:56
mlavalledoes this make sense?14:56
*** lbragstad has joined #openstack-meeting14:56
njohnstonmlavalle: makes sense to me14:57
elodyes, that's it14:57
bcafarelthat was my understanding (and yes makes sense)14:57
* mlavalle had to be slapped twice by smcginnis befory getting this ;-)14:58
amotokione question from me is whether it is aware of plugin maintainers?14:58
smcginnisHah. There was a lot of confusion around it. ;)14:58
amotokiaround ocata EM, what we struggled is how we coordinate all stadium projects.14:58
mlavallein our case we should be careful in letting our eco-system know what is happening with stable branch14:59
mlavallea consequence of our plugin architecture14:59
mlavalleok guys, we ran out of time15:00
mlavallethanks for attending15:00
amotokiplugin is not the only eco-system we ahve thohgh.....15:00
mlavalle#endmeeting15:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"15:00
openstackMeeting ended Tue Apr  9 15:00:23 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:00
njohnston\o15:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking/2019/networking.2019-04-09-14.00.html15:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking/2019/networking.2019-04-09-14.00.txt15:00
openstackLog:            http://eavesdrop.openstack.org/meetings/networking/2019/networking.2019-04-09-14.00.log.html15:00
amotokio/15:00
davidsha_thanks!15:00
lajoskatona\o15:00
bcafarelo/15:00
slaweqo/15:00
ralonsoh#startmeeting neutron_qos15:00
openstackMeeting started Tue Apr  9 15:00:55 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
openstackThe meeting name has been set to 'neutron_qos'15:00
*** boden has left #openstack-meeting15:01
ralonsohYou can stay here if you want15:01
mlavalleo/15:01
slaweqo/15:01
rubasovo/15:01
ralonsohhello everybody15:01
davidsha_o/15:01
*** ttsiouts has quit IRC15:01
davidsha_hey!15:01
lajoskatonao/15:01
* mlavalle walking to the kitchen to quickly grab a glass of water15:01
*** ttsiouts has joined #openstack-meeting15:02
ralonsohI think today meeting is going to be shorter15:02
ralonsohok, let's go15: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,Fix released] - Assigned to Bence Romsics (bence-romsics)15:02
ralonsohWe still have some doc patches15:03
ralonsohis that correct?15:03
rubasovnot exactly15:03
rubasovdocs are merged15:03
rubasovsome tests are still open15:03
ralonsohperfect15:03
lajoskatonaralonsoh: we have fullstack test, and tempest.15:03
ralonsohdo you have the link of those tests?15:03
lajoskatonaActually tempest now seems to be moving with reviews: https://review.openstack.org/62925315:04
ralonsohI think you can remove the depends15:04
lajoskatonathe fullstack stuff is wip, for that I have to go back, and push them15:05
*** ijw has quit IRC15:05
ralonsohI'll add this one to the etherpad15:05
lajoskatonabut general comments about the way I chose would be good15:05
lajoskatonathe fullstack patch: https://review.openstack.org/64252715:05
lajoskatonaralonsoh: thanks15:05
*** ijw has joined #openstack-meeting15:05
*** ttsiouts has quit IRC15:05
ralonsohI'll add both to my review list15:06
*** ttsiouts has joined #openstack-meeting15:06
ralonsohFirst the tempest one15:06
ralonsohsomething else in this RFE?15:06
lajoskatonaralonsoh:  that's all15:07
ralonsohthanks!15:07
ralonsoh#link https://bugs.launchpad.net/neutron/+bug/156096315:07
openstackLaunchpad bug 1560963 in neutron "[RFE] Minimum bandwidth support (egress)" [Wishlist,In progress] - Assigned to Rodolfo Alonso (rodolfo-alonso-hernandez)15:07
mlavallelet's just keep in mind that there will be discussions in Denver15:07
ralonsohmlavalle, about what?15:07
mlavalleabout follow up work for the previous RFE15:08
ralonsohmlavalle, for sure15:08
rubasovmlavalle: we plan to prepare an etherpad collecting that15:08
mlavallehttps://etherpad.openstack.org/p/ptg-train-xproj-nova-neutron15:08
ralonsohok15:08
ralonsohI was looking for this15:08
mlavallethis just wanted to make sure everybody is aware of this15:09
mlavalleplease carry on15:09
*** ijw has quit IRC15:09
ralonsohmlavalle, thanks!15:09
ralonsohok, about https://bugs.launchpad.net/neutron/+bug/156096315:09
openstackLaunchpad bug 1560963 in neutron "[RFE] Minimum bandwidth support (egress)" [Wishlist,In progress] - Assigned to Rodolfo Alonso (rodolfo-alonso-hernandez)15:09
*** ijw has joined #openstack-meeting15:09
ralonsohI'm still implementing the tunnelled traffic patch15:09
ralonsohbut because is a low priority one, I'm a bit stuck15:10
ralonsohI need to make some progress this week15:10
ralonsohbtw, for now it's going to be limited to vxlan because the way of filtering the traffic in the TC filter15:10
mlavallethanks for keeping it alive :-)15:10
ralonsohI'll explain it in the release note15:11
ralonsohthat's all15:11
ralonsohnext one is15:11
ralonsoh#link https://bugs.launchpad.net/neutron/+bug/181847915:11
openstackLaunchpad bug 1818479 in neutron "RFE Decouple placement reporting service plugin from ML2" [Wishlist,New] - Assigned to Bence Romsics (bence-romsics)15:11
ralonsohdid you talk about this one in the drivers meeting?15:12
rubasovI had a week long training so I still did not make progress with this sorry15:12
ralonsohnp15:12
rubasovbut I promise to bring this to a drivers meeting still before the ptg15:12
ralonsohbut did you add it in the drivers meeting etherpad?15:12
ralonsohperfect15:12
rubasovnot yet, but will do asap15:12
ralonsohthanks!!15:12
mlavallewe had an exchange I beleive in the RFE15:13
ralonsohI'll be in this meeting too15:13
mlavalleand he indicated that it is not ready yet15:13
mlavalleto be discussed in the drivers meeting15:13
mlavallebut it is in my radar screen15:13
mlavalleso as soon as rubasov15:14
mlavalleindictes in the RFE, I'll schedule it15:14
rubasovmlavalle: thanks in advance15:14
ralonsohI have no more RFEs in the list15:15
ralonsohAm I missing something?15:15
ralonsohbtw, just to know15:16
ralonsohhow https://bugs.launchpad.net/nova/+bug/1820588 is going to be addressed?15:16
openstackLaunchpad bug 1820588 in OpenStack Compute (nova) "Bandwidth resource is leaked if a bound port is deleted in neutron" [Low,Confirmed]15:16
ralonsohI said that in advance to the xproj meeting15:17
gibiralonsoh: we documented the bug but at the moment I have no solution15:17
ralonsohgibi, ok15:17
mlavallethis is one of the conversation topics for Denver15:17
davidsha_What happens if min_bw is applied through the network rather than the port?15:17
mlavalleit is in the nova neutron session15:17
ralonsohI know, just if there is something more15:17
mlavalleright?15:17
ralonsohyes15:18
lajoskatonadavidsha_: that is not supported15:18
gibidavidsha_: As far as I know if the port is create in the network it will inherit the min_bw settings15:18
davidsha_kk15:18
lajoskatonadavidsha_: I mean to boot vm with network that has bandwidth15:18
gibidavidsha_: but the port needs to be pre-created in neutron before the boot15:18
davidsha_lajoskatona, gibi: Ah, understood!15:19
davidsha_conflicting messages there :P15:19
lajoskatonadavidsha_: your welcome15:19
ralonsohok, we'll discuss possible solutions in the xproj meeting. Thanks for the explanations!15:20
ralonsohlet's move to next topic15:20
ralonsoh#topic Bugs15:20
*** openstack changes topic to "Bugs (Meeting topic: neutron_qos)"15:20
ralonsoh#link https://bugs.launchpad.net/neutron/+bug/181912515:20
openstackLaunchpad bug 1819125 in neutron "Fullstack test test_min_bw_qos_policy_rule_lifecycle failing often" [Critical,Fix released] - Assigned to Rodolfo Alonso (rodolfo-alonso-hernandez)15:20
ralonsoh#link https://review.openstack.org/#/c/646082/15:21
ralonsohSo we can consider it closed15:21
mlavalle+115:21
ralonsohand I don't have more bugs in the backlog15:21
ralonsohdo you have any other one?15:22
mlavalleNONE FROM ME15:22
mlavallesorry for the caps15:22
ralonsohnp15:22
ralonsohok, let's move to next topic15:23
ralonsoh#topic Open Discussion15:23
*** openstack changes topic to "Open Discussion (Meeting topic: neutron_qos)"15:23
ralonsoh#link https://bugs.launchpad.net/neutron/+bug/1476527 - Adoption of Neutron Classifier API into QoS15:23
openstackLaunchpad bug 1476527 in neutron "[RFE] Add common classifier resource" [Wishlist,Triaged] - Assigned to Igor D.C. (igordcard)15:23
ralonsoh#link https://review.openstack.org/#/c/63633015:23
ralonsoh#link https://review.openstack.org/#/c/63633315:23
ralonsohsorry davidsha_ I didn't have time to review both patches15:23
davidsha_Ya, I've just been working on the RPC part of the code to propagate the messages, almost got that wrapped up15:23
*** e0ne has quit IRC15:23
davidsha_ralonsoh: np, I'm hoping before the next meeting to have the full PoC working15:24
ralonsohperfect15:24
ralonsohdavidsha_, will you present it in Denver?15:25
ralonsohI mean, do you have a slot to present this feature?15:25
davidsha_Not yet, I can create the topic, there were a few projects interested in the classifier15:25
davidsha_mlavalle: that ok with you?15:25
ralonsohthat's the point, to have some traction15:26
mlavalleyes, that's ok with me15:26
davidsha_ya, I'll add that now15:26
mlavalledavidsha_: will you be coming to Denver?15:26
ralonsohhe will15:26
davidsha_mlavalle: yup, got approval recently!15:26
mlavalleNice!15:27
*** e0ne has joined #openstack-meeting15:27
bcafareldavidsha_: great news, will be nice to see you there :)15:27
mlavalleI can see your name in the therpad indeed15:28
davidsha_bcafarel: first time in Denver, used to the late night livestreams ;)15:28
*** lpetrut has quit IRC15:29
ralonsohI don't have any other topic in the agenda15:29
davidsha_added it under "Cross networking project topics (e.g. items that could impact other plugin projects/repos)"15:29
ralonsohdavidsha_++15:29
mlavalledavidsha_: ack15:30
*** iyamahat has quit IRC15:30
ralonsohok, I think we can close the meeting here. See you in the CI meeting in 30 mins15:31
lajoskatonabye15:31
mlavalleo/15:31
*** lajoskatona has quit IRC15:31
ralonsohbye15:31
rubasovthank you15:31
rubasovbye15:31
ralonsoh#endmeeting15:31
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"15:31
openstackMeeting ended Tue Apr  9 15:31:16 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:31
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_qos/2019/neutron_qos.2019-04-09-15.00.html15:31
davidsha_thanks, talk to ye!15:31
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_qos/2019/neutron_qos.2019-04-09-15.00.txt15:31
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_qos/2019/neutron_qos.2019-04-09-15.00.log.html15:31
*** gyee has joined #openstack-meeting15:35
*** jamesmcarthur has quit IRC15:42
*** bobh has quit IRC15:44
*** apetrich has quit IRC15:50
*** ijw has quit IRC15:50
*** ijw has joined #openstack-meeting15:51
*** elod has left #openstack-meeting15:52
*** ttsiouts has quit IRC15:56
*** ttsiouts has joined #openstack-meeting15:57
*** bobh has joined #openstack-meeting15:57
slaweq#startmeeting neutron_ci16:00
openstackMeeting started Tue Apr  9 16:00:04 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
slaweqhi everyone16:00
openstackThe meeting name has been set to 'neutron_ci'16:00
ralonsohhi16:00
bcafarelhey again16:00
mlavalleo/16:01
*** ttsiouts has quit IRC16:01
*** diablo_rojo has joined #openstack-meeting16:01
slaweqok, lets start16:02
slaweqfirst of all16:02
slaweqGrafana dashboard: http://grafana.openstack.org/dashboard/db/neutron-failure-rate16:02
slaweqPlease open now :)16:02
mlavalledone16:02
haleybhi16:02
slaweq#topic Actions from previous meetings16:02
*** openstack changes topic to "Actions from previous meetings (Meeting topic: neutron_ci)"16:02
slaweqmlavalle to debug reasons of neutron-tempest-plugin-dvr-multinode-scenario failures16:02
slaweqmlavalle: any progress?16:03
mlavalleslaweq: didn't make much progress there :-(16:03
slaweqok, no problem :)16:03
slaweqI will assign it to You for next week just to have "reminder"16:03
slaweqfine for You?16:03
mlavalleyes, thanks!16:03
slaweq#action mlavalle to debug reasons of neutron-tempest-plugin-dvr-multinode-scenario failures16:03
slaweqnext one16:04
slaweqslaweq to mark test_floatingip_port_details test as unstable16:04
slaweqDone: https://review.openstack.org/#/c/647816/16:04
*** ygbo has quit IRC16:04
slaweqand the last one from previous meeting was:16:04
slaweqslaweq to report a bug related to intermittent ssh failures in various tests16:04
slaweqBug reported https://bugs.launchpad.net/neutron/+bug/182191216:04
openstackLaunchpad bug 1821912 in neutron "intermittent ssh failures in various scenario tests" [High,Confirmed]16:04
slaweqthat is basically all about actions from last week16:04
slaweqanything You want to add?16:05
mlavallenope16:05
slaweqok16:05
*** mjturek has quit IRC16:05
slaweqnext topic then16:05
*** jamesmcarthur has joined #openstack-meeting16:05
slaweq#topic Python 316:06
*** openstack changes topic to "Python 3 (Meeting topic: neutron_ci)"16:06
slaweqStadium projects etherpad: https://etherpad.openstack.org/p/neutron_stadium_python3_status16:06
slaweqI don't have anything new to add here16:06
slaweqnjohnston any updates?16:06
njohnstonMe neither; I have this after the tempest plugin migration work in my personal pile.16:06
slaweqahh right, You mentioned that earlier today :)16:07
slaweqok, so lets move to next topic then16:07
slaweq#topic tempest-plugins migration16:07
*** openstack changes topic to "tempest-plugins migration (Meeting topic: neutron_ci)"16:07
slaweqnjohnston: any updates? :)16:07
bcafarel:)16:07
slaweqor anyone else have any updates on this?16:07
njohnstonSo it was pointed otu to me that there need to be zuul jobs defined both in the source repo and in neutron-tempest-plugin16:08
mlavalleI started working on the vpnaas one16:08
mlavallehttps://review.openstack.org/#/c/649373/16:08
bcafarelworking on networking-sfc one, should probably push step 1 tomorrow (16:08
njohnstonso I am about to push a change to neutron-tempest-plugin that will run fwaas jobs when they are changed in the n-t-p repo.16:08
*** e0ne has quit IRC16:08
mlavalleI'll push the next revision today or tomorrow16:08
*** Lucas_Gray has quit IRC16:08
njohnstonI wish there was a "relevant files" so I could say "only run if one of the affected files is in this path" but I think we only have the opposite, irrelevant-files.16:09
slaweqnjohnston: yes, I think that having zuul job definition together with tests would be nice to check if tests actually works16:09
slaweqnjohnston: yes, but maybe we can put such tests for stadium project in separate folder16:10
slaweqlike neutron_tempest_plugin/fwaas/16:10
slaweqand then You can define that all other files are irrelevant for this job16:11
njohnstonyes they are definitely in a different folder.  And actually it looks like my wish is granced: "files" will do the job: https://zuul-ci.org/docs/zuul/user/config.html#attr-job.files16:11
njohnston*granted16:11
slaweqnjohnston: super :)16:11
njohnstonthat's it for me16:12
slaweqthx all for update16:12
slaweqI didn't start work on bgpvpn project yet :/16:13
slaweqbut I will try to do it soon16:13
slaweqI promise :)16:13
*** priteau has joined #openstack-meeting16:13
slaweqok, lets move on16:14
slaweq#topic Grafana16:14
*** openstack changes topic to "Grafana (Meeting topic: neutron_ci)"16:14
slaweq#link http://grafana.openstack.org/dashboard/db/neutron-failure-rate16:14
slaweq(just a reminder)16:15
mlavallenot too bad16:16
slaweqyes16:16
mlavallefullstack somewhat misbahaving16:16
mlavallebut not tooo bad16:16
bcafarelfullstack seems a bit grumpy again recently?16:16
slaweqin check queue?16:17
njohnstonI've definitely had some trouble from fullstack, functional, and iptables_hybrid.  The fullstack and functional problems were "ovsdbapp: timeout after 10 seconds" style errors.16:17
mlavalleyeah, bit grumpy is good desscription16:17
slaweqnjohnston: this issue is very long standing one, it popping up from time to time and IMO it's related to slow node on which job is running16:18
njohnstonyes that was my recollection as well16:18
slaweqotherwiseguy was looking into it couple of times and he didn't found anything there16:19
slaweqalso I think that recently we were able to merged quite many patches without rechecking each of them like 10 times :)16:20
slaweqso that is IMHO progress ;)16:20
njohnstonyes, down to only 7 rechecks - 30% improvement!16:20
njohnston;-)16:20
slaweqLOL16:20
mlavalleOOL16:20
mlavalleLOL16:20
slaweqok, so lets talk about some specific issues now16:21
slaweq(I prepared couple for today)16:21
slaweq#topic fullstack/functional16:21
*** openstack changes topic to "fullstack/functional (Meeting topic: neutron_ci)"16:21
slaweqfirst of all, we had issue with fullstack on stable branches recently: https://bugs.launchpad.net/neutron/+bug/182315516:21
openstackLaunchpad bug 1823155 in neutron "neutron-fullstack fails on stable/rocky at ovs compilation" [Critical,Confirmed] - Assigned to Bernard Cafarelli (bcafarel)16:21
slaweqthx bcafarel it's fixed16:21
slaweqbcafarel: do You think we can close this bug? or there is still something to do with it?16:22
bcafarelslaweq: I was wondering about backporting it further, as job is non-voting there, but it may be useful to see results16:23
*** jamesmcarthur has quit IRC16:23
bcafarelthough I admit I rarely check non-voting jobs results in stable branches16:23
slaweqIMO we should backport it, even if it is non-voting, would be better to not have it failing 100% times :)16:23
bcafarelslaweq: ack, I'll hit that cherry-pick button, and then we should be good with that bug16:25
slaweqok, thx bcafarel16:25
mlavalle++16:25
slaweqfrom other things related to fullstack16:25
slaweqI was today checking results of ci jobs on some recent patches16:25
slaweqand I found failure like http://logs.openstack.org/85/644385/9/gate/neutron-fullstack/f7d4eb4/testr_results.html.gz16:26
ralonsohI'll take a look at this one16:26
slaweqralonsoh: in logs there is error like http://logs.openstack.org/85/644385/9/gate/neutron-fullstack/f7d4eb4/controller/logs/dsvm-fullstack-logs/TestMinBwQoSOvs.test_min_bw_qos_policy_rule_lifecycle_egress,openflow-native_/neutron-openvswitch-agent--2019-04-09--12-35-31-673671_log.txt.gz#_2019-04-09_12_35_46_73516:27
slaweqisn't it something what was supposed to be already fixed?16:27
ralonsohthis is something new16:27
mlavallein scenario tests, yes16:27
slaweqyes, it's on "fresh" patch https://review.openstack.org/#/c/644385/16:28
mlavallebut this failure seems different issue16:28
slaweqand in gate queue, so for sure this was run on current master16:28
ralonsohwe never had this problem before, but we need to deal with having several min QoS rules at the same time16:28
ralonsohduring tests16:28
slaweqok, so ralonsoh can You report it as a bug in launchpad?16:29
* bcafarel needs to leave o/16:29
ralonsohyes16:29
slaweqthx a lot16:29
slaweqI will assign this as an action for You, ok?16:29
slaweq#action ralonsoh to report and triage new fullstack test_min_bw_qos_policy_rule_lifecycle failure16:30
mlavalleyes, if he raises the hand, he gets the action item16:30
slaweqmlavalle: :)16:31
slaweqok, lets move on16:31
slaweqregarding functional tests I found that we again have some failures with db migrations :/16:31
slaweqlike http://logs.openstack.org/73/636473/25/check/neutron-functional-python27/0ef9362/testr_results.html.gz16:31
slaweqand what is strange here, that should be IMO skipped with this decorator skip_if_timeout which I added some time ago16:33
njohnstonyes that is odd16:33
slaweqmaybe I know why16:34
slaweqit is the same error but different exception is raised16:34
*** yamahata has quit IRC16:35
slaweqin decorator there is catched InterfaceError: https://github.com/openstack/neutron/commit/c0fec676723649a0516cf3d4af0dccc0fe832095#diff-7ae004589c685d938508e48bea69c581R12316:35
slaweqand in this failure test oslo_db.exception.DBConnectionError was raised16:35
slaweqI will report this as a bug and check why there is such change in raised exceptions16:35
*** mattw4 has joined #openstack-meeting16:36
slaweq#action slaweq to report and debug yet another db migration functional tests issue16:36
slaweqand that is all related to functional/fullstack tests this week16:37
slaweqanything else You want to add?16:37
mlavallenope16:38
slaweqso, next one16:38
slaweq#topic Tempest/Scenario16:38
*** openstack changes topic to "Tempest/Scenario (Meeting topic: neutron_ci)"16:38
slaweqour main issue there is https://bugs.launchpad.net/neutron/+bug/182191216:38
openstackLaunchpad bug 1821912 in neutron "intermittent ssh failures in various scenario tests" [High,Confirmed]16:38
mlavalleyeap16:39
slaweqI think we should think about some possible actions how to debug this issue16:39
slaweqI described my "findings" in last comment there16:39
slaweqbasically from what I saw in logs which I was checking is that VM was able to reach metadata server16:40
slaweqso (probably) it was able to reach router16:40
slaweqbut FIP wasn't working16:40
slaweqso it could be some security groups issue maybe or something with configuration of NAT in router's namespace maybe16:41
slaweqany ideas?16:41
mlavalleI like the idea of DNM with tcpdump16:42
njohnstonyes I think that is pretty good... this is the exact case where skydive would be helpful16:43
*** ijw has quit IRC16:43
slaweqfrom other things, maybe (for single node jobs) we can do DNM patch to tempest that will simply dump iptables state, routing table state and other things from qrouter- namespace16:44
slaweqI know that it's not what tempest should do, but in single node job, we are sure that namespace is on same host as tests are run, we know namespace name, so that also can be maybe useful16:44
slaweqnjohnston: I know that skydive would be useful here but we don't have it yet :/16:45
*** jamesmcarthur has joined #openstack-meeting16:45
slaweqso any volunteers to do that?16:46
*** jrbalderrama has quit IRC16:47
slaweqok, I will try do send such DNM patches maybe this or next week16:47
mlavalleI will help16:48
slaweq#action slaweq prepare DNM patches for debug FIP ssh issue in tempest jobs16:48
slaweqthx mlavalle16:48
mlavalleI can try to help with the tcpdump patch16:48
slaweqgreat16:48
mlavalleit just took me some time to understand what you were talking about16:49
slaweqso I will do patch to tempest to "dump router's namespace state"16:49
mlavalleI though skydive16:49
slaweqahh16:49
slaweqskydive is a tool which ajo and dalvarez were presenting us in Denver16:49
mlavalleI know16:49
slaweqit is like "distributed tcpdump"16:49
slaweqok16:50
mlavalleand I've seen patches from Assaf16:50
slaweqbut after Assaf send those patches we discussed it and decided that skydive can be more helpful in debugging such issues like we have now instead of doing some new tests16:51
*** mjturek has joined #openstack-meeting16:51
slaweqso to sum up16:51
mlavalleah ok16:51
mlavalleI'll see if I have time to look at skydive again16:51
slaweq#action mlavalle will send DNM patch which will add tcpdump in routers' namespaces to debug ssh issue16:51
slaweq#action slaweq will send DNM patch to tempest to dump router's namespace state when ssh will fail16:52
slaweqcorrect ^^?16:52
mlavalleyes16:52
slaweqok, thx16:52
slaweqfrom other things related to tempest jobs I saw one failure like:16:53
slaweqhttp://logs.openstack.org/47/650947/2/check/tempest-full/8688145/testr_results.html.gz16:53
slaweqit is also "well known" problem16:53
slaweqtempest is cleaning after test, sends DELETE request16:53
slaweqand this DELETE is processed for veeeeery long time in neutron, here it was like 83 seconds16:53
slaweqso tempest http client got timeout, and repeats request16:54
slaweqbut in the meantime neutron removed resource and tempest got 404 response for its second request16:54
slaweqand test is failed16:54
slaweqwe can maybe talk with gmann and other qa folks if maybe tempest shouldn't fail when it got 404 when deleting something16:54
slaweqbut that would be only workaround of the problem16:55
gmannslaweq: yeah we usually have ignore case for 404 when deleting the resource after tests16:55
slaweqso gmann will it be reasonable to send patch to tempest to ignore such case and not fail?16:56
gmannslaweq: if delete is part of test then we cannot ignore otherwise you are right we can consider the 404 as pass for tests16:56
gmannslaweq: for cleanup things yes. but i did not check the tests you mentioned16:56
*** iyamahat has joined #openstack-meeting16:57
slaweqgmann: ok, thx16:57
njohnstonWe're just about out of time; do we want to talk about WSGI testing?16:57
gmannpush a patch and i can review that16:57
slaweqso I will check exactly what was the place when this failed and will push patch16:57
slaweqnjohnston: sure, go on16:57
slaweqgmann: thx :)16:58
*** electrofelix has quit IRC16:58
slaweqnjohnston: or maybe we can add it to next week's agenda?16:58
njohnstonwell, I was wondering if we should move the wsgi jobs from experimental to check (leaving them nonvoting)16:58
slaweqand have more time for it?16:58
njohnstonjust to gather data, and add them to the dashboard so we can see how their failure rates are16:58
slaweqI think that we can move those jobs to check queue16:59
njohnstonand then we can talk more about it next week, but armed with facts16:59
slaweqthat would be fine16:59
mlavalle++16:59
slaweqnjohnston++16:59
njohnstonok I'll do that16:59
slaweqthx16:59
mlavallebefore we go16:59
njohnston#action njohnston move wsgi jobs to check queue nonvoting16:59
mlavallecongrats to njohnston16:59
mlavallehttps://www.wsj.com/articles/virginia-wins-ncaa-men-s-basketball-championship-11554781679?mod=article_inline16:59
slaweqnjohnston: congrats :)16:59
njohnstonthank you! \o/16:59
mlavallehis alma mater is national basketball champion17:00
slaweqok, thx for attending the meeting17:00
slaweqsee You all next week17:00
slaweq#endmeeting17:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"17:00
openstackMeeting ended Tue Apr  9 17:00:23 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-04-09-16.00.html17:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_ci/2019/neutron_ci.2019-04-09-16.00.txt17:00
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_ci/2019/neutron_ci.2019-04-09-16.00.log.html17:00
ralonsohbye17:00
mlavalleo/17:00
*** psachin has quit IRC17:00
*** priteau has quit IRC17:04
*** yamahata has joined #openstack-meeting17:07
*** mriedem is now known as mriedem_away17:27
*** ijw has joined #openstack-meeting17:28
*** yamamoto has joined #openstack-meeting17:28
*** bobh has quit IRC17:32
*** kopecmartin is now known as kopecmartin|off17:36
*** gmann is now known as gmann_afk17:40
*** ralonsoh has quit IRC17:44
*** mriedem_away is now known as mriedem17:46
*** Shrews has joined #openstack-meeting17:49
*** sridharg has quit IRC17:55
*** davidsha_ has quit IRC17:55
*** sidx64 has joined #openstack-meeting18:00
*** ricolin has quit IRC18:04
*** dmsimard has joined #openstack-meeting18:04
*** sidx64_ has joined #openstack-meeting18:06
*** sidx64 has quit IRC18:06
*** ijw has quit IRC18:13
*** e0ne has joined #openstack-meeting18:16
*** yamamoto has quit IRC18:19
*** gmann_afk is now known as gmann18:21
*** e0ne has quit IRC18:23
*** lpetrut has joined #openstack-meeting18:25
*** lpetrut has quit IRC18:29
*** e0ne has joined #openstack-meeting18:33
*** eharney has quit IRC18:42
*** jamesmcarthur has quit IRC18:55
*** yamamoto has joined #openstack-meeting18:58
clarkbanyone here for the infra meeting?18:59
clarkbwe'll get started in a minute or so19:00
ianwo/19:00
cmurphyo/19:00
clarkb#startmeeting infra19:01
openstackMeeting started Tue Apr  9 19:01:05 2019 UTC and is due to finish in 60 minutes.  The chair is clarkb. Information about MeetBot at http://wiki.debian.org/MeetBot.19:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:01
*** openstack changes topic to " (Meeting topic: infra)"19:01
openstackThe meeting name has been set to 'infra'19:01
clarkb#link http://lists.openstack.org/pipermail/openstack-infra/2019-April/006308.html19:01
clarkb#topic Announcements19:01
*** openstack changes topic to "Announcements (Meeting topic: infra)"19:01
clarkbI don't have anything to announce19:01
clarkb#topic Actions from last meeting19:01
*** openstack changes topic to "Actions from last meeting (Meeting topic: infra)"19:02
clarkb#link http://eavesdrop.openstack.org/meetings/infra/2019/infra.2019-04-02-19.01.txt minutes from last meeting19:02
*** ijw has joined #openstack-meeting19:02
clarkbianw was going to talk to fedora about their i18n plans. This happened and there is a separate meeting agenda item for it19:02
*** njohnston has left #openstack-meeting19:02
clarkbianw: do you want to talk about that now or should we continue on and get to it when it comes up in our agenda runthrough?19:02
ianwclarkb: let's just talk at end and do more important stuff first19:03
clarkbok19:03
clarkb#topic Specs approval19:03
*** openstack changes topic to "Specs approval (Meeting topic: infra)"19:03
clarkbUnsurprisingly I think we've been largely heads down on the opendev and LE specs so nothing new here19:03
clarkb#topic Priority Efforts19:03
*** openstack changes topic to "Priority Efforts (Meeting topic: infra)"19:03
clarkbI guess we get to dig straight into the fun topics today :)19:03
clarkb#topic Update Config Management19:04
*** openstack changes topic to "Update Config Management (Meeting topic: infra)"19:04
clarkbThe puppet-4 upgrades have slowed down due to the openstack release this week. I plan to pick that up again on thursday/friday time permitting19:04
clarkbwe have been able to cleanup some of our ansible around puppet installation and configuration which is nice19:04
*** ociuhandu has joined #openstack-meeting19:05
clarkbOn the docker side of things our docker image build jobs don't work with ipv6 because docker doesn't work with ipv619:05
clarkbhttps://review.openstack.org/651353 is a possible fix but I'm not super confident in it as it assumes skopeo doesn't have the same issue that docker has19:05
* mordred has faith in skopeo19:05
clarkb#link https://github.com/moby/moby/issues/39033 Upstream docker bug19:05
clarkbmostly a heads up that we may see these jobs fail until they are fixed and if you have spare cycles to review that potential fix it will liekly be helpful19:06
clarkbthe parent change explains some of the problems in more detail19:06
*** bbowen_ has joined #openstack-meeting19:06
clarkbpabelanger and dmsimard have been poking at the zuulcd jobs again and I approved pabelanger's fix for the current/previous issue19:07
clarkbif that fixed it in general I think we should pivot the existing job away from doing zuul reloads to configuring gitea and/or the nameservers since gitea and the nameservers do not puppet19:08
clarkbI am hoping to dig into this particular thing this afternoon19:08
clarkbanything else to add on this topic?19:08
mordred++19:08
*** bbowen has quit IRC19:09
*** yamamoto has quit IRC19:09
clarkbSounds like no. Onward!19:10
clarkb#topic OpenDev19:10
*** openstack changes topic to "OpenDev (Meeting topic: infra)"19:10
clarkbhttps://review.openstack.org/#/c/651268/ is on its way in to test our cgit to gitea redirects19:11
clarkbianw notes it is ok to merge git -> https protocol changes. I approved a couple yesterday19:11
clarkbOne thing I realized yesterday was that we should confirm that the new project creation in gitea works without needing fixups. I think things look ok but I haven't been able to check a new projects with multiple branches to ensure the default branch = master fix is working19:12
fungiworth noting, i use a /etc/hosts addition like the following for testing the legacy site redirects:19:12
fungi2001:4800:7817:103:be76:4eff:fe04:e3e3 git.airshipit.org git.openstack.org git.starlingx.io git.zuul-ci.org19:12
clarkbfungi: I expect you'll be passing that along to the various projects as well?19:12
mordredclarkb: I cannot speak for projects with multiple branches - but the three projects I just created in gitea all worked, so that's good19:12
clarkbmordred: yup projects with just master branches look great19:12
ianwclarkb: oh, i just wanted to confirm if it was ok if i merged those as we discussed19:12
fungii was hoping to give dtroyer and jroll and ... (who's our airship contact?) a heads up now19:12
* jroll pops head up19:13
* dtroyer raises head… :)19:13
clarkbianw: oh got it. Ya I think so19:13
* mordred hands jroll and dtroyer pies19:13
clarkbianw: the git:// protocol is going away :)19:13
dtroyerbutterscotch!19:13
clarkbjroll: dtroyer about half an hour after https://review.openstack.org/#/c/651268/ merges you'll be able to test our redirects from cgit to gitea19:13
ianwyep, ok, so i'll probably do that thu or fri .au time, get them out of the way (for any that don't have comments ... and maybe one or two have merge failures)19:14
jrollcool19:14
clarkbjroll: dtroyer 23.253.125.17 is the ipv4 address of the host if you can't use the ipv6 rule fungi pasted above19:14
fungijroll: dtroyer: see the /etc/hosts entry i mentioned above for how i recommend performing local testing19:14
jrollso I should just be able to drop that hosts file entry and clone some things?19:15
fungialso noted in a review comment on that change19:15
clarkbjroll: that and browse urls yup19:15
fungiyes, cloning and browsing should both be supported19:15
dtroyergotcha, thanks!19:15
*** e0ne has quit IRC19:15
jrollexcellent, thank you19:15
jrollI'll do that tomorrow19:15
fungitechnically the git.openstack.org one has been in place for testing for a couple weeks already19:15
fungithat change is adding the necessary fixups to also support git.airshipit.org, git.starlingx.io and git.zuul-ci.org19:16
clarkbon the testing front the other gitea thing I wanted to make sure we have tested is that the gitea side redirects work (at least generally)19:16
clarkbmordred: fungi ^ do you know if we've done that yet?19:16
mordredyes - I have tested broadly-speaking that gitea-side redirects work19:16
fungiwhen performing repository renames and namespace moves? i believe that was tested already19:17
*** whoami-rajat has quit IRC19:17
clarkbgreat19:17
clarkbI know corvus did some work on them and found the inter org didn't work as is and then he got ap atch merged to fix that19:17
mordredand I think corvus sent a patch upstream to improve cases where a redirect redirected to a redirect or something crazy like that19:17
mordredyeah19:17
clarkbseems like things are coming together and its mostly down to writing a script/playbook/somethign to do the actual changesi n gerrit and gitea?19:18
fungiit was if you renamed a project to teh old name of another project19:18
fungi(which is now fixed, i gather)19:18
fungiyes, i'm on the hook to get ther in-repo edits scripted and tested, but happy to take help19:18
* mordred offers fungi help by cheering him on19:18
clarkbfungi: feel free to reach out when you've got some tasks that you can point me at.19:19
mordredfungi, fungi, he's our man, if he can't do it ... we have no backup options!19:19
mordred(yeah, also happy to actually help)19:19
fungias discussed last week, this will be both the git.openstack.org to opendev.org edits as well as renaming references to the repositories and their namespaces in those repositories and other repositories which may mention them19:19
jrollfungi: while we're on the topic, do you want/need anything from me for scripting the no-longer-openstack-namespace renames?19:20
fungiclarkb: thanks, will do19:20
anteayaI picturing that with pom-poms19:20
jrollI always picture mordred with pom-poms :D19:20
clarkbjroll: fungi on that topic I think we should pick a day to freeze project changes. Say starting Thursday after the openstack release?19:20
anteayait explains the typos19:20
*** jamesmcarthur has joined #openstack-meeting19:21
clarkbmaybe we don't need to be so conservative, but that gives us a chance to generate accurate reviewable lists that can be reviewed without wondering "where does this random new project go"19:21
jrollclarkb: as in code changes? or changes to the project list?19:21
jrollI assume the latter19:21
clarkbjroll: ya chagnes to the project list. So that on the 19th we don't have to figure out where openstack/new-thing-from-yesterday goes19:21
jrollclarkb: I don't see any problem freezing that for a week19:22
fungijroll: maybe at least a clear plan... i'm imagining something like: leave anything mentioned ni openstack governance projects.yaml in the openstack namespace (except for infra and qa projects which are in openstack-infra and openstack-dev?) and then move everything else to a not-openstack namespace (i had some new ideas to float, btw)19:22
fungioh, also probably repos for sigs and the governance repos themselves would remain in the openstack namespace?19:22
fungiwould be good to have all that spelled out though19:22
jrollfungi: ok, maybe we can chat tomorrow sometime?19:23
fungihappy to, but maybe not in the middle of release activity19:23
fungiafter 15:00z should work for me19:23
jrollah right. friday would also work, since the release will be done by then :)19:23
fungicatch up with me when you have time19:24
jrollwill do, thanks19:24
fricklerhow's the plan with ipv6 for opendev.org?19:24
dtroyernot that we have many changes but I'll announce that freeze to stx also…19:24
fungiyeah, airship just proposed a new repo earlier today, so there is some activity from the pilot projects as well19:25
clarkbjroll: fungi: when you've got a plan sorted out we should start sending periodic communication reminders19:25
fungiyes, definitely19:25
jroll++19:25
clarkbfrickler: I think to start we aren't going to ipv6?19:25
clarkbfrickler: then when mnaser is able to deploy ipv6 in that cloud we'll update things for ipv6?19:25
mnaserI think we're in a week or two away, sorry for the delay, carriers can kinda suck :)19:26
clarkbthat shouldn't break anything (we already have jobs use ipv4 only github repos from our ipv6 only clouds)19:26
fricklerclarkb: I was hoping that that was going to happen earlier19:26
clarkband jobs should use the zuul provided repo19:26
clarkbrather than talk to opendev.org directly19:26
mnaserthey've blocked us because of router issues apparently but they're patched it and ipv6 will arrive natively without any changes19:27
clarkbmnaser: our servers will start getting RAs one day?19:27
*** sidx64_ has quit IRC19:27
mnaserclarkb: yup pretty much19:27
mordredneat19:27
mnaserso that should be transparent as long as you have autoconf enabled19:27
clarkbfrickler: ^ so we should be able to add AAAA records as soon as our servers notice the RAs and configure themselves19:28
mordredthat will be pleasing19:28
clarkbmight also need to restart haproxy and gitea to start listening on the new addr depending on how they are configured19:28
fricklero.k., two weeks doesn't sound too far in the future19:28
fungihopefully we don't have any contributors/users hitting those from v6-only parts of the internet with no 6to4 nat available19:29
clarkbAlright anything else before we move on to storyboard?19:29
*** efried is now known as efried_afk19:30
clarkb#topic Storyboard19:31
*** openstack changes topic to "Storyboard (Meeting topic: infra)"19:31
clarkbfungi diablo_rojo sorry I've been very swamped with the other priority efforts and server upgrades and haven't had time for storyboard lately19:31
fungiyou and me both, i'm afraid19:31
clarkbLooks like mkarray is working to improve mysql queries which is good19:32
* mordred also apologizes19:32
fungiyes, database optimization is sorely needed for the storyboard.openstack.org deployment in particular19:32
fungiobserve the time it takes to load, say, the story for our opendev git/gerrit transition19:33
fungiwhich is not an overly massive one19:33
clarkbany idea where we are with outreachy?19:33
clarkbI think diablo_rojo was particulary involved in ^19:33
fungi#link https://storyboard.openstack.org/#!/story/2004627 OpenDev Gerrit Hosting19:34
clarkbAlright any other storyboard topics? Our general topics list is reasonably large so we should keep moving if not19:34
fungiyeah, i think we can move along19:35
clarkb#topic General Topics19:35
*** openstack changes topic to "General Topics (Meeting topic: infra)"19:35
clarkb#link https://www.openstack.org/ptg#tab_schedule PTG Schedule has us Thursday and Friday19:35
clarkbas a reminder we've got Thursday and Friday at the PTG19:35
clarkbOne thing I've struggled with all the rather large changes we've been making recently is figuring out a ptg schedule19:35
clarkbOne Idea I had was to do it more unconference style. The other was don't worry about it until the week before the PTG19:36
clarkbIf you plan to attend any sense for whether or not waiting until the week before to write down a schedule will be a hindrance?19:36
clarkbits just hard to predict what will be important after the opendev switch19:36
fungii tried the unconference method for our first couple of ptgs. it was a good way for me to deflect attention from my abject lack of planning ;)19:37
*** boxiang has quit IRC19:37
clarkbwe also don't have the dedicated helproom time19:37
clarkbbut I figure I'll be around saturday and can help with those things then19:37
*** boxiang has joined #openstack-meeting19:37
*** eharney has joined #openstack-meeting19:38
clarkbI'm not hearing screaming about that so for now I'll continue to not worry about it until after the opendev switch on the 19th :)19:38
clarkbNext up is letsencrypt progress19:38
clarkbianw any luck with the staging service on graphite?19:38
*** tssurya has quit IRC19:39
ianwclarkb: need to look soon, got stuck yesterday with ansible stopping due to the puppet deb thing19:39
clarkb#link https://review.openstack.org/#/c/651055/ Really letsencrypt graphite.o.o19:39
clarkbok I'll review ^ after the meeting and the puppet deb fix merged19:40
ianwoh yeah, that going in will help too, thanks19:40
clarkbNext is Trusty server upgrades19:40
clarkb#link https://etherpad.openstack.org/p/201808-infra-server-upgrades-and-cleanup19:40
clarkbI'd like to do the lists.o.o upgrade Friday19:40
clarkb#link https://etherpad.openstack.org/p/lists.o.o-upgrade-notice Upgrade lists.o.o Friday19:40
clarkbif ya'll want to read over that notice ^ I'll send it out in a bit19:41
clarkbBasically says we need to upgrade due to ubuntu lts support cycles and that the outage should be minimally visible19:41
clarkbI've tested the upgrade with notes linked to from the first etherpad there19:41
clarkbAnyone know of a reason to not do it this friday other than our mail guru is hiking in the desert?19:41
mordredthat would be the primary reason - but we're _probably_ fine19:42
clarkbya I tested that our vhosting of mailman works after the upgrade which was my biggest concern19:42
mordredI'm pretty sure at this point you're a mailman expert :)19:42
clarkbmordred: that was fun debugging for sure19:43
mordredI'm a little surprised you didn't rage-rewrite it in haskell19:43
clarkbOnce lists.o.o is upgraded we are left with static, status, ask, refstack, and wiki19:43
clarkbfungi is working on wiki I think. which means we need volunteers for the other 419:43
clarkbif you are able to please grab one :)19:43
mordredI can look at status19:43
*** bbowen__ has joined #openstack-meeting19:43
clarkbAlso I spoke with people on the foundation side about groups going away and that is still the plan and they are aware of it19:44
*** awaugama has quit IRC19:44
clarkbso no change there (which is good means we can delete it)19:44
*** e0ne has joined #openstack-meeting19:44
clarkbAnd that takes us to Fedora Zanata plans (and mulling our own i18n plans)19:44
clarkbianw: ^ thank you for following up with fedora on that19:45
clarkbIt sounds like they are moving to another tool: weblate19:46
*** bbowen_ has quit IRC19:46
clarkba python django app that hopefulyl doesn't present much trouble for us to run if we want to move to it too19:46
fungiwhich, according to AJaeger, is used by (some of) suse?19:46
clarkbbut I haven't looked at the details yet19:46
ianwyeah, i got no concrete answers, but weblate seems ok19:47
clarkbOne of the big features our translators want is translation memory. I expect if we don't lose that they will be happy19:47
ianwi had a bit of a play, it seems like it could integrate in a similar way to zanata19:47
ianwone thing i wanted to float was, that if this is communicating via being notified of changes via webhooks in a post job, and proposing updates back via gerrit19:48
ianw... the hosted options look pretty compelling19:48
fungisure, our beef with transifex is that their hosted service wasn't the same as the software they published, and eventually ended up dropping their gratis offering entirely19:49
clarkblooks like they negotiate hosted service for open source software19:49
mordredyah19:49
fungiand there was no hosted zanata19:49
fungiso we hosted that ourselves19:49
clarkbso we shouldn't assume we'll be able to negotiate a favoriable setup but certainly seems worth reaching out to them19:49
ianwyeah, this isn't run by $MEGACORP, seems committed to open source and it seems like it would be mutually beneficial19:50
ianwanyway, just wanted to mention that19:50
clarkband they list translation memory as a feature on the hosted option so it checks that requirement19:50
mordredianw: my biggest concern would be its ability to propose changes to gerrit (since lots of things that integrate with git assume that they're going to just push to git) ... but assuming engineering can be sorted, I wouldn't have an issue with a hosted thing19:50
fungiwe may also lack for configurability/flexibility if we don't host it ourselves, but that might be okay. one thing we lost when dropping transifex was the existing community of translators who would just pick up random projects19:50
ianwmordred: yeah, it has gerrit plugins, and uses git-review underneath.  it's not well documented, but it's an option19:51
mordredoh wow19:51
clarkbfungi: I think transifex shared memory across all their hosted projects too19:51
clarkbfungi: so you'd get free translations for common strings19:51
clarkbianw: nice19:51
mordredso cool - yeah - that sounds like a potential win19:51
clarkbI wonder what the proper way to reach out there is. I think reed did the transifex "barganing" in the past19:51
fungii'm entirely fine with recommending gratis services we don't operate when they're running free software themselves19:52
mordredclarkb: I'm sure jbryce has tons of free time19:52
clarkbmaybe I send them a nice email and cc frank/ianychoi/ianw/ and jbryce ?19:52
mordredclarkb: ++ seems like a good start19:52
clarkbmordred: exactly :) I'll see if there is any concern on the foundation side as they may have to handle any official contracting19:52
mordredclarkb: also - if we can figure it out generally, it would be a nice integration/partnership for opendev overall potentially19:53
ianwsure; there will definitely be engineering but nice thing is it could all be parallel; no need to shut zanata down to experiement with it19:53
mordred++19:53
clarkbsounds good. Thanks again for digging into that ianw19:54
clarkb#topic Open Discussion19:54
*** openstack changes topic to "Open Discussion (Meeting topic: infra)"19:54
clarkbYesterday I put together https://etherpad.openstack.org/p/infra-backlog-cleanout to collect a list of infra related changes that we could clear out of our backlog easily19:54
clarkbI've added and remvoed things as changes merge19:54
clarkbfeel free to add things if you notice they need attention19:55
clarkbmy next step was to try and figure out dashboarding of that so you could jsut get it at a gerrit url19:55
clarkbAlso remember we are trying to be slushy to avoid causing problems for the openstack release tomorr19:56
clarkb*tomorrow19:56
anteayaI can be slushy19:57
* anteaya looks out the window19:57
clarkbspeaking of slushy the weather in denver today is like 20C tomorrow they have a blizzard warning19:57
mordredit's a bit too warm here to be slushy19:57
clarkbIf the weather is good when we are there I think it would be fun to go back to the beer garden :)19:57
mordredit's 31C here today19:58
anteayawow, shorts weather19:58
clarkbbut clearly that can't be sorted until we are closer to the summit/ptg19:58
anteayait's maple syrup weather here19:58
fungithough as we come out the other end of the openstack release, it might be good to merge dmsimard's gerrit replication config change and then restart gerrit with that so we can test with it before the opendev maintenance19:58
clarkbfungi: ++19:58
clarkbI think thursday might eb a lot less slushy :)19:58
clarkbI'd like to get some puppet-4 upgrades in on thursday if release team is happy with where they are19:58
clarkbAnd we are at time. Thanks everyone19:59
clarkb#endmeeting19:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"19:59
openstackMeeting ended Tue Apr  9 19:59:14 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/infra/2019/infra.2019-04-09-19.01.html19:59
anteayathanks clarkb19:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/infra/2019/infra.2019-04-09-19.01.txt19:59
openstackLog:            http://eavesdrop.openstack.org/meetings/infra/2019/infra.2019-04-09-19.01.log.html19:59
*** bbowen__ has quit IRC20:08
*** pfallenop has quit IRC20:08
*** Shrews has left #openstack-meeting20:08
*** jamesmcarthur has quit IRC20:17
*** jamesmcarthur has joined #openstack-meeting20:18
*** mjturek has quit IRC20:18
*** pfallenop has joined #openstack-meeting20:20
*** pcaruana has quit IRC20:31
*** ijw has quit IRC20:33
*** pcaruana has joined #openstack-meeting20:33
*** pcaruana has quit IRC20:36
*** pcaruana has joined #openstack-meeting20:39
*** jamesmcarthur has quit IRC20:44
*** jamesmcarthur has joined #openstack-meeting20:45
*** pcaruana has quit IRC20:47
*** ttsiouts has joined #openstack-meeting20:55
*** bbowen__ has joined #openstack-meeting21:09
*** SpamapS has quit IRC21:10
*** SpamapS has joined #openstack-meeting21:11
*** jamesmcarthur has quit IRC21:11
*** eharney has quit IRC21:19
*** efried_afk is now known as efried21:25
*** igordc has quit IRC21:25
*** e0ne has quit IRC21:28
*** tejdeep has joined #openstack-meeting21:38
*** tejdeep has left #openstack-meeting21:46
*** mattw4 has quit IRC21:56
*** mattw4 has joined #openstack-meeting21:57
*** ijw has joined #openstack-meeting22:00
*** slaweq has quit IRC22:01
*** jamesmcarthur has joined #openstack-meeting22:03
*** hongbin has joined #openstack-meeting22:13
*** slaweq has joined #openstack-meeting22:14
*** ttsiouts has quit IRC22:16
*** ttsiouts has joined #openstack-meeting22:17
*** slaweq has quit IRC22:18
*** ttsiouts has quit IRC22:21
*** rcernin has joined #openstack-meeting22:28
*** jamesmcarthur has quit IRC22:42
*** bdperkin has quit IRC22:47
*** jamesmcarthur has joined #openstack-meeting22:52
*** jamesmcarthur has quit IRC23:03
*** bdperkin has joined #openstack-meeting23:03
*** raildo has quit IRC23:05
*** jamesmcarthur has joined #openstack-meeting23:06
*** enriquetaso has quit IRC23:11
*** jamesmcarthur has quit IRC23:14
*** _erlon_ has quit IRC23:25
*** mattw4 has quit IRC23:29
*** jamesmcarthur has joined #openstack-meeting23:30
*** jamesmcarthur has quit IRC23:30
*** mlavalle has quit IRC23:32
*** mattw4 has joined #openstack-meeting23:39
*** slaweq has joined #openstack-meeting23:48
*** hongbin has quit IRC23:48
*** dklyle has quit IRC23:52
*** slaweq has quit IRC23:52
*** LiangFang has quit IRC23:56

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