Tuesday, 2019-07-30

*** njohnston has quit IRC00:02
*** njohnston has joined #openstack-meeting00:03
*** yamahata has joined #openstack-meeting00:13
*** diablo_rojo has joined #openstack-meeting00:21
*** artom has joined #openstack-meeting00:25
*** tetsuro has joined #openstack-meeting00:25
*** gyee has quit IRC00:28
*** cheng1 has quit IRC00:29
*** cheng1 has joined #openstack-meeting00:30
*** yamamoto has joined #openstack-meeting00:32
*** tetsuro has quit IRC00:56
*** ricolin_ has joined #openstack-meeting00:58
*** brinzhang has joined #openstack-meeting01:00
*** dtrainor has quit IRC01:01
*** cheng1 has quit IRC01:01
*** brinzhang_ has quit IRC01:02
*** cheng1 has joined #openstack-meeting01:04
*** panda has quit IRC01:06
*** panda has joined #openstack-meeting01:08
*** igordc has quit IRC01:15
*** bbowen has joined #openstack-meeting01:18
*** tetsuro has joined #openstack-meeting01:31
*** mhen has quit IRC01:34
*** cheng1 has quit IRC01:42
*** cheng1 has joined #openstack-meeting01:46
*** brinzhang_ has joined #openstack-meeting01:50
*** cheng1 has quit IRC01:51
*** brinzhang_ has quit IRC01:51
*** ykatabam has quit IRC01:51
*** brinzhang_ has joined #openstack-meeting01:52
*** cheng1 has joined #openstack-meeting01:52
*** brinzhang_ has quit IRC01:52
*** brinzhang_ has joined #openstack-meeting01:53
*** brinzhang has quit IRC01:53
*** brinzhang_ has quit IRC01:54
*** brinzhang_ has joined #openstack-meeting01:54
*** brinzhang_ has quit IRC01:56
*** brinzhang_ has joined #openstack-meeting01:56
*** brinzhang has joined #openstack-meeting01:57
*** carloss has quit IRC01:59
*** brinzhang_ has quit IRC02:01
*** yaawang has joined #openstack-meeting02:05
*** diablo_rojo has quit IRC02:06
*** enriquetaso has quit IRC02:10
*** baojg has joined #openstack-meeting02:18
*** sridharg has joined #openstack-meeting02:23
*** cheng1 has quit IRC02:41
*** cheng1 has joined #openstack-meeting02:45
*** sridharg has quit IRC02:50
*** ykatabam has joined #openstack-meeting02:53
*** hongbin has joined #openstack-meeting02:53
*** tetsuro has quit IRC02:55
*** brinzhang_ has joined #openstack-meeting03:01
*** cheng1 has quit IRC03:02
*** cheng1 has joined #openstack-meeting03:02
*** brinzhang has quit IRC03:04
*** ykatabam has quit IRC03:23
*** ykatabam has joined #openstack-meeting03:23
*** cheng1 has quit IRC03:25
*** cheng1 has joined #openstack-meeting03:26
*** hongbin has quit IRC03:34
*** psachin has joined #openstack-meeting03:36
*** brinzhang_ has quit IRC03:43
*** tpatil has joined #openstack-meeting03:45
samP#startmeeting masakari04:01
openstackMeeting started Tue Jul 30 04:01:04 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 masakari!04:01
tpatilHi04:01
samPtpatil: Hi04:01
*** nitinuikey has joined #openstack-meeting04:01
samP#topic Critical Bugs or Patches04:01
*** openstack changes topic to "Critical Bugs or Patches (Meeting topic: masakari)"04:02
samPAny critical bugs or patches need to discuss here?04:02
samPI noticed that zuul jobs are failing for functional testing04:02
tpatilDue to sdk changes functional tests are failing , working on it04:02
samPtpatil: got it. fixing sdk?04:03
tpatilIn one of patch set the functional tests executed successfully but it’s failing again04:04
tpatilwill analyse the issue today04:05
samPtpatil: sure, thanks04:05
*** imsurit has joined #openstack-meeting04:07
samPAny other issues?04:08
tpatilBugs, no04:08
samPthanks for reviewing spec https://review.opendev.org/#/c/67047604:08
tpatilAwaiting for reply from author on my question on the specs04:09
samPit seems that suzhengwei want to sort the instances before evacuate.04:09
samPI think he post one comment about this.04:10
*** tpatil has quit IRC04:10
*** tpatil has joined #openstack-meeting04:11
tpatilI will check his comments and reply back04:11
samPit tpatil : thanks04:11
samPit seems to me like a reasonable options, when you enable VMHA for all instances.04:12
samPI will put the comments on the spec04:13
samP#topic Train Work Items04:13
tpatilOk thanks04:13
*** openstack changes topic to "Train Work Items (Meeting topic: masakari)"04:13
samPPlease share any updates on Train work items04:13
tpatilDevstack host Monitor aupport04:13
tpatil please review the patch04:14
samPtpatil: sorry for the delay. I will04:14
tpatilIn the meantime we will fix the functional test issue04:15
samPtpatil: got it.04:15
*** ykatabam has quit IRC04:15
tpatilWorking on installing masakari on CentOs04:15
*** ykatabam has joined #openstack-meeting04:15
samPtpatil: install with pip?04:16
tpatilusing source code as masakari packages are not available on CentOs04:16
*** ykatabam has quit IRC04:16
samPtpatil: got it. Masakari does not have rpm packages for CentOS.04:17
*** tpatil has quit IRC04:18
*** ykatabam has joined #openstack-meeting04:18
*** tpatil has joined #openstack-meeting04:19
tpatilDo you know which OS distributions supports installation of masakari using packages?04:20
*** apetrich has quit IRC04:20
tpatilon Centos we are trying to install it from source code04:20
samPCurrently, Ubuntu, SUSE, only04:20
tpatilok04:20
samPHowever, I build packages for Fedora04:21
samP#link https://copr.fedorainfracloud.org/coprs/sampntt/masakari/04:21
tpatilI will check this link04:22
samPThose are outdated now. If you need them, I can update the source and rebuild them.04:22
samPThis can be used on CentOS.04:22
tpatilwe could installed masakari on  CentOS04:22
tpatilusing source code04:23
tpatilwill send these steps on the mailing list and also update Masakari readme04:23
samPtpatil: thanks.04:23
tpatiland will also try Fedora  packages on CentOS04:24
samPsure. Are you installing master or any other stable version?04:26
tpatilmaster04:26
samPgot it.04:26
tpatilThat’s all update from my end about train items04:28
samPtpatil: thanks04:29
samP#topic04:29
*** openstack changes topic to " (Meeting topic: masakari)"04:29
samP#topic AOB04:29
*** openstack changes topic to "AOB (Meeting topic: masakari)"04:29
samPAny one going to next PTG and Summit?04:29
tpatili will attend04:30
samPtpatil: my current plan is not to attend.04:31
*** gary_perkins has quit IRC04:32
samPHowever, it might be change in the future. I would like to do a project update for masakari.04:33
samPThat is all from my side04:33
samPAny other topics need to discuss?04:33
*** gary_perkins has joined #openstack-meeting04:33
tpatilNo04:35
samPOK then, let's end today's meeting here.04:35
samPThank you all for attending!04:35
samP#endmeeting04:35
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"04:35
openstackMeeting ended Tue Jul 30 04:35:47 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)04:35
openstackMinutes:        http://eavesdrop.openstack.org/meetings/masakari/2019/masakari.2019-07-30-04.01.html04:35
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/masakari/2019/masakari.2019-07-30-04.01.txt04:35
openstackLog:            http://eavesdrop.openstack.org/meetings/masakari/2019/masakari.2019-07-30-04.01.log.html04:35
*** tpatil has quit IRC04:36
*** whoami-rajat has joined #openstack-meeting04:40
*** nitinuikey has quit IRC04:48
*** rubasov has quit IRC04:53
*** osmanlicilegi has quit IRC04:53
*** osmanlicilegi has joined #openstack-meeting04:54
*** belmoreira has joined #openstack-meeting04:54
*** links has joined #openstack-meeting05:04
*** Luzi has joined #openstack-meeting05:05
*** raildo has quit IRC05:11
*** raildo has joined #openstack-meeting05:12
*** ricolin__ has joined #openstack-meeting05:21
*** ricolin_ has quit IRC05:24
*** d34dh0r53 has quit IRC05:25
*** yamamoto has quit IRC05:26
*** yamamoto has joined #openstack-meeting05:27
*** jamesmcarthur_ has quit IRC05:28
*** radeks_ has joined #openstack-meeting05:37
*** SWDevAngel has quit IRC05:47
*** kopecmartin|off is now known as kopecmartin05:48
*** vishalmanchanda has joined #openstack-meeting05:53
*** brinzhang has joined #openstack-meeting05:58
*** belmoreira has quit IRC06:13
*** brinzhang_ has joined #openstack-meeting06:16
*** d34dh0r53 has joined #openstack-meeting06:17
*** brinzhang has quit IRC06:19
*** radeks__ has joined #openstack-meeting06:34
*** radeks_ has quit IRC06:36
*** slaweq has joined #openstack-meeting06:53
*** brinzhang has joined #openstack-meeting06:54
*** ykatabam has quit IRC07:00
*** rcernin has quit IRC07:02
*** belmoreira has joined #openstack-meeting07:08
*** tesseract has joined #openstack-meeting07:11
*** tssurya has joined #openstack-meeting07:16
*** nnsingh has joined #openstack-meeting07:42
*** ricolin__ is now known as ricolin07:44
*** brault has joined #openstack-meeting07:47
*** tpatil has joined #openstack-meeting07:49
*** takahashi-tsc has joined #openstack-meeting07:56
*** ralonsoh has joined #openstack-meeting07:58
*** nitinuikey has joined #openstack-meeting07:59
*** nitinuikey has quit IRC08:00
*** nitinuikey has joined #openstack-meeting08:01
*** bhagyashris has joined #openstack-meeting08:03
*** shubham_potale has joined #openstack-meeting08:04
*** priteau has joined #openstack-meeting08:08
*** joxyuki has joined #openstack-meeting08:09
*** imsurit has quit IRC08:11
*** lpetrut has joined #openstack-meeting08:18
*** hokeeeeun has joined #openstack-meeting08:19
*** hjwon has joined #openstack-meeting08:19
*** hokeeeeun has quit IRC08:20
*** nitinuikey has quit IRC08:25
*** nitinuikey has joined #openstack-meeting08:26
*** jaewook_oh_ has joined #openstack-meeting08:29
*** ttsiouts has joined #openstack-meeting08:32
*** imsurit has joined #openstack-meeting08:33
*** nitinuikey has quit IRC08:37
*** tpatil has quit IRC08:40
*** nitinuikey has joined #openstack-meeting08:42
*** e0ne has joined #openstack-meeting08:45
*** johnthetubaguy has quit IRC08:51
*** johnthetubaguy has joined #openstack-meeting08:53
*** belmoreira has quit IRC08:54
*** belmoreira has joined #openstack-meeting08:55
*** belmoreira has quit IRC08:56
*** apetrich has joined #openstack-meeting08:59
*** nitinuikey has quit IRC09:01
*** rubasov has joined #openstack-meeting09:04
*** SotK has quit IRC09:06
*** SotK has joined #openstack-meeting09:08
*** johnthetubaguy has quit IRC09:09
*** johnthetubaguy has joined #openstack-meeting09:11
*** nitinuikey has joined #openstack-meeting09:30
*** takahashi-tsc has quit IRC09:30
*** nitinuikey has quit IRC09:38
*** ykatabam has joined #openstack-meeting09:49
*** links has quit IRC09:51
*** dansmith has quit IRC09:52
*** ykatabam has quit IRC09:53
*** ianw has quit IRC09:55
*** dansmith has joined #openstack-meeting09:58
*** ianw has joined #openstack-meeting09:59
*** shubham_potale has quit IRC10:04
*** bhagyashris has quit IRC10:06
*** nnsingh has quit IRC10:06
*** links has joined #openstack-meeting10:12
*** ttsiouts has quit IRC10:14
*** ttsiouts has joined #openstack-meeting10:15
*** ociuhandu has joined #openstack-meeting10:17
*** ttsiouts has quit IRC10:19
*** ociuhandu_ has joined #openstack-meeting10:25
*** ociuhandu has quit IRC10:25
*** yamamoto has quit IRC10:32
*** belmoreira has joined #openstack-meeting10:33
*** Lucas_Gray has joined #openstack-meeting10:44
*** belmoreira has quit IRC10:48
*** links has quit IRC10:58
*** belmoreira has joined #openstack-meeting11:01
*** belmoreira has quit IRC11:02
*** ttsiouts has joined #openstack-meeting11:04
*** belmoreira has joined #openstack-meeting11:09
*** yamamoto has joined #openstack-meeting11:12
*** brinzhang_ has quit IRC11:15
*** brinzhang_ has joined #openstack-meeting11:16
*** yamamoto has quit IRC11:18
*** yamamoto has joined #openstack-meeting11:19
*** brtknr has quit IRC11:19
*** Lucas_Gray has quit IRC11:19
*** brault has quit IRC11:20
*** links has joined #openstack-meeting11:20
*** osmanlicilegi has left #openstack-meeting11:33
*** ociuhandu_ has quit IRC11:34
*** belmoreira has quit IRC11:35
*** ociuhandu has joined #openstack-meeting11:35
*** Lucas_Gray has joined #openstack-meeting11:36
*** belmoreira has joined #openstack-meeting11:36
*** hjwon has quit IRC11:39
*** hjwon has joined #openstack-meeting11:40
*** hjwon has quit IRC11:46
*** hjwon has joined #openstack-meeting11:46
*** jamesmcarthur has joined #openstack-meeting11:50
*** njohnston has quit IRC11:56
*** yamamoto has quit IRC11:57
*** jamesmcarthur has quit IRC12:03
*** njohnston has joined #openstack-meeting12:05
*** yamamoto has joined #openstack-meeting12:12
*** ociuhandu has quit IRC12:14
*** yamamoto has quit IRC12:17
*** eharney has joined #openstack-meeting12:23
*** psachin has quit IRC12:25
*** hjwon has quit IRC12:31
*** carloss has joined #openstack-meeting12:33
*** ricolin has quit IRC12:35
*** joxyuki has quit IRC12:36
*** yamamoto has joined #openstack-meeting12:37
*** jamesmcarthur has joined #openstack-meeting12:44
*** enriquetaso has joined #openstack-meeting12:45
*** links has quit IRC12:50
*** bbowen has quit IRC12:50
*** ociuhandu has joined #openstack-meeting12:50
*** jamesmcarthur has quit IRC12:51
*** bbowen has joined #openstack-meeting12:51
*** belmoreira has quit IRC12:51
*** belmoreira has joined #openstack-meeting12:55
*** links has joined #openstack-meeting12:59
*** jamesmcarthur has joined #openstack-meeting13:01
*** jamesmcarthur has quit IRC13:02
*** jamesmcarthur has joined #openstack-meeting13:03
*** links has quit IRC13:06
*** mriedem has joined #openstack-meeting13:13
*** ttsiouts has quit IRC13:14
*** ttsiouts has joined #openstack-meeting13:15
*** ttsiouts has quit IRC13:19
*** belmoreira has quit IRC13:31
*** belmoreira has joined #openstack-meeting13:31
*** yamamoto has quit IRC13:33
*** yamamoto has joined #openstack-meeting13:36
*** yamamoto has quit IRC13:36
*** radeks_ has joined #openstack-meeting13:37
*** yamamoto has joined #openstack-meeting13:37
*** radeks__ has quit IRC13:38
*** yamamoto has quit IRC13:42
*** ttsiouts has joined #openstack-meeting13:45
*** mlavalle has joined #openstack-meeting13:54
*** links has joined #openstack-meeting13:54
*** Luzi has quit IRC13:55
slaweq#startmeeting networking14:00
slaweqo/14:00
openstackMeeting started Tue Jul 30 14:00:05 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
*** openstack changes topic to " (Meeting topic: networking)"14:00
openstackThe meeting name has been set to 'networking'14:00
mlavalleo/14:00
njohnstono/14:00
tidwellro/14:00
rubasovo/14:00
bcafarel\o14:00
*** liuyulong has joined #openstack-meeting14:01
slaweqwelcome back bcafarel :)14:01
haleybhi14:01
*** lajoskatona has joined #openstack-meeting14:01
slaweqand welcome back haleyb :)14:01
lajoskatonao/14:01
ralonsohhi14:01
slaweqok, I think we can start14:01
bcafarelback to full crowd? :)14:01
slaweq#topic Announcements14:01
*** openstack changes topic to "Announcements (Meeting topic: networking)"14:01
slaweqMilestone T-2 was last week14:02
slaweqNext milestone is T-3 in week of Sep 0914:02
slaweqhttps://releases.openstack.org/train/schedule.html14:02
mlavalleat the end of summer :-)14:02
amotokihi14:02
slaweqplease note that in next few weeks there will be also time for nominations for TC election and later for PTLs if someone will want to candidate :)14:03
slaweqit will be week of Aug 2614:03
slaweqnext one:14:03
slaweqShanghai PTG planning etherpad:14:03
*** radeks_ has quit IRC14:03
slaweqhttps://etherpad.openstack.org/p/Shanghai-Neutron-Planning14:03
*** e0ne has quit IRC14:04
slaweqplease add Your name there if You are planning to attend14:04
slaweqmlavalle needs this info before Aug 4th14:04
mlavalleno cheanges since lastt week14:04
mlavallesome it seems we are converging to the answer14:04
slaweqPlease also free to propose topics. We don't have deadline for this other than the PTG itself14:05
slaweqand last reminder on the list:14:05
slaweqTrain PTG summary: http://lists.openstack.org/pipermail/openstack-discuss/2019-May/006408.html14:05
slaweqany other announcements/reminders from the team?14:05
slaweqok, I think we can continue14:06
slaweq#topic Blueprints14:06
*** openstack changes topic to "Blueprints (Meeting topic: networking)"14:06
*** davidsha has joined #openstack-meeting14:07
slaweqI moved existing, not finished BPs from T-2 to T-314:07
slaweqlist is on https://launchpad.net/neutron/+milestone/train-314:07
slaweqany updates about BPs?14:07
tidwellrI added a couple test cases to https://review.opendev.org/#/c/667511/, subnets-different-pools-same-net just needs one last round of reviews14:08
mlavallewill review today14:08
slaweqtidwellr: thx, I can review it tomorrow morning my time14:10
*** brtknr has joined #openstack-meeting14:10
njohnstonI am working on the ethertype change for iptables_hybrid; I added a validator last week but I realized last night that it needs to handle some additional scenarios so I'll push a change to that today.  Thanks slaweq for helping me with the fullstack test problem.14:10
slaweqnjohnston: no problem, I hope that my advice was somehow useful :)14:11
slaweqfrom other blueprints14:12
slaweqhttps://blueprints.launchpad.net/neutron/+spec/multiple-segment-per-network-per-host - spec for this one is ready for review: https://review.opendev.org/#/c/657170 -14:13
slaweqplease take a look14:13
slaweqand I would also want to ask for reviews of patches from rubasov for https://blueprints.launchpad.net/neutron/+spec/improve-extraroute-api - patches are available at https://review.opendev.org/#/q/topic:extraroute+(status:open+OR+status:merged) and IMO at least some of them looks quite good already14:14
slaweqthat's all from my about blueprints14:14
slaweqany other updates from the team?14:14
slaweqok, I will take it as "no"14:15
slaweqlets move on14:15
slaweq#topic Community goals14:15
*** openstack changes topic to "Community goals (Meeting topic: networking)"14:15
slaweqamotoki: njohnston any updates on py3 and pdf docs?14:16
amotokion pdf docs, sample neutron.conf causes latex error now.14:16
amotokiI am thinking to split sample neutron.conf into more meaningful pieces14:17
amotokiand started to look into the current sample config file in detail.14:17
amotokithat's the update from me.14:17
*** mlavalle has quit IRC14:17
*** radeks has joined #openstack-meeting14:18
slaweqthx amotoki14:18
njohnstonFor the python 3 transition, there is outstanding work left to do for networking-bagpipe, networking-midonet, networking-odl, and it looks like amotoki is making good headway on python-neutronclient14:18
*** yamamoto has joined #openstack-meeting14:19
amotokinjohnston: yes, neutronclient py3 migration will complete by my patch series14:19
*** mlavalle has joined #openstack-meeting14:19
slaweqthat is good news about neutronclient :)14:20
njohnstonlajoskatona: we usually discuss this in more detail in the neutron CI meeting later, do you want to join to talk about networking-odl?14:20
slaweqthx amotoki for working on it14:20
* mlavalle had an internet connection hiccup14:20
*** boden has joined #openstack-meeting14:20
lajoskatonanjohnston: sure, perhaps I will late, as after this meeting I will go home ,and that's take some time14:20
njohnstonlajoskatona: Would you like to give us your status now, would that be easier?14:21
lajoskatonanjohnston: yeah, why not. There are a few patches for fixing minor things in networking-odl to make it py3 compatible14:21
lajoskatonanjohnston: and we started to modernize the jobs / and make them use py314:22
*** jaewook_oh_ has quit IRC14:22
lajoskatonanjohnston: so the work is ongoing, some review attention is always helpful :-)14:22
njohnstonlajoskatona: If you have a common topic or topics for those changes let us know and we can drive extra reviews to it14:22
amotokiyeah, zuulv3 migration first would make things easier :)14:23
slaweqlajoskatona: or You can add links to patches to the etherpad: https://etherpad.openstack.org/p/neutron_stadium_python3_status14:23
njohnstoneven better14:23
lajoskatonaslaweq: I add them, I just wanted to ask where can I advertise the ready to review patches14:23
lajoskatonaI think that's it for networking-odl14:24
slaweqlajoskatona: IMO You can add all Your related patches to this etherpad and ask for reviews even on neutron meeting when patches will be ready14:24
lajoskatonaslaweq: ok, thanks14:25
njohnstonyamamoto: Any word on midonet py3 updating?14:25
slaweqbut will be good to have it in etherpad as we are using it to track progress14:25
njohnstonThanks all for the updates, I think overall the stadium is looking in really good shape.14:26
amotokislaweq: njohnston: osc-check-pluigns job in python-neutronclient is from openstackclient repo. Is it okay to track it as OSC and to make it out-of-rader of neutron team?14:26
amotokiI am taking care of it though.14:26
slaweqamotoki: yes, if it's defined in osc repo than I think that it makes sense to not track it here14:27
njohnstonagreed14:27
amotokithanks for confirmation14:27
slaweqfrom my side I have small update about Support IPv6-Only Deployments14:28
slaweqgmann started pushing some patches to various projects14:28
*** yamamoto has quit IRC14:28
slaweqrecently he asked me about list of neutron stadium projects which are using some kind of communication between e.g. agents and which will require to have separate jobs defined to cover that14:29
*** hjwon has joined #openstack-meeting14:29
slaweqI made list of such projects in http://lists.openstack.org/pipermail/openstack-discuss/2019-July/008084.html14:29
slaweqplease take a look into it and correct this list if I missed some projects for example14:29
*** Lucas_Gray has quit IRC14:29
slaweqI think we can move on to the next topic then14:31
slaweq#topic Bugs14:31
*** openstack changes topic to "Bugs (Meeting topic: networking)"14:31
slaweqour bug deputy last week was boden14:31
slaweqhe send summary which is available at http://lists.openstack.org/pipermail/openstack-discuss/2019-July/008089.html14:32
*** Lucas_Gray has joined #openstack-meeting14:32
*** Lucas_Gray has quit IRC14:32
slaweqthere wasn't too many bugs during last week14:33
slaweqone which I would like to mention here is https://bugs.launchpad.net/neutron/+bug/183755214:33
openstackLaunchpad bug 1837552 in neutron "neutron-tempest-with-uwsgi job finish with timeout very often" [Medium,Confirmed]14:33
*** baojg has quit IRC14:33
slaweqthis one don't have assignee yet14:33
*** e0ne has joined #openstack-meeting14:33
slaweqso if someone would like to help with uwsgi than this is good place to start :)14:33
mlavalleand there is a duplicate in the list also14:34
slaweqother than that we have one RFE https://bugs.launchpad.net/neutron/+bug/1837847 -  which is already in good hands of njohnston and mlavalle who asked some questions in comments14:34
openstackLaunchpad bug 1837847 in neutron "[RFE] neutron-vpnaas OpenVPN driver" [Undecided,New]14:34
mlavallehttps://bugs.launchpad.net/neutron/+bug/183791614:34
openstackLaunchpad bug 1828375 in neutron "duplicate for #1837916 Bulk creation of subports fails with StaleDataError" [Low,In progress] - Assigned to Bence Romsics (bence-romsics)14:34
slaweqmlavalle: yes, thx14:35
mlavallerubasov is working on this one14:35
rubasovmlavalle, boden: kind of14:35
rubasovI think it's a duplicate of a previously fixed one14:35
mlavallethanks for the clarification14:36
rubasovbut would be nice to get feedback if the fix is working as expected14:36
slaweqI will ping dulek to check if Your patch will help him14:36
*** bobh has joined #openstack-meeting14:36
rubasovslaweq: thank you14:37
slaweqrubasov: thx for taking care of this bug :)14:37
rubasovof course14:37
slaweqany other bugs You want to talk about today?14:37
slaweqif not, lets move on14:39
slaweqour bug deputy this week is haleyb14:39
slaweqjust after PTO :)14:39
haleybyes, into the deep end of the pool :)14:39
mlavalleand lajoskatona won't be available next week, nor the next one14:39
*** Lucas_Gray has joined #openstack-meeting14:39
mlavallecorrect?14:39
lajoskatonamlavalle: thanks :-)14:39
lajoskatonaand the wee kafter that the same14:40
lajoskatonaweek after that14:40
mlavallewould amotoki or njohnston be willing to switch with lajoskatona?14:40
slaweqLOL, it took me a while to understand what "wee kafter" means :)14:40
amotokii would like to switch14:40
njohnstonI will also be on PTO during lajoskatona's shift; I traded places with haleyb already because of it :-/14:41
lajoskatonaamotoki: thanks, that's good for me14:41
mlavalleso amotoki does next week and lajoskatona does week of August 26th14:41
mlavalledoes that work for both?14:41
*** liuyulong has quit IRC14:41
amotokimlavalle: yes14:41
slaweqthx amotoki, so I will update schedule afgter this meeting if it works for You14:41
*** radeks has quit IRC14:41
mlavalleslaweq: I say let's leave the schedule as it is14:41
lajoskatonamlavalle: yes14:41
mlavallelet's not change the order in the roster14:42
-amotoki- can enjoy travel at the end of Aug :)14:42
slaweqmlavalle: ok14:42
mlavallelet's just remember the exception this cycle14:42
mlavallerotation that is14:42
slaweqok, lets move on than14:43
slaweqnext topic14:43
slaweq#topic neutron-lib14:43
*** openstack changes topic to "neutron-lib (Meeting topic: networking)"14:43
slaweqboden: any updates?14:43
bodenhi14:43
bodenmainly just business as usual; with nothing exciting to report14:44
bodenbut I do have 1 question14:44
*** radeks has joined #openstack-meeting14:44
bodendoes the networking-ovn-tempest-dsvm-ovs-release job for neutron pull ovn from source?14:44
*** belmoreira has quit IRC14:45
slaweqI don't think so14:45
slaweqbut let me check14:45
bodenslaweq... maybe I can just ping you later about this.. no need to waste everyones time?14:45
slaweqboden: https://opendev.org/openstack/networking-ovn/src/branch/master/zuul.d/networking-ovn-jobs.yaml#L21914:46
slaweqthis job is using branch 2.1114:46
slaweqbut is compiling it from source14:46
bodenslaweq let me ping you about this later... seems like something we can chat about "offline".. is that ok?14:46
haleybslaweq: i have a change to stop doing that (if we're talking about the same thing), but it's dependent on moving to F2914:47
slaweqboden: sure14:47
bodennothing else for neutron-lib unless others have comments14:47
*** liuyulong has joined #openstack-meeting14:47
slaweqok, thx boden for updates14:48
slaweqlast topic for today14:48
slaweq#topic On demand agenda14:48
*** openstack changes topic to "On demand agenda (Meeting topic: networking)"14:48
slaweqanything else You want to talk about today?14:48
slaweqif not, I will give You back about 10 minutes :)14:48
slaweqok, so lets finish this meeting earlier14:49
slaweqthx for attending14:49
mlavalleo/14:49
slaweqand have a nice week14:50
slaweqo/14:50
amotokio/14:50
lajoskatonabye14:50
slaweq#endmeeting14:50
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"14:50
openstackMeeting ended Tue Jul 30 14:50:05 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:50
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking/2019/networking.2019-07-30-14.00.html14:50
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking/2019/networking.2019-07-30-14.00.txt14:50
ralonsohbye14:50
openstackLog:            http://eavesdrop.openstack.org/meetings/networking/2019/networking.2019-07-30-14.00.log.html14:50
*** mlavalle has quit IRC14:50
*** lajoskatona has left #openstack-meeting14:50
njohnstono/14:50
*** boden has left #openstack-meeting14:50
*** belmoreira has joined #openstack-meeting14:50
rubasovbye14:51
*** belmoreira has quit IRC14:51
bcafarelyay for 10 mins back :)14:51
*** dklyle has quit IRC14:52
*** radeks has quit IRC14:52
*** dklyle has joined #openstack-meeting14:53
*** e0ne has quit IRC14:54
*** takamatsu has joined #openstack-meeting14:54
*** belmoreira has joined #openstack-meeting14:59
ralonsoh#startmeeting neutron_qos15:00
openstackMeeting started Tue Jul 30 15:00:58 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
ralonsohhello15:01
*** openstack changes topic to " (Meeting topic: neutron_qos)"15:01
openstackThe meeting name has been set to 'neutron_qos'15:01
slaweqhi15:01
ralonsohhe don't have agenda, but the qos classification15:02
ralonsohi'm waiting for davidsha15:02
davidshaHey15:02
* njohnston lurks15:02
ralonsohso, as commented, there is no agenda15:03
ralonsohno RFEs15:03
ralonsohno bugs15:03
ralonsoh#topic Open Discussion15:03
*** openstack changes topic to "Open Discussion (Meeting topic: neutron_qos)"15:03
ralonsoh#link https://bugs.launchpad.net/neutron/+bug/147652715:03
openstackLaunchpad bug 1476527 in neutron "[RFE] Add common classifier resource" [Wishlist,Triaged] - Assigned to Igor D.C. (igordcard)15:03
davidshanjohnston: Does that change on https://review.opendev.org/#/c/670050/2 work for you? I remember a tonne of semantic discussions early on in neutron-classifier about classifier vs classification15:03
*** e0ne has joined #openstack-meeting15:04
ralonsohdavidsha, I'm still writing a review in your neutron and n-lib patches15:04
njohnstondavidsha: Yes that works great for me!15:04
ralonsohdavidsha, ok, let me push what I have now15:04
ralonsohdavidsha, I would like, for the records, one thing15:04
davidshaI updated the endpoint to classification based on comments, which is the main change since last update, I'm going to try and add in the propagation code to the various neutron agents, but mainly L2 for the moment.15:05
ralonsohI don't understand the relationship between ClassificationGroup, CGToClassificationMapping and CGToClassificationGroupMapping15:05
davidsharalonsoh: CGToClassificationMapping maps classifications to classification groups and CGToClassificationGroupMapping maps classification groups to classification groups.15:06
ralonsohdavidsha, can you explain how this mapping is done15:08
davidshaOn creation when you pass in what classification/classification group objects compose a classification group, the service plugin will create a mapping from the newly created classification group to the previously created classification/classification group, there is no update mechanism for this to avoid a circular dependency at the moment15:09
ralonsohso you can have two classifications and you can create a CG15:10
ralonsohand then one CG and one C, and you can create a second CG15:10
ralonsohlike a binary tree15:10
davidshaYup15:11
ralonsohokidoki, understood15:11
ralonsohnow I need to retake the POC in neutron to review the DB definition15:11
ralonsohbtw15:11
ralonsohin the n-lib15:11
ralonsohone sec15:11
ralonsohhttps://review.opendev.org/#/c/670049/15:12
*** belmoreira has quit IRC15:12
ralonsohyou are missing a lot of information15:12
ralonsohname, description, timestamp, etc15:12
ralonsohthat's why in the neutron patch,  here https://review.opendev.org/#/c/670050/2/neutron/extensions/classification.py15:13
ralonsohyou use api_ext.ExtensionDescriptor, instead of APIExtensionDescriptor15:13
ralonsohanyway, I still need to review the n-lib patch15:13
ralonsohanother question15:14
*** links has quit IRC15:14
davidshakk, I wasn't sure how much was necessary and how much was for this instance. I'll update this15:14
ralonsohclass ClassificationBase()15:14
*** dtrainor has joined #openstack-meeting15:14
*** ricolin has joined #openstack-meeting15:14
ralonsohwhy do you need it? this is not a classification itself15:14
ralonsohthere should not be a DB definition of this generic classification, or at least you should have a class not inheriting from model_base.BASEV215:15
ralonsohand then inherit it from the classification type classes15:16
ralonsohis that ok for you?15:17
davidshaAck, We used it initially for a generic pull in the classification and then use it to find out which classification it was specifically. I'll remove model_base.BASEV2, I'll see do we need it for the previous functionality still.15:17
ralonsohdo you need a generic classification table?15:18
davidshaFor now, I'll say we do, but it can be refactored out15:19
ralonsohwhat is the goal/use of this generic type?15:19
ralonsohthere won't be a classification base on this generic type15:20
ralonsohsame a in QoS: there is no generic QoS rule15:20
ralonsohyou have max, min or dscp15:20
davidshaWe have it here on line 65: https://review.opendev.org/#/c/670050/2/neutron/db/migration/alembic_migrations/versions/train/expand/ae8df423b477_neutron_classifier.py15:20
ralonsohyes, the migration and the db definition should be the same15:21
ralonsohbut my question is: do you need this generic classification?15:22
ralonsohyou have ipv4, 6, udp, ethernet and tcp15:22
ralonsoh5 types, if I'm not wrong15:22
davidshaAt the moment yes, it handles how classifcations can be retrieved only with they're ID when you don't know what type that ID is15:22
davidshaThere are 5 types, but when we were scoping out an RFE to enable security groups with Neutron classifier I think it would involve about 40 different protocols15:23
ralonsohyes, but you can build a classification only with known types15:24
ralonsohnow those types are these 515:24
ralonsohonly15:24
*** liuyulong has quit IRC15:25
davidshaNot necessarily, for the backend, it only provides the ID, it doesn't have what types the classifications are.15:25
ralonsohthe backend won't know what the classifications are?15:27
ralonsohhow are you going to implement the DSCP rules without this information?15:27
ralonsohin the backend15:27
*** belmoreira has joined #openstack-meeting15:27
ralonsohif you don't have this info, how are you going to config, for example, linux bridge with those specific dscp rules?15:27
davidshaThey do know the type by the time it's consumed, but it's just being provided classification group id as an arguement.15:28
ralonsohok, I still don't know why we need a generic classification table15:29
ralonsohplease, comment it in the review15:29
ralonsohI don't see any reason for that15:29
ralonsohas said, for me this is the same as the qos rules: there is no generic type15:30
amotokimlavalle: slaweq: I updated the neutron bug deputy schedule by adding a column of "note". we can keep the order :)15:30
*** kopecmartin is now known as kopecmartin|off15:30
slaweqamotoki: thx, but please don't disturb qos meeting here :)15:31
amotokiwoops.... I thought I was in #-neutron channel. sory15:31
ralonsohhahahaha15:31
ralonsohno problem amotoki15:31
davidshakk, I'll respond, it's basically to do with the API only having a "Classification" type, and the DB having the subtypes based on their definitions, I'll clarify in the patch15:31
ralonsohdavidsha, thank you! I need to understand this better15:32
ralonsohjust one last thing15:32
ralonsohboth patches (neutron and n-lib)15:32
ralonsohare the server part15:32
ralonsohdid you try  the agent implementation?15:33
*** mriedem has quit IRC15:33
ralonsohwhich backend are you using?15:33
davidshaYa, my next update is migrating in the advertiser and the classification AgentExtenionsAPIMixin that I had in the other patch15:33
davidshaFor the moment, I'm test with OvS15:34
ralonsohokidoki15:34
ralonsohand about the spec15:34
ralonsohdo you have something written down?15:34
davidshaSpec for the QoS integration? No, I'll start that now15:35
ralonsoh(you know this is not going to be approved for train, but just to start reviewing it)15:35
*** mriedem has joined #openstack-meeting15:35
davidshaThere is the one we used for defining the Classification API that was merged into Neutron Specs15:35
davidshakk15:35
ralonsohyes, but the justification to integrate this in Neutron15:36
ralonsohyou should be ready to present it in Shanghai15:36
davidshakk15:36
ralonsohthat was a good "interrogatory"!!15:36
ralonsohthank you davidsha15:36
davidshano prob, thanks!15:37
ralonsohis there something else to be discussed today in this meeting?15:37
ralonsohI think we can finish here15:38
ralonsohthank you all15:38
davidshacool, thanks!15:38
ralonsoh#endmeeting15:38
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"15:38
openstackMeeting ended Tue Jul 30 15:38:24 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:38
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_qos/2019/neutron_qos.2019-07-30-15.00.html15:38
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_qos/2019/neutron_qos.2019-07-30-15.00.txt15:38
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_qos/2019/neutron_qos.2019-07-30-15.00.log.html15:38
*** whoami-rajat has quit IRC15:39
*** belmoreira has quit IRC15:42
*** ttsiouts has quit IRC15:42
*** ttsiouts has joined #openstack-meeting15:42
*** tssurya has quit IRC15:46
*** _pewp_ has joined #openstack-meeting15:46
*** ttsiouts has quit IRC15:47
*** imsurit has quit IRC15:47
*** gyee has joined #openstack-meeting15:52
*** mlavalle has joined #openstack-meeting15:57
*** e0ne has quit IRC15:59
slaweq#startmeeting neutron_ci16:00
openstackMeeting started Tue Jul 30 16:00:40 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
slaweqhi again16:00
*** openstack changes topic to " (Meeting topic: neutron_ci)"16:00
openstackThe meeting name has been set to 'neutron_ci'16:00
ralonsohhi16:00
mlavalleo/16:00
*** radeks has joined #openstack-meeting16:00
slaweqI know that haleyb and bcafarel will be late so I think we can start16:01
slaweqI hope njohnston will join us soon :)16:01
slaweq#startmeeting neutron_ci16:01
openstackslaweq: Error: Can't start another meeting, one is in progress.  Use #endmeeting first.16:01
slaweq#undo16:01
slaweq#topic Actions from previous meetings16:01
*** openstack changes topic to "Actions from previous meetings (Meeting topic: neutron_ci)"16:01
slaweqfirst one:16:02
slaweqmlavalle to report bug with router migrations16:02
mlavalleI didn't report the bug but I started working on fixing it16:02
slaweq:)16:02
mlavalleI'll report it today16:02
slaweqthx a lot16:02
slaweqdo You have any ideas what is the root cause of this failure?16:02
mlavallehaven't got to the root yet16:03
slaweqok, so please report it this week that we can track it16:03
slaweq#action mlavalle to report bug with router migrations16:03
mlavallebut the problem is that the tests are failing because once the router is updated with...16:03
mlavalleadmin_state_up False16:03
mlavallethe router service ports (at least the one used for the interface) never gets down16:04
slaweqI remember we had such issue with some kind of routers in the past already16:04
mlavalleI can see it being removed from the hypervisor where it was originally scheduled16:04
mlavallebut the server doesn't catch it16:05
mlavallethat's where I am right now16:05
slaweqok, I think You should look into ovs-agent maybe as this agent is IMHO responsible for updating port status to DOWN or UP16:06
mlavalleyeap, that's where I am looking presently16:06
slaweqgreat16:06
slaweqthx mlavalle16:06
slaweqok, lets move on16:07
slaweqnext action item16:07
slaweqralonsoh to report bug with qos scenario test failures16:07
*** whoami-rajat has joined #openstack-meeting16:07
ralonsoh#link https://bugs.launchpad.net/neutron/+bug/183806816:07
openstackLaunchpad bug 1838068 in neutron ""QoSTest:test_qos_basic_and_update" failing in DVR node scenario" [Undecided,In progress] - Assigned to Rodolfo Alonso (rodolfo-alonso-hernandez)16:07
ralonsohand patch: #link https://review.opendev.org/#/c/673023/16:07
ralonsohin 20 secs:16:08
ralonsohforce to stop the ns process, close the socket from the test machine and set a socket timeout, to recheck it again if there is still time16:08
ralonsohthat;s all16:08
bcafarellate hi o/ (as promised)16:09
slaweqI hope this will help ralonsoh :)16:09
slaweqthx for the patch16:09
*** panda has quit IRC16:09
ralonsohno problem!16:09
slaweqbtw. I forgot at the beginning: http://grafana.openstack.org/d/Hj5IHcSmz/neutron-failure-rate?orgId=116:09
slaweqplease open it to be ready later :)16:09
slaweqok, next one16:10
slaweqslaweq to take a look at issue with dvr and metadata: https://bugs.launchpad.net/neutron/+bug/183076316:10
openstackLaunchpad bug 1830763 in neutron "Debug neutron-tempest-plugin-dvr-multinode-scenario failures" [High,In progress] - Assigned to Slawek Kaplonski (slaweq)16:10
slaweqI did, my findings are in https://bugs.launchpad.net/neutron/+bug/1830763/comments/13 and I proposed patch https://review.opendev.org/#/c/673331/16:10
slaweqlong story short: I found out that there is race condition and sometimes one L3 agent can have created 2 "floating ip agent gateway" ports for network16:10
slaweqand that cause later error in L3 agent during configuration of one of routers and metadata is not reachable in this router16:11
*** lpetrut has quit IRC16:11
slaweqso workaround which I proposed now should help to solve this problem in gate as we are always using only single controller node there16:11
slaweqand this can be also backported to stable branches if needed16:12
*** links has joined #openstack-meeting16:12
slaweqbut proper fix will IMO require some db changes to provide correct constraint on db level for that kind of ports16:12
slaweqI will work on it later16:12
*** panda has joined #openstack-meeting16:13
mlavalleso constraint the db and if when creating the gateway you get a duplicate ignore?16:13
njohnstono/ sorry I am late16:13
*** Lucas_Gray has quit IRC16:14
slaweqmlavalle: basically yes, something like that16:15
mlavalleack16:15
*** davidsha has quit IRC16:16
slaweqok, next one16:16
slaweqralonsoh to try a patch to resuce the number of workers in FT16:16
ralonsohslaweq, I've seen that the problems we have now in zuul is lower than 2/3 weeks ago16:17
ralonsohand this patch will slow down the FT execution16:17
ralonsohcan we hold this patch?16:17
slaweqralonsoh: so do You think that we should just wait to see how it will be in the future?16:17
ralonsohyes16:17
slaweq+1 for that, I also didn't saw many of such issues last week16:18
ralonsohreducing the number of workers (from 8 to 7) will reduce a lot the speed of FT executiuon16:18
slaweqralonsoh: do You know by how much it will slow down the job?16:18
ralonsohalmost proportionally to the core reduction16:18
ralonsohin this case, 12,5%16:19
slaweqso second question: do You know by how much it may improve stability of tests? :)16:20
ralonsohslaweq, I can't answer this question16:20
slaweqralonsoh: I though that :)16:20
slaweqok, lets maybe keep it as our last possible thing to do16:20
slaweqthx ralonsoh for checking that16:21
slaweqnext one16:21
ralonsohnp!16:21
slaweqralonsoh to report a bug and investigate failed test neutron.tests.fullstack.test_qos.TestMinBwQoSOvs.test_bw_limit_qos_port_removed16:21
*** lseki has joined #openstack-meeting16:21
ralonsohthat's the previous one16:21
ralonsohnope, my bad16:22
ralonsohno sorry, I didn't have time for this one16:22
slaweqok, no problem16:22
slaweqcan I assign it to You for next week than?16:22
slaweqjust to report it at least :)16:22
ralonsohI hope I have time, yes16:22
slaweqthx16:22
*** yonglihe has quit IRC16:22
*** arne_wiebalck has quit IRC16:22
slaweq#action ralonsoh to report a bug about failed test neutron.tests.fullstack.test_qos.TestMinBwQoSOvs.test_bw_limit_qos_port_removed16:23
slaweqthx ralonsoh16:23
slaweqok, that's all from last week16:23
slaweqany questions/comments?16:23
*** evgenyl has quit IRC16:24
slaweqok, so lets move on16:24
slaweq#topic Stadium projects16:24
*** openstack changes topic to "Stadium projects (Meeting topic: neutron_ci)"16:24
slaweqPython 3 migration16:24
slaweqStadium projects etherpad: https://etherpad.openstack.org/p/neutron_stadium_python3_status16:24
njohnstonI think we covered that really well in the neutron team meeting16:24
slaweqwe already discussed that on neutron meeting today16:24
slaweqright njohnston16:24
njohnstonslaweq++16:24
slaweq:)16:24
slaweqso lets move quickly to second part of this topic16:25
slaweqtempest-plugins migration16:25
slaweqEtherpad: https://etherpad.openstack.org/p/neutron_stadium_move_to_tempest_plugin_repo16:25
slaweqany progress on this?16:25
*** yonglihe has joined #openstack-meeting16:26
njohnstonI'll update the second part of the fwaas change today; escalations got the better of me this week16:26
*** evgenyl has joined #openstack-meeting16:26
slaweqsure, thx njohnston16:27
slaweqI know that tidwellr is also making some progress on neutron-dynamic-routing recently16:27
bcafarelI saw some recent updates by tidwellr on https://review.opendev.org/#/c/652099/ (though it's still in zuul checks)16:27
slaweqyep, it is16:27
mlavalleand I will try to make progress with vpn16:27
*** arne_wiebalck has joined #openstack-meeting16:28
*** rajinir has quit IRC16:28
slaweqso we are covered on this topic and I hope we will be ready with this at the end of T cycle16:28
bcafarelnot sure if it got already in latest revisions, but we should make sure all these new moved plugins have a config switch to enable/disable them16:28
bcafarel(as added for the 3 completed ones for 0.4.0 release)16:29
slaweqbcafarel: good point16:29
*** rajinir has joined #openstack-meeting16:30
slaweqok, I think we can move on to the next topic then16:30
slaweq#topic Grafana16:30
*** openstack changes topic to "Grafana (Meeting topic: neutron_ci)"16:30
slaweq#link http://grafana.openstack.org/dashboard/db/neutron-failure-rate16:30
slaweqwe didn't have many commits in gate queue recently so there is no data in last few days there16:32
slaweqbut lets look at check queue graphs16:32
njohnstoninteresting that in the last couple of hours there is a spike in failures across multiple charts in the check queue.  I wonder if someone is just pushing some really crappy changes.16:32
*** trident has quit IRC16:32
*** igordc has joined #openstack-meeting16:33
haleybi was nowhere the check queue :)16:33
njohnstonlol16:33
slaweqnjohnston: IMHO it is just getting back to normal as there was almost nothing running during the weekend16:34
*** evgenyl has quit IRC16:34
njohnstonoh, that makes sense16:34
slaweqnjohnston: but that is only my theory - lets keep an eye on it for next days :)16:35
njohnstonsounds good16:35
haleybis the midonet co-gating job healthy?  it's been 100% failure (non-voting)16:35
slaweqhaleyb: no, it's not16:35
njohnstonyeah, I think we mentioned that last week, yamamoto needs to take a look16:35
*** evgenyl has joined #openstack-meeting16:36
mlavalleI think he also mentioned he doesn't have much time16:36
*** rajinir has quit IRC16:36
*** trident has joined #openstack-meeting16:37
slaweqI will take a look into this job this week and try to check if it's always the same test(s) which are failing or maybe various ones16:37
slaweqand will report bug(s) for that16:37
slaweqsounds good for You?16:37
mlavalleyes16:37
haleybyes, good for me16:37
slaweq#action slaweq to check midonet job and report bug(s) related to it16:38
*** rajinir has joined #openstack-meeting16:38
slaweqother than that I think we are in pretty good shape recently16:38
slaweqany other questions/comments about grafana?16:39
mlavalleniot from me16:40
slaweqok, so lets move on then16:40
slaweq#topic fullstack/functional16:40
*** openstack changes topic to "fullstack/functional (Meeting topic: neutron_ci)"16:40
slaweqI was looking into some recent patches looking for some failures and I found only few of them16:41
slaweqfirst functional tests16:41
slaweqhttp://logs.openstack.org/12/672612/4/check/neutron-functional/e357646/testr_results.html.gz16:41
slaweqfailure in neutron.tests.functional.agent.linux.test_linuxbridge_arp_protect.LinuxBridgeARPSpoofTestCase16:41
slaweqbut this looks like issue related to host load, and we talked about it with ralonsoh already16:41
slaweqright ralonsoh?16:41
ralonsohI think so16:42
ralonsohyes, that's right16:42
slaweqand second issue which I found:16:42
slaweq    neutron.tests.functional.services.trunk.drivers.openvswitch.agent.test_trunk_manager.TrunkManagerTestCase16:42
slaweqhttp://logs.openstack.org/03/670203/10/check/neutron-functional/80d0831/testr_results.html.gz16:42
slaweqlooking at logs from this test: http://logs.openstack.org/03/670203/10/check/neutron-functional/80d0831/controller/logs/dsvm-functional-logs/neutron.tests.functional.services.trunk.drivers.openvswitch.agent.test_trunk_manager.TrunkManagerTestCase.test_connectivity.txt.gz16:43
slaweqI don't see anything obvious16:43
slaweqbut as it happend only once, lets just keep an eye on it for now16:44
slaweqdo You agree?16:44
njohnstonyes16:44
ralonsohthat's curious: the test is claiming that the ping process was not spawned, but it was16:44
mlavalle++16:44
slaweqralonsoh: true16:46
slaweqthat is strange16:46
*** ociuhandu has quit IRC16:46
*** ociuhandu has joined #openstack-meeting16:47
*** yonglihe_ has joined #openstack-meeting16:47
slaweqif I will have some time, I will take deeper look into this16:47
*** yonglihe has quit IRC16:47
*** yonglihe_ is now known as yonglihe16:47
slaweqmaybe at least to add some more logs which will help debugging such issues in the future16:47
slaweqany other issues related to functional tests?16:48
slaweqor can we continue?16:48
slaweqok, lets move on16:49
slaweqI don't have anything new related to fullstack for today16:49
slaweqso next topic16:49
slaweq#topic Tempest/Scenario16:50
*** openstack changes topic to "Tempest/Scenario (Meeting topic: neutron_ci)"16:50
slaweqfirst of all, my patch to tempest https://review.opendev.org/#/c/672715/ is merged16:50
slaweqso I hope it should be much better with SSH failured due to failing to get public-keys now16:51
njohnston\o/16:51
slaweqif You will see such errors now, let me know - I will investigate again16:51
mlavalleThanks!16:51
slaweqthis should help for all jobs which inherits from devstack-tempest16:51
slaweqso it will not solve problem in e.g. tripleo based jobs16:52
slaweq(just saying :))16:52
slaweqbut in neutron u/s gate we should be much better now I hope16:52
slaweqok16:52
slaweqfrom other things I spotted one new error in API tests:16:52
slaweqhttp://logs.openstack.org/30/670930/3/check/neutron-tempest-plugin-api/5a731da/testr_results.html.gz16:52
slaweqit is failure in neutron_tempest_plugin.api.test_port_forwardings.PortForwardingTestJSON16:53
slaweqlooks like issue in test for me, I will report bug and work on it16:53
slaweqok for You?16:53
mlavallesure16:53
slaweqthx16:54
slaweq#action slaweq to report and try to fix bug in neutron_tempest_plugin.api.test_port_forwardings.PortForwardingTestJSON16:54
slaweqok16:54
slaweqand that's all from my side for today16:54
slaweqanything else You want to discuss today?16:54
mlavallenot from me16:55
bcafarelcatching up on the recent activity, so nothing from me eiher :)16:55
slaweqok, thx for attending16:55
bcafarelnice recent findings btw (race condition, memcached in nova,  ...)16:55
slaweqand have a nice week16:55
slaweqthx bcafarel  :)16:55
slaweqo/16:56
slaweq#endmeeting16:56
bcafarelo/16:56
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"16:56
openstackMeeting ended Tue Jul 30 16:56:07 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:56
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_ci/2019/neutron_ci.2019-07-30-16.00.html16:56
ralonsohbye16:56
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_ci/2019/neutron_ci.2019-07-30-16.00.txt16:56
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_ci/2019/neutron_ci.2019-07-30-16.00.log.html16:56
njohnstono/16:56
*** mlavalle has left #openstack-meeting16:56
*** jamesmcarthur has quit IRC17:00
*** markvoelker has quit IRC17:03
*** ociuhandu has quit IRC17:07
*** ricolin has quit IRC17:11
*** links has quit IRC17:21
*** links has joined #openstack-meeting17:22
*** ralonsoh has quit IRC17:23
*** links has quit IRC17:26
*** jamesmcarthur has joined #openstack-meeting17:26
*** enriquetaso has quit IRC17:28
*** links has joined #openstack-meeting17:29
*** links has quit IRC17:32
*** brault has joined #openstack-meeting17:32
*** brault has quit IRC17:32
*** tesseract has quit IRC17:34
*** links has joined #openstack-meeting17:35
*** links has quit IRC17:37
*** armax has quit IRC17:40
*** links has joined #openstack-meeting17:42
*** links has quit IRC17:42
*** priteau has quit IRC18:02
*** Shrews has joined #openstack-meeting18:08
*** enriquetaso has joined #openstack-meeting18:15
*** armax has joined #openstack-meeting18:18
*** links has joined #openstack-meeting18:22
*** links has quit IRC18:22
*** yamamoto has joined #openstack-meeting18:27
*** yamamoto has quit IRC18:31
*** jamesmcarthur has quit IRC18:35
*** bbowen has quit IRC18:36
*** enriquetaso has quit IRC18:39
*** enriquetaso has joined #openstack-meeting18:40
*** bobh has quit IRC18:56
clarkbanyone else here for the weekly infra meeting?18:59
clarkbwe will get started in a couple minutes18:59
clarkb#startmeeting infra19:01
openstackMeeting started Tue Jul 30 19:01:19 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
ianwo/19:01
clarkbGood morning ianw19:01
clarkb#link http://lists.openstack.org/pipermail/openstack-infra/2019-July/006431.html19:01
clarkb#topic Announcements19:01
*** openstack changes topic to "Announcements (Meeting topic: infra)"19:01
clarkbI think everyone is having too much fun debugging web browser behavior. That is ok I don't have any announcements19:02
fungiheh, "fun"19:02
clarkb#topic Actions from last meeting19:03
*** openstack changes topic to "Actions from last meeting (Meeting topic: infra)"19:03
clarkbmordred: any progress on the github actions?19:04
clarkbfwiw hogepodge was asking about zuul mirror on github because someone was asking him19:04
mordredoh it's meeting time19:04
mordredno19:04
clarkbso we may want to get that sorted soon to make it clearer to people19:04
mordredyes19:04
clarkb#action mordred create opendevadmin github account19:05
mordredsorry - I keep bouncing off the github api part of it - I'll try harder to not bounce off19:05
clarkb#action mordred clean up openstack-infra github org19:05
clarkbmordred: is the scope of the problem small enough that we can click buttons? we had a lot of repos so probably not?19:05
mordredprobably not - given how many repos we have19:05
clarkbya I guess that would be a lot of clicking19:06
clarkb#topic Priority Efforts19:06
*** openstack changes topic to "Priority Efforts (Meeting topic: infra)"19:06
corvuswhat do we need to do there?19:06
clarkb#undo19:06
openstackRemoving item from minutes: #topic Priority Efforts19:06
corvuswe're what, force-pushing "moved" messages to the repos?19:06
clarkbcorvus: archive all of the repos under https://github.com/openstack-infra19:06
mordredoh - you know ... yeah - I think I might have been fixating too much on the archive thing19:06
corvuswe're archiving them?19:07
mordredjust force-pushing "we've moved" is a bit easier19:07
clarkbwell I think archive does what we want?19:07
clarkbit gives a banner that says "this repo is RO and archived and doesn't live here anymore" type of message19:07
corvusdoes it say where it does live?19:07
mordredhow about I start with the force-push - and we can come back to the archive later?19:07
fungii'd be fine with just deleting them, but maybe i'm not thinking of the users19:07
clarkbcorvus: I'm not sure if the message is configurable by the user19:07
mordredforce-push (or really even just a regular push) is super easy and I can have that done pretty quickly19:08
corvusfungi: anything without a new location is no better than a delete from my pov19:08
clarkbmordred: but ya pushing something that says the content is over there: works too then if we archive it will just make that ab it more explicit19:08
fungithe archive message does not appear to be configurable when i looked19:08
mordredyeah19:08
mordredso - I'll work on force-push19:08
fungiso it would need to be readme/description/something19:08
mordredthen later, when we feel like it, we can archive or not archive as we feel like19:08
clarkbok19:08
mordredfungi: yeah - I'm thikning a normal retire-this-repo type commit19:08
mordredleaving only a README with a "this is now elsewhere"19:08
mordredpointing to the elsewhere19:09
corvusokay, then the 2 options i like are: 1) push readme + archive; 2) delete.  the one thing i don't want to do is archive without readme.19:09
mordredI think push readme is the absolute easiest19:09
corvus(because archive without readme looks even more like the project terminated than just deleting it)19:09
clarkbsounds like 1) is the current plan. mordred any reason that you don't think 1) will work?19:10
corvuscool, let's action that explicitly so we don't forget which way we decided to "clean up" the org :)19:10
mordrednope. I am very confident in 1 - or at least the 1st part - and I think the second part is a get-to-it-later thing - since that's a new feature that hasn't even existed that long19:10
*** diablo_rojo has joined #openstack-meeting19:11
mordredso I don't think we have to say "we must use the new gh feature that lets you mark a repo readonly" - since those are readonly anyway19:11
clarkb#action mordred Push commits to repos under github.com/openstack-infra to update READMEs explaining where projects live now. Then followup with github repo archival when that can be scripted.19:11
corvus\o/19:11
mordred++19:11
corvusthanks mordred19:11
clarkb#topic Priority Efforts19:11
*** openstack changes topic to "Priority Efforts (Meeting topic: infra)"19:11
fungiyeah, the deeper i looked into the "archive" option the less convinced i became that it's super useful19:12
fungi(for us)19:12
mordred++19:12
clarkb#topic OpenDev19:12
*** openstack changes topic to "OpenDev (Meeting topic: infra)"19:12
clarkbfungi has done a bunch of work over the last week or so to replace our gitea backends. Thank your fungi!19:12
clarkbThese gitea backends all have 80GB of disk now instead of 40GB. That should give us plenty of room for growth as repos are adding and otherwise have commits pushed to them.19:12
clarkbThis process has also added 8GB swapfiles to address the OOMing we saw and the images we used have properly sized ext4 journals19:13
clarkbthat should make teh servers happier19:13
fungiand improve performance as well as stability/integrity19:13
clarkbSome things we have learned in the process: the /var/gitea/data/git/.gitconfig.lock files can go stale when the servers have unhappy disks. When that happens all replications fail to that host19:14
clarkbIf we end up doing bulk replications in the future we want to double check that file isn't stale (check timestamp and dmesg -T for disk errors) before trigger replication19:14
clarkbunfortunately from gerrit's perspective replication succeeds and it moves on, but the data doesn't actually update on the gitea server19:14
*** eharney has quit IRC19:15
clarkbfungi: ^ anything else you think we should call out from that process?19:15
corvuswe should also try to figure out where the sshd logs are going and fix that19:15
clarkb++19:15
clarkbthere is a good chance they go to syslog like the haproxy logs19:15
corvuscause i think that would have helped debugging (we learned about the problem via strace)19:15
clarkband if we mount /dev/log into the container we'll get the logs on the host syslog19:15
fungiyeah, nothing other than we also added health checks in haproxy19:15
corvusor maybe we can add an option to send them to stdout/stderr?19:16
fungiand got it restarting on config updates19:16
corvusbecause we run sshd in the foreground19:16
corvusthough i don't know if that is compatible with its child processes19:16
clarkb-e      Write debug logs to standard error instead of the system log.19:16
clarkbthat might work19:16
fungiyeah, or i think sshd_config can be set for it19:16
fungieither one19:16
clarkbchanges to the docker file should all be tested19:17
clarkb#action infra Update gitea sshd container to collect logs (either via stderr/stdout or syslog)19:18
clarkb#topic Update Configuration Management19:19
*** openstack changes topic to "Update Configuration Management (Meeting topic: infra)"19:19
clarkbmordred: has been doing a bunch of work to build docker images for gerrit19:19
clarkbI think we should now (or very soon once jobs run) have docker images for gerrit 2.13, 2.15, 2.16, and 3.019:19
clarkbmordred: is the next step in that process to redeploy review-dev using the 2.13 image?19:19
*** mriedem has quit IRC19:20
mordredclarkb: yes.19:20
mordredwell - the next step will be writing a little config management to do that19:20
mordredbut yes19:20
clarkbexciting19:20
clarkbianw: on the ansible'd mirror side of thigns I had to reboot the new mirror in fortnebula that fungi built recently to get the afs mounts in place (it was failing the ansible afs sanity checks prior to that)19:21
clarkbianw: have all the fixes related to that merged? I thought I had approved the one fix you had called out. But maybe we need to add a modprobe to the ansible?19:22
ianwyes, afaik19:22
clarkbone thing it could be is if dkms only builds the module for the latest kernel on the host but we haven't rebooted into that kernel yet?19:23
fungiyeah, afs clients will need a reboot partway through configuration (or maybe just a modprobe)19:23
fungii believe dkms will do it for all installed kernels by defauly19:23
ianwin CI testing we do build and then test straight away19:23
fungidefault19:23
clarkbhrm behavior difference between cloud images and nodepool images maybe?19:24
clarkbsomething to look at closer when we build more opendev mirrors I guess19:24
fungimaybe when ansible installed the openafs packages it didn't wait long enough for the dkms builds to complete?19:24
fungimaybe longer because more kernels?19:24
clarkbfungi: it should wait for apt-get to return19:24
ianwmaybe ... the dpkg doesn't return till it's done19:24
ianwhard to say at this point, as you say something to watch with a new server19:24
ianwi didn't notice this doing the other rax openafs based opendev.org servers, iirc19:25
clarkbAny other configuration management updates/bugs to call out?19:25
clarkbSounds like now19:27
clarkb#topic Storyboard19:27
*** openstack changes topic to "Storyboard (Meeting topic: infra)"19:27
clarkbfungi: diablo_rojo: anything to call out for storyboard?19:27
fungii don't think we have anything new and exciting this week19:27
diablo_rojoNothing new, except to beg again for sql help19:27
diablo_rojomordred, would you have some time in the next week or so to look at the querylogs and suggest some changes?19:28
diablo_rojoBetter yet, make some changes..19:28
mordreddiablo_rojo: yes - I will look at them in the next week or so19:29
diablo_rojomordred, thank you thank you thank you19:29
fungii can try to follow the earlier example of generating a fresh analysis of the slow query log and publishing that, at least19:29
fungibut my sql-fu doesn't run very deep19:29
fungiso beyond a git grep for some of the combinations of field names to see where those queries could be coming from (or guessing based on what they look like they're trying to do) i don't know that i'll be able to run many of them down19:30
clarkbdoes sqlalchemy have a way to annotate queries with that info?19:31
clarkb(I'm guessing now because sql)19:31
clarkb*no19:31
clarkblike comments would just get thrown out before the slow query log ever sees them19:31
*** mriedem has joined #openstack-meeting19:32
clarkbSounds like that may be it? lets move on19:33
clarkb#topic General Topics19:33
*** openstack changes topic to "General Topics (Meeting topic: infra)"19:33
clarkbTrusty server update progress19:33
clarkb#link https://etherpad.openstack.org/p/201808-infra-server-upgrades-and-cleanup19:33
fungiclarkb got wiki-dev puppeting!19:33
clarkbI think puppet is running successfully on wiki-dev02 now19:33
fungiyeah, it's probably time to delete it and boot another one now19:34
clarkbfungi: what is the next step there? testing that the wiki works?19:34
clarkbah ok so start from fresh, make sure that works, then maybe copy data from prod wiki ?19:34
fungijust to make sure things still get puppeted smoothly from the get-go19:34
clarkb++19:34
fungiand then exercise it and try adding a copy of the db19:34
clarkbsounds good19:35
fungii can try to poke at that some now that the gitea replacements are behind us19:35
clarkbSeparately corvus has been adding features to make browsing logs in zuul's web ui possible19:35
clarkbThose changes merged yesterday. And today there has been much debugging19:35
clarkbI think this is the last major step in getting us to a point where logs.o.o can be a swift container19:36
clarkbcorvus: ^ anything to add to that?19:36
*** bobh has joined #openstack-meeting19:36
corvusat some point, this will become the default report url for jobs19:36
corvusso instead of linking directly to the log server when we report a job back, we'll link to zuul's build page19:36
fungithat will be great19:37
clarkbIt should give people more of what they expect if they've used a tool like travisci previously19:37
corvusideally, i think we'd want to make that switch before we switch to swift (from a UX pov), but technically they are orthogonal19:37
clarkbya I think this work makes the swift change far less painful for our users because the zuul experience should remain the same19:37
corvus(because i think the transition of osla -> zuul-js is better than osla -> swift static -> zuul-js)19:38
corvusso yeah, i think debugging this, then flipping that switch, then swift are the next major steps19:38
fungialso the lack of autoindex if we point them directly at logs in swift, right?19:38
fungithis way zuul acts as the file index19:39
clarkbfungi: we actually do get autoindex in swift if you toggle the feature19:39
fungioh, cool19:39
*** dtrainor has quit IRC19:39
clarkbbut the way zuul does it should be much nicer19:39
*** senrique_ has joined #openstack-meeting19:39
corvusfungi: we have static index generation to compensate for that, but i'd rather not use it19:39
fungiwe just previously used swifts which didn't19:39
fungioh, also good point, i forgot we worked out uploading prebuilt file indices19:39
corvuswell, we actually put some static generation into the swift roles so we didn't have to rely on that19:39
corvusbut yeah, neither that, nor the static severity stuff is better than osla, but i think that zuul-js is (or, at the least, no worse).  so if we can do it in the order i propose, that's better19:40
clarkb++19:40
fungii concur19:40
clarkbNext up on the agenda is a quick cloud status update19:41
fungione remaining blocker to doing them in that order is to add https for logs.openstack.org, yeah?19:41
*** enriquetaso has quit IRC19:41
clarkbfungi: ya or we serve the zuul links with http://19:41
corvusfungi: ah, yes.  or remove https from zuul.  :|19:41
clarkbI think we can do https://logs.opendev.org easily19:42
*** bobh has quit IRC19:42
clarkbthen set the CORS headers appropriately19:42
corvuswe should double check all the swifts we plan to use19:42
corvusoh, someone said that most of those should be under the swift api anyway, right?  so should be https?19:42
clarkbcorvus: yes I would expect them to be https19:42
clarkbwe should double check but I'm not super worried about it19:43
corvusthat would only leave rax, and technically that needs a bit more work anyway to support the cdn stuff19:43
corvus(er, i mean that would leave rax as something to investigate)19:43
clarkbOn the cloud test resources side of things donnyd has rebuilt the fortnebula control plane and we've run into some networking trouble with the mirror after that. I'll look at that after the meeting19:44
clarkbOnce that is sorted out I think we are hopefully near a longer term setup with that cloud whcih we can use going forward19:45
clarkbmordred: any news on MOC enabling service tokens?19:45
clarkb(or whatever that term is I'm searching for)19:45
clarkbWe must've lost mordred19:47
clarkbI'll try to followup on that after the meeting too19:47
clarkbLast up is PTG planning. Still quite a bit early but if you have any idea you can put them up at:19:47
clarkb#link https://etherpad.openstack.org/p/OpenDev-Shanghai-PTG-201919:47
clarkbcorvus: related to ^ I'm going to start sorting out the gitea stuff too19:49
corvusclarkb: thanks19:49
clarkbAnd that was the agenda19:50
clarkb#topic Open Discussion19:50
*** openstack changes topic to "Open Discussion (Meeting topic: infra)"19:50
corvusdid folks see the ml post about rget?19:51
corvusi know there were some replies19:51
corvussounds like we have consensus to proceed19:51
clarkbdid not hear anything say it was a bad idea19:51
fungiyeah, to reiterate here, it sounds like a worthwhile thing to participate in19:51
corvus#link http://lists.openstack.org/pipermail/openstack-discuss/2019-July/008107.html19:51
corvusi'm a little unclear about the githubiness of that...19:52
corvusfrom what i can see, it doesn't look like it should be an issue19:52
corvusbut the authors seem to think maybe there's a little more work?  https://github.com/merklecounty/rget/issues/119:53
clarkbI think they've done some magic to handle github urls specially19:53
clarkbbut my read of it was that this wasn't required19:53
clarkbwe can feed it a tarballs.o.o url and validate that19:53
corvusat any rate, it seems like they don't want to require github, so any issues we run into we should be able to resolve19:54
clarkboh that issue contradicts my read of it19:54
clarkbbut ya seems they'll be likely to fix that for us19:54
corvusyeah, i think i'm going to go stick a static file on a private server and see what breaks :)19:54
clarkbthe way the certs end up into the certificate transparency log shouldn't prevent any domain from working19:55
fungii have personal projects where i already publish sha256sums i can easily test with as well19:55
corvus(maybe the client isn't the big issue?  maybe it's the something the server does?)19:55
clarkbthey do mangle the path component and the hostname though19:55
clarkband with github it isn't a 1:1 I guess that is what they have to sort out19:55
*** whoami-rajat has quit IRC19:57
clarkbI'll let everyone got get breakfast/lunch/dinner now.19:58
clarkbThank you all!19:58
clarkb#endmeeting19:58
fungithanks clarkb!19:58
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"19:58
openstackMeeting ended Tue Jul 30 19:58:09 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:58
openstackMinutes:        http://eavesdrop.openstack.org/meetings/infra/2019/infra.2019-07-30-19.01.html19:58
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/infra/2019/infra.2019-07-30-19.01.txt19:58
openstackLog:            http://eavesdrop.openstack.org/meetings/infra/2019/infra.2019-07-30-19.01.log.html19:58
diablo_rojoThanks clarkb!19:58
*** Shrews has left #openstack-meeting19:58
*** dtrainor has joined #openstack-meeting19:59
*** radeks has quit IRC20:03
*** diablo_rojo has quit IRC20:06
*** e0ne has joined #openstack-meeting20:16
*** vishalmanchanda has quit IRC20:32
*** bbowen has joined #openstack-meeting20:36
*** pabelanger has quit IRC20:37
*** links has joined #openstack-meeting20:38
*** e0ne has quit IRC20:41
*** bobh has joined #openstack-meeting20:42
*** e0ne has joined #openstack-meeting20:42
*** zbitter is now known as zaneb20:44
*** belmoreira has joined #openstack-meeting20:44
*** eharney has joined #openstack-meeting20:46
*** bobh has quit IRC20:48
*** igordc has quit IRC20:50
*** links has quit IRC20:57
*** bobh has joined #openstack-meeting21:05
*** bobh has quit IRC21:05
*** bbowen has quit IRC21:06
*** e0ne has quit IRC21:16
*** gyee has quit IRC21:23
*** belmoreira has quit IRC21:32
*** belmoreira has joined #openstack-meeting21:37
*** gyee has joined #openstack-meeting21:42
*** njohnston has quit IRC21:52
*** belmoreira has quit IRC21:53
*** slaweq has quit IRC21:53
*** njohnston has joined #openstack-meeting21:54
*** bobh has joined #openstack-meeting21:59
*** bobh has quit IRC21:59
*** diablo_rojo has joined #openstack-meeting22:00
*** raildo has quit IRC22:02
*** jamesmcarthur has joined #openstack-meeting22:09
*** panda has quit IRC22:15
*** panda has joined #openstack-meeting22:18
*** diablo_rojo has quit IRC22:19
*** eharney has quit IRC22:26
*** carloss has quit IRC22:27
*** yamamoto has joined #openstack-meeting22:29
*** yamamoto has quit IRC22:33
*** jamesmcarthur has quit IRC22:39
*** armax has quit IRC22:41
*** senrique_ has quit IRC22:41
*** mriedem has quit IRC22:45
*** dviroel has quit IRC22:51
*** bobh has joined #openstack-meeting22:54
*** ykatabam has joined #openstack-meeting22:59
*** rcernin has joined #openstack-meeting23:01
*** rfolco|ruck has quit IRC23:02
*** brault has joined #openstack-meeting23:06
*** brault has quit IRC23:10
*** slaweq has joined #openstack-meeting23:11
*** yamamoto has joined #openstack-meeting23:11
*** stevebaker is now known as stevebaker223:13
*** slaweq has quit IRC23:15
*** lseki has quit IRC23:20
*** armax has joined #openstack-meeting23:44

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