Tuesday, 2018-08-28

*** gyee has quit IRC00:02
*** tetsuro has joined #openstack-meeting00:08
*** longkb has joined #openstack-meeting00:11
*** slaweq has joined #openstack-meeting00:11
*** slaweq has quit IRC00:16
*** macza has quit IRC00:17
*** macza has joined #openstack-meeting00:17
*** macza has quit IRC00:20
*** ykatabam has joined #openstack-meeting00:54
*** imacdonn has quit IRC01:18
*** imacdonn has joined #openstack-meeting01:18
*** yamahata has quit IRC01:25
*** hongbin has joined #openstack-meeting01:39
*** dtrainor_ has quit IRC01:51
*** dtrainor has joined #openstack-meeting01:51
*** slaweq has joined #openstack-meeting02:11
*** slaweq has quit IRC02:16
*** apetrich has quit IRC02:19
*** annabelleB has joined #openstack-meeting02:23
*** annabelleB has quit IRC02:26
*** dtrainor has quit IRC02:40
*** dtrainor has joined #openstack-meeting02:40
*** yamamoto has joined #openstack-meeting02:42
*** psachin has joined #openstack-meeting02:55
*** ricolin has joined #openstack-meeting03:08
*** sagara has joined #openstack-meeting03:13
*** dtrainor_ has joined #openstack-meeting03:34
*** dtrainor has quit IRC03:34
*** hongbin has quit IRC03:43
*** yamamoto has quit IRC03:46
*** ykatabam has quit IRC03:49
*** yamamoto has joined #openstack-meeting03:51
*** dtrainor has joined #openstack-meeting03:53
*** samP has joined #openstack-meeting03:54
*** dtrainor_ has quit IRC03:54
*** ykatabam has joined #openstack-meeting03:54
samPHi all for masakari04:00
*** tpatil has joined #openstack-meeting04:00
samP#startmeeting masakari04:00
openstackMeeting started Tue Aug 28 04:00:32 2018 UTC and is due to finish in 60 minutes.  The chair is samP. Information about MeetBot at http://wiki.debian.org/MeetBot.04:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.04:00
*** openstack changes topic to " (Meeting topic: masakari)"04:00
openstackThe meeting name has been set to 'masakari'04:00
samPHi all04:00
tpatilHi04:00
samPtpatil: Hi04:01
sagaraHi04:01
samPsagara: Hi04:01
*** sagara has quit IRC04:01
samPI guess noting much to discuss... anyway Let's start the meeting04:02
samP#topic bug/patches discussion04:02
*** openstack changes topic to "bug/patches discussion (Meeting topic: masakari)"04:02
tpatilas discussed in last IRC meeting, there are 4 patches to be reviewed04:03
*** qwebirc1660 has joined #openstack-meeting04:03
tpatilproposed against critical LP bug04:03
tpatilsamP and sagara: could you please review those patches04:04
samPtpatil: Thanks for reminder. I will review right after this meeting.04:04
tpatilsamP: thanks04:04
tpatil#link : https://review.openstack.org/#/q/topic:bug/1779752+(status:open+OR+status:merged)04:04
tpatil#link : https://review.openstack.org/#/c/591557/04:04
tpatil#link : https://review.openstack.org/#/c/562973/04:04
tpatilthe last two patches, let us know whether it should be back ported to stable/rocky branch or nor04:05
tpatils/nor/not04:05
samPtpatil: I will check them04:05
tpatilsamP: ok04:06
samPNeed to review import zuul job patches from Nguyen for all masakari projects04:07
samPAny other patches or bug need to discuss?04:08
tpatilthese patches are targeted for stein release, correct?04:08
samPtpatil: correct04:08
tpatilI think he has back ported these patches for stable branches as well04:09
tpatilDo we need to review those patches?04:09
tpatile..g https://review.openstack.org/#/c/592987/04:09
samPtpatil: yes, backports are also there.04:10
samPno need to review backports. Let's finish the patches on master. Then I will review and merge the backport patches.04:10
tpatilok04:11
*** slaweq has joined #openstack-meeting04:11
samP#topic PTG04:13
*** openstack changes topic to "PTG (Meeting topic: masakari)"04:13
samPSorry, could not finish the etherpad. definitely finish it before next week.04:13
samPMasakari meeting time is Sept. 11 (Tuesday)04:15
*** slaweq has quit IRC04:15
samPWe can skip IRC meeting on same day, cause we are meeting F2F04:15
tpatilOk04:15
samP#topic AOB04:16
*** openstack changes topic to "AOB (Meeting topic: masakari)"04:16
samPAny other items/issues need to discuss?04:16
tpatilNo04:17
*** Bhujay has joined #openstack-meeting04:18
samPOK then, it is a sort meeting but, we can finish today's meeting here04:18
samPThank you for your time.04:18
qwebirc1660Thank you04:18
tpatilThank you04:19
qwebirc1660sorry04:19
*** Bhujay has quit IRC04:19
samPPlease use openstack-dev ML with [masakari] or #openstack-masakari on IRC for further discussion.04:19
samPqwebirc1660: is this sagara san?04:19
qwebirc1660yes04:20
*** qwebirc1660 is now known as sagara04:20
samPqwebirc1660: :) thanks. I saw you drop.. thanks for re-join04:20
sagarasorry, I forgot to change my nick04:20
samPsagara: NP.. we finished early.04:21
samPCU then.04:21
sagaraAnyway, thank you for toady's meeting. bye.04:21
samPbye04:21
samP#endmeeting04:21
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"04:21
openstackMeeting ended Tue Aug 28 04:21:32 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)04:21
openstackMinutes:        http://eavesdrop.openstack.org/meetings/masakari/2018/masakari.2018-08-28-04.00.html04:21
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/masakari/2018/masakari.2018-08-28-04.00.txt04:21
openstackLog:            http://eavesdrop.openstack.org/meetings/masakari/2018/masakari.2018-08-28-04.00.log.html04:21
*** samP has left #openstack-meeting04:21
*** sagara has quit IRC04:23
*** tpatil has quit IRC04:24
*** dtrainor_ has joined #openstack-meeting04:26
*** dtrainor has quit IRC04:26
*** tdasilva has quit IRC04:27
*** haleyb has quit IRC04:54
*** armax has quit IRC04:59
*** macza has joined #openstack-meeting05:00
*** annabelleB has joined #openstack-meeting05:01
*** slaweq has joined #openstack-meeting05:11
*** slaweq has quit IRC05:16
*** ykatabam has quit IRC05:18
*** tetsuro has quit IRC05:24
*** janki has joined #openstack-meeting05:26
*** dtrainor_ has quit IRC05:27
*** dtrainor has joined #openstack-meeting05:27
*** slaweq has joined #openstack-meeting05:28
*** bnemec has quit IRC05:30
*** bnemec has joined #openstack-meeting05:31
*** ykatabam has joined #openstack-meeting05:33
*** slaweq has quit IRC05:33
*** tetsuro has joined #openstack-meeting06:08
*** tetsuro has quit IRC06:09
*** slaweq has joined #openstack-meeting06:11
*** radeks has joined #openstack-meeting06:12
*** macza has quit IRC06:12
*** radeks_ has joined #openstack-meeting06:14
*** apetrich has joined #openstack-meeting06:15
*** slaweq has quit IRC06:16
*** radeks has quit IRC06:16
*** yamahata has joined #openstack-meeting06:32
*** jchhatbar has joined #openstack-meeting06:35
*** janki has quit IRC06:38
*** pcaruana has joined #openstack-meeting06:39
*** aojea has joined #openstack-meeting06:40
*** yamamoto has quit IRC06:54
*** ykatabam has quit IRC06:54
*** tetsuro has joined #openstack-meeting06:57
*** yamamoto has joined #openstack-meeting06:58
*** alexchadin has joined #openstack-meeting07:00
*** rcernin has quit IRC07:02
*** slaweq has joined #openstack-meeting07:02
*** tetsuro has quit IRC07:07
*** tssurya has joined #openstack-meeting07:08
*** dims has quit IRC07:08
*** dims has joined #openstack-meeting07:10
*** kopecmartin has joined #openstack-meeting07:24
*** joxyuki has joined #openstack-meeting07:43
*** hadai has joined #openstack-meeting07:58
*** dangtrinhnt_x has joined #openstack-meeting08:06
*** dangtrinhnt_x has quit IRC08:10
*** macza has joined #openstack-meeting08:11
*** macza has quit IRC08:16
*** tetsuro has joined #openstack-meeting08:19
*** yamamoto has quit IRC08:19
*** yamamoto has joined #openstack-meeting08:20
*** akozhevnikov has joined #openstack-meeting08:27
*** ttsiouts has joined #openstack-meeting08:29
*** jchhatbar is now known as janki08:37
*** e0ne has joined #openstack-meeting08:43
*** apetrich has quit IRC08:43
*** electrofelix has joined #openstack-meeting08:46
*** yamamoto_ has joined #openstack-meeting08:58
*** rcernin has joined #openstack-meeting08:59
*** yamamoto has quit IRC08:59
*** priteau has joined #openstack-meeting09:00
*** sambetts|afk has quit IRC09:03
*** ttsiouts has quit IRC09:05
*** sambetts_ has joined #openstack-meeting09:06
*** takamatsu has joined #openstack-meeting09:15
*** hadai has quit IRC09:26
*** ttsiouts has joined #openstack-meeting09:30
*** joxyuki has quit IRC09:31
*** alexchadin has quit IRC09:31
*** erlon has joined #openstack-meeting09:44
*** nguyenhai_ has joined #openstack-meeting09:45
*** rcernin has quit IRC09:47
*** nguyenhai has quit IRC09:49
*** longkb has quit IRC10:00
*** ttsiouts has quit IRC10:01
*** tetsuro has quit IRC10:02
*** alexchadin has joined #openstack-meeting10:04
*** Emine has joined #openstack-meeting10:11
*** Emine has quit IRC10:14
*** Emine has joined #openstack-meeting10:14
*** stephenfin has quit IRC10:35
*** stephenfin has joined #openstack-meeting10:36
*** ttsiouts has joined #openstack-meeting10:52
*** alexchadin has quit IRC10:56
*** alexchadin has joined #openstack-meeting10:56
*** alexchadin has quit IRC10:56
*** alexchadin has joined #openstack-meeting10:57
*** alexchadin has quit IRC10:57
*** alexchadin has joined #openstack-meeting10:58
*** alexchadin has quit IRC10:58
*** alexchadin has joined #openstack-meeting10:58
*** alexchadin has quit IRC10:59
*** dmacpher__ has joined #openstack-meeting11:03
*** dmacpher_ has quit IRC11:07
*** erlon has quit IRC11:22
*** ricolin has quit IRC11:24
*** slagle has joined #openstack-meeting11:30
*** alexchadin has joined #openstack-meeting11:35
*** tpsilva has joined #openstack-meeting11:36
*** yamamoto_ has quit IRC11:39
*** yamamoto has joined #openstack-meeting11:39
*** alexchadin has quit IRC11:41
*** mmethot has joined #openstack-meeting11:48
*** giblet_off is now known as gibi11:49
*** alexchadin has joined #openstack-meeting11:51
*** raildo has joined #openstack-meeting12:08
*** yamamoto has quit IRC12:09
*** Emine has quit IRC12:17
*** Emine has joined #openstack-meeting12:21
*** sambetts_ is now known as sambetts12:26
*** mriedem has joined #openstack-meeting12:35
*** yamamoto has joined #openstack-meeting12:36
*** kosamara has quit IRC12:50
*** _hemna has quit IRC12:57
*** _pewp_ has joined #openstack-meeting12:58
*** eharney has quit IRC12:58
*** _hemna has joined #openstack-meeting12:58
*** annabelleB has joined #openstack-meeting13:01
*** r-mibu has joined #openstack-meeting13:03
*** dangtrinhnt_x has joined #openstack-meeting13:11
*** tdasilva has joined #openstack-meeting13:13
*** jchhatbar has joined #openstack-meeting13:14
*** chenyb4 has joined #openstack-meeting13:15
*** Emine has quit IRC13:16
*** janki has quit IRC13:17
*** dustins has joined #openstack-meeting13:18
*** jchhatbar has quit IRC13:19
*** janki has joined #openstack-meeting13:20
*** apetrich has joined #openstack-meeting13:27
*** rubasov has joined #openstack-meeting13:28
*** efried is now known as efried_doc13:29
*** stephenfin has quit IRC13:33
*** annabelleB has quit IRC13:34
*** rtjure has quit IRC13:34
*** stephenfin has joined #openstack-meeting13:34
*** rtjure has joined #openstack-meeting13:37
*** psachin has quit IRC13:39
*** Emine has joined #openstack-meeting13:40
*** liuyulong has joined #openstack-meeting13:42
*** dangtrinhnt_x has quit IRC13:45
*** dangtrinhnt_x has joined #openstack-meeting13:47
*** psachin has joined #openstack-meeting13:49
*** eharney has joined #openstack-meeting13:50
*** dangtrinhnt_x has quit IRC13:52
*** mlavalle has joined #openstack-meeting13:52
*** annp_ has joined #openstack-meeting13:54
*** awaugama has joined #openstack-meeting13:57
*** psachin has quit IRC13:58
mlavalle#startmeeting networking14:00
openstackMeeting started Tue Aug 28 14:00:05 2018 UTC and is due to finish in 60 minutes.  The chair is mlavalle. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** openstack changes topic to " (Meeting topic: networking)"14:00
openstackThe meeting name has been set to 'networking'14:00
annp_hi mlavalle14:00
*** hongbin has joined #openstack-meeting14:00
rubasovo/14:00
hongbino/14:00
*** mjturek has joined #openstack-meeting14:00
slaweqhi14:00
*** manjeets_ has joined #openstack-meeting14:01
manjeets_hi14:01
mlavalleHi Team, nice to see you all!14:01
annp_hi14:01
*** shintaro has joined #openstack-meeting14:01
mlavalleLet's get going14:02
mlavalle#topic Announcements14:02
*** openstack changes topic to "Announcements (Meeting topic: networking)"14:02
*** manjeets_ has quit IRC14:02
mlavalleThis week the community releases OpenStack Rocky14:02
bcafarelo/14:02
mlavalleThanks you very much to all of you for your hard work14:02
*** manjeets_ has joined #openstack-meeting14:03
mlavallewe made it to the end of another cycle14:03
*** amotoki has joined #openstack-meeting14:03
slaweq\o/14:03
-amotoki- needs to be offline next 20 mins unfortunately. will be back after that.14:03
*** amotoki has quit IRC14:03
*** chenyb4 has quit IRC14:04
bcafarelcongrats to the rocky contributors, now on to stein :)14:04
mlavalleThe Stein PTG starts in a little less than two weeks in Denver. I am looking forward to see you many of you there \o/14:04
manjeets_++14:04
mlavalleRemember that the etherpad is here:14:04
mlavalle#link  https://etherpad.openstack.org/p/neutron-stein-ptg14:05
mlavalleYesterday I had a quick conversation with melwitt and it seems we don't have Nova / Neutron cross projects topics to discuss this time around....14:05
*** njohnston has joined #openstack-meeting14:06
mlavallerubasov: do we need to discuss anything with the Nova team regarding bandwidth based scheduling?14:06
njohnstono/14:06
*** amotoki has joined #openstack-meeting14:06
*** haleyb has joined #openstack-meeting14:06
rubasovmlavalle: I'm not aware of anything14:06
mlavallerubasov: that's cool. I don't want to force it. Just in case we had something pending14:07
mlavallein any case, if the team thinks of anything we should discuss with Nova, please add it to the etherpad14:07
rubasovmlavalle: gibi thinks the same, so I'm quite sure14:07
mlavallerubasov: cool, then14:08
* haleyb was lost in the ether somewhere or there was a netsplit14:08
bcafarelhaleyb: looks like you found your way back in the end14:08
-amotoki- needs to be offline next 15 mins. will be back then.14:08
*** amotoki has quit IRC14:08
mlavalleLike last year, we are going to have our team dinner on Thursday 13th. I was thinking going to the same place we went last year: https://www.famousdaves.com/Denver-Stapleton14:09
mlavalleThe food was good, very affordable and within walking distance of the hotel14:09
mlavallewhat do folks think?14:09
manjeets_+1 first time for me in denver14:10
slaweq+114:10
njohnstonSure, all the Famous Dave's restaurants around me closed about a year ago.  Good BBQ.14:10
*** yamamoto has quit IRC14:10
bcafarelI missed the first Denver train, so +1 (especially if good BBQ)14:10
slaweqI never had any Famous Dave's restaurant around me so it's good for me :D14:11
haleyb+1 from me, the food at the local brewery was only hit or miss at best14:11
mlavalleok, cool. Please go to the etherpad and add a yes (or no) to the line where your name is to indicate whether you are attending the dinner14:11
mlavalleI will sned a message to the ML anyways14:12
mlavalleany other announcements from the team?14:12
mlavalleok, let's move on....14:13
mlavalle#topic Blueprints14:13
*** openstack changes topic to "Blueprints (Meeting topic: networking)"14:13
mlavalleI have rolled over the blueprints of Rocky into the Stein-1 dashboard: https://launchpad.net/neutron/+milestone/stein-114:14
mlavalleand added some of the stuff that we have approved recently in the drivers meetings14:15
mlavallenjohnston: please note the addition to https://blueprints.launchpad.net/neutron/+spec/enginefacade-switch14:16
njohnstonYes, I was just reading that14:16
mlavalleso we can carry out the consolodation of this effort with https://blueprints.launchpad.net/neutron/+spec/adopt-oslo-versioned-objects-for-db14:16
*** ttsiouts has quit IRC14:16
njohnston+114:16
mlavallethis way the topic has visibility every week14:17
mlavalleI also added https://blueprints.launchpad.net/neutron/+spec/port-mirroring-sriov-vf14:17
*** ricolin has joined #openstack-meeting14:17
mlavalleThis is still in discussion, with a spec under review14:17
mlavalle#link https://review.openstack.org/#/c/574477/14:18
mlavallemuninsh will be at the PTG, so it will be a topic of discussion there14:18
mlavalleI invite the team to read the spec and get familiar with the topic14:18
njohnstonI would like to also note https://blueprints.launchpad.net/neutron/+spec/speed-up-neutron-bulk-creation which is also a discussion topic at the PTG, I hope we can add this as well14:19
* mlavalle will get back to bulk creation in a bit14:20
njohnstonThanks, sorry to jump the line mlavalle :-)14:20
*** boden has joined #openstack-meeting14:20
mlavallemunish needs help getting in shape the CI system of one of the networking sub-projects (I think it is tap as a service but not sure)14:21
mlavalleslaweq: maybe we give him some guidance14:21
*** armax has joined #openstack-meeting14:22
slaweqmlavalle: I can help, sure14:22
mlavallecool thanks14:22
mlavallenjohnston: yeeeees.... On Firday, when I was working on this, I knew I was forgetting something big. Yes, that has been agreed upon since Dublin14:23
mlavalleif more discussion is needed in Denver, that is perfectly fine14:23
mlavalleI just added it to the dashboard14:24
njohnstonthanks mlavalle!14:24
mlavallethanks for bringing it up :-)14:24
mlavalleanything else on blueprints14:25
mlavalle?14:25
mlavalleok, let's move on14:26
mlavalle#topic Community goals14:27
*** openstack changes topic to "Community goals (Meeting topic: networking)"14:27
*** dtrainor has quit IRC14:27
mlavalleLast week slaweq volunteered for the "Support Pre Upgrade Checks" community goal14:27
manjeets_I can help with ci too count me in14:27
mlavalleThanks you very much!!!!14:27
slaweqbut I didn't do anything with it yet :/14:28
mlavallethat's is fine,..... we are still officially in Rocky14:28
mlavalle;-)14:28
slaweq:)14:28
bcafarelslaweq: maybe start by adding a PTG topic? ;)14:28
bcafarelor is it coverd by the general neutron upgrades one14:28
slaweqbcafarel: yes, that's good idea14:29
slaweqI will add it there14:29
mlavalle++14:29
*** pcaruana has quit IRC14:29
mlavalleany updates on the Python-3 goal, njohnston?14:29
*** erlon has joined #openstack-meeting14:29
*** pcaruana has joined #openstack-meeting14:30
njohnstonNothing at the moment on the functional job, been pulled in other directions.  Did we get any guidance on the tempest jobs from the TC?  I don't recall if we had resolved that.14:30
mlavalleyeah, essentially the guidance is "let's convert everything to Python 3"14:31
mlavalleall the jobs14:31
manjeets_so py2 jobs will be dropped at some point ?14:31
mlavallewe should only have python 2.7 jobs for exeplicitely testing python 2.714:31
mlavallenjohnston: does that help?14:32
bodenI think py2 will be dropped at some point, but as I understand that'll be mostly dependant on when the linux distros drop support14:32
njohnstonok, so the option is that we can have a py27 and a py3 version of all the tempest jobs, or we can have either a py27 or a py3 version of each job and we transition from one to the other14:32
bcafarelor cut a list of "important" jobs to have both (ie make sure that py27 still works)14:33
njohnstonit sounds like they are OK with doubling the number of tempest jobs, so as long as that14:33
bcafarelguess pep8 etc only need py314:33
*** amotoki has joined #openstack-meeting14:33
mlavallenjohnston: no.... everything should be python 3, except where we are testing for python 2.7 explicitely14:33
njohnstonas long as that's not a zuulbreaker then I am good to get started on it14:33
slaweqsome of jobs, like scenario or others are not very stable and if we will run them all for both py27 and py3 I'm affraid we will be lost with rechecking :/14:33
slaweqand it will also consume a lot of infra resources14:33
*** Bhujay has joined #openstack-meeting14:33
njohnstonso which tempest jobs are important to keep in py27?  Just one py27 full run, or do we need the scenario tests too?14:34
mlavalleI'd say have one py27 run14:34
*** Bhujay has quit IRC14:34
mlavallelet's do only one14:35
bcafarelslaweq: do you think we should add a neutron specific CI topic at ptg? (to get a better passing rate)14:35
*** reedipb has joined #openstack-meeting14:35
*** Bhujay has joined #openstack-meeting14:35
bcafareland... we also can add a py3 topic14:35
mlavalleand maybe the py27 unit tests14:35
reedipbo/14:35
njohnstonok, I can start with bifurcating the tempest-full into py3 and py27 jobs, and then I'll work on converting all the others to py3, one at a time14:36
slaweqbcafarel: I think we can discuss on PTG about that what jobs should be run in both py27 and py3 and which only on py314:36
*** ttsiouts has joined #openstack-meeting14:36
*** amotoki has quit IRC14:36
*** dtrainor has joined #openstack-meeting14:37
*** eharney_ has joined #openstack-meeting14:37
*** eharney has quit IRC14:37
*** amotoki has joined #openstack-meeting14:37
mlavallethe general idea is that we need a minimum of py27, just to make sure we support it14:37
mlavallebut everything else should be py314:37
njohnstonactually never mind, the bifurcation is already done and tempest-full-py3 already exists.  so I'll get changes up for review to switch to py3 for the other jobs, but I'll -W them until after we discuss it at the PTG14:37
mlavallenjohnston: that is a good approach14:37
mlavallenjohnston: would you add the topic to the etherpad?14:38
njohnstonwill do14:38
bcafarelnjohnston: started it (point 14), feel free to expand14:38
amotokihi, I had trouble in connecting irc and reading the log today14:38
mlavalleok14:38
mlavalleok, let's move on14:39
mlavalle#topic Bugs14:39
*** openstack changes topic to "Bugs (Meeting topic: networking)"14:39
mlavallehongbin sent a comprehensive report here: http://lists.openstack.org/pipermail/openstack-dev/2018-August/133886.html14:40
hongbinhi14:40
hongbinyes, there are many reported bugs last week14:40
*** efried_doc is now known as efried14:41
hongbinone of them is critical, two of them are high14:41
mlavalleThe critical bug was alfeady fixed by slaweq, correct?14:41
hongbinmlavalle: it is assigned to you14:41
mlavallehongbin: yeah, but he took it off my hands ;-)14:42
hongbin#link https://bugs.launchpad.net/neutron/+bug/178818514:42
openstackLaunchpad bug 1788185 in neutron "[Stable/Queens] Functional tests neutron.tests.functional.agent.l3.test_ha_router failing 100% times " [Critical,Confirmed] - Assigned to Miguel Lavalle (minsel)14:42
hongbinmlavalle: ok14:42
slaweqmlavalle: but it was agreed with You :P14:42
hongbinmlavalle: if it is already fixed, please mark the bug as fixed14:42
*** yamamoto has joined #openstack-meeting14:42
mlavalleyeah, you did, slaweq, LOL14:42
mlavallehongbin: will do14:42
hongbinmlavalle: thanks14:42
bcafarelnot sure we got all the backports merged yet?14:42
slaweqhongbin: I will mark as fixed when patches will land14:43
slaweqnow they are in the gate still14:43
hongbinslaweq: ack14:43
mlavalleone the ofhigh priuorities: https://bugs.launchpad.net/neutron/+bug/1788006....14:43
openstackLaunchpad bug 1788006 in neutron "neutron_tempest_plugin DNS integration tests fail with "Server [UUID] failed to reach ACTIVE status and task state "None" within the required time ([INTEGER] s). Current status: BUILD. Current task state: spawning."" [High,Confirmed] - Assigned to Miguel Lavalle (minsel)14:43
mlavalleI worked on it over the weekend. It is really a NOva issue and I opened a correspondig bug on that side14:43
mlavalleI left comprenhensive notes in the bug14:44
njohnstonthanks very much for running that one down14:44
hongbin+114:45
*** yamamoto has quit IRC14:45
hongbinthere is another one, which i traiged it as "high"14:45
mlavalleI see that the RFEs are properly tagged, so we will catch them in the RFE / Neutron drivers process14:45
hongbin#link https://bugs.launchpad.net/neutron/+bug/178791914:45
openstackLaunchpad bug 1787919 in neutron "Upgrade router to L3 HA broke IPv6" [High,Confirmed]14:45
*** markvoelker has joined #openstack-meeting14:45
mlavallefor that one I added l3-dv-backlog tag. we will process it further on Thursday during the Le sub-team meeting14:46
hongbinmlavalle: great. thanks14:47
mlavalleL3 subteam^^^14:47
slaweqhongbin: I added comment there also14:47
slaweqit looks for me that You spotted different issue then described originally in bug report, can You check that?14:47
mlavalleok, this week's deputy is hichihara. I already contacted him over email and he is working on it14:48
mlavallelet's move on14:48
*** alexchadin has quit IRC14:48
mlavalle#topic neutron-lib14:48
*** openstack changes topic to "neutron-lib (Meeting topic: networking)"14:48
mlavalleboden: any updates here?14:48
bodenhi14:48
*** dangtrinhnt_x has joined #openstack-meeting14:48
bodennothing exciting, just back to business as usual.. we've landed a number of neutron-lib patches and there's some consumption patches out there for review in neutron and others14:49
mlavalleI am keeping an eye on both14:49
*** markvoelker has quit IRC14:49
bodenthat's really all I have to report at this time unless there's comments/questions14:49
mlavallenot from me14:49
*** alexchadin has joined #openstack-meeting14:49
mlavalleok, moving on14:49
mlavalle#topic Ryu14:50
*** openstack changes topic to "Ryu (Meeting topic: networking)"14:50
mlavallehongbin: you are up again....14:50
hongbinhi14:50
* hongbin is checking the ryu patches14:50
hongbin#link https://review.openstack.org/#/c/588358/14:50
hongbinabove is the proposed patch and it looks very closed to merge14:50
mlavalleGreat!14:51
hongbinactually, checking the last comment, they said the patch was approved14:52
mlavalleeven better14:52
mlavallethat's from the governance point of view14:52
hongbinyes14:52
mlavalleyou have one for the repo, right?14:52
hongbin#link https://review.openstack.org/#/c/588355/14:52
hongbinthis is the one to create the repo14:53
hongbinand it got one +2 already14:53
hongbini think we will get that one approved soon, we are able to proceed14:53
mlavalleGreat progress hongbin.... do you think the next step is to discuss in the PTG how to start importing from the new repo and giving maintenance to it?14:54
amotokiI failed to follow this discussion, but naming ken is from the street fighter as the rival of ryu?14:54
mlavalleamotoki: exactly14:54
hongbinmlavalle: sure, that would be a good idea14:54
njohnstonamotoki: ryu's best friend14:54
amotokinjohnston: nice point14:54
mlavalleok, let's move on14:55
mlavalle#topic CLI / SDK14:55
*** openstack changes topic to "CLI / SDK (Meeting topic: networking)"14:55
mlavalleamotoki: any updates here:14:55
mlavalle?14:55
amotokiI plan to release neutornclient next week14:55
amotokito include the gate fix14:55
mlavallecool14:55
*** e0ne has quit IRC14:56
amotokiit will happen in both stein and rocky branch.14:56
amotokiapart from that, fwaas support in openstacksdk is proposed.14:56
amotokiI will follow up and resume the SDK migration till PTG.14:57
mlavallenice!14:57
amotokithat's all from me this week.14:57
mlavallethanks14:57
mlavalle#topic Open Agenda14:57
*** openstack changes topic to "Open Agenda (Meeting topic: networking)"14:57
mlavalleSomobody pinged yesterday about a joint session Cyborg / Neutron during the PTG14:57
slaweqI would like to ask for anoter round of reviews of https://review.openstack.org/#/c/594326/14:58
mlavalleis that person around?14:58
mlavalleslaweq: I will look at it again14:58
slaweqI would like to run it when it will be merged :)14:58
slaweqmlavalle: thx a lot14:58
*** Bhujay has quit IRC14:58
mlavalleok14:59
mlavallethe other topic I wanted to mention is https://review.openstack.org/#/q/project:openstack/neutron+branch:feature/graphql14:59
mlavalleThis is a pilot to implement some of the Neutron API in GraphQL: https://graphql.org/14:59
*** pcaruana has quit IRC15:00
mlavalleI encourgae the team to take a look and help with reviews if you can15:00
mlavalle#endmeeting15:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"15:00
openstackMeeting ended Tue Aug 28 15:00:18 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking/2018/networking.2018-08-28-14.00.html15:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking/2018/networking.2018-08-28-14.00.txt15:00
amotokiI also would like to raise a topic around patrol project next week15:00
openstackLog:            http://eavesdrop.openstack.org/meetings/networking/2018/networking.2018-08-28-14.00.log.html15:00
mlavalleamotoki: ok, let's add it to the agenda15:00
amotokiyeah15:00
*** boden has left #openstack-meeting15:00
*** hongbin has quit IRC15:00
slaweq#startmeeting neutron_qos15:01
openstackMeeting started Tue Aug 28 15:01:07 2018 UTC and is due to finish in 60 minutes.  The chair is slaweq. Information about MeetBot at http://wiki.debian.org/MeetBot.15:01
mlavalleslaweq: the room is all yours...15:01
slaweqhi15:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:01
*** openstack changes topic to " (Meeting topic: neutron_qos)"15:01
openstackThe meeting name has been set to 'neutron_qos'15:01
slaweqmlavalle: thx :)15:01
rubasovhi again15:01
reedipbo/15:01
slaweq#topic RFEs15:01
*** openstack changes topic to "RFEs (Meeting topic: neutron_qos)"15:01
mlavallefwiw.... I didn't want to trigger the fury of the Hulk15:01
*** shintaro has quit IRC15:01
slaweqLOL15:01
slaweqYou will not trigger it for sure :)15:02
slaweqlet's talk about RFEs which are in progress somehow and about new ones later15:02
mlavalleLOL15:02
mlavallelet's do that15:02
slaweq#link https://bugs.launchpad.net/neutron/+bug/175704415:02
openstackLaunchpad bug 1757044 in neutron "[RFE] neutron L3 router gateway IP QoS" [Wishlist,In progress] - Assigned to LIU Yulong (dragon889)15:02
*** manjeets_ has quit IRC15:03
slaweqWe have now API def patch merged now: https://review.openstack.org/#/c/567497/15:03
*** dtrainor_ has joined #openstack-meeting15:03
*** dtrainor has quit IRC15:03
njohnstono/15:03
mlavalleyes, I pushed it a few days ago15:03
slaweqthere is no other patches in progress currently but I hope it will be going forward as it's approved by drivers now15:04
*** ttsiouts has quit IRC15:04
mlavalleahhh15:04
mlavallehang on15:04
slaweqyes?15:04
mlavallelet me find the patches15:05
mlavallehttps://review.openstack.org/#/q/topic:bp/router-gateway-ip-qos,n,z15:05
*** jroll has quit IRC15:05
mlavalleThere are server and agent side patches15:06
*** jroll has joined #openstack-meeting15:06
slaweqahh, so there are patches already but with different topic15:06
slaweqthx mlavalle15:06
slaweqI will review them this week15:06
mlavalleyeah, what happened is that I created the topic after I pushed the APi definition15:06
mlavalleand also created the blueprint, so we can track it in our weekly meeting15:07
mlavallehttps://blueprints.launchpad.net/neutron/+spec/router-gateway-ip-qos15:07
mlavalleslaweq: do you want to be the approver?15:07
slaweqI can15:07
mlavalledone15:07
slaweqthx15:08
slaweqok, next RFE is #link https://bugs.launchpad.net/neutron/+bug/157898915:08
openstackLaunchpad bug 1578989 in neutron "[RFE] Strict minimum bandwidth support (egress)" [Wishlist,In progress] - Assigned to Lajos Katona (lajos-katona)15:08
liuyulongHi, the neutron patches now need a new neutron-lib release for the testing since I updated the extension to the merged patch here: https://review.openstack.org/#/c/567497/15:08
slaweqrubasov: any updates?15:08
rubasovslaweq: yes15:08
slaweqI know that patches are going forward :)15:08
mlavalleliuyulong: ack, I will discuss with boden15:08
rubasovwe have landed many neutron-lib patches15:09
rubasovthanks a lot for everyone helping15:09
liuyulongthanks, and sorry for the interrupt15:09
rubasovmany of the open neutron changes are actually ready for review, the zuul-1 is only because of the neutron-lib changes not being released yet15:10
slaweqmlavalle: will it be possible to release new neutron-lib soon then?15:10
mlavallerubasov: I will include the neutron-lib patches in my conversation with boden about releasing neutron-lib again15:11
mlavalleslaweq: yeap15:11
slaweqmlavalle: thx15:11
mlavallewe clearly need it15:11
mlavalleprobably next week15:11
rubasovthat would be cool15:11
rubasovthank you15:11
mlavalleonce we get rocky completely out of the door15:11
mlavallethat way we know we can break things without too much impact15:12
slaweqyes, that was what I though :)15:12
liuyulongcool15:12
rubasovthis week I was putting together a new end-to-end integration of the whole feature (including the open nova and placement changes)15:12
slaweqI think that rocky is already bound to some released version of neutron-lib so new version shouldn't break it, right?15:12
rubasovI hope to show that to you on the ptg15:12
slaweqrubasov: sounds good15:13
mlavalleslaweq: right. let's see how boden feels about it15:13
slaweqmlavalle: ok, thx :)15:13
mlavallebecause neutron-lib impacts a number of projects15:13
rubasovlajoskatona couldn't be here today, but I know he is working on tests for neutron-tempest-plugin15:13
rubasovI am working on pushing a new version of the placement sync service plugin with a plan of how to handle transient placement api errors15:14
rubasovthat's the current status I think15:15
*** yamamoto has joined #openstack-meeting15:15
slaweqok, thx for update rubasov :)15:15
mlavallerubasov: great progress!, Thanks for your hardwork...15:15
mlavalleand lajoskatona's as well15:16
slaweq+115:16
rubasovI'll forward it to lajoskatona15:16
mlavallelet's not forget gibi ;-)15:16
slaweqright15:17
mlavalleour infiltrated man in the Nova team ;-)15:17
slaweqLOL15:17
rubasovand in the Placement team :-D15:17
slaweqok, let's move forward to next RFEs now :)15:19
slaweqwe have 2 new RFEs reported recently15:19
slaweqfirst one is:15:19
slaweqhttps://bugs.launchpad.net/neutron/+bug/178779215:19
openstackLaunchpad bug 1787792 in neutron "[RFE] Does not support ipv6 N-S qos" [Wishlist,New]15:19
mlavalleThis one actually came from my trip to China15:20
slaweqIMO it may be achieved by implementing classful bandwidth limit, e.g. using Common Classifier Framework15:20
slaweqmlavalle: You bring it from China? :)15:21
reedipblol15:21
mlavalleI asked Na Zhu to file the RFE15:21
mlavalleand we are ready to decidcate a resource to it15:21
slaweqthat sounds good :)15:21
mlavalleit could be me15:21
slaweqI'm perfectly fine to improve our qos rules for such things15:22
slaweqbut I think that it can be something more than only support for IPv615:22
slaweqif You e.g. use CCF then it may be classified by different things also15:22
mlavallewell, if you give me some guidance, I am willing to pursue it15:23
slaweqmlavalle: I don't know this CCF too much, I just know there is (was) something like that15:24
mlavalleslaweq: ok, we can investigate15:24
slaweqaccording to backend implementation, I can help for sure15:24
slaweqmlavalle: sounds good15:25
mlavalleand we can elaborate in the PTG15:25
slaweqyes15:25
slaweqI will try to read a bit more about this classifier framework and check if we can use it here15:26
mlavalleok15:26
njohnstonIf you can find davidsha, he is a good resource on it15:26
*** dtrainor_ has quit IRC15:26
mlavalleahhh, ok, I'll ping him15:27
*** gyee has joined #openstack-meeting15:27
slaweqnjohnston: thx15:27
*** dtrainor_ has joined #openstack-meeting15:27
slaweqok, moving on15:28
slaweqwe have also one more new RFE15:28
slaweqhttps://bugs.launchpad.net/neutron/+bug/178779315:28
openstackLaunchpad bug 1787793 in neutron "[RFE] Does not support shared N-S qos per-tenant" [Wishlist,New]15:28
mlavalleThis is a similar case as the previous one15:29
mlavalleI asked Na Zhu to file the RFE15:29
slaweqIIUC this one, it's about making shared bandwidth limit for tenant's ports/floating IPs, right?15:29
mlavalleyes15:29
mlavalleI wanted first to see what slaweq and liuyulong think about it15:30
mlavallewhether it is doable or not?15:30
slaweqidea is fine, but I don't know how we could realize it15:30
*** hongbin has joined #openstack-meeting15:30
slaweqI'm not sure how it should work on API level15:31
liuyulongI'm not very sure about the TC ipv6 status, does it supporting now?15:31
slaweqliuyulong: I don't know, it should be checked15:31
*** janki has quit IRC15:32
mlavalleso if you tell me where to go and chack, I can take that as homework15:32
*** david-lyle has quit IRC15:33
slaweqare You asking about IPv6 in tc?15:33
*** dklyle has joined #openstack-meeting15:34
mlavalleyeah15:34
mlavallebut that's ok, I can search for that information15:34
slaweqI don't know exactly tbh, I need to search simply :)15:35
mlavalleok15:35
slaweqok, getting back to this QoS per tenant15:36
slaweqdo You have any idea how You would see it?15:37
mlavalleNo, I wanted to get ideas from you and liuyulong15:37
slaweqmy first idea was to use Quota and treat bandwidth as any other resource15:38
slaweqbut I don't know if that will work fine15:38
slaweqand probably there will be some problems with that15:38
mlavalleso, this is not something that we can enforce at the dataplane, right?15:38
slaweqI don't know15:39
slaweqhow You want to enforce it at dataplane only?15:39
mlavalleany thoughts liuyulong?15:39
liuyulongIMO, dvr will block the dataplane bandwidth share.15:39
liuyulongbut bandwidth quota can be introduced to the neutron.15:40
*** jhesketh has quit IRC15:41
mlavalleso let me ask you a question15:41
*** jhesketh has joined #openstack-meeting15:41
mlavallelet's forget about DVR15:41
mlavallelet's say the fips are centralized15:41
mlavallein the same network server15:41
mlavallecan we set up something in TC whereby two or more floating IPs can share a bandwidth limit?15:42
liuyulongYes, in such centralized router, it can.15:43
liuyulongThe tc classifier rules can do such work.15:44
mlavallelet's start from there. could you post the tc commands that would do that in the RFE?15:44
slaweqok, but how as an operator I should tell neutron that this limit should be shared between FIPs?15:45
mlavallein my mind that is something that we can fix in the API15:45
mlavalleI suggested in the RFE adding an attibute to the policy resource15:46
slaweqmlavalle: ok15:46
slaweqthen we can definitely start with something supported only by L3HA and not supported in DVR15:46
mlavalleindicating that that policy is meant to share limits at the tenant level15:46
liuyulongI don't have it right now, let me google one.15:46
mlavalleliuyulong: didn't mean right now15:46
mlavallelet's start brainstorming in the RFE as to what the TC commands would be15:47
slaweqmlavalle: sounds good to me15:47
liuyulongOK, I will paste it to the RFE LP bug.15:47
slaweqand thx liuyulong for working on this15:47
mlavalleslaweq, liuyulong: thanks you very much!!!! I think we made progress on this15:47
mlavalleand liuyulong thanks for responding so quickly to my mail message. Much appreciated15:48
liuyulongI think Zhaobo's VPN qos patch has something helpful.15:48
liuyulonghttps://review.openstack.org/#/c/558986/15:48
mlavalleon top of that you are attending this meeting at midnight your time ;-)15:48
liuyulongHe already has a new tc-wrapper for the classifier tc rules.15:49
*** annp_ has quit IRC15:49
mlavalleliuyulong: ok, I'll take a look15:50
*** cloudrancher has joined #openstack-meeting15:50
slaweqthx liuyulong for info :)15:50
slaweqok, are there any other questions related to RFEs?15:51
mlavallenot from me15:51
slaweqor can we move forward to bugs now?15:52
mlavallelet's move on15:52
slaweq#topic Bugs15:52
*** openstack changes topic to "Bugs (Meeting topic: neutron_qos)"15:52
slaweq#link https://bugs.launchpad.net/neutron/+bug/178355915:52
openstackLaunchpad bug 1783559 in neutron "Qos binding network causes ovs-agent to send a lot of rpc" [Medium,In progress] - Assigned to s10 (vlad-esten)15:52
slaweqPatch https://review.openstack.org/#/c/585752/ - IMO it's good to go but someone needs to check it as well15:52
slaweqmlavalle: please add it to Your queue :)15:52
mlavalledone15:52
slaweqthx15:53
slaweqnext one is:15:53
slaweq#link https://bugs.launchpad.net/neutron/+bug/178400615:53
openstackLaunchpad bug 1784006 in neutron "Instances miss neutron QoS on their ports after unrescue and soft reboot" [Medium,Confirmed] - Assigned to Miguel Lavalle (minsel)15:53
slaweqany updates mlavalle on this one?15:53
mlavallesorry, this one slipped from my todo list15:53
*** radeks_ has quit IRC15:53
mlavalleI'll work on it this week15:53
slaweqok, no problem at all :)15:54
slaweqnext one on the list:15:54
slaweq#link https://bugs.launchpad.net/neutron/+bug/177866615:54
openstackLaunchpad bug 1778666 in python-openstackclient "QoS - “port” parameter is required in CLI in order to set/unset QoS policy to floating IP" [Low,Confirmed] - Assigned to Lajos Katona (lajos-katona)15:54
slaweqlajoskatona pushed cherry-pick: https://review.openstack.org/#/c/594244/15:54
slaweqso it's almost fixed now15:54
slaweqnext:15:55
slaweq#link https://bugs.launchpad.net/neutron/+bug/177874015:55
openstackLaunchpad bug 1778740 in neutron "Quality of Service (QoS) in Neutron - associating QoS policy to Floating IP" [Low,In progress] - Assigned to Slawek Kaplonski (slaweq)15:55
slaweqPatch is ready for review: https://review.openstack.org/591619 - I need to address comments in it15:55
mlavalleok15:55
slaweqI will do it this week15:55
slaweqsame for:15:55
slaweq#link https://bugs.launchpad.net/neutron/+bug/177786615:55
openstackLaunchpad bug 1777866 in neutron "QoS CLI – Warning in case when provided burst is lower than 80% BW" [Wishlist,New]15:55
slaweqpatch for docs: https://review.openstack.org/591623 - I will have to address comments there15:56
slaweqand lajoskatona did patch with updated help message in OSC: https://review.openstack.org/#/c/588168/15:56
slaweqlast one on the list:15:57
slaweq#link https://bugs.launchpad.net/neutron/+bug/177905215:57
openstackLaunchpad bug 1779052 in neutron "Quality of Service (QoS) in Neutron (documentation) - only different types rules can be combined in QoS policy" [Low,In progress] - Assigned to yanpuqing (ycx)15:57
slaweqpatch if waiting: https://review.openstack.org/581941 - also some comments waiting to be addressed there15:57
slaweqand that's all from my about bugs15:57
slaweqany questions/something to add?15:57
mlavallenot from me?15:58
slaweqmlavalle: are You asking me? :D15:58
mlavalleno15:58
slaweqLOL15:58
mlavallethe question mark shouldn't be there15:58
mlavalleLOL15:58
slaweqok, let's finish meeting then15:59
slaweqthx for attending guys15:59
slaweqahh, one more thing15:59
mlavalleo/15:59
slaweqnext meeting will be cancelled as it's during PTG15:59
mlavalleyeap15:59
slaweqI will send an email about that15:59
slaweq#endmeeting15:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"15:59
openstackMeeting ended Tue Aug 28 15:59:31 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_qos/2018/neutron_qos.2018-08-28-15.01.html15:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_qos/2018/neutron_qos.2018-08-28-15.01.txt15:59
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_qos/2018/neutron_qos.2018-08-28-15.01.log.html15:59
slaweqo/15:59
mlavalleo/15:59
manjeetso/16:00
liuyulongBye, good night guys.16:00
rubasovbye16:00
*** liuyulong is now known as liuyulong_zzz16:00
slaweq#startmeeting neutron_ci16:00
openstackMeeting started Tue Aug 28 16:00:34 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
mlavalleliuyulong: thanks for attending. Have a great night!16:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
*** openstack changes topic to " (Meeting topic: neutron_ci)"16:00
slaweqhello again :)16:00
njohnstono/16:00
openstackThe meeting name has been set to 'neutron_ci'16:00
mlavalleo/16:00
mlavallelast leg of "Meetings Tuesday"16:00
manjeetsprior o/ was for CI .. lol16:01
slaweq:)16:01
slaweqshort info16:01
haleybhi16:01
slaweqI need to finish this meeting in 45 minutes16:01
slaweqso mlavalle You will continue it after that or we will finish 15 minutes earlier today16:02
slaweqok for You?16:02
mlavallelet's finish 15 min earlier16:02
slaweqfine :)16:02
slaweq#topic Actions from previous meetings16:02
*** openstack changes topic to "Actions from previous meetings (Meeting topic: neutron_ci)"16:02
slaweq* njohnston to tweak stable branches dashboards16:02
njohnstonhttps://review.openstack.org/#/c/597168/16:02
*** Emine has quit IRC16:02
njohnstonthis brings the stable dashboards in line with your reformat of the main one16:03
njohnstonbut with jobs dropped if they don't exist for the stable rbanches, like all the scenario jobs16:03
slaweqnjohnston: thx, I will review it soon16:03
*** alexchadin has quit IRC16:03
njohnstonand I bump the versions, so old dashboard == stable/rocky and older == stable/queens now16:03
*** macza has joined #openstack-meeting16:03
*** raildo has quit IRC16:03
slaweqthat's good :)16:04
slaweqthx njohnston16:04
*** eharney_ is now known as eharney16:04
slaweqok, next one was:16:04
slaweq* slaweq to update grafana dashboard to ((FAILURE + TIME_OUT) / (FAILURE + TIME_OUT + SUCCESS))16:04
slaweqPatch: https://review.openstack.org/59576316:04
njohnstonthere were 9 jobs I excluded from the file because Graphite has no record of them for stable branches.  Not sure if that is interesting info, but I have the list if you like16:04
slaweqsure, we can check this list together16:05
njohnstonI put the list in acomment on https://review.openstack.org/#/c/59716816:06
*** e0ne has joined #openstack-meeting16:06
slaweqok, thx16:07
slaweqI will check it also16:07
slaweqthx for working on this njohnston16:07
njohnstonnp16:07
slaweqso getting back to next action, which was:* slaweq to update grafana dashboard to ((FAILURE + TIME_OUT) / (FAILURE + TIME_OUT + SUCCESS))16:08
slaweqI sent patch, frickler found one issue there so I need to fix it16:08
slaweqmoving on to next action16:08
*** liuyulong_zzz has quit IRC16:08
slaweq* mlavalle to check neutron_tempest_plugin.scenario.test_dns_integration.DNSIntegrationTests.test_server_with_fip issue16:08
mlavalleI did16:09
mlavalleI found that the Nova API never reports that the instance got ip addresses in port16:09
mlavalleNeutron communicates the vif plugged in event correctly to compute16:10
*** mjturek has quit IRC16:10
slaweqbut I wonder why it happens so often in this job recently and not in another16:10
slaweqor maybe You spotted it in different jobs also?16:10
mlavalleno16:10
mlavallethat is agood question16:10
mlavalleI will take a look again with other case16:10
mlavalleI left a good kibana query in the bug16:11
mlavalleso it is easy to find other cases16:11
slaweqI remember from my previous company that we had such issues somewhere around Juno IIRC16:11
slaweqand we even patched nova-compute to check status of port directly in neutron before set instance in ERROR16:11
slaweqbut later I never saw it in newer versions16:12
slaweqmaybe in this scenario there is different rabbitmq used or something like that16:12
mlavalleI'll check another case16:12
slaweqmlavalle: ok, thx16:12
slaweq#action mlavalle to check another cases of failing neutron_tempest_plugin.scenario.test_dns_integration.DNSIntegrationTests.test_server_with_fip test16:13
*** raildo has joined #openstack-meeting16:13
slaweqok, that's all for actions from previous week16:13
slaweq#topic Grafana16:14
*** openstack changes topic to "Grafana (Meeting topic: neutron_ci)"16:14
slaweqhttp://grafana.openstack.org/dashboard/db/neutron-failure-rate16:14
slaweqdo You see anything You want to talk at first?16:15
*** raildo has quit IRC16:15
mlavalleI'll follow your lead16:15
slaweqthere is again problem with Neutron-tempest-plugin-dvr-multinode-scenario16:16
*** raildo has joined #openstack-meeting16:16
slaweqit's 100% failing since few days16:16
slaweqI found that it's always issue with neutron_tempest_plugin.scenario.test_migration.NetworkMigrationFromHA16:16
slaweqlike:         * http://logs.openstack.org/37/382037/71/check/neutron-tempest-plugin-dvr-multinode-scenario/605ed17/logs/testr_results.html.gz16:16
slaweqI reported bug for that https://bugs.launchpad.net/neutron/+bug/1789434 today16:16
openstackLaunchpad bug 1789434 in neutron "neutron_tempest_plugin.scenario.test_migration.NetworkMigrationFromHA failing 100% times" [High,Confirmed]16:17
*** Bhujay has joined #openstack-meeting16:17
slaweqit looks like related somehow to my patch: https://review.openstack.org/#/c/589410/16:17
slaweqbut this test was fine on this patch, so something happend later probably that it's failing now16:17
slaweqany volunteer to check that?16:18
mlavalleo/16:18
slaweqthx mlavalle :)16:19
haleyb<5 seconds to volunteer :)16:19
mlavallehaleyb: do you want it?16:19
slaweq#action mlavalle to check failing router migration from DVR tests16:19
slaweqshould I assign it to haleyb?16:20
mlavallenot unless he explictely wants it16:20
mlavalleotherwise, I take it16:20
haleybmlavalle: no, feel free16:20
mlavallehaleyb: ack16:20
slaweqok, so we have the winner :)16:20
slaweqthx mlavalle16:20
mlavalleyaaay!!!!16:20
mlavalleI wan!!!!16:21
slaweqLOl16:21
slaweqok, so let's continue about scenario jobs then16:21
slaweqother scenario job which is failing quite often is this designate job which we already talk about16:22
slaweqand I also found couple of times timeouts in neutron-tempest-plugin-scenario-linuxbridge16:22
slaweq    * http://logs.openstack.org/59/596959/1/check/neutron-tempest-plugin-scenario-linuxbridge/f62f1c6/job-output.txt.gz16:22
slaweq    * http://logs.openstack.org/18/591818/3/check/neutron-tempest-plugin-scenario-linuxbridge/212183e/job-output.txt.gz16:22
slaweq    * http://logs.openstack.org/34/596634/1/check/neutron-tempest-plugin-scenario-linuxbridge/098b6f3/job-output.txt.gz16:22
*** Bhujay has quit IRC16:22
*** raildo has quit IRC16:23
*** raildo has joined #openstack-meeting16:23
*** dangtrinhnt_x has quit IRC16:23
slaweqthere is virt_type=kvm set but it shouldn't be problem if it's supported by host16:26
*** mjturek has joined #openstack-meeting16:26
slaweqis there any voluneer to check why there there are such timeouts?16:26
slaweqif no, I will report it as a bug and take a look when I will have some time16:27
slaweqbut currently I'm quite overloaded :/16:27
mlavalleI am also a bit overloaded16:28
mlavalleif nobody else steps up and you are patient with me, then sign me up16:29
slaweqmlavalle: thx16:29
mlavalleI might not get to it until next week16:29
slaweqI will report it as a bug for now and we will see who will have some cycles to check that16:29
slaweqfine for You?16:29
*** dustins has quit IRC16:29
haleybyes, report as bug and i can look at logs at least16:30
slaweq#action slaweq to report a bug about timouts in neutron-tempest-plugin-scenario-linuxbridge16:30
slaweqhaleyb: thx16:30
*** Bhujay has joined #openstack-meeting16:30
slaweqI will send link to bug report when I will report it16:30
haleybor just recheck, recheck, recheck...16:30
*** macza_ has joined #openstack-meeting16:30
slaweqyes, for now it's kind of workaround but... :)16:30
mlavallesounds good slaweq16:31
slaweqthx guys16:31
slaweqok16:31
slaweqfrom scenario jobs it were most often failures which I found last week16:31
slaweqso let's move on16:31
slaweq#topic functional16:31
*** openstack changes topic to "functional (Meeting topic: neutron_ci)"16:32
slaweqFYI: We have fixes almost merged for failing functional tests in stable branches, bug: https://bugs.launchpad.net/neutron/+bug/178818516:32
openstackLaunchpad bug 1788185 in neutron "[Stable/Queens] Functional tests neutron.tests.functional.agent.l3.test_ha_router failing 100% times " [Critical,Confirmed] - Assigned to Miguel Lavalle (minsel)16:32
slaweqbasically this issue is caused by keepalived in version which is now in Xenial repo16:32
slaweqI was talking today with frickler and coreycb about it16:33
slaweqI will try to prepare some small reproducer and add it to keepalived bug report16:33
slaweqbut we should be good using older version of keepalived for now16:34
*** macza has quit IRC16:34
mlavalleok16:34
mlavallewe merged the patches yesterday, right?16:34
slaweqfor Queens it's merged16:34
slaweqfor Pike and Ocata I have to recheck it16:34
mlavalleok16:35
slaweqother issue with functional tests is, that we Still from time to time we hit: https://bugs.launchpad.net/neutron/+bug/178483616:35
openstackLaunchpad bug 1784836 in neutron "Functional tests from neutron.tests.functional.db.migrations fails randomly" [Medium,Confirmed]16:35
slaweqe.g. in http://logs.openstack.org/18/591818/3/check/neutron-functional/ddb3327/logs/testr_results.html.gz16:35
slaweqit's not very often but maybe someone with good db experience could take a look at it16:36
slaweqmlavalle:  do You know who we can potentially ask for look at this one?16:37
mlavalleI would ask Mike Bayer16:37
slaweqthx mlavalle16:37
slaweq#action mlavalle to ask Mike Bayer about functional db migration tests failures16:37
slaweqanything else to add related to functional tests?16:38
mlavallenot from me16:38
*** njohnston_ has joined #openstack-meeting16:38
slaweqok, so let's move to next topic then16:39
slaweq#topic Fullstack16:39
*** openstack changes topic to "Fullstack (Meeting topic: neutron_ci)"16:39
*** njohnston has quit IRC16:39
*** njohnston_ is now known as njohnston16:39
slaweqspeaking about fullstack, I have only one thing16:39
slaweqwe still have quite lot of failure but all (or almost) are caused by this  https://bugs.launchpad.net/neutron/+bug/1779328 and I still don’t know why it happens16:39
openstackLaunchpad bug 1779328 in neutron "Fullstack tests neutron.tests.fullstack.test_securitygroup.TestSecurityGroupsSameNetwork fails" [High,In progress] - Assigned to Slawek Kaplonski (slaweq)16:39
slaweqmaybe we should mark this test as unstable again to make our life easier?16:39
slaweqwhat You think about it?16:40
mlavalleyesh, let's do it16:40
slaweqok, I will do it then16:40
njohnstondo we have a rule in elastic-recheck for that failure?16:40
slaweq#action slaweq to mark fullstack security group test as unstable again16:41
slaweqnjohnston: I don't think so16:41
*** sambetts is now known as sambetts|afk16:41
slaweqnjohnston: do You think we should add it there also?16:42
slaweqif we mark it as unstable, it will be skipped simply instead of failing16:42
mlavalleyeah16:42
njohnstonI never think it's a bad idea to look at elastic-recheck rules, but then again it is hard to find cores to +2 them these days :-)16:43
*** Bhujay has quit IRC16:43
slaweqyeah, so maybe let's just mark it in our repo as unstable for now16:44
*** Bhujay has joined #openstack-meeting16:44
slaweqok, that was all what I had for today16:44
slaweqand I need to end this meeting right now :)16:44
slaweqperfect timing16:44
mlavalleThanks!16:44
slaweqthx guys for attending16:44
njohnstonthanks!16:44
slaweqand see You next week16:44
mlavalleo/16:44
slaweq#endmeeting16:44
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"16:44
openstackMeeting ended Tue Aug 28 16:44:51 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:44
manjeetsthanks16:44
slaweqo/16:44
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_ci/2018/neutron_ci.2018-08-28-16.00.html16:44
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_ci/2018/neutron_ci.2018-08-28-16.00.txt16:44
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_ci/2018/neutron_ci.2018-08-28-16.00.log.html16:44
*** mlavalle has left #openstack-meeting16:45
*** aojea has quit IRC16:45
*** amotoki has quit IRC17:04
*** amotoki has joined #openstack-meeting17:05
*** yamahata has quit IRC17:08
*** r-mibu has quit IRC17:12
*** amotoki has quit IRC17:15
*** dustins has joined #openstack-meeting17:17
*** dustins_ has joined #openstack-meeting17:21
*** dustins has quit IRC17:22
*** reedipb has quit IRC17:23
*** Bhujay has quit IRC17:24
*** dustins_ has quit IRC17:25
*** apetrich has quit IRC17:32
*** dustins has joined #openstack-meeting17:34
*** raildo has quit IRC17:35
*** kopecmartin has quit IRC17:37
*** raildo has joined #openstack-meeting17:38
*** yamahata has joined #openstack-meeting17:42
*** raildo_ has joined #openstack-meeting17:42
*** raildo has quit IRC17:45
*** raildo_ is now known as raildo17:46
*** ricolin has quit IRC17:50
*** markvoelker has joined #openstack-meeting17:51
*** electrofelix has quit IRC18:23
*** mjturek has quit IRC18:24
*** markvoelker has quit IRC18:32
*** markvoelker has joined #openstack-meeting18:33
*** markvoelker has quit IRC18:37
*** mjturek has joined #openstack-meeting18:44
*** pabelanger has joined #openstack-meeting18:49
*** AJaeger has joined #openstack-meeting18:51
*** mjturek has quit IRC18:52
*** Shrews has joined #openstack-meeting18:52
clarkbHello anyone here for the infra meeting19:00
ianwo.19:00
ianwo/19:00
diablo_rojoo/19:00
*** mjturek has joined #openstack-meeting19:00
AJaegero/19:00
fungiohai19:00
clarkb#startmeeting infra19:01
openstackMeeting started Tue Aug 28 19:01:02 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
*** openstack changes topic to " (Meeting topic: infra)"19:01
openstackThe meeting name has been set to 'infra'19:01
clarkb#link https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting#Agenda_for_next_meeting19:01
clarkb#topic Announcements19:01
*** openstack changes topic to "Announcements (Meeting topic: infra)"19:01
clarkbThe OpenStack Rocky release happens on Thursday19:01
clarkbat least this is what I have been told19:01
Shrewso/19:01
clarkbfungi should have a new gpg key for that pushed out shortly so be on the lookout for that and be ready to sign it if you can19:02
fungiyes, it's generated19:02
fungi0xD943D5D270273ADA is the master key id19:02
fungihaven't pushed it up to the keyserver network yet nor added the symmetric decryption passphrase for it to the secrets list19:03
fungithere are some nuanced differences in the behavior, configuration and options for the gnupg version in bionic, so with the move to bridge.o.o i have some notes i'll work into a process documentation update19:04
clarkbthat seems like a fairly common activity around this transition19:04
fungiyup19:04
fungialso worth noting, the validity period is set to 10 months19:04
clarkbbecause we expect the next cycle to be longer?19:04
fungibecause the stein cycle is a tall one19:04
fungier, long one19:04
fungilong pour?19:04
fungianyway, yes19:04
fungirelease is scheduled for april19: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-08-21-19.02.txt Minutes from last meeting19:06
clarkbfungi: thank you for running that last week19:06
funginp19:06
clarkbI don't see any explicit actions but appears that we did a lot of talking around testing of the ansible work19:06
clarkbI've been reviewing changes that add said testing today so thank you for getting that in19:06
clarkbwhich is probably a good lead into our config management update priority effort19:07
clarkb#topic Priority Efforts19:07
*** openstack changes topic to "Priority Efforts (Meeting topic: infra)"19:07
clarkb#topic Update Config Management19:07
*** openstack changes topic to "Update Config Management (Meeting topic: infra)"19:07
clarkbI'm still sort of catching up on the changes that have happened around this from last week. I've jumped onto getting launch node to work again though19:08
*** cloudrancher has quit IRC19:08
*** annabelleB has joined #openstack-meeting19:08
*** e0ne has quit IRC19:08
corvusclarkb: i think your email basically laid out our next work items :)19:08
corvusclouds.yaml, cloud launcher,  etc19:08
fungiit was nice and detailed19:08
clarkb#link https://review.openstack.org/#/c/596873/ and its parent will get launch node minimally working again19:09
clarkbthat change has reviews but its parent needs them too19:09
*** cloudrancher has joined #openstack-meeting19:09
clarkb#link http://lists.openstack.org/pipermail/openstack-infra/2018-August/006108.html Thread on getting launch node working19:10
corvuschange https://review.openstack.org/596849 from Shrews is the last base role we identified last week.  i just +3d it19:10
clarkbthe major outstanding item now is getting puppet installed so that puppet can run on new nodes that are still puppeted19:10
clarkbianw: ^ has been working on that and I think after a rebase and squash with some minor test changes we should be ready to get that in?19:10
ianwone comment from corvus on the integration roles but we can follow up outside meeting i think19:11
clarkb#link https://review.openstack.org/#/c/596913/ is another important change that will allow ansible to work on xenial as we transition off trusty19:11
clarkbI maybe need ot update the topic on these changes19:12
* clarkb scribbles a note to do that after the meeting19:12
corvusoh yeah, using update-cfg-mgmt on these would be helpful19:12
clarkbcorvus: does that mean we are near to having nothing in server.pp?19:12
corvusclarkb: i think so19:12
clarkbneat19:12
Shrewsclarkb: 913 might need changes from 849 for unattended upgrades19:13
corvuslooks like automatic upgrades and afs client are the last19:13
*** dustins_ has joined #openstack-meeting19:13
clarkbShrews: ok I can rebase that if necesary (will look after the meeting)19:14
*** cloudrancher has quit IRC19:14
corvusianw: i'm not sure what's needed to remove afs from server.pp... you've been mostly looking at wheel builders, but i imagine this also affects zuul executors, files.o.o, etc...19:14
ianwyes, that was the plan, i can look at the control-plane side19:14
*** cloudrancher has joined #openstack-meeting19:15
corvusmaybe the afs client role should be in per-hostgroup playbooks?19:15
*** dustins_ has quit IRC19:15
*** dustins has quit IRC19:16
corvusso instead of moving it from server.pp to base.yaml, we move it to zuul-executor.yaml or whatever...?  it'll slow down the removal of server.pp slightly, but i think makes more sense19:16
ianwas in staging the rollout?19:17
ianwthat's definitely a good idea.  we just had the wheel jobs change approved today, so i will first validate the roles in action there, and then can add them as we progress19:18
clarkbonce I've got the launch node python and puppet intsallation stuff mostly behind me I'll hopefully have time to help with cloud launcher and clouds.yaml changes19:18
pabelangeryah, I'm starting on clouds.yaml change, just getting some testinfra things in place19:18
pabelangershould be able to get eyes on reviews for tomorrow19:19
*** markvoelker has joined #openstack-meeting19:19
*** cloudrancher has quit IRC19:20
clarkbanything else on this topic?19:20
clarkbseems like its mostly just working through the todo list (and we are doing that \o/)19:20
clarkb#topic Storyboard19:21
*** openstack changes topic to "Storyboard (Meeting topic: infra)"19:21
clarkbfungi: diablo_rojo: I have not caught up on storyboard happenings over the last week. Anything to bring up here?19:21
diablo_rojoTwo migrations of official projects + one unofficial project this Friday.19:22
fungia few migrations probably going down friday19:22
fungiyeah, freezer, searchlight and slogging19:22
diablo_rojoLots of SotK's things got merged. Only a few open reviews which is cool.19:22
diablo_rojoTime to get some new work in.19:22
AJaeger;)19:22
diablo_rojoI have one, fatema_ has one, SotK has a few.19:22
fungiparticularly lots of webclient fixes/improvements19:22
fungigot merged19:23
diablo_rojoAJaeger, :)19:23
diablo_rojoThat's all I have there.19:23
fungiyep, i didn't have anything new to report either19:23
clarkbfungi: I assume that we are still deploying those updates successfully?19:23
clarkb(so users will see them)19:23
*** e0ne has joined #openstack-meeting19:23
fungicorrect19:23
fungias of a while back, the webclient about page also mentions the git commit19:24
fungi#link https://storyboard.openstack.org/#!/page/about19:24
fungi"Webclient version: e6bf69d..."19:24
fungiso it's easy to check whether it's current19:25
clarkbthat is helpful thanks19:25
clarkb#topic General Topics19:26
*** openstack changes topic to "General Topics (Meeting topic: infra)"19:26
clarkbThis may end up being a short meeting.19:26
clarkbThe motivation for getting launch node working is mnaser is giving us access to a new vexxhost region to burn in with nodepool19:26
fungii hear it has some very recent openstack19:27
clarkbI'm working on spinning up the in region mirror there (which reuired launch node)19:27
*** annabelleB has quit IRC19:27
clarkbI think mnaser said it is running rocky19:27
fungiright on!19:27
corvusnot stein?19:27
corvusso old19:27
clarkbmostly an FYI that this is happening and keep an eye out for odd nodepool behavior19:27
AJaegera low prio task - we have a couple of repos that look dead, see http://lists.openstack.org/pipermail/openstack-infra/2018-August/006058.html - anybody interested to review and suggest which ones to retire?19:28
corvusoh, flashing back to the ansible topic -- i'm also resuming work on the per-project ssh keys work for zuul, as it may be helpful during our ptg work19:28
clarkb#link http://lists.openstack.org/pipermail/openstack-infra/2018-August/006058.html list of openstack-infra repos which have been idle and may need retirement19:29
clarkbAJaeger: I can take a look. I think the vinz repos for sure can be retired19:29
* AJaeger is happy to help retiring...19:29
AJaegerthanks, clarkb19:29
corvusi'd work from your list at the bottom, for starters.19:29
clarkbfungi: you had a winterscale topic item, I think this was from last week but probably worth bringing up again today? Basically there is an email thread now where your feedback would be appreciated19:30
fungiyeah, that's pretty much the long and short of it19:30
clarkb#link http://lists.openstack.org/pipermail/openstack-infra/2018-August/006075.html winterscale naming thread, please provide feedback19:30
corvus(git-restack is not dead, it's just perfect)19:30
fungiwould be nice to pick a name before the ptg19:30
clarkbcorvus: ha19:30
clarkbfungi: ++19:30
clarkbI think if we can decide on a name that will make many people happy19:30
fungioh, speaking of idle, how do people feel about knocking out a new git-review release?19:30
fungi#link http://lists.openstack.org/pipermail/openstack-infra/2018-August/006084.html git-review tagging schedule19:30
corvus[not actually kidding :)]19:30
clarkbfungi: I'm happy that gerrit reached out about it19:31
fungii didn't see much from the infra team on that thread19:31
clarkbfungi: I htink we should go ahead and do that19:31
corvussounds important19:31
fungiyes19:31
AJaegercorvus: that's why I didn't list it at the bottom ;)19:31
fungithey tracked down an openstack mailing list (granted not the one we watch closely, but still)19:31
clarkbwill probably make electrofelix and others happy to have some bug fixes included as well19:32
fungiyeah, as noted i at least want to get the release notes change in if anyone is up to approve19:32
clarkbfungi: maybe do it after the openstack release just to avoid tripping that up with new behavior?19:32
*** radeks_ has joined #openstack-meeting19:32
fungisure, official rocky release is two days away anyway19:32
clarkbfungi: do you have a link to the change you want in?19:32
corvusthe lesson here, btw, is *not* to adjust your code until required by deprecation.  you might think the lesson is the opposite -- but we're only in this situation because we adopted refs/publish, because it was supposed to replace refs/for.  :)19:33
clarkbI don't see it on the -infra list thread19:33
clarkbcorvus: indeed19:33
fungibut to be honest, i don't think any contributions people push to gerrit tomorrow are likely to be in the initial rocky tag anyway ;)19:33
ianwI haven't had too much more feedback on the 3rd-party CI spec.  I will probably re-frame this as a "help wanted" spec, because I don't think anyone one single person is willing to drive it ATM (if you are, speak up).  But i'll be glad if it is in a sanctioned state such that someone with interest can work from it19:33
fungiclarkb: it's linked in the last paragraph of the message i linked19:33
clarkbianw: ++19:33
corvusianw: that sounds appropriate to me19:33
fungi#link https://review.openstack.org/593670 Start using reno for releasenotes19:34
clarkbhrm my email client has broken up the threads looks like19:34
fungioh, though that's actually one change in a series19:34
fungithe release notes themselves are in 59367119:35
fungino, ignore me, that one's abandoned19:35
fungiit was squashed into 59367019:35
clarkb#topic Open Discussion19:36
*** openstack changes topic to "Open Discussion (Meeting topic: infra)"19:36
fungiianw: yeah, i'd like to think that someone interested in running/upgrading to zuul v3 for their third-party ci system might pick up some tasks from that spec19:37
clarkbIt didn't make it to the official agenda because I'm still catching up after a week off, but a reminder that the PTG is coming up ina few weeks19:37
clarkbcollecting agenda thoughts at https://etherpad.openstack.org/p/infra-ptg-denver-2018 and if you want to join us for biergarten dinner whilke there please put rough availability on https://ethercalc.openstack.org/fgry72wu42qw19:37
clarkbI'll send out a note with a night for that week before PTG probably19:38
clarkbin two weeks19:38
clarkbwow where did time go19:38
clarkbfloor is open for any other items, but I'll probably end the meeting at 19:45 UTC if nothing comes up and we can go eat lunch or breakfast 15 minutes early :)19:39
clarkbor dinner!19:39
ShrewsOh, for those interested, we are due to begin pushing zuul and nodepool container images to dockerhub any moment now (next merge for zuul and after https://review.openstack.org/597171 lands for nodepool)19:39
pabelangerhttps://hub.docker.com/r/zuul/19:40
pabelangerlooks like some are live?19:40
Shrewsnext we'll add infra edge computing somehow19:40
corvusyeah, i enqueued a ref earlier19:40
Shrewspabelanger: oh neat!19:40
pabelangerI'm totally spending some time now to try them out19:41
clarkboh another PTG item is Friday is a "free" day for infra.  Ithink TC may be doing stuff on Friday but thought it gave us an opportunity to find something fun to do together if we want19:41
AJaegercan we add some descriptoins for the images?19:41
pabelangerAJaeger: hopefully not via webui19:42
AJaeger:)19:42
corvuswow that's a lot of screen real estate for almost no content19:42
*** njohnston has quit IRC19:42
clarkbpbrx can probably grab the description out of the setup.cfg and publish that?19:42
*** awaugama has quit IRC19:43
Shrewsi don't thing setup.cfg provides per-entrypoint descriptions? so that might be a bit difficult19:43
funginote that the "something" the openstack tc members are doing on ptg friday is holding sessions for which anyone is welcome to attend and participate19:43
*** njohnston has joined #openstack-meeting19:43
clarkbfungi: is there an agenda for those yet?19:43
clarkb(I wasn't sure of the details just saw a room blocked off for TC)19:43
fungi#link https://etherpad.openstack.org/p/tc-stein-ptg19:43
clarkbthanks!19:44
*** cloudrancher has joined #openstack-meeting19:44
corvussunday, otoh, is a day of internal reflection for the tc19:44
fungii wanted sunday to be wide open too, but there wasn't much space available on short notice19:45
fungithis was as an alternative to trying to get together around some other conference where even fewer of the tc members were likely to be around19:45
clarkbalright its 19:45 UTC I'll go ahead and call it a meeting we can follow up in the infra channel and on the infra list. Time for food :) thank you everyone.19:46
clarkb#endmeeting19:46
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"19:46
openstackMeeting ended Tue Aug 28 19:46:33 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:46
openstackMinutes:        http://eavesdrop.openstack.org/meetings/infra/2018/infra.2018-08-28-19.01.html19:46
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/infra/2018/infra.2018-08-28-19.01.txt19:46
openstackLog:            http://eavesdrop.openstack.org/meetings/infra/2018/infra.2018-08-28-19.01.log.html19:46
clarkb(mostly thats a defensive tactic as my todo list just grew like 6 items)19:46
clarkb:)19:46
*** Shrews has left #openstack-meeting19:47
*** AJaeger has left #openstack-meeting19:47
*** dustins has joined #openstack-meeting19:49
*** hongbin has quit IRC19:50
*** hongbin has joined #openstack-meeting19:52
*** raildo has quit IRC20:05
*** annabelleB has joined #openstack-meeting20:14
*** erlon has quit IRC20:15
*** tssurya has quit IRC20:16
*** slaweq has quit IRC20:40
*** slaweq has joined #openstack-meeting20:40
*** radeks__ has joined #openstack-meeting20:41
*** priteau has quit IRC20:43
*** radeks_ has quit IRC20:44
*** annabelleB has quit IRC20:47
*** radeks__ has quit IRC20:56
*** e0ne has quit IRC20:58
*** markvoelker has quit IRC21:05
*** bnemec has quit IRC21:12
*** bnemec has joined #openstack-meeting21:13
*** eharney has quit IRC21:16
*** rcernin has joined #openstack-meeting21:46
*** ykatabam has joined #openstack-meeting22:03
*** macza_ has quit IRC23:00
*** sambetts|afk has quit IRC23:01
*** tpsilva has quit IRC23:04
*** sambetts_ has joined #openstack-meeting23:05
*** hongbin has quit IRC23:15
*** dustins has quit IRC23:25
*** erlon has joined #openstack-meeting23:34
*** dmacpher__ has quit IRC23:48
*** cloudrancher has quit IRC23:57

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