Wednesday, 2019-03-13

*** Qiming has joined #openstack-meeting00:04
*** mattw4 has quit IRC00:05
*** Qiming has quit IRC00:08
*** jamesmcarthur has quit IRC00:10
*** Qiming has joined #openstack-meeting00:11
*** slaweq has joined #openstack-meeting00:11
*** enriquetaso has joined #openstack-meeting00:13
*** jamesmcarthur has joined #openstack-meeting00:14
*** enriquetaso has quit IRC00:20
*** Qiming has quit IRC00:22
*** Qiming has joined #openstack-meeting00:23
*** slaweq has quit IRC00:24
*** jamesmcarthur has quit IRC00:27
*** gyee has quit IRC00:30
*** number80 has quit IRC00:38
*** lbragstad has quit IRC00:40
*** hyunsikyang has quit IRC00:43
*** markvoelker has joined #openstack-meeting00:43
*** hyunsikyang has joined #openstack-meeting00:43
*** JangwonLee_ has joined #openstack-meeting00:43
*** tetsuro has joined #openstack-meeting00:44
*** JangwonLee has quit IRC00:46
*** cheng1 has joined #openstack-meeting00:48
*** whoami-rajat has joined #openstack-meeting00:51
*** rbudden has quit IRC00:53
*** zhubx has quit IRC00:58
*** zhubx has joined #openstack-meeting00:58
*** jiaopengju has joined #openstack-meeting00:58
*** number80 has joined #openstack-meeting01:02
*** liuyulong has joined #openstack-meeting01:03
*** armax has joined #openstack-meeting01:11
*** slaweq has joined #openstack-meeting01:11
*** markvoelker has quit IRC01:21
*** jamesmcarthur has joined #openstack-meeting01:23
*** slaweq has quit IRC01:24
*** Nel1x has joined #openstack-meeting01:25
*** zbr has quit IRC01:34
*** rbudden has joined #openstack-meeting01:38
*** lbragstad has joined #openstack-meeting01:44
*** tetsuro has quit IRC01:47
*** jamesmcarthur has quit IRC02:22
*** jamesmcarthur has joined #openstack-meeting02:23
*** lbragstad has quit IRC02:24
*** slaweq has joined #openstack-meeting02:26
*** slaweq has quit IRC02:39
*** cheng1_ has joined #openstack-meeting02:43
*** cheng1 has quit IRC02:46
*** iyamahat_ has quit IRC02:50
*** yamahata has quit IRC02:50
*** jamesmcarthur has quit IRC02:53
*** jamesmcarthur has joined #openstack-meeting02:53
*** yamamoto has quit IRC02:55
*** yamamoto has joined #openstack-meeting02:55
*** yamamoto has quit IRC02:56
*** psachin has joined #openstack-meeting03:03
*** Nel1x has quit IRC03:05
*** yamamoto has joined #openstack-meeting03:08
*** yamamoto has quit IRC03:09
*** yamamoto has joined #openstack-meeting03:10
*** slaweq has joined #openstack-meeting03:12
*** yamamoto has quit IRC03:15
*** apetrich has quit IRC03:16
*** roman_g has quit IRC03:20
*** slaweq has quit IRC03:24
*** diablo_rojo has quit IRC03:26
*** jamesmcarthur has quit IRC03:27
*** armax has quit IRC03:41
*** imsurit_ofc has joined #openstack-meeting03:53
*** cheng1_ has quit IRC04:07
*** slaweq has joined #openstack-meeting04:11
*** rfolco|ruck has quit IRC04:17
*** slaweq has quit IRC04:24
*** rfolco has joined #openstack-meeting04:24
*** rbudden has quit IRC04:27
*** rfolco has quit IRC04:30
*** rfolco has joined #openstack-meeting04:30
*** zhubx has quit IRC04:34
*** zhubx has joined #openstack-meeting04:35
*** zhubx has quit IRC04:36
*** zhubx has joined #openstack-meeting04:36
*** zhubx has quit IRC04:37
*** zhubx has joined #openstack-meeting04:38
*** zhubx has quit IRC04:44
*** zhubx has joined #openstack-meeting04:45
*** mahatic has joined #openstack-meeting04:45
*** cheng1 has joined #openstack-meeting05:03
*** janki has joined #openstack-meeting05:04
*** cheng1 has quit IRC05:07
*** slaweq has joined #openstack-meeting05:11
*** slaweq has quit IRC05:24
*** sridharg has joined #openstack-meeting05:27
*** igordc has quit IRC05:30
*** iyamahat has joined #openstack-meeting05:38
*** liuyulong has quit IRC05:41
*** zhubx has quit IRC05:43
*** zhubx has joined #openstack-meeting05:44
*** markvoelker has joined #openstack-meeting05:47
*** slaweq has joined #openstack-meeting06:11
*** yamahata has joined #openstack-meeting06:13
*** pcaruana has joined #openstack-meeting06:19
*** slaweq has quit IRC06:24
*** slaweq has joined #openstack-meeting06:26
*** slaweq has quit IRC06:36
*** e0ne has joined #openstack-meeting06:40
*** Luzi has joined #openstack-meeting06:48
*** diablo_rojo has joined #openstack-meeting06:52
*** imsurit_ofc1 has joined #openstack-meeting06:58
*** imsurit_ofc has quit IRC06:58
*** imsurit_ofc1 is now known as imsurit_ofc07:00
diablo_rojo#startmeeting fc_sig07:03
openstackMeeting started Wed Mar 13 07:03:47 2019 UTC and is due to finish in 60 minutes.  The chair is diablo_rojo. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.07:03
*** openstack changes topic to " (Meeting topic: fc_sig)"07:03
openstackThe meeting name has been set to 'fc_sig'07:03
diablo_rojo#link Agenda that I forgot to update07:04
diablo_rojo#New Contributor patches07:04
diablo_rojo#topic New Contributor Patches07:04
*** openstack changes topic to "New Contributor Patches (Meeting topic: fc_sig)"07:04
tonyb<- didn't do homework07:05
* diablo_rojo looks around to see if anyone else did07:05
* mattoliverau just looked.. does that count? :P07:05
diablo_rojomattoliverau, Sure!07:05
mattoliverauTho there was a swift one a few days ago, but it's already landed :)07:06
diablo_rojoWell thats good news :)07:06
diablo_rojoIts nice when new contributor patches get that quick attention07:07
*** kopecmartin|off is now known as kopecmartin07:07
mattoliverauYeah, hopefully it'll help engage them, even is it was just a too fix07:07
diablo_rojoGotta start somewhere.07:08
diablo_rojoAnything else on this topic?07:09
tonybNot from me07:09
diablo_rojo#topic Ask.o.o07:10
*** openstack changes topic to "Ask.o.o (Meeting topic: fc_sig)"07:10
mattoliverauThere's a lot of stackylitics ones so capturing their second patches will be harder.07:10
diablo_rojoI actually did what I volunteered :)07:11
diablo_rojoI wrote two more anonymous questions07:11
tonybmattoliverau: Hmmm that sounds like a challenge ;P07:11
mattoliveraudiablo_rojo: nice, I just saw em, I think. Mentoring was on right?07:12
*** slaweq has joined #openstack-meeting07:12
diablo_rojoI think so?07:12
diablo_rojoLol it was like two weeks ago that I wrote them.07:12
tonybhmm ask.o.o is down ... oh backup o'clock07:12
mattoliverauReally lol, maybe not a great time for our meeting then :p07:13
diablo_rojoLuckily it will be moving07:13
mattoliverauWe should make sure they're answered correctly then07:14
mattoliverauRe: seeded questions07:15
diablo_rojoYes we should :)07:15
diablo_rojoI can go back and upvote answers that I like07:15
mattoliverauSorry trying to type on a phone with a 6 month old in my arms. /Me needs an extra one07:15
mattoliverauarm that is07:16
tonybq mattoliverau Glad you didn't mean 6mo ;P07:16
diablo_rojomattoliverau, this is what voice to text is for07:17
diablo_rojoAnything else on this topic?07:17
mattoliverauTrue.. but you might get baby babble07:17
tonybcan you imagine what a mess talk-to-text would make ;P07:18
diablo_rojo#topic Sandbox bot07:20
*** openstack changes topic to "Sandbox bot (Meeting topic: fc_sig)"07:20
diablo_rojotonyb, any updates?07:20
*** tonyb is now known as tonyb_gone07:20
diablo_rojoHa ha ha07:21
*** tonyb_gone is now known as tonyb07:21
tonybNo I swear I'll send the update to the list tomorrow07:21
diablo_rojo#action tonyb will update the openstack-discuss list with progress tomorrow07:22
diablo_rojoIts written in stone now.07:22
mattoliverauSorry tonyb I've been meaning to play with it, but somehow my days fly by and keep forgetting.07:22
tonybmattoliverau: It's all good07:22
diablo_rojoNothing else here then?07:22
*** jrbalderrama has joined #openstack-meeting07:23
mattoliverauSeems like we need a group action item to do our homework :p07:23
diablo_rojo#action Everyone should do their homework07:24
tonybmattoliverau: be careful or we'll end up with a hoemwork bot ;P07:24
diablo_rojoThere mattoliverau :)07:24
diablo_rojoHa ha ha that would be interesting.07:24
diablo_rojo#topic Summit + Forum Planning07:24
*** openstack changes topic to "Summit + Forum Planning (Meeting topic: fc_sig)"07:24
*** slaweq has quit IRC07:24
diablo_rojoSo I submitted one Forum session to talk about the deduplication of efforts around onboarding/mentoring/etc07:25
diablo_rojoHopefully it gets put on the schedule after the help wanted list forum session07:25
diablo_rojoI also requested a BoF to be a hangout meet and greet thing like we did last time.07:25
tonybwith switch support ;P07:26
diablo_rojomattoliverau, also had a presentation he submitted to the cfp, did that get accepted?07:26
diablo_rojotonyb, yes I will probably have the switch07:26
mattoliverauNope :(07:26
diablo_rojomattoliverau, dang :/07:27
diablo_rojoBut you did get permission to go and everything right?07:27
diablo_rojoOtherwise you can take for forum session moderation ;)07:27
mattoliverauYeah, I'll be there.07:29
mattoliverauShane tho it wouldve made even a good lightning talk07:30
diablo_rojoIf I end up hearing about openings for lightning talks I will let them know you are still interested07:30
*** e0ne has quit IRC07:31
diablo_rojoAnything else anyone wants to chat about wrt to this huge event bearing down on us?07:32
tonybThe doodle poll07:33
mattoliverauNo, I figure we can do a lot in the hallway track. And I plan to create some onboardings07:33
mattoliverau* crash07:33
tonybmostly for gmann when he reads the logs07:33
diablo_rojotonyb, oh yeah for the new meeting time07:34
diablo_rojothanks :)07:34
diablo_rojoNothing else on this topic though?07:34
diablo_rojoI dont have anything for the next two topics on the list..07:34
tonybdiablo_rojo: No, for the SYNC call which is really a #tangent07:34
diablo_rojoNor the last one actually.07:34
*** slaweq has joined #openstack-meeting07:34
* diablo_rojo didnt read enough of the words on the page07:35
tonybsomehow in my brain that that was more related :/07:35
* tonyb blames the run07:36
diablo_rojoHa ha ha no worries.07:36
diablo_rojo#topic People to Reach out to07:38
*** openstack changes topic to "People to Reach out to (Meeting topic: fc_sig)"07:38
diablo_rojoSo...definitely didnt do anything here07:38
* diablo_rojo looks at old meeting logs for actions07:38
diablo_rojoNo actions for this section07:39
diablo_rojoMaybe we should write some?07:40
mattoliverauShould we attempt to reach out at summit?07:41
mattoliverauIf companies are there?07:41
diablo_rojoOh that would be cool.07:42
diablo_rojoI suppose I could stalk the eventbrite and see who will be there/if any of them will be there07:42
cmurphymaybe reach out to these people directly to ask if they will be at the summit and invite them to the bof?07:43
tonybYeah I like that idea07:43
cmurphyi kind of assume these people may not get sent to the summit or won't know about fc events07:43
diablo_rojoI can check reg to see if any are there and can reach out to the ones that will be (if any)07:44
diablo_rojo#action Check reg for contributors from the 'people to reach out to' list and invite them to fc sig BOF07:45
diablo_rojoAnything else on this topic?07:47
diablo_rojo#topic Open Discussion07:48
*** openstack changes topic to "Open Discussion (Meeting topic: fc_sig)"07:48
mattoliverauI'm good07:48
*** apetrich has joined #openstack-meeting07:50
diablo_rojoEveryone got their flights + hotels booked?07:50
*** e0ne has joined #openstack-meeting07:51
* tonyb does!07:51
* tonyb may have been the first?07:51
* cmurphy still needs to book flight07:52
diablo_rojoI have flight booked and probably a hotel? I don't handle that for summits/ptgs. I just go where told.07:52
diablo_rojocmurphy, lol07:52
diablo_rojocmurphy, you got the hotel though?07:52
tonybcmurphy: do you have a city of origin? ;P07:52
cmurphytonyb: that's why i'm delaying :P07:52
tonybcmurphy: LOL07:52
mattoliverauI've got both.. kinda. I should have flights by tomorrow, and registered at the summit hotel. I arrive on Friday07:53
cmurphyat least it won't be a trans-oceanic flight so i'm not worried about it07:53
diablo_rojomattoliverau, what time do you arrive?07:54
tonybcmurphy: Oh that does make things less stressful07:54
mattoliverauNo idea :p arvo? I'd need to check.. long flight so I don't really pay that much attention to arrival :p07:55
diablo_rojomattoliverau, perhaps we could do dinner Friday night and you could meet my sister IRL.07:57
mattoliverauOnly if tonyb joins us :)07:58
* tonyb is in!07:58
diablo_rojoAnything else important in our last two min?07:58
diablo_rojoAwesome :)07:59
* tonyb kinda assumed it was an open invitation ;P07:59
mattoliverauWell agreed to do dinner then, and I wasn't going to Pike on you tonyb  ;)07:59
mattoliverauAnd I'd love to meet up with diablo_rojo (an cmurphy but she's not coming until later).08:00
cmurphyi might be in on friday08:00
cmurphyjust not openstacking until sunday08:00
mattoliverauAhh kk08:01
diablo_rojoTimes up!08:02
*** openstack changes topic to "OpenStack Meetings ||"08:02
openstackMeeting ended Wed Mar 13 08:02:10 2019 UTC.  Information about MeetBot at . (v 0.1.4)08:02
cmurphythanks diablo_rojo08:02
openstackMinutes (text):
*** tssurya has joined #openstack-meeting08:02
diablo_rojothanks everyone for attending!08:02
mattoliverauYeah thanks diablo_rojo08:02
*** lennyb has joined #openstack-meeting08:06
*** ralonsoh has joined #openstack-meeting08:09
*** rcernin has quit IRC08:09
*** zhubx has quit IRC08:17
*** zhubx has joined #openstack-meeting08:17
*** yamamoto has joined #openstack-meeting08:19
*** electrofelix has joined #openstack-meeting08:19
*** Liang__ has joined #openstack-meeting08:21
*** zhubx has quit IRC08:21
*** Liang__ is now known as LiangFang08:22
*** zhubx has joined #openstack-meeting08:23
*** yamamoto has quit IRC08:23
*** zhubx has quit IRC08:23
*** zhubx has joined #openstack-meeting08:23
*** zhubx has quit IRC08:25
*** rubasov has left #openstack-meeting08:26
*** zhubx has joined #openstack-meeting08:26
*** e0ne has quit IRC08:36
*** a-pugachev has joined #openstack-meeting08:37
*** cheng1 has joined #openstack-meeting08:40
*** roman_g has joined #openstack-meeting08:43
*** ttsiouts has joined #openstack-meeting08:53
*** zbr has joined #openstack-meeting09:05
*** dmacpher has joined #openstack-meeting09:05
*** ttsiouts has quit IRC09:06
*** ttsiouts has joined #openstack-meeting09:07
*** ttsiouts has quit IRC09:11
*** kukacz has quit IRC09:15
*** a-pugachev_ has joined #openstack-meeting09:16
*** kukacz has joined #openstack-meeting09:17
*** a-pugachev has quit IRC09:19
*** a-pugachev_ is now known as a-pugachev09:19
*** a-pugachev has quit IRC09:20
*** a-pugachev has joined #openstack-meeting09:21
*** ttsiouts has joined #openstack-meeting09:26
*** yamamoto has joined #openstack-meeting09:27
*** rfolco is now known as rfolco|ruck09:32
*** jrbalderrama has quit IRC09:48
*** hyunsikyang has quit IRC10:01
*** rbudden has joined #openstack-meeting10:01
*** rbudden has quit IRC10:02
*** diablo_rojo has quit IRC10:11
*** zhubx has quit IRC10:19
*** zhubx has joined #openstack-meeting10:20
*** yamamoto has quit IRC10:30
*** carlos_silva has joined #openstack-meeting10:38
*** priteau has joined #openstack-meeting10:45
*** verdurin has joined #openstack-meeting11:02
*** verdurin has left #openstack-meeting11:02
*** rossella_s has quit IRC11:06
*** yamamoto has joined #openstack-meeting11:06
*** rossella_s has joined #openstack-meeting11:08
*** yamamoto has quit IRC11:13
*** yamamoto has joined #openstack-meeting11:18
*** cheng1 has quit IRC11:23
*** mriedem has joined #openstack-meeting11:26
*** hyunsikyang has joined #openstack-meeting11:26
*** belmoreira has quit IRC11:31
*** belmoreira has joined #openstack-meeting11:32
*** yaawang has quit IRC11:33
*** e0ne has joined #openstack-meeting11:36
*** raildo has joined #openstack-meeting11:37
*** imsurit_ofc has quit IRC11:41
*** yaawang has joined #openstack-meeting11:42
*** ttsiouts has quit IRC12:06
*** ttsiouts has joined #openstack-meeting12:06
*** zhubx has quit IRC12:07
*** ttsiouts has quit IRC12:11
*** markvoelker has quit IRC12:12
*** markvoelker has joined #openstack-meeting12:13
*** ttsiouts has joined #openstack-meeting12:28
*** janki has quit IRC12:34
*** a-pugachev has quit IRC12:45
*** jamesmcarthur has joined #openstack-meeting12:47
*** rbudden has joined #openstack-meeting12:54
*** janki has joined #openstack-meeting12:58
*** e0ne has quit IRC13:05
*** haleyb has left #openstack-meeting13:24
*** haleyb has joined #openstack-meeting13:24
*** priteau has quit IRC13:27
*** lbragstad has joined #openstack-meeting13:31
*** mjturek has joined #openstack-meeting13:33
*** eharney has joined #openstack-meeting13:37
*** jamesmcarthur has quit IRC13:41
*** zhubx has joined #openstack-meeting13:43
*** zhubx has quit IRC13:48
*** yamamoto has quit IRC13:50
*** yamamoto has joined #openstack-meeting13:52
*** yamamoto has quit IRC13:54
*** awaugama has joined #openstack-meeting13:56
*** davidsha has joined #openstack-meeting13:56
*** jamesmcarthur has joined #openstack-meeting14:00
*** jamesmcarthur has quit IRC14:00
*** jamesmcarthur has joined #openstack-meeting14:01
haleybhi, wondering if i messed-up the l3 meeting time with our time change here14:03
*** mlavalle has joined #openstack-meeting14:04
davidshaIt's meant to be now right?14:04
mlavalle#startmeeting neutron_l314:04
openstackMeeting started Wed Mar 13 14:04:10 2019 UTC and is due to finish in 60 minutes.  The chair is mlavalle. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:04
*** openstack changes topic to " (Meeting topic: neutron_l3)"14:04
openstackThe meeting name has been set to 'neutron_l3'14:04
mlavallehi there!14:04
haleybthis daylight savings is messing me up14:04
*** xubozhang has joined #openstack-meeting14:04
mlavalleyes, in betwween the change of time and being in California, I'm also messed up14:06
mlavalle#chair haleyb14:06
openstackCurrent chairs: haleyb mlavalle14:06
*** zhubx has joined #openstack-meeting14:07
haleyb#chair liuyulong_14:07
openstackCurrent chairs: haleyb liuyulong_ mlavalle14:07
mlavallehaleyb: I have to leave 15 minutes before the hour. In case you need to continue the meeting ^^^^14:07
*** irclogbot_1 has quit IRC14:09
mlavalle#topic Bugs14:09
*** openstack changes topic to "Bugs (Meeting topic: neutron_l3)"14:09
openstackRemoving item from minutes: #topic Bugs14:09
mlavalle#topic Announcements14:09
*** openstack changes topic to "Announcements (Meeting topic: neutron_l3)"14:09
*** e0ne has joined #openstack-meeting14:10
mlavalleWe are in the RC-1 period until the end of next week14:10
mlavalleThis is what we are targeting for RC-1:
*** irclogbot_1 has joined #openstack-meeting14:13
mlavalleAlso the PTL nomination period ended yesterday14:13
mlavalleand we are in the voting period:14:13
*** rbudden has quit IRC14:14
mlavalleany other annoucements?14:15
mlavalleok, let's move on14:16
mlavalle#topic Bugs14:16
*** openstack changes topic to "Bugs (Meeting topic: neutron_l3)"14:16
*** yamamoto has joined #openstack-meeting14:16
mlavallewe have a critical bug assigned to slaweq:
openstackLaunchpad bug 1818614 in neutron "Various L3HA functional tests fails often" [Critical,In progress] - Assigned to Slawek Kaplonski (slaweq)14:17
slaweqI have patch for it
slaweqbut I wanted to check another approach also and maybe try to modify ExternalProcess monitor class that it would only return that neutron-keepalived-state-change process is active if "ip monitor" would be active also14:18
slaweqbut if You can take a look at current approach and You think that it's enough, that it's fine for me too :)14:19
mlavalleslaweq: ahh ok, we'll take a look14:20
slaweqthx mlavalle14:20
mlavallehaleyb, liuyulong_: ^^^^14:20
haleybi never knew you could pass options via AGENT-$option14:20
*** enriquetaso has joined #openstack-meeting14:20
*** qianmingyue has joined #openstack-meeting14:21
slaweqit's like that because option is defined to be in AGENT group14:21
liuyulong_Yes, slaweq and I have talked about this, we are still working on this.14:21
haleybis there another change checking ip monitor?  i hadn't seen it14:22
slaweqliuyulong_: I think You are talking about now14:22
openstackLaunchpad bug 1819160 in neutron "Functional tests for dvr ha routers are broken" [High,In progress] - Assigned to Slawek Kaplonski (slaweq)14:22
*** bnemec has quit IRC14:22
slaweqhaleyb: no, there isn't yet14:22
slaweqI want to try it locally and then push patch14:22
slaweqbut for now I don't know if it will be easy to do and really will fix the problem14:23
slaweqso I just want to explore such another approach to fix this bug14:23
mlavallethe other patch is really experimental, for now, right?14:23
*** eharney has quit IRC14:23
slaweqright mlavalle14:23
haleybi think what's there should fix it, will review again14:23
slaweqhaleyb: yes, this one is for sure fixing the issue14:24
slaweqYou can even check in journal.log of functional tests that it happens couple of times that this helped :)14:24
*** zhubx has quit IRC14:24
*** irclogbot_1 has quit IRC14:25
mlavalleok slaweq we will review the current patch14:26
slaweqmlavalle: thx14:26
*** bnemec has joined #openstack-meeting14:27
liuyulong_slaweq, sorry, my bad memory... they have similar tittle...14:27
mlavalleNext one is
openstackLaunchpad bug 1795870 in neutron "Trunk scenario test test_trunk_subport_lifecycle fails from time to time" [High,In progress] - Assigned to Miguel Lavalle (minsel)14:27
*** eharney has joined #openstack-meeting14:28
*** irclogbot_1 has joined #openstack-meeting14:28
mlavalleafter deep exploration on how to avoid kill filters for python interpreter, we decided it is not possible without change to oslo.rootwrap14:29
mlavalleso for the time being we are going with
mlavalleslaweq: I just addressed your comment14:30
slaweqthx mlavalle14:30
mlavalleso hopefully it is good to go today14:30
mlavallenext one is
openstackLaunchpad bug 1717302 in neutron "Tempest floatingip scenario tests failing on DVR Multinode setup with HA" [High,In progress] - Assigned to Slawek Kaplonski (slaweq)14:32
mlavalleslaweq: this is fixed isn't it?14:33
slaweqmy patch is merged14:33
slaweqso it should be better14:33
slaweqbut I'm not sure if there is no other issues which cause similar problems14:33
mlavalleI will mark it fixed then14:33
mlavalleok, slaweq?14:34
slaweqif there will be other issues, we can open new bug always :)14:34
mlavallenext one is
openstackLaunchpad bug 1789434 in neutron "neutron_tempest_plugin.scenario.test_migration.NetworkMigrationFromHA failing 100% times" [High,Confirmed] - Assigned to Manjeet Singh Bhatia (manjeet-s-bhatia)14:36
slaweqIIRC this one should be fixed by Your patch mentioned above14:36
mlavalleI'm assigning it back to me14:36
slaweqI was recently checking it locally and with changes in rootwrap filters it was working fine for me14:36
mlavallefor the time being, assuming that the filters patch fixes it14:36
mlavalleI just want to confirm14:37
slaweqso You can send follow up patch to unmark those tests as unstable14:37
mlavalleslaweq: yes, I'll do that14:37
slaweqthx mlavalle14:37
haleybmlavalle: should you update the commit message to include that bug?14:37
mlavallehaleyb: good point. I'll do it in a bit14:38
mlavalleNext one is
openstackLaunchpad bug 1818334 in neutron "Functional test test_concurrent_create_port_forwarding_update_port is failing" [High,Confirmed] - Assigned to LIU Yulong (dragon889)14:39
liuyulong_Let me output some updates about this bug.14:39
liuyulong_I can not reproduce this locally in 100+ times run.14:39
*** cloudrancher has quit IRC14:40
*** munimeha1 has joined #openstack-meeting14:40
liuyulong_But I can indeed meet the issue when run two concurrent functional tests.14:40
liuyulong_It may be related to the thread pool which is simulating concurrent updating port ip and creating fip port forwarding for this port.14:40
liuyulong_3 times in last 15days.14:41
liuyulong_Maybe we can lower the priority for now.14:41
mlavallewill you continue working on it?14:42
*** cloudrancher has joined #openstack-meeting14:42
mlavalleok, lets lower to medium14:42
mlavallelast one in my list is
openstackLaunchpad bug 1819160 in neutron "Functional tests for dvr ha routers are broken" [High,In progress] - Assigned to Slawek Kaplonski (slaweq)14:44
mlavallethis is also fixed, isn't it?14:44
liuyulong_No, just marked as unstable14:44
slaweqno, this one is what liuyulong_ mentioned before14:44
mlavalleah ok, so let's keep it alive14:44
mlavallethose are all the bugs I had for today14:44
slaweqbasically IMO those dvr ha functional tests are not testing what they should test14:44
mlavalleok, understood14:45
slaweqbecause routers created there aren't "one router on 2 nodes" but "2 different routes on 2 nodes"14:45
slaweqand liuyulong_ is checking how to fix it :)14:45
mlavallethanks slaweq, liuyulong_ !14:45
liuyulong_Here are my try:, not the root cause for now IMO14:45
mlavalleI have to leave now, please continue the meeting14:46
mlavalleI don't have any more bugs14:46
*** mlavalle has quit IRC14:47
davidshaDoes anyone have anymore bugs to discuss?14:49
haleyboh, mlavalle must have dropped14:50
davidshaHe had to leave at XX:4514:50
ralonsohhaleyb, you or liuyulong_ should finish the meeting14:51
haleyb14:54:29 <mlavalle>14:51
haleyb#topic On demand agenda14:51
*** openstack changes topic to "On demand agenda (Meeting topic: neutron_l3)"14:51
davidshaWe have a question about ovs dvr14:52
davidshaWe're working on converting it to backend rather than another agent-mode, I was just wondering is there any documentation specificly about what each mode supports individually, so are there any that shouldn't support Floating IP for example?14:53
liuyulong_No floating IP for L3 ?14:54
haleybdvr_no_external has no external network, so no floating IP in that one mode14:55
davidshaliuyulong_, just using it as an example14:55
*** lseki has joined #openstack-meeting14:55
davidshahaleyb: kk, we'll keep that one in mind.14:57
haleybany other topics?  2 minutes14:58
davidshanone from me14:59
haleybok, thanks for attending everyone14:59
*** openstack changes topic to "OpenStack Meetings ||"14:59
xubozhangi tagged the patches14:59
openstackMeeting ended Wed Mar 13 14:59:55 2019 UTC.  Information about MeetBot at . (v 0.1.4)14:59
openstackMinutes (text):
*** vishalmanchanda has joined #openstack-meeting15:00
liuyulong_xubozhang, thanks15:00
xubozhangthank you15:00
*** psachin has quit IRC15:07
*** armax has joined #openstack-meeting15:08
*** rfolco|ruck is now known as rfolco15:10
*** mriedem has quit IRC15:10
*** mriedem has joined #openstack-meeting15:11
*** _alastor_ has quit IRC15:13
*** _alastor_ has joined #openstack-meeting15:14
*** lpetrut has joined #openstack-meeting15:14
*** Luzi has quit IRC15:14
*** martinkennelly has joined #openstack-meeting15:22
*** igordc has joined #openstack-meeting15:23
*** _alastor_ has quit IRC15:24
*** _alastor_ has joined #openstack-meeting15:24
*** erlon has joined #openstack-meeting15:29
*** zhubx has joined #openstack-meeting15:32
*** irclogbot_1 has quit IRC15:36
*** irclogbot_1 has joined #openstack-meeting15:40
*** enriquetaso has quit IRC15:41
*** a-pugachev has joined #openstack-meeting15:42
*** eharney has quit IRC15:49
*** irclogbot_1 has quit IRC15:49
*** irclogbot_1 has joined #openstack-meeting15:51
*** irclogbot_1 has quit IRC15:52
*** tejdeep has joined #openstack-meeting15:55
*** irclogbot_1 has joined #openstack-meeting15:57
*** rosmaita has joined #openstack-meeting15:58
*** woojay has joined #openstack-meeting15:59
jungleboyj#startmeeting cinder16:00
openstackMeeting started Wed Mar 13 16:00:47 2019 UTC and is due to finish in 60 minutes.  The chair is jungleboyj. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
*** openstack changes topic to " (Meeting topic: cinder)"16:00
openstackThe meeting name has been set to 'cinder'16:00
geguileohi! o/16:00
davidshahi o/16:01
martinkennellyhey o/16:01
jungleboyjcourtesy ping:  jungleboyj diablo_rojo, diablo_rojo_phon, rajinir tbarron xyang xyang1 e0ne gouthamr thingee erlon tpsilva ganso patrickeast tommylikehu eharney geguileo smcginnis lhx_ lhx__ aspiers jgriffith moshele hwalsh felipemonteiro lpetrut lseki _alastor_ whoami-rajat yikun rosmaita enriquetaso hemna _hemna16:01
_pewp_jungleboyj (¬_¬)ノ16:01
*** diablo_rojo has joined #openstack-meeting16:01
*** electrofelix has quit IRC16:02
*** mattw4 has joined #openstack-meeting16:02
*** mattw4 has quit IRC16:03
*** walshh_ has joined #openstack-meeting16:03
jungleboyjOk.  Looks like we are getting a good crowd here.16:03
*** jbernard has joined #openstack-meeting16:04
jungleboyj#topic announcements16:04
*** openstack changes topic to "announcements (Meeting topic: cinder)"16:04
jungleboyjWe have passed Milestone-3 for Stein so we should now be focusing on testing Stein and fixing bugs.16:04
jungleboyjrosmaita:  Thank you.16:05
*** cloudrancher has quit IRC16:05
jungleboyjAny questions about that?16:06
*** cloudrancher has joined #openstack-meeting16:06
jungleboyjAlso, I did submit my candidacy for PTL again.16:07
jungleboyjDidn't look like anyone else submitted a nomination.16:07
jungleboyjSo, thanks for the continued vote of confidence?16:08
whoami-rajatjungleboyj: congratulations. :)16:08
e0nejungleboyj: thanks for your hard work16:08
jungleboyjYou are welcome.  Doing my best.16:09
jungleboyjOk, so I think we can move on from that.16:09
jungleboyj#topic Cinder RSD driver status update16:10
*** openstack changes topic to "Cinder RSD driver status update (Meeting topic: cinder)"16:10
*** erlon has quit IRC16:11
davidshaHi, We have had the CI running for almost a month now and it appears to be stable, we were wondering were there any additional requirements we need to meet before submissions are accepted again?16:11
hemna_are we trying to merge the rsd driver for this release?16:13
hemna_or next?16:13
jungleboyjJust looking at the CI results.16:13
hemna_seems a bit late ?16:13
jungleboyjhemna_:  Next.16:13
jungleboyjThe test results look good I think.16:13
jungleboyjWill need eharney to verify eventually but he is not here.16:13
jungleboyjNeed to have smcginnis add your CI to the list of CIs we are monitoring.16:14
jungleboyjSo, I think all-in-all we are looking good to merge early in Train.16:15
jungleboyjNeed to do a review of it still.16:15
jungleboyjAs far as the merge date is concerned it can merge once we have done the RC for Stein and have opened Train for development.16:16
jungleboyjThank you for your patience and for the update.16:18
davidshano prob, thanks for reviews (past and future).16:18
jungleboyjdavidsha:  Welcome.  Anything else?16:18
davidshaNope, thanks!16:19
*** mattw4 has joined #openstack-meeting16:19
jungleboyjdavidsha:  Are you able to stick around?  We have a discussion on os-brick that may impact you.16:19
davidshaYa, sure16:19
jungleboyjCool.  Thanks.16:19
jungleboyj#topic cinder - os-brick (driver-connector) gaps16:20
*** openstack changes topic to "cinder - os-brick (driver-connector) gaps (Meeting topic: cinder)"16:20
jungleboyjwhoami-rajat: All your's.16:20
whoami-rajatJust wanted to bring to everyone's awareness that we merged a rebranding patch of scaleio -> vxflexos in os-brick but it's dependent patches for nova and cinder were blocked due to feature freeze16:21
jungleboyjwhoami-rajat:  But we are reverting those patches so we shouldn't have a gap there anymore.  Correct?16:22
whoami-rajatthe discussion regarding this led to the conclusion that driver name changes doesn't need change in protocol or connection_properties (simply no change required in os-brick)16:23
whoami-rajatjungleboyj: right.16:23
*** b3nt_pin is now known as beagles16:23
whoami-rajatalso i feel like to mention the sync should be maintained so as to avoid these type of reverts in future IMHO.16:24
*** priteau has joined #openstack-meeting16:24
jungleboyjwhoami-rajat:  Yes, agreed. I think this has been an learning experience for all of us.16:24
jungleboyjNow that hemna_  has been more active again he was able to come in and catch our mistake.16:24
*** irclogbot_1 has quit IRC16:24
hemna_I'm kinda here16:25
*** thgcorrea has joined #openstack-meeting16:25
whoami-rajatjungleboyj: may i query my concern regarding RSD driver?16:25
whoami-rajathemna_: all thanks for fixing it so quickly :)16:25
jungleboyjSo, first, I just want to make sure that we have the issues with scaleio resolved.16:25
hemna_there are lots of problems associated with rebranding the protocol string16:25
*** gyee has joined #openstack-meeting16:25
*** luizbag_ has joined #openstack-meeting16:26
jungleboyjwhoami-rajat: Has the patch for Nova been updated as well?16:26
whoami-rajatjungleboyj: just this one is remaining.16:26
whoami-rajatjungleboyj: unrelated to rebranding but during revert we also reverted this fix.16:26
*** irclogbot_1 has joined #openstack-meeting16:26
whoami-rajatjungleboyj: checking16:27
*** tejdeep has quit IRC16:27
jungleboyjwhoami-rajat: Ok.  Thanks for pointing that out.  So we also need to get that merged before we cut a new release.16:27
whoami-rajatjungleboyj: i think this needs to be abandoned .16:27
whoami-rajatbut hemna_  already left a comment there regarding the same so its good.16:27
hemna_yah that nova patch shouldn't land16:28
jungleboyjOk.  Good.16:29
jungleboyjSo, I think we can move on to the questions about the RSD Connector.16:29
jungleboyj#topic Concerns with the RSD connector16:30
*** openstack changes topic to "Concerns with the RSD connector (Meeting topic: cinder)"16:30
whoami-rajathemna_:  since you abandoned your change regarding removing the nvmeof connector name, why are we still keeping it?16:30
hemna_why are we keeping what?16:31
hemna_I'm not clear what you are asking sorry16:31
jungleboyjwhoami-rajat:  That was abandoned.16:31
hemna_I abandoned that one yesterday16:31
whoami-rajatinitiator name*16:31
hemna_so there is some confusion here16:32
hemna_the protocol name returned by initialize_connection calls is how nova looks up which connector to use in os-brcik16:32
hemna_the nova nvmeof libvirt volume driver had hard coded to use the nvme connector in os-brick16:32
hemna_because there wasn't one for nvmeof16:33
hemna_so the patch to add the nvmeof support in os-brick is actually ok16:33
hemna_but we should eventually update nova to use the nvmeof connector in os-brick16:33
hemna_the problem is that we have 2 protocols pointing to the same connector16:34
whoami-rajathemna_:  but there isn't a connector for nvmeof16:34
hemna_which creates confusion from an os-brick side of things16:34
*** a-pugachev has quit IRC16:34
hemna_so I think we need to put some comments about it in code to explain.  it sux0rs16:34
hemna_I'm not sure we can remove the nvme protocol mapping16:34
hemna_once a protocol is in os-brick I don't think it can ever be removed safely16:35
whoami-rajathemna_: so we can update nova to use protocol name (that is nvmeof returned by cinder) rather than hardcoded NVME initiator name then we can rename the connector in os-brick?16:35
hemna_re: detaching a volume that's been attached would fail16:35
jungleboyjwhoami-rajat:  But can we rename the connector in os-brick?16:35
jungleboyjDon't we have to keep nvme and nvmeof now.16:36
hemna_sure, as long as the mapping is updated too16:36
hemna_the mapping has to stay16:36
jungleboyjOh, but we can change the connector and just update the mapping.16:36
hemna_and by mapping, I mean this:
hemna_would there ever be a reason to have nvme vs nvmeof connectors?16:37
* hemna_ is nvme illiterate16:37
* jungleboyj looks at davidsha 16:38
jungleboyjDo you guys know more here or e0ne16:38
davidshajust so I'm clear, this is updating the nvme connector to nvmeof and also keeping nvme to support backwards compatibility?16:38
e0nehonestly, I don't remember why do we have two connectors16:38
hemna_if all we are doing is renaming NVMeConnector to NVMeOFConnector, then I'm not sure what the point of that would be16:38
whoami-rajathemna_:  nvmeof is the cloud version of nvme protocol i think. same as SCSI and iSCSI16:39
hemna_SCSI and iSCSI are 2 totally different things, not sure that's a good analogy16:39
hemna_anyway, os-brick actually only has 1 connector16:39
hemna_that supports both the nvme and nvmeof protocol mappings16:39
hemna_so I don't think os-brick needs to change16:39
hemna_what is confusing is that cinder drivers are returning 'nvmeof' to nova (initialize_connection)16:40
hemna_and nova says....hey, I'll use nvme connector in os-brick16:40
hemna_because nvmeof doesn't exist....or didn't.16:40
hemna_so, shit os-brick with the mapping as is16:40
whoami-rajathemna_: i meant the relation between SCSI and iSCSI.16:41
hemna_then next release, update nova to use the initiator.NVMEOF constant when constructing the connector.16:41
hemna_that's it.16:41
hemna_or not, either way it works16:41
jungleboyjOh, ship os-brick as is.16:41
hemna_it's just confusing16:41
* jungleboyj was trying to process that.16:42
davidshaOh, thats meant to be ship16:42
hemna_jungleboyj:yah I don't see the point in renaming the connector object itself16:42
jungleboyjdavidsha:  Yes.  I thought he was just really pissed about os-brick's state.16:42
hemna_unless we are simply trying to align everything with nvmeof16:42
jungleboyjDo we have anyone who is an nvmeof expert?16:42
e0nejungleboyj: I'll ask Intel and Mellanox team who worked on nvmeof16:43
jungleboyjSo, actually, as I am looking around here, I don't know that whoami-rajat 's analogy is wrong.16:44
*** lpetrut has quit IRC16:44
jungleboyjNVME is the name for the protocol to talk to the hardware while NVMEoF is like iSCSI where it can be accessed remotely over the network.16:44
jungleboyjSo, we really should never have let the NVME protocol patch merge.16:45
jungleboyjWe can't fix that though, because it has been out in the wild for some time now.16:46
e0newe've got SPDK drivere with: pool["storage_protocol"] = 'NVMe-oF'16:46
whoami-rajatNVMe was developed for SSD's since AHCI was too slow for them, so we have NVMeoF as a TCP/IP alternative of iSCSI.16:46
*** dviroel_ has joined #openstack-meeting16:46
jungleboyjwhoami-rajat:  Right.16:46
jungleboyjSo, to be truly correct the NVME drivers should use NVMEoF for the connector.16:47
hemna_so the protocol that I'm talking about is what is returned as part of initialize_connection16:47
hemna_the protocol is actually the contents of the driver_volume_type16:47
hemna_not the capabilities as being reported by get_volume_stats()16:48
jungleboyjhemna_:  And that is correct.16:48
hemna_2 completely different unrelated things16:48
hemna_the driver_volume_type field is sent to nova/os-brick to lookup the correct connector object to handle the connect/disconnect calls for a volume16:49
whoami-rajathemna_: oh, yeah different context.16:50
jungleboyjSo, it would seem to me that what you are saying hemna_  is right.  Really os-brick should changed to have an NVMeoFConnector and the mappings should be updated and we will have to leave the NVME mapping for backwards compatibility.16:50
hemna_I can rename the connector if so desired16:51
hemna_that's easy16:51
hemna_but not sure the value of it16:51
davidshaSo nvme would be removed for the V or X release then?16:51
hemna_other than consistency in the code16:51
hemna_we can't remove it16:51
jungleboyjIn the future when new protocols come along we should better understand them before merging.16:51
davidshakk, understood16:51
hemna_the mapping from nvme will have to exist forever16:52
whoami-rajathemna_: i think lack of consistency created a lot of confusion currently.16:52
hemna_but it'll just point to the nvmeof connector16:52
hemna_whoami-rajat:yah I agree16:52
jungleboyjwhoami-rajat:  ++16:52
hemna_ok, so I'll put up a review to rename the NVMeConnector to NVMeOFConnector16:52
jungleboyjAnd we should add a note here
jungleboyjExplaining why the two mappings.16:53
jungleboyjhemna_: That, however doesn't need to go in to os-brick 2.8.1 .16:53
hemna_yah, it's not a critical change16:53
hemna_it works as is now16:53
whoami-rajatonce the nova code is changed, we can remove the NVME initiator right?16:54
jungleboyjOk.  Good.  I feel I better understand the situation now.16:54
jungleboyjwhoami-rajat:  No.16:54
hemna_nova isn't the only service that uses os-brick16:54
hemna_cinder does too16:54
jungleboyjwhoami-rajat: We can't be guaranteed that some other consumer isn't using NVME.16:54
hemna_as does the cinderclient with the brick extension (for bare metal attaches)16:55
whoami-rajathemna_: and we're using NVME initiator in spdk only?16:55
hemna_spdk uses nvmeof protocol afaik16:55
whoami-rajathemna_: for copy_image_to_volume and copy_volume_to_image16:55
hemna_also, it's possible that we can have an old nova (using nvme) with a newer os-brick16:55
jungleboyj#action hemna_  To update NVMeConnector to NVMeOFConnector  and add notes on why there are two mappings.16:56
jungleboyjSo, I think we should wrap this up and can finish discussion in channel if necessary.16:56
davidshahemna_: could you ask Nova to put a cap on the version of os-brick it uses in the stable branches?16:57
hemna_coolio, now that everyone is completely confused :)16:57
jungleboyjgeguileo:  Also wanted to cover a topic.16:57
jungleboyjhemna_:  I think we are less confused?16:57
hemna_are you sure you are not confused about being confused?16:57
jungleboyjhemna_:  :-p16:57
whoami-rajathemna_: lol16:57
jungleboyjgeguileo:  Are you around?16:58
geguileojungleboyj: yup16:58
jungleboyj#topic cinderlib update16:58
*** openstack changes topic to "cinderlib update (Meeting topic: cinder)"16:58
jungleboyjYou have 2 minutes.16:58
geguileoNext week is the RC1 target week, and for Cinderlib we need to add the publish-to-pypi job16:58
geguileoI've also found some bugs in cinderlib16:59
geguileoIt would be great to these 4 fixes in the repo:16:59
geguileoAnd less urgent would be the devstack patch, that will allow us to add cinderlib's functional tests to Cinder jobs:16:59
geguileoAaaan we have 20 seconds left16:59
*** jgriffith has quit IRC16:59
jungleboyjOk.  Thanks for the update.  Will take a look at your patches.17:00
jungleboyjAnd time is up.17:00
jungleboyjI will be watching the os-brick patches and pushing up a new release as soon as everything has merged.17:00
jungleboyjSorry for the mess there and thanks to everyone for the help.17:00
jungleboyjIf there are more items to discuss. Lets talk in the CInder channel.17:01
martinkennellythanks !17:01
*** openstack changes topic to "OpenStack Meetings ||"17:01
openstackMeeting ended Wed Mar 13 17:01:22 2019 UTC.  Information about MeetBot at . (v 0.1.4)17:01
openstackMinutes (text):
*** e0ne has quit IRC17:01
*** rosmaita has left #openstack-meeting17:02
*** lpetrut has joined #openstack-meeting17:04
*** igordc has quit IRC17:19
*** gyee has quit IRC17:20
*** gyee has joined #openstack-meeting17:20
*** kopecmartin is now known as kopecmartin|off17:23
*** tssurya has quit IRC17:26
*** lpetrut has quit IRC17:30
*** dmacpher has quit IRC17:31
*** davidsha has quit IRC17:32
*** Swami has joined #openstack-meeting17:33
*** iyamahat_ has joined #openstack-meeting17:38
*** luizbag_ has left #openstack-meeting17:41
*** iyamahat has quit IRC17:41
*** eharney has joined #openstack-meeting17:41
*** jamesmcarthur has quit IRC17:49
*** vishalmanchanda has quit IRC17:49
*** dviroel_ has left #openstack-meeting17:52
*** ianychoi has quit IRC17:55
*** igordc has joined #openstack-meeting17:58
*** jbernard has left #openstack-meeting17:58
*** mattw4 has quit IRC18:00
*** ttsiouts has quit IRC18:01
*** mkarray has joined #openstack-meeting18:01
*** ttsiouts has joined #openstack-meeting18:01
*** martinkennelly has quit IRC18:02
*** mattw4 has joined #openstack-meeting18:03
*** ttsiouts has quit IRC18:05
*** igordc has quit IRC18:08
*** a-pugachev has joined #openstack-meeting18:09
*** igordc has joined #openstack-meeting18:13
*** hongbin has joined #openstack-meeting18:15
*** a-pugachev has quit IRC18:15
*** priteau has quit IRC18:18
*** a-pugachev has joined #openstack-meeting18:19
*** mattw4 has quit IRC18:25
*** pcaruana has quit IRC18:29
*** sridharg has quit IRC18:29
*** ralonsoh has quit IRC18:31
*** enriquetaso has joined #openstack-meeting18:34
*** roman_g has left #openstack-meeting18:38
*** priteau has joined #openstack-meeting18:41
*** priteau has quit IRC18:44
*** jamesmcarthur has joined #openstack-meeting18:47
*** gmann is now known as gmann_afk18:48
*** mattw4 has joined #openstack-meeting18:51
*** mattw4 has quit IRC18:56
*** mattw4 has joined #openstack-meeting18:57
*** e0ne has joined #openstack-meeting19:01
*** mattw4 has quit IRC19:02
*** mattw4 has joined #openstack-meeting19:03
*** bdperkin has quit IRC19:05
*** enriquetaso has quit IRC19:13
*** bdperkin has joined #openstack-meeting19:23
*** gibi has quit IRC19:26
*** enriquetaso has joined #openstack-meeting19:29
*** thgcorrea has quit IRC19:31
*** gibi has joined #openstack-meeting19:38
*** awaugama has quit IRC19:46
*** hongbin has quit IRC19:53
*** hongbin has joined #openstack-meeting19:54
*** mattw4 has quit IRC19:58
*** mattw4 has joined #openstack-meeting20:00
*** iyamahat_ has quit IRC20:06
*** yamahata has quit IRC20:06
*** dklyle has quit IRC20:09
*** mattw4 has quit IRC20:13
*** dklyle has joined #openstack-meeting20:16
*** iyamahat has joined #openstack-meeting20:21
*** iyamahat_ has joined #openstack-meeting20:24
*** mattw4 has joined #openstack-meeting20:25
*** lpetrut has joined #openstack-meeting20:27
*** iyamahat has quit IRC20:27
*** jamesmcarthur has quit IRC20:29
*** lpetrut has quit IRC20:31
*** e0ne has quit IRC20:38
*** munimeha1 has quit IRC20:40
*** gmann_afk is now known as gmann20:41
*** e0ne has joined #openstack-meeting20:41
*** mattw4 has quit IRC20:43
*** mattw4 has joined #openstack-meeting20:43
*** e0ne has quit IRC20:45
*** cloudrancher has quit IRC20:52
*** enriquetaso has quit IRC20:52
*** yamamoto has quit IRC20:53
*** cloudrancher has joined #openstack-meeting20:53
*** cloudrancher has quit IRC20:54
*** cloudrancher has joined #openstack-meeting20:55
*** mjturek has quit IRC20:55
*** alexlecuyer has joined #openstack-meeting20:57
*** cloudrancher has quit IRC20:57
*** cloudrancher has joined #openstack-meeting20:58
*** patchbot has joined #openstack-meeting20:59
notmyname#startmeeting swift21:01
openstackMeeting started Wed Mar 13 21:01:13 2019 UTC and is due to finish in 60 minutes.  The chair is notmyname. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:01
*** openstack changes topic to " (Meeting topic: swift)"21:01
openstackThe meeting name has been set to 'swift'21:01
notmynamewho's here for the swift team meeting?21:01
*** mkarray has left #openstack-meeting21:01
*** m_kazuhiro has joined #openstack-meeting21:01
*** zaitcev has joined #openstack-meeting21:01
notmynamewelcome, everyone21:02
notmynamelooks like we figured out the american time zone change21:02
notmynamewe've got a few things to go over this week...21:02
notmynamebut I'm guessing we should be able to be done quickly :-)21:02
notmynamekota_: I saw that you got the gate jobs working on feature/losf. that's great!21:03
notmynameare they all working? anything else to do?21:03
kota_for the dsvm gate, it's done21:03
notmynamekota_: rledisez: timburke: note especially that the changes to the zuul config that enabled the gate will need to be *excluded* from the final review branch and merge to master21:04
kota_I'll work the next thing in the rest of week and the next week21:04
*** cloudrancher has quit IRC21:04
notmynamethe mechanics of that sortof make sense when I see the change, but I don't really understand why it didn't work (when it's worked for all the other feature branches we've done)21:04
*** cloudrancher has joined #openstack-meeting21:05
notmynamewas it a zuul v3 change? maybe we haven't done a feature branch since then21:05
kota_ah, I can.21:05
kota_it seems like that happens since we migrated to zuul v3 from legacy jobs.21:05
notmynameah ok21:05
notmynameinteresting. and unfortunate21:05
kota_then, basically zuul v3 assumes the required project has same branch name to checkout the repo21:06
kota_that is why stable branch works as expected without change.21:06
notmynameunfortunate in that it more strongly discourages using feature branches because it requires more boilerplate to set up21:06
notmynamealso, it means there's a problem when we pull it out of the eventual review branch. it means that while we're reviewing the final change, those tests won't be gating the patch. which is kinda the most important time to have them...21:07
kota_absolutely other projects (devstack, keystone, etc) doesn't have feature/losf branch so that we should set to checkout from the master explicitly21:07
notmynametimburke: kota_: rledisez: does my fear of the testing gap make sense to you?21:07
notmynameok, good. just want to make sure (1) I'm not crazy and (2) I'm not the only one thinking of it :-)21:08
rlediseznotmyname: yes (i think i understood)21:08
mattoliverauDo we need to raise a zuul bug or feature request?21:08
timburkeyeah -- i'm thinking that we should probably keep the change on the review branch, but at the very end. merge everything else to the feature/review-losf branch, but never +A that last one. then merge to master21:09
mattoliverauit is an open infrastructure project, can we get it improved?21:09
notmynamemattoliverau: I'm not sure. it's a definite change from zuul v2, and in our use case it's a regression. but zuul team may not feel that way21:09
mattoliveraucan always ask :)21:09
kota_it seems like sort of implied-branch might helps, but it was difficult to me to understand how it works.21:09
notmynametimburke: yeah, something like that. kinda depends on what the zuul team says about it or what existing mechanisms exist that we don't know about yet21:09
timburkei feel like there's certainly some room for improvement... like if a branch of the same name exists in the other repo, great! use that! but if not, fall back to master21:10
notmynametimburke: I feel like that used to be what happened21:10
notmynameit's not a looming problem--it's not like losf will be landing in the next few weeks--but good to start thinking about if there are changes we'll ask other people to land21:10
notmynamemattoliverau: if you could ask the infra/zuul team about it, that would be helpful21:11
*** whoami-rajat has quit IRC21:11
mattoliverauis there notes on the problem, /me is suffering from lack of sleep (baby). But yeah I can chase it down21:11
mattoliverauthough re-reading these meeting notes after coffee would probably help :P21:11
notmynamemattoliverau: nope. no notes. just what I gathered in my head from kota_'s patch (see the comments in swift's suul file)21:12
mattoliverauahh cool21:12
kota_mattoliverau: I asked about the issue to AJeager in infra channel so I'll point out the log for you too.21:12
mattoliveraukota_: thanks :)21:12
kota_mattoliverau: patch is aslo at
patchbotpatch 642645 - swift (feature/losf) - Enable swift-dsvm-functional tests at losf feature... (MERGED) - 11 patch sets21:12
notmynamerledisez: looks like I had a question on the agenda about device names/labels/uuids in our docs. what was I supposed to ask you about it? :-)21:13
rledisezso, i created the bug report and answered to the one who raised the point21:13
openstackLaunchpad bug 1817966 in OpenStack Object Storage (swift) "Encourage the use of static device names in fstab" [Undecided,New]21:13
rledisezi'll try to propose a doc patch this week21:13
notmynamerledisez: nice. thanks21:14
notmynamealexlecuyer: back to losf... I seem to remember soemthing about removing grpc? what's up with that? tell us more21:15
alexlecuyerSo I had false hopes with the newer grpc versions,21:15
alexlecuyerit really wants to run a thread from its C core which does not work with eventlet21:15
zaitcevHah! I studied grpc for nothing :-)21:15
alexlecuyerzaitcev, sorry ! :/21:15
tdasilvaalexlecuyer: the patch for Gorka doesn't help ?21:16
notmynamealexlecuyer: sounds like the problem is eventlet, amiright? ;-)21:16
alexlecuyertdasilva: not for our case directly, maybe we could try to adapt it but I still feel it would be brittle21:16
alexlecuyernotmyname: yes but I didn't feel I should bring up eventlet removal (from the object server) in that context21:17
alexlecuyerhappy to be told I am wrong, tho :)21:17
notmynamealexlecuyer: so what's the next idea?21:17
zaitcevnotmyname: (I may be less than fully available just now, just ask timburke about py3, sorry)21:17
notmynamezaitcev: ok, thanks21:17
alexlecuyerSo I wrote a quick and dirty patch to replace grpc with http21:17
rlediseznotmyname: I tried to convince him to do it, but he's saying it a "too big requirement" for losf :)21:17
alexlecuyerkeeping protobuf21:17
notmynamerledisez: it's something we all want, but don't want to work on :-)21:17
*** mattw4 has quit IRC21:17
notmynamealexlecuyer: interesting. so protobuf-over-http? is that a thing?21:18
alexlecuyerand it works well enough that I'm quite confident it would work. the latency is worse, but I think we don't care (the actual RPC calls still take time, so)21:18
*** cloudrancher has quit IRC21:18
alexlecuyerwell I just write serialized protobuf as the body21:18
*** mattw4 has joined #openstack-meeting21:18
alexlecuyerand the URL is the rpc call name21:18
*** janki has quit IRC21:19
notmynamewhat verb to you use? (probably too close to bikeshedding for right now)21:19
*** cloudrancher has joined #openstack-meeting21:19
alexlecuyerI did POST for everything (I always expect a reply, similar to grpc, even if an empty one)21:19
alexlecuyerand I used HTTP code to emulate grpc error codes (FAILED_PRECONDITION, etc)21:20
alexlecuyerso the rest of the code need not change21:20
notmynameis that functionality on losf yet? is it in prod at ovh yet? (I think you've got it backwards there ;-)21:20
alexlecuyerSo, I posted a PR, I will put the link in a moment, so that kota could take a look21:20
alexlecuyerit passes functest, but it's quick and dirty)21:21
alexlecuyerIt's not in prod at OVH, it needs work21:21
notmynameis that what you're currently working on until it's better?21:21
kota_I should go to look as the next thing21:21
alexlecuyerI need to work on grpc replacemnt yes.(I have had to work on other things the past few days)21:21
notmynameok, thanks for the update :-)21:22
alexlecuyerand for now I think 'im happy with HTTP but, I can consider other options, if you have ideas21:22
notmynameanything else to share on losf for this week's meeting?21:22
alexlecuyernot from me21:22
notmynamelet's move to py321:22
notmynamethat also has some good news this week21:22
notmynametimburke: want to share?21:22
timburkei can get some replicated func tests to pass on py37!
patchbotpatch 642520 - swift - Get functional/ running under py3 - 6 patch sets21:23
notmynamethat's wonderful!21:23
notmynameawww yeah! you've even got a py3 ratchet in there21:24
timburkeit needed us to stop monkeypatching mimetools (see and it has its own crazy stuff going on in but... hey! py3 func tests!21:24
patchbotpatch 640552 - swift - Stop monkey-patching mimetools - 5 patch sets21:24
patchbotpatch 642520 - swift - Get functional/ running under py3 - 6 patch sets21:24
timburkethat mimetools patch is already approved (thanks tdasilva, thanks zaitcev!)21:25
timburkejust waiting on the gate21:25
timburkei'll try to keep up-to-date with patches in progress21:25
notmynamethe monkeypatching-ectomy (appologies for anyone who's a non-native english speaker for that) is nice because it also introduces the mechanism for fixing historic metadata stored in clusters. it gives a migration path!21:25
*** yamamoto has joined #openstack-meeting21:26
timburkedoes it? i don't think it actually matter there much... *shrug*21:26
timburkenext main things are so i can get EC func tests21:26
patchbotpatch 638019 - swift - Clean up how we walk through ranges in ECAppIter - 1 patch set21:26
timburkeand figuring out how i want to get the func tests actually running in the gate21:27
notmynametimburke: I thought it did becuase you use the same protocol class to read older metadata without needing to patch stdlib (and/or wait for py38)21:27
notmynameor was it http headers? or both?21:27
timburkeso the wsgi parse_request() change makes it so we don't have to wait on, which is very much a good thing21:28
timburkethat was in the py3-func-tests patch21:29
notmynameright, that's the thing. it's all very exciting21:29
timburkei also got around to writing up
timburke(http.client cannot send non-ASCII request lines)21:29
timburkeand i'm working on putting up two PRs so CPython can decide which path they want to take on it21:30
notmynameI love the implication here. "Why hasn't swift completely ported to py3 yet?!?!" and tim is like, "well, I've been filing bugs in cpython and waiting for them to land my patches" ;-)21:30
mattoliveraunice work timburke21:30
timburkemeanwhile, i'm probably gonna have swift_test_client patch out putrequest()21:30
*** njohnston has quit IRC21:30
timburkenothing like discovering bugs as old as notmyname's kids...21:31
notmynameI have 3. one's 11, and two that are 9. we're in a meeting about one of those younger kids right now21:31
*** njohnston has joined #openstack-meeting21:32
mattoliveraua misbehaving kid who wont run on py3 :P21:32
notmynamewhat a slacker!21:32
notmynametimburke: zaitcev: great work on py3 this week21:33
notmynameanything else to report on that, or things to call out for help on?21:33
timburkethis probably won't come as any great surprise, but what i need most is reviewer bandwidth21:33
notmynamewait, who replaced timburke with zaitcev?21:33
notmynamezaitcev has been saying that for a really long time21:34
notmynameyou know, that's a really good segue to the next topic, actually....21:34
notmynamethe priority reviews page21:34
timburkeif you can, look at the patches. if there's something that seems weird, ask about it. make me explain what's going on in my head, so i'm not the only one with a model of how to do this polyglot thing21:34
* mattoliverau will try and spend more time with py3 reviews. 21:34
notmynametimburke: is the py3 section up to date?21:35
timburkei think so? mostly.21:35
*** yamamoto has quit IRC21:35
notmynameso here's the thing abotu open reviews... we need to tag a swift release soon21:35
notmynamebased on the openstack release schedule, we need to tag a swift release the week of march 2521:36
notmynameon that schedule, we're currently in R-4. the cycle release projects (nova) will do an RC next week21:36
notmynameand the final tag is requires by the week of april 121:37
kota_so close21:37
notmynamewe can tag at any time21:37
mattoliverauan april fools release :P21:37
tdasilvawe ported to py3 :)21:38
notmynameI do not know of any major outstanding patches or issues. that is, I don't think we're waiting on some patch to land that would otherwise block a release21:38
kota_the release is the lie! :P21:38
timburketdasilva, i was just thinking that :-)21:38
notmynameso I think we can tag at any time21:38
notmynameif we do it right now (wont' happen), that may be ok, but there may be a few things otherwise that would be nice to land21:38
notmynameif we wait until the last moment, then we're at risk of getting delayed by the gate21:39
notmynamewhich is why I said "week of march 25"21:39
timburkenot really a release blocker, but landing would make me feel *much* better about our unicode support21:39
patchbotpatch 641855 - swift - Fix how we UTF-8-ify func tests - 1 patch set21:39
mattoliverausounds like a reasonable target date21:39
notmynameI think I should work with timburke on getting the priority review page up to date for the next release21:39
notmynamebecause timburke is the new ptl, starting whenever new ptls start. april? now? IDK21:40
* kota_ is wondering if it's the last work for notmyname as the PTL? when timburke will start to cheer the meeting?21:40
notmynamekota_: yeah, me too :-)21:40
kota_oh, said same thing with notmyname21:40
notmynameI'm trying to get him to do all the things, starting yesterday, but I don't think he's on the hook to do it until after the release :-)21:40
timburkenotmyname, you've never had to worry about these sorts of things before ;-)21:40
notmynameI know!21:40
*** cloudrancher has quit IRC21:40
notmynamespeaking of which, I'd like to say, on the record here in the meeting, that timburke will do a great job as PTL for swift and I'm very happy he's volunteered to take the role21:41
mattoliverautimburke: are you still only coming to the PTG part of the summit? do we need to think about the project update?21:41
timburkemattoliverau, yep, just wed-sat21:41
notmynamemattoliverau: depending on when the update is scheduled, either he or I will do it. if timburke can't, then I'll do it21:41
mattoliverauthough at the same time, sad to see notmyname not PTLing21:42
*** cloudrancher has joined #openstack-meeting21:42
mattoliveraujust didn't want it to slip through the cracks :)21:42
notmynameI'll be in denver sunday-saturday21:42
* mattoliverau will be there from Friday - Saturday21:43
notmynameI heard a rumor (nothing official) that the swift update may be on monday. if so, I'll do it21:43
notmyname"everything's great. if it's not, go talk to timburke. updated done"21:43
notmynameok, anything else to bring up in the meeting thins week?21:44
notmynameany questions, concerns, or help-needed?21:44
timburkenotmyname will be playing on repeat while he makes his slides ;-)21:44
notmynamerledisez: ok, the meeting wasn't as quite as short as I expected :-)21:45
notmynamethanks everyone for coming this week21:45
notmynameand thank you for your work on swift21:45
*** openstack changes topic to "OpenStack Meetings ||"21:45
openstackMeeting ended Wed Mar 13 21:45:41 2019 UTC.  Information about MeetBot at . (v 0.1.4)21:45
openstackMinutes (text):
*** patchbot has left #openstack-meeting21:45
*** m_kazuhiro has quit IRC21:50
*** a-pugachev has quit IRC21:52
*** a-pugachev has joined #openstack-meeting21:53
*** a-pugachev has quit IRC21:54
*** rcernin has joined #openstack-meeting21:57
*** mattw4 has quit IRC22:01
*** iyamahat__ has joined #openstack-meeting22:01
*** mattw4 has joined #openstack-meeting22:01
*** iyamahat_ has quit IRC22:04
*** carlos_silva has quit IRC22:07
*** raildo has quit IRC22:10
*** mriedem is now known as mriedem_afk22:18
*** lifeless has quit IRC22:27
*** lifeless has joined #openstack-meeting22:27
*** alexlecuyer has quit IRC22:37
*** woojay has left #openstack-meeting22:46
*** cloudrancher has quit IRC22:51
*** cloudrancher has joined #openstack-meeting22:54
*** iyamahat__ has quit IRC23:02
*** iyamahat__ has joined #openstack-meeting23:03
*** slaweq has quit IRC23:05
*** ianychoi has joined #openstack-meeting23:06
*** iyamahat_ has joined #openstack-meeting23:06
*** iyamahat__ has quit IRC23:09
*** iyamahat_ has quit IRC23:10
*** slaweq has joined #openstack-meeting23:11
*** slaweq has quit IRC23:15
*** iyamahat has joined #openstack-meeting23:16
*** mjturek has joined #openstack-meeting23:18
*** hongbin has quit IRC23:26
*** lseki has quit IRC23:31
*** rbudden has joined #openstack-meeting23:31
*** mattw4 has quit IRC23:36
*** mjturek has quit IRC23:43
*** erlon has joined #openstack-meeting23:48
*** rbudden has quit IRC23:55

Generated by 2.15.3 by Marius Gedminas - find it at!