Tuesday, 2018-08-07

*** tetsuro_ has quit IRC00:01
*** gyee has quit IRC00:06
*** Nel1x has joined #openstack-meeting00:09
*** zhurong has joined #openstack-meeting00:23
*** harlowja has quit IRC00:26
*** bobh has quit IRC00:28
*** longkb has joined #openstack-meeting00:37
*** tetsuro_ has joined #openstack-meeting00:44
*** ykatabam has quit IRC01:00
*** ykatabam has joined #openstack-meeting01:00
*** tetsuro_ has quit IRC01:01
*** hongbin has joined #openstack-meeting01:03
*** erlon has joined #openstack-meeting01:06
*** tetsuro_ has joined #openstack-meeting01:09
*** erlon has quit IRC01:13
*** mriedem has quit IRC01:15
*** erlon has joined #openstack-meeting01:26
*** zhurong has quit IRC01:26
*** tetsuro_ has quit IRC01:27
*** tetsuro_ has joined #openstack-meeting01:28
*** ricolin has joined #openstack-meeting01:29
*** tetsuro_ has quit IRC01:34
*** tetsuro_ has joined #openstack-meeting01:41
*** tetsuro_ has quit IRC01:44
*** tetsuro_ has joined #openstack-meeting01:53
*** naichuans has joined #openstack-meeting02:12
*** bobh has joined #openstack-meeting02:13
*** lbragstad has quit IRC02:18
*** tetsuro_ has quit IRC02:19
*** tetsuro_ has joined #openstack-meeting02:23
*** tetsuro_ has quit IRC02:26
*** bobh has quit IRC02:34
*** psachin has joined #openstack-meeting02:40
*** erlon has quit IRC02:45
*** tetsuro_ has joined #openstack-meeting02:50
*** tpatil has joined #openstack-meeting02:53
*** markstur_ has quit IRC02:53
*** tetsuro__ has joined #openstack-meeting02:53
*** tetsuro_ has quit IRC02:54
*** markstur has joined #openstack-meeting02:55
*** tetsuro__ has quit IRC02:59
*** markstur has quit IRC03:00
tpatil#startmeeting Masakari03:01
openstackMeeting started Tue Aug  7 03:01:42 2018 UTC and is due to finish in 60 minutes.  The chair is tpatil. Information about MeetBot at http://wiki.debian.org/MeetBot.03:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.03:01
openstackThe meeting name has been set to 'masakari'03:01
tpatilHi All03:01
*** wanghao has joined #openstack-meeting03:02
tpatilWill wait for 10 mins as some of them must be facing registration issue. If no one joins during this time, I will end this meeting.03:05
*** samP has joined #openstack-meeting03:12
tpatilHi samP03:12
tpatilI have started the meeting03:12
samPtpatil: sorry Im late03:13
tpatilNP03:13
tpatilPlease take the pilot seat03:13
samPtpatil: thanks,03:13
samP#topic Any critical bugs/patches03:13
samPI guess commands are not working for me :)03:14
*** jhesketh_ is now known as jhesketh03:14
samPAnyway, is there any patches or bugs need to discuss?03:14
tpatil#topic Any critical bugs/patches03:14
samP#link https://review.openstack.org/#/c/588157/03:14
tpatilhttps://bugs.launchpad.net/masakari/+bug/177975203:15
openstackLaunchpad bug 1779752 in masakari "masakari segment-list returns error (openstack queens)" [Critical,Confirmed] - Assigned to SamP (sampath-priyankara)03:15
tpatilShilpa has proposed a patch to fix about issue in stable/queens03:15
tpatils/about/above03:15
samPI tested this patch. LGTM03:16
tpatilit will work with openstacksdk >=0.11.003:16
tpatilbut stable/queens also supports 0.9.19 and 0.10.003:16
tpatilso I have requested Shilpa to add a user friendly message if sdk version is above two and call sys.exit03:17
samPyep, that is the problem03:17
tpatilso users will be aware to use sdk >0.11.003:17
tpatilWhat is your opinion?03:17
samPtpatil: That means, users are force to use >0.11.003:18
tpatilyes03:18
tpatilor we can update requirements lower constraints to 0.11.003:18
tpatilin requirements project for stable/queens branch03:19
samPtpatil: updating the lower constraints to 0.11.0 seems a good idea.03:19
tpatilmee too03:19
samPIn that case, we dont need to worry about lower versions.03:19
tpatilcorrect03:20
samPOK then, Let's give it a try with Shilpa's current patch.03:20
samPThere is a very less chance that someone use python-masakariclient with sdk > 0.11.0.03:21
samPHowever, as OpenStack we must support all the versions as it is in requirement.03:21
tpatilI will request Shilpa to upload a patch to change the lower constraints in requirements project from 0.9.19 to 0.11.003:22
tpatilis it ok?03:22
*** Nel1x has quit IRC03:22
samPtpatil: sure, thanks. Let's submit the patch to raise the lower constraints to 0.11.003:22
tpatilok, will do03:23
samPThanks03:23
tpatilsame issue is also there in masakari-monitors03:24
tpatilShilpa will upload a patch soon to fix this issue in masakari-monitors03:25
*** diablo_rojo has quit IRC03:25
samPtpatil: thanks. not the master but the stable/queens right/03:25
tpatilyes03:25
tpatilone observation, masakari-monitors is not using openstackclient but it's still present in requirements.txt03:25
tpatilwe will fix this issue in master branch. Do you think it should be back ported to stable/queens branch as well?03:27
samPtpatil: seems like it. sure, we can backport this03:29
tpatilok, will upload patches soon to fix this issue as well03:29
tpatilI will report a LP bug for this03:29
samPwe have to release new version for stable/queens anyway. let's include this too03:30
tpatilit's trivial fix03:30
samPtpatil: thanks03:30
tpatilsamP: Sure03:30
samPEnd of this week is the deadline for the RC1 tag and cut off the stable/rocky03:31
tpatilRecovery customization patch is up for review03:32
*** niraj_singh has joined #openstack-meeting03:33
samPtpatil: ah..yes.03:33
tpatilhttps://review.openstack.org/#/c/583127/03:33
tpatilPooja has fixed the unit tests issue and uploaded a new PS03:34
samPI will take a look again.03:34
*** liuyulong has joined #openstack-meeting03:34
samPLast time I look it was OK. wont take much time.03:34
samPThanks for the reminder03:35
samPI will try to merge this before rc1.03:36
tpatilYes, please03:36
*** markstur has joined #openstack-meeting03:37
samPEnd of this week, I will propose patches to release rc1 for masakari, masakari-monitors03:37
samPstable/rocky for masakari, masakari-monitors, masakari-dashboard03:37
samPAnd will release new version for masakari-dashboard03:38
tpatilOk, Great03:39
samPAnd from next week, we will be able to work on master for Stein03:39
*** tetsuro_ has joined #openstack-meeting03:39
samPAny other issues to discuss?03:40
tpatilAny deadline to fix masakariclient and masakari-monitors issue in stable/queens?03:40
*** janki has joined #openstack-meeting03:41
samPNo deadline, but sooner the better03:42
*** markstur has quit IRC03:42
tpatilyes, masakari-monitor and requirement patches will be uploaded soon, maybe by tomorrow03:43
samPAnd I have to announce the deprecation of python-masakariclient in Stein03:43
samPtpatil: sure, thanks.03:43
tpatilIs it possible to change IRC meeting time to it's original one?03:45
tpatili.e. 1:00 JST -> 4:00 UTC03:46
samPtpatil: sure. I think we can change it back. or bring it 1h early, from 11:00-12:00?03:47
*** tetsuro_ has quit IRC03:47
tpatilInitially we had change IRC meeting timing in the hope that more people can join meeting. But I could see anyone join this meeting for last 1-2 months.03:47
samPtpatil: unfortunately, agree ;)03:48
tpatilIt's better 1:00 - 2:00 P.M becoz India people can join during this time03:48
*** tetsuro_ has joined #openstack-meeting03:48
samPtpatil: great, then let's change it back03:48
tpatilThank you03:49
tpatilAre you going to propose a patch to change meeting time?03:49
samPtpatil: sure I will03:49
tpatilThanks03:50
tpatilWill this change be effective from next meeting?03:50
tpatilI guess after your patch is approved, it will be effective03:50
samPtpatil: Let's do it form next week meeting. If some one need to change it, let's consider it then03:51
*** tetsuro_ has quit IRC03:51
tpatilsamP: Sure03:51
samPtpatil: yes, I can ask them to approve it asap03:51
tpatilGreat!!!03:52
samPI think we can conduct this meeting in #openstack-masakari03:53
tpatilyou mean weekly IRC meeting?03:53
samPtpatil: yes.03:53
tpatilThat's great then, it won't conflict with other team meetings at all.03:54
samPbots are there. I need to try it.03:54
samPlet me try it, and if it work I will propose to change the channel also.03:54
tpatilSounds good03:55
samP#openstack-masakari channel is currently been logged,03:55
tpatilyes03:55
samPOK then, I will propose those changes03:55
samPAny other items to discuss, we have 5 mins left03:56
tpatilNo03:56
samPtpatil: thanks03:56
samPLet's finish today's meeting then03:56
samPThank you for your time03:56
tpatilOk, I will end this meeting03:56
tpatilThank you03:56
tpatil#endmeeting03:56
openstackMeeting ended Tue Aug  7 03:56:51 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)03:56
openstackMinutes:        http://eavesdrop.openstack.org/meetings/masakari/2018/masakari.2018-08-07-03.01.html03:56
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/masakari/2018/masakari.2018-08-07-03.01.txt03:56
openstackLog:            http://eavesdrop.openstack.org/meetings/masakari/2018/masakari.2018-08-07-03.01.log.html03:56
samPtpatil: thanks03:56
*** jaypipes has quit IRC04:02
*** jaypipes has joined #openstack-meeting04:02
*** tpatil has quit IRC04:10
*** tetsuro_ has joined #openstack-meeting04:12
*** bdperkin has quit IRC04:14
*** hongbin has quit IRC04:15
*** markstur has joined #openstack-meeting04:18
*** markstur has quit IRC04:23
*** markstur has joined #openstack-meeting04:39
*** bdperkin has joined #openstack-meeting04:44
*** markstur has quit IRC04:44
*** e0ne has joined #openstack-meeting05:00
*** markstur has joined #openstack-meeting05:00
*** markstur has quit IRC05:05
*** tetsuro_ has quit IRC05:15
*** psachin has quit IRC05:18
*** markstur has joined #openstack-meeting05:21
*** tetsuro_ has joined #openstack-meeting05:22
*** psachin has joined #openstack-meeting05:25
*** markstur has quit IRC05:26
*** tetsuro_ has quit IRC05:27
*** cloudrancher has joined #openstack-meeting05:31
gmanndhellmann: +105:42
*** e0ne has quit IRC05:58
*** tetsuro_ has joined #openstack-meeting05:59
*** aagate has quit IRC06:01
*** apetrich has joined #openstack-meeting06:01
*** e0ne has joined #openstack-meeting06:02
*** tetsuro_ has quit IRC06:02
*** tetsuro_ has joined #openstack-meeting06:02
*** cloudrancher has quit IRC06:12
*** markstur has joined #openstack-meeting06:30
*** pcaruana has joined #openstack-meeting06:36
*** markstur has quit IRC06:36
*** tetsuro_ has quit IRC06:36
*** cloudrancher has joined #openstack-meeting06:49
*** markstur has joined #openstack-meeting06:52
*** cloudrancher has quit IRC06:52
*** markstur has quit IRC06:56
*** e0ne has quit IRC07:02
*** ykatabam has quit IRC07:19
*** wznoinsk has quit IRC07:27
*** wznoinsk has joined #openstack-meeting07:27
*** markstur has joined #openstack-meeting07:34
*** e0ne has joined #openstack-meeting07:35
*** markstur has quit IRC07:39
*** ahrechny has joined #openstack-meeting07:39
*** e0ne has quit IRC07:41
*** e0ne has joined #openstack-meeting07:52
*** e0ne has quit IRC07:53
*** apetrich has quit IRC07:56
*** yamamoto has joined #openstack-meeting08:00
*** akhil_jain has joined #openstack-meeting08:01
*** kopecmartin has joined #openstack-meeting08:03
*** ahrechny has left #openstack-meeting08:07
*** ahrechny has joined #openstack-meeting08:07
*** yamamoto has quit IRC08:07
*** phuoc has joined #openstack-meeting08:08
*** rcernin has quit IRC08:11
*** boden has joined #openstack-meeting08:14
*** markstur has joined #openstack-meeting08:17
*** ykatabam has joined #openstack-meeting08:17
*** boden has quit IRC08:19
*** markstur has quit IRC08:21
*** electrofelix has joined #openstack-meeting08:33
*** DaisukeHara has joined #openstack-meeting08:35
*** markstur has joined #openstack-meeting08:38
*** markstur has quit IRC08:43
*** ahrechny has quit IRC08:45
*** yamamoto has joined #openstack-meeting08:46
*** tetsuro_ has joined #openstack-meeting08:53
*** priteau has joined #openstack-meeting08:55
*** markstur has joined #openstack-meeting08:59
*** markstur has quit IRC09:04
*** yamamoto has quit IRC09:11
*** DaisukeHara has quit IRC09:15
*** markstur has joined #openstack-meeting09:21
*** markstur has quit IRC09:25
*** finucannot is now known as stephenfin09:30
*** wanghao has quit IRC09:32
*** ykatabam has quit IRC09:43
*** tetsuro_ has quit IRC09:45
*** tetsuro_ has joined #openstack-meeting09:45
*** niraj_singh has quit IRC09:50
*** tetsuro_ has quit IRC09:59
*** tetsuro has joined #openstack-meeting09:59
*** electrofelix has quit IRC10:18
*** tetsuro has quit IRC10:21
*** electrofelix has joined #openstack-meeting10:26
*** tetsuro has joined #openstack-meeting10:28
*** tetsuro has quit IRC10:28
*** liuyulong has quit IRC10:45
*** ricolin has quit IRC10:58
*** artom has joined #openstack-meeting11:11
*** slagle has joined #openstack-meeting11:39
*** apetrich has joined #openstack-meeting11:53
*** boden has joined #openstack-meeting11:56
*** erlon has joined #openstack-meeting11:56
*** boden has left #openstack-meeting11:58
*** raildo has joined #openstack-meeting12:02
*** raildo has quit IRC12:03
*** edmondsw has joined #openstack-meeting12:04
*** raildo has joined #openstack-meeting12:06
*** raildo has quit IRC12:07
*** tpsilva has joined #openstack-meeting12:07
*** raildo has joined #openstack-meeting12:15
*** e0ne has joined #openstack-meeting12:40
*** bollig has quit IRC12:50
*** cebruns_ has quit IRC12:50
*** weshay has quit IRC12:50
*** samP has quit IRC12:53
*** bobh has joined #openstack-meeting12:54
*** vgreen has joined #openstack-meeting12:58
*** dklyle has quit IRC12:59
*** janki has quit IRC13:03
*** janki has joined #openstack-meeting13:04
*** tssurya has joined #openstack-meeting13:07
*** lbragstad has joined #openstack-meeting13:11
*** longkb has quit IRC13:13
*** mriedem has joined #openstack-meeting13:16
*** chenyb4 has joined #openstack-meeting13:21
*** eharney has joined #openstack-meeting13:22
*** dustins has joined #openstack-meeting13:23
*** r-mibu has joined #openstack-meeting13:42
*** aagate has joined #openstack-meeting13:42
*** mjturek has joined #openstack-meeting13:43
*** chenyb4 has quit IRC13:44
*** psachin has quit IRC13:51
*** awaugama has joined #openstack-meeting14:05
*** jamesmcarthur has joined #openstack-meeting14:05
*** dklyle has joined #openstack-meeting14:33
*** longkb has joined #openstack-meeting14:35
*** hongbin has joined #openstack-meeting14:38
*** e0ne has quit IRC14:39
*** markstur has joined #openstack-meeting14:44
*** markstur has quit IRC14:49
*** priteau has quit IRC14:50
*** markstur has joined #openstack-meeting14:56
*** bobh has quit IRC14:56
*** lamt has joined #openstack-meeting15:02
*** longkb has quit IRC15:05
*** mriedem is now known as mriedem_afk15:06
*** pcaruana has quit IRC15:11
*** hemna_ has joined #openstack-meeting15:12
*** bobh has joined #openstack-meeting15:17
*** bobh has quit IRC15:17
*** markstur_ has joined #openstack-meeting15:18
*** markstur has quit IRC15:20
*** priteau has joined #openstack-meeting15:26
*** gyee has joined #openstack-meeting15:32
*** bobh has joined #openstack-meeting15:45
slaweq#startmeeting neutron_ci16:00
openstackMeeting started Tue Aug  7 16:00:20 2018 UTC and is due to finish in 60 minutes.  The chair is slaweq. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
openstackThe meeting name has been set to 'neutron_ci'16:00
*** mlavalle has joined #openstack-meeting16:00
slaweqhi16:00
mlavalleo/16:00
*** wxy|xiyuan has joined #openstack-meeting16:00
slaweqhi mlavalle16:01
slaweqlets wait few minutes for others maybe16:01
*** akhil_jain has left #openstack-meeting16:01
*** onovy has quit IRC16:01
mlavalledid you throw a party during your home mancation?16:01
slaweqno, I didn't16:01
mlavalleLOL16:01
*** armstrong has joined #openstack-meeting16:02
mlavalleI wouldn't either. I live in perpetual fear of my wife16:02
slaweqbut funny thing was, last week I told my wife about this term "mancation" and I explained here what it means16:02
slaweqshe then asked me when she will be on "womencation"16:02
slaweqI told her that she is already (with kids) - she was a bit angry for me :D16:03
mlavalleLOL16:03
slaweqok, I think we will start16:04
slaweq#topic Actions from previous meetings16:04
slaweqmlavalle to check dvr (dvr-ha) env and shelve/unshelve server16:04
mlavalleI did16:04
mlavalleJust filed this bug: https://bugs.launchpad.net/neutron/+bug/178584816:05
openstackLaunchpad bug 1785848 in neutron "Neutron server producing tracebacks with 'L3RouterPlugin' object has no attribute 'is_distributed_router' when DVR is enabled" [Medium,New] - Assigned to Miguel Lavalle (minsel)16:05
*** wxy|xiyuan has quit IRC16:05
mlavalleIn a nutshell, this patch https://review.openstack.org/#/c/579058 introduced a bug16:05
*** r-mibu has quit IRC16:06
mlavallelook at https://review.openstack.org/#/c/579058/3/neutron/db/l3_dvrscheduler_db.py@46016:06
slaweqI noticed those errors in neutron logs this week and I wanted to ask about it later :)16:06
mlavalleit is trying to call is_distributed_router in the l3_plugin16:06
slaweqmlavalle: do You think we should do it for RC1 or it's not so important?16:06
mlavalleit is probably good is we fix it16:07
slaweq*do it => fix16:07
mlavalleI'll push a patch at the end of this meeting16:07
mlavallelet's see what haleyb thinks16:07
slaweqgreat16:07
slaweqthx16:07
haleybhi16:07
slaweqhi haleyb16:07
*** onovy has joined #openstack-meeting16:08
slaweqok, let's go to the next one then16:08
slaweqnjohnston to tweak stable branches dashboards16:08
slaweqI don't know if he did anything about that this week16:08
slaweqlet's check it next week, ok?16:09
mlavallehe is off today16:09
mlavalleand tomorrow as well16:09
slaweqyes, I know16:09
mlavalleI know because he came collecting debts late last week16:09
mlavalleI got an action item from him last meeting16:10
*** mriedem_afk has quit IRC16:11
slaweqso do You think we can move it to next week to check then?16:11
mlavalleyou mean the stable dashboard?16:12
slaweqyes16:12
mlavalleyeah16:12
slaweq#action njohnston to tweak stable branches dashboards16:12
slaweqthx16:12
slaweqnext one:16:12
slaweqslaweq to talk with infra about gaps in grafana graphs16:12
slaweqI did16:12
slaweqI talked with ianw, he explained me that it was like that all the time probably, maybe some setting changed during grafana upgrade and that’s why it’s visible now16:13
slaweqWe can change nullPointMode to connected mode to make it „not visible” in dashboard config, but I don't know if we want to do that16:13
slaweqwhat You think? is it necessary to change?16:13
*** jaypipes_ has joined #openstack-meeting16:16
mlavalleMhhh16:16
mlavalleI don't think it's worth it16:16
mlavalleif it's been there all the time, maybe we just should get used to it16:17
*** jaypipes has quit IRC16:17
*** jaypipes_ has quit IRC16:17
*** e0ne has joined #openstack-meeting16:18
slaweqexactly, that's it's what I think16:18
slaweqbut wanted to ask You, as our boss ;)16:18
mlavalleI am just another contributor with some additional duties16:18
slaweqmlavalle: :)16:18
*** armax has joined #openstack-meeting16:19
slaweqok, let's move on to the next one16:19
slaweqslaweq to report a bug with failing neutron.tests.functional.db.migrations functional tests16:19
slaweqI did it: https://bugs.launchpad.net/neutron/+bug/178483616:19
openstackLaunchpad bug 1784836 in neutron "Functional tests from neutron.tests.functional.db.migrations fails randomly" [Medium,Confirmed]16:19
slaweqbut it's not assigned to anybody yet16:19
slaweqnext one:16:19
slaweq* slaweq to check tempest delete_resource method16:19
slaweqso I checked it and there is nothing to fix in tempest16:20
slaweqIt was caused by very slow processing of DELETE network call by neutron: http://logs.openstack.org/01/584601/2/check/neutron-tempest-dvr/65f95f5/logs/tempest.txt.gz#_2018-07-27_22_42_11_57716:20
slaweqBecause of that client repeated the call after http_timeout but then network was already deleted by neutron (from first call) and that’s the issue.16:20
slaweqso we have sometimes very slow API - I know that njohnston was woring recently on some improvements for that16:20
mlavalleshould we discuss this in the PTG?16:21
slaweqthat's good idea16:22
slaweqit hits us in many tests and quite often from what I can see in different job's results16:22
*** phuoc has left #openstack-meeting16:22
mlavalleso I propose you add a topic to the etherpad and gather some data to disucss in Denver16:22
slaweqok, I will do that16:22
mlavalleThanks16:23
slaweq#action slaweq add data about slow API to etherpad for PTG16:23
slaweqso, next one16:23
slaweq* slaweq to check with infra if virt_type=kvm is possible in gate jobs16:23
mlavalleand you did16:23
mlavalleI think I reviewed a patch last week16:23
slaweqI again talked with ianw, clarkb and johnsom about it16:23
slaweqyes, I added patch to scenario jobs which uses zuulv3 syntax last week16:24
slaweqand also https://review.openstack.org/#/c/588465/ to use it in "legacy" jobs16:24
johnsomo/16:24
mlavalleahh cool16:25
slaweqas johnsom said they are using it for quite long time in octavia jobs and works fine16:25
slaweqhi johnsom :)16:25
mlavallehey johnsom :-)16:25
johnsomYeah, a kernel update to the nodepool images a few months back fixed the one issue we were seeing with guests crashing, otherwise it works great.16:26
johnsomSaves up to 50 minutes on some of our gates16:26
mlavallewow, that's great16:26
slaweqyes, I saw for our linuxbridge scenario job something like 40 minutes speed up IIRC16:26
slaweqso should be better I hope16:26
mlavalle++16:26
slaweqok, next one16:27
slaweq* slaweq to report a bug with tempest.scenario.test_security_groups_basic_ops.TestSecurityGroupsBasicOps.test_in_tenant_traffic16:27
slaweqDone: https://bugs.launchpad.net/neutron/+bug/178483716:27
openstackLaunchpad bug 1784837 in neutron "Test tempest.scenario.test_security_groups_basic_ops.TestSecurityGroupsBasicOps.test_in_tenant_traffic fails in neutron-tempest-dvr-ha-multinode-full job" [Medium,Confirmed]16:27
slaweqnext one:16:27
slaweqslaweq to send patch to add logging of console output in tests like tempest.scenario.test_security_groups_basic_ops.TestSecurityGroupsBasicOps.test_in_tenant_traffic16:27
slaweqPatch for tempest: https://review.openstack.org/#/c/588884/  merged today16:27
slaweqif I will find such issue again, we will be able maybe to check if vm was booted properly and how fast it was booted16:28
slaweqok, and finally last one from last week:16:28
mlavallecool16:28
slaweq* mlavalle will check with tc what jobs should be running with py316:28
mlavalleIt's actually an ongoing conversation16:28
*** electrofelix has quit IRC16:29
mlavalleI am talking to smcginnis about it16:29
mlavalleas soon as I finish that conversation, I'll report back16:29
slaweqthx mlavalle16:29
slaweqwe will be waiting then :)16:29
mlavallethat's the debt that njohnsgton collected ahead of time last week16:30
slaweqahh, ok :)16:30
slaweqlet's move on16:30
slaweqnext topic16:30
slaweq#topic Grafana16:31
slaweqhttp://grafana.openstack.org/dashboard/db/neutron-failure-rate16:31
slaweqand according to grafana I want to propose one small (maybe) improvement16:32
slaweqwhat You think about adding to graphs line with total number of tests16:32
*** lbragstad[m] has quit IRC16:32
slaweqthen we could see e.g.  for UT that there was 100% of failures but there were on e.g. 2 tests run and those 2 failed16:32
*** jaypipes has joined #openstack-meeting16:33
slaweqor graph with number of failed tests instead (or together) with % of failures16:33
mlavalleyeah, that's actually an excellent idea16:34
mlavallebecause that way we can understand quickly whether we have a trend or just a few outliers failling16:34
slaweqexactly16:34
slaweqlike now, e.g on UT graph it has spike to 100% but we don't know if it was one WIP patch rechecked few times or many patches failing with reason not related to change :)16:35
slaweqbut which do You think would be better? number of failures together with percentage on same graph?16:36
mlavallesounds good as a first step16:36
mlavallewe can experiment and tweak it as we learn more16:37
slaweqok, I will then try to add something like that this week16:37
slaweqthx for blessing :)16:37
mlavallethanks for improving our Grafana reporting :-)16:38
slaweq#action slaweq will add number of failures to graphana16:38
slaweqI'm trying to make my life easier just :P16:38
*** imacdonn has quit IRC16:38
*** imacdonn has joined #openstack-meeting16:38
slaweqspeaking about graphana, there are some spikes there from last week in few jobs16:38
slaweqbut I was trying to check and note failures during whole last week16:39
slaweqand I didn't found so many failures related to neutron, like it looks from graphs16:39
slaweq(that's why I had this idea of improving graphs)16:39
mlavalleyeap16:39
mlavalleit makes sense16:40
slaweqI saw that many patches were merged quite quickly during last week16:40
mlavallethat was my impression last week as well16:40
slaweqso maybe we can talk about some failures which I found16:40
slaweqlet's first talk about voting jobs16:40
slaweq#topic Integrated tempest16:41
slaweqthere were couple of errors which looks for me like slow neutron API or global timeouts (maybe also because of slow API)16:41
slaweqe.g.:16:41
slaweq    * http://logs.openstack.org/80/585180/3/check/tempest-full/1f62b43/testr_results.html.gz16:42
slaweq    * http://logs.openstack.org/31/585731/8/gate/tempest-full/ecac3d5/16:42
slaweq    * http://logs.openstack.org/59/585559/3/check/neutron-tempest-dvr/b4b7fda/job-output.txt.gz#_2018-08-01_08_45_22_47766716:42
slaweqand one with timeout and "strange" exception: http://logs.openstack.org/80/585180/3/gate/tempest-full-py3/5d2fb38/testr_results.html.gz16:42
slaweqthis last one looks for me like some race but I don't know between what this race could be16:44
slaweqI found it only once during last week16:44
slaweqdid You saw it before?16:44
mlavallenope16:44
mlavalledo you mean the HTTPSConnectionPool exception?16:44
*** tssurya has quit IRC16:45
slaweqno16:45
slaweqthis one unfortunatelly is quite "common"16:45
slaweqI was asking about error in tearDownClass (tempest.api.network.test_ports.PortsIpV6TestJSON)16:46
slaweqin http://logs.openstack.org/80/585180/3/gate/tempest-full-py3/5d2fb38/testr_results.html.gz16:46
mlavallethat may be a faulty test16:47
*** janki has quit IRC16:47
mlavallethat is not cleaning up after itself16:47
slaweqbut then it would be visible more often IMHO16:47
slaweqas it happens only once let's just be aware of this :)16:47
slaweqok?16:47
mlavalleyeah16:48
mlavalleI would check anyways if something changed with the test anyways16:48
mlavallebut I see your point16:48
slaweqand those HTTPSConnectionPool exceptions is different issue16:50
slaweqlooks e.g. on http://logs.openstack.org/80/585180/3/gate/tempest-full-py3/5d2fb38/controller/logs/screen-q-svc.txt.gz?level=INFO#_Aug_06_16_44_12_68539716:50
slaweqPOST took 80 seconds :/16:50
mlavalledang16:50
slaweqI will prepare more data like that to PTG etherpad16:50
mlavalleGreat16:51
slaweqbecause I think it happens quite often16:51
slaweqother issues which I saw in those tempest integrated jobs weren't related to neutron - most often some errors with volumes16:52
slaweqso let's move on to next jobs16:52
slaweq#topic Fullstack16:52
slaweqI found again test * neutron.tests.fullstack.test_securitygroup.TestSecurityGroupsSameNetwork.test_securitygroup(linuxbridge-iptables) failing sometimes16:52
slaweqit was always linuxbridge scenario, never ovs from what I seen16:53
slaweqand I spotted it only once in neutron-fullstack job16:53
slaweqbut at least 5 or sic times in neutron-fullstack-python3516:53
slaweqpy27:     * http://logs.openstack.org/27/534227/16/check/neutron-fullstack/2a475f6/logs/testr_results.html.gz16:53
slaweqpy35:     * http://logs.openstack.org/27/534227/16/check/neutron-fullstack-python35/f9e25c1/logs/testr_results.html.gz16:54
slaweqso I don't know if that is only coincidence or something works differently in py35 and that trigger issue more often16:55
slaweqI will report new issue for that and try to investigate it16:55
slaweqfine for You?16:55
mlavalleyes16:56
slaweq#action slaweq to report new bug about fullstack test_securitygroup(linuxbridge-iptables) issue and investigate this16:56
slaweqfrom other jobs, I have list of failures in scenario jobs16:57
slaweqbut it's mostly same issues like every week - many issues with shelve/unshelve, issues with volumes, some issues with FIP connectivity (randomly)16:58
slaweqbut we don't have time to talk about them now I think16:58
mlavallejust two things then16:58
slaweqgo on mlavalle16:58
mlavalle"part of what Doug is driving now is that everything should run using py3 except for those jobs explicitly testing py2"16:58
mlavallequote from smcginnis guidance regarding py3 testing16:59
mlavalleand next week I will be in China, so I won't be able to attend this meeting16:59
slaweqany actions I should take on it next week?17:00
slaweqor we should just wait?17:00
slaweqok, I think we are out of time now17:00
slaweqthx mlavale17:01
slaweqlet's talk on neutron channel more17:01
slaweq#endmeeting17:01
openstackMeeting ended Tue Aug  7 17:01:17 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_ci/2018/neutron_ci.2018-08-07-16.00.html17:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_ci/2018/neutron_ci.2018-08-07-16.00.txt17:01
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_ci/2018/neutron_ci.2018-08-07-16.00.log.html17:01
*** mlavalle has left #openstack-meeting17:02
*** armstrong has quit IRC17:02
*** jgriffith_pto is now known as jgriffith17:05
*** cloudrancher has joined #openstack-meeting17:09
*** kopecmartin has quit IRC17:13
*** dtrainor has quit IRC17:16
*** dtrainor has joined #openstack-meeting17:19
*** e0ne has quit IRC17:20
*** e0ne has joined #openstack-meeting17:21
*** e0ne has quit IRC17:22
*** cloudrancher has quit IRC17:22
*** ricolin has joined #openstack-meeting17:30
*** harlowja has joined #openstack-meeting17:31
*** harlowja has quit IRC17:43
*** markvoelker_ has quit IRC17:45
*** Leo_m has joined #openstack-meeting18:01
*** e0ne has joined #openstack-meeting18:04
*** Swami has joined #openstack-meeting18:12
*** AlanClark has joined #openstack-meeting18:21
*** bollig has joined #openstack-meeting18:25
*** bollig has left #openstack-meeting18:25
*** bollig has quit IRC18:25
*** bollig has joined #openstack-meeting18:25
*** ricolin has quit IRC18:27
*** apetrich has quit IRC18:35
*** Shrews has joined #openstack-meeting18:46
*** diablo_rojo has joined #openstack-meeting18:51
*** boden has joined #openstack-meeting18:54
*** boden has left #openstack-meeting18:54
*** jamesmcarthur has quit IRC18:58
*** jamesmcarthur has joined #openstack-meeting18:59
*** sdatko has joined #openstack-meeting18:59
clarkbHello, anyone here for the infra meeting?18:59
ianwo/18:59
clarkbwe'll get started in a couple minutes18:59
cmurphyo/19:00
sdatkohello o/19:00
Shrewso/19:00
corvuso/19:00
mordredo/19:01
clarkb#startmeeting infra19:01
openstackMeeting started Tue Aug  7 19:01:28 2018 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
openstackThe meeting name has been set to 'infra'19:01
*** bobh has quit IRC19:01
clarkb#link https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting#Agenda_for_next_meeting19:02
clarkb#topic Announcements19:02
clarkbhrm I guess bot isn't update topics right now (is it not oper?)19:02
*** diablo_rojo has quit IRC19:02
*** ChanServ sets mode: +o openstack19:03
fungihopefully that helps19:03
clarkbPTG is coming up. If we have time at end of meeting we might brainstorm agenda a bit19:03
fungi[i already had to do that once last week]19:03
fungi[[might be something is breaking +O mode]]19:04
clarkbI'll also put out an ethercalc link to figure out when is a good night to have biergarten trip in denver19:04
clarkbfungi: possibly related to +r?19:04
fungiyour guess is as good as mein19:04
ianwfungi: hrm, just rolled out changes to accessbot to mlock, that runs infrequently, i wonder if related19: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/2018/infra.2018-07-31-19.01.txt Minutes from last meeting19:05
clarkbNo explicit actions recorded, but mordred has been hard at work getting ansible things going, cmurphy's puppet-4 stack is almost completely merged, and ianw's spec for letsencrypt has been updated19:06
clarkbThank you everyone for pushing on that stuff19:06
clarkb#topic Specs approval19:06
*** openstack changes topic to "Specs approval (Meeting topic: infra)"19:06
clarkbianw: how are we feeling about https://review.openstack.org/#/c/563849/ now?19:07
* fungi has partially read, saw there was a new revision today19:08
clarkbThis is the 3rd party ci spec. I seem to recall we wanted to hold on it a bit, but not sure if that happened between now and last meeting or if that was last meeting19:08
ianwoh, i owed an update to that to focus on windmill, which i have failed to do19:08
clarkbah ok19:08
fungioh, wait, i was thinking of another spec19:08
clarkbin that case I won't propose we put it up for approval this week :)19:09
fungimissed that one too while on vacation but starred to catch up on19:09
clarkbfungi: thanks19:09
clarkb#topic Priority Efforts19:10
*** openstack changes topic to "Priority Efforts (Meeting topic: infra)"19:10
clarkbfungi: want to start with storyboard?19:10
fungioh, hrm19:10
* diablo_rojo_phon lurks19:10
clarkblooks like search changes are happening?19:10
diablo_rojo_phonYep :) fatema has been working on that19:11
funginame-based project urls are finally working on storyboard.o.o19:11
diablo_rojo_phonHer internship is getting close to done though.19:11
fungi#link https://storyboard.openstack.org/#!/project/openstack-infra/storyboard Name-based project URLS!19:11
diablo_rojo_phonI thiiink she'll keep working on stuff but when school starts it will probably slow a bit.19:11
diablo_rojo_phonWoot woot!19:11
fungithere's a lengthy stack of webclient improvements SotK has up for review19:11
clarkbneat to both things. The name based urls will make a lot of people happy19:12
diablo_rojo_phonYes it will.19:12
corvusi've seen changes to start updating readmes!  very exciting!19:12
clarkband I'm sure improved search will be welcomed by many as well19:12
fungiyeah, especially the ability to sort stories by status in search results19:12
corvusi'll celebrate by approving one of them now19:12
clarkbcorvus: such productive celebration19:12
fungi(and there was much rejoicing)19:13
diablo_rojo_phonAwesome :) thanks corvus19:13
diablo_rojo_phonThere are definitely a lot of patches with my +2 that just need one more19:13
diablo_rojo_phonTrying to get on top of all of that a bit more.19:14
fungilast week we performed our first project-group rename in sb19:14
fungi(it was a trivial update query changing a single row)19:14
diablo_rojo_phonBut still :)19:14
clarkbfungi: this was the api-sig change?19:14
fungiyup. they has a project-group but thankfully project-groups (like most resources in sb) have integer ids and the names are just a mapping table19:15
clarkb( I didn't realize that was the first case of that particular rename)19:15
fungiwe've renamed lots of projects in sb but no project-groups before now19:15
clarkbother than needing reviews anything else before we move on?19:16
funginope, not that i can think of19:17
fungii probably missed some stuff while i was travelling though19:17
clarkbAlright #2 priority effort is the config mgmt modernization.19:17
cmurphyo/19:18
fungii did see some of that going on but also wasn't able to follow super closely yet19:18
clarkbI approved the change to make this an official priority effort. We had mostly operated under that assumption anyway19:18
clarkbThe big change in the last week is we now have a node bootstrapped by ansible only and is a replacement bastion host19:18
*** bobh has joined #openstack-meeting19:18
* fungi will love to see the old puppetmaster instance finally go away19:19
clarkbit is called bridge.openstack.org. The idea here was we needed a more modern bastion since trusty python is getting unhappy particularly with cryptography19:19
clarkband we need to uprade anyway19:19
clarkbEventually it will take over the triggering of puppet on remote nodes but it is not doing that quite yet19:19
fungiwhat was the story behind the name choice there? i'm sure there was one19:19
mordredclark suggested it and I just ran with it :)19:19
fungiit's a bridge from our old model to eventually just using zuul?19:19
clarkbfungi: monty asked for name ideas and I threw out a few and said I liked bridge the most19:19
clarkbfungi: more star trek bridge19:20
mordredyah. it's "the bridge"19:20
fungiaha19:20
clarkbbut it fits that way too :)19:20
corvuspatrick stewart is apparently going to reprise jean-luc in a new show.  this is relevant information for this meeting.19:20
mordredI could use more reviews on that stack - I'm a little bit stalled at the moment needing to get the install_modules change landed19:20
* fungi musters to his station19:20
ianwshould have changed the motd to "make it so"19:20
clarkbthe big thing to be aware of at the moment is we need to double account hiera data changes on puppetmaster.o.o and brdige.o.o until bridge takes over the puppet triggering19:20
mordredand yes, that19:20
mordredI don't think we're too far away from being able to move triggering to bridge and decommission puppetmaster19:21
clarkbcorvus: cautiously optomistic about that :)19:21
corvusalso, you *are* allowed to call it "bilge" when things go wrong19:21
mordredoh - also, double-accounting any password info in /root too19:21
corvusmordred: maybe we could decide to just use bridge for root/passwords.gpg?19:21
corvussince that's just manual19:21
clarkbcorvus: that is probably a good idea19:22
mordredyah. I'm fine with that19:22
clarkbmaybe send a followup to the fyi email thread saying we are doing ^19:22
corvusmordred: can you do one final sync, then move the old ones out of the way and replace with a README?19:22
mordredmaybe let's set u-w on passwords.gpg on puppetmaster just to be sure ... o rthat19:22
mordredyes19:22
corvusya, something like that :)19:22
* mordred will do that19:22
clarkbmordred: I'll also rebuild the rax dns venv on bridge so that ssl works19:23
clarkb(I hadn't done that on puppet master yet)19:23
*** bobh has quit IRC19:23
*** mriedem has joined #openstack-meeting19:24
clarkbSemi related are the set of changes at topic:puppet-419:24
clarkbI think I'm mostly up to date on my reviews there if someone else is willing tomake a followup pass through19:24
clarkbbut the vast majority of those changes have been merged at this point19:24
cmurphyi think we're stuck on ask and ask-staging19:24
cmurphysince ask-staging seems to not exist right now19:24
clarkboh right, ianw ^ is there a tl;dr for the status on ask-staging?19:24
clarkb(I think you had mentioned that there were some things)19:25
ianwoh, hrm ... so i think i was waiting on a change to get numerical hosts for it into puppet19:25
ianwand then probably got distracted19:25
*** jamesmcarthur has quit IRC19:25
ianwyes, https://review.openstack.org/#/c/558992/19:26
clarkbianw: ya I left a couple comments on that one last week when I was trying to get the future parser stuff going19:26
clarkbianw: I think we need to set up the hiera groups in puppet for that (and then add hiera data)19:26
clarkbcmurphy: would it make sense to skip ask* for now and continue with another service or three?19:27
cmurphyclarkb: sure19:27
ianwi can do that, we really should look at getting ask.o.o updated and will need the staging host19:27
clarkbianw: ++19:27
ianwthere's an email out there i sent when i investigated issues with ask.o.o19:28
clarkbI think we can do the puppet 4 parser work in parallel (on other services) and update ask19:28
cmurphyi've just been going through site.pp looking for candidates19:28
cmurphyi have a change to remove stackalytics.o.o since that seesm to not exist anymore https://review.openstack.org/58520819:28
clarkbcmurphy: ethercalc, ehterpad, logstash-workers, elasticsearch, paste are favorites of mine fwiw. They tend to be straightforward19:28
cmurphyclarkb: ether* scare me because nodejs19:28
fungistoryboard-dev?19:29
cmurphyalso there are a few in-flight beaker tests for ether* that i think are still unmerged19:29
clarkbcmurphy: we have etherpad-dev too but getting tests happy first is probably a good idea19:30
cmurphyfungi: storyboard-dev is good except it's slightly less dev than other -dev sites since some people are using it to trial storyboard19:30
cmurphyalso i noticed that odsreg.o.o seems very sad19:30
fungii thought we removed that19:30
clarkbI want to say we did19:31
fungii need to follow up with ttx to find out if i missed deleting that after he said i could or something19:31
cmurphyit's still in site.pp19:31
cmurphyif it's not needed i'll propose a change to remove it19:31
clarkband dns19:31
clarkbwe should clean that up if possible19:31
fungii'll take care of it19:31
clarkbthanks19:31
fungiafter i check that it's really gone from the tenant too19:32
*** e0ne has quit IRC19:32
clarkbmordred: cmurphy: anything else we should be aware of with the changes that are happening?19:33
cmurphynothing from me i think19:33
*** apetrich has joined #openstack-meeting19:33
fungiyeah, not finding odsreg in our tenant, so it's just puppet/dns i need to clean up i guess19:34
clarkb#topic General Topics19:34
*** openstack changes topic to "General Topics (Meeting topic: infra)"19:34
clarkbcorvus: Swift logs is back on the agenda19:34
corvuswe're very close to being able to switch19:35
corvuswe need to land this change:19:35
corvus#link https://review.openstack.org/588383 Add severity info to logstash and filter out DEBUG lines19:36
corvusto the log processor19:36
corvusthat should be compatible with the current system too, so is safe to land now19:36
clarkbI've reviewed it and has my +2. It should be forward and backward compatible19:36
clarkbyup19:36
*** jamesmcarthur has joined #openstack-meeting19:36
corvusthen i can push up some test changes (to, say, devstack) so we can see how everything will look19:36
corvusthen we should be able to switch19:37
corvusso, basically, now's the time to start talking about whether we want to, any concerns folks have, etc.19:37
clarkbcorvus: we should clarify to openstack release team that this won't affect the releaes artifacts (all of that goes to tarballs still aiui)19:37
clarkbI'm surethey will be concered about it impacting the release (but its logs only shold be quite safe)19:37
clarkbcorvus: is the plan to use vexxhost to start?19:38
corvuscurrently, it's only easy to use one provider.  we can use vexxhost or ovh.  i think we should be able to randomly pick one of the two in the near future if we want, but i haven't implemented that yet.19:38
corvuswe *might* be able to extend it to support rax's not-swift.  no promises.19:39
corvusthose are the only things vaguely like swift that i believe we have access to at the moment.19:39
mordred++19:40
corvusthere are definite downsides to this.  severity filtering in the ui will be gone.  we'll be storing plain text *and* htmlified logs.  and tristanC apparently wanted to use os-loganalyze for some of the machine learning log stuff.19:40
clarkbwe are trading complexity for reliability and retention19:41
clarkbI'm personally happy to use grep myself if I have to in return for having logs for longer period of time19:41
corvusthat's how i look at it.  and i'd like to look into implementing some of that complexity in javascript if we can.19:42
clarkbvim users, you can open http(s) urls directly in vim too. Quite useful for this stuff19:42
clarkbI'm sure emacs does similar19:42
fungiyeah, i expect some css/js magic would make it possible to filter in-browser (though the browser would still have to retrieve the full log first)19:42
corvusif we can't, maybe we should revisit the idea of a proxy.  tobiash is running one anyway (for access control purposes), so we might want to revisit that.  but at the moment at least, i feel like i'd like to try to avoid that.  it's where we hit the wall last time we tried swift.19:43
fungiand the implementation gives us a durable url to the index for any given build?19:43
corvusfungi: yeah.  https://object-storage-ca-ymq-1.vexxhost.net/swift/v1/86bbbcfa8ad043109d2d7af530225c72/logs_78/587178/1/check/tox-py35-on-zuul/1f46ccf/  is the latest test19:44
clarkbfungi: until the expiration happens and it is deleted. Couple that with zuul dashboard and you should be able to find builds reasonably well19:44
corvusoh, yeah, icons are still to-do.19:44
mordredI think it's a reasonable tradeoff19:44
fungimeh, icons ;)19:45
mordredespecially given the cost to th eproject overall whenver logs.o.o goes south19:45
clarkbmordred: ya19:45
clarkbwe have 15 minutes left, ok if we move on? Please go review the log processor change if you have some cycles19:45
mordredand I agree, we can always run a proxy in the future - OR we could just run a web service that does os-loganalyze/machine-learning like things that is not what we normally route people to for log viewing19:46
corvusyep.19:46
corvussounds like folks want to move forward still.19:46
mordredclarkb: I already +A'd the processor change19:46
clarkbmordred: woot19:46
corvuslet me know if you have concerns.  or, you know, propose patches to fix them.  :)19:46
*** vgreen has quit IRC19:46
fungido we want a redirector of some sort (rather than a proxy) in case we need to move objects to another container or provider or something? or just plan to do phased transitions and consider the loss of that data an acceptable risk in such situations?19:46
corvusfungi: personally, i'd suggest never moving data19:47
corvusif we lose a provider holding logs, we lose those logs19:47
clarkbnot all that different from the 30 day expiry on mega fs today19:48
fungisince we don't control those domains though, we have to assume domain name changes will never occur, and urls paths will never be rejiggered, right?19:48
clarkbfungi: yes, though I think that is sort of the point of those services.19:48
fungiwfm19:48
corvusthe nice thing about not having a proxy (at least, in the current system) is that we no longer have a single hostname for logs.  each log has its own url.  a job that runs today may be stored in vexxhost.  tomorrow in ovh.19:48
clarkbfungi: I would be surprised if they change those ever19:48
corvusso us changing log-storageprovider19:48
corvusgah19:48
corvusso us changing log-storage-providers is a non-event19:49
fungiyep, i'm fine with all that as long as we set expectations around it19:49
fungistill no guarantee of any particular retention in cases where we have to move off of a provider we were using19:49
mordredyup19:49
fungi(thinking ahead to a broadly distributed object storage future for logging)19:49
mordredmmm. broadly distributed19:50
*** tobiash has joined #openstack-meeting19:50
corvusfungi: yeah, we may want to not enable log storage on a provider until we have a reasonable expectation they'll stick around for 6 months :)19:50
fungiheh19:50
fungigood call!19:50
clarkbReally quickly, the winterscale naming thread hsa an update from jbryce with a proposal. Would appreciate all yall's feedback. I think we are also keeping it to that private thread we are on for now while some last details are sorted.19:50
clarkbfeedback that has been provided so far is positive though. I am excited :)19:51
mordred++19:51
corvusyeah, hopefully we can make that public again soon, but it's good to know there's progress19:51
* mordred is excited - and also excited to get to the point where we can talk about it publically19:51
clarkb++19:51
clarkb#topic Open Discussion19:52
*** openstack changes topic to "Open Discussion (Meeting topic: infra)"19:52
clarkbCouple items from me that weren't quite proper agenda worthy: I am taking tomorrow off to go fishing and spend time with family. I expect that I will be properly afk. The other thing is PTG planning is quickly bubbling up to the top of my todo list19:52
clarkbI think the config management stuff is getting to the point where we should hav a good idea of what we can dig into in denver19:53
clarkbwhich is good19:53
corvushttps://zuul-ci.org/users.html  and  http://superuser.openstack.org/articles/zuul-case-study-bmw/  are cool19:55
tobiash:)19:55
fungias is https://www.podcastinit.com/zuul-with-monty-taylor-episode-172/19:55
corvuswell, except for that none of the links go to zuul-ci.org.  i'll email them i guess :)19:55
clarkbcorvus: dhellmann and I have been asked to start working on similar from an openstack perspective19:56
clarkbhappy to inclue others if they are interested (maybe to review?)19:56
corvuscool!19:57
*** jamesmcarthur has quit IRC19:57
*** jamesmcarthur has joined #openstack-meeting19:57
fungieek, yeah i see one nodepool link gong to our openstack deployment operational docs, and another going to a github mirror19:57
clarkbAlright we are basically at time and I have a leftover burger patty to turn into lunch19:58
clarkbThank you everyone19:58
*** jamesmcarthur_ has joined #openstack-meeting19:58
fungithanks clarkb!19:58
clarkb#endmeeting19:58
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"19:58
openstackMeeting ended Tue Aug  7 19:58:58 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:58
openstackMinutes:        http://eavesdrop.openstack.org/meetings/infra/2018/infra.2018-08-07-19.01.html19:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/infra/2018/infra.2018-08-07-19.01.txt19:59
openstackLog:            http://eavesdrop.openstack.org/meetings/infra/2018/infra.2018-08-07-19.01.log.html19:59
*** bobh has joined #openstack-meeting19:59
*** sdatko has left #openstack-meeting20:00
*** jamesmcarthur has quit IRC20:01
*** raildo has quit IRC20:02
*** raildo has joined #openstack-meeting20:07
*** tobiash has left #openstack-meeting20:08
*** raildo has quit IRC20:28
*** dustins has quit IRC20:30
*** dustins has joined #openstack-meeting20:36
*** AlanClark has quit IRC20:41
*** apetrich has quit IRC20:45
*** trandles has joined #openstack-meeting20:58
*** slaweq has quit IRC20:58
*** martial has joined #openstack-meeting21:04
martialtesting?21:05
trandleshello21:05
trandlesmeeting today?21:05
martialHi Tim, is it just a few regulars today?21:06
*** Shrews has left #openstack-meeting21:06
*** janders has joined #openstack-meeting21:07
jandersgday everyone21:07
martialHi janders, any update on your presentation?21:08
janders:) what presentation? :)21:08
martialI must be confusing with something else then21:09
martialno stig or blair I guess? they are otherwise occupied I am sure and that is fine21:09
jandershope they are not fighting fires.. I missed last week's meeting after one of my colleagues accidentally connected two subnet managers which started killing each other. That hurt :(21:11
trandlesmight be just a few of us, not sure21:11
trandlesI didn't see a meeting announcement email this week21:11
jandersyeah looks like a small meeting21:11
janderswe don't have an agenda set, right? do we spontaneously make one? :)21:12
jandershave you guys had much exposure to placement api?21:15
jandersI've been fighting some interesting placement issues this week21:15
martialI did not see an agenda or any announcement either, Blair and Stig are off, moving or otherwise21:17
martialwe will keep it as a short meeting21:17
martialsimple21:17
martialtim: I got contacted by a person that is also doing a Container on HPC BoF for SC1821:18
*** dustins has quit IRC21:18
martialand that is not the person you introduced me to21:18
trandlesmartial: I'm not aware of that one...21:18
trandlesunless it's a likely suspect21:18
martialnot sure I must say21:19
trandlesno worries21:19
trandlesI suspect the organizers will be sending emails asking submissions to merge21:19
martialpossible, we will see what happens21:20
jandersdo you guys know when the Summit Berlin organisers will start notifying those who submitted presentations about the selection outcomes?21:20
martialnot sure but since you do not have one ;)21:21
trandlesjanders: I don't know but usually they publish that info.  IIRC there was a mini draft schedule/agenda posted on FB in the past day or two21:21
*** awaugama has quit IRC21:21
trandlesI'm guessing it was just confirmed keynotes21:21
trandlessince I can't go to the Berlin Summit I haven't been paying much attention...too depressing to think about ;)21:22
*** slaweq has joined #openstack-meeting21:23
janderstrandles: thanks, I will look around21:24
*** edmondsw has quit IRC21:29
martialsame :)21:32
martialwell it was a good meeting :)21:32
martialthanks team :)21:33
bolligshort meeting21:33
jandersthanks guys21:33
jandersto answer my question: Dates to remember:  August 13: Event schedule goes live21:34
janderswe should know by the next meeting21:34
jandershave a good day / night depending on where you are :)21:34
trandlessorry, I'm also on a conference call which I NEVER participate in, then I heard my name...21:35
trandleslater all21:35
martialno worries Tim, short meetings are good too :)21:35
*** trandles has quit IRC21:35
*** Leo_m has quit IRC21:40
*** jamesmcarthur_ has quit IRC21:41
*** Leo_m has joined #openstack-meeting21:46
*** Leo_m has quit IRC21:51
*** slagle has quit IRC21:56
*** Leo_m has joined #openstack-meeting21:57
*** priteau has quit IRC22:09
*** bobh has quit IRC22:12
*** janders has quit IRC22:12
*** beagles has quit IRC22:13
*** ykatabam has joined #openstack-meeting22:15
*** beagles has joined #openstack-meeting22:20
*** rcernin has joined #openstack-meeting22:20
*** strigazi has joined #openstack-meeting22:20
*** strigazi has quit IRC22:21
*** strigazi has joined #openstack-meeting22:21
*** strigazi has quit IRC22:27
*** strigazi has joined #openstack-meeting22:28
*** strigazi has quit IRC22:28
*** strigazi has joined #openstack-meeting22:29
*** strigazi has quit IRC22:32
*** strigazi has joined #openstack-meeting22:33
*** hongbin has quit IRC22:39
*** gothicmindfood has quit IRC22:42
*** edmondsw has joined #openstack-meeting22:54
*** edmondsw has quit IRC22:59
*** tpsilva has quit IRC23:12
*** priteau has joined #openstack-meeting23:16
*** Leo_m has quit IRC23:46
*** Swami has quit IRC23:46
*** Leo_m_ has joined #openstack-meeting23:46

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