Wednesday, 2019-03-20

*** jamesmcarthur has quit IRC00:01
*** jamesmcarthur has joined #openstack-meeting00:07
*** lseki has quit IRC00:09
*** markvoelker has joined #openstack-meeting00:17
*** markvoelker has quit IRC00:21
*** jmlowe has left #openstack-meeting00:31
*** igordc has quit IRC00:42
*** diablo_rojo has quit IRC00:48
*** markvoelker has joined #openstack-meeting00:48
*** lbragstad has quit IRC00:49
*** brbowen has quit IRC00:49
*** jamesmcarthur has quit IRC00:50
*** slaweq has joined #openstack-meeting00:56
*** gyee has quit IRC00:57
*** slaweq has quit IRC01:00
*** tetsuro has joined #openstack-meeting01:01
*** b1airo has quit IRC01:02
*** brbowen has joined #openstack-meeting01:12
*** mriedem_away has quit IRC01:15
*** jamesmcarthur has joined #openstack-meeting01:16
*** jamesmcarthur has quit IRC01:18
*** jamesmcarthur has joined #openstack-meeting01:19
*** senrique__ has joined #openstack-meeting01:19
*** tetsuro has quit IRC01:20
*** jamesmcarthur has quit IRC01:22
*** cheng1 has joined #openstack-meeting01:26
*** whoami-rajat has joined #openstack-meeting01:29
*** jamesmcarthur has joined #openstack-meeting01:33
*** brbowen has quit IRC01:42
*** hyunsikyang__ has quit IRC01:46
*** hyunsikyang has joined #openstack-meeting01:46
*** larainema has joined #openstack-meeting01:46
*** yamahata has quit IRC01:48
*** iyamahat_ has quit IRC01:49
*** markvoelker has quit IRC01:49
*** zhubx has quit IRC01:53
*** zhubx has joined #openstack-meeting01:55
*** yamamoto has joined #openstack-meeting02:02
*** senrique__ has quit IRC02:04
*** senrique__ has joined #openstack-meeting02:20
*** jamesmcarthur has quit IRC02:22
*** jamesmcarthur has joined #openstack-meeting02:26
*** senrique__ has quit IRC02:27
*** yamamoto has quit IRC02:39
*** yamamoto has joined #openstack-meeting02:44
*** yamamoto has quit IRC02:44
*** psachin has joined #openstack-meeting02:57
*** yamamoto has joined #openstack-meeting03:09
*** apetrich has quit IRC03:14
*** pcarver has quit IRC03:21
*** rbudden has joined #openstack-meeting03:24
*** sridharg has joined #openstack-meeting03:32
*** pcarver has joined #openstack-meeting03:36
*** rbudden has quit IRC03:52
*** zhubx has quit IRC03:56
*** jamesmcarthur has quit IRC03:56
*** zhubx has joined #openstack-meeting03:56
*** jamesmcarthur has joined #openstack-meeting04:00
*** jamesmcarthur has quit IRC04:00
*** jamesmcarthur has joined #openstack-meeting04:01
*** jamesmcarthur has quit IRC04:05
*** pfallenop has quit IRC04:07
*** jamesmcarthur has joined #openstack-meeting04:27
*** psachin has quit IRC04:34
*** cheng1 has quit IRC04:41
*** psachin has joined #openstack-meeting04:41
*** janki has joined #openstack-meeting04:47
*** iyamahat has joined #openstack-meeting04:53
*** larainema has quit IRC05:12
*** martial has quit IRC05:18
*** markvoelker has joined #openstack-meeting05:22
*** cheng1 has joined #openstack-meeting05:23
*** markvoelker has quit IRC05:26
*** pwu_ has joined #openstack-meeting05:40
*** janki has quit IRC05:50
*** jbadiapa has joined #openstack-meeting05:51
*** markvoelker has joined #openstack-meeting05:53
*** janki has joined #openstack-meeting05:57
*** yamahata has joined #openstack-meeting05:57
*** jbadiapa has quit IRC06:17
*** vishalmanchanda has joined #openstack-meeting06:28
*** iyamahat has quit IRC06:39
*** Luzi has joined #openstack-meeting06:45
*** pwu_ has quit IRC07:14
*** e0ne has joined #openstack-meeting07:17
*** pcaruana has joined #openstack-meeting07:20
*** e0ne has quit IRC07:27
*** apetrich has joined #openstack-meeting07:40
*** simon-AS559 has joined #openstack-meeting07:41
*** e0ne has joined #openstack-meeting07:42
*** slaweq has joined #openstack-meeting07:55
*** ttsiouts has joined #openstack-meeting08:05
*** simon-AS5591 has joined #openstack-meeting08:14
*** e0ne has quit IRC08:15
*** simon-AS559 has quit IRC08:17
*** ttsiouts has quit IRC08:26
*** ttsiouts has joined #openstack-meeting08:34
*** rcernin has quit IRC08:38
*** Lucas_Gray has joined #openstack-meeting08:40
*** ttsiouts has quit IRC08:52
*** ttsiouts has joined #openstack-meeting08:54
*** ralonsoh has joined #openstack-meeting08:58
*** Luzi has quit IRC08:59
*** sridharg has quit IRC09:01
*** sridharg has joined #openstack-meeting09:09
*** jbadiapa has joined #openstack-meeting09:17
*** iyamahat has joined #openstack-meeting09:24
*** simon-AS5591 has quit IRC09:34
*** psachin has quit IRC09:48
*** cheng1 has quit IRC09:49
*** yamamoto has quit IRC09:50
*** jbadiapa has quit IRC09:56
*** dmacpher has joined #openstack-meeting10:01
*** dmacpher has quit IRC10:01
*** cheng1 has joined #openstack-meeting10:06
*** hjensas has joined #openstack-meeting10:10
*** Lucas_Gray has quit IRC10:13
*** vishalmanchanda has quit IRC10:13
*** Lucas_Gray has joined #openstack-meeting10:13
*** jbadiapa has joined #openstack-meeting10:16
*** electrofelix has joined #openstack-meeting10:21
*** simon-AS559 has joined #openstack-meeting10:23
*** psachin has joined #openstack-meeting10:24
*** yamamoto has joined #openstack-meeting10:28
*** e0ne has joined #openstack-meeting10:45
*** yamamoto has quit IRC10:47
*** yamamoto has joined #openstack-meeting10:47
*** shilpasd has quit IRC10:54
*** yamamoto has quit IRC10:58
*** yamamoto has joined #openstack-meeting11:00
*** carlos_silva has joined #openstack-meeting11:06
*** brbowen has joined #openstack-meeting11:11
*** janki has quit IRC11:16
*** janki has joined #openstack-meeting11:16
*** ttsiouts has quit IRC11:21
*** simon-AS559 has quit IRC11:27
*** rcernin has joined #openstack-meeting11:28
*** lpetrut has joined #openstack-meeting11:29
*** ttsiouts has joined #openstack-meeting11:37
*** pcaruana has quit IRC11:38
*** cheng1 has quit IRC11:39
*** yamamoto has quit IRC11:40
*** yamamoto has joined #openstack-meeting11:41
*** ttsiouts has quit IRC11:42
*** raildo has joined #openstack-meeting11:45
*** yamamoto has quit IRC11:46
*** tssurya has joined #openstack-meeting11:47
*** dmacpher has joined #openstack-meeting11:47
*** ttsiouts has joined #openstack-meeting12:04
*** e0ne has quit IRC12:07
*** dmacpher has quit IRC12:08
*** yamamoto has joined #openstack-meeting12:10
*** jbadiapa has quit IRC12:11
*** yamamoto has quit IRC12:11
*** psachin has quit IRC12:11
*** markvoelker has quit IRC12:13
*** pcaruana has joined #openstack-meeting12:16
*** jrbalderrama has joined #openstack-meeting12:18
*** psachin has joined #openstack-meeting12:19
*** simon-AS559 has joined #openstack-meeting12:39
*** njohnston has quit IRC12:40
*** njohnston has joined #openstack-meeting12:41
*** eharney has joined #openstack-meeting12:42
*** cheng1 has joined #openstack-meeting12:42
*** rbudden has joined #openstack-meeting12:44
*** cheng1 has quit IRC12:47
*** yamamoto has joined #openstack-meeting12:49
*** artom has joined #openstack-meeting12:58
*** mjturek has joined #openstack-meeting13:00
*** artom has quit IRC13:01
*** artom has joined #openstack-meeting13:01
*** yaawang has quit IRC13:02
*** yaawang has joined #openstack-meeting13:07
*** lbragstad has joined #openstack-meeting13:07
*** lseki has joined #openstack-meeting13:09
*** rcernin has quit IRC13:16
*** e0ne has joined #openstack-meeting13:16
*** mriedem has joined #openstack-meeting13:17
*** cloudrancher has quit IRC13:20
*** cloudrancher has joined #openstack-meeting13:21
*** jbadiapa has joined #openstack-meeting13:21
*** psachin has quit IRC13:30
*** njohnston has quit IRC13:30
*** njohnston has joined #openstack-meeting13:31
*** njohnston has quit IRC13:36
*** njohnston has joined #openstack-meeting13:37
*** simon-AS559 has quit IRC13:40
*** senrique__ has joined #openstack-meeting13:42
*** senrique__ has quit IRC13:44
*** enriquetaso has joined #openstack-meeting13:44
*** cloudrancher has left #openstack-meeting13:45
*** awaugama has joined #openstack-meeting13:57
*** mlavalle has joined #openstack-meeting14:02
mlavalle#startmeeting neutron_l314:02
openstackMeeting started Wed Mar 20 14:02:20 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:02
*** openstack changes topic to " (Meeting topic: neutron_l3)"14:02
openstackThe meeting name has been set to 'neutron_l3'14:02
*** eharney has quit IRC14:03
hjensaso/ I'm guesting again. :)14:03
*** Luzi has joined #openstack-meeting14:03
haleybhjensas: hi, let me make sure to add that item to the agenda14:03
mlavalle#topic Announcement14:04
*** openstack changes topic to "Announcement (Meeting topic: neutron_l3)"14:04
mlavalleWe are in RC-1 week14:04
mlavalleWe went over our RC-1 targets yesterday and it seems we are in good shape:14:06
mlavalleand PTL election ended yesterday14:07
mlavallehaven't seen results message. Has anybody?14:08
haleybwho won? :)14:08
mlavallewell, we will soon know who is the Nova PTL for the next cycle14:09
mlavallethat is really what I'm wondering14:09
mlavalleany other announcements14:09
*** ttsiouts has quit IRC14:10
mlavalleoh yeah, I have another one14:10
*** ttsiouts has joined #openstack-meeting14:10
mlavallePlease don't forget that we have started an etherpad to collect topics for the PTG:
haleybmlavalle: i see the results, nova ptl is eric fried14:11
mlavalleyeap. it was a clear win14:12
mlavalleok, let's move on14:13
mlavalle#topic Bugs14:13
*** openstack changes topic to "Bugs (Meeting topic: neutron_l3)"14:14
mlavallewe have
openstackLaunchpad bug 1819160 in neutron "Functional tests for dvr ha routers are broken" [High,In progress] - Assigned to Slawek Kaplonski (slaweq)14:15
*** ttsiouts has quit IRC14:15
slaweqhi, sorry I forgot about this meeting14:16
mlavalleno problem14:16
mlavallewe were looking at
openstackLaunchpad bug 1819160 in neutron "Functional tests for dvr ha routers are broken" [High,In progress] - Assigned to Slawek Kaplonski (slaweq)14:16
*** mjturek has quit IRC14:17
slaweqyes, I described what I found in this bug14:17
slaweqbasically those tests are creating 2 independent routers always14:17
slaweqand it should be one router on 2 nodes14:17
slaweqone master and one standby14:17
slaweqso basically those tests are usually passing because it's excuted fast enough14:18
slaweqwhen for example You will wait a bit longer it will fail14:18
slaweqbecause both router1 and router2 will have state "master"14:19
*** ttsiouts has joined #openstack-meeting14:19
mlavalleso still in progress? liuyulong's comments confused me14:19
liuyulongWe also have some comments here.14:19
slaweqit's for sure not fixed yet14:20
mlavallelet's keep an eye on it14:21
slaweqand I think we should change those tests that routers would be created in the way similar to
slaweqbut for now I don't have time for this,14:21
slaweqI even pushed some WIP patch
mlavallewill you get back to it at some point?14:22
slaweqbut I don't know when I will be able to get back to it14:22
slaweqmlavalle: probably not this and not next week14:22
slaweqbut I will try14:22
mlavalleshould we ask a volunteer to take over?14:22
ralonsohI can give a try14:23
slaweqwould be great if someone wants to take it :)14:23
slaweqthx ralonsoh14:23
ralonsoh(I slaweq wants)14:23
* mlavalle was thinking of ralonsoh... heh heh heh14:23
slaweqfeel free to assign it to Yourself14:23
ralonsohslaweq, I'll talk to you later , thanks!14:24
mlavallethanks ralonsoh !14:24
liuyulongslaweq, uuid of router is not the critical data. The router are connected by veth pair devices.14:24
liuyulongHere are some log research:
slaweqliuyulong: sure, but they aren't connected14:24
slaweqand having same uuid will be much better for future users of tests, e.g. in case of some another debugging14:25
*** jamesmcarthur has quit IRC14:25
liuyulongThere are two test ovs br-test-xxx bridge, and each has veth pair device on it.14:25
*** jamesmcarthur has joined #openstack-meeting14:25
slaweqliuyulong: but as I said, if You would use remote_pdb in place which I pointed before, You will see that those routers will both become master after some time14:27
slaweqand that isn't expected behaviour14:27
liuyulongWhen the test running, you can run "watch -n 1 ovs-vsctl show" to see the test bridges and devices.14:27
slaweqor maybe I missunderstand those tests14:27
liuyulongslaweq, for the pdb issue, I guess, you may block some router processing actions.14:28
slaweqliuyulong: no, nothing is blocked imo14:28
slaweqliuyulong: test starts, routers are created and both are "standby"14:29
slaweqthen after some time keepalived process for each of routers switch router to master14:29
liuyulongslaweq, that's ture, they are standby.14:29
slaweqso IMO that means that those routers aren't connected to each other14:29
slaweqanyway, I think we can discuss about it in bug report or later on irc14:30
slaweqI don't want to "use" all meeting time for it :)14:30
mlavalleand involve ralonsoh14:30
liuyulongAnd thanks ralonsoh join this bug ship.14:30
slaweqyeah :)14:30
mlavalleNext one is
openstackLaunchpad bug 1789434 in neutron "neutron_tempest_plugin.scenario.test_migration.NetworkMigrationFromHA failing 100% times" [High,In progress] - Assigned to Miguel Lavalle (minsel)14:31
mlavalleI will send a patch removing the unstable tag for those tests14:31
mlavalleI will do that today14:31
* mlavalle ran out of time last night14:31
mlavallethis bug is expected to be fixed by
mlavalleand that's all the bugs I had14:32
mlavalledoes anyone else have other bugs?14:32
liuyulongI have14:33
openstackLaunchpad bug 1818334 in neutron "Functional test test_concurrent_create_port_forwarding_update_port is failing" [Medium,In progress] - Assigned to LIU Yulong (dragon889)14:34
liuyulongThe fix was sent here: IMO, there was IP collision during the test.14:34
liuyulongSometimes the '_find_ip_address' can even return a IP address in-used by other ports.14:35
liuyulongThis is the root cause. But the fix is just a work around which only prevent such IP collision by randomly choice the IP addr.14:36
ralonsohI took a look at those tests and I didn't see it. But what I saw was a problem in the DB14:36
ralonsohthe FIP assignation is not deleted14:37
liuyulong this is the test result locally.14:37
ralonsohand it's using the new private IP with the previously assigned FIP14:37
*** awaugama has quit IRC14:38
*** luizbag has joined #openstack-meeting14:39
*** thgcorrea has joined #openstack-meeting14:39
liuyulongI'm not sure, but for this test, the floating IP is free?14:39
mlavalleshould we continue the conversation in the patch?14:39
*** rbudden has quit IRC14:40
mlavallethanks liuyulong, ralonsoh14:40
mlavalleany other bugs?14:40
*** electrofelix has quit IRC14:41
mlavalleok, let's move on14:41
mlavalle#topic Openflow DVR14:42
*** openstack changes topic to "Openflow DVR (Meeting topic: neutron_l3)"14:42
mlavalleI don't see igordc and xubozhang here today14:43
mlavallebut I want to mention that I will pay special attention to their patches and I encourgae others to do the same14:44
mlavalleit would be good if if we can merge them early in Train14:44
mlavalleideally before Train-114:44
mlavallethat way we have time to play with them14:45
mlavalle#topic On demand agenda14:46
*** openstack changes topic to "On demand agenda (Meeting topic: neutron_l3)"14:46
mlavalleanything else we should discuss today?14:46
haleybmlavalle: i added one item14:46
haleybi'd like to talk about nf_conntrack_helper14:47
*** ivy has joined #openstack-meeting14:47
mlavalleyes I see it14:47
mlavallego ahead14:47
*** sridharg has quit IRC14:47
haleybthere was an initial patch that just enabled it by default in the router namespace14:47
haleybhjensas had another suggestion to add an extension that would enable it for a router14:48
mlavalleyeah, it was originally brought up a couple of months abo by Julia and someone else14:48
haleybi'm still not sure of the downside of just always enabling it, since the qrouter isn't running services14:49
mlavallean l3 extension, right?14:49
haleybyes, and you'd specify the ports and helper14:49
haleybi've been meaning to ping someone internal that knows more about the helper than i, but think he's out this week14:50
haleybmlavalle: any thoughts on which you prefer?14:51
mlavallewell, the extension makes it configurable, doesn't it?14:51
*** jbadiapa has quit IRC14:51
haleybi'm always under the impression that if we make it hard noone will use it/know how to use it14:51
haleybmlavalle: yes, it could allow a user to configure it for a single router14:51
mlavalleI am open to explore that option14:52
mlavallemaybe, when you get feedback from this other fellow, we can discuss it agin in this meeting14:52
mlavallewould that help?14:52
haleybmlavalle: sure.  i'm guessing he'll say "you really shouldn't always enable this"14:53
haleyb#action haleyb to get more info on enabling the nf-conntrack-helper by default14:53
mlavalleif that's the case, the extension seems the way to go14:54
mlavalledoesn't it?14:54
haleybmlavalle: yes14:54
mlavalleso I'd say let's start moving in that direction14:54
mlavalleand just confirm with this person14:54
mlavalleare you ok with this, hjensas?14:55
* mlavalle will also do some digging14:55
haleybmlavalle: ack14:55
mlavalleanything else?14:56
haleybnot from me14:56
hjensasmlavalle: yes, I have started some work on the extension approach. So I will continue on that, and haleyb can ping me if it turns out we just want to enable by default.14:56
haleybhjensas: great, thanks!14:56
mlavallehjensas: thanks for working on this14:56
mlavallethanks for attending14:56
*** openstack changes topic to "OpenStack Meetings ||"14:56
openstackMeeting ended Wed Mar 20 14:56:44 2019 UTC.  Information about MeetBot at . (v 0.1.4)14:56
openstackMinutes (text):
*** vishalmanchanda has joined #openstack-meeting14:57
*** mjturek has joined #openstack-meeting14:57
*** dmacpher has joined #openstack-meeting14:58
*** rbudden has joined #openstack-meeting14:59
*** lpetrut has quit IRC15:01
*** manjeets_ is now known as manjeets15:02
*** hjensas has quit IRC15:07
*** enriquetaso has quit IRC15:08
*** mlavalle has left #openstack-meeting15:15
*** yamamoto has quit IRC15:16
*** Luzi has quit IRC15:17
*** yamamoto has joined #openstack-meeting15:18
*** yamamoto has quit IRC15:18
*** yamamoto has joined #openstack-meeting15:18
*** yamamoto has quit IRC15:18
*** hongbin has joined #openstack-meeting15:32
*** eharney has joined #openstack-meeting15:40
*** rosmaita has joined #openstack-meeting15:49
*** gyee has joined #openstack-meeting15:51
*** lpetrut has joined #openstack-meeting15:54
*** liuyulong is now known as liuyulong|away15:57
*** dmacpher has quit IRC15:57
*** tejdeep has joined #openstack-meeting15:57
smcginnis#startmeeting cinder16:00
openstackMeeting started Wed Mar 20 16:00:03 2019 UTC and is due to finish in 60 minutes.  The chair is smcginnis. 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
smcginnisCourtesy ping: 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:00
*** abishop has joined #openstack-meeting16:00
geguileohi! o/16:00
smcginnisJay has some personal business to attend to today, so I'm your guest moderator for today. :)16:00
smcginnis#link Agenda16:01
geguileosmcginnis: thanks16:01
whoami-rajat:( :)16:01
*** woojay has joined #openstack-meeting16:01
smcginnisGuess we have a pretty good turnout, so I'll get going.16:02
smcginnis#topic Announcements16:02
*** openstack changes topic to "Announcements (Meeting topic: cinder)"16:02
smcginnisWanted to make sure folks were aware tomorrow is the RC1 deadline.16:02
smcginnisWe are getting really close to the end of stein now.16:02
e0nethere is also Hard String Freeze deadline16:02
smcginnise0ne: Oh, good point.16:03
smcginnisThere are multiple things that come with this deadline.16:03
whoami-rajatsmcginnis: so my api-ref patches won't merging after it? right?16:03
*** Lucas_Gray has quit IRC16:03
*** efried is now known as efried_rolling16:03
smcginniswhoami-rajat: Probably not for stein.16:03
*** walshh_ has joined #openstack-meeting16:04
e0neafter RC1 master branch will be opened for Train, so any fixes to Stain should be backported to stable/stien16:04
smcginnisBut technically, as soon as we cut RC1 and a stable/stein branch, that makes master Train.16:04
diablo_rojo_phonAlso if cinder has cycle highlights.. getting those in ASAP.16:04
smcginnisBut we should still be focusing on stein work until the cycle is done.16:04
smcginnisdiablo_rojo_phon: Thanks!16:04
e0nesmcginnis: +116:05
smcginnisWith Jay tied up, I guess I'll try to put together some highlights.16:05
smcginnisCould use input from others on that though.16:05
diablo_rojo_phonsmcginnis: thank you for the convenient segue :)16:05
diablo_rojo_phonAnd in advance for the highlights.16:05
jungleboyjsmcginnis: I have that on my list.16:05
smcginnisjungleboyj: Oh, awesome16:06
jungleboyjI will get them done.16:06
jungleboyjdiablo_rojo_phon: thanks for thr reminder.16:06
smcginnisAll cores, please mark patches as review-priority +1 or +2 if you think there is anything critical to get in for stein yet.16:06
*** dviroel_ has joined #openstack-meeting16:06
smcginnisThe Train schedule has also been published.16:07
diablo_rojo_phonjungleboyj: if you have any questions myself or other release folks can help. I have a meeting Thursday to start processing all the info so by EOD today would be preferable if possible?16:07
jungleboyjdiablo_rojo_phon: ok. Will do. Have done those before. Just need to figure out what to say.16:08
smcginnisdiablo_rojo_phon: I'm thinking those kinds of meetings either need to be held later, or we should move the highlights deadline up to be earlier in train.16:08
diablo_rojo_phonsmcginnis: I think both :)16:09
jungleboyjsmcginnis: ++16:09
diablo_rojo_phonjungleboyj: happy to help if you need me.16:09
jungleboyjdiablo_rojo_phon: cool thanks.16:10
diablo_rojo_phonI would have pushed the meeting later if I could. It was slated to happen last week.16:10
smcginnisOne more announcement - PTL election for Train is over. Long live the king (of the jungle).16:10
jungleboyjHa ha.16:10
*** igordc has joined #openstack-meeting16:10
*** enriquetaso has joined #openstack-meeting16:11
smcginnis#topic Generalized filtering fixes16:11
*** openstack changes topic to "Generalized filtering fixes (Meeting topic: cinder)"16:11
smcginnisI wanted to bring this one up because I think we want to get this in stein.16:11
smcginnisBut I've also not been following things as closely.16:11
eharneyyeah, we should get it in if we can16:11
smcginnisSo hoping for input from whoami-rajat and eharney16:11
*** lpetrut has quit IRC16:12
smcginniseharney did mark it review-priority +1, so assuming so. So we also need some eyes on it.16:12
smcginniseharney: I think there was some question at some point about the correct approach to fix things. Is this where we want it now?16:12
smcginniseharney: You didn't +2 it, so wasn't sure if there were still questions.16:12
whoami-rajatI've been finding different cases and the ones i tested i've added so far, if anyone faces problems in any command as a non-admin user, they can notify me so i can append into the patch.16:13
eharneysmcginnis: it's the right approach -- the tricky part was to review it thoroughly enough to make sure there weren't any unexpected side effects, mostly around knowing that all of the correct checking exists around "all_tenants" for each resource etc16:13
smcginniswhoami-rajat: I see eharney pointed out a bug it should be linked to. Can we get that updated quick?16:13
*** rfolco has quit IRC16:14
whoami-rajatsmcginnis: sure will do.16:14
*** rfolco has joined #openstack-meeting16:14
smcginnisOK, I'll try to review later today, but call for help from other cores to check that out.16:15
whoami-rajatsmcginnis: done16:15
smcginnis#topic RSD driver follow up16:15
*** openstack changes topic to "RSD driver follow up (Meeting topic: cinder)"16:15
smcginniswhoami-rajat: THanks16:15
smcginnistejdeep: All yours.16:15
smcginnisI see this was on the agenda last week. Was there some follow up to cover?16:16
*** rfolco has quit IRC16:16
smcginnistejdeep: You around?16:17
*** rfolco has joined #openstack-meeting16:17
smcginnisWell, I'll move on since I'm not sure why we're covering new drivers in the meeting at this point anyway.16:17
smcginnis#topic cinderlib followup16:17
*** openstack changes topic to "cinderlib followup (Meeting topic: cinder)"16:17
smcginnisgeguileo: You have the floor.16:18
geguileoso this is a follow up of last week patches16:18
geguileothere's been some reviews and iterations, but they are still pending16:18
geguileobut the most important one is the one that fixes the package16:18
geguileowhich is currently broken (my bad)16:18
*** tejdeep_ has joined #openstack-meeting16:18
geguileoso now I've split the publish to pypi patch in 216:19
geguileothe fix of the package in cinderlib16:19
*** tejdeep_ has quit IRC16:19
geguileosorry, that's the pypi job that's now in project-config16:19
geguileothis is the one that fixes cinderlib:
geguileoit's important to get ^ merged16:19
*** tejdeep_ has joined #openstack-meeting16:20
*** tejdeep has quit IRC16:20
geguileowithout it we cannot built tarballs16:20
smcginnisAdded to my review queue.16:20
geguileosmcginnis: thanks!!!16:20
*** _pewp_ has quit IRC16:20
tejdeep_hi sorry i lost connection while giving update16:20
geguileoand the distros need the tarballs to test their packages for Stein release16:20
smcginnisYeah, we've merged most of it, so we should follow through and get it in good shape for stein.16:21
*** _pewp_ has joined #openstack-meeting16:21
geguileothat would be awesome16:21
geguileothat's all I had to say16:22
smcginnisOK, thanks geguileo16:22
smcginnis#topic RSD driver16:22
*** openstack changes topic to "RSD driver (Meeting topic: cinder)"16:22
smcginnistejdeep_: Was there some follow up from last week?16:22
*** jbadiapa has joined #openstack-meeting16:22
tejdeep_nothing, CI status looks good, just following up on merge status16:23
smcginnisWe're still wrapping up stein for a few more weeks yet. We will be looking at new drivers once we switch focus to train.16:24
smcginnis#topic Stable release update16:25
*** openstack changes topic to "Stable release update (Meeting topic: cinder)"16:25
smcginnisrosmaita: OK, on to you.16:25
rosmaitathe last stable releases were mid-February16:25
rosmaitathere hasn't been a lot of activity (except for cinder)16:25
rosmaitamy idea is to put up release patches next week when things should be kind of quiet after RC-1 and before final RCs16:25
rosmaitaone thing to keep in mind is that stable/pike is scheduled to go to 'extended maintenance' mode when stein is released16:26
smcginnisrosmaita: That seems like a good point to do it.16:26
rosmaitaok, cool16:26
rosmaitathat means we can continue to patch it, but no more releases16:26
rosmaitathere's only 1 change in os-brick stable/pike, and 1 patch with a -216:26
rosmaitathere are 2 changes in cinder stable/pike, and 1 patch having trouble getting through the gate16:26
smcginnisI've been meaning to send something out about extended maintenance to make sure teams are ready for that.16:26
*** _pewp_ has quit IRC16:26
*** mattw4 has joined #openstack-meeting16:26
rosmaitasomeone sent something out16:26
whoami-rajatrosmaita: are these the latest stats, i think many rocky backports merged recently.16:27
rosmaitayes, just looked, there are 10 backports unreleased in rocky16:27
smcginnisThere are several rocky patches queued up if they can get past job failure issues.16:27
rosmaitafor pike, i could hold off on releasing those until just before stein release (week of apr 8)16:27
rosmaitaor could just release next week with the rest, and then do one more if anything new is backported16:28
whoami-rajatsmcginnis: oh yes, they didn't merge due to the tempest issue16:28
smcginnisI think a few made it through, but a bunch still pending.16:28
rosmaitawell, i could hold off on cinder stable/rocky, or just do another one after all that stuff merges16:28
whoami-rajatrosmaita:  smcginnis can we wait until the rocky backports make their way until pike? i saw few important ones.16:29
smcginnisProbably no reason to hold off. They can always be picked up on the next stable release.16:29
rosmaitawhoami-rajat: so we will have to move fast on stuff going into pike16:29
smcginniswhoami-rajat: That would be good to backport as far as we can.16:29
smcginnisWe haven't always been good about that unless someone had a specific fix they wanted to get backported.16:30
*** mjturek has quit IRC16:30
smcginnisIt would be nice to have a better process around that.16:30
rosmaitathe other thing to keep in mind, is that pike is still "open" ... just won't be able to release from it after stein release april 10 or thereabouts16:30
whoami-rajatsmcginnis: i can start cherrrypicking for previous stable branches if its ok?16:30
smcginniswhoami-rajat: Definitely for anything that has merged in a later branch.16:31
whoami-rajatsmcginnis: ok thanks...16:31
smcginnisrosmaita: It's not a hard and fast rule on the transition. I think if we need a few extra days to finalize things we can get it.16:31
rosmaitasmcginnis: this was the email about pike extended maintenance:
smcginnisrosmaita: Oh yeah, I was part of the conversation that led to him sending that. :)16:32
rosmaitaok, so sounds like stable releases next week ... what about pike? release next week and then again if necessary?16:33
*** priteau has joined #openstack-meeting16:33
smcginnisThat sounds good. Let's get out what we have, then see if there's anything else we can get backported in time to get a good final release out before EM.16:33
rosmaitaok, great.  that's all from me16:34
smcginnisThanks for tracking that rosmaita16:34
smcginnis#topic Issue deploying cinder with gunicorn16:34
*** openstack changes topic to "Issue deploying cinder with gunicorn (Meeting topic: cinder)"16:34
smcginniswhoami-rajat: What? :)16:34
smcginnisWhere is gunicorn used and why do we care are my first thoughts. :]16:35
rosmaitayou are reading my mind16:35
whoami-rajatadriant tried deploying cinder with gunicorn but faced an issue,16:35
*** mattw4 has quit IRC16:36
e0nesmcginnis: +116:36
e0newhy do we need gunicorn for api?16:36
smcginniswhoami-rajat: Is there more context to that? Why do we care?16:36
whoami-rajatthe gunicorn application func required 2 mandatory fields which wasn't present here,16:37
*** igordc has quit IRC16:37
whoami-rajatoh just wanted to ask if anyone tried that way, it should be possible to use other servers to deploy cinder right?16:37
smcginnisOfficially we just support running behind a web server like apache or nginx I think.16:38
e0neI would like to say that we support only wsgi servers for API16:38
smcginnisLooks like gunicorn is a wsgi server16:39
whoami-rajatyes it is16:39
*** altlogbot_2 has joined #openstack-meeting16:40
whoami-rajatwe currently run on uWSGI IMO16:40
smcginnisI guess if there's a non-intrusive way that we can make it not blow up with it, but doesn't have an impact on anything else, I'd be fine merging any fix for it.16:40
eharneypresumably there would be similar changes in other openstack projects?16:40
smcginnisBut I don't think we should put much time into caring about it unless there's some overall effort to make gunicorn a "standard" deployment method.16:41
*** altlogbot_2 has quit IRC16:41
whoami-rajateharney: adriant said he would be trying deploying keystone next and check if he face the same error, will follow up with him on that16:41
*** igordc has joined #openstack-meeting16:42
rosmaitais gunicorn considered a production server?16:42
whoami-rajatsmcginnis: agreed, just felt like deployers should have flexibility.16:42
whoami-rajatrosmaita: yes.16:42
smcginniswhoami-rajat: Would be good it it was a cross-project effort.16:42
whoami-rajatsmcginnis: yes it would be, i will follow up with him regarding other projects too.16:43
e0nesmcginnis: I agree. if only cinder supports gunicorn, it makes less sense to me even for stand alone mode16:43
whoami-rajatoh keystone is using flask, he said he would be trying glance. my bad.16:44
e0neif we decide to add gunicorn support, we need to have it on CI or it will be broken16:44
smcginnisWe have so many things that need attention right now, so I'd rather we don't put much effort into something like this until it becomes more of a priority for the community.16:44
e0nesmcginnis: +116:44
whoami-rajate0ne: smcginnis  ++16:44
*** awaugama has joined #openstack-meeting16:44
smcginnis#topic Open floor16:45
*** openstack changes topic to "Open floor (Meeting topic: cinder)"16:45
smcginnisAlong those lines, another plea for folks to take a look at what we have out there and identify the things that are important to get in for stein.16:45
smcginnisTime is running out.16:45
*** iyamahat has quit IRC16:45
whoami-rajat i would like to request reviews on this since this maybe the last one of api-ref samples to go in stein.16:46
*** mjturek has joined #openstack-meeting16:46
smcginnisAfter the RC tomorrow, we really should only get bugfixes in for any further RCs. Anything that is not a straight bug fix should get attention over the next 24 hours or so if we want it in stein.16:47
*** hjensas has joined #openstack-meeting16:47
eharneywhat does that patch do exactly?  says it adds "tests"?16:47
eharneyi guess i don't know how functional tests related to api-ref samples, which i thought were for documentation16:49
smcginnisI'm wondering now if we should have written up a spec to at least document what that is all doing.16:49
*** yamahata has quit IRC16:49
smcginniswhoami-rajat: Do you have a quick overview of how this all ties in?16:49
eharneyhow functional tests are related to*16:49
smcginnisMy understanding is, the functional tests capture the API request/response that can then be used for the examples in the api-ref.16:50
e0neif it's only tests, why don't hold on it until Train?16:50
smcginnisBut I'm not sure what the whole process looks like.16:50
smcginnisYeah, also not sure it's that big of a priority that we can't just wait until train.16:50
eharneyis it only tests?  i thought api-ref was used for doc16:50
whoami-rajateharney:  smcginnis with new features being added, our api-ref isn't always updated, running these tests will auto generate the responses that are examples in the api-ref guide.16:50
smcginniswhoami-rajat: Is it a manual process to then have someone take the output from the functional tests and update the api-ref?16:51
*** mattw4 has joined #openstack-meeting16:51
whoami-rajateharney: these are tests as it fails the gate when someone tries to manually interfere with the natural responses of api16:51
whoami-rajatsmcginnis: these are autogenerated16:51
smcginnisHow is the api-ref updated automatically? That's a separate job that's run in gate.16:52
whoami-rajaton second thoughts we can hold it since bug fixes are more critical than this one. e0ne16:52
*** jamesmcarthur has quit IRC16:52
*** armax has joined #openstack-meeting16:53
smcginnisIt is trivial enough, since it's just tests and documentation, that we could maybe still backport it later if we decide to.16:53
*** jamesmcarthur has joined #openstack-meeting16:53
eharneydoes stein currently have incorrect api-ref materials?  or just that some are missing?16:53
whoami-rajatsmcginnis: since i'm implementing the base responses currently its not an issue, but for every MV update there will be a separate response,16:53
smcginniswhoami-rajat: I'm wondering if it might be useful to post something to the ML explaining what the overall process of this is so we at least have something to refer to if someone needs to understand how this is supposed to work.16:54
whoami-rajateharney: there were several mistakes and people were manually updating it with several patches, so gmann  proposed to implement it just like nova did to not have human errors in it.16:54
smcginnisOr maybe better, add something to the cinder contributor docs explaining it.16:54
smcginnisOh right, this is following something that Nova already did, right?16:54
whoami-rajatsmcginnis: sure, i can put up a doc for it.16:55
whoami-rajatsmcginnis: yes but they haven't clearly documented it. :(16:55
smcginnisThanks, I think that would help having something written down.16:55
smcginnis4 minutes left. Anything else important to cover in the meeting?16:55
*** thgcorrea has quit IRC16:55
eharneyis cinderclient done for stein now?16:56
smcginnisOne final plea for folks to look for things that we should make sure we get into stein.16:56
smcginniseharney: Yeah, client lib freeze was a couple weeks ago.16:56
eharneydid we release it?16:56
eharney4.1.0 was in october..?16:57
*** thgcorrea has joined #openstack-meeting16:57
rosmaitawell, maybe not, then16:57
smcginnispewp -
smcginnisNothing super critical at least. No new features.16:58
*** mattw4 has quit IRC16:58
smcginnisWe can get what we really need backported and a stable release done once freeze is over.16:59
eharneyyeah, nothing huge in there at least, but should we look for a 4.1.1 soonish, or what?16:59
smcginnisOK, out of time.16:59
smcginnisThanks everyone.17:00
*** openstack changes topic to "OpenStack Meetings ||"17:00
openstackMeeting ended Wed Mar 20 17:00:12 2019 UTC.  Information about MeetBot at . (v 0.1.4)17:00
openstackMinutes (text):
*** woojay has left #openstack-meeting17:01
*** tejdeep_ has quit IRC17:02
*** luizbag has left #openstack-meeting17:03
*** mattw4 has joined #openstack-meeting17:03
*** mattw4 has quit IRC17:05
*** patchbot has joined #openstack-meeting17:07
*** jbadiapa has quit IRC17:07
*** e0ne has quit IRC17:07
*** mattw4 has joined #openstack-meeting17:09
*** yamamoto has joined #openstack-meeting17:11
*** thgcorrea has left #openstack-meeting17:12
*** iyamahat has joined #openstack-meeting17:14
*** mjturek has quit IRC17:19
*** altlogbot_2 has joined #openstack-meeting17:26
*** yamamoto has quit IRC17:27
*** altlogbot_2 has quit IRC17:28
*** armax has quit IRC17:28
*** altlogbot_0 has joined #openstack-meeting17:30
*** yamamoto has joined #openstack-meeting17:30
*** yamamoto has quit IRC17:30
*** yamamoto has joined #openstack-meeting17:30
*** yamahata has joined #openstack-meeting17:31
*** yamamoto has quit IRC17:35
*** abishop_ has joined #openstack-meeting17:40
*** ttsiouts has quit IRC17:40
*** ttsiouts has joined #openstack-meeting17:41
*** sridharg has joined #openstack-meeting17:42
*** abishop has quit IRC17:43
*** rsimai_away is now known as rsimai17:44
*** rsimai is now known as rsimai_away17:44
*** ttsiouts has quit IRC17:46
*** armax has joined #openstack-meeting18:02
*** enriquetaso has quit IRC18:02
*** priteau has quit IRC18:04
*** raildo has quit IRC18:05
*** armax has quit IRC18:06
*** mjturek has joined #openstack-meeting18:07
*** mkarray has joined #openstack-meeting18:12
*** e0ne has joined #openstack-meeting18:17
*** ralonsoh has quit IRC18:19
*** kopecmartin is now known as kopecmartin|off18:19
*** irclogbot_1 has quit IRC18:21
*** brbowen has quit IRC18:23
*** dviroel_ has left #openstack-meeting18:23
*** irclogbot_3 has joined #openstack-meeting18:24
*** jrbalderrama has quit IRC18:24
*** hjensas has quit IRC18:26
*** irclogbot_3 has quit IRC18:27
*** irclogbot_3 has joined #openstack-meeting18:29
*** PrinzElvis has quit IRC18:30
*** clayg has quit IRC18:30
*** evgenyl has quit IRC18:30
*** sweston has quit IRC18:31
*** amito has quit IRC18:31
*** dougwig has quit IRC18:32
*** evgenyl has joined #openstack-meeting18:32
*** PrinzElvis_ has joined #openstack-meeting18:33
*** clayg has joined #openstack-meeting18:33
*** amito has joined #openstack-meeting18:33
*** sweston has joined #openstack-meeting18:33
*** diablo_rojo has joined #openstack-meeting18:33
*** _pewp_ has joined #openstack-meeting18:34
*** _pewp_ has quit IRC18:36
*** bbowen has joined #openstack-meeting18:38
*** sridharg has quit IRC18:38
*** _pewp_ has joined #openstack-meeting18:39
*** martial has joined #openstack-meeting18:42
*** dougwig has joined #openstack-meeting18:45
*** abishop_ has quit IRC18:50
*** abishop_ has joined #openstack-meeting18:51
*** abishop_ is now known as abishop18:52
*** e0ne has quit IRC18:53
*** altlogbot_0 has quit IRC19:00
SotK#startmeeting storyboard19:01
openstackMeeting started Wed Mar 20 19:01:16 2019 UTC and is due to finish in 60 minutes.  The chair is SotK. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:01
_pewp_[ MeetBot. - Debian Wiki ] - wiki.debian.org19:01
*** openstack changes topic to " (Meeting topic: storyboard)"19:01
openstackThe meeting name has been set to 'storyboard'19:01
*** rosmaita has left #openstack-meeting19:01
SotK#link Agenda19:01
_pewp_[ Meetings/StoryBoard - OpenStack ] - wiki.openstack.org19:01
*** altlogbot_3 has joined #openstack-meeting19:02
SotK#topic Announcements19:02
*** openstack changes topic to "Announcements (Meeting topic: storyboard)"19:02
SotKI don't think there are any things to announce this week19:02
diablo_rojoNone that I know of19:02
SotK#topic Migration Updates19:03
*** openstack changes topic to "Migration Updates (Meeting topic: storyboard)"19:03
SotKgoing off the agenda, looks like the same story here19:03
diablo_rojoand no patches from the NDSU students that Ive seen19:03
SotK#topic Outreachy19:04
*** openstack changes topic to "Outreachy (Meeting topic: storyboard)"19:04
SotKthere are many patches that we should review, since I think the submission deadline for applications is soon19:05
*** PrinzElvis_ is now known as PrinzElvis19:05
mkarrayJust out of curiousity, were all the outreachy contributions lowhanging stories?19:06
diablo_rojomkarray, I think basically all of them were19:06
*** altlogbot_3 has quit IRC19:06
diablo_rojoThey cleaned out out19:06
*** _pewp_ has quit IRC19:06
diablo_rojoI had to do a saturday triage to tag some more19:06
diablo_rojoBut I would guess those are now claimed too19:06
diablo_rojoI also think we might have some that are assigned but wont see patches for so we can wait a bit before un assigning them.19:06
*** _pewp_ has joined #openstack-meeting19:06
*** tssurya has quit IRC19:07
SotKI've already given a +2 to a number of the patches, but still have a heap to review19:07
*** altlogbot_0 has joined #openstack-meeting19:07
*** lpetrut has joined #openstack-meeting19:08
diablo_rojoI will do my due diligence today19:08
diablo_rojofungi, if you have some time to help us out it would be greatly appreciated19:08
SotKthanks :)19:08
SotK#topic Forum + PTG Planning19:09
*** openstack changes topic to "Forum + PTG Planning (Meeting topic: storyboard)"19:09
SotK#link Forum Session19:09
_pewp_[ Open Infrastructure Summit | Ibuprofen for Your StoryBoard Pain Points ] - www.openstack.org19:09
fungioh, yes indeed. reviewing19:09
SotKI should probably add that to my schedule19:10
fungidoes anybody claim this _pewp_ bot?19:10
fungiif not, i'll kick it19:10
diablo_rojofungi, a long time ago it was for doing table flips in the cinder meetings19:10
diablo_rojobut it seems to have evolved into something more obnoxious19:11
diablo_rojohemna_, ? ^^19:11
diablo_rojoBut yes SotK please add it to your schedule19:11
fungiyeah, if nobody's around to shut it up, i'll take care of it in a few19:11
*** efried_rolling is now known as efried19:11
smcginnishemna_: ^^19:12
SotKdoes the Thursday bug triage idea still sound good to folks?19:12
*** lpetrut has quit IRC19:12
diablo_rojoThursday works for me19:13
diablo_rojoSotK, you will still be around right?19:13
SotKyeah, I fly back on Saturday morning so just miss the last day19:13
fungisure, thursday at ptg sounds like a good time for that. i'll probably be splitting my time with other infra/opendev stuff but can pitch in19:14
*** irclogbot_3 has quit IRC19:16
diablo_rojoAs soon as the ptgbot is setup we can make a storyboard track and say hiding in the infra room or whatever19:16
*** tssurya has joined #openstack-meeting19:16
fungioff-topic for this meeting, but lmk if you want to take a stab at pushing up the denver config for ptgbot and i'm happy to review19:17
*** irclogbot_2 has joined #openstack-meeting19:17
*** hjensas has joined #openstack-meeting19:18
SotKsounds good to me19:18
SotK#topic In Progress Work19:18
*** openstack changes topic to "In Progress Work (Meeting topic: storyboard)"19:18
SotKmkarray: I believe you wanted to discuss some query structure stuff19:18
mkarraySo for some context, which items show up based on a query is defined by these objects which are usually scattered across the code
_pewp_[ storyboard-webclient/story.js at master · openstack-infra/storyboard-webclient · GitHub ] - github.com19:19
diablo_rojofungi, once we have the room names I think ttx or myself can handle that. Dont have all the details yet.19:20
*** _pewp_ has quit IRC19:21
mkarrayOriginally I was going to remove the limitation of one value per key, but after looking into it, it seems like the only key which has multiple values is User19:21
*** _pewp_ has joined #openstack-meeting19:21
mkarraythese consist of assignee_id, creator_id, subscriber_id, and user_id19:21
*** ChanServ sets mode: +b *!*@
*** _pewp_ was kicked by ChanServ (Banned: unofficial bots must be accompanied by an adult at all times while visiting the park)19:22
*** _pewp_ has quit IRC19:22
mkarrayit seemed sort of silly to remove the limitation just to fix it for that single key, so instead I think we should just make the values associated with the 'User' key, into their own keys. Like so:
mkarrayNow if we want to add or remove what can be searched on a storyboard component, we either just add or remove a key/value pair19:24
fungiseems fine to me. i guess we need to come up with new icons? that'll be the "hard part" ;)19:24
fungii honestly don't know why "user" got the amalgamation treatment there to begin with19:25
mkarrayI thought this was worth bringing up in the meeting because 1. What fungi said ^ and 2. It will require a file (I'll take care of this) for each key19:25
fungiyeah, that was the biggest unknown for me... is anybody aware of why that choice was made in the first place?19:25
mkarrayAnd yes fungi, I haven't seemed to find a purpose for merging them into one type either19:25
fungiit's entirely possible i'm just not aware19:25
fungiand that there was a good reason19:26
mkarrayI bugged Sotk about it back when I first hopped on the project, but he wasn't sure either at the time19:26
fungii think if none of the present maintainers are aware of what problem that was solving, it's probably enough reason to assume it was just happenstance/convenience19:27
*** vishalmanchanda has quit IRC19:27
fungii suppose there might be some benefit to preserving the old "user" key semantics in the webui so that existing query urls continue to work the same, and just no longer expose that in autocompletion?19:28
SotKI suspect it was just convenience19:28
SotKthe User there is the User $resource which maps to the /v1/users endpoint, so it would probably have to continue to exist to avoid lots of churn elsewhere19:29
fungiso effectively add the new assignee, creator and subscriber keys and have them do normal autocomplete; leave user as a viable url parameter which maps to assignee+creator but no longer gets included in autocompletion19:29
mkarrayWhat Sotk said. It would be useful just to avoid refactoring everything else in the process19:29
*** abishop has quit IRC19:30
SotKit gets mapped to assignee_id in urls at the moment anyway iirc19:30
*** irclogbot_2 has quit IRC19:30
mkarraythe links wont be affected,19:30
SotKits just needed for places we make general user-related queries in the code19:30
fungisounds like a solid plan to me in that case19:31
SotKbut yeah that paste looks nice to me, +1 to that approach19:31
diablo_rojoI think that all sounds like a good plan19:31
*** irclogbot_3 has joined #openstack-meeting19:31
fungimkarray: thanks for working on this! i think it'll be useful to a lot of folks19:32
mkarraygreat, ill crack away at a solution and commit it when I have a reasonable one19:32
mkarrayMy pleasure :)19:32
diablo_rojoSounds good.19:32
SotKyep, its much appreciated, thank you19:33
mkarrayThat's all for me on this subject19:33
SotKin other in progress work, I have many patches that need review :)19:33
diablo_rojoAnd for once we did you topic during the meeting with adequate time mkarray :)19:33
mkarrayprogress  is progress! diablo_rojo19:34
diablo_rojoI'm so on it.19:34
*** altlogbot_0 has quit IRC19:34
SotKa good portion of those are attachments-related, and the security team stuff is dependent on at least part of the attachment stuff at the moment, because that was easier than repeatedly up/downgrading my database19:35
fungiand trying to nail down the apparent performance regressions on the deployment19:35
*** artom has quit IRC19:35
SotKI'd especially appreciate review on
*** altlogbot_2 has joined #openstack-meeting19:36
fungiwhich i thought might have been cache memory pressure, but even after temporarily releiving that with a restart of the offending memory hogs SotK reports similar poor performance on loading stories19:36
diablo_rojoI'll start with those then.19:36
fungiare people successfully running storyboard on python 3 at this point? if so, it might make sense to try switching storyboard-dev over to using python 3.5 instead of 2.7 and see if it's still working, then look at a similar switch for storyboard.o.o19:37
SotKyeah, I run my development instance on 3.619:37
fungi3.6 for us will probably have to wait for container-based deployment, or at least ansible-driven puppetless deployment19:38
fungisince switching to a puppet which will work on a platform providing 3.6 is a bit of a hassle still19:38
fungi(we're still wrapping up transition to puppet 4, and we need puppet 5 on newer platforms)19:39
SotKI believe I've had success running on 3.5 in the past, but I don't remember for sure19:40
SotKI definitely think its worth trying out switching storyboard-dev19:40
fungii'll make a note on my todo list19:40
fungimostly curious if performance will be any better. but regardless we need to consider moving off python 2.7 by the end of this year19:40
fungii don't want storyboard devs stuck trying to maintain compatibility with a python which is past eol19:41
mkarraypython 2 loses support beginning of 2020 iirc, probably a good idea19:41
diablo_rojoAgreed. Not enough of us and not enough time19:42
SotKanything else in-progress that folk want to raise?19:44
*** hjensas has quit IRC19:45
funginothing i'm aware of19:45
mkarrayI pushed my first patch earlier this week, would be nice if any of you could review when there's some time19:45
fungiand thanks!19:45
diablo_rojomkarray, definitely will take a look today19:46
diablo_rojoCongratulations :)19:46
SotKI plan to catch up on my review backlog in the morning, so hopefully I'll get to it then :)19:46
fungii'd like to say i'll take a look today, but i'll have to see how the rest of my day goes19:46
mkarraySounds good, thanks all19:46
fungisun will be down here soon and i still have too many irons in the fire i think19:47
*** ChanServ sets mode: -b *!*@
*** awaugama has quit IRC19:48
diablo_rojofungi, theres always another day :)19:48
diablo_rojoSotK, thanks for running the meeting :)19:49
fungithere are no guarantees, but that's certainly what i hope for every nigvt when i go to sleep!19:49
diablo_rojofungi, lol thats dark19:49
*** eharney has quit IRC19:50
*** carlos_silva has left #openstack-meeting19:51
SotKthanks for coming folks!19:52
*** openstack changes topic to "OpenStack Meetings ||"19:52
openstackMeeting ended Wed Mar 20 19:52:12 2019 UTC.  Information about MeetBot at . (v 0.1.4)19:52
openstackMinutes (text):
fungithanks again SotK!19:52
fungihemna_: i've un-banned the ip address _pewp_ was joining from for now and it doesn't seem to have tried to reconnect, but please keep an eye on it19:52
*** igordc has quit IRC19:56
*** dhellmann has quit IRC19:57
*** hjensas has joined #openstack-meeting19:58
*** dhellmann has joined #openstack-meeting19:59
*** eharney has joined #openstack-meeting20:02
*** armax has joined #openstack-meeting20:06
*** rbudden has quit IRC20:07
hemna_fungi: will do20:10
hemna_I have bounced it a few times today trying to get some things fixed with it20:10
fungihemna_: cool, if it's going to join shared community channels like this one just please at least make sure it's silent during meetings you're not involved in20:13
*** eharney has quit IRC20:22
*** igordc has joined #openstack-meeting20:31
*** pfallenop has joined #openstack-meeting20:38
*** irclogbot_3 has quit IRC20:45
*** irclogbot_0 has joined #openstack-meeting20:47
*** pfallenop has quit IRC20:51
*** pfallenop has joined #openstack-meeting20:51
*** igordc has quit IRC20:51
*** igordc has joined #openstack-meeting20:52
*** e0ne has joined #openstack-meeting20:52
*** altlogbot_2 has quit IRC20:53
*** altlogbot_1 has joined #openstack-meeting20:55
*** zaitcev has joined #openstack-meeting20:58
*** ivy has quit IRC21:00
timburke#startmeeting swift21:00
openstackMeeting started Wed Mar 20 21:00:25 2019 UTC and is due to finish in 60 minutes.  The chair is timburke. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:00
*** openstack changes topic to " (Meeting topic: swift)"21:00
openstackThe meeting name has been set to 'swift'21:00
timburkewho's here for the swift meeting?21:00
*** mkarray has left #openstack-meeting21:00
mattoliverauwe know that kota_ and notmyname wont be here21:01
timburkeso we've got a pretty short agenda; perfect for me to try my hand running a meeting :-)21:01
timburkefirst up: release!21:02
timburke#topic Swift release21:02
*** openstack changes topic to "Swift release (Meeting topic: swift)"21:02
timburkethis'll be our last release for Stein21:02
timburkei put a handful of patches that i think would be good to get in on the priority reviews page21:03
timburkeand i think clayg has already approved one!21:03
timburke seems like it must be hurting zigo; i'd really like to make him whole21:03
patchbotpatch 633671 - swift - Fix decryption for broken objects - 8 patch sets21:03
claygthe easy one21:04
timburke was tangentially related to that21:04
patchbotpatch 634507 - swift - encryption: Be more tolerant of errors while decry... - 2 patch sets21:04
timburkeand fixes a bunch of bugs and already has a +221:04
patchbotpatch 571905 - swift - Fix quoting for large objects - 5 patch sets21:04
timburkebeyond that, we've got a bunch of great stuff currently working its way through the gate21:05
claygOMG p 571905 scares me - do we ALWAYS need to quote when we make a subrequest with a path built by hand like that... probably!?21:05
patchbot - swift - Fix quoting for large objects - 5 patch sets21:05
timburkeclayg, 99% sure, yeah21:05
timburkeand once it all lands, we'll tag a release! unless anyone has patches to advocate for that i'm not thinking of21:06
timburkeso... anybody got patches that should land ahead of a release?21:06
clayghow long do we have to get that all landed?  you and kota fixed up p 637662 for me21:06
patchbot - swift - Simplify empty suffix handling (MERGED) - 4 patch sets21:06
timburkeyeah, i was going to add that, then i realized i could just approve it ;-)21:07
claygbut you know p 644691 hasn't made sufficient sacrifice to the zuul21:07
patchbot - swift - Remove uncalled function - 1 patch set21:07
*** Lucas_Gray has joined #openstack-meeting21:07
*** mjturek has quit IRC21:07
timburkeall right, i'll assume the current patchlist is pretty good then21:08
*** iyamahat_ has joined #openstack-meeting21:08
mattoliverauI'd have to look at other patches, but they look good.21:08
timburkefeel free to message me later to know that i'm wrong ;-)21:08
timburkenext up, updates!21:08
timburke#topic losf21:09
*** openstack changes topic to "losf (Meeting topic: swift)"21:09
clayg@timburke wait... how long do we have?21:09
timburkeoh, right: final deadline is end of the week next week, but with notmyname out of town next week, i'm treating friday as deadline21:09
clayg@timburke do we have to land everything on the page?  oh... no just that top catagory - ok21:09
*** iyamahat has quit IRC21:10
timburkehmm... with kota_ and alecuyer not here... i guess i'll let rledisez offer losf updates?21:10
rlediseztimburke: i'm not completly aware of everything, but I know alecuyer was working on tests21:11
rledisezhe wrote an ansible playbook for zuul21:11
rledisezand I can't really say more21:11
patchbotpatch 644879 - swift (feature/losf) - WIP - start working on ansible playbooks for LOSF - 1 patch set21:11
timburkecool! love that we're moving toward tests running with it in the gate21:12
timburkeonly other agenda item was py3 updates21:12
timburke#topic py321:12
*** openstack changes topic to "py3 (Meeting topic: swift)"21:12
timburkei've seen a bunch of stuff from zaitcev and mattoliverau lately (feel free to offer your own updates)21:13
timburkewe've got a (nonvoting) py37 unit test job now21:13
zaitcevI don't know, I was away for a week on customer cases. Didn't do a thing for py3 until today.21:13
mattoliverauI've done some reviews and attempting to write a py3 port patch:
patchbotpatch 643855 - swift - py3: port staticweb middleware - 4 patch sets21:14
timburkeand once one of the patches in the recheck-cycle pands, py37 will even pass!21:14
mattoliverauprobably still needs some work21:14
mattoliverautimburke: \o/21:14
timburkemattoliverau, yeah, i'm hoping to look at it today -- i'm wondering if the func test failure may actually be legit21:15
mattoliverauoh yeah, I should probably look more closely at the func tests. I'll poke today.21:15
timburkei'll work on getting rebased, too, and hopefully by next week i'll have a follow-up to run that test in the gate21:16
patchbotpatch 642520 - swift - Get functional/ running under py3 - 8 patch sets21:16
mattoliveraugetting func tests would make the py3 stuff feel more stable :)21:16
timburkei think that's about all i've got for py321:17
timburke#topic open discussion21:17
*** openstack changes topic to "open discussion (Meeting topic: swift)"21:17
claygI think this was the most well run meeting evar - you're hired21:17
zaitcevI'm actually looking at mattoliverau's staticweb thing... It's getting a 412 in what I presume a py2 environment, which is really strange.21:17
timburkeclayg, glad you approve :-) also, too late if you *don't* like it :P21:17
mattoliverauzaitcev: I could also have done something wrong, /me is learning this crazy py3 stuff ;)21:18
mattoliverauwe now know that it's notmyname and kota_ that slow down the meeting ;P21:18
*** eharney has joined #openstack-meeting21:19
timburkeso, i know has been going a while; zaitcev has a +2, rledisez still seemed to have some questions... i wonder if that would be a good thing to try to get in after the release21:20
patchbotpatch 601950 - swift - Enable to configure object-expirer in object-serve... - 11 patch sets21:20
timburkei feel like we've been talking about it forever21:20
zaitcevIt's Kazuhiro's thing, isn't it. Seems fine, although it's only a stepping stone to the distributed expirer, if I remember right.21:20
zaitcevOh, BTW21:21
claygwhoa - after the release - that's like next week business21:21
timburkeright. in part, i want to make sure that he can move forward on that; the general task queue seems like a useful thing21:21
zaitcevDid you guys see what I dregged out from my pile of old patches - patch 7051321:21
patchbot - swift - Add Guru Meditation - 3 patch sets21:21
timburkei did just notice that!21:21
timburkeseems interesting21:22
zaitcevImagine a patch so old that creiht reviewed it21:22
timburkenotmyname just lol'ed21:22
timburkeliterally; he's over my shoulder now21:22
zaitcevAnd we never merged it, because Swift almost never hungs, so there is no need for a tool to diagnose hungs.21:23
timburke...then torgomatic needed to write ...21:24
rledisezzaitcev: so, it can help when process are hanging? if so, i'm interrested21:24
zaitcevBut this week I had a customer case come in with updaters hanging for no reason. I suspect a bug in eventlet in case when os is not monkey-patched, so we fork while holding eventlet's internal pipes, and then the forked processes do something to each other over that pipe. Or something. Either way it hungs.21:24
claygidk, lp bug #1820893 sure feels like a hung replication object-server - allthough all signs just point to a forever growing backlog of REPLICATE requests 😞21:25
openstackLaunchpad bug 1820893 in OpenStack Object Storage (swift) "Unable to limit number of REPLICATE requests per drive" [Undecided,New]
* clayg is trying to think if he's ever seen hung object-updaters...21:25
zaitcevOuch, I wish I knew python-stack-xray was a thing.21:26
timburkeit takes a bit to learn how to read the stacks, but it's been super-helpful for me before21:26
timburkei'll try to take a look at the meditation patch, at least get an idea of what it's doing21:27
zaitcevIf you have a moment.21:28
timburkeanybody else have anything to bring up?21:28
*** whoami-rajat has quit IRC21:29
timburkeall right, i'm'a call it21:30
timburkethank you all for coming, and thank you for working on swift!21:30
*** openstack changes topic to "OpenStack Meetings ||"21:30
openstackMeeting ended Wed Mar 20 21:30:47 2019 UTC.  Information about MeetBot at . (v 0.1.4)21:30
openstackMinutes (text):
mattoliveraunice work timburke21:30
*** zaitcev has left #openstack-meeting21:30
*** patchbot has left #openstack-meeting21:31
*** _pewp_ has joined #openstack-meeting21:38
*** _pewp_ has quit IRC21:40
*** _pewp_ has joined #openstack-meeting21:40
*** _pewp_ has quit IRC21:43
*** _pewp_ has joined #openstack-meeting21:43
*** e0ne has quit IRC22:00
*** njohnston has quit IRC22:09
*** pcaruana has quit IRC22:11
*** iyamahat_ has quit IRC22:16
*** iyamahat_ has joined #openstack-meeting22:17
*** mriedem is now known as mriedem_away22:25
*** yamamoto has joined #openstack-meeting22:45
*** yamamoto has quit IRC22:49
*** Lucas_Gray has quit IRC22:51
*** armax has quit IRC22:55
*** rcernin has joined #openstack-meeting22:57
*** rcernin has quit IRC22:58
*** rcernin has joined #openstack-meeting22:58
*** jamesmcarthur has quit IRC23:23
*** hongbin has quit IRC23:23
*** mriedem_away has quit IRC23:28
*** mriedem has joined #openstack-meeting23:29
*** jamesmcarthur has joined #openstack-meeting23:32
*** jamesmcarthur has quit IRC23:38
*** jamesmcarthur has joined #openstack-meeting23:38
*** rf0lc0 has joined #openstack-meeting23:47
*** rfolco has quit IRC23:49
*** artom has joined #openstack-meeting23:57

Generated by 2.15.3 by Marius Gedminas - find it at!