Tuesday, 2019-08-27

*** markvoelker has joined #openstack-meeting00:10
*** markvoelker has quit IRC00:15
*** gyee has quit IRC00:18
*** bobh has joined #openstack-meeting00:20
*** bobh has quit IRC00:30
*** seongsoocho has joined #openstack-meeting00:34
*** hongbin has joined #openstack-meeting00:37
*** njohnston_ has joined #openstack-meeting00:42
*** njohnston_ has quit IRC00:45
*** brault has joined #openstack-meeting00:52
*** ociuhandu has joined #openstack-meeting00:53
*** brault has quit IRC00:57
*** ociuhandu has quit IRC00:57
*** enriquetaso has quit IRC01:09
*** bobh has joined #openstack-meeting01:10
*** slaweq has joined #openstack-meeting01:11
*** lseki has quit IRC01:12
*** rcernin has quit IRC01:13
*** bobh has quit IRC01:13
*** slaweq has quit IRC01:16
*** zhubx has quit IRC01:57
*** zhubx has joined #openstack-meeting01:57
*** mhen has quit IRC01:58
*** zhubx has quit IRC02:08
*** apetrich has quit IRC02:10
*** slaweq has joined #openstack-meeting02:11
*** rcernin has joined #openstack-meeting02:13
*** ykatabam has joined #openstack-meeting02:14
*** slaweq has quit IRC02:16
*** larainema has joined #openstack-meeting02:23
*** ekcs has joined #openstack-meeting02:40
*** markvoelker has joined #openstack-meeting03:10
*** markvoelker has quit IRC03:15
*** nicolasbock has quit IRC03:25
*** psachin has joined #openstack-meeting03:33
*** tpatil has joined #openstack-meeting03:55
*** shilpasd has joined #openstack-meeting03:59
samP#startmeeting masakari04:00
openstackMeeting started Tue Aug 27 04:00:36 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
samPtpatil: hi04:00
shilpasdHi04:01
samP#topic Critical Bugs and patches04:01
*** openstack changes topic to "Critical Bugs and patches (Meeting topic: masakari)"04:01
samPshilpasd: hi04:01
samPAny critical issues need to discuss here?04:01
samPany update about py3 testing?04:01
tpatilwe have addressed those issues04:02
tpatilmasker-monitors: https://review.opendev.org/#/c/66938704:02
samPtpatil: thanks.04:02
*** rfolco has quit IRC04:03
tpatilmasakari: https://review.opendev.org/#/c/678495/104:03
tpatilMasakari-client: https://review.opendev.org/#/c/665639/, I think this patch will address py3.7 issue as well04:03
tpatilon the above patch, I have given few nits, otherwise the patch is good to go04:03
*** nitinuikey has joined #openstack-meeting04:04
samPgot it. I will review those. Thanks for the fix04:04
samPtpatil: could you please take a look at following issue?04:08
samP#link https://bugs.launchpad.net/masakari/+bug/184074704:08
openstackLaunchpad bug 1840747 in masakari "relax api payload and accept custom input" [Undecided,New]04:08
*** markvoelker has joined #openstack-meeting04:10
*** slaweq has joined #openstack-meeting04:11
tpatilThat's possible, but we will need to handle the input at various places before processing04:11
tpatilit's also possible to add a new notification type which the payload can be generic04:12
tpatils/which/where04:12
samPI think the second option is better.04:13
tpatilAgree04:13
*** hongbin has quit IRC04:13
samPtpatil: Could you please take a look on this issue?04:14
*** markvoelker has quit IRC04:15
tpatilI will add a comment on the LP bug and see if the bug reporter is interested to implement it04:15
samPtpatil: sure, that will do.04:15
tpatilor you want us to take care of adding a new notification type04:15
*** ykatabam has quit IRC04:15
samPtpatil: let see whether the reporter has a solutoin in mind. Because he has the usecase04:16
*** slaweq has quit IRC04:16
tpatilsamP: Ok04:16
samPAny other ciritical items?04:17
samPif any, please bring them up anytime04:17
samP#topic Train Work Itmes04:17
*** openstack changes topic to "Train Work Itmes (Meeting topic: masakari)"04:17
samPPlease share if any update on Train work items04:18
shilpasdfor masakari-monitor documentation, two main section pending, will work on this in this week04:19
tpatildevstack support for host monitors, I have added a comment that this patch cannot be merged until CI has support for setting up IPMI, but is it possible to enable IPMI support in NTT third party CI job?04:19
*** nnsingh has joined #openstack-meeting04:20
tpatilI'm talking about "masakari-build-test" CI Job04:20
samPtpatil: I need to discuss this with CI maintenance team.04:21
tpatilsamP: Ok04:21
samPCurrently above ci have only VM base testing env.04:21
samPfor IPMI, you need bare metel or IPMI emulator in VM04:22
samPI will discuss this with maintenance team and get back to you,04:22
tpatilsamP: Ok, Thanks04:23
tpatilOperators Guide for masakari-monitors and masakari04:24
tpatilwork is in progress04:24
samPtpatil: thanks04:24
tpatilPlanning to add documentation to install and configure masakari and masakari-monitors from source code04:24
tpatilThat's all update on Train work items form my side04:25
samPthanks.04:25
samPNo update from my side.04:25
samP#topic AOB04:25
*** openstack changes topic to "AOB (Meeting topic: masakari)"04:25
samPAny other issues need to discuss here?04:25
samPif not, we could finish today's meeting here.04:28
tpatilsamP: no other issues to be discussed from my end04:28
samPOK then, please use openstack-discuss@lists.openstack.org ML or #openstack-maskari @freenode IRC for further discussions04:30
samPThank you all!04:30
samP#endmeeting04:30
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"04:30
openstackMeeting ended Tue Aug 27 04:30:22 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)04:30
openstackMinutes:        http://eavesdrop.openstack.org/meetings/masakari/2019/masakari.2019-08-27-04.00.html04:30
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/masakari/2019/masakari.2019-08-27-04.00.txt04:30
openstackLog:            http://eavesdrop.openstack.org/meetings/masakari/2019/masakari.2019-08-27-04.00.log.html04:30
*** tpatil has quit IRC04:42
*** ykatabam has joined #openstack-meeting04:49
*** ociuhandu has joined #openstack-meeting04:53
*** ykatabam has joined #openstack-meeting04:54
*** ociuhandu has quit IRC04:57
*** macz has joined #openstack-meeting04:58
*** shilpasd has quit IRC05:02
*** macz has quit IRC05:03
*** rubasov has quit IRC05:10
*** sridharg has joined #openstack-meeting05:10
*** sridharg has quit IRC05:10
*** markvoelker has joined #openstack-meeting05:10
*** sridharg has joined #openstack-meeting05:11
*** slaweq has joined #openstack-meeting05:11
*** markvoelker has quit IRC05:15
*** slaweq has quit IRC05:16
*** boxiang has joined #openstack-meeting05:23
*** Luzi has joined #openstack-meeting05:43
*** links has joined #openstack-meeting05:52
*** lpetrut has joined #openstack-meeting06:02
*** nitinuikey has quit IRC06:06
*** e0ne has joined #openstack-meeting06:06
*** nnsingh has quit IRC06:09
*** macz has joined #openstack-meeting06:11
*** zhubx has joined #openstack-meeting06:11
*** e0ne has quit IRC06:11
*** slaweq has joined #openstack-meeting06:11
*** boxiang has quit IRC06:11
*** macz has quit IRC06:15
*** slaweq has quit IRC06:15
*** zhubx has quit IRC06:24
*** zhubx has joined #openstack-meeting06:24
*** zhubx has quit IRC06:26
*** zhubx has joined #openstack-meeting06:26
*** rubasov has joined #openstack-meeting06:38
*** brault has joined #openstack-meeting06:38
*** macz has joined #openstack-meeting06:39
*** macz has quit IRC06:44
*** zhubx has quit IRC06:51
*** zhubx has joined #openstack-meeting06:52
*** trident has quit IRC07:00
*** markvoelker has joined #openstack-meeting07:06
*** trident has joined #openstack-meeting07:10
*** slaweq has joined #openstack-meeting07:11
*** _pewp_ has quit IRC07:12
*** _pewp_ has joined #openstack-meeting07:13
*** joxyuki has joined #openstack-meeting07:14
*** markvoelker has quit IRC07:15
*** slaweq has quit IRC07:15
*** macz has joined #openstack-meeting07:17
*** macz has quit IRC07:22
*** zhubx has quit IRC07:23
*** zhubx has joined #openstack-meeting07:23
*** zhubx has quit IRC07:25
*** zhubx has joined #openstack-meeting07:25
*** zhubx has quit IRC07:31
*** zhubx has joined #openstack-meeting07:31
*** markvoelker has joined #openstack-meeting07:35
*** rcernin has quit IRC07:40
*** markvoelker has quit IRC07:40
*** boxiang has joined #openstack-meeting07:41
*** zhubx has quit IRC07:43
*** slaweq has joined #openstack-meeting07:52
*** ralonsoh has joined #openstack-meeting07:52
*** tpatil has joined #openstack-meeting07:54
*** panda has quit IRC08:02
*** nitinuikey has joined #openstack-meeting08:02
*** panda has joined #openstack-meeting08:02
*** nnsingh has joined #openstack-meeting08:11
*** tetsuro has joined #openstack-meeting08:21
*** apetrich has joined #openstack-meeting08:22
*** nnsingh has quit IRC08:37
*** markvoelker has joined #openstack-meeting08:40
*** nitinuikey has quit IRC08:41
*** markvoelker has quit IRC08:45
*** priteau has joined #openstack-meeting08:50
*** slaweq has quit IRC08:53
*** macz has joined #openstack-meeting08:53
*** macz has quit IRC08:58
*** Lucas_Gray has joined #openstack-meeting09:01
*** Lucas_Gray has quit IRC09:08
*** slaweq has joined #openstack-meeting09:10
*** zbr has joined #openstack-meeting09:12
*** Lucas_Gray has joined #openstack-meeting09:13
*** tpatil has quit IRC09:14
*** slaweq has quit IRC09:14
*** slaweq has joined #openstack-meeting09:20
*** slaweq has quit IRC09:25
*** brinzhang_ has quit IRC09:32
*** brinzhang_ has joined #openstack-meeting09:32
*** psachin has quit IRC09:37
*** psachin has joined #openstack-meeting09:41
*** psachin has quit IRC09:48
*** brinzhang_ has quit IRC09:49
*** brinzhang_ has joined #openstack-meeting09:50
*** apetrich has quit IRC09:55
*** apetrich has joined #openstack-meeting10:00
*** Lucas_Gray has quit IRC10:04
*** Lucas_Gray has joined #openstack-meeting10:06
*** e0ne has joined #openstack-meeting10:11
*** macz has joined #openstack-meeting10:19
*** macz has quit IRC10:24
*** e0ne has quit IRC10:26
*** e0ne has joined #openstack-meeting10:28
*** e0ne has quit IRC10:32
*** tetsuro has quit IRC10:34
*** macz has joined #openstack-meeting10:40
*** macz has quit IRC10:45
*** slaweq has joined #openstack-meeting10:55
*** macz has joined #openstack-meeting11:01
*** nicolasbock has joined #openstack-meeting11:02
*** carloss has joined #openstack-meeting11:03
*** macz has quit IRC11:06
*** brinzhang_ has quit IRC11:09
*** brinzhang_ has joined #openstack-meeting11:09
*** tesseract has joined #openstack-meeting11:11
*** ykatabam has quit IRC11:13
*** macz has joined #openstack-meeting11:22
*** macz has quit IRC11:27
*** slaweq has quit IRC11:31
*** slaweq has joined #openstack-meeting11:33
*** slaweq has quit IRC11:41
*** slaweq has joined #openstack-meeting11:52
*** raub has quit IRC11:52
*** slaweq has quit IRC11:57
*** markvoelker has joined #openstack-meeting12:10
*** slaweq has joined #openstack-meeting12:12
*** slaweq has quit IRC12:17
*** links has quit IRC12:20
*** rfolco has joined #openstack-meeting12:22
*** links has joined #openstack-meeting12:35
*** larainema has quit IRC12:35
*** slaweq has joined #openstack-meeting12:39
*** priteau has quit IRC12:44
*** jraju__ has joined #openstack-meeting12:58
*** links has quit IRC12:59
*** slaweq has quit IRC13:04
*** macz has joined #openstack-meeting13:10
*** brinzhang_ has quit IRC13:12
*** brinzhang has joined #openstack-meeting13:14
*** macz has quit IRC13:15
*** slaweq has joined #openstack-meeting13:20
*** mriedem has joined #openstack-meeting13:22
*** eharney has joined #openstack-meeting13:23
*** Lucas_Gray has quit IRC13:24
*** slaweq has quit IRC13:25
*** dklyle has quit IRC13:38
*** david-lyle has joined #openstack-meeting13:38
*** priteau has joined #openstack-meeting13:44
*** macz has joined #openstack-meeting13:48
*** macz has quit IRC13:52
*** davee_ has joined #openstack-meeting13:53
*** e0ne has joined #openstack-meeting13:54
*** boden has joined #openstack-meeting13:59
*** mlavalle has joined #openstack-meeting13:59
mlavalle#startmeeting networking14:00
openstackMeeting started Tue Aug 27 14:00:38 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
rubasovhi14:01
amotokihi14:01
haleybhi14:01
*** lajoskatona has joined #openstack-meeting14:01
ralonsohhi14:01
njohnstono/14:01
bcafarel\o14:01
mlavalleok, let's get going14:01
mlavalle#topic Announcements14:02
*** openstack changes topic to "Announcements (Meeting topic: networking)"14:02
*** lseki has joined #openstack-meeting14:02
lajoskatonao/14:02
*** Luzi has quit IRC14:02
mlavalleOur T-3 milestone will be the week of September 9th14:03
*** shintaro has joined #openstack-meeting14:03
mlavallePlease remember that we are in the PTL candidates self nomination week: https://releases.openstack.org/train/schedule.html#u-ptl-nominations14:03
mlavalleif you want to run for PTL, please don't miss the deadline14:04
*** davidsha has joined #openstack-meeting14:04
*** liuyulong has joined #openstack-meeting14:04
mlavallewhich is Sep 03, 2019 23:45 UTC14:05
mlavallethat is next week14:05
mlavalle#link https://governance.openstack.org/election/14:05
mlavalleDon't forget to propose topics for the PTG in Shanghai. Here's the etherpad: https://etherpad.openstack.org/p/Shanghai-Neutron-Planning14:06
mlavallemany of you registered "tentative" in the etherpad14:07
mlavalleplease update it as soon as you get a yes or no from your sponsors14:08
mlavalleany other announcements from the team?14:08
amotokithe next week is "Final release for non-client libraries"14:09
amotokiwe need to release neutron-lib next week if needed.14:09
amotokithis is just a reminder.14:09
mlavalleok, let's get ready for that14:09
mlavallethanks for the reminder14:10
mlavalleok, let's move on14:10
mlavalle#topic Blueprints14:10
*** openstack changes topic to "Blueprints (Meeting topic: networking)"14:10
mlavalleThese are the blueprints we are targeting for T-3: https://launchpad.net/neutron/+milestone/train-314:11
mlavalleany updates on any of those blueprints?14:11
rubasovthe extraroute change's neutron-lib dependency was merged and released, thank you all14:12
rubasovI have a random question I'd like to raise at the end of the meeting14:13
mlavalleyeah I saw that14:13
rubasovI did write it up here: https://wiki.openstack.org/wiki/Network/Meetings#On_Demand_Agenda14:13
mlavalleis it related to the extraroute work?14:14
rubasovyes14:14
mlavalleok14:14
mlavallenjohnston: any updates on custom ethertypes?14:14
njohnstonI've been working away at it in the background and I have figured out I need to refactor it into multiple smaller changes; going to start pushing those this week14:15
mlavallethanks for the hard work!14:16
mlavalle#topic Community goals14:17
*** openstack changes topic to "Community goals (Meeting topic: networking)"14:17
mlavalleany updates on community goals?14:17
amotokiI have an update on the PDF goal.14:17
amotokithere are a lot of progress since last week. I worked with the docs/infra team to support the common job configuration and it has landed.14:18
amotokinow we can work on individual projects.14:18
amotokiI started to send patches to neutron stadium projects as you may notice.14:18
amotokiwe can find review links via https://review.opendev.org/#/q/topic:build-pdf-docs+(status:open+OR+status:merged)14:19
mlavalleThanks!14:19
amotokithe effort is tracked by https://storyboard.openstack.org/#!/story/2006099 and I will send more patches for projects uncovered yet.14:19
amotokiI don't see a big problem so far and time will complete the goal :)14:20
njohnstonFOr python 3 in the stadium - https://etherpad.openstack.org/p/neutron_stadium_python3_status - lajoskatona can you update us for networking-odl?  amotoki has done some work to finish up networking-bagpipe.  I haven't seen yamamoto online to ask him about networking-midonet.14:20
lajoskatonanjohnston: sure14:20
bcafarelamotoki: great progress on that PDF goal!14:21
amotokire: networking-bagpipe, I updated the etherpad to clarify the remaining topics.14:21
njohnstonamotoki: Thanks for your work, I just gave a +2 to both patches you point out14:21
lajoskatonathe most important patches for networking-odl are on the master, and I have few other (perhaps 4 with elod's patch) to make te old job efinitions zuulv3 compatible14:21
lajoskatonanjohnston: so as I have written on the pad, the must be done part is ready, but I try again to find somebody from qa team as well for zuul related review to push the other patches.14:22
njohnstonlajoskatona: let me know if you need any assistance14:24
amotokilajoskatona: which patches need to be reviewed by the qa team?14:25
amotokion zuulv3 migration?14:25
lajoskatonaamotoki: these: https://review.opendev.org/#/q/status:open+project:openstack/networking-odl+branch:master+topic:use-latest-odl14:25
mlavalleI can help with those14:26
mlavalleI'll take a look later today14:26
mlavalleor early tomorrow morning14:26
lajoskatonaamotoki: it is a series, and the top one, which is for tempest is under investigation from ODL team, as the job ends with timeout14:26
amotokilajoskatona: thanks14:26
lajoskatonamlavalle: thanks, I got some promise from gmann as well14:27
mlavalleso the first two are good to go14:27
mlavalle?14:27
lajoskatonanjohnston: thanks, I will check the patches, if I need ot rebase or similar14:27
mlavalleok, let's move on14:28
amotokinetworking-bagpipe fullstack job is failing by some neutron change even after https://review.opendev.org/#/c/677711/ lands. it is nice if someone can take a look (as I will be travel since tomorrow this week)14:28
lajoskatonamlavalle: yes14:28
mlavalle+14:28
mlavalleok, let' move on14:29
mlavalle#topic Bugs14:29
*** openstack changes topic to "Bugs (Meeting topic: networking)"14:29
mlavallelast week our deputy was Swami. Did anybody see a report from him in the ML?14:31
amotokiI see him message in #openstack-neutron channel. Looking for it.14:31
mlavallehe confirmed last week by email that he was going to take care of his duty week14:31
amotokiFound!  https://docs.google.com/spreadsheets/d/1JjcSHL6hFYsAvlrcgK7_Eje1S4vvJdvm363_Mmy557I/edit?usp=sharing14:32
bcafarelhttps://docs.google.com/spreadsheets/d/1JjcSHL6hFYsAvlrcgK7_Eje1S4vvJdvm363_Mmy557I/edit?usp=sharing14:32
bcafarelhe, a second too late :)14:32
mlavalleThanks14:34
mlavalleso everything high has been fixed or has an owner14:35
haleybor is incomplete14:35
* haleyb just marked 1840952 incomplete14:36
mlavalleyes, the undecided ones are incomplete14:36
mlavallethanks for the undecided tag an that last one haleyb14:37
mlavalleI mean, incomplete14:37
amotokibug 1841067 is related to nova interaction. do we have any tag for nova interaction?14:37
openstackbug 1841067 in neutron "SR-IOV agent depends on mac addresses for getting bound ports" [Medium,Confirmed] https://launchpad.net/bugs/184106714:37
haleybnp, i forgot to change when i looked yesterday14:37
mlavalleno, but maybe we should create one14:38
*** priteau has quit IRC14:39
mlavallein any case, I'll look at that bug14:39
mlavalleany other bugs we should discuss today?14:40
mlavalleok, for this week our deputy is lajoskatona14:41
lajoskatonamlavalle: my eyes on lunchpad14:41
mlavalleand next week it's njohnston's turn14:42
lajoskatonalaunchpad--^14:42
njohnstonaye aye captain14:42
mlavallecool14:42
mlavalle#topic CLI / SDK14:42
*** openstack changes topic to "CLI / SDK (Meeting topic: networking)"14:42
mlavalleamotoki: anything else to say about this in preparation for end of cycle?14:43
amotokinothing special except extra route support patch.14:43
mlavalleThanks!14:43
mlavalle#topic nuetron-lib14:44
*** openstack changes topic to "nuetron-lib (Meeting topic: networking)"14:44
*** lpetrut has quit IRC14:44
mlavalle#undo14:44
openstackRemoving item from minutes: #topic nuetron-lib14:44
mlavalle#topic neutron-lib14:44
*** openstack changes topic to "neutron-lib (Meeting topic: networking)"14:44
mlavalleboden: any updates?14:44
bodenhi14:44
mlavallenice to see you back :-)14:45
mlavallethe new Idahoan!14:45
bodenno updates from me really... I'm just back from a long vacation so just catching up with some patches that were out prior to vaca14:45
bodenMontanaian actually, or whatever they call us14:45
mlavalleahhh, well, congrats!14:45
bodenthanks14:46
mlavalledid you see amotoki's comment about releasing neutron-lib next week?14:46
*** shintaro has quit IRC14:46
bodenI saw the comment.. we can release whenever folks want; no problems there14:47
mlavallecool14:47
mlavallelet's move on14:47
mlavalle#topic On demand agenda14:47
*** openstack changes topic to "On demand agenda (Meeting topic: networking)"14:47
ralonsohhi, we talked about this https://bugs.launchpad.net/neutron/+bug/184106714:48
openstackLaunchpad bug 1841067 in neutron "SR-IOV agent depends on mac addresses for getting bound ports" [Medium,Confirmed]14:48
ralonsohbut we should raise the importance of it14:48
ralonsohthat will imply a nova-neutron coordination14:48
ralonsohand a change on the sriov agent14:48
ralonsohdoes this rfe need a spec??14:49
ralonsohjust asking14:49
ralonsoh(btw, is not marked as rfe)14:49
njohnstonI just wanted to discharge my oslo liaison responsibility and let everyone know that there is an issue in oslo.service with using SIGHUP signals to reload mutable configs; we worked on this a cycle or two ago.  Fix in progress: https://review.opendev.org/#/c/641907/14:49
njohnstonbasically what happens is that the SIGHUP causes a full service restart instead of a graceful config reload14:50
* bcafarel reads14:51
njohnstonwhich means some RPC messages can get lost, and all the other sorts of negative effects an unanticipated service restart might generate14:51
bcafarelI wonder if it could help for that neutron sighup issue I was looking into at some point (trying to find lp number)14:51
mlavallenjohnston: thanks for the heads up14:52
amotokiralonsoh: is the approach clear enough? If it is just an implementation topic, I think we can skip a spec.14:52
mlavalleralonsoh: yeah, to me it looks like border line RFE / bug14:53
amotokiRFE sounds fine for bug 1841067. I will add the tag14:53
openstackbug 1841067 in neutron "SR-IOV agent depends on mac addresses for getting bound ports" [Medium,Confirmed] https://launchpad.net/bugs/184106714:53
ralonsohamotoki, if you agree with https://review.opendev.org/#/c/676713 that's ok14:53
ralonsohthat was just a heads-up, because this is a change in the architecture of the sriov agent14:53
mlavalledo you forsee a massive change?14:54
ralonsohmlavalle, maybe with the way we assign the white-list14:54
mlavalleok, in that case let's look at it as RFE, as suggested by amotoki14:55
mlavalleok looking at the topic raised by rubasov....14:55
rubasovthanks14:56
rubasovI'm asking for directions14:56
mlavalleI faced something similar when implementing the activate action for multiple port bindings14:56
rubasovif extension2 builds on extension114:56
rubasovthen should its api-def repeat extension1's api-def parts?14:56
rubasovmy assumption was it shouldn't14:57
rubasovbut then I get strange test failures like referred in the wiki page14:57
mlavalleit is possible we have a bug in Pecan14:57
mlavalleI mean our code based on Pecan14:57
mlavallebecuase I also faced some weird stuff with multiple port binding14:58
rubasovmlavalle: so you're thinking the api-def is right as is14:58
mlavalleyes14:58
rubasovokay14:58
rubasovI can continue in that direction I just wasn't sure if that's the direction to take14:58
amotokiI think we need to check when member actions are registered.14:59
amotokiif they are specified when a resource is registered, it might not work.14:59
rubasovamotoki: they are, I think14:59
rubasovthat's why I had to add something to RESOURCE_ATTRIBUTE_MAP too15:00
mlavalleok, top of the hour15:00
rubasovthank you guys15:00
mlavallethanks for attending!15:00
ralonsohthanks15:00
bcafarelthanks!15:00
mlavalle#endmeeting15:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"15:00
openstackMeeting ended Tue Aug 27 15:00:50 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:00
amotokithanks15:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking/2019/networking.2019-08-27-14.00.html15:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking/2019/networking.2019-08-27-14.00.txt15:00
openstackLog:            http://eavesdrop.openstack.org/meetings/networking/2019/networking.2019-08-27-14.00.log.html15:00
lajoskatonabye15:00
davidshaThanks!15:00
ralonsoh#startmeeting neutron_qos15:01
openstackMeeting started Tue Aug 27 15:01:05 2019 UTC and is due to finish in 60 minutes.  The chair is ralonsoh. 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
ralonsohhello15:01
davidshao/15:01
ralonsohsame as previous meeting, there is no agenda today15:01
*** mlavalle has left #openstack-meeting15:01
ralonsohno bugs or rfe15:01
*** david-lyle has quit IRC15:01
ralonsohapart from15:01
ralonsoh#15:01
*** david-lyle has joined #openstack-meeting15:01
ralonsoh#link https://bugs.launchpad.net/neutron/+bug/147652715:02
openstackLaunchpad bug 1476527 in neutron "[RFE] Add common classifier resource" [Wishlist,Triaged] - Assigned to Igor D.C. (igordcard)15:02
*** sridharg has quit IRC15:02
ralonsohdavidsha, I've seen that you have uploaded the spec15:02
ralonsoh#link https://review.opendev.org/#/c/678865/1/specs/train/qos_classifier.rst15:02
ralonsohbut is not finished yet15:02
davidshaYup, it's very basic at the moment, I still need to do the Proposed solutions15:03
ralonsohone question (we have discussed this before)15:03
davidshashot15:03
ralonsohis neutron classifier going to be something depending on QoS? an extension to the extension?15:03
ralonsohor will it have it's own entity15:04
davidshaNo, I think there had been other RFEs for other services to use it, one was for Security Groups I think15:04
ralonsohof course, if you want to use dscp, you'll need qos15:04
ralonsohok15:04
*** jamesmcarthur has joined #openstack-meeting15:05
ralonsohbecause this is very QoS centric, just to make this visible in the spec15:05
ralonsohthat this is an independent extension15:05
davidshaYup, there are optional extensions and thats how I'm trying to implement the classifier, an optional extension to other extension.15:06
davidshaAck15:06
ralonsohso ping me once you have something to read there15:06
davidshaWill do!15:06
ralonsohdo you have any update on the POC? #link https://review.opendev.org/#/c/670050/15:06
davidshaYup, I'm going to redo the DB models to work closer to how you suggested, I think there might be some deviation though as I work, I'll comment as I go to explain why I changed things15:08
ralonsohperfect, thanks!15:09
davidshaI haven't pushed that yet, will try to get it up asap, after that I'll try porting all the tests.15:09
ralonsohthank you davidsha15:09
ralonsohany other update on this RFE?15:09
davidshaI have the DSCP patch rebased and it can be tested: https://review.opendev.org/#/c/636333/1415:10
davidshaI'm also considering adding another field to DSCP to mark what priority the rule should be compared to the other DSCP Rules, what are your thought?15:11
ralonsohbut first you should add the patch https://review.opendev.org/#/c/636333 to neutron15:12
ralonsohis that right?15:12
davidshaWell it would be adding a classification-groups-id field and a classification-priority field to the DSCP rule in this patch15:13
ralonsohright15:14
davidshaclassification-priority being an positive integer rangeing from 0-X15:14
ralonsohbut what does it means?15:14
ralonsohyou can have several rukles for the same traffic?15:15
ralonsohand then only the high prio one will be used?15:15
davidshaKinda, ya, if one classification is for traffic from a host and another is for traffic to tcp port 80 which would take priority if both conditions match15:15
ralonsohahhh ok,15:16
ralonsohthe rules can overlap15:16
davidshayup15:16
ralonsohso you propose to have a priority index in the qos dscp rule15:17
davidshaI know with openflow, it's not predicatble what will happen, when the traffic first hits the flow it will just use that for as long as the flow exists15:17
davidshayup15:17
*** mattw4 has joined #openstack-meeting15:17
ralonsohyes, I know OF is not deterministic on this15:17
ralonsohok, perfect for me15:18
ralonsohbtw, one question15:18
ralonsohshould not https://review.opendev.org/#/c/636333 be on top of https://review.opendev.org/#/c/670050/?15:18
davidshaIt is, isn't it? Or do you mean the patch number?15:19
davidshalike 636333 < 67005015:19
ralonsohnot the number, the git precedence15:19
ralonsohno no, the git tree15:20
davidshaYa the git tree shuld have 6333 on 05015:20
ralonsohok, just to make this clear15:21
ralonsohok, any other update?15:21
davidshaNope, I think thats all from me, Thanks!15:22
ralonsohthank you davidsha15:22
*** mattw4 has quit IRC15:22
ralonsohanything else? to those reading the meeting15:22
ralonsohthank you very much15:23
ralonsohsee you next meeting15:23
ralonsoh#endmeeting15:23
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"15:23
davidshaSee ya!15:23
ralonsohbye15:23
openstackMeeting ended Tue Aug 27 15:23:32 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:23
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_qos/2019/neutron_qos.2019-08-27-15.01.html15:23
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_qos/2019/neutron_qos.2019-08-27-15.01.txt15:23
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_qos/2019/neutron_qos.2019-08-27-15.01.log.html15:23
*** lajoskatona has left #openstack-meeting15:30
*** gyee has joined #openstack-meeting15:37
*** macz has joined #openstack-meeting15:42
*** boden has left #openstack-meeting15:45
*** brault has quit IRC15:50
*** e0ne has quit IRC15:52
*** brinzhang has quit IRC15:52
*** brinzhang has joined #openstack-meeting15:52
*** mlavalle has joined #openstack-meeting15:59
mlavalle#startmeeting neutron_ci16:00
openstackMeeting started Tue Aug 27 16:00:03 2019 UTC and is due to finish in 60 minutes.  The chair is mlavalle. 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
njohnstono/16:00
ralonsohhi16:01
bcafarelhi again16:02
mlavalleI am not slaweq so it will be hard to sub for him but I'll do my best16:02
mlavallePlease remember to open the grafana dashboard now: http://grafana.openstack.org/dashboard/db/neutron-failure-rate16:03
mlavalle#topic Actions from previous meetings16:03
*** openstack changes topic to "Actions from previous meetings (Meeting topic: neutron_ci)"16:03
mlavallealonsoh to review the CI (functional tests), search for error patterns and open bugs if needed16:03
mlavalleralonsoh: ^^^^16:03
ralonsohyes16:03
ralonsohI found this one16:04
ralonsoh#link https://review.opendev.org/#/c/67826216:04
ralonsohwell, this is the patch16:04
ralonsohand, btw, liuyulong found another error16:04
ralonsohI'm wroning on the patch right now16:04
ralonsohI'll push the second one after the meeting16:05
mlavallethanks for the update!16:05
ralonsohthat's all16:05
mlavallemlavalle will continue debugging router migration bug: https://bugs.launchpad.net/neutron/+bug/183844916:05
openstackLaunchpad bug 1838449 in neutron "Router migrations failing in the gate" [Medium,Confirmed] - Assigned to Miguel Lavalle (minsel)16:05
mlavalleI have continued working on this one. Here's the situation16:05
mlavalle1) Before staring the migration, the test sets the router's admin_state_up to false16:06
mlavalle2) Server is expected to set the routers ports to DOWN after that16:07
mlavalle3) Problem is that, in some cases, those ports are not set to DOWN16:07
mlavalle4) This is because one of the L3 agents involved is supposed not to get any routers here: https://github.com/openstack/neutron/blob/4f6b8bb3e55dfa564e87d90e4c1257d0153ef141/neutron/agent/l3/agent.py#L73016:08
mlavalleso the agent never removes the routers interfaces. I am investigating why the server is returning the router. I have his DNM patch: https://review.opendev.org/#/c/677098/16:09
mlavalleproblem is that so far, all the migrations have succeeded after my re-checks16:09
*** boxiang has quit IRC16:09
mlavalleso I'll keep pulling the thread16:10
mlavalleany questions?16:10
*** boxiang has joined #openstack-meeting16:10
*** jawad_axd has joined #openstack-meeting16:10
ralonsohmlavalle, can you guest why is this happening?16:10
ralonsohor what is generating this?16:10
mlavalleI am suspecting the "related routers" mechanism16:11
mlavalleand some sort of race condition16:11
ralonsohthanks!16:11
mlavallenjohnston to look at errors in the neutron-tempest-postgres-full periodic job16:12
njohnstonSo I need to get in touch with #openstack-infra about that16:12
njohnstonWith the move to Swift I don't know where the new log location is16:12
njohnstonBut if you look at the old location: http://logs.openstack.org/periodic/opendev.org/openstack/neutron/master/neutron-tempest-postgres-full/16:12
njohnstonyou can see that there was one successful run on 8/24, which is the only run registered since 8/1516:13
njohnstonSo I am guessing the issues can be found in the new log location16:13
mlavalleok16:13
mlavalleso to summarize:16:13
njohnstonSo I will send an email to the ML to see where the new location is, and continue16:13
mlavalle#action ralonsoh will continue working on error patterns and open bugs for functional tests16:14
ralonsohok16:14
mlavalle#action mlavalle will continue debugging https://bugs.launchpad.net/neutron/+bug/183844916:15
openstackLaunchpad bug 1838449 in neutron "Router migrations failing in the gate" [Medium,Confirmed] - Assigned to Miguel Lavalle (minsel)16:15
mlavalle#action njohnston will get the new location for periodic jobs logs16:15
mlavalleis that correct?16:16
ralonsohI think so16:16
mlavalleok16:17
mlavalle#topic Stadium projects16:17
*** openstack changes topic to "Stadium projects (Meeting topic: neutron_ci)"16:17
mlavalleFor Python 3 migration I think we had a good update during the Neutron meeting16:17
njohnstonWe covered the python 3 topic for stadium pretty well in the neutron team meeting earlier16:17
mlavallelajoskatona did progress on networking-odl last week. He needs help merging: https://review.opendev.org/#/q/status:open+project:openstack/networking-odl+branch:master+topic:use-latest-odl16:18
mlavallenetworking-bagpipe: merged releasenotes: https://review.opendev.org/#/c/677648/.16:18
mlavalledid I miss anything?16:18
mlavalleI'll take that as a no16:19
mlavallein regards to tempest-plugins migration16:19
mlavallelet's look at the etherpad16:19
mlavallehttps://etherpad.openstack.org/p/neutron_stadium_move_to_tempest_plugin_repo16:20
njohnstonwe were able to mark fwaas done last week thanks to slawek16:20
mlavalleyeap16:20
mlavalleand neutron-dynamic-routing and neutron-vpnaas are still in progress16:21
mlavalleI will work on vpnaas this week16:21
mlavalletidwellr is working on dynamic routing16:21
mlavalleok, let's look at:16:22
mlavalle#topic Grafana16:22
*** openstack changes topic to "Grafana (Meeting topic: neutron_ci)"16:22
*** jamesmcarthur has quit IRC16:22
*** david-lyle is now known as dklyle16:23
mlavallewell, we had a peak yesterday in tempest and grenade16:24
mlavallebut things seem to be getting back to normal16:24
mlavalleany observations?16:25
njohnstoneither something was broken and got fixed, or the 4 runs were all just for the same broken job16:25
mlavalleyeap16:25
njohnstonThe openstack-tox-docs jobs look high, peaking at 20%, but based on the volume of jobs that's only 2 or 3 failures - which is not really much at all.  I think that same story applies for most of the the other panels in the check queue.16:25
bcafarelyes recent runs look good for tempest/grenade16:25
bcafareland docs job may be amotoki's series of pdf docs reviews16:26
mlavallethat's true16:26
njohnstonI am worried about data loss for the gate queue, I know I have seen more things merge than the quantitative graphs would have us believe16:27
*** jamesmcarthur has joined #openstack-meeting16:27
njohnstondata loss as in Grafana/elasticsearch data loss16:27
mlavalleshould we take this as a warning and watch this week?16:27
clarkbelasticsearch is a best effort due to sheer volume of data16:28
clarkbgrafana should be fairly accurate though16:28
mlavalleor should we do something more urgent?16:28
clarkbalso we had a gap in elasticsearch after the switch to swift hosted logs, we've since plugged it but there is a hole there16:28
njohnstonthe only thing that suffers is the utility of grafana, so it's only as big a deal as we deem it to be.  I think let's just check for a week, and if we can show that we're losing significant amounts of job results then we look to infra.  But better to have facts instead of suppositions and suspicions.16:29
mlavallefair enough16:29
mlavalleok, let's move on then16:30
mlavalle#topic fullstack/functional16:30
*** openstack changes topic to "fullstack/functional (Meeting topic: neutron_ci)"16:30
amotokiregarding openstack-tox-docs failure, I am not sure it is really triggered by pdf docs reviews, but we use neutron review to check the infra job review. let's see what happens next week.16:30
mlavalleI found this https://storage.bhs1.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/logs_21/678021/4/check/neutron-functional/7e999b2/testr_results.html.gz16:31
mlavallenjohnston: this is what you were talking about during the Neutron meeting, right njohnston?16:31
*** slaweq has joined #openstack-meeting16:32
njohnstonhmm, did I mention that?  My mind is blanking.16:32
*** liuyulong has quit IRC16:33
mlavalleyou didn't mention this failure16:33
mlavallebut you mentioned the sighup stuff for oslo16:33
bcafarelis that oslo issue a recent one?16:34
njohnstonAh, yes!  I'm not sure hopw oslo.service works for functional tests, but it might be at fault.16:34
njohnstonI don't have a precise answer as far as when the oslo issue started, but my impression is that it has been happening for some time.16:35
mlavalleok, you wanted to make sure it's the same stuff16:35
bcafarelack that was my general impression too16:35
mlavalleok, let's move on16:36
mlavalle#topic Open discussion16:36
*** openstack changes topic to "Open discussion (Meeting topic: neutron_ci)"16:36
mlavalleanything else we should discuss today?16:36
njohnstonI got an email back about the periodic jobs location - thanks clarkb16:38
njohnstonand looking at it, it looks like it is a sqlalchemy error on glance db migrations16:38
njohnstonhttp://paste.openstack.org/show/765665/16:39
bcafarelso one action point (periodic jobs logs location) already down :)16:39
njohnstonso I will raise that with the glance folks16:39
njohnstonand possibly zzzeek16:39
mlavalleok, thanks16:40
mlavallethanks for attending16:40
mlavalle#endmeeting16:40
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"16:40
openstackMeeting ended Tue Aug 27 16:40:27 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:40
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_ci/2019/neutron_ci.2019-08-27-16.00.html16:40
ralonsohbye16:40
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_ci/2019/neutron_ci.2019-08-27-16.00.txt16:40
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_ci/2019/neutron_ci.2019-08-27-16.00.log.html16:40
mlavalleo/16:40
njohnstono/16:40
bcafarelo/16:40
*** mlavalle has left #openstack-meeting16:41
*** amotoki is now known as amotoki_16:42
*** efried has left #openstack-meeting16:46
*** jamesmcarthur has quit IRC16:47
*** ekcs has quit IRC16:50
*** psachin has joined #openstack-meeting16:53
*** armax has quit IRC16:56
*** davidsha has quit IRC16:58
*** e0ne has joined #openstack-meeting17:01
*** diablo_rojo has joined #openstack-meeting17:02
*** jawad_axd has quit IRC17:03
*** brault has joined #openstack-meeting17:23
*** slaweq has quit IRC17:27
*** jamesmcarthur has joined #openstack-meeting17:27
*** slaweq has joined #openstack-meeting17:28
*** psachin has quit IRC17:29
*** tesseract has quit IRC17:30
*** psachin has joined #openstack-meeting17:33
*** slaweq has quit IRC17:33
*** ekcs has joined #openstack-meeting17:34
*** bbowen has quit IRC17:37
*** bbowen has joined #openstack-meeting17:37
*** ralonsoh has quit IRC17:38
*** psachin has quit IRC17:45
*** hemna has quit IRC17:47
*** e0ne has quit IRC17:49
*** jamesmcarthur has quit IRC17:52
*** eharney has quit IRC17:54
*** diablo_rojo has quit IRC18:03
*** hyunsikyang has joined #openstack-meeting18:34
*** hyunsikyang__ has quit IRC18:36
*** Shrews has joined #openstack-meeting18:49
*** armax has joined #openstack-meeting18:51
*** e0ne has joined #openstack-meeting18:51
*** bobh has joined #openstack-meeting18:52
*** bobh has quit IRC18:57
clarkbanyone else here for the infra team meeting? we'll get started shortly18:59
fungiyeah, may as well18:59
fungi;)18:59
*** eharney has joined #openstack-meeting19:00
ianwo/19:01
clarkb#startmeeting19:01
openstackclarkb: Error: A meeting name is required, e.g., '#startmeeting Marketing Committee'19:01
Shrewsneat19:01
clarkbI expect it will be quite a quiet meeting today with cmurphy|afk corvus and mordred all doing travel of different sorts19:01
clarkb#startmeeting infra19:01
openstackMeeting started Tue Aug 27 19:01:41 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-August/006458.html Our Agenda19:01
clarkbthe bot is super helpful19:02
clarkb#topic Announcements19:02
*** openstack changes topic to "Announcements (Meeting topic: infra)"19:02
fungiif only it could read your mind19:02
clarkbOpenStack election season is upon us19:02
clarkbfungi has mentioned he will be busy helping there quite a bit this time around19:02
clarkbalso now is your chance to run for PTL of $project or TC if you would like to19:02
clarkbI think nominations open sometime today?19:03
fungi(or just run screaming?)19:03
*** jamesmcarthur has joined #openstack-meeting19:03
fungiyeah, in another 4 hours and change19:03
fungi#link https://governance.openstack.org/election/19:03
clarkbAlso this weekend is a long one for many of us (I'll not be around Friday though may actually work the holiday itself to make up for Friday)19:04
fungithough folks are welcome to push up nominations ahead of time, the officials just won't confirm them before the start of the official nomination period19:04
clarkbfungi: gotcha19:04
fungiyeah, i've been informed that this weekend is when i'll be getting all sorts of construction projects done around the house19:04
fungiso i don't expect to be on hand much19:04
clarkbwe have family/friends in town so are doign things with them19:05
clarkb#topic Actions from last meeting19:05
*** openstack changes topic to "Actions from last meeting (Meeting topic: infra)"19:05
clarkb#link http://eavesdrop.openstack.org/meetings/infra/2019/infra.2019-08-20-19.01.txt minutes from last meeting19:05
clarkbianw did do an audit of the static server which is an agenda item further on in the agenda19:05
clarkblets keep moving and we'll talk about it there instaed19:05
fungithanks ianw!19:06
clarkb#topic Priority Efforts19:06
*** openstack changes topic to "Priority Efforts (Meeting topic: infra)"19:06
clarkb#topic Update Config Management19:06
*** openstack changes topic to "Update Config Management (Meeting topic: infra)"19:06
clarkbAnything to add under this topic? I've been distracted by other things the last week or so and haven't noticed much from others19:06
*** markvoelker has quit IRC19:07
fungii think focus has been elsewhere19:07
clarkb#topic OpenDev19:08
*** openstack changes topic to "OpenDev (Meeting topic: infra)"19:08
clarkbSimilar to config management updates I think things have gotten quiet here too. I'ev not had time to reload my golang stuff into memory to run tests on my fix for that or file the bug I talked about last week19:08
*** markvoelker has joined #openstack-meeting19:08
clarkbI suppose I should just go ahead and file the bug/do a PR19:08
fungithe updates to publication jobs are sort of on topic here19:09
clarkbajaeger's updates to use the promote pipeline?19:09
fungibut again probably better covered under the separate topic entry19:09
fungiyeah, they're somewhat intertwined with ianw's review of static hosting as well19:09
clarkbgotcha19:10
clarkbWe'll keep moving then19:10
clarkb#topic Storyboard19:10
*** openstack changes topic to "Storyboard (Meeting topic: infra)"19:10
fungii was able to work out how to reenable slow query logging19:10
fungiand how to use the pt-query-digest tool corvus and mordred found19:11
fungiand so i have an updated analysis, i'm just now fiddling with a local openafs issue so i can post the results somewhere consumable19:11
clarkbexcellent news.19:12
* SotK looks forward to seeing it, thanks19:12
clarkbfwiw I almost always have local afs issues because tumbleweed and usually just use one of the fileservers directly19:12
clarkbthe in kernel openafs stuff that ianw has been helping along should help my install quite a bit though19:12
fungii almost never have afs trouble, but for some reason today i'm getting connection timeouts on operations19:13
clarkb#topic General Topics19:14
*** openstack changes topic to "General Topics (Meeting topic: infra)"19:14
clarkbFirst up is server upgrade progress19:14
clarkb#link https://etherpad.openstack.org/p/201808-infra-server-upgrades-and-cleanup19:14
fungiaha, and afs fixed after an lkm reload and a client service restart'19:14
clarkbfungi: the next step with wiki-dev is to redeploy it with the split out static content and the bumped release version?19:14
fungishouldn't have been a need to redeploy since the static content was never there19:15
clarkbwhat about the upgrade? I guess that just updates the git checkout and submodules?19:15
fungibut i've now overwritten the wiki-dev trove db contents with the most recent mysqldump from the production server19:15
fungiand copied in a tarball of the images tree from production to the new cinder volume on wiki-dev19:15
fungiand yeah, a redeploy might not hurt, or i can just blow away /srv/mediawiki and let puppet put it back again to be sure19:16
fungiwas going to do that next because content currently isn't loading19:16
clarkbit seems the server is serving a blank page currently?19:16
clarkbya19:16
fungiafter that, i'll be diffing the production Settings.php (mediawiki's primary config file) against the templated one puppet is installing on wiki-dev19:17
fungiand coming up with a patch to update it accordingly19:17
clarkbsounds good thanks19:17
fungioh, also the old wiki-dev server has been deleted, since there's nothing of value on it anyway19:18
fungiand on the new server the only state is being stored in trove and cinder now19:18
*** e0ne has quit IRC19:19
clarkbwhereas before it was the root disk and trove right? that should simplify future replacements to have the static resources on cinder19:19
fungiyeah19:19
fungithough we might want to look soon at moving the db to a local mysql and out of trove19:19
fungibut that's less critical19:19
fungifirst i want to get a working wiki deployed from puppet-mediawiki and then blow away the old production server and replace it19:19
fungiand then we no longer have that liability hanging over us19:19
clarkb++19:20
fungiafter that we can look at further upgrades19:20
clarkbNext up is ianw's audit of static.o.o services (which ties into server upgrades because static needs upgarding or replacing)19:20
clarkb#link https://etherpad.openstack.org/p/static-services service audit19:20
clarkbianw: it sounds like you want to try using haproxy as a light weight http redirector19:21
ianwso yeah, last week was an action item to look into what to do19:21
fungifwiw, we have redirect sites hosted on files.o.o already19:21
ianwthat was one thought, to get the legacy redirects it currently does off it19:21
clarkb#link https://review.opendev.org/#/c/677903/ Generic HaProxy ansible configs19:22
clarkb#link https://review.opendev.org/678159 Service load balancer/redirector19:22
ianwand also to provide another load-balancer we could expand a bit but that doesn't overlap with gitea19:22
clarkbare the changes related to that19:22
fungicurious why haproxy is preferred over the ones we're already serving with apache19:22
ianwfungi: well, i'm just thinking that the future isn't static servers setup with apache19:23
fungiinstead it's... static servers set up with haproxy? ;)19:23
ianwwell it's containerised haproxy, so sort of one step above that :)19:23
clarkbianw what do you think we should do with the sites that are more than redirects?19:24
fungigot it. does containerizing haproxy have any benefits over just installing the packaged haproxy?19:24
clarkbor feel free to say you don't have an opinion on that yet :)19:24
clarkbfungi: its currently the only way we are deploying it so consistency I would guess19:24
ianwthat's the other question; is there are reason the other sites can't use afs based publishing?19:24
fungiclarkb: what's currently the only way we are deploying?19:25
clarkbfungi: haproxy in container deployed with docker-compose19:25
clarkbfungi: we don't deploy haproxy from packages19:25
fungiianw: i had always assumed we were moving them all to afs and making them vhosts on files.o.o19:25
fungijust hadn't found time to do that yet19:25
fungiclarkb: oh, i get you19:25
fungihaproxy specifically19:26
ianwok, so if it's just "haven't found time" v "can't be done" that's good19:26
clarkbya I think moving to afs volumes is likely a reasonable long term strategy. Before that happens we may want to sort out some of the vos release problems we've had recently though?19:26
clarkbalso I think the xenial to bionic upgrade for the fileservers will require outages because we can't mix the versions of afs on the fileservers like that?19:26
clarkbwhich is a risk/downside but not a reason to avoid it19:26
fungiianw: the tricky bits are likely going to be tarballs (if we want to roll it into the new tarballs.opendev.org volume, because of a slightly different layout lacking prefix namespacing) and governance (because it will need something akin to the root-marker setup we use to keep documentation subtrees from wiping each other)19:27
ianwso, i think this is probably all pointing towards "static.o.o" is not upgraded, but retired19:27
fungiright, i would much prefer the outcome where static.o.o is simply no longer in use and we deleet it19:28
fungiextra effort to upgrade it seems like a waste19:28
clarkbok sounds like two next steps can be "move redirect hosting of current static.o.o redirects" and "move one vhost with files from static.o.o to afs" then "move the other vhosts to afs"19:29
clarkbwith the goal of simply deleting static.o.o in the nearish future19:29
ianwyeah, i mean if people wish to put names against parts of https://etherpad.openstack.org/p/static-services ...?19:30
clarkbianw: maybe we can put a TODO list at the bottom that distills the info above?19:30
clarkbbut then ya we can start grabbing work off that TODO list when it is there19:30
ianwsure19:31
clarkbthanks!19:31
ianwwe can think about the generic load balancer (with redirects) into the future ... i'm not tied to it19:31
fungiif we're going with the plan of doing redirects with haproxy instead of apache, then we probably need to include in that a plan to move our other redirects to the same new solution for consistency19:31
fungii don't personally see the benefit, but will admit i haven't looked super closely at the proposed change yet19:32
clarkbya I think to start reusing the redirects on files.o.o is likely the simplest thing19:32
clarkbbut like fungi I should review the changes before committing to that :)19:32
fungiif the implementation of doing redirects in haproxy is simpler and cleaner then i could be convinced, surely19:32
ianwfungi: that is one nice thing, it's all just in one config file19:32
ianwrather than split into vhosts19:32
fungiwell, apache could be done that way too if we wanted19:33
ianwi think it makes most sense if it was also a front-end doing some other lb tasks for other services too19:33
fungione vhost with all the redirect names as aliases, and then individual redirect rule groups for eth various targets19:33
clarkbfungi: how does that work with ssl?19:33
clarkbwould that force us to use multiname certs?19:34
funginope, could just use sni19:34
ianwnone of the ones on static.o.o have provided ssl anyway, which simplifies things a bit19:34
fungiwe do that on it already in fact19:34
clarkbianw: oh that is good to know thanks19:34
clarkbfungi: right but isn't a cert usually mapped to a single vhost?19:35
clarkb(I'm not sure how to use multiple certs in one vhost for different names)19:35
fungioh, good question, i'd have to double-check what the options are there19:35
clarkbsounds like it is a non issue in this case thankfully19:35
fungiwell, a non-issue at the moment, but if we want to start redirecting more openstack.org sites to opendev.org in the future it could become relevant19:36
clarkbya19:36
clarkbbut we can also sort that out outside the meeting19:36
clarkblets note that as a potential item to solve for any redirecting setup and mvoe on19:36
*** artom has quit IRC19:36
fungianyway, i agree that we should consider changes in how we host site redirects as a separate effort from moving stuff off static.o.o so it's not a blocker19:36
clarkbNext up is Fedora's mirror vos release struggles19:37
clarkb#link http://eavesdrop.openstack.org/irclogs/%23openstack-infra/%23openstack-infra.2019-08-26.log.html#t2019-08-26T07:25:1619:37
ianwyeah, right now it's releasing again ... it seems to finish but something is wrong with it taking this long19:38
clarkbianw: I like the idea of improving our debugging. We might also be able to tcpdump those transfers (though that may produce way too much data?)19:38
fungiworst case, can we mirror into a new volume and then dump the old one?19:39
ianwaudit logging might be the next step; see19:39
ianw#link https://review.opendev.org/#/c/672847/19:39
ianwalthough, !0 chance restarting the servers might just fix things mysteriously too19:39
fungibut yeah. knowing *why* it's doing this would be good19:39
fungisince if it's happened once it could quite possibly happen again19:39
clarkbianw: magic19:39
ianw#link https://review.opendev.org/#/c/678717/19:39
clarkbfungi: it has happened several timse now so I expect it will keep happening19:39
ianwupdates the logging to have more timestamps19:40
fungi"has happened several time" that vos release is slow, or that we've made the problem go away and then it's come back19:40
ianwespecially timestamping logs of vos release might be useful when correlating across audit logs19:40
clarkbgreat I'll do my best to review those quickly19:40
fungiand for different volumes or just this one?19:40
ianwthe vos release slow is new i think19:40
ianwit just not working in various ways is not :)19:40
clarkbfungi: many of them were sad at the end of july but this is the only one that has been persistent about it19:41
clarkbfungi: epel, suse, fedora, and I think somethign else all went out to lunch ~july 2619:41
clarkbthen ianw and I fixed them a coupel weeks ago and fedora is theo nly one that continues to struggle aiui19:41
clarkbthis seems like a reasonable path forward (more debugging info) and lets see what we catch19:42
ianwi think that's right, given opensuse seems to be upstream issues19:42
*** artom has joined #openstack-meeting19:43
clarkbWe have ~2 topics left lets keep moving. But please do review those two changes when you get a chance infra-root19:43
clarkbNext up is Kayobe needs an opendev.org project rename to be included in the openstack train release?19:43
clarkbI feel like we might be conflating two different things there19:44
clarkbfungi: ttx ^ can you expand on that from the TC perspective?19:44
fungiyes, kayobe is currently not in the openstack namespace19:45
clarkbThe two things are "where the project is hosted" and "is this project considered openstack by the TC"19:45
clarkbin the past the openstack TC has considered things outside of the openstack namespace to be openstack19:45
fungii gather the openstack release team isn't comfortable doing release management on kayobe until it's renamed19:45
fungiinto the openstack namespace19:45
clarkband we've done our best to reconcile the hosting name delta when it makes sense19:45
clarkb(aka when we can take a gerrit downtime)19:46
clarkbfungi: ok this is just news to me that we are conflating the two because my memory says we've never done that before19:46
clarkbinstead we've just done our best to be eventually consistent19:46
fungii thought we were just going to discuss scheduling the next rename, but i can dig into the details from the release team's perspective and find out if it is related to their automating and tooling needing fixes to deal with projects in the x namespace19:47
fungithough they released things in the openstack-dev (and maybe openstack-infra) namespaces so i would be surprised if that's the case19:48
clarkbya the struggle is getting it down early enough if that is indeed a requirement for them19:48
clarkbwith all the other end of cycle stuff going on we've typcially not done renames until early the next cycle19:48
clarkbhowever we could probably make it work R-4?19:49
clarkbthat looks like a quiet week19:49
clarkband is pre RC1 deadline19:49
clarkbWould have to be early that week for me as I'm traveling at the end of that week19:49
clarkbmaybe we pencil in September 16 and run that by the release team?19:49
fungiyeah, no mention of "kayobe" in the last release team meeting logs19:50
* mordred waves to clarkb19:50
* mordred apologizes for tardiness19:50
fungithe only mention of them in #openstack-release was on august 119:50
clarkbin that case maybe that is our best option, aim for the 16th and bring that up with the release team to see if that works for them19:51
clarkbmordred: ^ does the 16th work for you to do project renames?19:51
clarkbmordred: might be good to have you and/or corvus around due to the relatively recently chagnes to gitea management19:51
fungiaha, seems to be related to this:19:52
mordredclarkb: I will be back from vacation on the 16th - although I'll be in EU timezone19:52
fungi#link https://review.opendev.org/673234 Add deliverable file for Kayobe19:52
mordredso - yes - pending hour of day19:52
clarkbmordred: early morning is probably best anyway since it is early week (getting done sooner is better)19:52
mordred(speaking of - I'm on vacation 31/8-14/9)19:52
fungiokay, so if we don't rename first, then the deliverable name will have to change in releases after the rename19:52
clarkbI mean my early morning19:52
mordredclarkb: woot19:52
mordredclarkb: yeah - your early morning will work great for me19:53
* mordred enjoys ambushing clarkb with tons of things in his early morning19:53
fungialso it's going to be a pain for upcoming election work because governance now refers to a repositories which do not exist19:53
clarkbfungi: well the change ahsn't merged right? so no reference yet?19:53
clarkboh wait governance not releases19:53
clarkbgot it19:53
clarkbfungi: the 16th is after polling begins19:54
clarkbfungi: so your voter rolls should be complete by then19:54
clarkbhopefully thatsimplifies things?19:54
clarkbif goverance says openstack/kayobe then that seems buggy fwiw19:55
clarkbshould say x/kayobe then update after we rename19:55
fungiclarkb: that change isn't what matters19:55
fungi#link https://review.opendev.org/669299 Add kayobe as a kolla deliverable19:55
fungithat added nonexistent deliverable repos to openstack governance19:56
clarkbthose repos do exist19:56
funginow i likely need to get the tc to rush through an un-renaming of those in governance19:56
fungioh, nevermind19:56
clarkbI think if we do the reanme on the 16th that solves the election problem19:56
fungii mistakenly thought they'd been added with the openstack namespace19:56
clarkbbut I don't know if it solves any releases problems19:56
fungiso yes, elections will be fine19:57
* fungi sighs19:57
fungithis is all stuff i should have thought to research before the meeting, sorry19:57
clarkbLets aim for the 16th and bring that up with the release team19:57
clarkb#topic Open Discussion19:57
*** openstack changes topic to "Open Discussion (Meeting topic: infra)"19:57
clarkband now we have ~2.5 minutes for any other topics19:57
clarkbI will be venturing into the city to take photos for a visa I need to apply for today. I'll be AFK for however long that takes19:58
clarkbthen back again to review teh changes ianw pointed out earlier that need review19:58
mordredclarkb: have fun with that!19:58
ianwone quick note on pbx.openstack.org ... i noticed yesterday it was dead (looking at cacti)19:58
ianwit was under a huge pbx spam attack that flooded the logs i think19:58
clarkbAlso be aware that tehre is a zuul bug that can cause zuul to test the wrong commit under special circumstances. Fixed here https://review.opendev.org/#/c/678895/319:59
ianwthis is a thing ... http://www.voipbl.org/ is all about mitigating it a bit19:59
clarkbI don't think the risk for that is super high right now but will be as soon as openstack starts branching stable/train19:59
clarkbianw: of course there is a voip pbl :)19:59
ianwout of interest i installed their rules, but then realised it's 85,000+ iptables blocks19:59
clarkbianw: is it pretty simple to add that to asterisk?19:59
clarkband we are at time. Thanks everyone20:00
clarkb#endmeeting20:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"20:00
openstackMeeting ended Tue Aug 27 20:00:19 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/infra/2019/infra.2019-08-27-19.01.html20:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/infra/2019/infra.2019-08-27-19.01.txt20:00
openstackLog:            http://eavesdrop.openstack.org/meetings/infra/2019/infra.2019-08-27-19.01.log.html20:00
clarkbfeel free to continue any topic of conversation from here over in #openstack-infra20:00
*** Shrews has left #openstack-meeting20:00
*** jraju__ has quit IRC20:10
*** bbowen has quit IRC20:15
*** ijw has joined #openstack-meeting20:19
*** artom has quit IRC20:23
*** artom has joined #openstack-meeting20:25
*** tidwellr has joined #openstack-meeting20:42
*** jamesmcarthur has quit IRC20:46
*** brault has quit IRC20:48
*** lpetrut has joined #openstack-meeting20:50
*** lpetrut has quit IRC20:51
*** lpetrut has joined #openstack-meeting20:51
*** ijw has quit IRC20:57
*** lpetrut has quit IRC20:58
*** ijw has joined #openstack-meeting20:59
*** ijw has quit IRC21:03
*** markvoelker has quit IRC21:19
*** bbowen has joined #openstack-meeting21:24
*** ijw has joined #openstack-meeting21:34
*** ijw has quit IRC21:37
*** ijw has joined #openstack-meeting21:37
*** baojg has quit IRC21:47
*** baojg has joined #openstack-meeting21:47
*** mriedem has quit IRC21:48
*** ykatabam has joined #openstack-meeting21:56
*** trident has quit IRC22:05
*** enriquetaso has joined #openstack-meeting22:10
*** tidwellr has quit IRC22:13
*** trident has joined #openstack-meeting22:13
*** rcernin has joined #openstack-meeting22:15
*** markvoelker has joined #openstack-meeting22:15
*** markvoelker has quit IRC22:20
*** brault has joined #openstack-meeting22:49
*** armax has quit IRC22:51
*** brault has quit IRC22:53
*** carloss has quit IRC23:06
*** markvoelker has joined #openstack-meeting23:15
*** markvoelker has quit IRC23:20
*** macz has quit IRC23:36
*** markvoelker has joined #openstack-meeting23:55

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