Tuesday, 2019-09-10

*** ociuhandu has joined #openstack-meeting00:10
*** ociuhandu has quit IRC00:15
*** mattw4 has quit IRC00:23
*** macz has quit IRC00:39
*** gyee has quit IRC00:42
*** markvoelker has joined #openstack-meeting00:46
*** markvoelker has quit IRC00:48
*** markvoelker has joined #openstack-meeting00:49
*** diablo_rojo has quit IRC00:57
*** markvoelker has quit IRC00:59
*** markvoelker has joined #openstack-meeting00:59
*** markvoelker has quit IRC01:04
*** markvoelker has joined #openstack-meeting01:07
*** senrique_ has joined #openstack-meeting01:14
*** yamamoto has joined #openstack-meeting01:15
*** markvoelker has quit IRC01:17
*** markvoelker has joined #openstack-meeting01:18
*** bobh has joined #openstack-meeting01:19
*** njohnston_ has quit IRC01:20
*** markvoelker has quit IRC01:23
*** hongbin has joined #openstack-meeting01:35
*** rfolco has quit IRC01:41
*** mhen has quit IRC01:43
*** markvoelker has joined #openstack-meeting01:48
*** jamesmcarthur has joined #openstack-meeting01:48
*** senrique_ has quit IRC02:01
*** baojg has joined #openstack-meeting02:02
*** apetrich has quit IRC02:10
*** yamamoto has quit IRC02:19
*** markvoelker has quit IRC02:20
*** markvoelker has joined #openstack-meeting02:22
*** bobh has quit IRC02:23
*** lseki has quit IRC02:28
*** jamesmcarthur has quit IRC02:30
*** larainema has joined #openstack-meeting02:33
*** macz has joined #openstack-meeting02:36
*** rbudden has joined #openstack-meeting02:36
*** macz has quit IRC02:41
*** yamamoto has joined #openstack-meeting03:03
*** igordc has quit IRC03:31
*** armax has quit IRC03:41
*** hongbin has quit IRC03:46
*** ykatabam has joined #openstack-meeting03:49
*** tpatil has joined #openstack-meeting03:56
*** shilpasd has joined #openstack-meeting03:56
samP#startmeeting masakari04:01
openstackMeeting started Tue Sep 10 04:01:29 2019 UTC and is due to finish in 60 minutes.  The chair is samP. Information about MeetBot at http://wiki.debian.org/MeetBot.04:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.04:01
*** openstack changes topic to " (Meeting topic: masakari)"04:01
openstackThe meeting name has been set to 'masakari'04:01
samPHi all for masakari04:01
tpatilHi04:01
shilpasdHi all04:01
samPtpatil: Hi04:01
samPshilpasd: Hi04:01
samP#topic Critical bugs and patches04:02
*** openstack changes topic to "Critical bugs and patches (Meeting topic: masakari)"04:02
samPAny critical bugs or patches need to discuss here?04:02
shilpasdobserved zuul failure because of novaclient.exceptions.EndpointNotFound removal04:03
shilpasdon patch https://review.opendev.org/#/c/673526/04:03
shilpasdthis patch is for https://bugs.launchpad.net/horizon/+bug/183841704:04
openstackLaunchpad bug 1838417 in masakari "Notification related functional tests fails randomly due to KeyError" [Undecided,In progress] - Assigned to Shilpa Devharakar (shilpasd)04:04
shilpasdobserved masakri refers novaclient version 9.1.0 and we have 15.0.0 running as latest04:05
*** nitinuikey has joined #openstack-meeting04:05
tpatilin requirements.txt, novaclient >=9.1.004:06
samPshilpasd: that novaclient version 9.1.0 is set as a requirement for masakari?04:06
samPtpatil: thanks04:06
tpatilso the question is do we need to upgrade the novaclient lower_constraints to 15.0.004:08
shilpasdtpatil: thanks04:08
tpatillooking at the code, there is no need to do that as it will always install the newer version 15.0.0 and even if 9.1.0 is installed, it won't cause issue as we are now using NotFound exception instead of EndpointNotFound04:09
tpatilNotFound exception is present in 9.1.004:09
samPtpatil: got it. then no problem.04:11
tpatilsamP: OK, thanks04:11
tpatilNew bug : https://bugs.launchpad.net/masakari/+bug/184303504:11
openstackLaunchpad bug 1843035 in masakari "masakari sets node as "under maintenance" and does not evacuate" [Undecided,New]04:11
samPtpatil: thanks. I wanted to bring this up04:11
samPtpatil: can you please reproduce this issue?04:13
tpatilfirst let me understand the steps04:14
tpatilafter nova-compute service and pacemaker remote is restarted, the processes are kill using -904:15
tpatilwhen the node comes up again, means user is reboot the compute node?04:15
tpatils/reboot/rebooting04:15
tpatilI have posted this comment on the LP bug04:17
samPit seems like user/operator bring it up manually04:18
samPand, I can not access to the log files links in the LP bug04:19
tpatiland after that, operator will set on_maintenance flag to False04:19
tpatilIf the on_maintenance flag is set to True, then evacuated won't be performed.04:20
tpatilbecoz of HostOnMaintenanceError04:21
tpatilwe have added this business rule04:21
samPtpatil: correct.04:22
tpatiland I think same error masakarihostmonitor must be logging as well as it's not able to send the notification successfully.04:22
samPtpatil: why masakarihostmonitor?04:23
samPyou mean the masakarihostmonitor process in the on_maintenance node?04:24
tpatilfor this bug, I think bug reporter is imitating the scenario but in real case, hostmonitor will log this error from another compute node04:25
tpatilit all depends on pacemaker cluster node status04:26
*** rbudden has quit IRC04:27
*** rbudden has joined #openstack-meeting04:27
*** rbudden has joined #openstack-meeting04:27
*** rbudden has joined #openstack-meeting04:28
samPAnyway, not evacuating in the on-maintenance mode it not a bug. That is how it works.04:29
*** ykatabam has quit IRC04:29
*** rbudden has quit IRC04:29
tpatilCorrect04:29
samPThe question is whether repoter wants to change it or not.04:29
tpatilI also want to check the masakari logs04:30
samPProblem is, we don't have access to those04:30
*** ociuhandu has joined #openstack-meeting04:30
*** ykatabam has joined #openstack-meeting04:31
samPI left a comment for that04:32
tpatilok, thanks04:32
*** ociuhandu has quit IRC04:34
samPAny other issues?04:35
tpatilNo04:35
samPthanks04:36
samP#topic Train work items04:36
*** openstack changes topic to "Train work items (Meeting topic: masakari)"04:36
samPplease share if you hae any update on train work items04:36
*** Luzi has joined #openstack-meeting04:36
*** macz has joined #openstack-meeting04:37
shilpasdregarding masakari documentation, internal review implementation is in progress, will upload patch to community gerrit today04:37
samPshilpasd: thanks04:37
tpatilshilpasd: what about masakarimonitors?04:38
shilpasdwill try to upload for monitors by tomorrow04:39
shilpasdto community gerrit04:39
tpatilshilpasd: Ok, Thanks04:40
*** macz has quit IRC04:41
samPshilpasd: tpatil: thanks04:43
*** igordc has joined #openstack-meeting04:44
samPAny other updates?04:44
samPif not we could finish todays's meeting04:44
tpatilNo other updates from my side04:45
samPtpatil: Thanks04:45
samPOK then, let's finish today's meeting.04:45
shilpasdthanks all04:45
samPThanks all04:45
samP#endmeeting04:46
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"04:46
openstackMeeting ended Tue Sep 10 04:46:10 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)04:46
openstackMinutes:        http://eavesdrop.openstack.org/meetings/masakari/2019/masakari.2019-09-10-04.01.html04:46
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/masakari/2019/masakari.2019-09-10-04.01.txt04:46
openstackLog:            http://eavesdrop.openstack.org/meetings/masakari/2019/masakari.2019-09-10-04.01.log.html04:46
*** tpatil has quit IRC04:47
*** markvoelker has quit IRC04:48
*** shilpasd has quit IRC04:59
*** ricolin has joined #openstack-meeting05:00
*** dkushwaha has joined #openstack-meeting05:04
*** markvoelker has joined #openstack-meeting05:26
*** markvoelker has quit IRC05:30
*** ralonsoh has joined #openstack-meeting05:38
*** pots has quit IRC05:42
*** links has joined #openstack-meeting05:47
*** browny has joined #openstack-meeting06:03
*** shubham_potale has joined #openstack-meeting06:12
*** nitinuikey has quit IRC06:14
*** dklyle has quit IRC06:20
*** dklyle has joined #openstack-meeting06:21
*** kopecmartin|off is now known as kopecmartin06:26
*** jawad_axd has joined #openstack-meeting06:29
*** slaweq has joined #openstack-meeting06:41
*** shubham_potale has quit IRC06:48
*** shubham_potale has joined #openstack-meeting06:55
*** igordc has quit IRC07:00
*** tesseract has joined #openstack-meeting07:05
*** ykatabam has quit IRC07:05
*** ykatabam has joined #openstack-meeting07:06
*** ykatabam has quit IRC07:06
*** rcernin has quit IRC07:09
*** ociuhandu has joined #openstack-meeting07:14
*** ociuhandu has quit IRC07:21
*** yamamoto has quit IRC07:22
*** apetrich has joined #openstack-meeting07:24
*** yamamoto has joined #openstack-meeting07:30
*** tssurya has joined #openstack-meeting07:31
*** keiko-k has joined #openstack-meeting07:33
*** yamamoto has quit IRC07:34
*** apetrich has quit IRC07:39
*** macz has joined #openstack-meeting07:39
*** apetrich has joined #openstack-meeting07:40
*** tpatil has joined #openstack-meeting07:42
*** macz has quit IRC07:43
*** apetrich has quit IRC07:45
*** trident has quit IRC07:50
*** apetrich has joined #openstack-meeting07:52
*** lpetrut has joined #openstack-meeting07:55
*** trident has joined #openstack-meeting08:01
dkushwaha#startmeeting tacker08:02
openstackMeeting started Tue Sep 10 08:02:43 2019 UTC and is due to finish in 60 minutes.  The chair is dkushwaha. Information about MeetBot at http://wiki.debian.org/MeetBot.08:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.08:02
*** openstack changes topic to " (Meeting topic: tacker)"08:02
openstackThe meeting name has been set to 'tacker'08:02
dkushwaha#topic Roll Call08:02
*** openstack changes topic to "Roll Call (Meeting topic: tacker)"08:02
*** keiko-k has quit IRC08:03
tpatilHi08:03
hyunsikyangHi all08:03
*** shubham_potale91 has joined #openstack-meeting08:04
*** shubham_potale91 has left #openstack-meeting08:04
*** shubham_potale has quit IRC08:05
dkushwahahello all08:05
*** keiko-k has joined #openstack-meeting08:05
hyunsikyangHi dkushwaha08:05
keiko-kHello08:05
*** joxyuki has joined #openstack-meeting08:05
joxyukihi08:06
*** e0ne has joined #openstack-meeting08:06
dkushwaha#chair joxyuki08:06
openstackCurrent chairs: dkushwaha joxyuki08:06
*** priteau has joined #openstack-meeting08:07
dkushwaha#topic announcement08:07
*** openstack changes topic to "announcement (Meeting topic: tacker)"08:07
*** shubham_potale has joined #openstack-meeting08:07
dkushwahaWe have to release client libs code freeze is in this week, so we needs to merge client code soon08:08
dkushwaha#topic BP08:09
*** openstack changes topic to "BP (Meeting topic: tacker)"08:09
*** nitinuikey has joined #openstack-meeting08:09
dkushwahatpatil, any update from ur side on VNF package?08:09
tpatildkushwaha: you have given one review comment on python-tackerclient patch: https://review.opendev.org/#/c/679956/2/tackerclient/osc/v1/vnfpkgm/vnf_package.py@5408:09
tpatilas per ETSI specs, tenant_id or project_id cannot be passed in the request body when you create a VNF package08:10
tpatilwe are getting the project_id that is available in the tacker context and setting it during creation of vnf package in tacker-api service08:11
*** keiko-k has quit IRC08:12
dkushwahatpatil, not sure why we can passe it. This way we may loose multi-tenancy08:12
*** nnsingh has joined #openstack-meeting08:12
dkushwahaIMO, its beeter to get in as additional params08:13
tpatilwith tacker context, multi-tenancy will be retain08:13
*** keiko-k has joined #openstack-meeting08:13
tpatilbecoz it all works using token, when you get a token you need to specify username, password and project name08:13
*** keiko-k has quit IRC08:14
tpatilIn tacker case, endpoint doesn't include tenant_id, but in other projects it's there.08:15
*** keiko-k has joined #openstack-meeting08:15
dkushwahatpatil, ok, lets go with current way, we needs to check it again and we may keep it as further AI08:15
hyunsikyangI will comeback soon08:16
tpatildkushwaha: Sure, Thanks08:16
dkushwaharest parts looks fine to me, and just reviewing https://review.opendev.org/#/c/679958/08:17
tpatildkushwaha: let me confirm, so there is no need to add tenant_id for this release, correct?08:17
dkushwahatpatil, IMO we need to add it08:18
dkushwahabut might be we can check it later08:18
dkushwahayea, i mean not needed in this release08:19
tpatildkushwaha: Understood, Thanks08:19
*** ociuhandu has joined #openstack-meeting08:20
dkushwahajoxyuki, please help to review https://review.opendev.org/#/q/topic:bp/tosca-csar-mgmt-driver+project:openstack/python-tackerclient08:20
dkushwahaso that we can get it in soon08:21
tpatildkushwaha: Talking about tosca-parser, we have got two +2 but workflow is not yet set.08:21
dkushwahatpatil, yea i seen it, i will ask them to get it in08:22
tpatildkushwaha: Thanks, some of the unit tests are failing becoz it depends on the tosca-parser changes08:23
*** nnsingh46 has joined #openstack-meeting08:23
*** panda|rover has quit IRC08:23
tpatil#link : https://review.opendev.org/#/c/675600/08:23
*** shubham_potale34 has joined #openstack-meeting08:24
*** shubham_potale34 has quit IRC08:24
*** panda has joined #openstack-meeting08:24
dkushwaha#topic Open Discussion08:25
*** openstack changes topic to "Open Discussion (Meeting topic: tacker)"08:25
*** ociuhandu has quit IRC08:25
*** shubham_potale48 has joined #openstack-meeting08:25
*** nnsingh has quit IRC08:26
*** ociuhandu has joined #openstack-meeting08:26
dkushwahatpatil, ok, lets wait to merge tosca patch.08:26
*** shubham_potale30 has joined #openstack-meeting08:26
*** shubham_potale30 has left #openstack-meeting08:26
*** shubham_potale has quit IRC08:26
dkushwahaI do not have other topics to discuss now08:27
hyunsikyangI have a one question:)08:27
hyunsikyangAnyway, we implement tacker-fenix integration. So we uploaded it. https://review.opendev.org/#/c/681157/08:28
hyunsikyangas a WIP.08:28
dkushwahahyunsikyang, thanks for update.08:28
hyunsikyangBut, I just want to ask your guys about alarm url.08:29
dkushwahahyunsikyang, please go ahead your question08:29
hyunsikyangwe implemented it to create alarm url for each VDU.08:29
hyunsikyangAt the first time, we just think that VNF maintenance happen by each VNF unit.08:30
*** ociuhandu has quit IRC08:30
*** ociuhandu has joined #openstack-meeting08:30
hyunsikyangbut, IMO, when we think about multi VDU in one VNF, it should manage for each VDU.08:30
*** shubham_potale has joined #openstack-meeting08:31
hyunsikyangWhat your guys think about it?08:31
dkushwahahyunsikyang, I think maintenance work will be done at VNF level, not for a single instance but for all instances in VNF08:34
dkushwahahyunsikyang, caould you please explains some use cases where it needed at specific VDUs08:35
dkushwaha?08:35
hyunsikyangIn the ETSI standard, one of the example is vEPC for VNF.08:36
*** keiko-k has quit IRC08:36
hyunsikyangIt means that each VDU is one of the component of vEPC. To support maintanance for each component, I think each VDU needs maintenance.08:37
*** keiko-k has joined #openstack-meeting08:37
hyunsikyangBUt, we also consider maintenance as a VNF level, too.08:37
hyunsikyangOther question, Do you think multi VDU deployed to different host?08:38
hyunsikyangCAN I THINK VDU AS A vnfc?08:39
dkushwahahyunsikyang, yes a VNF can multiple VDUs/vnfc08:40
joxyukifor the first question, yes. VDUs can be deployed to different host.08:40
*** ociuhandu has quit IRC08:40
hyunsikyangI think so.08:41
*** ociuhandu has joined #openstack-meeting08:41
dkushwahahyunsikyang, As per your current spec, we needs to apply same maintenance policies for each instances in VNFs08:43
hyunsikyangwhat is the mean of each instance?08:44
hyunsikyangonly for VNF?08:44
*** ociuhandu has quit IRC08:44
dkushwahahyunsikyang, i mean the each VDUs08:45
dkushwahamaintenance should be true inside each VDU08:45
hyunsikyangok08:46
hyunsikyangthanks08:46
hyunsikyangSo if we also consider maintenance for VNF level, we will add that function for vnf url08:48
hyunsikyangwe will think about it:)08:48
hyunsikyangthanks all08:48
dkushwahahyunsikyang, +108:48
dkushwahahyunsikyang, JangwonLee, I will be great if you add test cases in your patch.08:49
*** yaawang_ has joined #openstack-meeting08:49
*** yaawang has quit IRC08:49
*** nnsingh46 has quit IRC08:50
dkushwahaDo we have anything else to discuss? otherwise we can close this meeting08:50
dkushwahaThanks Folks08:52
dkushwahaClosing this meeting08:52
dkushwaha#endmeeting08:52
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"08:52
openstackMeeting ended Tue Sep 10 08:52:42 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)08:52
openstackMinutes:        http://eavesdrop.openstack.org/meetings/tacker/2019/tacker.2019-09-10-08.02.html08:52
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/tacker/2019/tacker.2019-09-10-08.02.txt08:52
openstackLog:            http://eavesdrop.openstack.org/meetings/tacker/2019/tacker.2019-09-10-08.02.log.html08:52
*** keiko-k has quit IRC08:54
*** tpatil has quit IRC08:54
*** yamamoto has joined #openstack-meeting08:56
*** ykatabam has joined #openstack-meeting09:08
*** ykatabam has quit IRC09:13
*** rfolco has joined #openstack-meeting09:14
*** yamamoto has quit IRC09:17
*** tetsuro has joined #openstack-meeting09:18
*** ykatabam has joined #openstack-meeting09:20
*** yaawang_ has quit IRC09:33
*** yaawang has joined #openstack-meeting09:33
*** boxiang has joined #openstack-meeting09:35
*** yaawang has quit IRC09:37
*** yaawang has joined #openstack-meeting09:37
*** rcernin has joined #openstack-meeting09:39
*** yaawang has quit IRC09:41
*** yaawang has joined #openstack-meeting09:43
*** dklyle has quit IRC10:03
*** dklyle has joined #openstack-meeting10:04
*** ykatabam has quit IRC10:09
*** apetrich has quit IRC10:10
*** markvoelker has joined #openstack-meeting10:16
*** tetsuro has quit IRC10:17
*** markvoelker has quit IRC10:21
*** macz has joined #openstack-meeting10:25
*** ykatabam has joined #openstack-meeting10:28
*** macz has quit IRC10:30
*** jawad_axd has quit IRC10:40
*** markvoelker has joined #openstack-meeting10:55
*** ociuhandu has joined #openstack-meeting11:00
*** markvoelker has quit IRC11:00
*** ociuhandu has quit IRC11:01
*** ociuhandu has joined #openstack-meeting11:07
*** larainema has quit IRC11:15
*** nitinuikey has quit IRC11:16
*** ykatabam has left #openstack-meeting11:17
*** jawad_axd has joined #openstack-meeting11:20
*** priteau has quit IRC11:38
*** jamesmcarthur has joined #openstack-meeting11:54
*** raildo has joined #openstack-meeting11:55
*** markvoelker has joined #openstack-meeting12:04
*** jamesmcarthur has quit IRC12:08
*** apetrich has joined #openstack-meeting12:12
*** njohnston has joined #openstack-meeting12:13
*** jamesmcarthur has joined #openstack-meeting12:13
*** jamesmcarthur has quit IRC12:24
*** Lucas_Gray has joined #openstack-meeting12:25
*** macz has joined #openstack-meeting12:26
*** jamesmcarthur has joined #openstack-meeting12:26
*** jamesmcarthur has quit IRC12:29
*** hyunsikyang__ has joined #openstack-meeting12:30
*** macz has quit IRC12:30
*** Lucas_Gray has quit IRC12:32
*** Wryhder has joined #openstack-meeting12:32
*** Wryhder is now known as Lucas_Gray12:33
*** hyunsikyang has quit IRC12:33
*** apetrich has quit IRC12:33
*** mriedem has joined #openstack-meeting12:55
*** rbudden has joined #openstack-meeting12:57
*** lseki has joined #openstack-meeting13:02
*** macz has joined #openstack-meeting13:03
*** enriquetaso has joined #openstack-meeting13:04
*** macz has quit IRC13:07
*** eharney has joined #openstack-meeting13:12
*** rubasov has quit IRC13:21
*** Luzi has quit IRC13:32
*** bbowen_ has joined #openstack-meeting13:35
*** carloss has joined #openstack-meeting13:36
*** bbowen__ has joined #openstack-meeting13:37
*** bbowen has quit IRC13:37
*** bbowen_ has quit IRC13:39
*** eharney has quit IRC13:42
*** jawad_axd has quit IRC13:43
*** rcernin has quit IRC13:45
*** jawad_axd has joined #openstack-meeting13:45
*** jawad_axd has quit IRC13:45
*** jawad_axd has joined #openstack-meeting13:49
*** jawad_axd has quit IRC13:53
*** tidwellr has joined #openstack-meeting13:53
*** eharney has joined #openstack-meeting13:55
*** rubasov has joined #openstack-meeting13:56
*** mlavalle has joined #openstack-meeting13:56
*** ociuhandu has quit IRC13:57
*** ociuhandu has joined #openstack-meeting13:58
*** lajoskatona has joined #openstack-meeting13:59
*** boden has joined #openstack-meeting14:00
*** shintaro has joined #openstack-meeting14:00
slaweq#startmeeting networking14:00
openstackMeeting started Tue Sep 10 14:00:30 2019 UTC and is due to finish in 60 minutes.  The chair is slaweq. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
slaweqhi14:00
*** openstack changes topic to " (Meeting topic: networking)"14:00
openstackThe meeting name has been set to 'networking'14:00
lajoskatonaHi14:00
rubasovhi14:00
tidwellrhi14:00
mlavalleo/14:00
ralonsohhi14:00
njohnstono/14:01
bcafarelo/14:01
slaweqok, I think we can start14:01
slaweq#topic Announcements14:01
*** openstack changes topic to "Announcements (Meeting topic: networking)"14:01
slaweqT-3 milestone and feature freeze is this week14:02
slaweq#link https://releases.openstack.org/train/schedule.html14:02
slaweqso no new features merged after this week until Train branch will be created14:02
*** ociuhandu has quit IRC14:03
amotokihi14:03
slaweqIt is also week of final release for client libraries14:03
slaweqhi amotoki14:03
slaweqamotoki: so I think we should release final python-neutronclient version for Train this week, right?14:04
amotokislaweq: yes, I will check it soon14:04
slaweqamotoki: thx a lot14:04
slaweqok, next announcement14:04
slaweqPTL and TC nominations and (no) elections are done14:04
slaweqhttp://lists.openstack.org/pipermail/openstack-discuss/2019-September/009072.html14:05
slaweqcongrats to our new TC member njohnston :)14:05
njohnstono/14:05
mlavalleCongratulations to our next PTL, slaweq !14:05
slaweqand amotoki who is now Horizon PTL :)14:05
ralonsohnjohnston, congrats!!14:05
ralonsohand amotoki !14:05
njohnstoncongrats to all - we have an incredible team of people14:05
amotokinjohnston and slaweq: congrats14:05
mlavallecongrats to njohnston14:05
slaweqand of course Thank You mlavalle for all Your hard work as PTL14:05
tidwellr+114:06
njohnston+100014:06
ralonsoh+114:06
amotoki+1000 :)14:06
lajoskatona+114:06
mlavalleall the succeses were thanks to you14:06
mlavalleall14:06
mlavalleand the failures are all mine :-)14:06
haleyb+2 +W14:06
slaweqLOL14:06
bcafarelcongrats all new and former "titles" :)14:06
haleybnot about the failures of course14:06
mlavalleLOL14:07
slaweqok, next one14:07
slaweqShanghai PTG planning etherpad14:07
slaweqhttps://etherpad.openstack.org/p/Shanghai-Neutron-Planning14:07
slaweqPTG will be in less than 2 months so please start thinking about topics and add them to etherpad14:07
slaweqand speaking about etherpads14:08
slaweqlast week we created brainstorming etherpad for potential forum sessions' topics14:08
tidwellrany thoughts on remote PTG participation?14:08
slaweqhttps://etherpad.openstack.org/p/neutron-shanghai-forum-brainstorming14:08
mlavalletidwellr: yes, we are exploring options14:08
mlavallegoing back to the forum etherpad14:09
slaweqok, thx mlavalle14:10
mlavalleslaweq and I added some topics there14:10
mlavallewe have a tight deadline to propose them14:10
mlavalleSep 20th, I think14:10
slaweqcorrect14:10
mlavalleso I.d say our internal deadline shoud be next Monday14:10
*** moguimar has quit IRC14:11
slaweqmlavalle++14:11
*** hyunsikyang has joined #openstack-meeting14:11
mlavalleay that point we make a final decision and propose the topics14:11
slaweqI was thinking that we can discuss final proposals on team meeting next monday14:11
*** brinzhang has quit IRC14:11
mlavalleso if you have any ideas, this the week to dump them in the etherpad14:11
mlavalleslaweq: yes, let's do that14:12
*** brinzhang has joined #openstack-meeting14:12
mlavalleso I will leave the topic I added to the on demand agenda section14:12
*** moguimar has joined #openstack-meeting14:12
mlavallewe can skip it today14:12
mlavallesince we alreade talked about it14:12
slaweqthx mlavalle14:12
slaweqabout ideas, please wrote them to etherpad even if You will not be there or You don't want/can't moderate such session14:13
slaweq:)14:13
slaweqok, and the last one announcement for today:14:13
slaweqTrain PTG summary: http://lists.openstack.org/pipermail/openstack-discuss/2019-May/006408.html (just as a reminder)14:13
slaweqany other announcements from the team?14:14
*** hyunsikyang__ has quit IRC14:14
slaweqok, lets move on than14:15
slaweq#topic Blueprints14:15
*** openstack changes topic to "Blueprints (Meeting topic: networking)"14:15
slaweqblueprints targeted for T-3 https://launchpad.net/neutron/+milestone/train-314:15
slaweqany updates about them?14:16
njohnstonNo update for ethertype; I hope to do some serious work on it for this week but I am in doubt that it will make Train14:16
rubasovthe extraroute stuff is currently held up by rechecks on this: https://review.opendev.org/68098014:17
slaweqaccording to extraroute, it looks for me that we are only missing https://review.opendev.org/#/c/670851/14:18
slaweqis that right?14:18
rubasovreviewers please keep in mind that the whole topic is quite well reviewed but it looks bad (zuul -1s) because of unmerged cross-repo dependencies14:18
slaweqand this can be done when we will bump neutron-lib version in neutron, right?14:18
amotokirubasov: I think requirements bump can be done in parallel.14:18
amotokiwe need both but it is not a blocker except lower-constraints job14:19
rubasovslaweq: and then these: https://review.opendev.org/#/q/status:open+topic:extraroute14:19
mlavallerubasov: so if we take this as a feature freeze exception, are you willing to continue pushing it?14:19
rubasovmlavalle: absolutely14:20
rubasovthank you14:20
slaweqrubasov: but in this list there is only this one neutron patch which I mentioned14:20
slaweqand python-neutronclient14:20
slaweqother than that, those are patches to heat and OSC14:20
rubasovneutronclient is a dependency for heat14:20
rubasovsdk and asc is more important from neutron perspective14:20
rubasovfor cli of course14:20
mlavallebut neutron cleint has already W+, right?14:21
rubasovsdk and osc ^^^14:21
rubasovmlavalle: yes14:21
mlavalleso if we focus on getting that lib patch14:21
mlavalleplus the neutron patch, we did our bit, coorect?14:21
amotokiosc and neutronclient patches depend on neutron implementation, right?14:22
amotokis/osc/sdk/14:22
rubasovideally: bump+neutron+sdk+osc14:22
rubasovamotoki: yes14:22
mlavalleI am just trying to highlight what the neutron team controls14:22
amotokiso, this week is the freeze week for sdk + neutronclent, so we need to get the neutron patch merged soon to land them.14:23
rubasovmlavalle: understood14:23
mlavalleand that is the neutron-lib and the neutron patches, correct?14:23
rubasovthen bump+neutron14:23
mlavallecool14:23
mlavallenjohnston: let's revisit the ethertypes during the drivers meeting on Friday, ok?14:24
mlavallewe make a decision then14:24
slaweqso lets focus on this bump neutron-lib patch and neutron patch then - I hope gate will be unblocked today14:24
rubasovwith urls: https://review.opendev.org/680980 and https://review.opendev.org/67085114:24
njohnstonmlavalle: sounds good14:24
rubasovthank you everybody14:24
amotokiis the heat patch targeted for Ussuri or do they consider FFE?14:24
*** Lucas_Gray has quit IRC14:24
rubasovamotoki: I don't know at the moment14:25
amotokiit affects the importance on SDK merge.14:25
*** Lucas_Gray has joined #openstack-meeting14:25
amotokirubasov: okay, so it looks like we can defer SDK stuffs to Ussuri.14:25
*** shintaro has quit IRC14:25
mlavalleI know we are trying to think as a broader community....14:26
rubasovamotoki: sdk is actually not a dependency for heat14:26
mlavallebut this extension has value in itself, regardless of whether we land the corresponding part in heat, right?14:26
rubasovit is a dependency for osc14:26
rubasovmlavalle: yes14:26
mlavalleso for this week, in the neutron team let's focus on landing the extension14:27
rubasovit feels like I should have a put an ascii art of the dependency tree in the commit messages :-)14:27
amotokiheat --> neutronclient --> neutron --> req bump14:28
slaweqmlavalle: sounds good, and lets check if we have all what's needed on friday's drivers meeting14:28
amotokiosc --> openstacksdk --> neutron14:28
slaweqwill that be ok?14:28
rubasovamotoki: yes14:28
slaweqor do we need to release neutronclient on Thursday?14:28
rubasovslaweq: will attend14:28
amotokineutronclient release can wait till Thur and if the neutron patch lands we can adjust the commit hash.14:28
slaweqok14:29
amotokiI see three small commits in neutornclient since the last release14:29
slaweqso we have plan for this one :)14:29
amotokiso it looks better to release the client.14:29
*** Lucas_Gray has quit IRC14:30
slaweqfor other BPs, we will have to move them to Ussuri cycle, right?14:31
*** armax has joined #openstack-meeting14:31
mlavalleyes14:31
mlavallebut let's wait until Friday14:32
slaweqmlavalle: sure :)14:32
slaweqok, next topic14:32
slaweq#topic Community goals14:32
*** openstack changes topic to "Community goals (Meeting topic: networking)"14:32
slaweqany updates about python3 or pdf docs?14:32
*** ociuhandu has joined #openstack-meeting14:32
*** ociuhandu has quit IRC14:33
bcafarelI saw some additional pdf docs merged I think14:33
njohnstonlajoskatona: How are things with python3 for networking-odl CI jobs, especially https://review.opendev.org/#/c/672925/ ?14:33
*** ociuhandu has joined #openstack-meeting14:33
amotokiRe pdf docs, we succeeded to have pathces for all stadium repos :)14:34
amotokiI think they are not urgent as they are doc changes.14:34
amotokiI added the review links to the meeting wiki14:35
lajoskatonanjohston: that one is still failing, I have to ping again the ODL team about that14:35
slaweqamotoki: only urgency which I see is that this week is also "Train Community Goals Completed"14:35
slaweqso my assumption is that it should be finished this week14:35
slaweqbut we can easily finish it later for stadium projects14:35
lajoskatonanjohston: thanks to the reviews other jobs are now in quite good sape14:35
amotokinot till the release date?14:35
amotokiah, I found https://releases.openstack.org/train/schedule.html#t-goals-complete14:36
*** ianychoi_ is now known as ianychoi14:37
slaweqamotoki: yes, that was the link I was referring to14:37
*** Lucas_Gray has joined #openstack-meeting14:37
*** ociuhandu has quit IRC14:37
amotokire the pdf goal, I will discuss it with asettle later. she is the goal champion.14:37
slaweqok, thx amotoki14:38
*** artom has quit IRC14:38
slaweqaccording to IPv6-Only Deployments in Neutron we are good14:38
mlavallecool14:38
*** artom has joined #openstack-meeting14:38
slaweqthere are WIP patches for networking-ovn and networking-odl now14:38
amotokicommunity goals are tracked by storyboard, so we can update the corresponding stories.14:38
*** ociuhandu has joined #openstack-meeting14:39
slaweqtidwellr: can You check if we would need similar IPv6 only job for neutron-dynamic-routing also?14:39
tidwellrslaweq: I'll double-check14:40
tidwellrwe might not need one though14:40
slaweqthx tidwellr14:40
slaweqI will also email tmorin with similar question about networking-bagpipe14:40
slaweqok, let's move on14:41
slaweq#topic Bugs14:41
*** openstack changes topic to "Bugs (Meeting topic: networking)"14:41
slaweqour bug deputy last week was njohnston14:41
slaweqhe sent summary in Bugs report for week of September 2nd: http://lists.openstack.org/pipermail/openstack-discuss/2019-September/009261.html14:41
slaweqthis week our bug deputy is mlavalle so we are in very good hands :)14:42
njohnstonMuch gate turmoil last week14:42
mlavallelet's see if I don't wreck the house ;-)14:42
njohnstonthanks rubasov for taking https://bugs.launchpad.net/neutron/+bug/184328514:43
openstackLaunchpad bug 1843285 in neutron "Trunk scenario test test_subport_connectivity failing with iptables_hybrid fw driver" [High,In progress] - Assigned to Bence Romsics (bence-romsics)14:43
njohnstonbut https://bugs.launchpad.net/neutron/+bug/1843290 is still unassigned14:43
openstackLaunchpad bug 1843290 in neutron "Remove network flavor profile fails" [High,New]14:43
rubasovnjohnston: of course14:43
njohnstonand while the report indicates https://bugs.launchpad.net/neutron/+bug/1843282 is complete; the CI is still failing.  slaweq pushed a change to make some CI nonvoting as a result https://review.opendev.org/#/c/681186/14:43
openstackLaunchpad bug 1843282 in neutron "Rally CI not working since jsonschema version bump" [High,Fix released] - Assigned to Rodolfo Alonso (rodolfo-alonso-hernandez)14:43
*** e0ne has quit IRC14:44
ralonsohonce rally releases a new version, we'll have rally-openstack working again14:44
*** e0ne has joined #openstack-meeting14:44
njohnstonand one bug I was not able to reproduce properly, so if someone is familiar with the network ip availability API: https://bugs.launchpad.net/neutron/+bug/184321114:45
openstackLaunchpad bug 1843211 in neutron "network-ip-availabilities' result is not correct when the subnet has no allocation-pool" [Undecided,New]14:45
njohnstonthose are the highlights of outstanding issues14:45
amotokinjohnston: I will check it.14:46
slaweqthx njohnston for update14:46
njohnstonthank you amotoki14:46
slaweqok, let's move on than14:47
slaweq#topic neutron-lib14:47
*** openstack changes topic to "neutron-lib (Meeting topic: networking)"14:47
slaweqboden: any updates?14:47
bodenhi14:47
*** jamesmcarthur has joined #openstack-meeting14:47
bodenno technical updates from me, but I did want to mention that due to a change in focus, I won't have much time to work on neutron-lib moving forward14:48
bodenthat said, there's still plenty of neutron-lib work left... if anyone wants to pick it up, I'm available to help ramp someone else up14:48
mlavalleis this change in your focus imediate or is there going to be a transition period?14:49
bodenit's immediate, but as I mentioned I still have some cycles here and there.14:49
bodenI think the neutron-lib work is at a good point for this anyway; there's nothing much I'm aware of in neutron-lib that's pending consumption in neutron14:50
mlavallein that case, I'll send a message to the ML indicating that we need a new neutron-lib champion14:50
bodenI do have some pending consumption patches out there, but they have been slow moving... some dating back months and month14:50
njohnstonthank you boden for the incredible quantity and quality of work you have done over the years14:50
bodenwelcome... I'll still be around so feel free to ping me for reviews, etc..14:51
mlavallewould you be able to respond to that message indicating whan needs to be done forward and the priorities?14:51
bodenmlavalle I can, but we've had a list out there for a long time now14:51
bodenhttps://etherpad.openstack.org/p/neutron-lib-volunteers-and-punch-list14:52
mlavalleok, just point to the list in that case in your response14:52
bodennothing changed here; all still valid14:52
slaweqboden: that's sad news but I understand it, thx a lot for all this hard work on neutron-lib14:52
mlavalleok, nevermind, I'll point to it in my message14:52
*** Lucas_Gray has quit IRC14:52
mlavalleand yes, I join the rest of the team in thanking for all your efforts....14:52
bodenbeen my pleasure14:53
mlavalleand wishing you good luck in your future endeavours14:53
bodenthank you14:53
bcafarelindeed thanks a lot for all the work you've completed there boden!14:54
slaweqok, let's move on than14:54
slaweq#topic On demand agenda14:54
*** openstack changes topic to "On demand agenda (Meeting topic: networking)"14:54
slaweqin the meeting agenda there is only one item from mlavalle but we already talked about it14:54
mlavallewe'll keep it for next week14:54
slaweqanyone has anything else to talk about?14:54
slaweqwe have 5 minutes14:54
slaweqok, if not, I will end this meeting here14:55
slaweqthx for attending14:56
slaweqand have a great week14:56
slaweq#endmeeting14:56
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"14:56
slaweqo/14:56
openstackMeeting ended Tue Sep 10 14:56:07 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:56
mlavalleo/14:56
ralonsohbye14:56
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking/2019/networking.2019-09-10-14.00.html14:56
njohnstono/14:56
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking/2019/networking.2019-09-10-14.00.txt14:56
amotokithanks all14:56
rubasovbye14:56
openstackLog:            http://eavesdrop.openstack.org/meetings/networking/2019/networking.2019-09-10-14.00.log.html14:56
*** boden has left #openstack-meeting14:56
lajoskatonao/14:58
bcafarelo/14:58
ralonsoh#startmeeting neutron_qos15:01
openstackMeeting started Tue Sep 10 15:01:38 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
*** diablo_rojo has joined #openstack-meeting15:01
ralonsohI don't know if David is going to join us today (I think he is in PTO)15:02
ralonsohok, so the only item in the agenda is15:03
ralonsoh#link https://blueprints.launchpad.net/neutron/+spec/neutron-classifier-neutron-qos15:03
ralonsohpatches: https://review.opendev.org/#/q/topic:qos-classifier+(status:open+OR+status:merged)15:03
ralonsohthe first one, the spec15:04
ralonsoh#link https://review.opendev.org/#/c/678865/15:04
ralonsohand then, the introduction of the NC in Neutron15:04
ralonsohn-lib: #link https://review.opendev.org/#/c/670049/15:04
ralonsohneutron: #link https://review.opendev.org/#/c/670050/15:04
ralonsohbecause David is not here, we can continue the discussion in gerrit15:05
slaweqI was reviewing spec for this recently15:05
slaweqDavid answered me but I didn't have time to read it carefully yet15:05
ralonsohme too, I think he needs to specify a bit the purpose15:05
ralonsohand, btw, he needs first to migrate the NC code to Neutron15:06
ralonsohat that's a big piece of code15:06
ralonsoh(previous links)15:06
*** jawad_axd has joined #openstack-meeting15:06
ralonsohthen, once the NC code is merged, there is a POC of the classification using DSCP15:07
ralonsoh#link https://review.opendev.org/#/c/636333/15:07
ralonsohthe next patch should be the back-end implementation15:07
ralonsohand that's all for today15:07
slaweqthat was quick :)15:07
ralonsohsomething else on this RFE?15:08
ralonsoh(not approved yet)15:08
slaweqnot from my side15:08
ralonsohok15:08
ralonsoh#topic Open Discussion15:08
*** openstack changes topic to "Open Discussion (Meeting topic: neutron_qos)"15:08
ralonsohand something else to add in general, about QoS?15:08
slaweqnope15:08
ralonsohthanks slaweq!15:08
ralonsohsee you later15:08
slaweqthx ralonsoh :)15:08
ralonsoh#endmeeting15:09
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"15:09
slaweqsee You on next meeting15:09
openstackMeeting ended Tue Sep 10 15:09:01 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:09
slaweq:)15:09
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_qos/2019/neutron_qos.2019-09-10-15.01.html15:09
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_qos/2019/neutron_qos.2019-09-10-15.01.txt15:09
slaweqo/15:09
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_qos/2019/neutron_qos.2019-09-10-15.01.log.html15:09
*** tssurya has quit IRC15:13
*** ociuhandu has quit IRC15:19
*** ociuhandu has joined #openstack-meeting15:19
*** links has quit IRC15:22
*** ociuhandu has quit IRC15:22
*** ociuhandu has joined #openstack-meeting15:23
*** ociuhandu has quit IRC15:28
*** ociuhandu has joined #openstack-meeting15:31
*** macz has joined #openstack-meeting15:35
*** gyee has joined #openstack-meeting15:35
*** ociuhandu has quit IRC15:38
*** browny_ has joined #openstack-meeting15:40
*** apetrich has joined #openstack-meeting15:41
*** browny has quit IRC15:42
*** ociuhandu has joined #openstack-meeting15:47
*** mattw4 has joined #openstack-meeting15:48
*** ociuhandu has quit IRC15:58
*** ociuhandu has joined #openstack-meeting15:58
slaweq#startmeeting neutron_ci16:00
openstackMeeting started Tue Sep 10 16:00:15 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
slaweqwelcome again16:00
openstackThe meeting name has been set to 'neutron_ci'16:00
ralonsohhi16:00
slaweqmlavalle will not be here today16:01
slaweqbut lets wait few more minutes for njohnston bcafarel and others16:01
* slaweq will be back in 2 minutes16:01
bcafarelo/ sorry did not see the time16:01
clarkbreally quickly I wanted to point out that some of octavia's CI problems were due to an ubuntu kernel bug in ovs that was causing the kernel to panic. Its possible neutron and others are seeing that too (if the job is retried)16:02
clarkbthat bug has been fixed we need to update our mirrors and rebuild images (complicated by a fileserver outage the other day we are still trying to recover from)16:02
*** ociuhandu has quit IRC16:02
*** ociuhandu has joined #openstack-meeting16:03
slaweqok, I'm back16:03
johnsom#link https://bugs.launchpad.net/ubuntu/+source/linux/+bug/184244716:03
openstackLaunchpad bug 1842447 in linux (Ubuntu) "Kernel Panic with linux-image-4.15.0-60-generic when specifying nameserver in docker-compose" [Undecided,Confirmed]16:03
johnsomfyi16:03
slaweqclarkb: johnsom thx for heads up16:03
johnsomI was going to ask after my meeting as we are not seeing new images today16:03
slaweqbut I didn't saw it in neutron jobs (yet)16:03
slaweqbut we will keep an eye on it for sure :)16:04
slaweqok, let's get going with meeting agenda16:04
slaweq#topic Actions from previous meetings16:04
*** openstack changes topic to "Actions from previous meetings (Meeting topic: neutron_ci)"16:04
slaweqfirst one16:04
slaweqmlavalle to continue investigating router migrations issue16:04
slaweqhe told me that he is still investigating16:05
slaweqso I will just assign it to him for next week too16:05
slaweq#action mlavalle to continue investigating router migrations issue16:05
slaweqnext one16:05
slaweqslaweq to check reasons of failures of neutron-tempest-plugin-scenario-openvswitch job16:05
slaweqI didn't have time but it looks much better now so I hope we will be good with this job :)16:05
slaweqnext one16:05
slaweqralonsoh to report bug and investigate failing test_get_devices_info_veth_different_namespaces functional test16:05
njohnstono/ sorry I am late16:06
ralonsohslaweq, that's solved in your patch16:06
slaweqahh, right :)16:06
slaweqok16:06
slaweqthx ralonsoh16:06
ralonsohnp!16:06
*** tesseract has quit IRC16:06
slaweqok, next one16:06
slaweqslaweq to check reason of failure neutron.tests.functional.agent.test_firewall.FirewallTestCase.test_rule_ordering_correct16:06
slaweqIt was the issue which should be fixed with https://review.opendev.org/#/c/679428/16:06
slaweqso nothing more to check there16:06
slaweqand the last one16:07
slaweqslaweq to add mariadb periodic job16:07
slaweqI proposed https://review.opendev.org/68120216:07
slaweqbut it also requires https://review.opendev.org/#/c/681200/1 and https://review.opendev.org/#/c/681201/16:07
ralonsoh+1 to this16:07
slaweqralonsoh: lets first check if that will work as expected :)16:08
slaweqI will continue this work during next week16:08
*** lajoskatona has left #openstack-meeting16:08
slaweqok, lets move on to the next topic than16:08
slaweq#topic Stadium projects16:08
*** openstack changes topic to "Stadium projects (Meeting topic: neutron_ci)"16:08
slaweqPython 3 migration16:08
slaweqStadium projects etherpad: https://etherpad.openstack.org/p/neutron_stadium_python3_status16:08
slaweqI think we already talked about it on neutron meeting16:08
njohnston+116:08
slaweqnjohnston: anything You want to add about it?16:09
njohnstonslaweq: Just that I have not had a chance to check in with yamamoto about midonet16:09
njohnstonthat's all16:10
slaweqok, yes, midonet is the last "almost not touched" one, right?16:10
njohnstonyes16:10
njohnstonI rarely see yamamoto online it seems16:10
slaweqwe still have some time but IMO we should finish this work before end of this year16:10
slaweqas python 2 is EOL at 1.1.202016:10
slaweqok, and second stadium projects topic16:11
slaweqtempest-plugins migration16:11
slaweqEtherpad: https://etherpad.openstack.org/p/neutron_stadium_move_to_tempest_plugin_repo16:11
slaweqI know that tidwellr is doing some progress with neutron-dynamic-routing still16:11
slaweqtidwellr: do You need help on this?16:11
njohnstonsame state as last week I believe; vpnaas is -W from mlavalle16:12
*** browny has joined #openstack-meeting16:12
*** lpetrut has quit IRC16:12
njohnstontidwellr did mention on his review that he was seeing worrisome errors from neutron https://review.opendev.org/#/c/65209916:12
*** browny_ has quit IRC16:13
slaweqyes, I saw 1 error on this patch today16:13
*** mattw4 has quit IRC16:14
slaweqok, tidwellr if You would need any help, please ping me :)16:14
*** bbowen__ has quit IRC16:14
slaweqanything else You want to talk regarding stadium projects CI today?16:14
tidwellrslaweq: I'm looking into it, but I could use some help16:15
tidwellrI thought it would be simple, but these issue aren't seeming so simple anymore :)16:15
slaweqtidwellr: ok, I will try to look into it this week too16:15
njohnstonnothing else from me16:15
slaweqand interesting question is why it's not failing in old, legacy jobs16:16
*** kopecmartin is now known as kopecmartin|off16:16
tidwellrslaweq: I'm seeing intermittent failures where BGP peering simply doesn't start, but then on a recheck everything begins peering and the test in question passes16:17
*** e0ne has quit IRC16:18
tidwellrbut we don't see this behavior with the legacy jobs in neutron-dynamic-routing16:18
slaweqBGP peering is something run in docker container, right?16:18
tidwellrBGP agent peers with docker container16:18
slaweqok, I will take a look into logs16:18
tidwellrthe BGP agent will always be the one to initiate the peering16:18
slaweqmaybe I will find something16:19
tidwellrgood luck :)16:19
slaweqthx tidwellr :)16:19
slaweqand thx for working on this16:19
slaweqok, lets move on16:19
slaweqnext topic16:19
slaweq#topic Grafana16:19
*** openstack changes topic to "Grafana (Meeting topic: neutron_ci)"16:19
slaweq#link http://grafana.openstack.org/dashboard/db/neutron-failure-rate16:19
slaweq(sorry that I forgot sent it at the beginning)16:19
slaweqcurrently we have 2 main issues in CI16:20
slaweq1. problems with rally16:21
slaweqwhich is failing 100% times due to jsonschema versions mismatch16:21
slaweq2. neutron-tempest-iptables_hybrid-fedora which is even not starting (RETRY LIMIT) 100% times16:22
slaweqbecause we were running it on F28 which is now EOL and there is no repositories for it anymore16:22
slaweqfor both cases there are patches to fix them16:22
slaweqfor rally issue we are waiting for new rally release16:22
ralonsohone question, if possible (about Fedora issue)16:23
slaweqralonsoh: sure16:23
ralonsohwhy, instead of using F29 we don't try F30?16:23
njohnstonslaweq: FOr Fedora issue, is this DNM patch the fix patch or is there a different one?16:24
njohnstonhttps://review.opendev.org/#/c/681213/16:24
ralonsohyes, why don't we switch to F30?16:24
ralonsohinstead of F2916:24
ralonsohmaybe Brian can help us (is not here now)16:24
slaweqmy DNM patch was send only to test if haleyb's change to devstack will fix this job16:24
ralonsohhaleyb, yes he is!16:25
slaweqbut it's not fix for the issue16:25
njohnstonah ok.16:25
slaweqfix is proposed by haleyb to devstack repo16:25
slaweqhttps://review.opendev.org/#/c/662529/516:25
clarkbre f30 I don't know that it is quite ready yet. We are adding it in nowish iirc16:25
*** mattw4 has joined #openstack-meeting16:25
slaweqaccording to comment from ianw there he had some issues with F3016:25
clarkb(but once it is ready you should feel free to test on it)16:25
haleyband doug is looking at the barbican failure today16:25
slaweqthat's why we are changing for F29 now16:25
ralonsohooook, thanks!!16:25
redrobothaleyb, o/16:26
haleybi didn't see any f30 support, so stopped at f2916:26
ralonsohperfect16:26
*** bbowen__ has joined #openstack-meeting16:26
slaweqralonsoh: njohnston is that clear for You now?16:27
ralonsohit is, for sure16:27
njohnstonslaweq: yes thanks16:27
slaweqgreat :)16:28
slaweqhaleyb: thx for fixing this16:28
haleybnp, wish everything had merged sooner, started as a periodic ovn job failure16:28
slaweqbut also to unblock our gates ASAP I sent today patch https://review.opendev.org/#/c/681186/16:28
slaweqlater we will be able to revert it when proper fixes in external repos will land16:29
slaweqok16:29
slaweqother than those 2 issues, we are quite fine16:29
slaweqeven functional/fullstack jobs are in quite good shape this week16:29
*** ekcs has joined #openstack-meeting16:30
slaweqand that's all from me according to grafana16:31
slaweqdo You have anything else about grafana today?16:31
njohnstonnope16:33
slaweqok, lets move on16:33
slaweq#topic fullstack/functional16:33
*** openstack changes topic to "fullstack/functional (Meeting topic: neutron_ci)"16:33
*** mattw4 has quit IRC16:33
slaweqI today found one new (for me) issue on functional tests16:33
slaweqand it happend at least twice16:33
slaweqit was on different tests16:33
slaweqbut same error in test's log16:33
slaweqhttps://0668011f33af6364883c-c555fae2d8c498523cc4b2c363541725.ssl.cf1.rackcdn.com/679852/11/gate/neutron-functional/6b7c424/controller/logs/dsvm-functional-logs/neutron.tests.functional.agent.linux.test_linuxbridge_arp_protect.LinuxBridgeARPSpoofTestCase.test_arp_protection_port_security_disabled.txt.gz16:34
slaweqor16:34
slaweqhttps://148a66b404dde523de26-17406e3478c64e603d8ff3ea0aac16c8.ssl.cf5.rackcdn.com/680393/1/check/neutron-functional-python27/59e721e/controller/logs/dsvm-functional-logs/neutron.tests.functional.agent.linux.test_l3_tc_lib.TcLibTestCase.test_clear_all_filters.txt.gz16:34
slaweqdid You saw something like that before?16:34
njohnstonno, that is a new one for me... very strange...16:34
ralonsohthis can be (i guess) because you are deleting the qos registers16:34
slaweqtbh this ovsdb error may be redhearing as it could happend during cleanup16:35
ralonsohand the rules are not there anymore16:35
slaweqbut that's only thing which was common in those 2 failed tests for me16:35
ralonsohyes, this could happen16:35
ralonsohI can check this tomorrow16:35
slaweqthx ralonsoh16:35
ralonsohdo you have a bug ref?16:35
slaweqralonsoh: no16:35
ralonsohok, I'll do it16:36
slaweqok, thx a lot16:36
slaweq#action ralonsoh to report bug and check issue with ovsdb errors in functional tests16:36
slaweqand I also found (happend once) issue with killing external process during cleanup16:36
slaweqI reported it here     New bug reported by me: https://bugs.launchpad.net/neutron/+bug/1843418 - not very urgent16:36
openstackLaunchpad bug 1843418 in neutron "Functional tests shouldn't fail if kill command will have "no such process" during cleanup" [Medium,In progress] - Assigned to Slawek Kaplonski (slaweq)16:36
slaweqI know that bcafarel and ralonsoh already reviewed proposed patch16:37
slaweqI didn't had time to check those reviews yet16:37
ralonsohslaweq, I propose to implement a os.kill() method with and wihtout privsep16:37
ralonsohif root is True/False16:37
ralonsohthere are several places in Neutron where a shell to execute "kill" is spawned16:38
slaweqralonsoh: that is good idea16:38
slaweqI will do it this way16:38
ralonsohperfect!16:39
*** igordc has joined #openstack-meeting16:39
bcafarel that will be nice :)16:39
njohnstonvery good +116:39
slaweqthx a lot for this idea and reviewing patch16:39
slaweqthat's all regarding functional/fullstack jobs from me16:40
slaweqanything else You want to add?16:40
*** jawad_axd has quit IRC16:41
slaweqok, if not that was all from me for today16:41
slaweqas I don't have anything new regarding scenario jobs16:42
slaweqdo You have anything else You want to talk about today?16:42
slaweqif not, I think I can give You back about 15 minutes :)16:42
njohnstono/16:43
bcafarelyay16:43
bcafarelo/16:43
slaweqok, lets finish than16:43
ralonsohbye16:43
slaweqthx for attending16:43
slaweqo/16:43
slaweq#endmeeting16:43
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"16:43
openstackMeeting ended Tue Sep 10 16:43:45 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:43
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_ci/2019/neutron_ci.2019-09-10-16.00.html16:43
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_ci/2019/neutron_ci.2019-09-10-16.00.txt16:43
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_ci/2019/neutron_ci.2019-09-10-16.00.log.html16:43
*** igordc has quit IRC16:44
*** ociuhandu_ has joined #openstack-meeting17:00
*** ociuhandu has quit IRC17:03
*** brault has joined #openstack-meeting17:03
*** lettucefuzz has joined #openstack-meeting17:05
*** ociuhandu_ has quit IRC17:05
*** brault has quit IRC17:08
*** jamesmcarthur has quit IRC17:18
*** brault has joined #openstack-meeting17:22
*** brault has quit IRC17:27
*** njohnston is now known as njohnston|lunch17:30
*** ralonsoh has quit IRC17:32
*** ralonsoh has joined #openstack-meeting17:39
*** igordc has joined #openstack-meeting17:44
*** trident has quit IRC17:46
*** e0ne has joined #openstack-meeting17:46
*** igordc has quit IRC17:50
*** cheng1 has quit IRC17:51
*** lettucefuzz has quit IRC17:51
*** cheng1 has joined #openstack-meeting17:55
*** diablo_rojo has quit IRC17:55
*** igordc has joined #openstack-meeting17:57
*** trident has joined #openstack-meeting17:59
*** igordc has quit IRC18:06
*** igordc has joined #openstack-meeting18:06
*** igordc has quit IRC18:15
*** eharney has quit IRC18:17
*** jamesmcarthur has joined #openstack-meeting18:18
*** ociuhandu has joined #openstack-meeting18:39
*** ociuhandu has quit IRC18:44
*** ralonsoh has quit IRC18:46
*** gyee has quit IRC18:49
*** gyee has joined #openstack-meeting18:50
*** Shrews has joined #openstack-meeting18:51
*** brinzhang has quit IRC18:54
*** brinzhang has joined #openstack-meeting18:54
*** panda is now known as panda|rover|off18:54
*** jamesmcarthur has quit IRC18:57
*** ricolin has quit IRC18:58
corvusyes!19:00
clarkbyou are here for the meeting?19:00
fungideh'ya19:00
ianwhello19:01
clarkb#startmeeting infra19:01
openstackMeeting started Tue Sep 10 19:01:11 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-September/006478.html Our Agenda19:01
clarkb#topic Announcements19:01
*** openstack changes topic to "Announcements (Meeting topic: infra)"19:01
clarkbno one objected to me holding the PTL baton for another cycle and I'm apparently PTL again :)19:02
fungicondolences19:02
clarkbas mentioned in my candidacy statement I'd like for this to be my last cycle. And will be more than happy to work with people to make such a transition easier19:02
clarkbThe another announcement is there is an openstack foundation board meeting immediately after our meeting19:03
corvusrelated -- we should probably talk about opendev governance at some point19:03
clarkbcorvus: ++19:03
corvus(don't want to derail announcements, but i expect that's intertwined with the openstack-infra ptl issue)19:03
clarkbboard meeting details here https://wiki.openstack.org/wiki/Governance/Foundation/10September2019BoardMeeting if you want to listen in. I'll do my best to avoid this meeting going long too19:03
fungiyes, i have a feeling if much of what we do became the jurisdiction of opendev, what's left and openstack-specific could maybe become a sig19:03
clarkbcorvus: ya there is definitely interconnectedness19:04
clarkbfwiw I'd happily let someone else be opendev PTL (or whatever we end up calling it) too :)19:04
clarkbcorvus: I'll scribble a note to get that ball rolling19:04
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-09-03-19.01.txt minutes from last meeting19:05
clarkbI don't see any actions there. Also not sure about you but the last week has been one of fighting fires for me19:06
clarkbnot much got done off of my normal TODO list. On the upside I think our log storage in swift should be much happier now and hopefully our jobs are slightly easier to debug when "networking" breaks19:06
clarkb#topic Priority Efforts19:07
*** openstack changes topic to "Priority Efforts (Meeting topic: infra)"19:07
clarkb#topic OpenDev19:07
*** openstack changes topic to "OpenDev (Meeting topic: infra)"19:07
clarkbMaybe now is a good time to talk about what we think the next step on moving opendev governance forward is?19:07
clarkbI assume it will involve a discussion with the openstack TC of some sort19:07
clarkbfungi: ^ as our TC rep an thoughts on that?19:07
fungiwell...19:08
fungii'm technically no longer on the tc ;)19:08
fungibut still happy to provide guidance there19:08
clarkboh right that also changed last week :)19:08
fungiand yes, the sooner we bring it up with them, the better19:09
fungi(for those who missed the openstack tc election, i stepped down to help make sure the election process went smoothly, since there were some significant tooling complexities due to scheduling constraints)19:09
clarkbfungi: is there a formal agenda we have to add ourselves to or is there still informal office horus we can show up to and discuss at?19:10
corvusyou know me: the closer it resembles a self-organized collective, the better as far as i'm concerned :)19:10
fungii recommend a thread on the openstack-discuss ml, with [tc][infra] in the subject19:10
clarkbfungi: ok I can draft an email for that on etherpad and we can decide when it is ready to be sent19:10
fungisounds great!19:11
*** eharney has joined #openstack-meeting19:11
fungibut yeah, the tc formally meets infrequently to satisfy requirements in the osf bylaws, and treats those meetings mostly as a reporting outlet19:11
corvusi think the main thing is it won't be *under* the tc (or any foundation project), but we want involvement from them; so figuring out what form that involvement should take is a big question i think.19:11
clarkbcorvus: ++19:11
fungiexactly19:12
clarkband I'm not sure we need to have that answer before kicking off a thread to discuss it, though some ideas will likely help guide discussion in a productive manner19:12
corvusyeah, for something like that "how would you like to be involved" is a fine open-ended question to ask i think19:12
fungii wholeheartedly concur19:13
corvusmaybe worth sending the same email to all the osf projects?19:13
fungior at least a similar e-mail, sure19:13
fungithe degree to which we're involved in and assisting each of them and with what tends to differ19:13
fungithough i expect what we want to offer all of them is roughly the same19:14
corvusand our interest in their participation is probably roughly equal :)19:14
clarkb++19:14
fungiabsolutely19:14
fungior at least proportional19:14
corvusnon-zero19:15
clarkbI think that gives us a really good starting point to being a draft and sort out details together there19:15
clarkbs/being/begin/19:15
corvusi'm a draft19:15
clarkbon nitrous?19:16
fungisounds like we all are19:16
corvusclarkb: yes, i'm also a drift19:16
clarkbAlright any other opendev related business or should we move on?19:16
corvus++19:17
clarkb#topic Update Config Management19:17
*** openstack changes topic to "Update Config Management (Meeting topic: infra)"19:17
funginone here19:17
clarkbOne thing I managed to get off of my todo list was merging and monitoring and applying mordreds config updates for Gerrit19:18
clarkbOur gerrits should no longer do full replication on restart19:18
* fungi celebrates19:18
corvusyay!  and the ssh timeout too, right?19:18
clarkband they have hour long ssh timeouts (I even tested this on review-dev with a stream-events connection. I don't think review.o.o is ever idle long enough to hit that so will depend on sad clients)19:18
clarkbcorvus: yup19:19
fungigranted, the upcoming rename restart will still need a reindex19:19
corvusfungi: yeah, we can target just the renamed projects though for that i think?19:19
fungioh, wait, replication19:19
fungiright19:19
clarkbya we can do targetted replication19:19
clarkband reindexing is online19:19
fungii think the rename process doesn't need rereplication19:19
clarkbshouldn't19:20
*** pcaruana has quit IRC19:20
fungigerrit needs reindexing, but that only happens automatically on restarts for upgrades19:20
fungii was confusing the two. sorry!19:20
clarkbAny other config management related business?19:20
funginada19:20
clarkb#topic Storyboard19:21
*** openstack changes topic to "Storyboard (Meeting topic: infra)"19:21
clarkbfungi: diablo_rojo_phon any news to share?19:21
fungii've been entirely disconnected for the past week, so while i don't think so i really don't know19:21
clarkbsilly hurricanes interrupting work19:21
fungithey should do a better job of scheduling those, yes19:22
fungidiablo_rojo_phon: may also not be on hand at the moment19:23
fungiSotK: ?19:23
fungiguessing we can move on. i'll hopefully have things to talk about next week as i get back into gear19:24
clarkbk19:24
clarkb#topic General Topics19:24
*** openstack changes topic to "General Topics (Meeting topic: infra)"19:24
clarkb#link https://etherpad.openstack.org/p/201808-infra-server-upgrades-and-cleanup19:24
clarkbFirst up is server cleanups19:24
clarkbI don't expect much movement happened on the wiki what with hurricanes and other fires19:25
clarkbfor static.o.o I think we now have a relatively complete list of tasks to be able to delete that server19:25
clarkb#link https://etherpad.openstack.org/p/static-services Sign up for tasks19:25
fungii've been pretty useless for the last week, yes, apologies19:25
clarkbthank you ajaeger for jumping on that already. If the rest of us can grab one or two of those we should be able to make good progress on it19:25
clarkbianw: ^ did you have anything else to add re static.o.o and your auditing?19:26
ianwno; we didn't really come to a conclusion on the redirects ... but we can defer that until the harder things like afs publishing are done19:26
clarkbok19:27
clarkbThat is a good transition into the next topic: AFS stability19:27
clarkbwe discovered that afs02.dfw.o.o was very unhappy last week. It looked like fallout from a live migration based on console content (I seem to recall similar messages from hosts that we were told had been migrated)19:27
clarkbcorvus rebooted it19:28
clarkbunfortunately that left some volumes locked. ianw has since fixed all of those but the opensuse mirror volume (is that correct?)19:28
clarkbI have also turned mirror-update.openstack.org back on but left mirror-update.opendev.org alone19:28
corvusoh, huh, i thought i checked that after rebooting19:28
corvuswhat steps should we have done after the reboot?19:28
clarkbianw: ^ can fill us in on his investigation and next steps19:29
ianwyes the opensuse mirror had a release error; something we've seen before and made a thread about on openafs lists (see updates in #openstack-infra)19:29
*** mattw4 has joined #openstack-meeting19:29
ianwi've tried the salvage recovery steps they suggest and an re-running the opensuse release19:29
clarkbcorvus: I believe that subsequent vos releases ended up timing out their auth (and this may have happend after the reboot)19:30
ianwcorvus: i think maybe everything needed to recreate r/o and everything timed out19:30
ianwor what clarkb said :)19:30
corvusoh. huh.  wonder why it needed to redo r/o19:31
clarkbso ya immediately after the reboot I think it was fine19:31
corvusso the short version of the recovery process is pause release activity before rebooting a server; after it boots, clean up any broken releases; perform a release on every volume manually on the db servers; unpause releases"  ?19:32
clarkbcorvus: yes I think that would do it mroe gracefully19:32
corvusis there a doc update with that, or should i write that up real quick?19:33
ianwyeah, possibly -- here's where ubuntu went wrong : http://paste.openstack.org/show/774655/19:33
clarkbcorvus: I am not aware of a doc update for that yet. I think you can write it19:33
*** mattw4 has quit IRC19:33
ianwso it's not exactly like "recreating r/o"19:33
ianwi haven't audited the logs of all the other ones to see what happened, but we could19:34
clarkbsounds like that may be it for this topic? lets move on as I want to finish before 2000UTC19:36
clarkbNext up is project renaming on Monday at 1400UTC that is 7am Pacific19:36
clarkb#link https://etherpad.openstack.org/project-renames-2019-09-10 Planning document19:37
*** panda|rover|off has quit IRC19:37
clarkbI've just started editing ^ based on the one we did at the end of may19:37
clarkbfrom that I need to write a chagne for the repos.yaml content19:37
clarkband need to get the project-config rename chagnes in order19:37
clarkbOne question I did have is whether or not the libification of gitea management affects our rename playbook at all19:37
clarkbI don't think it does because rename playbook should call into that like the normal ansible runs do too19:38
clarkbbut I'll look at that as well19:38
corvus#link https://review.opendev.org/681338 Add docs for recovering an OpenAFS fileserver19:38
*** panda has joined #openstack-meeting19:38
clarkbmonty said he would be around monday and early pacific time would work for him. fungi I think you said that works too, does it still work post hurricane?19:39
clarkb(and anyone else should feel free to help too :) )19:40
fungiyeah, it's fine. i'll be here with bells on19:40
clarkbgreat I'll see you all there then19:40
clarkbNext up is volume of ara file in ara reports is making ceph sad19:41
clarkbWanted to bring this up to cover the changes we made really quickly19:41
clarkbfirst corvus updated the zuul dashboard to largely cover our needs there via the job output json file19:41
clarkbcorvus: do we still need to get that fix for handlers merged? or do we just need an executor erstart for that?19:42
corvuser 1 sec; i'm unprepared :)19:42
corvushttps://review.opendev.org/680726 is unmerged, but not very important19:43
clarkbinterseting that zuul didn't enqueue it when its parent merged19:44
corvusthe current output is misleading if ansible "handler" tasks are used, but they don't get used that often in the main body of jobs19:44
clarkbin any case we stopped running ara for every job19:44
clarkbnested ara runs are still there but the root report is no longer a thing19:44
clarkbthat should cut back on our total object count for log files in swift/ceph19:44
corvusclarkb: it did; but zuul's gate pipeline doesn't honor 'recheck'19:44
clarkbthe other major chagne we made was to shard logs into containers based on the first three chars of the build uuid19:44
clarkbwe should get 4096 containers in each cloud region to shard logs into as a result19:45
clarkbhopeflly that spreads things out well19:45
clarkbcorvus: ah19:45
clarkband as of this mornign all swifts are back in service19:45
corvusi still consider the current state an emergency fix... and we should figure out what to do about nested aras19:45
clarkbcorvus: k19:45
clarkbvexxhost is the last remaining cloud we've kept out (it is ceph)19:45
clarkbI think as soon as mnaser is ready for us to try using vexxhost again we can go ahead and do that19:46
corvuswe know that we have reduced the file count by turning off the zuul-ara, but we don't know what proportion of the files that was compared to nested-ara -- meaning we don't know how much of an impact the nested-aras will continue to be19:47
corvusi suspect it's still significant, and if so, it would be good to come up with another option there19:47
clarkbcorrect. We have also removed hot containers like periodic/ by replacing them with the build uuid sharded containers19:47
corvusthere was an etherpad with ideas, right?19:48
corvusdmsimard: ping19:48
clarkb#link https://etherpad.openstack.org/p/Vz5IzxlWFz ARA file count reduction ideas19:48
corvusi feel like #2 isn't worth the gain19:49
fungiyeah, i got the impression some of those nested aras reported on orders of magnitude more ansible tasks than our job ara19:49
corvusif that's the case, then turning off zuul-ara may not change as much as we'd hoped.19:49
clarkbfungi: but we run an order of magnitude fewer jobs for them (I think)19:49
corvusmaybe that cancels out?19:49
fungithe number of tasks involved in, e.g., deploying a complete openstack is waaaay more than to run a typical zuul job19:50
fungibut yes, hard to know due to the difference in frequency19:50
clarkbnested ara is just system-config jobs, osa, and tripleo19:50
clarkb(at least those are the ones I know of)19:50
corvusit's "just tripleo" i'm worried about :)19:50
clarkbya that could be significant (though their use of resources is more due to running long multinode jobs than many many jobs I think)19:51
corvuslooking at the etherpad, broadly, i see only two ways to improve this: 1) use a static server; 2) do more in javascript19:51
dmsimardhi, I'm here19:51
fungithose were basically the two possible roads i was aware of19:51
fungido more server-side (so not in swift since we can't provide our own swift middleware), or do more on the client side (so probably with js)19:52
corvusif we need to do something urgently, #1 (static server) is probably the only thing that will do.   if our effort so far has given us some breathing room, we can look into #2 (javascript development)19:52
clarkbcorvus: I think the current swift clouds have no problem with the existing setup (at least I've not heard complaints)19:53
clarkbcorvus: given that I think we do have breathing room19:53
dmsimardusing the sqlite middleware is my preferred option, it was designed to solve this exact problem19:53
dmsimardI do not have the javascript skills to take on the other option19:53
fungiwe'll presumably know more for sure as we approach our retention19:53
fungiabout whether it's a strain on them19:54
clarkbfungi: ya and donnyd can likely give us detailed info19:54
corvusi'm not opposed to using a static server; i'm opposed to being personally responsible for sysadmining one19:54
clarkbhttps://grafana.fortnebula.com/d/9MMqh8HWk/openstack-utilization?orgId=2&refresh=30s publishes swift info from FN19:55
corvusi'm over-extended (as i think the team is), so i'm trying to simplify both the system and our responsibilities, so i'd still like to avoid that if possible19:55
donnydyea, and there is little in the way of load on those swift servers19:55
clarkbcorvus: ++ also we've found that there are problems with sysadmining such a system even if we have all the time to do it19:55
donnydI can also grab any other stats needed and publish them19:55
clarkbparticularly around device limits and volume attachments (one alternative we considered was ceph but if it has problems with the object store version of this will it have problems with the block/fs version?)19:56
donnydi am 2x on objects, so what you see there you can /219:56
corvusdmsimard: we talked about maybe zuul and ara sharing some react widgets... maybe we can find a way to combine zuul's "load data from json" approach with ara?19:57
donnydI am about to move swift to nvme so it really won't matter on my end at all19:57
clarkb(as a timecheck we have just under 3 minutes left in the meeting but this was the agenda so we can talk about ara until then)19:57
clarkbmore than happy to have further discussion in #openstack-infra on this topic or any other afterwards too19:57
corvusdmsimard: i don't know what that looks like, or how to do it, but i feel like there should be something we can do to start converging19:58
dmsimardcorvus: yes, I believe it was tristanC who came up with that. I'll be at the office with him tomorrow, will bring it up.19:58
corvusdmsimard: cool -- why don't the 2 of you bat around some ideas, and then maybe the 3 of us can have a conference call or something afterwords?19:59
dmsimardsounds like a plan20:00
clarkband we are at time. Thank you everyone!20:00
clarkb#endmeeting20:00
corvus(others welcome too of course; mostly just trying to get some effective brainstorming/design time to get something started)20:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"20:00
openstackMeeting ended Tue Sep 10 20:00:10 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-09-10-19.01.html20:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/infra/2019/infra.2019-09-10-19.01.txt20:00
openstackLog:            http://eavesdrop.openstack.org/meetings/infra/2019/infra.2019-09-10-19.01.log.html20:00
corvusdmsimard: thanks!20:00
*** Shrews has left #openstack-meeting20:00
fungitank yuh, clarkb!20:00
*** enriquetaso has quit IRC20:15
*** e0ne has quit IRC20:19
*** ociuhandu has joined #openstack-meeting20:37
*** ociuhandu has quit IRC20:52
*** ociuhandu has joined #openstack-meeting20:53
*** ociuhandu has quit IRC20:57
*** shubham_potale has quit IRC21:02
*** raildo has quit IRC21:06
*** hemna has joined #openstack-meeting21:29
*** hemna has quit IRC21:34
*** jamesmcarthur has joined #openstack-meeting21:35
*** mriedem has quit IRC21:37
*** aloga has quit IRC21:45
*** hemna has joined #openstack-meeting21:57
*** jamesmcarthur has quit IRC22:14
*** jamesmcarthur has joined #openstack-meeting22:15
*** jamesmcarthur has quit IRC22:17
*** jamesmcarthur has joined #openstack-meeting22:18
*** slaweq has quit IRC22:21
*** jamesmcarthur has quit IRC22:21
*** jamesmcarthur has joined #openstack-meeting22:24
*** panda has quit IRC22:26
*** panda has joined #openstack-meeting22:28
*** aloga has joined #openstack-meeting22:29
*** ociuhandu has joined #openstack-meeting22:30
*** ociuhandu has quit IRC22:35
*** jamesmcarthur has quit IRC22:37
*** brault has joined #openstack-meeting22:43
*** jamesmcarthur has joined #openstack-meeting22:44
*** hemna has quit IRC22:50
*** mattw4 has joined #openstack-meeting22:55
*** jamesmcarthur has quit IRC22:57
*** brault has quit IRC22:59
*** rcernin has joined #openstack-meeting22:59
*** mattw4 has quit IRC23:00
*** macz has quit IRC23:05
*** slaweq has joined #openstack-meeting23:11
*** slaweq has quit IRC23:15
*** jamesmcarthur has joined #openstack-meeting23:18
*** jamesmcarthur has quit IRC23:21
*** jamesmcarthur has joined #openstack-meeting23:23
*** _pewp_ has joined #openstack-meeting23:24
*** jamesmcarthur has quit IRC23:26
*** jamesmcarthur has joined #openstack-meeting23:31
*** ykatabam has joined #openstack-meeting23:32
*** mlavalle has quit IRC23:37
*** jamesmcarthur has quit IRC23:41
*** mtreinish has quit IRC23:43
*** mtreinish has joined #openstack-meeting23:48
*** ykatabam has quit IRC23:52

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