Tuesday, 2018-09-25

*** ekcs_ has quit IRC00:03
*** zigo has quit IRC00:05
*** mriedem_away has quit IRC00:10
*** annabelleB has joined #openstack-meeting00:21
*** longkb has joined #openstack-meeting00:35
*** ykatabam has joined #openstack-meeting00:42
*** annabelleB has quit IRC00:42
*** hongbin has joined #openstack-meeting01:00
*** erlon has quit IRC01:21
*** jamesmcarthur has joined #openstack-meeting01:28
*** rbudden has joined #openstack-meeting01:29
*** iyamahat_ has joined #openstack-meeting01:32
*** jamesmcarthur has quit IRC01:33
*** yamahata has quit IRC01:34
*** iyamahat has quit IRC01:35
*** mmethot has quit IRC01:41
*** iyamahat_ has quit IRC01:41
*** iyamahat has joined #openstack-meeting01:41
*** iyamahat has quit IRC01:46
*** iyamahat has joined #openstack-meeting01:48
*** diablo_rojo has quit IRC01:48
*** rbudden has quit IRC01:56
*** felipemonteiro has joined #openstack-meeting02:01
*** felipemonteiro has quit IRC02:02
*** iyamahat_ has joined #openstack-meeting02:16
*** iyamahat has quit IRC02:19
*** _alastor_ has joined #openstack-meeting02:23
*** _alastor_ has quit IRC02:27
*** felipemonteiro has joined #openstack-meeting02:28
*** Bhujay has joined #openstack-meeting02:29
*** Bhujay has quit IRC02:30
*** Bhujay has joined #openstack-meeting02:30
*** jamesmcarthur has joined #openstack-meeting02:35
*** iyamahat_ has quit IRC02:36
*** felipemonteiro has quit IRC02:43
*** psachin has joined #openstack-meeting02:43
*** imacdonn has quit IRC02:50
*** imacdonn has joined #openstack-meeting02:50
*** ijw has joined #openstack-meeting03:03
*** ijw has quit IRC03:03
*** cloudrancher has joined #openstack-meeting03:06
*** tpatil has joined #openstack-meeting03:10
*** armax has quit IRC03:11
*** felipemonteiro has joined #openstack-meeting03:11
*** tpatil has quit IRC03:17
*** cloudrancher has quit IRC03:18
*** cloudran_ has joined #openstack-meeting03:18
*** vipul has quit IRC03:20
*** jamesmcarthur has quit IRC03:23
*** jamesmcarthur has joined #openstack-meeting03:24
*** jamesmcarthur has quit IRC03:28
*** felipemonteiro has quit IRC03:30
*** Bhujay has quit IRC03:41
*** tpatil has joined #openstack-meeting03:53
*** sagara has joined #openstack-meeting03:57
tpatilsamP: Ping?04:05
*** tetsuro has quit IRC04:05
tpatilIt looks samP is not available to host today's Masakari meeting04:07
sagaratpatil: Hi04:07
tpatilsagara: Hi04:07
sagaratpatil: OK. Do we skip today's meeting?04:08
tpatilsagara: Yes, let's skip today's meeting04:08
sagaratpatil: OK, thanks. See you then!04:08
tpatilsagara: Bye04:09
*** sagara has quit IRC04:09
*** tpatil has quit IRC04:22
*** rcernin has quit IRC04:24
*** cloudran_ has quit IRC04:26
*** cloudrancher has joined #openstack-meeting04:26
*** cloudrancher has quit IRC04:26
*** e0ne has joined #openstack-meeting04:28
*** hongbin has quit IRC04:33
*** Bhujay has joined #openstack-meeting04:37
*** rcernin has joined #openstack-meeting04:38
*** yamamoto has quit IRC04:46
*** yamamoto has joined #openstack-meeting04:46
*** e0ne has quit IRC04:51
*** e0ne has joined #openstack-meeting05:09
*** e0ne has quit IRC05:10
*** pescobar has joined #openstack-meeting05:16
*** rcernin_ has joined #openstack-meeting05:17
*** lbragstad has quit IRC05:18
*** rcernin has quit IRC05:19
*** ykatabam has quit IRC05:37
*** pcaruana has joined #openstack-meeting05:41
*** iyamahat has joined #openstack-meeting05:48
*** belmoreira has joined #openstack-meeting05:59
*** Bhujay has quit IRC06:00
*** yamahata has joined #openstack-meeting06:05
*** Bhujay has joined #openstack-meeting06:14
*** Bhujay has quit IRC06:15
*** Bhujay has joined #openstack-meeting06:16
*** slaweq has joined #openstack-meeting06:18
*** aojea has joined #openstack-meeting06:24
*** yamahata has quit IRC06:28
*** aojeagarcia has joined #openstack-meeting06:29
*** aojea has quit IRC06:32
*** Bhujay has quit IRC06:32
*** Bhujay has joined #openstack-meeting06:33
*** ykatabam has joined #openstack-meeting06:40
*** Luzi has joined #openstack-meeting06:53
*** lpetrut has joined #openstack-meeting06:54
*** lpetrut has quit IRC06:56
*** lpetrut has joined #openstack-meeting06:56
*** strigazi has joined #openstack-meeting06:56
*** slaweq has quit IRC06:58
*** ykatabam has quit IRC06:59
*** rcernin_ has quit IRC07:05
*** slaweq has joined #openstack-meeting07:11
*** slaweq has quit IRC07:16
*** iyamahat has quit IRC07:27
*** psachin has quit IRC07:41
*** alexchadin has joined #openstack-meeting07:42
*** psachin has joined #openstack-meeting07:49
*** e0ne has joined #openstack-meeting07:52
*** e0ne has quit IRC07:53
*** joxyuki has joined #openstack-meeting08:03
*** hadai has joined #openstack-meeting08:04
*** jamesmcarthur has joined #openstack-meeting08:09
*** jamesmcarthur has quit IRC08:13
*** ttsiouts has joined #openstack-meeting08:27
*** jamesmcarthur has joined #openstack-meeting08:30
*** tpatil has joined #openstack-meeting08:32
*** jamesmcarthur has quit IRC08:34
*** ttsiouts has quit IRC08:46
*** ttsiouts has joined #openstack-meeting08:47
*** hadai has quit IRC08:48
*** slaweq has joined #openstack-meeting08:49
*** jamesmcarthur has joined #openstack-meeting08:50
*** ttsiouts has quit IRC08:51
*** priteau has joined #openstack-meeting08:54
*** jamesmcarthur has quit IRC08:55
*** tpatil has quit IRC08:55
*** e0ne has joined #openstack-meeting08:59
*** joxyuki has left #openstack-meeting09:01
*** ttsiouts has joined #openstack-meeting09:07
*** ttsiouts has quit IRC09:10
*** ttsiouts has joined #openstack-meeting09:10
*** tetsuro has joined #openstack-meeting09:11
*** jamesmcarthur has joined #openstack-meeting09:11
*** alexchadin has quit IRC09:12
*** alexchadin has joined #openstack-meeting09:16
*** jamesmcarthur has quit IRC09:16
*** tssurya has joined #openstack-meeting09:17
*** Emine has joined #openstack-meeting09:18
*** janki has joined #openstack-meeting09:20
*** jamesmcarthur has joined #openstack-meeting09:32
*** jamesmcarthur has quit IRC09:36
*** longkb has quit IRC09:59
*** electrofelix has joined #openstack-meeting10:00
*** janki has quit IRC10:07
*** e0ne has quit IRC10:12
*** jamesmcarthur has joined #openstack-meeting10:13
*** jamesmcarthur has quit IRC10:17
*** Bhujay has quit IRC10:31
*** Bhujay has joined #openstack-meeting10:32
*** yamamoto has quit IRC10:32
*** jamesmcarthur has joined #openstack-meeting10:34
*** ttsiouts has quit IRC10:35
*** jamesmcarthur has quit IRC10:38
*** rcernin_ has joined #openstack-meeting10:44
*** stephenfin_ is now known as stephenfin10:48
*** janki has joined #openstack-meeting10:50
*** rcernin_ has quit IRC10:52
*** alexchadin has quit IRC10:52
*** yamamoto has joined #openstack-meeting10:57
*** e0ne has joined #openstack-meeting10:58
*** artom has quit IRC11:00
*** erlon has joined #openstack-meeting11:00
*** ttsiouts has joined #openstack-meeting11:04
*** janki has quit IRC11:07
*** rubasov has joined #openstack-meeting11:10
*** pcaruana has quit IRC11:15
*** jamesmcarthur has joined #openstack-meeting11:15
*** jamesmcarthur has quit IRC11:20
*** e0ne_ has joined #openstack-meeting11:22
*** e0ne has quit IRC11:25
*** alexchadin has joined #openstack-meeting11:56
*** jamesmcarthur has joined #openstack-meeting11:57
*** jamesmcarthur has quit IRC12:01
*** psachin has quit IRC12:07
*** ttsiouts has quit IRC12:09
*** raildo has joined #openstack-meeting12:12
*** ttsiouts has joined #openstack-meeting12:21
*** yamamoto has quit IRC12:22
*** tpsilva has joined #openstack-meeting12:24
*** tetsuro has quit IRC12:28
*** Bhujay has quit IRC12:31
*** Bhujay has joined #openstack-meeting12:32
*** Bhujay has quit IRC12:33
*** Bhujay has joined #openstack-meeting12:33
*** lpetrut has quit IRC12:33
*** alexchadin has quit IRC12:36
*** lpetrut has joined #openstack-meeting12:36
*** alexchadin has joined #openstack-meeting12:37
*** alexchadin has quit IRC12:37
*** alexchadin has joined #openstack-meeting12:37
*** alexchadin has quit IRC12:38
*** alexchadin has joined #openstack-meeting12:38
*** alexchadin has quit IRC12:38
*** alexchadin has joined #openstack-meeting12:39
*** rbudden has joined #openstack-meeting12:39
*** alexchadin has quit IRC12:39
*** alexchadin has joined #openstack-meeting12:49
*** alexchadin has quit IRC12:54
*** ssbarnea has quit IRC12:56
*** yamamoto has joined #openstack-meeting12:59
*** lbragstad has joined #openstack-meeting12:59
*** cloudrancher has joined #openstack-meeting12:59
*** tssurya has quit IRC13:01
*** tssurya has joined #openstack-meeting13:01
*** bobh has joined #openstack-meeting13:03
*** belmoreira has quit IRC13:05
*** ssbarnea has joined #openstack-meeting13:06
*** lbragstad has quit IRC13:09
*** alexchadin has joined #openstack-meeting13:16
*** cloudrancher has quit IRC13:20
*** cloudrancher has joined #openstack-meeting13:20
*** zaneb has quit IRC13:21
*** yamamoto has quit IRC13:22
*** zaneb has joined #openstack-meeting13:23
*** lbragstad has joined #openstack-meeting13:23
*** lbragstad has quit IRC13:24
*** lbragstad has joined #openstack-meeting13:24
*** cloudrancher has quit IRC13:26
*** lbragstad has quit IRC13:26
*** lbragstad_ has joined #openstack-meeting13:26
*** lbragstad_ has quit IRC13:26
*** cloudrancher has joined #openstack-meeting13:27
*** lbragstad has joined #openstack-meeting13:27
*** ttsiouts has quit IRC13:27
*** dustins has joined #openstack-meeting13:28
*** belmoreira has joined #openstack-meeting13:29
*** munimeha1 has joined #openstack-meeting13:37
*** iyamahat has joined #openstack-meeting13:38
*** yamamoto has joined #openstack-meeting13:42
*** yamamoto has quit IRC13:42
*** yamamoto has joined #openstack-meeting13:45
*** mlavalle has joined #openstack-meeting13:54
*** hongbin has joined #openstack-meeting13:57
*** annp has joined #openstack-meeting13:58
*** manjeets_ has joined #openstack-meeting13:59
*** awaugama has joined #openstack-meeting14:00
mlavalle#startmeeting networking14:00
openstackMeeting started Tue Sep 25 14:00:26 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
njohnstono/14:00
haleybhi14:00
bcafarelhi14:00
annphi14:01
manjeets_hi14:01
slaweqhi14:01
mlavalleok, let's get going14:01
mlavalle#topic Announcements14:01
*** openstack changes topic to "Announcements (Meeting topic: networking)"14:01
munimeha1hi all14:02
rubasovo/14:02
mlavalleOur next milestone is Stein-1, October 22 - 2614:02
hongbino/14:02
mlavalleThe complete Stein release schedule is here: https://releases.openstack.org/stein/schedule.html14:03
*** evrardjp has joined #openstack-meeting14:03
mlavalleYesterday I sent to the ML a summary of the meetings we had in Denver during the PTG:14:04
mlavalle#link http://lists.openstack.org/pipermail/openstack-dev/2018-September/135032.html14:04
mlavalleI hope I captured the discussions accurately14:04
njohnstonThanks for that, it is very complete14:04
*** ttsiouts has joined #openstack-meeting14:05
mlavalleWe will keep a pointer to that summary in the announcements section of our weekly agenda, for rapid reference14:05
mlavalleAny other announcements?14:06
mlavalleok, let's move on14:06
mlavalle#topic Blueprints14:07
*** openstack changes topic to "Blueprints (Meeting topic: networking)"14:07
munimeha1summary looks good, thanks14:07
*** alexchadin has quit IRC14:07
mlavalleThese are the blueprints that we are targeting at this point in the cycle:14:07
mlavalle#link https://launchpad.net/neutron/+milestone/stein-114:07
mlavalleAs a result of the PTG summary, I might update it over the next few days14:08
mlavalleDoes anyone have any updates or requests for help in regards to blueprints?14:08
tidwellr_I've been out of the loop, does anyone know the status of https://blueprints.launchpad.net/neutron/+spec/subnet-onboard ?14:10
*** e0ne_ has quit IRC14:10
munimeha1We have implemented the new solution as discussed at PTG14:10
munimeha1i need to know if we are ok with it14:10
*** e0ne has joined #openstack-meeting14:10
bcafareltidwellr_: that one is mine now, target for Stein indeed14:10
munimeha1https://review.openstack.org/#/c/603501/14:11
tidwellr_bcafarel: great! do you have a link to a review handy?14:11
mlavallemunimeha1: I took a look on Friday at the spec. I will look again today or tomorrow, but it seemed to me that we were close to converge on a solution14:11
munimeha1thanks14:12
*** alexchadin has joined #openstack-meeting14:12
mlavallemunimeha1: also, this week, per the PTG summary, I will push a patch with the evaluation criteria to bring TaaS to the Stadium. In the first version, all the questions will be "Fail" and then you and I start working on them one by one14:13
mlavallewe have to start from somewhere :-)14:13
bcafareltidwellr_: https://review.openstack.org/#/c/348080/ (I have some local changes here on top, but that's mostly it atm)14:14
manjeets_munimeha1, spec need changes since with tap flow it will have data model impact14:14
munimeha1manjeet i updated that in version 1814:14
mlavallemunimeha1: thanks for the update :)14:15
mlavalleok, anything else on blueprints?14:15
manjeets_cool14:15
mlavallelet's move on then14:16
mlavalle#topic Community goals14:16
*** openstack changes topic to "Community goals (Meeting topic: networking)"14:16
*** alexchadin has quit IRC14:17
*** boden has joined #openstack-meeting14:17
mlavalleamotoki is off on a well deserved vacation this week, so no update on policy in code14:17
mlavallenjohnston: any updates worth mentioning on PY36?14:17
njohnstonThe neutron-fullstack-python36 job is now voting14:18
*** longkb has joined #openstack-meeting14:18
mlavalle\o/14:18
bcafarelnjohnston: btw I sent https://review.openstack.org/#/c/604749/ -python36 job actually still runs 3.5 :)14:18
bcafarelit fails finding py36 though14:18
*** alexchadin has joined #openstack-meeting14:19
njohnstonI am going to ask the infra team if when we convert jobs from the legacy format tot he new zuulv3 format if we need to do anything to enable python 3 or if it comes by default14:19
njohnstonbcafarel: Thanks for that!  I'll check on the failing to find python 3.6 issue with infra as well14:19
mlavallegood catch bcafarel!14:19
njohnstonI have one change up to convert the iptables_hybrid tempest job to the new format so I will see if I can use that to see if we get python 3 for free there14:20
njohnstonthat's it for python 3 for now14:21
mlavallethanks for the update, njohnston14:21
mlavalleslaweq: any updates on pre-upgrade checks?14:22
slaweqmlavalle: not too much yet14:22
mlavalleslaweq: cool, thanks14:22
slaweqbut there is topic about that in ML also: http://lists.openstack.org/pipermail/openstack-dev/2018-September/134249.html14:22
slaweqI'm following it for now14:22
slaweqit looks that most of the common code will be in new oslo repository so I will consume it from there14:22
mlavallethis seems good. You have a recipe to follow and mriedem is very thorough in this type of things14:24
mlavalleso it should cover all or close to all that you have to do14:24
slaweqyes, I only need some time to start this patch :)14:24
mlavallevery good14:24
mlavalleok, let's move on14:25
mlavalle#topic Bugs14:25
*** openstack changes topic to "Bugs (Meeting topic: networking)"14:25
*** mjturek has joined #openstack-meeting14:25
bodenI sent a summary of last weeks bugs to the ML14:26
boden#link http://lists.openstack.org/pipermail/openstack-dev/2018-September/135008.html14:26
*** mriedem has joined #openstack-meeting14:26
* mlavalle was beaten by boden posting the pointer :-)14:26
bodenI can read minds... that comes along with being married14:26
mlavallethat's tru, LOL14:27
mlavalleany bugs that you might want to highlight?14:27
bodenthe bugs in the first 2 lists of that email still require some attention by technical experts in the respective area14:27
mlavalleok, I'll go over those two lists after the morning meetings. I encourage others to do the same14:28
bodenI will just note that it appears bug https://bugs.launchpad.net/neutron/+bug/1792925  breaks  ironic's grenade job... I'm assuming that's high priority for them, but not sure14:29
openstackLaunchpad bug 1792925 in neutron "q-dhcp crashes with guru meditation on ironic's grenade" [Undecided,New]14:29
mlavallethanks for pointing that out. I will follow up with them14:29
bodenthat's all I have on this topic14:29
mlavalleThis week our deputy is njohnston14:30
munimeha1In end can we discuss these issues, i have a question about a two issues - we want solution/can develop for it in Stein-2, One is for trunk sriov port multiple vlans on a direct port, another is bonding of SRIOV VFs for VRRP(all direct ports with 00:00:00:00) mac so tenant can do HA with changing macs of interfaces. Nics support this on VF but Openstack don't allow it since we have random mac in neutron port.14:30
mlavallemunimeha1: yes, let's discuss that at the end14:31
njohnstonThanks mlavalle, I am on it14:31
*** longkb has quit IRC14:31
mlavalleand also pelase note that I updated our bugs deputy calendar. removed garyk, since he doesn't work upstream anymore14:32
mlavalleif any other volunteers one to add their name to the calendar, please speak up14:32
mlavalleit's only one week every 3 months14:32
mlavalleok, let's move on14:33
*** Luzi has quit IRC14:33
rubasovI could also be a bug deputy14:33
mlavallerubasov: of course you can :-)14:33
rubasovplease add my name too14:33
mlavallerubasov: will the first week of Decmber be good for you?14:34
rubasovit's new to me but I'll try doing my best14:34
rubasovyes14:34
mlavallerubasov: we have a set of guidelines in the docs, that were originally created by njohnston if I remember correctly14:35
mlavalleand you can always yell for help14:35
rubasovmlavalle: I'm aware14:35
rubasovmlavalle: I'm still digesting some of it14:35
mlavallecool14:35
rubasovI'm sure I will ask a few times on that week :-)14:35
mlavallelet's move on then14:35
mlavalle#topic os-ken14:36
*** openstack changes topic to "os-ken (Meeting topic: networking)"14:36
*** annabelleB has joined #openstack-meeting14:36
mlavallefirst of all, please note that I just changed the title of this topic in our agenda: https://wiki.openstack.org/wiki/Network/Meetings#os-ken14:36
mlavallehongbin: any updates worth mentioning this week?14:37
hongbinhi14:37
hongbin#link https://review.openstack.org/#/q/project:openstack/os-ken14:37
hongbinabove is the list of patches that are under review in that repo14:37
hongbinas we discussed, we plans the first release after those patches are merged14:38
mlavalleah nice. I will review them later today14:38
hongbinmlavalle: thanks14:38
hongbinthere is a question raised in the code review though14:38
hongbinslaweq raised a question about whether os-ken should move to storyboard? or stay at launchpad14:38
hongbinthroughts?14:39
mlavallethat's a good question (which I fully expect slaweq to raise). and I think we should skip launchpad and go straight to storyboard14:39
njohnston+114:40
mlavalleleapfrog14:40
slaweqIMHO it might be good, small project to start playing with storyboard a bit14:40
slaweqand we will don't need to migrate it later14:40
mlavalleexactly right14:40
bcafarel+ no need to add additional ingredients in the curent neutron launchpad soup :)14:40
mlavalleLOL, the soup14:41
hongbinok, i will look into how to setup the storyboard later14:41
njohnstonhongbin: diablo_rojo can help14:42
mlavallehongbin: I will copy you in an email thread that slaweq and I have been exchanging with diablo_rojo14:42
mlavalleshe is more than willing to help14:42
hongbinmlavalle: njohnston ack, thanks14:42
*** longkb has joined #openstack-meeting14:43
mlavalleok, moving on14:43
mlavalle#topic neutron-lib14:43
*** openstack changes topic to "neutron-lib (Meeting topic: networking)"14:43
mlavalleboden: any updates this week?14:43
bodenI do have a few things... I will try to be quick14:44
bodenFirst there's a new release of lib proposed: https://review.openstack.org/#/c/604908/   looks good to me, but others can have a looksee14:44
mlavalleadded to my pile14:44
bodennext, during the PTG we talked about identifying "current' projects and getting them updated for zuul/local testing... I started that work... details in https://etherpad.openstack.org/p/neutron-sibling-setup  under the "List of networking..." section14:45
bodenI would ask folks to keep an eye out for related patches and help out when possible14:45
mlavalleok, I'll lookout for those14:46
bodenwe also discussed how to test with neutron-lib master... there's a discussion in https://review.openstack.org/#/c/602748/ I was hoping cores could weigh in on14:46
mlavallewill look at it later today14:47
mlavalleor tomorrow14:47
mlavalleadded to my pile14:47
munimeha1tap-as-a-service is not considered as neutron sibling?14:47
bodenthere's also a discussion in https://review.openstack.org/#/c/596959/ that the callback payload patches are waiting on... I added some details there a week or so ago, but waiting for some concensus14:47
mlavalleI'll chime in14:48
bodenmunimeha1 it is not.. there's no neutron-lib in requirements https://github.com/openstack/tap-as-a-service/blob/master/requirements.txt14:48
bodenfinally, we talked about adding something to consumer projects that indicates they want neutron-lib updates... mlavalle were you still planning to send a note about that or should I?14:49
mlavalleboden: yes.... I wrote the summary first. and it is one of my todo's there. I'll tackle them this week14:50
yamamotoboden: i'm sure taas requires neutron-lib. i guess it's just a missing req.14:50
mlavallebut if you want to do it yourself, please feel free14:50
bodenmlavalle whichever14:50
bodenyamamoto I guess so and the topic mlavalle and I are just talking about is related14:51
bodenthat's enough lib fun for now since I just added a few hrs of work to mlavalle :)14:51
mlavalleLOL14:51
mlavallethanks for the update14:51
bodenmlavalle I can send the ML note for the lib topic14:52
mlavalleboden: cool, go ahead14:52
mlavallelet's move on14:52
mlavalle#topic On demand agenda14:52
*** openstack changes topic to "On demand agenda (Meeting topic: networking)"14:52
annphi14:52
*** AlanClark has joined #openstack-meeting14:54
mlavallego ahead annp14:54
annpmlavalle, thanks.14:54
annpIn order to support SNAT log extension, we inend to use libnefilter_log (Which is used for firewall logging) to capture packet log. So we’re planing to move libnetfilter_log to neutron-lib14:54
annpBut, neutron-lib doesn’t allow eventlet.14:54
annpCurrently, libnetfilter_log is using eventlet.green.zmp for communicating between libnetfilter_log process (privilege process) and log-application( un-privilege process)14:54
annpSo I’d like to get your advice: How do I deal with this issue or we should place libnetfilter_log in neutron?14:55
mlavalleIwould say that Neutron will have to have its own implementation of libnefilter_log14:55
annpmlavalle, I see. Thanks.14:56
mlavalleat least for the time being14:56
mlavallewe could leave a comment in the code14:56
*** cloudrancher has quit IRC14:56
njohnstonand if neutron-fwaas does the same logging then I guess we will need to live with code duplication14:56
mlavalleyeap, for the time being. Let's leave a todo comment14:56
mlavalleok, moving on....14:57
munimeha1hi14:57
annpmlavalle, yes. I will add todo comment. you read my mind. :-)14:57
mlavallemunimeha1: Please file a couple of RFEs for those two things as soon as possible14:57
*** alexchadin has quit IRC14:57
mlavalleif you file them today and we can have some exchanbge of thought over the next few days, we'll see if we can discuss them in the next drivers meeting14:58
munimeha1thanks, will do14:58
mlavallethank you14:59
mlavalleok team, we ran out of time. Thanks for attending. Have a great week!14:59
mlavalle#endmeeting14:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"14:59
openstackMeeting ended Tue Sep 25 14:59:35 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:59
slaweqthx14:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking/2018/networking.2018-09-25-14.00.html14:59
slaweqo/14:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking/2018/networking.2018-09-25-14.00.txt14:59
openstackLog:            http://eavesdrop.openstack.org/meetings/networking/2018/networking.2018-09-25-14.00.log.html14:59
munimeha1thanks14:59
annpthanks all.14:59
annpbye.14:59
*** annp has quit IRC15:00
slaweq#startmeeting neutron_qos15:00
openstackMeeting started Tue Sep 25 15:00:18 2018 UTC and is due to finish in 60 minutes.  The chair is slaweq. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
slaweqhi :)15:00
*** openstack changes topic to " (Meeting topic: neutron_qos)"15:00
openstackThe meeting name has been set to 'neutron_qos'15:00
rubasovhello again15:00
njohnstono/15:00
slaweq#topic RFEs15:00
*** openstack changes topic to "RFEs (Meeting topic: neutron_qos)"15:01
*** felipemonteiro has joined #openstack-meeting15:01
*** longkb has quit IRC15:01
*** boden has left #openstack-meeting15:01
mlavalleagain???? these zombies chase me all morning long15:01
slaweqwhat zombies? :)15:01
mlavalleslaweq, rubasov, njohnston, etc....15:01
slaweqLOL15:02
slaweqonly 2 hours left for today :P15:02
mlavalleyeap15:02
slaweqok, lets start15:02
slaweq#link https://bugs.launchpad.net/neutron/+bug/156096315:02
openstackLaunchpad bug 1560963 in neutron "[RFE] Minimum bandwidth support (egress)" [Wishlist,In progress]15:02
slaweqthere is still no any progress on this one15:02
*** Bhujay has quit IRC15:03
slaweqbut now as ralonsoh is back to Neutron I will try to talk with him about this one15:03
slaweqI just pinged him - maybe he will join us here15:03
*** david-lyle has quit IRC15:04
*** lpetrut has quit IRC15:04
slaweqlets go to the next one15:04
slaweq#link https://bugs.launchpad.net/neutron/+bug/172757815:04
openstackLaunchpad bug 1727578 in neutron "[RFE]Support apply qos policy in VPN service" [Wishlist,Triaged]15:04
mlavalleyeah, ralonsoh is a good addition to this team15:04
slaweqhere also it looks that there was no activity on this one also for some time15:04
*** dklyle has joined #openstack-meeting15:05
mlavallegive me an action item on this one for next week15:05
mlavalleI will ping zhaobo AND the VPN team15:05
*** jamesmcarthur has joined #openstack-meeting15:05
mlavalleto get it moving15:05
slaweq#action mlavalle to ping zhaobo about vpnaas qos patch15:05
slaweqthx mlavalle15:05
slaweqnext is:15:06
slaweq#link https://bugs.launchpad.net/neutron/+bug/175704415:06
openstackLaunchpad bug 1757044 in neutron "[RFE] neutron L3 router gateway IP QoS" [Wishlist,In progress] - Assigned to LIU Yulong (dragon889)15:06
slaweqfor this there are 2 patches in review already15:06
slaweqserver side changes: #link https://review.openstack.org/#/c/424468/15:06
*** felipemonteiro has quit IRC15:06
slaweqand L3 agent side: #link https://review.openstack.org/#/c/568526/15:06
slaweqI will need to review them this week15:06
mlavalleserver side is failing all zuul tests15:07
slaweq#action slaweq to review L3 GW QoS patches15:07
mlavalleactually both15:07
*** ttsiouts has quit IRC15:08
slaweqlooks like we need new neutron-lib release: http://logs.openstack.org/68/424468/26/check/openstack-tox-pep8/0a6f63b/job-output.txt.gz#_2018-09-20_20_25_59_66667215:08
slaweqbut I don't know if that is only problem with it15:08
mlavalleslaweq: let's make sure that in the relase that njohnston we are including a=everything that is needed for these two patches15:08
mlavalleso at least we remove that variable15:09
slaweqmlavalle: You mean 1.19, right?15:09
mlavalleyes15:09
slaweqok15:09
slaweqsounds good for me15:09
njohnstonfor the 1.19 release I set the tag where HEAD is right now15:09
njohnstonso if it has merged by now it is in15:09
slaweqhttps://github.com/openstack/neutron-lib/blob/master/neutron_lib/api/definitions/qos_gateway_ip.py15:10
slaweqthis api def is merged already15:10
mlavallenjohnston, slaweq: cool, thanks :-)15:10
*** ttsiouts has joined #openstack-meeting15:10
slaweqcan we go to next one then?15:10
mlavalleyes15:11
slaweqok15:11
slaweq#link https://bugs.launchpad.net/neutron/+bug/177762715:11
openstackLaunchpad bug 1777627 in neutron "RFE: QoS – rule's management (set,delete, show…) requires <qos-policy> parameter in addition to <rule-id>" [Wishlist,Triaged] - Assigned to Miguel Lavalle (minsel)15:11
*** kopecmartin is now known as kopecmartin|off15:11
slaweqmlavalle: any progress on this? I think You didn't work on it yet15:11
*** ralonsoh has joined #openstack-meeting15:12
mlavalleslaweq: I just realized that arkady is not going to implement15:12
slaweq:)15:12
slaweqso at least You know now :)15:12
mlavalleso I guess I'll start this week. Most likely over the weekend15:13
slaweqgreat, thx mlavalle15:13
mlavalleit shouldn't be very difficult15:13
slaweqI don't think so15:13
mlavalleand if I get in trouble, I'll come to get help from slaweq, the WoS guru15:13
mlavalleQoS15:14
slaweqLOL15:14
slaweqI was wondering what the hell is WoS ;)15:14
mlavalleLOL15:14
slaweqok, I have one more on the list15:14
slaweq#link https://bugs.launchpad.net/neutron/+bug/157898915:14
openstackLaunchpad bug 1578989 in neutron "[RFE] Strict minimum bandwidth support (egress)" [Wishlist,In progress] - Assigned to Lajos Katona (lajos-katona)15:14
slaweqrubasov: any updates?15:15
rubasovslaweq: a bit15:15
slaweqdemo in Denver was great - thx for that :)15:15
mlavalleyeah15:15
rubasovI did write that up15:15
rubasovthere's a mail about on the ML15:15
slaweqI saw it :)15:16
rubasovlajoskatona made progress with the code while I was slacking in Denver :-)15:16
rubasovhe has several patches in neutron and a few in neutron-tempest-plugin, where review is always welcome15:16
rubasovand I also hope to make a new round on my patches later this week15:17
* mlavalle wished he had included the demo write up in the PTG summary15:18
rubasovnow that's about all15:18
rubasovmlavalle: don't worry about that15:18
slaweqrubasov: all patches should be available under this topic like here: https://review.openstack.org/#/q/topic:minimum-bandwidth-allocation-placement-api+(status:open+OR+status:merged) right?15:19
*** fuentess has joined #openstack-meeting15:19
rubasovone little thing: I'll be out of office next week, but lajoskatona keeps up with the work15:19
rubasovslaweq: yes, that's the topic15:19
slaweqrubasov: ok, thx15:20
slaweqthx for update and for all Your and lajoskatona work on this feature :)15:20
rubasovthanks for all the help15:20
mlavalleyeap, great work!15:20
slaweqmlavalle: one thing FYI, I updated "implementation" of BP to "good progress" now based on the demo we saw in Denver15:21
slaweqI hope it's fine for You15:21
mlavalleperfectly fine. Thanks!15:21
slaweqk15:21
slaweqok, so that was all RFEs which I had on list15:22
slaweqany questions or something else what You want to add?15:22
mlavallenot from me15:22
rubasovnope15:22
slaweqok, so lets move on to the next topic15:23
slaweq#topic Bugs15:23
*** openstack changes topic to "Bugs (Meeting topic: neutron_qos)"15:23
slaweqI didn't see any new bugs related to qos15:23
slaweqbut we have few existing ones to mention :)15:23
slaweqfirst15:23
slaweq#link https://bugs.launchpad.net/neutron/+bug/178400615:23
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:23
slaweqmlavalle - any progress on this one?15:23
mlavalleso I was looking at it lately15:24
mlavalleand misunderstood the submitter comment15:24
mlavalleI thought it was not an issue anymore15:24
mlavallebut last night he left additional comment15:25
mlavalleso I'll get back to it15:25
slaweqok, thx15:25
slaweqnext one then15:26
slaweq#link https://bugs.launchpad.net/neutron/+bug/173285215:26
openstackLaunchpad bug 1732852 in neutron "neutron don't support Router gateway rate limit " [Low,New]15:26
slaweqit's long standing one :)15:26
slaweqand I have a question here15:26
slaweqcan we mark it as "duplicate" of  https://bugs.launchpad.net/neutron/+bug/1757044 ?15:26
openstackLaunchpad bug 1757044 in neutron "[RFE] neutron L3 router gateway IP QoS" [Wishlist,In progress] - Assigned to LIU Yulong (dragon889)15:26
slaweqit's not exactly duplicate but in fact both are about the same issue15:26
slaweqwhat You think mlavalle?15:26
* mlavalle looking15:27
mlavalleyeah, I think that makes sense15:28
slaweqok, thx15:28
slaweqI will do it after this meeting then15:28
mlavalle++15:28
slaweqnext one15:28
slaweq#link https://bugs.launchpad.net/neutron/+bug/177905215:28
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:28
slaweqthere is patch https://review.openstack.org/#/c/581941/ but there is no progress on it15:28
mlavallelet's leave a warning in the patch15:29
slaweqif there will be no update of it this week I will address comments from review and continue it to make it merged finally15:29
mlavalleyeap15:29
slaweq++15:29
mlavalleleave a comment today15:29
slaweqI will write a comment in review after this meeting also15:29
mlavallethat if we don't see progress this week, you will it over15:29
slaweqok, I will do that15:30
mlavalleThanks15:30
ralonsohI can continue with this one, if the developer doesn't continue with it15:30
*** armax has joined #openstack-meeting15:30
mlavalleniuce to see you again in this meeting :-)15:30
ralonsohthanks15:30
mlavalleralonsoh:15:30
slaweqralonsoh: please go ahead if You want and owner will not update it :)15:31
ralonsohslaweq: perfect!15:31
*** manjeets_ has quit IRC15:31
slaweqok, next one then15:31
slaweq#link https://bugs.launchpad.net/neutron/+bug/177616015:31
openstackLaunchpad bug 1776160 in neutron "'burst' does not take effect for neutron egress qos bindlimit by ovs" [Undecided,New]15:31
*** yamamoto has quit IRC15:31
slaweqI didn't have time to reproduce it yet15:32
*** yamamoto has joined #openstack-meeting15:32
slaweqit was marked as incomplete but reporter wrote some new comment so I switched it to new for now15:32
*** yamamoto has quit IRC15:32
*** cloudrancher has joined #openstack-meeting15:33
slaweqok, and the last one:15:33
slaweq#link https://bugs.launchpad.net/neutron/+bug/178518915:33
openstackLaunchpad bug 1785189 in neutron "Floatingip and router bandwidth speed limit failure" [Undecided,In progress] - Assigned to Brian Haley (brian-haley)15:33
slaweqPatch is proposed: https://review.openstack.org/#/c/596637/15:33
slaweqplease review if You have some time :)15:33
mlavalleLiu Yulong left some comments15:34
slaweqahh, there wasn't those comments when I was checking it today morning :)15:34
slaweqso let's wait for reply to Liu Yulong's comment and review it :)15:35
mlavalleyeap15:36
slaweqok, so that is all what I have for today15:36
slaweq#topic Open Discussion15:36
*** openstack changes topic to "Open Discussion (Meeting topic: neutron_qos)"15:36
*** Leo_m has joined #openstack-meeting15:36
slaweqanything You want to talk about?15:36
mlavallenot from me15:36
slaweqif not I will give You 22 minutes back today :)15:37
*** e0ne has quit IRC15:37
slaweqthx for attending15:37
ralonsohbye!15:37
mlavalleo/15:37
slaweqand see You in 2 weeks15:37
slaweqo/15:37
njohnstono/15:37
rubasovbye15:37
slaweq#endmeeting15:37
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"15:37
openstackMeeting ended Tue Sep 25 15:37:38 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:37
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_qos/2018/neutron_qos.2018-09-25-15.00.html15:37
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_qos/2018/neutron_qos.2018-09-25-15.00.txt15:37
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_qos/2018/neutron_qos.2018-09-25-15.00.log.html15:37
mlavalleslaweq: I might bew a few minutes late to the next meeting, but I'll be there15:37
slaweqmlavalle: ok, thx for info15:38
*** ttsiouts has quit IRC15:40
*** ttsiouts has joined #openstack-meeting15:43
*** yamamoto has joined #openstack-meeting15:44
*** yamamoto has quit IRC15:49
*** dustins has quit IRC15:49
*** artom has joined #openstack-meeting15:49
*** aojeagarcia has quit IRC15:52
*** belmoreira has quit IRC15:52
*** yamahata has joined #openstack-meeting15:52
slaweq#startmeeting neutron_ci16:00
openstackMeeting started Tue Sep 25 16:00:14 2018 UTC and is due to finish in 60 minutes.  The chair is slaweq. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
*** openstack changes topic to " (Meeting topic: neutron_ci)"16:00
slaweqwelcome again :)16:00
openstackThe meeting name has been set to 'neutron_ci'16:00
haleybhi16:00
mlavalleo/16:01
mlavallemade it16:01
slaweq:)16:01
bcafarelnow I remember why I miss most ci meetings, usually have to leave shortly after they start16:01
bcafarelstill hi again16:01
slaweqbcafarel: LOL16:02
slaweqok, lets go then16:02
slaweq#topic Actions from previous meetings16:02
*** openstack changes topic to "Actions from previous meetings (Meeting topic: neutron_ci)"16:02
slaweq* manjeets continue debugging why migration from HA routers fails 100% of times16:02
slaweqmanjeets: any progress on this one?16:02
slaweqI proposed today to mark those tests as unstable for now: https://review.openstack.org/60505716:02
*** bobh_ has joined #openstack-meeting16:03
slaweqI think manjeets is not available now16:03
slaweqmlavalle: please just take a look at this mine patch - I think it would be good to make this job passing at least sometimes :)16:04
njohnstono/16:04
mlavalledone16:04
njohnstono/16:04
slaweqthx mlavalle16:04
slaweqhi njohnston16:04
slaweqok, next one16:05
njohnstonsorry about the repeat there16:05
slaweq* mlavale to check issue with failing test_attach_volume_shelved_or_offload_server test16:05
slaweqno problem njohnston :)16:05
slaweqno problem njohnston :)16:05
slaweqLOL16:05
njohnston:-)16:05
*** _d34dh0r53_ is now known as d34dh0r5316:05
slaweqok, mlavalle any update about this shelved unshelved server test fail?16:06
mlavalleslaweq: hang on16:06
*** bobh has quit IRC16:06
slaweqk16:06
*** pcaruana has joined #openstack-meeting16:07
*** felipemonteiro has joined #openstack-meeting16:08
mlavalleslaweq: I don't find it. I think I left some notes recentky there16:08
slaweqYou don't find any issues like that recently, right?16:09
mlavalleyes16:10
mlavallebut do you have a pointer to the bug?16:10
slaweqI don't have16:11
slaweqbut let me find it16:11
*** Emine has quit IRC16:12
slaweqI can't find it16:13
slaweqwas it reported as a bug?16:13
slaweqmaybe we forgot about that?16:13
mlavalleyeah, that maybe the problem16:14
mlavallein any case, I spent some time last week searching kibana for it16:14
mlavalleand didn't find instances16:14
slaweqso maybe we will be good with it :)16:14
mlavalleI'll dig the query and get back to you16:14
slaweqok, thx16:15
mlavalleI sent myself an email16:15
mlavallewith the query that I need to dig16:15
slaweq#action mlavalle will work on logstash query to find if issues with test_attach_volume_shelved_or_offload_server still happens16:15
slaweqok, next one then16:16
slaweq* njohnston will continue work on switch fullstack-python35 to python36 job16:16
njohnstonSo it is voting now but as bcafarel pointed out it is still using py3516:16
njohnstonI am looking in to it now16:16
slaweqok16:16
slaweqwhat about removing old fullstack with py27?16:16
slaweqI think we are ready for that now16:17
njohnstonagreed, I'll push a change for that16:17
slaweqmlavalle: haleyb: are You ok with it?16:17
haleybyes, i'm fine with it16:17
mlavalleme too16:17
slaweqgreat16:18
slaweqok, thx njohnston for working on this16:18
slaweq#action njohnston will debug why fullstack-py36 job is using py3516:18
slaweq#action njohnston will send a patch to remove fullstack py27 job completly16:18
slaweqok, and the last one is:16:19
slaweq* slaweq will continue debugging multinode-dvr-grenade issue16:19
slaweqI was working on this last week but I didn't found anything16:19
slaweqI found that this issue happens very often on master branch and also on stable/pike16:19
*** ttsiouts has quit IRC16:20
slaweqbut I didn't found it even once on queens or rocky branches16:20
slaweqI suspected that it may be some package which was upgraded recently or something like that16:20
bcafarelso the "middle" branches are not affected? wierd16:20
*** ttsiouts has joined #openstack-meeting16:20
slaweqbut all such packages like ovs, libvirt, qemu and so on are in completly different versions in stable/pike and master branch16:21
slaweqso I don't think it's that16:21
*** yamamoto has joined #openstack-meeting16:21
slaweqI was using query like: http://logstash.openstack.org/#/dashboard/file/logstash.json?query=message:%5C%22'%5BFail%5D%20Couldn'%5C%5C''t%20ping%20server'%5C%2216:22
bcafarelyeah a master branch change that only got backported to versions used in pike sounds strange16:22
slaweqfrom last week (now in logstash): 91 failures on master, 33 on stable/pike16:23
* mlavalle found the logstash query: http://logstash.openstack.org/#/dashboard/file/logstash.json?query=build_status:%5C%22FAILURE%5C%22%20AND%20project:%5C%22openstack%2Fneutron%5C%22%20AND%20message:%5C%22test_attach_volume_shelved_or_offload_server%5C%22%20AND%20tags:%5C%22console%5C%22&from=7d16:23
*** ttsiouts has quit IRC16:25
slaweqmlavalle: so it looks that it happens still from time to time16:25
mlavalleslaweq: yeah but my obeservation last week is that, when it shows up, many other tests also fail16:26
mlavalleso that makes me suspicious of the the changes16:26
mlavalleand that's the case for the two ocurrences at the top16:26
slaweqok, it can be that it fails together with other tests also16:26
mlavallein today's result16:26
mlavalleso I'll dig today on this16:27
slaweqok16:27
haleybmlavalle: which changes are suspicious?16:27
haleyboh, maybe package changes16:28
mlavalleone example is https://review.openstack.org/#/c/60133616:28
mlavalleit's at the top of the search today16:28
haleyboh, that's just WIP though16:29
mlavalleyeah, that's why I say, I discount those16:30
mlavalleas not valid for this bug16:30
haleybright16:30
mlavallebut I will try to find a valid failure and investigate16:30
haleyb+116:30
slaweqthx mlavalle for working on this16:31
mlavallemy point is that there are less failures than the kibana results show16:31
mlavalleI mean real failures16:32
slaweqthat is possible :)16:32
* slaweq hopes that it's not another real issue16:32
haleybit could be we can add more debug commands to one of slaweq's patches too, because when it failed it was "happy" once we logged in to look around - running some more things from the console perhaps?  we just don't know where to start16:32
haleyblike looking at routes and arp table and flows...16:33
*** iyamahat has quit IRC16:33
slaweqhaleyb: are You talking about grenade issue now?16:33
*** yamahata has quit IRC16:33
haleybdid i miss a topic change ?16:33
mlavalleyes16:34
mlavallebut that's ok16:34
slaweqI think so :)16:34
slaweqLOL16:34
mlavalleI'm done with the other one16:34
slaweqso Your questions about "which change" were not related to what mlavalle was talking about?16:34
haleybdoh, last one i saw was " slaweq will continue debugging multinode-dvr-grenade issue"16:34
*** ayoung has joined #openstack-meeting16:34
mlavalleit was my fault16:34
mlavalleI interjected the discussion with my query16:35
mlavalleso blame it all on me16:35
mlavalleit's always the dumb PTL anyways16:35
haleyb:)16:35
slaweq:)16:35
slaweqok, so lets go back to grenade job now16:35
slaweqyes, when I was checking that after logging to node it was all fine16:36
slaweqand still there is one important thing - all smoke tests are passing first16:36
*** annabelleB has quit IRC16:36
slaweqand then there is this instance created and it fails16:36
slaweqbtw. as it happens also on pike - we can assume that it's not openvswitch firewall fault :)16:37
*** AlanClark has quit IRC16:38
slaweqhaleyb: if You want to execute some more commands for debug this, I did 2 small patches:16:38
slaweqhttps://review.openstack.org/#/c/602156/16:38
slaweqand16:38
slaweqhttps://review.openstack.org/#/c/602204/16:38
haleybright, that's a good thing.  it still could be ovs, or some config on the job side of things16:38
slaweqfeel free to update it with any new debug informations You want there :)16:38
haleybi'll take a look and probably add a few things16:38
*** AlanClark has joined #openstack-meeting16:39
slaweqfor now there is "sleep 3h" in https://review.openstack.org/#/c/602204/10/projects/60_nova/resources.sh added16:39
slaweqand in https://review.openstack.org/#/c/602156/ there is my ssh key added16:39
*** dklyle has quit IRC16:40
slaweqso if it will fail on https://review.openstack.org/#/c/602156/ I can ssh to master node easy without asking infra team about that :)16:40
slaweqif You want to debug job with some other things, You maybe will have to remove that sleep :)16:40
haleyb:)16:40
* slaweq will buy a beer for someone who will solve this issue :)16:41
* haleyb marks it critical :)16:41
mlavalleLOL16:41
slaweq:D16:42
slaweqthx haleyb for help with this one16:42
slaweqI think we can move on to next topic then16:42
slaweq#topic Grafana16:43
*** openstack changes topic to "Grafana (Meeting topic: neutron_ci)"16:43
slaweqhttp://grafana.openstack.org/dashboard/db/neutron-failure-rate16:43
njohnstongate functional looks unhappy16:43
*** dklyle has joined #openstack-meeting16:44
slaweqyes16:45
slaweqa bit16:45
mlavallenot sure, we don't know how many runs in the graph16:45
mlavalleat least I don't16:46
mlavallebut worth keeping an eye on, definitely16:46
slaweqI can't find specific examples now16:46
*** zaneb has quit IRC16:46
*** zaneb has joined #openstack-meeting16:46
slaweqbut I'm almost sure that it's again this issue with db migration tests which hits us from time to time16:46
*** annabelleB has joined #openstack-meeting16:47
slaweqok, as mlavalle said, lets keep an eye on it for now16:48
mlavalleslaweq: do you mean this bug https://bugs.launchpad.net/neutron/+bug/1687027?16:49
openstackLaunchpad bug 1687027 in neutron "test_walk_versions tests fail with "IndexError: tuple index out of range" after timeout" [High,Confirmed] - Assigned to Miguel Lavalle (minsel)16:49
slaweqmlavalle: yes16:49
mlavalleslaweq: we have a query there. I'll run it today16:49
slaweqok16:50
mlavalleand report in the bug my findings16:50
mlavallelet's see if we can correlate the spike in functional with the bug16:50
*** iyamahat has joined #openstack-meeting16:50
slaweqok16:50
*** yamahata has joined #openstack-meeting16:51
slaweqfrom other things there are only known issues like grenade dvr job failures and this migration from HA test failures in multinode dvr scenario job16:53
slaweqso basically I think we will be good if we will fix those 2 issues :)16:53
mlavallethe HA failures is what manjeets is working on, right?16:53
slaweqright16:54
mlavalleack16:54
*** tdasilva has joined #openstack-meeting16:54
slaweqok, so that's all from me for today16:55
slaweqdo You want to talk about anything else?16:55
slaweq#topic Open discussion16:55
*** openstack changes topic to "Open discussion (Meeting topic: neutron_ci)"16:55
njohnstonI pushed a change to delete the python2 fullstack job https://review.openstack.org/605126 but I was wondering if I needed to update the neutron-fullstack-with-uwsgi job that is nonvoting experimental16:55
njohnstonI also pushed an update to grafana for fullstack: https://review.openstack.org/60512816:55
slaweqhmm, we already merged support for uwsgi, right?16:55
mlavalleyes, last cycle16:56
slaweqso maybe we should do this job at least non voting but in check queue?16:56
slaweqand switch to py36 also16:56
njohnstonis uwsgi enabled by default now, or is it just a supported config?16:56
slaweqwhat You think?16:56
njohnstonnote that there are also neutron-functional-with-uwsgi and neutron-tempest-with-uwsgi jobs also in experimental16:58
* njohnston has no opinion on uwsgi jobs16:58
slaweqIMO we should promote it to check queue as nonvoting for now16:58
mlavallewe can do that16:59
haleybnjohnston: NEUTRON_DEPLOY_MOD_WSGI: True in zuul.yaml - so i'm assuming it's not default, that's tweaking some other flag16:59
slaweqok, we are out of time now16:59
slaweqthx for attending the meeting16:59
mlavalleo/16:59
njohnstonmlavalle if you agree then I'll do that and also convert them to zuulv3 syntax and add them to grafana16:59
slaweqand see You next week16:59
slaweqnjohnston++16:59
mlavallenjohnston: ok16:59
slaweq#endmeeting16:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"16:59
njohnstoncool16:59
openstackMeeting ended Tue Sep 25 16:59:54 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_ci/2018/neutron_ci.2018-09-25-16.00.html16:59
slaweqo/16:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_ci/2018/neutron_ci.2018-09-25-16.00.txt16:59
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_ci/2018/neutron_ci.2018-09-25-16.00.log.html17:00
*** mlavalle has left #openstack-meeting17:00
*** AlanClark has quit IRC17:07
*** AlanClark has joined #openstack-meeting17:09
*** diablo_rojo has joined #openstack-meeting17:12
*** priteau has quit IRC17:13
*** ralonsoh has quit IRC17:15
*** AlanClark has quit IRC17:20
*** jamesmcarthur has quit IRC17:21
*** AlanClark has joined #openstack-meeting17:21
*** AlanClark has quit IRC17:22
*** felipemonteiro has quit IRC17:28
*** njohnston has quit IRC17:31
*** njohnston has joined #openstack-meeting17:32
*** ekcs has joined #openstack-meeting17:34
*** jamesmcarthur has joined #openstack-meeting17:34
*** cloudrancher has quit IRC17:35
*** cloudrancher has joined #openstack-meeting17:36
*** jamesmcarthur has quit IRC17:46
*** tssurya has quit IRC17:51
*** annabelleB has quit IRC17:52
*** annabelleB has joined #openstack-meeting17:54
*** jamesmcarthur has joined #openstack-meeting17:55
*** Shrews has joined #openstack-meeting18:05
*** njohnston has quit IRC18:07
*** njohnston has joined #openstack-meeting18:07
*** macza has joined #openstack-meeting18:11
*** AJaeger has joined #openstack-meeting18:46
*** dustins has joined #openstack-meeting18:48
*** gouthamr has quit IRC18:52
*** dmellado has quit IRC18:53
*** raildo_ has joined #openstack-meeting18:53
*** stevebaker has quit IRC18:53
*** raildo has quit IRC18:55
*** fuentess_ has joined #openstack-meeting18:55
*** fuentess has quit IRC18:55
*** bobh_ has quit IRC18:55
*** fuentess_ has quit IRC18:56
*** bobh has joined #openstack-meeting18:56
*** fuentess has joined #openstack-meeting18:56
clarkbHello anyone here for the infra meeting?18:59
mordredo/19:00
AJaegero/19:00
fuentesso/19:00
* fungi peers up over the edge of his input prompt19:00
fungisome people, at least19:00
clarkb#startmeeting infra19:01
openstackMeeting started Tue Sep 25 19:01:01 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
ianwo/ yay, last !summer-time meeting19:01
*** bobh has quit IRC19: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
clarkbForum session submissions are due tomorrow at midnight Pacific time (I think). If you want to propose a session do so now19:01
cmurphyo/19:01
clarkb#topic Actions from last meeting19:02
*** openstack changes topic to "Actions from last meeting (Meeting topic: infra)"19:02
clarkb#link http://eavesdrop.openstack.org/meetings/infra/2018/infra.2018-09-18-19.01.txt minutes from last meeting19:02
clarkblast meeting was a little different in that I tried to use it to get PTG recap thoughts written down in some format before all that memory gets replaced19:02
*** cloudrancher has quit IRC19:02
mordredwe had a PTG?19:03
clarkbNo actions, but if you are interested in PTG happenings that is a great place to start. I think ttx is hoping there will be more emails to the dev list recapping the various happenings. I'll try to get one out this week based on what I wrote down in the meeting last week19:03
clarkbThis reminds me I will be at ansiblefest next week and likely won't be able to run the meeting19:04
clarkbif anyone is willing to volunteer as meeting chair next week let me know19:04
clarkb#topic Specs approval19:04
*** openstack changes topic to "Specs approval (Meeting topic: infra)"19:04
clarkbianw: did you have a chance to see my response on the third party ci direction spec?19:05
ianwummm, not that i remember ...19:05
*** toabctl has quit IRC19:05
clarkb#link https://review.openstack.org/#/c/563849/ third party testing direction spec19:06
ianwoh right, yeah, windmil v SF19:06
clarkbianw: summary is I think we can go with the proposal as is since windmill has some advantages over SF that make it good for general direction setting (multi platform in particular). Then reevaluate if everyone simply uses SF19:06
ianwright, i mean i've put it under help wanted, so it's going to be a situation of someone who needs this says "what do i do" and we say "here's what we'd like to help you do"19:07
clarkbyup. Given that thoughts on putting it up for approval this week?19:07
*** toabctl has joined #openstack-meeting19:07
ianwi'm fine with that, i don't have anything more to add19:07
clarkbok infra specs reviewers can you review ^ and I'll check back in on it later this week (likely friday morning local time) for approval19:08
*** cloudrancher has joined #openstack-meeting19:09
clarkb#topic Priority Efforts19:09
*** openstack changes topic to "Priority Efforts (Meeting topic: infra)"19:09
clarkb#topic Update Config Management19:09
*** openstack changes topic to "Update Config Management (Meeting topic: infra)"19:09
clarkbtopic:puppet-4 and topic:update-cfg-mgmt is the gerrit query to follow for this19:10
clarkbI need to pick up the puppet futureparser updates again. Those have been going reasonably well as our testing catching most problems before we run into them19:10
*** bobh has joined #openstack-meeting19:11
clarkbThere are a few outstanding items on the ansible/zuul/cd front though. We've got the inventory group membership improvements, triggering of ansible on bridge.openstack.org from zuul executors, and running useful playbooks in that way on the todo list I think19:11
mordredyeah19:12
clarkbmordred: re inventory group membership fixes, did you figure out the negative membership? is that change ready for review?19:12
*** gouthamr has joined #openstack-meeting19:12
mordredI need to swing back around to finish that off - and no, it is not ready for review yet19:12
clarkbok19:12
clarkb#link https://review.openstack.org/#/c/604932/2 and its parent aim to fix the ssh issues from zuul to bridge.openstack.org19:13
mordredthe negative membership is still weird ... but, it's no worse than today, so maybe we get it in shape to be faster19:13
mordredan then making disabled: a special thing can come later19:13
clarkbmordred: that seems reasonable19:13
corvuswfm19:13
clarkbfor 604932 that should probably get careful review from people that understand ansible better than I do :)19:14
clarkbthe basic idea there is we want to manage multiple dynamic ssh keys (so they can be rotated) in the zuul user's authorized keys file so that zuul jobs can ssh into the bastion and run playbooks for CD stuff19:14
*** ssbarnea|bkp has joined #openstack-meeting19:14
clarkbI've written a small ansible module in python to handle the logic around generating the authorized_keys content for that19:15
*** bobh has quit IRC19:15
clarkbonce that gets in we can start writing job that run playbooks that hopefully do interesting things :)19:16
corvus++19:16
clarkbcorvus: any thoughts on the getting to where we can decouple a useful unit of work from the puppet?19:16
corvusclarkb: our last thoughts at the ptg were that in order to do the scheduler reload we were thinking of, we'd need to port a bunch of puppet to ansible first.  it's probably a few days of work, and i think needs to be done anyway.  we can proceed with that, or if someone has another idea of something smaller to test out first, we could try that first.19:18
corvusthough, in the mean time, i'd be happy with a working "debug: msg='hello world'" playbook :)19:18
clarkbok I'll have to keep my eyes out for useful units of work19:18
clarkbcorvus: ++19:18
*** Leo_m has quit IRC19:18
clarkbif anyone else has suggestions ^ let us know or push a change to run that playbook instead of the current hello world playbook19:19
*** Leo_m has joined #openstack-meeting19:19
clarkbAny other config management update changes/topics worth calling out?19:19
* cmurphy nope19:20
clarkb#topic Storyboard19:20
*** openstack changes topic to "Storyboard (Meeting topic: infra)"19:20
clarkbI wasn't able to join the storyboard room in denver19:20
clarkbdiablo_rojo: did send out a PTG recap though19:21
* clarkb finds a link to that19:21
clarkb#link http://lists.openstack.org/pipermail/openstack-dev/2018-September/134923.html Storyboard PTG recap19:21
clarkbthank you for putting that together diablo_rojo19:21
clarkbdiablo_rojo: SotK fungi anything worht calling out on ^ or new news since that was sent?19:22
*** gabyc_ has joined #openstack-meeting19:22
fungii'm currently working on the task footer linking configuration for the its-storyboard gerrit plugin, diablo_rojo is working through test imports of oslo and neutron19:22
diablo_rojoI'm running a Neutron migration (don't expect it to finish for a week or so)19:23
fungithere's yet another resurgence of the bucket-priority discussion on the -dev ml19:23
diablo_rojoAlso investigating the discrepancy in numbers of oslo bugs in lp vs sb19:23
clarkbdiablo_rojo: neutron is migrating soon then?19:25
diablo_rojoclarkb, they are interested19:25
diablo_rojothey wanted to see what it would look like in dev first19:25
clarkbgotcha19:26
clarkbI think one of the big items of interest to the infra team is the work around file attachments to stories19:26
clarkbdiablo_rojo: fungi when the spec gets written we should try to get as many eyebalsl on that as possible19:27
diablo_rojoAgreed.19:27
diablo_rojoAfter I figure out this oslo bugs mismatch I think thats the next thing on my todo list19:27
clarkbgreat19:27
clarkbanything else before we go to the next topic19:28
clarkb#topic General Topics19:29
*** openstack changes topic to "General Topics (Meeting topic: infra)"19:29
clarkbfuentess: hello, still hanging out?19:29
fuentessclarkb, hi19:29
*** jamesmcarthur has quit IRC19:29
ssbarneai do also have a subject i want to propose19:30
clarkbssbarnea: ok, I expect we'll have time19:30
clarkbeveryone meet fuentess. fuentess works on kata things and has helped with my work of getting a zuul job running against kata19:30
fuentesshello everyone, first meeting here19:30
clarkbI think we got the general thing working, but there are some rough edges (mnaser doesn't seem to be around to talk about the one related to the new vexxhost region)19:31
fuentesswe also have gabyc_, which also helps on the kata CI19:31
mnasero/19:31
clarkboh there is mnaser19:31
* mordred waves to fuentess and gabyc_19:31
mordredand to mnaser19:31
fuentessclarkb, ok, for that, I was thinking that as a short term solution, we can modify our job to run with another storage driver, instead of using devicemapper19:31
clarkba quick recap (at least as I understand things and fuentess can fill in where I miss details or am just wrong):19:32
*** electrofelix has quit IRC19:32
clarkbwe have got a generalized kata functional job running that compiles the kata components then tests them with various test suites and with docker, crio, k8s (and probably other things I don't even know about)19:32
mnaserkata has a custom flavor in the montreal region, which we added ephemeral storage to get /dev/vdb (and nested virt).  because we have nested virt in all of sjc1, i defaulted to the 'normal' flavor.. but that doesn't have /dev/vdb in it because we don't provide it by default.. and thats the differences19:32
mnaseri'll let clarkb continue and comment if/when necessary :)19:33
clarkbkata requires nested virt for these tests because kata relies on kvm to run the vm containers19:33
clarkbdue to this we set up jobs only in vexxhost since vexxhost was already running their jenkins jobs (meant we didn't have to spend so much time debugging nested virt)19:33
fuentessmnaser, do you think that in the future, it would be easy to add those ephemeral volumes?19:33
clarkbI think this is stable in the montreal region, but is resource constrained (special host aggregate there to run the kata tests)19:34
clarkbin the sjc1 region this aggregate and special flavor don't exist because the entire region supports nested virt19:34
clarkbbut that exposed that the tests currently rely on the special flavor to provide a /dev/vdb disk device in the montreal region19:35
mnasermaybe it could be a zuul feature to attach an extra empty volume as part of a node definition :)19:35
mnaserbut then im signing up people for work :-P19:35
clarkbfuentess: I think the tests are still running against the proxy repo but you have disabled the app on the other repo?19:35
fuentessmnaser, clarkb: we used to use loopback devices, but we had some stability issues with cri-o, so we moved to use a block device19:35
fuentessclarkb, right, we had it in the runtime repo, but removed it for the moment19:36
fungihaving nodepool create, attach, track and delete volumes is probably a nodepool design discussion19:36
clarkbok I think that covers the current setup. I think fuentess and I and probably others are looking to see if we can figure out how to move forward19:36
clarkband get back to running reliable jobs for them19:36
funginodepool's focus at the moment is around managing pools of compute instances, though there has been discussion among the nodepool maintainers of turning it into a more generic thingpool manager19:37
clarkbya I think we should decouple having nodepool manage those resources from this effort. We've talked about adding other resource tracking but its not the current dev priority for anyone that I know of19:37
mnaseryeah.. also, i feel like it makes it easier for users to run tests locally if a device is not required (imho)19:38
ianwhrmmm, i'm hesitant to suggest it but DIB has LVM support ... you could create an image with volumes if that's really what's required19:38
corvusin openstack, we've use loopback for this... but that doesn't work?19:38
clarkband I think it would represent significant work in nodepool (so not a quick solution)19:38
fuentessclarkb, yes, it would be great if we can have the jobs running successfully. So if currently nodepool cannot handle these requests, I can patch my tests to use another storage-driver when running on zuul19:38
clarkbcorvus: ya that was my suggestion. We use it for swift and cinder to great effect19:38
clarkbfuentess: what is the difference between the storage drivers?19:39
fuentesscorvus, we have tried with loopback, but seems like cri-o has some stability issues when using them19:39
fuentessclarkb, well, cri-o and docker support different storage drivers, the others are overlay and btrfs, which do not require block devices19:39
fuentessso I think that we could use overlay, which is the default of cri-o19:40
clarkbgot it. We wouldn't get test coverage of support for that specific driver, but get coverage of the general api stuff?19:40
clarkbfuentess: that seems reasonable if it is their default19:40
fuentessright, we still have tests running on devicemapper in jenkins jobs19:40
fungipretty sure it's also possible to feed lvm2 a loopback block device as a pvm and create volumes in there19:40
* fungi tries19:41
clarkbfungi: that is what cinder tests do19:41
fungiahh, saves me trying ;)19:41
fuentessfungi, clarkb: ohh, that could also handle our case, although not sure if the stability issues would come back19:41
fungiso anyway, wouldn't necessarily have to point cri-o at a raw loopback device, could still hand it lvm2 volumes or a vg19:41
*** e0ne has joined #openstack-meeting19:41
clarkbfuentess: assuming one of those options gets us back to reliable testing. How do you see the next steps from there going? Add the job back to the runtime repo, then if stable run it more globally?19:42
fungiusually when we've seen stability issues it's been due to sparse backing/thin provisioning19:42
clarkbfuentess: my other concern was with the on demand rather than continuous testing, is it a problem if zuul continues to do continuous testing?19:42
fuentessright, now if we make this work on the proxy repository, we could enable the jobs on the other repos19:43
fuentessclarkb, right now I dont think it is a problem19:43
*** erlon has quit IRC19:43
fuentessmaybe in the future, we would like to change it to on-demand19:43
fuentessis this possible for zuul?19:43
clarkbok good, configuring things to handle the on demand stuff is probably out of scope for what I'd be interested in :) it is possible with zuul but we would have to add kata specific pipelines19:44
clarkband I think we'd like to see kata drive more of that itself if that was the need/interest19:44
*** bobh has joined #openstack-meeting19:44
fungiopenstack currently has an on-demand independent zuul pipeline it calls "experimental"19:44
clarkb(happy to help, but I won't be able to debug github's esoteric behavior when it doesnt' work right)19:44
fuentessclarkb, ok, cool, I think it would be great as a next step, once everything is stable19:44
fungipresumably something similar would be possible with a gh-triggered pipeline19:44
clarkbfungi: ya should be possible, but getting all the little details right with github api is likely to be a learning experience :)19:45
fungiagreed. those of us who eschew github have the privilege of not concerning ourselves with its proprietary api behaviors19:45
clarkbok I think that gives us a bit of a path forward. The other thing I'll mention is that most of the infra team don't subscribe to the kata ci (and other repo) issues on github19:46
clarkbfuentess: if there are issues or concerns (particularly if urgent) it would be helpful to reach out directly to the team to get eyes on things. #openstack-infra or the openstack-infra mailing list are probably the best places for that today19:46
fungiopenstack-infra@lists.openstack.org is the mailing list (in case that wasn't clear)19:46
fuentessclarkb, ok, good to know, I didnt know this until last week, hehe19:47
fuentessthanks for the infio19:47
clarkbalright anything else? if not I'll give the floor to ssbarnea19:47
fuentessI think thats it, lets move on19:47
corvusfuentess: thanks!19:47
fuentessthanks everyone for your comments19:47
ssbarneai would like to propose changing the ansible output callback used by zuul from"default" to a more human readable one, either "yaml" or "debug" ones (debug used to be called human_log). We already have a wip change to do this on tripleo. initial attempt to change to yaml didn't work very well because this callback was introduced only in ansible 2.5, but debug one which is similar was introduced in ~2.2.19:47
ssbarneafor those that do not know the differences, it may help to have a look at https://sbarnea.com/f/ansible-output/19:48
ssbarneaclick on "default", "debug" and "yaml" to see how they differ.19:48
fungiwe're using ansible 2.5 on the zuul.openstack.org executors currently, right?19:48
corvusssbarnea: what's the use case?19:48
ssbarneamainly is about *not* displaying stdout/err as JSON19:48
fungithe text console logfile doesn't serve that purpose?19:49
clarkbfungi: you still get the json output in the console logfile when there are errors iirc19:49
fungiahh19:49
ssbarneadefault callback displays the stdout, stderr, (and ther splitted version) in a way that makes it very user unfriendly, especially for commands that return more than a couple of lines.19:49
ssbarneamaybe my example does not contian enough lines to make the difference obvious19:50
clarkbya I agree that the yaml is a bit more readable19:50
corvusssbarnea: we (zuul) have discussed using the json output that we save to render a console log which is more readable but also can have functionality like expanding/contracting plays/tasks/etc.19:51
corvusssbarnea: would that serve your purpose?19:51
ssbarneacorvus: not really because a fix can be achieved with one line, and you are talking about a complex feature which needs to developed, tested.....19:52
corvus(we still need a streaming console output which would probably be similar to what we have now, but that doesn't have to be the same thing that shows up in the archived logs)19:52
ssbarneaand colapsable output is not something you ship after a weekend of writing it.19:52
corvusssbarnea: wait, you're saying it won't satisfy your use-case because it will be hard to do?19:52
ssbarneais what we can do now, vs what we could do in the future (as in long term).19:53
clarkbI think ssbarnea is pointing out that its a minor change to make that would make the situation better today (anddoesn't conflict with the harder but maybe overal better UX work)19:53
ssbarneai am not against the colapsable feature, but I am also realistic. if I can sort something today, i do.19:53
corvusi think it's fine to point that out.  i would, however, appreciate a straight answer to my question since i'm trying rather hard to understand the request.19:54
ssbarneaclarkb: well pointed.19:54
clarkbmaybe this discussion would be a good one to have in #zuul or on the zuul mailing list? we have a few minutes left in our hour. I'd like to make sure we don't ignore any other pressing concerns19:55
clarkb#topic Open Discussion19:56
*** openstack changes topic to "Open Discussion (Meeting topic: infra)"19:56
*** dustins has quit IRC19:56
ssbarneain few minutes I can update the examples to make it easier to spot the difference in output19:56
corvusssbarnea: that would be helpful.  also, answering my question would be helpful.19:56
clarkbcorvus: I spoke quickly with the foundation last week about drafting the opendev message and they agreed that it made sense to figure that out. I'll try to get a discussion going in some venue now that we are all back from travel and vacation19:56
clarkbianw: gary_perkins: anything we can do to help with the new arm cloud work?19:57
*** dustins has joined #openstack-meeting19:57
*** cloudrancher has quit IRC19:58
ianwclarkb: i have outstanding queries to gary_perkins ATM ...19:58
fungii think the branding discussion we had in irc at the beginning of the name selection process worked well. something along those lines again seems reasonable19:58
*** cloudrancher has joined #openstack-meeting19:59
clarkbalright we are basically at time. as mentioned before find us ing #openstack-infra or at openstack-infra@lists.openstack.org for further discussion19:59
clarkbThank you everyone!19:59
clarkb#endmeeting19:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"19:59
openstackMeeting ended Tue Sep 25 19:59:53 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/infra/2018/infra.2018-09-25-19.01.html19:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/infra/2018/infra.2018-09-25-19.01.txt19:59
openstackLog:            http://eavesdrop.openstack.org/meetings/infra/2018/infra.2018-09-25-19.01.log.html19:59
*** AJaeger has left #openstack-meeting20:00
*** Shrews has left #openstack-meeting20:00
*** gouthamr_ has joined #openstack-meeting20:05
*** e0ne has quit IRC20:05
*** gabyc_ has quit IRC20:06
*** dmellado has joined #openstack-meeting20:07
*** janki has joined #openstack-meeting20:12
*** cloudrancher has quit IRC20:17
*** cloudrancher has joined #openstack-meeting20:17
*** e0ne has joined #openstack-meeting20:19
*** annabelleB has quit IRC20:28
*** gouthamr has quit IRC20:38
*** gouthamr_ is now known as gouthamr20:39
*** pcaruana has quit IRC20:43
*** e0ne has quit IRC20:43
*** annabelleB has joined #openstack-meeting20:48
*** awaugama has quit IRC20:50
slaweqclarkb: hi20:50
slaweqclarkb: I today did patch with new role for neutron-tempest-plugin: https://review.openstack.org/#/c/578796/2820:51
slaweqbut it looks for me that this new role wasn't run in my job neutron-tempest-plugin-dvr-multinode-scenario-zuulv320:51
slaweqclarkb: can You maybe take a look at it and help me to find what I missed?20:51
*** ttsiouts has joined #openstack-meeting20:53
clarkbslaweq: where is the change that adds the new job?20:54
slaweqclarkb: https://review.openstack.org/#/c/578796/20:54
slaweqit's this one20:54
slaweqand it also adds new role20:55
clarkbslaweq: I think that there may be a name colision with multi-node-setup role name?20:55
* clarkb double checks20:55
clarkbmaybe not20:56
clarkboh I see, the roles list in the job configuration is a list of repository locations of where to find roles20:57
clarkbthe roles in the same git repo are implied. To use the role you need to invoke it from one of your playbooks20:57
clarkbslaweq: you may need to add a pre playbook to executore that role20:57
clarkbthen set that playbook at the pre-run on that job20:57
slaweqclarkb: ok, I understand20:58
slaweqclarkb: thx again for quick help :)20:58
slaweqclarkb: such pre-run playbook will be run after devstack roles are run?20:58
slaweqso I can assume that this br-infra bridge is already created and e.g. openvswitch is installed or it's not sure?20:59
clarkbslaweq: ya the parent's  pre-run runs first20:59
slaweqok, thx a lot20:59
*** fuentess has quit IRC21:01
*** cloudrancher has quit IRC21:02
*** fuentess has joined #openstack-meeting21:02
*** cloudrancher has joined #openstack-meeting21:02
*** Qiming has quit IRC21:05
*** Qiming has joined #openstack-meeting21:06
*** cloudrancher has quit IRC21:07
*** janki has quit IRC21:08
*** stevebaker has joined #openstack-meeting21:12
*** dustins has quit IRC21:14
*** fuentess has quit IRC21:17
*** raildo_ has quit IRC21:17
*** awaugama has joined #openstack-meeting21:19
*** awaugama has quit IRC21:24
*** slaweq has quit IRC21:27
*** slaweq has joined #openstack-meeting21:27
*** bobh has quit IRC21:31
*** Qiming has quit IRC21:40
*** awaugama has joined #openstack-meeting21:42
*** Qiming has joined #openstack-meeting21:43
*** cloudrancher has joined #openstack-meeting21:50
*** cloudrancher has quit IRC21:55
*** munimeha1 has quit IRC22:03
*** ttsiouts has quit IRC22:05
*** ttsiouts has joined #openstack-meeting22:06
*** mriedem has quit IRC22:10
*** ttsiouts has quit IRC22:10
*** bobh has joined #openstack-meeting22:23
*** Qiming has quit IRC22:23
*** jamesmcarthur has joined #openstack-meeting22:23
*** Qiming has joined #openstack-meeting22:26
*** Qiming has quit IRC22:33
*** Qiming has joined #openstack-meeting22:42
*** Leo_m has quit IRC22:43
*** dklyle has quit IRC22:48
*** tpsilva has quit IRC22:52
*** awaugama has quit IRC22:59
*** felipemonteiro has joined #openstack-meeting23:03
*** ykatabam has joined #openstack-meeting23:05
*** rcernin has joined #openstack-meeting23:07
*** bobh has quit IRC23:08
*** jamesmcarthur has quit IRC23:10
*** rbudden has quit IRC23:13
*** macza has quit IRC23:17
*** macza has joined #openstack-meeting23:17
*** jaypipes has quit IRC23:21
*** macza has quit IRC23:22
*** erlon has joined #openstack-meeting23:27
*** hongbin has quit IRC23:27
*** felipemonteiro has quit IRC23:41
*** mjturek has quit IRC23:42

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