Wednesday, 2019-02-20

*** artom has joined #openstack-meeting00:00
*** liuyulong has quit IRC00:04
*** number80 has quit IRC00:13
*** markvoelker has quit IRC00:15
*** number80 has joined #openstack-meeting00:20
*** b1airo has quit IRC00:21
*** jamesmcarthur has quit IRC00:22
*** jamesmcarthur has joined #openstack-meeting00:23
*** jamesmcarthur has quit IRC00:27
*** macza has quit IRC00:29
*** mlavalle has quit IRC00:32
*** lbragstad has quit IRC00:34
*** sdake has joined #openstack-meeting00:59
*** lbragstad has joined #openstack-meeting01:01
*** hongbin has joined #openstack-meeting01:07
*** markvoelker has joined #openstack-meeting01:12
*** mattw4 has quit IRC01:23
*** igordc has quit IRC01:30
*** markvoelker has quit IRC01:44
*** yamamoto has joined #openstack-meeting01:45
*** yamamoto has quit IRC01:45
*** yamamoto has joined #openstack-meeting01:46
*** tetsuro has joined #openstack-meeting01:50
*** eharney has quit IRC02:08
*** igordc has joined #openstack-meeting02:15
*** whoami-rajat has joined #openstack-meeting02:31
*** sdake has quit IRC02:36
*** jamesmcarthur has joined #openstack-meeting02:37
*** yaawang has joined #openstack-meeting02:37
*** markvoelker has joined #openstack-meeting02:41
*** macza has joined #openstack-meeting02:52
*** macza has quit IRC02:57
*** JangwonLee has joined #openstack-meeting03:02
*** psachin has joined #openstack-meeting03:04
*** apetrich has quit IRC03:14
*** markvoelker has quit IRC03:15
*** jamesmcarthur has quit IRC03:21
*** jamesmcarthur has joined #openstack-meeting03:22
*** jamesmcarthur has quit IRC03:27
*** jamesmcarthur has joined #openstack-meeting03:44
*** larainema has joined #openstack-meeting03:46
*** jamesmcarthur has quit IRC03:59
*** jamesmcarthur has joined #openstack-meeting04:00
*** jamesmcarthur has quit IRC04:05
*** jamesmcarthur has joined #openstack-meeting04:09
*** markvoelker has joined #openstack-meeting04:12
*** imsurit_ofc has joined #openstack-meeting04:13
*** jamesmcarthur has quit IRC04:22
*** janki has joined #openstack-meeting04:22
*** jamesmcarthur has joined #openstack-meeting04:25
*** sridharg has joined #openstack-meeting04:26
*** jamesmcarthur has quit IRC04:30
*** lbragstad_ has joined #openstack-meeting04:36
*** lbragstad has quit IRC04:37
*** markvoelker has quit IRC04:44
*** jamesmcarthur has joined #openstack-meeting04:53
*** diablo_rojo has quit IRC04:55
*** jamesmcarthur has quit IRC04:59
*** hongbin has quit IRC05:04
*** igordc has quit IRC05:08
*** igordc has joined #openstack-meeting05:20
*** lbragstad has joined #openstack-meeting05:23
*** lbragstad_ has quit IRC05:25
*** cloudrancher has joined #openstack-meeting05:26
*** lbragstad_ has joined #openstack-meeting05:29
*** ociuhandu_ has quit IRC05:30
*** ociuhandu has joined #openstack-meeting05:30
*** lbragstad has quit IRC05:31
*** lbragstad has joined #openstack-meeting05:41
*** markvoelker has joined #openstack-meeting05:42
*** lbragstad_ has quit IRC05:43
*** cloudrancher has quit IRC05:52
*** k4ch0 has joined #openstack-meeting05:53
*** lbragstad_ has joined #openstack-meeting05:57
*** lbragstad has quit IRC05:58
*** dmacpher_ has quit IRC06:00
*** markvoelker has quit IRC06:15
*** yaawang has quit IRC06:15
*** lbragstad has joined #openstack-meeting06:20
*** lbragstad_ has quit IRC06:22
*** k4ch0 has quit IRC06:22
*** sdake has joined #openstack-meeting06:26
*** sdake has quit IRC06:27
*** igordc has quit IRC06:31
*** macza has joined #openstack-meeting06:34
*** macza has quit IRC06:38
*** cloudrancher has joined #openstack-meeting06:39
*** Luzi has joined #openstack-meeting06:52
*** markvoelker has joined #openstack-meeting07:01
*** jamesmcarthur has joined #openstack-meeting07:18
*** yamamoto has quit IRC07:19
*** jamesmcarthur has quit IRC07:22
*** aojea has joined #openstack-meeting07:23
*** e0ne has joined #openstack-meeting07:25
*** apetrich has joined #openstack-meeting07:37
*** cloudrancher has quit IRC07:55
*** pcaruana has joined #openstack-meeting07:59
*** ralonsoh has joined #openstack-meeting08:07
*** kopecmartin|off is now known as kopecmartin08:09
*** jchhatbar has joined #openstack-meeting08:09
*** jchhatbar has quit IRC08:10
*** yamamoto has joined #openstack-meeting08:10
*** yamamoto has quit IRC08:10
*** jchhatbar has joined #openstack-meeting08:11
*** yamamoto has joined #openstack-meeting08:11
*** janki has quit IRC08:11
*** yamamoto has quit IRC08:13
*** yamamoto has joined #openstack-meeting08:13
*** yamamoto has quit IRC08:13
*** lbragstad has quit IRC08:15
*** ttsiouts has joined #openstack-meeting08:22
*** tssurya has joined #openstack-meeting08:22
*** cschwede has joined #openstack-meeting08:23
*** rcernin has quit IRC08:29
*** yamamoto has joined #openstack-meeting08:38
*** yamamoto has quit IRC08:38
*** yamamoto has joined #openstack-meeting08:38
*** nguyenhai has joined #openstack-meeting08:40
*** nguyenhai has quit IRC08:40
*** electrofelix has joined #openstack-meeting08:45
*** yamamoto has quit IRC08:49
*** ociuhandu has quit IRC09:00
*** gibi has quit IRC09:00
*** tetsuro has quit IRC09:12
*** yamamoto has joined #openstack-meeting09:13
*** cloudrancher has joined #openstack-meeting09:18
*** ociuhandu has joined #openstack-meeting09:24
*** ociuhandu has quit IRC09:29
*** e0ne has quit IRC09:33
*** kopecmartin is now known as kopecmartin|afk09:37
*** zaneb has quit IRC09:53
*** ociuhandu has joined #openstack-meeting09:57
*** markvoelker has quit IRC10:01
*** markvoelker has joined #openstack-meeting10:02
*** markvoelker has quit IRC10:06
*** yamamoto has quit IRC10:11
*** yamamoto has joined #openstack-meeting10:14
*** yamamoto has quit IRC10:19
*** priteau has joined #openstack-meeting10:22
*** priteau has quit IRC10:28
*** gibi has joined #openstack-meeting10:32
*** jgriffith has quit IRC10:49
*** erlon has joined #openstack-meeting10:50
*** ianychoi has quit IRC10:59
*** yamamoto has joined #openstack-meeting11:02
*** markvoelker has joined #openstack-meeting11:03
*** JangwonLee has quit IRC11:05
*** yamamoto has quit IRC11:07
*** ttsiouts has quit IRC11:13
*** ttsiouts has joined #openstack-meeting11:13
*** ttsiouts has quit IRC11:18
*** yamamoto has joined #openstack-meeting11:20
*** thgcorrea has joined #openstack-meeting11:27
*** yamamoto has quit IRC11:34
*** markvoelker has quit IRC11:36
*** yamamoto has joined #openstack-meeting11:36
*** yamamoto has quit IRC11:37
*** yamamoto has joined #openstack-meeting11:37
*** yamamoto has quit IRC11:42
*** yamamoto has joined #openstack-meeting11:42
*** yamamoto has quit IRC11:47
*** e0ne has joined #openstack-meeting11:54
*** dmacpher has joined #openstack-meeting11:57
*** ttsiouts has joined #openstack-meeting11:59
*** erlon has quit IRC12:04
*** erlon has joined #openstack-meeting12:06
*** kopecmartin|afk is now known as kopecmartin12:07
*** erlon has quit IRC12:07
*** erlon_ has joined #openstack-meeting12:07
*** erlon__ has joined #openstack-meeting12:09
*** erlon_ has quit IRC12:13
*** janki has joined #openstack-meeting12:14
*** imsurit_ofc has quit IRC12:15
*** jchhatbar has quit IRC12:15
*** raildo has joined #openstack-meeting12:30
*** cloudrancher has quit IRC12:30
*** macza has joined #openstack-meeting12:31
*** markvoelker has joined #openstack-meeting12:33
*** macza has quit IRC12:35
*** liuyulong has joined #openstack-meeting12:43
*** sridharg has quit IRC12:52
*** psachin has quit IRC13:01
*** cloudrancher has joined #openstack-meeting13:02
*** psachin has joined #openstack-meeting13:04
*** markvoelker has quit IRC13:05
*** jrbalderrama has quit IRC13:07
*** JangwonLee has joined #openstack-meeting13:11
*** nnsingh has left #openstack-meeting13:11
*** enriquetaso has joined #openstack-meeting13:14
*** jamesmcarthur has joined #openstack-meeting13:18
*** jamesmcarthur has quit IRC13:22
*** jamesmcarthur has joined #openstack-meeting13:22
*** ianychoi has joined #openstack-meeting13:22
*** mriedem has joined #openstack-meeting13:28
*** electrofelix has quit IRC13:31
*** jamesmcarthur has quit IRC13:33
*** bbowen has joined #openstack-meeting13:41
*** njohnston_ has quit IRC13:47
*** yamamoto has joined #openstack-meeting13:50
*** jamesmcarthur has joined #openstack-meeting13:51
*** jamesmcarthur has quit IRC13:51
*** jamesmcarthur has joined #openstack-meeting13:52
*** jchhatbar has joined #openstack-meeting13:52
*** jchhatbar has quit IRC13:53
*** jchhatbar has joined #openstack-meeting13:54
*** janki has quit IRC13:54
*** vishakha has joined #openstack-meeting13:55
*** mlavalle has joined #openstack-meeting14:00
mlavalle#startmeeting neutron_l314:01
openstackMeeting started Wed Feb 20 14:01:49 2019 UTC and is due to finish in 60 minutes.  The chair is mlavalle. Information about MeetBot at http://wiki.debian.org/MeetBot.14:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:01
*** openstack changes topic to " (Meeting topic: neutron_l3)"14:01
openstackThe meeting name has been set to 'neutron_l3'14:01
liuyulonghi14:02
mlavalleGood evening14:02
mlavalleWelcome to our first L3 meeting on Wednesday14:02
mlavalle#chair liuyulong14:02
openstackCurrent chairs: liuyulong mlavalle14:02
*** markvoelker has joined #openstack-meeting14:02
liuyulongIt is not merged yet, https://review.openstack.org/#/c/637900/14:03
mlavalleoh yeah14:03
mlavallelet me ping the infra guys14:03
*** mpiwowarczy has joined #openstack-meeting14:04
mlavalleok, posted a review request there14:05
mlavalleliuyulong: this is a better time for you, right?14:07
liuyulongYeah, it is14:08
liuyulongAnd it is also better for most east Asia developers. : )14:09
mlavallehow ready do you feel to start running this meeting?14:09
mlavallein fact, in the patch I replaced my name with yours as meeting chair14:09
*** sdake has joined #openstack-meeting14:10
*** mkarray has quit IRC14:12
liuyulongYes, I noticed that, I think I need some more time, since I have a lot of works from my employer after a really long holiday.14:12
mlavalleok, just let us know when you feel ready14:14
liuyulongBut it will not be too long, I think I will talk to you guys about running this meeting in our next 1-1 conversation.14:14
mlavalleok14:15
*** ttsiouts has quit IRC14:15
mlavalleI will still be attending the meetings anyway. So I can always help14:15
*** ttsiouts has joined #openstack-meeting14:15
mlavalleThis week I am going to take some time to clean up the etherpad14:16
slaweqhi14:16
slaweqsorry, I wasn't sure if that is already changed14:16
mlavallehttps://etherpad.openstack.org/p/neutron-l3-subteam14:17
mlavalleslaweq: I think we got caught in a bit of a gray area14:17
mlavallethe patch hasn't merged14:17
mlavallebut we mentioned last week that we were going to have the meeting this week on Wednesday14:18
slaweqsure, that's fine for me :)14:18
mlavalleso I started the meeting and have been chatting with liuyulong14:18
*** sdake has quit IRC14:18
mlavallewe are talking about him taking the chair of this eeting14:18
mlavallemeeting^^^14:19
slaweqyeah, I saw logs in the channel already14:19
mlavalleso, let's move on14:20
mlavalle#topic Announcements14:20
*** openstack changes topic to "Announcements (Meeting topic: neutron_l3)"14:20
mlavalleWe have our Stein-3 milestone around the corner, week of March 7th14:20
mlavalleand there is a TC election going on14:23
fungithe meeting schedule update has just been approved, so you should see it update on the schedule within the next few minutes14:23
mlavalleThank you!14:24
fungi(sorry we didn't see it before your meeting time!)14:24
mlavallefungi: well, sorry I jumped the gun and started the meeting anyway ;-)14:25
liuyulongfungi, thank you14:25
fungiit's just a formality. nobody minds as long s you're not taking up someone else's scheduled slot ;)14:25
*** cloudrancher has quit IRC14:25
liuyulongmlavalle, we do not see your TC candidacy14:25
mlavalleliuyulong: you are not going to see one, at least not for the time being14:26
mlavalleok, let's look at bugs14:26
mlavalle#topic Bugs14:26
*** openstack changes topic to "Bugs (Meeting topic: neutron_l3)"14:26
mlavallewe have this freshly filed bug by Swami: https://bugs.launchpad.net/neutron/+bug/181669814:29
openstackLaunchpad bug 1816698 in neutron "DVR-HA: Removing a router from an agent, does not clear the namespaces on the agent" [High,Confirmed]14:29
*** yamamoto has quit IRC14:29
*** yamamoto has joined #openstack-meeting14:30
mlavalleI'll verify that this bug happens with master14:30
slaweqI would like to see logs from l3 agent in such case14:31
slaweqbut it might be an issue with rootwrap filters also14:31
*** eharney has joined #openstack-meeting14:32
*** lbragstad has joined #openstack-meeting14:32
mlavalleslaweq: I agree that it might be a result of the rootwrap issue14:33
mlavalleby the way, the same with https://bugs.launchpad.net/neutron/+bug/178943414:33
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:33
slaweqmlavalle: I also today saw some similar issues on Ocata14:33
slaweqbut those were related to keepalived process14:33
slaweqin filters we have kill filter for /usr/sbin/keepalived and L3 agent was failing with that14:33
slaweqbut when we changed it to "keepalived" (without full path) it worked fine14:34
slaweqso, that's why I would like to see logs for that :)14:34
*** sdake has joined #openstack-meeting14:34
*** cloudrancher has joined #openstack-meeting14:35
*** priteau has joined #openstack-meeting14:35
mlavalleok14:35
mlavallegood points14:35
slaweqmlavalle: I can take a look at https://bugs.launchpad.net/neutron/+bug/1789434 if You want14:36
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
*** markvoelker has quit IRC14:36
mlavalleslaweq: yes, please go ahead14:36
slaweqI will unmark those tests as unstable and check in logs how it will be then14:36
slaweqok14:36
mlavalleand remove the assignment to manjeets14:36
slaweqok, will do14:37
mlavalleand I'm working on https://bugs.launchpad.net/neutron/+bug/179587014:37
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:37
mlavallewhich seems to be caused by the now infamous lack of rootwrap filter for killing state change monitor14:38
mlavalleI have a fix proposed here https://review.openstack.org/#/c/636710/14:38
mlavalleand I'll refine it with dougwig's comments14:38
mlavalleany other bugs we should discuss today?14:39
slaweqyes14:39
slaweqI have one14:39
slaweqhttps://bugs.launchpad.net/neutron/+bug/181677114:39
openstackLaunchpad bug 1816771 in neutron "Creation of router fails in devstack" [Undecided,New]14:39
slaweqI just opened it14:40
slaweqas frickler asked me about that14:40
*** lbragstad_ has joined #openstack-meeting14:40
slaweqit failed on creating router so I added L3 tags to it14:40
*** electrofelix has joined #openstack-meeting14:40
slaweqbut it might be that it is related to https://review.openstack.org/#/c/635671/ which was merged today14:40
mlavalledo we need help triaging it?14:41
*** lbragstad has quit IRC14:41
slaweqmlavalle: I think so14:41
mlavalleok, I'll probably take a look14:41
slaweqtbh I have no idea why it failed like that14:41
slaweqbut looks like somehow related to db :)14:42
liuyulongThis is worthy to backport to our stable branches.14:42
slaweqliuyulong: are You talking about https://review.openstack.org/#/c/635671/ ?14:42
liuyulongYes14:42
slaweqI agree but lets first ensure that it didn't introduce any regression in master :)14:43
mlavalleliuyulong: let's wait a bit. Let's dig first into the bug just filed by slaweq14:43
slaweqmlavalle++14:43
liuyulongsURE14:43
haleybhi, i didn't know this weeks meeting was changing14:44
liuyulongI will update one mentioned in last l3 meeting: https://bugs.launchpad.net/neutron/+bug/179249314:44
openstackLaunchpad bug 1792493 in kolla-ansible "DVR and floating IPs broken in latest 7.0.0.0rc1?" [Undecided,New]14:44
liuyulonghttps://bugs.launchpad.net/neutron/+bug/1792493/comments/1514:44
liuyulong^^14:45
mlavalleliuyulong: thanks14:45
mlavallehaleyb: welcome to the first ever L3 meeting on Wednesday :-)14:45
haleyb:)14:45
mlavalle#topic Openflow DVR14:46
*** openstack changes topic to "Openflow DVR (Meeting topic: neutron_l3)"14:46
*** davidsha has joined #openstack-meeting14:47
mlavalledavidsha: welcome14:47
davidsha*Pretends I was here the whole tme*14:47
davidshaHey14:47
mlavalleprobably xuubozhang didn't realize the change this week14:47
mlavalleso I am going to send a message to the ML to make sure everybody is aware of the change14:48
davidshaNot yet,  Igor is working on the linux/ovs backend part atm I think14:48
mlavalleyeah, that's what I thought14:48
davidshaXubo is drafting the unit tests for the ovs-dvr patch atm.14:48
mlavalleok, let's move on14:48
mlavalleThanks for the update!14:49
mlavalle#topic On demand agenda14:49
*** openstack changes topic to "On demand agenda (Meeting topic: neutron_l3)"14:49
mlavalleanything else we should discuss today?14:49
mlavalleok, thanks for attending14:50
slaweqthanks o/14:50
mlavalleenjoy the rest of your week14:50
davidshathanks!14:50
mlavalle#endmeeting14:51
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"14:51
openstackMeeting ended Wed Feb 20 14:51:01 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:51
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_l3/2019/neutron_l3.2019-02-20-14.01.html14:51
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_l3/2019/neutron_l3.2019-02-20-14.01.txt14:51
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_l3/2019/neutron_l3.2019-02-20-14.01.log.html14:51
*** jamesmcarthur has quit IRC14:53
*** lbragstad has joined #openstack-meeting14:53
*** lbragstad_ has quit IRC14:54
*** jgriffith has joined #openstack-meeting14:55
*** jgriffith has quit IRC14:56
*** lbragstad_ has joined #openstack-meeting14:56
*** mlavalle has left #openstack-meeting14:56
*** awaugama has joined #openstack-meeting14:56
*** sdake has quit IRC14:58
*** lbragstad has quit IRC14:58
*** lbragstad_ has quit IRC14:58
*** woojay has joined #openstack-meeting14:59
*** woojay has left #openstack-meeting14:59
*** lbragstad has joined #openstack-meeting15:01
*** efried is now known as efried_pto15:02
*** mjturek has joined #openstack-meeting15:07
*** enriquetaso has quit IRC15:08
*** Luzi has quit IRC15:11
*** lbragstad_ has joined #openstack-meeting15:12
*** lbragstad has quit IRC15:13
*** lbragstad_ is now known as lbragstad15:18
*** jchhatbar has quit IRC15:19
*** markvoelker has joined #openstack-meeting15:33
*** mpiwowarczy has quit IRC15:43
*** cloudrancher has quit IRC15:56
*** rosmaita has joined #openstack-meeting15:57
*** woojay has joined #openstack-meeting15:58
*** ttsiouts has quit IRC15:58
*** enriquetaso has joined #openstack-meeting15:59
*** ttsiouts has joined #openstack-meeting15:59
jungleboyj#startmeeting cinder16:00
openstackMeeting started Wed Feb 20 16:00:46 2019 UTC and is due to finish in 60 minutes.  The chair is jungleboyj. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
*** openstack changes topic to " (Meeting topic: cinder)"16:00
openstackThe meeting name has been set to 'cinder'16:00
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
gouthamro/16:01
*** e0ne has quit IRC16:01
geguileohi! o/16:01
eharneyhi16:01
rosmaitao/16:01
yikuno/16:01
whoami-rajatHi16:01
smcginniso/16:01
jungleboyj@!16:01
_pewp_jungleboyj (。・∀・)ノ16:01
*** ganso has joined #openstack-meeting16:02
*** e0ne has joined #openstack-meeting16:02
enriquetasoo/16:02
gansohello16:02
jungleboyjHello from Snowy Minnesota.16:03
rosmaitahello from snowy Virginia :)16:03
* jungleboyj is getting very tired of this winter16:03
* jungleboyj waves16:03
e0nehi16:03
*** ttsiouts has quit IRC16:03
*** ttsiouts has joined #openstack-meeting16:05
tbarronjungleboyj: :) just remembering 12 years in Minneapolis16:05
jungleboyjOk, should probably get started as we have a good number of topics today.16:05
e0nejungleboyj: it's in Kharkiv, my home city about month ago https://www.objectiv.tv/wp-content/uploads/2018/01/1-239.jpg16:05
xyanghi16:05
smcginnise0ne: Haha, that looks fun.16:05
jungleboyjxyang:  ?  Who is xyang ?  ;-)16:05
xyang:)16:06
jungleboyjOk.16:06
*** markvoelker has quit IRC16:06
jungleboyj#topic Announcements16:06
*** openstack changes topic to "Announcements (Meeting topic: cinder)"16:06
rosmaitae0ne: i am ashamed to have mentioned the 2 inches of snow i shoveled this morning16:06
jungleboyje0ne:  Yikes, thanks for putting it in perspective.  :-)16:07
e0ne:)16:07
*** cloudrancher has joined #openstack-meeting16:07
jungleboyj#link https://releases.openstack.org/stein/schedule.html16:07
jungleboyjSo, the week of 3/4 is feature freeze.  So we should be winding down development and starting to focus on testing and bug fixes.16:08
smcginnisDon't forget that next week is non-client lib freeze too (os-brick).16:09
jungleboyjWhich leads into the first topic I have below.16:09
jungleboyjsmcginnis:  Ah, thank you.16:09
smcginnishttps://review.openstack.org/#/q/project:openstack/os-brick+status:open16:09
jungleboyjI will take a look at those open reviews.16:10
jungleboyjgeguileo: and hemna_  it would be good to have your input as well.16:11
geguileojungleboyj: ok16:12
jungleboyjsmcginnis:  Anything more on that topic from you?16:12
smcginnisNo, just that client lib freeze is soon after that.16:12
smcginnisSo don't forget those python-cinderclient patches either.16:12
jungleboyjOk.  Cool.16:12
jungleboyjYeah, would be good to make sure we get everything merged that go along with server changes.  We have been bad about that in the past.16:13
*** yamamoto has quit IRC16:13
e0nethere is nothing important to release in https://review.openstack.org/#/q/project:openstack/python-brick-cinderclient-ext++status:open16:13
jungleboyjOk.  Moving on.16:13
jungleboyje0ne: Good.16:14
jungleboyj#topic checkup on feature implementation16:15
*** openstack changes topic to "checkup on feature implementation (Meeting topic: cinder)"16:15
jungleboyj#link https://etherpad.openstack.org/p/cinder-spec-review-tracking16:15
jungleboyjSo, we didn't do the best job of keeping the spec tracking list updated this time around.  :-(16:15
jungleboyjWant to just ask about a few of the things that were of higher priority.16:16
*** yamamoto has joined #openstack-meeting16:16
e0nejungleboyj: can we switch to priorities dashboard in gerrit in the next release?16:16
jungleboyjsmcginnis:  We talked about the upgrade checker goal in RTP.16:16
smcginnise0ne: ++16:16
jungleboyje0ne:  ++16:16
jungleboyjYes, I think that would help.16:17
smcginnisYep. We've met the goal requirement, but would still be great if someone could look through upgrade release notes to see if there's anythign important we should add to that.16:17
jungleboyjsmcginnis:  That is right.  That was where that was left.16:18
jungleboyjsmcginnis:  I will take the TODO there.  I think I might have done that at the PTG.16:18
jungleboyj#action jungleboyj to review release notes for appropriate checks16:18
* jungleboyj put it on my whiteboard16:19
e0nejungleboyj: did you mean snowboard?16:20
jungleboyje0ne:  Looks like you moved out the Generic Backup Implementation16:20
jungleboyje0ne:  :-p16:20
jungleboyj@!j16:20
_pewp_jungleboyj (._.) ~ ︵ ┻━┻16:20
*** igordc has joined #openstack-meeting16:20
e0nejungleboyj: TBH, I didn't push https://review.openstack.org/#/c/630305/ to get everything ready for generic backups this release :(16:20
*** yamamoto has quit IRC16:21
jungleboyje0ne:  Yeah.  I think it is something we want to push in the future though because people are interested in it.16:21
e0nejungleboyj: I'll finish with unit tests asap and propose generic backup patch but obviously it's too late in a release cycle for such change16:21
e0neI have to propose a spec movement to Train16:22
jungleboyje0ne:  Ok.  Fair enough.16:22
jungleboyje0ne:  Anything more on that?16:23
e0neI'll be glad to have some feedback on https://review.openstack.org/#/c/630305/ and https://review.openstack.org/#/c/620881/16:24
e0neI rebased these patches against master16:24
e0ne(just before I read meeting agenda)16:24
jungleboyjBut we want to hold those two for Train?16:25
e0nehttps://review.openstack.org/#/c/620881/ looks pretty safe but it's up to the team16:25
jungleboyjOk.  Well, we can work that through the review.16:26
e0nejungleboyj: thank you!16:26
jungleboyje0ne:  No problem.  Thanks for continuing to push stuff in Cinder.  :-)16:26
*** cloudrancher has quit IRC16:26
jungleboyjeharney:  Drivers Capability Reporting ...16:26
e0neI'll do my best to finally finish this effort in Train16:26
jungleboyjThink based on the discussion at the mid-cycle this should be a priority in Train.16:27
eharneyi'm working on a spec for this but it's definitely not going very far for Stein16:27
eharneyyeah16:27
jungleboyjeharney:  Actually, that would be a good topic for the Forum with follow up at the PTG.16:27
eharneyi will probably miss the forum part, but, yes16:28
jungleboyjGet input on what users might really want there.16:28
jungleboyjOk, I have a good enough idea of what I would like to see that I could run the session.  Just make sure to get on the same page with you before the forum.16:28
jungleboyjI will champion that topic.16:28
jungleboyjOk.  So that makes sense.16:29
jungleboyjLooks like the API to re-image an attached volume will also need to move to train?16:29
*** cloudrancher has joined #openstack-meeting16:30
jungleboyjyikun: ^^16:30
e0ne+116:30
smcginnismriedem: If you're around - anything going on with that boot volume reimage work on the nova side?16:30
yikunyou mean re-image available/reserved volume?16:31
jungleboyjyikun:  I thought it was an attached volume.16:31
mriedemit's attached16:32
*** cloudrancher has quit IRC16:32
mriedemwell, technically reserved, but yes we're splitting hairs16:32
jungleboyj:-)16:32
mriedemsmcginnis: the original dev working on the nova changes dropped off16:32
yikunwe were prepared to only support reseved/available volume in Stein release.16:32
*** macza has joined #openstack-meeting16:32
mriedemKevin_Zheng was working on updating the nova side stuff but it's not a priority for him since he has other stuff he was originally assigned to16:32
*** ttsiouts has quit IRC16:33
mriedemsmcginnis: so with 2 weeks left, i'm not holding out much hope that everything will be merged without some major help and review on the nova side16:33
jungleboyjmriedem:  Ok, so not something we should be trying to push to get into Stein.16:33
mriedemi don't think so16:33
*** ttsiouts has joined #openstack-meeting16:33
jungleboyjOk.  We will keep pulling that along.16:34
jungleboyjgeguileo: I think you got changes for shared_targets improvements in and they didn't get recorded in the etherpad.16:34
jungleboyjgeguileo:  Is there more that needs to be done there?16:35
geguileojungleboyj: Once we release os-brick I need to land the Nova patch16:35
geguileobut nothing more afaik16:36
jungleboyjgeguileo:  Ok.  Cool.  Any concerns with getting the Nova patch landed?16:36
geguileojungleboyj: not really, it's a trivial patch16:36
geguileoremoves code with a context manager, cleaning their code16:36
jungleboyjgeguileo:  Ok.  Cool.  So mriedem shouldn't harass us.  ;-)16:36
geguileoXD16:37
jungleboyj👮‍♀️16:37
jungleboyjOk.  I think we are good there so we should move on as we have more to cover.16:38
*** ttsiouts has quit IRC16:38
jungleboyj#topic Adding similar type of functionalities under one mv before release16:38
*** openstack changes topic to "Adding similar type of functionalities under one mv before release (Meeting topic: cinder)"16:38
jungleboyjwhoami-rajat:16:38
*** hongbin has joined #openstack-meeting16:38
jungleboyjWe talked about this a bit in channel before the meeting.16:38
jungleboyjAnyone have concerns with updating a MV ed change without incrementing the MV given that we haven't released it yet.16:39
e0neay concerns from my side16:39
whoami-rajatjungleboyj: also the changes are almost serving similar functionalities.16:39
eharneywe should probably revise our microversion rules doc a bit to cover this case of small adjustments for changes we've made recently16:40
smcginnisMy take is, we've never stated we would support continuous deployment, so we should be fine.16:40
e0neit could affect only if somebody uses cinder from master in a production16:40
e0neeharney: +116:40
eharneythe current doc indicates we should bump mv again for this, but i agree it's better to be pragmatic here16:40
jungleboyjeharney:  ++16:40
eharneyhttps://git.openstack.org/cgit/openstack/cinder/tree/doc/source/contributor/api_microversion_dev.rst16:41
jungleboyjOk, does anyone want to take the TODO to update the doc?16:41
jungleboyjIf not I can take a stab at it.16:41
jungleboyjShould be a simple change.16:42
whoami-rajatjungleboyj:  i will do it.16:42
jungleboyjwhoami-rajat:  Awesome.  Thanks.16:42
whoami-rajatsince i'm the one violating it :)16:42
jungleboyj#action whoami-rajat to update documentation on micro version policies.16:43
smcginniswhoami-rajat: Thanks!16:43
whoami-rajatsmcginnis:  np :)16:43
jungleboyjwhoami-rajat: Yes,  Thank you.  Your contributions are greatly appreciated.16:44
jungleboyj#topic Denver Forum and Summit Planning16:44
*** openstack changes topic to "Denver Forum and Summit Planning (Meeting topic: cinder)"16:44
jungleboyj#link https://etherpad.openstack.org/p/cinder-denver-forum-brainstorming16:44
whoami-rajatjungleboyj:  wouldn't be possible with all the great help i get here. Thanks for that :)16:44
jungleboyj#link https://etherpad.openstack.org/p/cinder-train-ptg-planning16:45
jungleboyjwhoami-rajat:  Awwww shucks.  :-)16:45
*** gyee has joined #openstack-meeting16:45
jungleboyjSo, I have put together etherpads for the Forum and PTG planning.16:45
jungleboyjFigured we should create both etherpads now as there are going to be topics that are appropriate for each venue brought up.16:45
jungleboyjThe Forum ones are reviewed first though, so please take a few minutes to add anything in there that may be appropriate to discuss with operators.16:46
jungleboyjI will be adding the capabilities topic in there.16:46
jungleboyjAppreciate your attention to the etherpads.16:48
jungleboyjI think that is all I have to say there.16:48
jungleboyj#topic Continued discussion with regards to Storyboard ...16:48
*** openstack changes topic to "Continued discussion with regards to Storyboard ... (Meeting topic: cinder)"16:48
e0neI'm OK to use storyboard now16:49
jungleboyje0ne:  Ok.16:49
e0newe're using it in vitrage since Rocky release and it works good16:49
jungleboyjThe issue I saw during the mid-cycle was resolved.16:49
e0newe can't use it in horizon now because it doesn't support attachements16:50
rosmaitathat's going to be a problem for security bugs, too16:50
jungleboyje0ne:  The attachments stuff is being fixed right now.16:50
enriquetasowhere can I find the link to the storyboard?16:50
e0nejungleboyj: oh.. thanks for letting me know16:51
jungleboyjI have gotten feedback from diablo_rojo on the design we talked about at the mid-cycle16:51
e0neenriquetaso: https://storyboard.openstack.org16:51
jungleboyj#link https://etherpad.openstack.org/p/cinder-launchpad-design16:51
enriquetasoe0ne++16:51
jungleboyjThe test migration is here:  https://storyboard-dev.openstack.org/#!/project/47316:51
jungleboyjSo, that is the current status.16:52
jungleboyjNow we have Cinderlib coming into place and we need to decide if it will use Storyboard for the bug tracking or not.16:52
jungleboyjsmcginnis:  Raised concerns that Cinder is still using Launchpad.16:52
jungleboyjThough, the bug tracking for os-brick has been in its own part of launchpad.16:53
smcginnisYeah, fine I guess if we just have the one using SB.16:53
jungleboyjWe could use cinderlib and os-brick as the starting points for migration.16:53
smcginnisBut with the tight coupling between cinderlib and the drivers in openstack/cinder, I was concerned there would be a lot of overlap.16:54
jungleboyjStart with cinderlib and then re-address as we go forward.16:54
geguileoI think we can start with cinderlib16:55
geguileothen migrate os-brick16:55
*** aojea has quit IRC16:55
geguileoand then we can continue with others...16:55
rosmaitaonly problem i see is if we want to use the "also affects project" in launchpad16:55
smcginnisAny reason to wait on os-brick? Or want to get one there and figure out usage first?16:55
geguileoI think we can also move os-brick now16:55
smcginnisrosmaita: Exactly. I was thinking we may have a few of those when it comes to this.16:56
geguileoI was just mentioning in case we wanted to be extra careful16:56
jungleboyjsmcginnis:  I would like to get how we want to use Storyboard actually documented and mocked out in the test migration.16:56
smcginnisOr... we just rip off the bandaid and migrate everything over and not have to be concerned about which ones are where.16:56
geguileojungleboyj: then I can just change the cinderlib project to use launchpad16:56
geguileoand then we continue with our current plan16:57
jungleboyjThe process will be a bit of overkill for cinderlib but I think it is a good way for us to get used to launchpad and propose fixes.16:57
jungleboyjI am fine with moving os-brick as well.16:57
enriquetasoShould we add the storyboard's number to gerrit's patchs?16:57
whoami-rajatone query. how will the migration process work exactly? will it automatically report all the existing bugs from launchpad to storyboard or is there any manual intervention?16:58
jungleboyjenriquetaso:  For os-brick or cinderlib patches, yes.16:59
smcginnisenriquetaso: Yes, once a project is migrated we will want to link patches to the story like we currently do with launchpad bugs.16:59
jungleboyjNot for CInder yet.16:59
jungleboyjwhoami-rajat:  It is an automatic migration they run.16:59
geguileojungleboyj: I think I'm getting more and more convinced by smcginnis' idea of adding cinderlib to launchpad16:59
geguileoXD16:59
jungleboyjgeguileo:  Wait, what?16:59
geguileolol17:00
rosmaitai vote we wait to move until nova has migrated17:00
geguileojungleboyj: if you want to have things documented before migrating os-brick17:00
geguileothen it makes sense to have cinderlib together with the other projects17:00
jungleboyjgeguileo: :-p  I am trying to push myself to make some progress here.17:00
geguileojungleboyj: me too, I want to get the cinderlib project in17:01
smcginnis++17:01
geguileoand it looks like launchpad is easier, and it makes more sense17:01
*** cloudrancher has joined #openstack-meeting17:01
geguileoin the cinder context17:01
jungleboyjOk.  We are supposed to wrap up here .  Lets finish in the cinder channel.17:01
geguileorosmaita: ++17:01
smcginnisGetting it in is more important than us using storyboard, IMO.17:01
geguileorosmaita: sounds like a good idea, wait until Nova!!!!!!!17:01
rosmaitai'm worried that since we had to move cinderlib to its own repo and don't have cross-project testing set up/possible, don't want to have another place where bugs can fall through the cracks17:01
jungleboyjLets finish this in channel.17:02
jungleboyj#endmeeting17:02
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"17:02
openstackMeeting ended Wed Feb 20 17:02:11 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:02
openstackMinutes:        http://eavesdrop.openstack.org/meetings/cinder/2019/cinder.2019-02-20-16.00.html17:02
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/cinder/2019/cinder.2019-02-20-16.00.txt17:02
openstackLog:            http://eavesdrop.openstack.org/meetings/cinder/2019/cinder.2019-02-20-16.00.log.html17:02
*** markvoelker has joined #openstack-meeting17:03
*** e0ne has quit IRC17:04
*** psachin has quit IRC17:04
*** ganso has left #openstack-meeting17:04
*** tssurya has quit IRC17:07
jungleboyj@!h geguileo17:10
_pewp_jungleboyj (/ .□.) ︵╰(゜Д゜)╯︵ /(.□. )17:10
*** pcaruana has quit IRC17:13
*** enriquetaso has quit IRC17:13
*** carlos_silva has joined #openstack-meeting17:13
*** woojay has left #openstack-meeting17:14
*** davidsha has quit IRC17:17
*** ircuser-1 has quit IRC17:26
*** cloudrancher has quit IRC17:29
*** yamamoto has joined #openstack-meeting17:30
*** enriquetaso has joined #openstack-meeting17:35
*** markvoelker has quit IRC17:36
*** ociuhandu_ has joined #openstack-meeting17:39
*** mattw4 has joined #openstack-meeting17:42
*** ociuhandu has quit IRC17:42
*** ociuhandu_ has quit IRC17:43
*** ociuhandu has joined #openstack-meeting17:54
*** ociuhandu has quit IRC17:58
*** factor has quit IRC17:58
*** cloudrancher has joined #openstack-meeting17:59
*** thgcorrea has quit IRC17:59
*** diablo_rojo has joined #openstack-meeting18:01
*** cloudrancher has quit IRC18:01
*** bbowen has quit IRC18:03
*** bbowen has joined #openstack-meeting18:03
*** sdake has joined #openstack-meeting18:04
*** ircuser-1 has joined #openstack-meeting18:04
*** kopecmartin is now known as kopecmartin|off18:15
*** ociuhandu has joined #openstack-meeting18:16
*** priteau has quit IRC18:21
*** jgriffith has joined #openstack-meeting18:21
*** enriquetaso has quit IRC18:21
*** factor has joined #openstack-meeting18:26
*** markvoelker has joined #openstack-meeting18:33
*** hongbin has quit IRC18:33
*** ralonsoh has quit IRC18:34
*** mkarray has joined #openstack-meeting18:48
*** martial has quit IRC18:49
*** e0ne has joined #openstack-meeting18:50
*** njohnston_ has joined #openstack-meeting18:51
*** sdake has quit IRC18:58
*** njohnston_ has quit IRC19:00
*** ivoline has joined #openstack-meeting19:04
*** njohnston has joined #openstack-meeting19:04
*** markvoelker has quit IRC19:06
*** e0ne has quit IRC19:10
*** sdake has joined #openstack-meeting19:13
SotK#startmeeting storyboard19:13
openstackMeeting started Wed Feb 20 19:13:47 2019 UTC and is due to finish in 60 minutes.  The chair is SotK. Information about MeetBot at http://wiki.debian.org/MeetBot.19:13
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:13
*** openstack changes topic to " (Meeting topic: storyboard)"19:13
openstackThe meeting name has been set to 'storyboard'19:13
fungithe suspense was unbearable! ;)19:13
SotKhaha19:14
SotKhopefully its worth the wait :D19:14
SotK#link https://wiki.openstack.org/wiki/Meetings/StoryBoard Agenda19:14
SotK#topic Announcements19:14
*** openstack changes topic to "Announcements (Meeting topic: storyboard)"19:14
SotKI don't have anything to announce, anyone else?19:14
funginothin19:15
mkarrayI'm good19:15
diablo_rojoNo announcements19:15
SotK#topic Migration Updates19:16
*** openstack changes topic to "Migration Updates (Meeting topic: storyboard)"19:16
SotKanything?19:16
fungikarbor has expressed an interest in moving from lanchpad to storyboard19:16
fungiwaiting to hear back from them on the change review19:16
diablo_rojoLooks like Karbor is migrating on their own accord19:16
diablo_rojoThere a patch right fungi ?19:16
SotKnice19:17
fungi#link https://review.openstack.org/636574 Update karbor to use storyboard19:17
fungiyep, that one19:17
diablo_rojoCinder also had a new lib that they were creating and were going to set up in storyboard19:18
diablo_rojobut I think I saw chatter this morning in their meeting about just wanting to get the patch in and now talking about making it in lp instead19:18
fungithey had second thoughts at the last moment (i didn't follow the discussion in their meeting)19:18
fungior rather slightly after the last moment19:18
fungii'm working out the db queries now to remove their unused project and project group and the associated mapping19:19
SotKyeah, they seemed to be concerned about ending up half in one tool and half in the other19:19
fungiif so, that's a reasonable concern19:19
SotKyep19:19
fungimost project teams migrate all their projects at once19:19
diablo_rojoWe could always migrate the rest of their stuff right now too ;)19:21
SotKI think the outcome of their discussion was to try to migrate during Train after having more discussions about workflows f2f at the PTG19:22
*** hongbin has joined #openstack-meeting19:23
SotKany other updates?19:23
fungias an update, i've dumped a copy of the db just in case and then deleted the associated records from the projects, project_groups and project_group_mapping tables19:23
fungigotta delete from project_group_mapping first because of foreign key constraints, it appears19:24
fungiand no, i don't have any other migration updates at the moment19:24
SotKoh, I forgot about that table19:24
SotK#topic Story Attachments19:24
*** openstack changes topic to "Story Attachments (Meeting topic: storyboard)"19:24
diablo_rojoWell thats sad that they are pushing it to Train. They had previously said Stein.,19:25
SotK#link https://review.openstack.org/#/q/status:open+topic:story-attachments19:25
fungilooks like diablo_rojo has reviewed about half of them. making me look bad! ;)19:26
SotKdiablo_rojo: it is, but hopefully it helps them feel more prepared19:26
SotKindeed, thanks for the reviews so far :D19:26
fungii'll try to go over those at least so we can get some of it merged quickly19:26
SotKthanks19:26
fungifor 3-week-long definitions of "quickly" i guess :/19:27
diablo_rojoHa ha ha19:27
diablo_rojoyeah I will finish reviewing those this week19:27
SotKhas anyone given thought to how to go about actually using it in production?19:27
SotKas in, around storage providers and such?19:27
SotKs/providers/donors/19:28
fungii need to have those conversations still19:28
fungiclarkb: ^ when you're not fishing, that's something we should probably bring up with the rest of the infra team19:28
diablo_rojoWe should get that on the infra agenda next week19:28
fungior talk through it sooner19:29
fungithat's 6 days away19:29
fungi#action fungi find a home for storing storyboard.openstack.org's attachments19:29
SotKyeah, the sooner the better as far as I'm concerned :)19:30
*** e0ne has joined #openstack-meeting19:30
fungiright, it'll take us some time to set up and figure out how we want to manage it, so getting that discussion going in parallel is warranted19:30
SotKwe should probably hold off on merging the webclient patches either until I've stopped the error that happens when attachments are disabled or we are ready to turn them on19:31
SotKhopefully I'll get that done or started before the next meeting19:31
SotKcan't promise anything though19:31
SotKbut I don't want to have to field complaints about red error messages on every story :D19:32
fungiahh, yeah, got a pointer to where the error is raised?19:32
*** rfolco has quit IRC19:32
diablo_rojoYeah okay. Hold off on webclient patches then19:33
*** enriquetaso has joined #openstack-meeting19:33
SotKthe issue is just that the webclient has no way of checking whether or not the API supports attachments and just always makes a request to get the attachments for a story19:34
SotKwith an old backend or a backend with attachments disabled that doesn't work and causes a (harmless) error to be displayed19:35
fungiyeah, maybe the api can just return an empty set for that query rather than an error when attachments aren't configured?19:35
fungilet the webclient always request attachments and make it a successful no-op for the api19:36
SotKyou can see it in action in the js preview: http://logs.openstack.org/12/633612/2/check/build-javascript-content/8309dae/npm/html/#!/story/119:36
fungi(brainstorming)19:36
SotKthat works for the retrieval side, but all the uploading UI will also be visible but non-functional19:37
fungiahh, right-o19:37
fungiso maybe we do need a webclient config option to toggle support19:37
SotKyeah, that's what we've done in the past19:37
SotK(for editable comments for example)19:38
fungisure19:38
SotKbut I'm increasingly feeling like both of these should be things that the webclient finds out from the API its pointed at19:38
*** electrofelix has quit IRC19:38
fungiyeah, a means of exposing configuration info from the api would be better design in the end, completely agree19:39
*** rfolco has joined #openstack-meeting19:39
SotKanything else on attachments?19:39
fungisome boolean methods like enabled_comment_editing, enabled_story_attachments, and so on19:40
fungii don't have any questions, nope. just need to get rolling on reviewing and discussing storage19:40
diablo_rojoNothing from me19:41
SotKindeed, or even making better use of the existing /v1/system_info endpoint19:41
SotK#topic Moving database closer to the site19:41
*** openstack changes topic to "Moving database closer to the site (Meeting topic: storyboard)"19:41
SotKthis is done now I think, thanks fungi!19:41
fungiyou're most welcome19:41
*** e0ne has quit IRC19:41
fungias also seen with storyboard-dev, we do experience rather heavy database query activity around loading boards/worklists19:42
fungibut this puts us in a better place to start doing some profiling of the production workload there and figuring out our hotspots19:42
* diablo_rojo takes it off agenda so we dont bring it up next week too19:42
SotKyep, hopefully we can start making some good improvements19:43
fungii just need to wrangle some help from some of our more relational-database-savvy contributors19:43
fungishould take advantage of the fact that we have former mysql developers on hand ;)19:44
fungi(several)19:44
SotKheh, yes19:44
SotK#topic Outreachy Intern19:45
*** openstack changes topic to "Outreachy Intern (Meeting topic: storyboard)"19:45
fungi#action fungi find out if some of our mysqlish folks have query profiling recommendations19:45
diablo_rojoCall for proposals is open19:45
SotK#link https://etherpad.openstack.org/p/sb-train-outreachy-planning19:45
diablo_rojoI was thinking optimizing database queries.19:45
diablo_rojoBut am open to other ideas\19:45
fungiit's a reasonable one to add there if you think that's not too much for an outreachy timeframe19:46
*** bbowen has quit IRC19:47
diablo_rojoI think if its broken down into small fixes at a time its doable19:47
diablo_rojoMaybe not quite as fun as working on an entire feature19:47
diablo_rojo?19:47
SotKsounds like an interesting one to me, but it might be dependent on folk with sufficient expertise being around to give advice19:47
diablo_rojoYeah thats fair.19:48
diablo_rojoI definitely am not the most qualified19:48
SotKif entire features are deemed more fun, maybe looking at implementing an "official" way of handling duplicates would be nice19:48
SotKor perhaps some of the board-related improvements that were discussed way back in Dublin (I'm not sure if they're written up anywhere)19:49
fungidare i say, overhauling the continuous testing may fit?19:49
diablo_rojoWe should decide on one thing. Maaaaaybe two.19:50
diablo_rojoThe application process was a pain last time19:50
*** sdake has quit IRC19:50
fungiwe've got an attempt at fixing the defect with private stories not sending e-mail notifications, blocked on being unable to actually write a working regression test, because the current test framework is rather inscrutible19:50
diablo_rojoEither of those sound good too if we think we can get other people to do the db query optimizations19:51
diablo_rojoYeah thats true19:51
fungijust from a personal pain-point perspective... folks reporting security vulnerabilities in private end up having to ping me to let me know they opened them because sb can't notify me19:51
*** e0ne has joined #openstack-meeting19:51
SotKyeah, fixing the tests would be good too but I suspect it won't sound like interesting work on an internship proposal19:52
* SotK could be wrong19:52
fungifixing that is likely not hard, but being unable to test that we don't break it in the future would be better19:52
mkarrayDo we currently have the ability to export a list into a CSV through the GUI?19:52
fungithat i'll agree with. qa/test work rarely looks glamorous on paper19:53
SotKmkarray: we don't, but it'd likely be fairly trivial to write a python script to generate one using the api19:54
*** vishakha has quit IRC19:54
fungimkarray: that also sounds useful, but i think we also don't have a shortage of feature requests which have already been prioritized19:54
fungiso it's more about coming up with one of those which would be tractable for (and attractive to) an intern to tackle19:54
*** bbowen has joined #openstack-meeting19:55
mkarraySounds good19:55
diablo_rojoI think we put the test one up last time, but it didn't get chosen19:55
fungisince the idea with outreachy is that there is an intern being paid to complete whatever assignment(s) we choose19:55
diablo_rojoWe can try again.19:55
fungino, i agree with SotK it's probably unlikely to garner much interest19:56
diablo_rojoSo either duplicates or query optimization?19:56
fungier, i should restate, the idea with outreachy is that there is an intern being paid to complete whatever assignment(s) THEY choose from the ones we suggest19:56
mkarrayAs an intern myself the query optimization task seems pretty cool19:57
*** njohnston has quit IRC19:57
fungiso we're sort of competing for offering work which will make them want to work on our project rather than another one19:57
*** njohnston has joined #openstack-meeting19:57
diablo_rojoI feel like we might be able to write both of them in time, but I will prioritize the query one first?19:58
SotKyeah I think if we're picking two then those two make sense, and if just one then I think I'd lean to the query optimisation19:58
*** njohnston has quit IRC19:58
fungiwe're running out of time on our meeting slot, btw19:59
SotKindeed, lets finish over in #storyboard :)19:59
fungithanks SotK!19:59
SotK#endmeeting19:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"19:59
diablo_rojothanks SotK !19:59
openstackMeeting ended Wed Feb 20 19:59:39 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/storyboard/2019/storyboard.2019-02-20-19.13.html19:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/storyboard/2019/storyboard.2019-02-20-19.13.txt19:59
openstackLog:            http://eavesdrop.openstack.org/meetings/storyboard/2019/storyboard.2019-02-20-19.13.log.html19:59
*** jamesmcarthur has joined #openstack-meeting20:02
*** markvoelker has joined #openstack-meeting20:03
*** carlos_silva has quit IRC20:08
*** ivoline has quit IRC20:25
*** ivoline_ has joined #openstack-meeting20:25
*** vishalmanchanda has quit IRC20:26
*** ivoline_ has quit IRC20:29
*** ivoline_ has joined #openstack-meeting20:30
*** markvoelker has quit IRC20:36
*** eharney has quit IRC20:46
*** raildo has quit IRC20:52
*** raildo has joined #openstack-meeting20:54
*** enriquetaso has quit IRC20:58
*** senrique_ has joined #openstack-meeting20:58
*** alecuyer has joined #openstack-meeting20:59
*** eharney has joined #openstack-meeting20:59
*** erlon__ has quit IRC21:01
*** ttsiouts has joined #openstack-meeting21:01
*** tdasilva has joined #openstack-meeting21:01
notmyname#startmeeting swift21:03
openstackMeeting started Wed Feb 20 21:03:18 2019 UTC and is due to finish in 60 minutes.  The chair is notmyname. Information about MeetBot at http://wiki.debian.org/MeetBot.21:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:03
*** openstack changes topic to " (Meeting topic: swift)"21:03
notmynameswift team meeting time!21:03
openstackThe meeting name has been set to 'swift'21:03
notmynamewho's here for it?21:03
*** senrique_ has quit IRC21:03
timburkeo/21:03
kota_o/21:03
alecuyero/21:03
tdasilvahi21:03
*** raildo has quit IRC21:04
claygsorry, thanks21:04
claygtypey typey21:04
mattoliverauo/21:04
notmynamekota_: thanks for reminding me of the meeting!21:04
kota_:-)21:05
kota_no one else at my desk in my home in the morning ;)21:05
*** jamesmcarthur has quit IRC21:05
*** zaitcev has joined #openstack-meeting21:05
notmynameoh, there's zaitcev!21:05
notmynameI'd like to check in on the py3 work.21:05
notmynamezaitcev: this morning timburke told me that with your work on the sharder, we'll soon be at about 60% coverage with py3?21:06
zaitcevnotmyname: It's only unit tests.21:06
zaitcevout of all tests it's about 41%21:06
zaitcevUnit tests are about 80% of all tests21:06
notmynamethat's still good though!21:07
timburkeonce we have things to the point that unit tests pass, i'm pretty sure we'll have services able to start. from there, we could run func tests under py2 against swift on py321:07
timburke...because porting func tests will be its own special hell, as i recall21:08
notmynamethat will be a great point to get to.21:08
zaitcevStill, it's way slower than I need.21:08
zaitcevCyril disappeared this week. He's helping py3 on other places too... Like, Sahara.21:09
timburkezaitcev, how much needs to be ported for RH to consider including it?21:09
zaitcevtimburke: Basically everything has to be there. Including obscure middleware, and the middleware I gave up upon, such as bulk.21:09
notmynamefor example, functests can run on a different system on py2 if the services are running under py321:11
*** mkarray has left #openstack-meeting21:11
timburkeyeah, i'm fine with everything under swift/ and bin/... i'm debating about how much value there is to be had in requiring func tests run under py3 if we can get to ^^^21:11
*** sdake has joined #openstack-meeting21:11
zaitcevWell... I don't remmeber, but I think we may be running in-process functests.21:11
notmynamehmm.. ok21:11
zaitcevSo, probe tests is the only thing that can be postponed.21:11
notmynamezaitcev: is there anything specific you need21:12
timburkewe do in-process func tests. we also do "spin up swift, then separately, run func tests".21:12
notmynameor... should we update https://wiki.openstack.org/wiki/Swift/PriorityReviews ?21:13
zaitcevnotmyname: more manpower, I think. Someone needs to adapt a thousand tests by adding b'' to everything.21:13
*** ivoline_ has left #openstack-meeting21:13
zaitcevI looked at slo, 83 failed21:13
zaitcevIf we can push container through, it unlocks a bunch of dependencies. Like dlo.21:13
timburkei'm actually hesitant to touch the func tests too much ATM -- i think it's going to be tricky verifying that we're still testing the same thing when running them under py2 vs py321:14
*** ijw has joined #openstack-meeting21:14
notmynamezaitcev: on slo?21:14
mattoliverauI'll focus on the container patch today.21:14
mattoliverauGot through a bunch of work stuff yesterday to free up more time to take a look today.21:15
zaitcevmattoliverau: thanks a lot. As you can see, it started as a "sharder CLI" patch, which snowballed.21:15
mattoliveraulol, yeah, I noticed that :)21:15
mattoliverauthanks for all that work and also sorry :P21:16
notmynamezaitcev: as you go through those patches, please highlight them in IRC and on https://wiki.openstack.org/wiki/Swift/PriorityReviews21:16
zaitcevtimburke: It is a concern. Worst comes to worst, I can ask people doing the release not to run in-process when building.21:16
notmynamekeeping them in front of the rest of us, I suspect, is a good way to get faster progress21:16
timburkeheh, sorry. when i start to review py3 stuff, i tend to start poking at the other bits around it and, well, here we are21:16
*** jamesmcarthur has joined #openstack-meeting21:17
mattoliverauI just keep asking questions about strings, byte strings and encoding :P21:17
zaitcevBy all means, ask away.21:18
zaitcevI'm happy to repeat all explanations, maybe you'll see a logical inconsistency.21:18
notmynametimburke: mattoliverau: if you could highlight the py3 patches, too, as you work on them, that would be great21:19
timburkefor sure, though, running the func tests is going to be the only way that i'll start to feel really good about declaring support. if it wasn't for those, i never would have found https://github.com/python/cpython/pull/793221:19
notmynameis there anything else about py3 that we need to bring up today in the meeting?21:20
timburkefound a bug in eventlet that's gonna block us porting ssync: https://github.com/eventlet/eventlet/pull/54821:20
timburkegood news is, they seem to be on board with fixing it21:20
notmynamealecuyer: kota_: rledisez: what's up with LOSF this week?21:21
alecuyerEarlier today I looked at grpcio/eventlet again,21:22
notmynamewas it amazing?21:22
alecuyersurprisingly the latest grpcio release (1.18.0) appears not to hang anymore with eventlet - just running the functests on SAIO21:22
claygand the survey says: threads, not so bad after all!21:22
alecuyerwell it may be :)21:22
notmynamenice!21:22
alecuyerSo I have to dig into this21:23
kota_nice21:23
claygthose google guys... I think they're pretty smart21:23
alecuyersee where it started working and why21:23
notmynamethat's expecially good, if tim's putting patches in eventlet for py3 support :-)21:23
alecuyerand if we can count on it working on later release or if i got lucky21:23
timburkeclayg, well, at least one of them is :-)21:23
timburkei miss torgomatic...21:23
claygalecuyer: 😍 "just cause it works doesn't mean I trust it enough to ship it"21:23
claygI need to _see__ the fix21:23
alecuyerclayg : thing is, they claim specifically that it will not work with eventlet, so im wary21:23
alecuyerso anyway I will give more details as soon as I find it21:24
notmynamethanks21:24
notmynamekota_: it looks like you have been merging from master. thanks for that21:24
notmynamerledisez: have you attempted that yet?21:24
alecuyer(I think rledisez isn't here, he's on vacation)21:24
notmynameah, ok21:24
notmynameok, what else do we need to talk about in the meeting this week?21:25
claygDoes anyone know for sure that they ARE interested in running for PTL?21:26
*** mjturek has quit IRC21:26
claygOr do we draw straws, or just make zaitcev do it?21:27
timburkei feel like there's three slots: i definitely *don't* want that job, i definitely *do* want that job, and i'd be *willing* to do that job if nobody else feels strongly21:27
timburkei'm kinda leaning toward the last one, personally21:27
claygright - if someone was in slot 2 that would be AMAZING21:27
clayglike, you don't even have to do it a 100 years like notmyname - we promise to let you out if it's even worse than you imagined21:28
zaitcevI'm with timburke on this. I could do it, but then I'll run the whole project into ground.21:28
clayg🤗21:28
timburkei firmly *don't* think anyone here would run the project into the ground21:29
timburkei think that's part of why i'm in the camp i am21:29
claygthis project runs itself, notmyname's be coasting :P21:29
notmynamelol21:30
claygLOL 🤗21:30
*** eharney has quit IRC21:30
timburkeclayg, it's like we're used to thinking in terms of a bunch of independent actors, all trying to bring a system into a truer/more correct state or something...21:30
claygtimburke: predisposed to organized chaos21:30
notmynameone thing to consider is the required public speaking. if that's not something you're comfortable with, then there are major parts of the job that you will hate21:31
*** takamatsu_ has joined #openstack-meeting21:31
*** takamatsu has quit IRC21:31
zaitcev"Hello, I'm the PTL and I have no clue about my project, but here's what they tell they're working on... some small files or other."21:31
*** markvoelker has joined #openstack-meeting21:33
clayghrm.. ok, I was really hoping someone was thinking this might be good - I mean... in reality it probably would be good21:33
notmynameok, let me make a few suggestions :-)21:33
clayg... an opportunity to expand your role - stretch your soft skills, leadership21:33
mattoliverauI'm currently in slot 3, Suse let's me spend time on it upstream, when I can. So not sure if PTL would mean they'd give me more time, or I'd be time limited which might not be great for the project.21:34
claygand of course force the rest of us to grow up and not "just make notmyname do it all the time"21:34
claygbecause realistically I'm not anyone of us thinks we dedicate the time and focus that notmyname has brought to us for all these years21:34
zaitcevRight, talk to TC about our go component for LOSF21:34
notmynamefirst, I suggest that there is an ongoing conversation about this. very few people will be comfortable discussing it in IRC (semi-public, logged), much less in an IRC meeting (logged, public, and more "formal")21:34
mattoliveraulol, that's true. but when you have a notmyname what did you expect us to do :P He's too damn good at the role21:34
notmynamefigure out a good way to discuss it, irc or otherwise21:35
claygwe don't need some one to "fill the shoes" - that's too daunting21:35
notmynamesecond, be very clear that whoever starts the conversation is NOT volunteering21:35
mattoliveraukk, I'll post back on the mailing list to get the ball rolling, we'll have the discussion there.21:36
mattoliverausorry not mailing list..21:36
timburkehahaha21:37
notmynamewhew21:37
mattoliverauA group email21:37
kota_i see, thx mattoliverau21:38
claygIs there any by-laws that say PTL nominations have to be core?21:38
* mattoliverau hasn't had any coffee so my brain isn't englishing very well :P21:38
notmynameclayg: no21:38
*** sdake has quit IRC21:38
claygjust checking21:38
mattoliveraunope21:38
claygok21:38
mattoliverautorgormatic for PTL!21:38
clayga'ight - i have another thing trying to get my attention... and I need to pee.  Sorry to bring it up!  :P21:38
kota_mattoliverau: lol21:39
timburkemattoliverau: we'll drag you back here, kicking and screaming!21:39
notmynameI think that's a good place to leave it for this meeting :-)21:39
notmynamethanks for coming today. and thank you for your work on swift21:39
notmyname#endmeeting21:40
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"21:40
openstackMeeting ended Wed Feb 20 21:40:02 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:40
openstackMinutes:        http://eavesdrop.openstack.org/meetings/swift/2019/swift.2019-02-20-21.03.html21:40
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/swift/2019/swift.2019-02-20-21.03.txt21:40
openstackLog:            http://eavesdrop.openstack.org/meetings/swift/2019/swift.2019-02-20-21.03.log.html21:40
*** sdake has joined #openstack-meeting21:41
*** zaitcev has left #openstack-meeting21:41
*** alecuyer has left #openstack-meeting21:42
*** takamatsu_ has quit IRC21:45
*** ijw has quit IRC21:45
*** takamatsu has joined #openstack-meeting21:46
*** sdake has quit IRC21:48
*** sdake has joined #openstack-meeting21:50
*** rosmaita has left #openstack-meeting21:54
*** jamesmcarthur has quit IRC21:55
*** ijw has joined #openstack-meeting21:58
*** jamesmcarthur has joined #openstack-meeting21:59
*** sdake has quit IRC21:59
*** enriquetaso has joined #openstack-meeting22:01
*** sdake has joined #openstack-meeting22:02
*** ijw has quit IRC22:05
*** markvoelker has quit IRC22:07
*** enriquetaso has quit IRC22:09
*** artom has quit IRC22:19
*** ijw has joined #openstack-meeting22:21
*** artom has joined #openstack-meeting22:24
*** mriedem has quit IRC22:25
*** ijw has quit IRC22:25
*** rcernin has joined #openstack-meeting22:27
*** awaugama has quit IRC22:30
*** whoami-rajat has quit IRC22:31
*** e0ne has quit IRC22:32
*** larainema has quit IRC22:34
*** hongbin has quit IRC22:51
*** ttsiouts has quit IRC22:52
*** mattw4 has quit IRC23:02
*** markvoelker has joined #openstack-meeting23:03
*** rcernin has quit IRC23:06
*** rcernin has joined #openstack-meeting23:08
*** imacdonn has quit IRC23:32
*** imacdonn has joined #openstack-meeting23:33
*** markvoelker has quit IRC23:35
*** jamesmcarthur has quit IRC23:55
*** jamesmcarthur has joined #openstack-meeting23:56
*** mriedem has joined #openstack-meeting23:57

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