Wednesday, 2019-04-17

*** tetsuro has joined #openstack-meeting00:02
*** enriquetaso has joined #openstack-meeting00:03
*** enriquetaso has quit IRC00:06
*** gyee has quit IRC00:08
*** jamesmcarthur has joined #openstack-meeting00:15
*** absubram has quit IRC00:16
*** martial has quit IRC00:22
*** armax has quit IRC00:23
*** lseki has quit IRC00:30
*** jamesmcarthur has quit IRC00:31
*** jamesmcarthur has joined #openstack-meeting00:31
*** mjturek has quit IRC00:32
*** Liang__ has quit IRC00:35
*** jamesmcarthur has quit IRC00:35
*** diablo_rojo has quit IRC00:38
*** mriedem has quit IRC00:38
*** diablo_rojo has joined #openstack-meeting00:43
*** ijw has quit IRC00:48
*** Liang__ has joined #openstack-meeting00:49
*** ricolin has joined #openstack-meeting00:56
*** baojg has joined #openstack-meeting00:57
*** ijw has joined #openstack-meeting01:04
*** baojg has quit IRC01:08
*** ijw has quit IRC01:09
*** bobh has joined #openstack-meeting01:16
*** Liang__ has quit IRC01:17
*** XSM_HUST has joined #openstack-meeting01:18
*** armax has joined #openstack-meeting01:23
*** tetsuro has quit IRC01:27
*** whoami-rajat has joined #openstack-meeting01:31
*** hongbin has joined #openstack-meeting01:37
*** bobh has quit IRC01:40
*** baojg has joined #openstack-meeting01:44
*** apetrich has quit IRC01:59
*** diablo_rojo has quit IRC02:05
*** mriedem has joined #openstack-meeting02:11
*** bobh has joined #openstack-meeting02:14
*** bobh has quit IRC02:15
*** lbragstad has quit IRC02:30
*** diablo_rojo has joined #openstack-meeting02:46
*** bobh has joined #openstack-meeting02:47
*** yamahata has joined #openstack-meeting02:54
*** bobh has quit IRC02:58
*** psachin has joined #openstack-meeting03:12
*** XSM_HUST has quit IRC03:13
*** hongbin has quit IRC03:38
*** diablo_rojo has quit IRC03:44
*** diablo_rojo has joined #openstack-meeting03:44
*** imsurit_ofc has joined #openstack-meeting03:47
*** armax has quit IRC03:51
*** mriedem has quit IRC04:08
*** iyamahat has joined #openstack-meeting04:12
*** david-lyle has joined #openstack-meeting04:13
*** manjeets_ has joined #openstack-meeting04:14
*** dklyle has quit IRC04:16
*** manjeets has quit IRC04:16
*** e0ne has joined #openstack-meeting04:35
*** e0ne has quit IRC04:42
*** e0ne has joined #openstack-meeting04:44
*** armax has joined #openstack-meeting04:48
*** armax has quit IRC04:55
*** absubram has joined #openstack-meeting05:01
*** absubram has quit IRC05:06
*** armax has joined #openstack-meeting05:07
*** vishakha has joined #openstack-meeting05:09
*** absubram has joined #openstack-meeting05:10
*** e0ne has quit IRC05:16
*** sridharg has joined #openstack-meeting05:23
*** rbudden has quit IRC05:31
*** iyamahat has quit IRC05:35
*** mattw4 has joined #openstack-meeting05:37
*** e0ne has joined #openstack-meeting05:40
*** janki has joined #openstack-meeting05:49
*** e0ne has quit IRC05:59
*** absubram has quit IRC06:01
*** pcaruana has joined #openstack-meeting06:11
*** mattw4 has quit IRC06:18
*** ralonsoh has joined #openstack-meeting06:21
*** hyunsikyang has quit IRC06:23
*** diablo_rojo has quit IRC06:45
*** hyunsikyang has joined #openstack-meeting06:56
*** shubham_potale has quit IRC07:02
*** kopecmartin|off is now known as kopecmartin07:09
*** apetrich has joined #openstack-meeting07:34
*** tssurya has joined #openstack-meeting07:43
*** e0ne has joined #openstack-meeting07:51
*** jrbalderrama has joined #openstack-meeting07:59
*** ttsiouts has joined #openstack-meeting08:06
*** dtrainor has quit IRC08:09
*** dtrainor has joined #openstack-meeting08:09
*** klindgren has quit IRC08:10
*** klindgren has joined #openstack-meeting08:10
*** rcernin has quit IRC08:13
*** ttsiouts has quit IRC08:17
*** ttsiouts has joined #openstack-meeting08:17
*** ttsiouts has quit IRC08:22
*** ttsiouts has joined #openstack-meeting08:28
*** rcernin has joined #openstack-meeting08:28
*** vishakha has quit IRC08:33
*** e0ne has quit IRC08:38
*** e0ne has joined #openstack-meeting08:42
*** e0ne has quit IRC08:43
*** e0ne has joined #openstack-meeting08:43
*** ygbo has joined #openstack-meeting08:49
*** e0ne has quit IRC08:58
*** e0ne has joined #openstack-meeting08:59
*** e0ne has quit IRC09:02
*** e0ne has joined #openstack-meeting09:09
*** Lucas_Gray has joined #openstack-meeting09:10
*** iyamahat has joined #openstack-meeting09:15
*** ttsiouts has quit IRC09:17
*** ttsiouts has joined #openstack-meeting09:18
*** ttsiouts_ has joined #openstack-meeting09:19
*** ttsiouts has quit IRC09:19
*** e0ne has quit IRC09:37
*** lpetrut has joined #openstack-meeting09:40
*** e0ne has joined #openstack-meeting09:40
*** electrofelix has joined #openstack-meeting09:46
*** e0ne has quit IRC09:46
*** e0ne has joined #openstack-meeting09:53
*** JangwonLee has quit IRC10:04
*** hyunsikyang has quit IRC10:04
*** hyunsikyang has joined #openstack-meeting10:04
*** JangwonLee has joined #openstack-meeting10:05
*** strigazi has quit IRC10:09
*** jchhatbar has joined #openstack-meeting10:14
*** janki has quit IRC10:16
*** janki has joined #openstack-meeting10:23
*** jchhatbar has quit IRC10:25
*** e0ne has quit IRC10:27
*** e0ne has joined #openstack-meeting10:31
*** a-pugachev has joined #openstack-meeting10:31
*** ttsiouts_ has quit IRC10:37
*** ttsiouts has joined #openstack-meeting10:38
*** ttsiouts has quit IRC10:42
*** ttsiouts has joined #openstack-meeting11:08
*** jchhatbar has joined #openstack-meeting11:20
*** ttsiouts has quit IRC11:20
*** ttsiouts has joined #openstack-meeting11:21
*** janki has quit IRC11:22
*** ttsiouts has quit IRC11:25
*** strigazi has joined #openstack-meeting11:25
*** ttsiouts has joined #openstack-meeting11:27
*** imsurit_ofc has quit IRC11:29
*** _erlon_ has joined #openstack-meeting11:42
*** ttsiouts has quit IRC11:43
*** ttsiouts has joined #openstack-meeting11:44
*** boxiang has quit IRC11:44
*** boxiang has joined #openstack-meeting11:45
*** ttsiouts_ has joined #openstack-meeting11:46
*** ttsiouts has quit IRC11:47
*** raildo has joined #openstack-meeting11:48
*** strigazi has quit IRC11:50
*** ttsiouts_ has quit IRC11:51
*** strigazi has joined #openstack-meeting11:51
*** bobh has joined #openstack-meeting11:51
*** strigazi has quit IRC11:52
*** strigazi has joined #openstack-meeting11:52
*** bobh has quit IRC11:54
*** strigazi has quit IRC11:55
*** strigazi has joined #openstack-meeting11:55
*** baojg has quit IRC12:00
*** e0ne has quit IRC12:00
*** bobh has joined #openstack-meeting12:01
*** sziviani has joined #openstack-meeting12:04
*** bobh has quit IRC12:05
*** e0ne has joined #openstack-meeting12:10
*** a-pugachev has quit IRC12:15
*** a-pugachev has joined #openstack-meeting12:18
*** Wryhder has joined #openstack-meeting12:24
*** Lucas_Gray has quit IRC12:25
*** Wryhder is now known as Lucas_Gray12:25
*** pcaruana has quit IRC12:30
*** rbudden has joined #openstack-meeting12:31
*** e0ne has quit IRC12:34
*** artom has quit IRC12:42
*** _pewp_ has quit IRC12:51
*** pcaruana has joined #openstack-meeting12:53
*** lbragstad has joined #openstack-meeting12:56
*** mriedem has joined #openstack-meeting12:57
*** e0ne has joined #openstack-meeting12:58
*** enriquetaso has joined #openstack-meeting13:21
*** bobh has joined #openstack-meeting13:22
*** mjturek has joined #openstack-meeting13:22
*** tidwellr has joined #openstack-meeting13:23
*** davidsha has joined #openstack-meeting13:25
*** awaugama has joined #openstack-meeting13:27
*** e0ne has quit IRC13:30
*** armstrong has joined #openstack-meeting13:35
*** baojg has joined #openstack-meeting13:44
*** artom has joined #openstack-meeting13:53
*** baojg has quit IRC14:00
*** mlavalle has joined #openstack-meeting14:02
mlavalle#startmeeting neutron_l314:02
openstackMeeting started Wed Apr 17 14:02:45 2019 UTC and is due to finish in 60 minutes.  The chair is mlavalle. Information about MeetBot at http://wiki.debian.org/MeetBot.14:02
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
ralonsohhi14:02
*** lseki has joined #openstack-meeting14:03
tidwellrhi14:03
slaweqhi14:03
mlavallehow are you all!14:03
slaweqgreat, thx :)14:04
slaweqand You?14:04
mlavallegreat also14:04
mlavalle#topic Announcements14:05
*** openstack changes topic to "Announcements (Meeting topic: neutron_l3)"14:05
*** bobh_ has joined #openstack-meeting14:05
mlavalleThree annoucements this week14:05
liuyulonghi14:05
mlavalle1) This is the first week of Train. So we left Stein behind us. Even stackalitycs shows TRain numbers now14:06
*** bobh has quit IRC14:06
mlavalle2) Don't forget to add topics to the PTG etherpad: https://etherpad.openstack.org/p/openstack-networking-train-ptg14:07
mlavalleI am starting to organize them in sessions14:07
slaweqmlavalle: deadline for adding topics is when?14:07
mlavalleNo deadline14:08
slaweqok, thx14:08
slaweqgood to know :)14:08
mlavallejust keep in mind that if you add a topic toooooo late, we might not have time slots available anymore14:08
mlavalle3) This week I'll also start looking for a venuw for our social event on May 3rd14:09
mlavalle17 people have confirmed attendance14:09
mlavalleliuyulong: when are you leaving Denver?14:09
*** baojg has joined #openstack-meeting14:11
mlavalleany other announcements?14:11
mlavalleok, moving on14:12
mlavalle#topic Bugs14:12
*** openstack changes topic to "Bugs (Meeting topic: neutron_l3)"14:12
mlavalleFirst this week is https://bugs.launchpad.net/neutron/+bug/182191214:13
openstackLaunchpad bug 1821912 in neutron "intermittent ssh failures in various scenario tests" [High,Confirmed]14:13
mlavalleI pushed a DNM patch adding some tcpdump to router namespaces: https://review.openstack.org/65302114:13
mlavallezuul actually looks beter than I expected14:14
mlavalleit seems it is failing unit tests and functional14:14
mlavallewhich is kind of expected14:15
mlavalleI'll start looking at results today14:15
slaweqyeah, but also tempest-slow-py3 failed on this patch14:15
mlavalleI'm going to start with neutron-tempest-dvr14:16
mlavalleand see what I can dig out14:16
liuyulongmlavalle, I couldn't be there.14:17
mlavalleany other comments form folks working also on this bug?14:17
mlavalleliuyulong: ahhh, since you added your name to the etherpad, I thought you would be there. We will miss you ;-)14:17
mlavalleok, next one is https://bugs.launchpad.net/neutron/+bug/182303814:19
openstackLaunchpad bug 1823038 in neutron (Ubuntu Bionic) "Neutron-keepalived-state-change fails to check initial router state" [High,Confirmed]14:19
mlavalleslaweq: we can close this one, can't we?14:21
slaweqmlavalle: no14:22
slaweqI saw some issues still in functional tests logs14:22
slaweqI will have to check that carefully14:22
mlavalleso you will look at it?14:22
slaweqyes, I will14:23
mlavalleThanks!14:23
liuyulongSeems I have a bad network traffic now...14:23
liuyulongMessages are delayed.14:23
mlavalleliuyulong: ack14:23
mlavalleNext one is https://bugs.launchpad.net/neutron/+bug/182457114:24
openstackLaunchpad bug 1824571 in neutron "l3agent can't create router if there are multiple external networks" [High,Confirmed]14:24
mlavalleFor this one, I voilunteered to work on it this week during the weekly Neutron meeting14:24
mlavalleI just assigned it to myself14:24
*** mjturek has quit IRC14:25
mlavalleunless of course someone wants badly to take it out of my hands ;-)14:25
liuyulongFor the bugs I've looked at, I will put my updates to the launchpad... Bad traffic14:26
mlavalleliuyulong: ack14:26
*** baojg has quit IRC14:26
*** liuyulong has quit IRC14:27
mlavalleany other bugs we should discuss today?14:27
*** liuyulong has joined #openstack-meeting14:28
*** lpetrut has quit IRC14:28
mlavalleok, moving on14:28
mlavalle#topic Openflow DVR14:28
*** openstack changes topic to "Openflow DVR (Meeting topic: neutron_l3)"14:28
mlavalleany updates on this topic this week?14:29
*** mjturek has joined #openstack-meeting14:29
davidshaI don't think so14:30
mlavalleok14:30
mlavallemoving on14:30
mlavalle#topic On demand agenda14:30
*** openstack changes topic to "On demand agenda (Meeting topic: neutron_l3)"14:30
mlavalleany other topics we should discuss today?14:30
liuyulongI'd like to add some bug14:31
liuyulonghttps://bugs.launchpad.net/neutron/+bug/182491114:31
openstackLaunchpad bug 1824911 in neutron "[scale issue] the bottleneck lock will multiply increase processing time of agent resources" [Undecided,New]14:31
liuyulonghttps://bugs.launchpad.net/neutron/+bug/182515214:31
openstackLaunchpad bug 1825152 in neutron "[scale issue] the root rootwrap deamon causes l3 agent router procssing very very slow" [Undecided,In progress] - Assigned to LIU Yulong (dragon889)14:31
liuyulongThese two are all about l3 agent performance during concurrently large set resource processing.14:32
*** bobh_ has quit IRC14:33
liuyulongSuch as l3-agent restart, if the agent has many scheduled routers, the restart time is indeed very long.14:33
liuyulonghttps://bugs.launchpad.net/neutron/+bug/182508814:33
openstackLaunchpad bug 1825088 in neutron "[port forwarding] should not process port forwarding if snat node only run DHCP" [Undecided,In progress] - Assigned to LIU Yulong (dragon889)14:33
liuyulongThis one is related to port forwarding, and it is a easy one with fix: https://review.openstack.org/65342314:34
*** vishalmanchanda has joined #openstack-meeting14:35
*** markvoelker has joined #openstack-meeting14:35
*** david-lyle is now known as dklyle14:35
liuyulongFor the bug #182191214:35
openstackbug 1821912 in neutron "intermittent ssh failures in various scenario tests" [High,Confirmed] https://launchpad.net/bugs/182191214:35
liuyulongI also noticed that, the check 'networking-ovn-tempest-dsvm-ovs-release' also has floating IP down related log. And then ssh failed.14:36
liuyulongFor instance: http://logs.openstack.org/36/652636/2/check/networking-ovn-tempest-dsvm-ovs-release/5bee185/testr_results.html.gz14:37
liuyulongOK, that's all from me.14:38
liuyulongThanks.14:38
mlavalleliuyulong: thanks for your update14:38
mlavalleI like those "scale issue" bugs14:38
mlavalleI'll keep an eye on them14:39
mlavalleanything else today?14:39
mlavalleok, thanks for attending14:40
mlavalle#endmeeting14:40
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"14:40
openstackMeeting ended Wed Apr 17 14:40:12 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:40
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_l3/2019/neutron_l3.2019-04-17-14.02.html14:40
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_l3/2019/neutron_l3.2019-04-17-14.02.txt14:40
davidshaThanks14:40
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_l3/2019/neutron_l3.2019-04-17-14.02.log.html14:40
ralonsohbye14:40
*** mattw4 has joined #openstack-meeting14:41
*** mattw4 has quit IRC14:50
*** manjeets has joined #openstack-meeting14:52
*** e0ne has joined #openstack-meeting14:53
*** jchhatbar has quit IRC14:53
*** jchhatbar has joined #openstack-meeting14:54
*** lpetrut has joined #openstack-meeting15:01
*** bobh has joined #openstack-meeting15:11
*** Liang__ has joined #openstack-meeting15:12
*** absubram has joined #openstack-meeting15:17
*** absubram has quit IRC15:21
*** rosmaita has joined #openstack-meeting15:23
*** absubram has joined #openstack-meeting15:29
*** a-pugachev_ has joined #openstack-meeting15:32
*** a-pugachev has quit IRC15:32
*** a-pugachev_ is now known as a-pugachev15:32
*** Liang__ has quit IRC15:32
*** jchhatbar has quit IRC15:33
*** jchhatbar has joined #openstack-meeting15:33
*** jchhatbar has quit IRC15:36
*** jchhatbar has joined #openstack-meeting15:36
*** jchhatbar has quit IRC15:40
*** lpetrut has quit IRC15:42
*** walshh_ has joined #openstack-meeting15:47
*** a-pugachev_ has joined #openstack-meeting15:48
*** a-pugachev has quit IRC15:50
*** a-pugachev_ is now known as a-pugachev15:50
*** luizbag has joined #openstack-meeting15:51
*** gyee has joined #openstack-meeting15:58
smcginnisWe now return to our regularly scheduled PTL.15:59
*** diablo_rojo has joined #openstack-meeting15:59
*** bobh has quit IRC15:59
*** thgcorrea has joined #openstack-meeting16:00
jungleboyj#startmeeting Cinder16:00
*** manjeets has quit IRC16:00
openstackMeeting started Wed Apr 17 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
jungleboyj:-)16:00
whoami-rajatHi16:00
smcginniso/16:01
jungleboyjcourtesy ping jungleboyj diablo_rojo, diablo_rojo_phon, rajinir tbarron xyang xyang1 e0ne gouthamr 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
*** carloss has joined #openstack-meeting16:01
_alastor_o/16:01
*** woojay has joined #openstack-meeting16:01
rajiniro/16:01
rosmaitao/16:01
jungleboyjMulti-tasking PTL.16:01
*** dviroel has joined #openstack-meeting16:01
e0nehi16:02
jungleboyj@!16:02
jungleboyjBooo!  hemna_ pewp is gone again.16:02
eharneyhi16:02
hemna_mep16:02
hemna_boo :(16:03
jungleboyjGive people another minute to connect.16:03
hemna_hrmm maybe pewp is down..../me checks16:03
walshh_hi16:03
jungleboyjHe he.16:03
jungleboyjOk, going to get started.16:03
jungleboyjHello all.16:03
enriquetasoo/16:03
jungleboyjI am back.  Thank you smcginnis for covering last week.16:04
jungleboyj#topic announcements16:04
enriquetasowelcome back!16:04
*** openstack changes topic to "announcements (Meeting topic: Cinder)"16:04
whoami-rajatjungleboyj: welcome back!16:04
jungleboyjThank you!16:04
jungleboyjSo, I am working on getting the Train PTG planned.16:04
jungleboyj#link https://etherpad.openstack.org/p/cinder-train-ptg-planning16:04
jungleboyjI see that a few topics have been added.  Thank you very much.16:05
jungleboyjPlease keep the topics coming so we can have a productive PTG.16:05
*** ygbo has quit IRC16:05
jungleboyjI am going to work on going through old discussions as well and try to add things as appropriate.16:06
jungleboyjAlso, we have our Dinner for the team at the Summit.16:06
jungleboyjTuesday night before the whole Summit event.16:06
jungleboyjHave a number of people that have indicated interest in attending.16:07
jungleboyjThank you!16:07
jungleboyjPlease add your name if interested as I will make reservations soon.16:07
jungleboyj#link https://etherpad.openstack.org/p/cinder-train-dinner-plan16:07
jungleboyjA happy announcement.16:07
*** dims has quit IRC16:07
jungleboyjI have put an e-mail out proposing rosmaita for Core!  :-)16:07
jungleboyjExcited to have another person to propose.16:08
smcginnisWoot! Nice work rosmaita16:08
jungleboyjsmcginnis: ++16:08
eharneyhooray16:08
enriquetasorosmaita++16:08
enriquetaso\o/16:08
jungleboyjrosmaita: Thank you for joining us and coming up to speed during the last release!16:08
* rosmaita blushes16:08
hemna_awesome16:08
jungleboyjTake a look at my note and if there are no concerns I will add him to the list next week.16:08
*** lpetrut has joined #openstack-meeting16:09
jungleboyjrosmaita:  Looking like you won't have problems.  :-)16:09
*** Lucas_Gray has quit IRC16:09
jungleboyjFinal announcement.16:09
jungleboyjI am working on getting the Forum Etherpads in place.  I think we only have a couple of topics.16:10
jungleboyjI will send out an e-mail once the etherpads are up so people can add topics.16:10
jungleboyjSo, that is it for announcements.16:11
jungleboyj#topic stable branch releases update16:11
*** openstack changes topic to "stable branch releases update (Meeting topic: Cinder)"16:11
jungleboyjrosmaita:  All yours.16:11
rosmaitaI figured it would be worth doing our monthly stable releases before the PTG.  Three things:16:12
rosmaita1 - cinder stable/rocky has 2 reviews sitting with 1 +2 ... i will propose 13.0.5 tomorrow, would be nice if a stable core could +W or -2 them in the meantime16:12
rosmaita2 - os-brick had only 1 unreleased change in rocky & queens, but i figured the point of the monthly releases is to make sure stuff doesn't sit, so i put up a release patch for each16:12
rosmaita3 - for cinderclient, looks like sean has a bunch of "raise API max" patches on master that will need to be backported to stein & rocky before we do a new release? (just want to verify that we want to hold the releases from stein & rocky for those)16:12
rosmaitaoops, i forgot the link to the etherpad16:12
rosmaita#link https://etherpad.openstack.org/p/cinder-releases-tracking16:13
jungleboyj:-)16:13
rosmaitaso the main question is 3, the others are points of information16:13
hemna_just for consistency ?16:14
eharneyi was trying to become more clear on those cinderclient api max patches -- do they actually get in the way of a couple of features working?16:14
rosmaitathat was my question too16:15
jungleboyjOk.  The rocky ones are on their way.16:15
rosmaitaok16:15
jungleboyjSo, the changes that Sean put up are required to expose new functions that went out in the server in Stein.16:16
smcginniseharney, rosmaita: Otherwise the client doesn't think it can talk that level: https://opendev.org/openstack/python-cinderclient/src/branch/master/cinderclient/api_versions.py#L31216:16
eharneyand roky16:16
eharneyrocky*16:16
jungleboyjThere is stuff that goes back to Rocky?16:17
rosmaitaok, we should def get those in before a release16:17
jungleboyjrosmaita:  ++16:17
jungleboyjDo we then need to backport those?16:18
jungleboyjTrying to remember what we did the last time we made this mistake.16:18
eharneyso the stein one doesn't appear to actually have much of an effect16:18
eharneywell, i guess it affects behavior, just doesn't need client changes, never mind16:19
*** _pewp_ has joined #openstack-meeting16:19
jungleboyjBut need to enable the client for that level to be able to use the server side support.16:20
jungleboyjsmcginnis:  Do you remember what we did in the past after they merged to master?16:21
smcginnisI think we backported them.16:21
smcginnisIt's a16:21
smcginnis"new feature" for the stable branch, but for missing functionality.16:21
jungleboyjOk, I thought that was the case.16:22
smcginnisAnd really just the one adds new stuff. The other two just set the max version correctly.16:22
jungleboyjRight.16:22
smcginnisIf we want, we can skip the one and just bump the version. Though that would be confusing.16:22
smcginnisAt least the max rocky version should get backported all the way.16:22
jungleboyjOk, lets get those in, backport and then do releases.16:22
eharneywill this need a minor version bump to handle the fact that it's a small compat change?16:23
smcginnisI don't think we can.16:23
* jungleboyj can hear jgriffith groaning16:23
smcginnisUsually we do a minor bump for the next cycle, so there's only room for a bugfix bump.16:23
rosmaitayes, that's the case here16:23
smcginnisYou could argue it's a bug that the client doesn't think it can talk to the server.16:23
*** david-lyle has joined #openstack-meeting16:24
jungleboyjI believe that was the decision in the past as well.16:24
jungleboyjPeople may grumble at us but I don't know of another way to do it.16:25
*** igordc has joined #openstack-meeting16:25
smcginnisWe have a few other agenda topics, so I think we can hash out any concerns later.16:25
rosmaitasounds good, that's all from me16:25
eharneythe other way to do is it to bump up both the stein version and the master version, but, ok16:26
*** manjeets__ has joined #openstack-meeting16:26
smcginniseharney: Not sure I follow.16:26
jungleboyjOk.  Lets move on and has that out when the release is proposed.16:26
rosmaitai will keep the etherpad updated, we can discuss there and/or on the release patches16:26
jungleboyjCool.16:27
jungleboyjrosmaita: Thank you for doing that work!16:27
*** dklyle has quit IRC16:27
jungleboyj@!16:27
*** mattw4 has joined #openstack-meeting16:27
*** manjeets_ has quit IRC16:27
jungleboyjhemna_:  Your pewp is still broken.  ;-)16:27
hemna_yah working on it16:28
hemna_container pain16:28
jungleboyj#topic Untyped volumes to default vol type16:28
*** openstack changes topic to "Untyped volumes to default vol type (Meeting topic: Cinder)"16:28
jungleboyjwhoami-rajat:16:28
whoami-rajatThe popular question appearing on the specs from every reviewer is the default type shouldn't be containing any extra_specs, the possible case i think to handle this is we shouldn't allow default_type to be updated but i think it's better to be discussed at the meeting.16:28
hemna_yah I raised that issue I think.16:29
whoami-rajathemna_: geguileo and eharney  too16:29
hemna_the problem is assigning that default type to untyped volumes16:29
jungleboyjwhoami-rajat:  Ok.  I need to catch up on that spec.16:29
hemna_if that type has attributes, it would kick off a retype operation which could result in a migration as well.16:29
whoami-rajat#link https://review.openstack.org/#/c/651480/16:29
_pewp_[ Gerrit Code Review ] - review.openstack.org16:29
hemna_it just gets ugly16:29
* jungleboyj laughs16:30
e0newhat if operators already configured default volume type with some extra specs?16:30
hemna_e0ne: then there shouldn't be any untyped volumes16:30
eharneyyeah, if the default volume type already has specs, they'll be used16:30
hemna_the question I think is the untyped volumes16:30
jungleboyjhemna_:  I think is a fair argument.16:31
smcginnisMaybe the more correct thing to do is just make sure we actually handle untyped volumes right since it's a valid case.16:31
hemna_The only conflict is if the name we are picking for default type is the same as what the operated has named16:32
eharneyright16:32
*** iyamahat has quit IRC16:32
jungleboyjhemna_:  That could be handled as an upgrade check?16:32
hemna_we could name it OMGWTFBBQ16:32
jungleboyjHe he.16:33
whoami-rajathemna_: should we be using a constant UUID format name to avoid that case?16:33
*** yamahata has quit IRC16:33
jungleboyjOr that.16:33
eharneywe could just implement the "retype" from None -> default as a db update and not a full retype operation, and don't do it if the default type has extra specs in it16:33
jungleboyjOMGBackYardBBQ16:33
eharneythis would cover the intended cases and also dodge breaking people in that odd case16:33
eharneythere's no reason it has to be a full retype/migration call if we design it so that it would never migrate volumes anyway16:33
hemna_eharney: that only works if the type has no attributes16:33
eharneyright, which is the primary use case for this16:34
smcginnisOr we could just fix our code where we assume there's going to be a type. :)16:34
eharney...16:34
hemna_if we guarantee the name we pick is unique, then there is no reason to worry about the attributes, since it will be empty16:34
e0nehemna_: +116:34
hemna_smcginnis: we have a patch out for 1 known issue16:34
hemna_the question is the unknown issues still16:34
eharneybut then you end up with a usability/documentation mess16:34
eharneyi'm not sure that's worthwhile16:35
hemna_as a side topic, we don't really have any documentation on volume types as a whole.16:35
hemna_s m h16:35
jungleboyjhemna_:  Yeah, one of our biggest things but not well documented.16:35
jungleboyj:-(16:35
hemna_what they are, how/why they can be used.  I think everyone just assumes that you use a type to associate it with a specific backend.16:35
jungleboyjhemna_:  True.16:36
whoami-rajateharney: i think a unique name is a simpler way to cover a lot of cases whereas handling case of retype might be just 1 of the problems.16:36
e0necan we just add a pre-upgrade check and force operators to retype untyped volumes?16:36
smcginnisSo we identified one issue that's been out there for years and we're afraid there may be more? If there are, no ones hitting it often enough to report it, and if they do, we fix it once it's identified.16:36
*** davidsha has quit IRC16:36
eharneya unique name is making things complicated for little benefit16:36
jungleboyje0ne: That could be another approach.  That could be less user friendly though.16:36
smcginnisThe bike shed should be blue!16:37
hemna_e0ne:I'm not sure that'd go over well with distros......16:37
hemna_so I suppose smcginnis is arguing against forcing volumes to have a type, and we do nothing (other than fix bugs)16:37
jungleboyjhemna_:  ++16:37
smcginnishemna_: That seems like the better approach to me.16:38
eharneyand the benefit of continuing to support volumes with no type is... we get to be lazier instead of implementing this?16:38
e0nedefault_volume_type=UNTYPED16:38
hemna_or we could just do what folks do in irc for nicknames  'hemna, hemna_, hemna__'16:38
eharneyi'm not convinced that untyped volumes actually benefits any users16:38
smcginnisRather than introducing a bunch of new issues.16:38
hemna_if you can't find a unique there......16:38
jungleboyjThe untyped volumes are very confusing IMHO.16:39
e0nehemna_: please, stop forking yourself :)16:39
*** jrbalderrama has quit IRC16:39
whoami-rajateharney:  i think of a case when pre-created default type contains extra specs related to a specific backend. won't every of the spec cause an issue for untyped volumes created in that backend ?16:39
smcginnishah16:39
* jungleboyj giggles16:39
_erlon_smcginnis: +1, I have seen a few bugs around the issue, but nothig that justify this change if it causing this much trouble16:39
eharneywhoami-rajat: i can think of a lot of cases, but we can also safely implement the useful cases16:39
eharney_erlon_: you say "justify this change" and "this much trouble" like it's an earth-shattering effort or something...?16:40
smcginnisIt sure seems to be a bigger effort than I think folks thought at first.16:40
jungleboyjwhoami-rajat:  You put this topic on the PTG list.  Right?16:40
hemna_I dunno, I think this is just a matter of either fixing an existing bug, and backporting it, or a simple way of finding a unique/useful name at db migration such that the untyped -> default type is nothin more than a db sql update.16:40
smcginnisWhat about if they did x? What about Y? Should we call it "pewp"? This is a bit nutty.16:41
whoami-rajatjungleboyj: yep16:41
hemna_if we have a unique name, there is almost no effort really16:41
hemna_sql update....done.16:41
hemna_it seems quite simple16:41
rosmaitasounds like we need to discuss this at the PTG16:41
_erlon_eharney: it seems that upgrading and avoiding naming conflicts might bring quite a lot of problems16:41
e0nehemna_:+116:41
eharneyright, i'm missing what is supposedly so hard about this16:41
hemna_eharney:+116:41
smcginnisThen announce in the release notes that "__DEFAULT__" is a reserved volume type name, make it that, and be done with this.16:41
hemna_I'm good with that16:42
jungleboyjeharney:  Yeah.16:42
eharneywell that's what we were going to do, just that it was going to be "default" instead of "__DEFAULT__"16:42
jungleboyjsmcginnis:  I am good with that too.16:42
_erlon_eharney: not earth-shattering, Im just comparing to hte problems of having untyped volumes16:42
jungleboyj__DEFAULT__ makes sense and is unlikely to conflict with anything.16:42
smcginnis"default" seems like it would have more risk of a conflict with an existing type.16:42
jungleboyjAdd a release note.16:42
jungleboyjDo an upgrade check.16:42
eharneyi already explained above how to handle conflicts w/ existing types16:42
hemna_smcginnis:+116:43
hemna___DEFAULT__ seems safer16:43
smcginnis"Before upgrading, if you have a volume type named WTF, it must be renamed."16:43
jungleboyj++16:43
jungleboyjOk, so I think we can stop bike shedding.16:44
jungleboyjOtherwise the reactor is going to melt down.16:44
eharneywell, now that we decided we actually want a bike shed, yeah16:44
jungleboyj:-)16:44
whoami-rajatwe've created a group-type migration before for migrating consistency groups to generic vol groups, i'm not sure if it faced much issues with the naming.16:45
jungleboyjBike sheds are the bees knees16:45
*** ijw has joined #openstack-meeting16:45
jungleboyjwhoami-rajat:  Can you get the spec updated and we can discuss further at the PTG if necessary.16:45
whoami-rajatjungleboyj: ok16:46
jungleboyjCool.  Thanks.16:46
whoami-rajatjust to be clear, we agreed on __DEFAULT__ ?16:46
jungleboyjwhoami-rajat:  I think that is good.16:46
jungleboyjwhoami-rajat:  Remind me, will you be at the PTG?16:46
whoami-rajatok16:46
whoami-rajatjungleboyj: i won't be making this time. but will connect remotely.16:47
jungleboyjOk.  So, if there are topics you want covered at a particular time for you please let me know in the etherpad.16:47
eharneywe'll cycle around on the name again once the spec is up to date with the general idea16:47
jungleboyjeharney:  ++16:47
whoami-rajatjungleboyj: sure, thanks.16:47
jungleboyj#topic Review of Specs before Train PTG.16:47
*** openstack changes topic to "Review of Specs before Train PTG. (Meeting topic: Cinder)"16:47
*** _pewp_ has quit IRC16:47
jungleboyjSo, just a reminder that looking through our outstanding specs can make time at the PTG more productive.16:48
jungleboyjPlease make some time to do that.16:48
jungleboyjI haven't looked in a while so I will do so.16:48
jungleboyjI think that is all I had on that unless there are others that want to pile on.16:49
_erlon_jungleboyj: have just added a topic there. Can you manage to put that on thu or friday?16:49
_erlon_jungleboyj: wont be able to attend on sat16:49
jungleboyj_erlon_:  Ok.  Don't expect there to be a lot of discussion on Saturday so we should be fine.16:49
*** ijw has quit IRC16:49
_erlon_jungleboyj: nice, thanks16:50
jungleboyjI am going to be exhausted after a full week of Summit and PTG.16:50
jungleboyj#topic Placement Discussion16:50
*** openstack changes topic to "Placement Discussion (Meeting topic: Cinder)"16:50
jungleboyjSo, has anyone been tracking impacts of the placement work on Cinder?16:50
jungleboyjWay back in Atlanta we met with the team on this.16:51
jungleboyjI don't think at lot has happened here other than talking about how they use the DB.16:51
smcginnisIIRC, we determined it doesn't help Cinder, but we could publish our resource usage to placement for other services to be able to query.16:52
e0neI think, it's a good time to start discussion again since it's a separate project now16:52
jungleboyjThere has been discussion on the mailing list but didn't see Cinder input.16:52
*** _pewp_ has joined #openstack-meeting16:52
jungleboyjsmcginnis:  That sounds familiar.16:52
*** _pewp_ has quit IRC16:52
e0ne#link https://review.openstack.org/#/c/559718/16:53
*** dims has joined #openstack-meeting16:54
jungleboyjHmmm.  Ok.16:55
jungleboyjSo, maybe I will reach out to the Placement group and see if they want to meet with us to discuss anything.  If not, I will let it be for now.16:55
jungleboyjSee what cdent thinks.16:56
jungleboyjGiven the silence it doesn't appear of great interest to anyone here.16:57
*** iyamahat has joined #openstack-meeting16:57
jungleboyjMoving on then.16:57
jungleboyj#topic Possible dinner location for team meeting at the Summit16:58
*** openstack changes topic to "Possible dinner location for team meeting at the Summit (Meeting topic: Cinder)"16:58
*** _pewp_ has joined #openstack-meeting16:58
jungleboyj#link http://www.rheinhausdenver.com/menus16:58
jungleboyjThis looks like our kind of place and it is about a mile away so within walking distance.16:58
rosmaitai am curious to see how giant a "giant pretzel" is16:58
jungleboyj:-)16:59
*** dims has quit IRC16:59
jungleboyjAnyone vote no for that place?  If not, I will make it official.16:59
smcginnisLooks good to me.16:59
hemna_they have Bier, do we need anything else?17:00
jungleboyjOk.  I will put it in the etherpad.17:00
jungleboyjhemna_:  ++17:00
jungleboyjI will make a reservation later this week.17:00
e0ne:)17:00
jungleboyjOk.  So, that is time.17:00
jungleboyjThanks everyone for joining.17:00
jungleboyj#endmeeting17:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"17:00
openstackMeeting ended Wed Apr 17 17:00:36 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/cinder/2019/cinder.2019-04-17-16.00.html17:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/cinder/2019/cinder.2019-04-17-16.00.txt17:00
openstackLog:            http://eavesdrop.openstack.org/meetings/cinder/2019/cinder.2019-04-17-16.00.log.html17:00
*** woojay has left #openstack-meeting17:00
*** e0ne has quit IRC17:01
*** rosmaita has left #openstack-meeting17:01
*** dims has joined #openstack-meeting17:01
*** thgcorrea has left #openstack-meeting17:01
*** ricolin has quit IRC17:04
*** kopecmartin is now known as kopecmartin|off17:05
*** _pewp_ has quit IRC17:06
*** _pewp_ has joined #openstack-meeting17:06
*** mattw4 has quit IRC17:06
*** _pewp_ has quit IRC17:09
*** _pewp_ has joined #openstack-meeting17:09
*** a-pugachev has quit IRC17:16
*** luizbag has left #openstack-meeting17:20
*** igordc has quit IRC17:26
*** yamahata has joined #openstack-meeting17:27
*** markvoelker has quit IRC17:31
*** markvoelker has joined #openstack-meeting17:31
*** vishalmanchanda has quit IRC17:34
*** markvoelker has quit IRC17:35
*** ralonsoh has quit IRC17:36
*** awaugama has quit IRC17:39
*** awaugama has joined #openstack-meeting17:39
*** igordc has joined #openstack-meeting17:44
*** factor has quit IRC17:46
*** bobh has joined #openstack-meeting17:50
*** manjeets__ is now known as manjeets17:53
*** david-lyle is now known as dklyle17:55
*** tssurya has quit IRC17:58
*** electrofelix has quit IRC18:00
*** armstrong has quit IRC18:04
*** dmacpher_ has joined #openstack-meeting18:11
*** psachin has quit IRC18:13
*** dmacpher has quit IRC18:13
*** JangwonLee_ has joined #openstack-meeting18:20
*** boxiang has quit IRC18:20
*** zhubx has joined #openstack-meeting18:20
*** rfolco has quit IRC18:20
*** rfolco has joined #openstack-meeting18:21
*** JangwonLee has quit IRC18:23
*** carloss has left #openstack-meeting18:33
*** mattw4 has joined #openstack-meeting18:40
*** lpetrut has quit IRC18:41
*** lpetrut has joined #openstack-meeting18:42
*** sridharg has quit IRC18:48
*** dviroel has left #openstack-meeting18:51
*** dtrainor has quit IRC18:51
*** b1airo has quit IRC18:57
fungistory time?19:00
SotK#startmeeting storyboard19:00
openstackMeeting started Wed Apr 17 19:00:43 2019 UTC and is due to finish in 60 minutes.  The chair is SotK. Information about MeetBot at http://wiki.debian.org/MeetBot.19:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:00
*** openstack changes topic to " (Meeting topic: storyboard)"19:00
openstackThe meeting name has been set to 'storyboard'19:00
diablo_rojoI love story time :)19:01
fungigather 'round19:01
SotK#link https://wiki.openstack.org/wiki/Meetings/StoryBoard Agenda-ish19:01
SotK#topic Announcements19:02
*** openstack changes topic to "Announcements (Meeting topic: storyboard)"19:02
SotKwe're having a repository rename!19:02
diablo_rojoWoohoo!19:02
fungieverybody loves those19:02
fungimore of a namespace move really19:03
fungiand also new hosting domain for the source code19:03
fungias well as a prettier git hosting platform at that domain19:03
SotKyeah, gitea is very shiny, I like it19:04
SotKI think the current plan for us is to basically do s/openstack-infra/opendev/19:04
fungithe long and short of it is that the openstack infra team has been spinning off some of its core services into a new hosting platform it calls "opendev" at opendev.org19:04
diablo_rojoIts all so shiny and new :)19:04
fungiand some of the first services to move are code review and git source hosting/browsing19:05
diablo_rojo+2 for s/openstack-infra/opendev/19:05
fungithat's finally happening this friday, universe willing19:05
fungias part of that effort, major projects were asked what they wanted to do about namespacing19:05
*** raildo has quit IRC19:05
fungithe openstack project has decided that deliverable repositories for official openstack teams and related efforts go in the "openstack" namespace19:06
fungibut anything not official has to go somewhere else (projects who don't pick a new namespace are going in one called "x")19:06
fungistoryboard's repositories are deliverables of the openstack infra team19:07
fungiso those would normally be expected to move from openstack-infra to openstack19:07
fungihowever the opendev effort has its own namespace for things it's extracting out of openstack governance19:07
*** mkarray has joined #openstack-meeting19:08
fungiso has given storyboard deliverables the option of moving out of the openstack namespace and into the opendev namespace19:08
fungithis does however also imply a governance change, that storyboard efforts would cease being part of the openstack project and become an opendev infrastructure project19:09
diablo_rojoI think opendev is good. Gives a better impression of not being solely used by openstack19:09
fungiopendev is still supported by the openstack foundation and all the same sponsoring organizations19:09
SotKdiablo_rojo: +119:09
fungibut it's a way to indicate that storyboard is not really an openstack-specific application19:10
diablo_rojoYeah that is a HUGE benefit I think19:10
fungithe governance for opendev isn't entirely fleshed out at this stage, though we do have a proposal floating around19:10
diablo_rojoMaybe this is how we get some more hands to help us19:10
fungii think the end result is at least no worse than remaining part of openstack (same benefits extended by osf and sponsors)19:11
fungiand hopefully a significant improvement in visibility19:11
fungiin the not too distant future, the storyboard instance hosted at storyboard.openstack.org would also start redirecting to a new storyboard.opendev.org name, or something along those lines19:12
fungias far as the actual maintenance happening on friday, we're trying to make it as seamless as possible, but still expect some bumps19:12
fungithere are redirects already prepped and tested so the old git urls will continue working as before19:13
fungiwe'll be pushing patches directly into all repositories (bypassing code review) to update git-review and zuul job configuration19:14
fungihowever, you will likely need to pull that commit locally, remove any existing gerrit remote in your repositories, and rerun `git review -s` to get it to reread that configuration so you can push new patches to review19:15
fungiblowing away your local repo and re-cloning is another option of course, if you don't have any local commits you need to save19:16
*** dtrainor has joined #openstack-meeting19:16
fungione other note, specific for the storyboard.openstack.org instance... when we rename projects or their namespaces, we do update the storyboard database to reflect that19:17
fungiwe don't currently have any redirecting solution in place though, so sb urls involving specific project names will need updating19:17
*** e0ne has joined #openstack-meeting19:17
fungifor example, https://storyboard.openstack.org/#!/project/openstack-infra/storyboard would need to become https://storyboard.openstack.org/#!/project/opendev/storyboard19:18
fungianyway, that's all i had on the namespace/hosting changes... any questions?19:20
*** e0ne has quit IRC19:20
*** raildo has joined #openstack-meeting19:20
SotKI don't think so, thanks for the heads up on the configuration changes19:21
* SotK wonders how many projects are using that style of project URL in docs and so on19:21
SotKwe should probabl;y make storyboard support renaming projects with the ability to redirect at some point19:21
fungia lot hadn't converted to it yet, so are still using project id numbers which will keep working as before19:21
*** e0ne has joined #openstack-meeting19:22
fungiand yeah, i was thinking that would be a nifty feature in the future19:22
*** artom has quit IRC19:22
diablo_rojoAgreed19:22
fungiwould probably want to do similar with renaming other things like project-groups and teams19:22
SotKyeah, that would make sense19:23
SotKI'll create a story for it after the meeting19:23
fungiin our deployment, i foresee wanting to also start namespacing project-groups and teams the same way we do with projects, but that doesn't really need any change to the software just how we're using it19:24
SotKyeah I suspect that would be a sensible thing to do19:26
SotKanything else on this?19:27
diablo_rojoNothing from me19:27
SotK#topic Migration Updates19:27
*** openstack changes topic to "Migration Updates (Meeting topic: storyboard)"19:27
fungii ran the test imports for all the openstack telemetry deliverables on storyboard-dev.openstack.org last week19:28
SotKhow did they go?19:28
fungitheir ptl gave the results a thumbs-up but we're holding off merging the change and doing the final import until he can arrange to get control of the corresponding launchpad projects so they can have their bug reporting closed down at the same time19:28
fungithere was a bit of a takeover of those projects as they were mostly orphaned by their previous maintainers and some new users have adopted them19:29
fungiso it's taking a bit of time for the new ptl to track down someone with admin privs on those (they had never correctly ceded ownership of the lp teams to the openstack admins team)19:30
fungihopefully next week though19:31
SotKnice, hopefully its all sorted soon19:31
fungialso in migration news, is seems like the ndsu interns are coming along with the lp blueprint importing implementation?19:32
fungidiablo_rojo has been following that more closely than i have19:32
diablo_rojoYeah a bit. Its still got some work but I think their semester is going to be done in a couple weeks so they have to be done with it by then lol19:32
fungia bit of the delay was due to the incomplete api on launchpad around its blueprints feature19:33
fungithe api actually calls them "specs"19:33
fungibut at any rate, there's no obvious way to query for "specs" which match a particular project on lp, so they're having to resort to scraping the web content for searches through its webui19:34
fungiugly, but gets the job done19:34
SotKyeah I had a quick look at the patch and assumed that missing apis were the cause behind that19:35
SotKI'll try to follow it more closely in the next week or two :)19:35
fungiand at least once you have the name of a spec you can use the lp api to fetch details19:35
fungii don't have any other migration updates19:36
SotK#topic Forum/PTG Planning19:37
*** openstack changes topic to "Forum/PTG Planning (Meeting topic: storyboard)"19:37
SotKdo we have anything left that we should plan?19:37
SotKand do we want to book a team photo slot? :D19:39
fungidiablo_rojo seems to be a fan of photos19:40
diablo_rojoI like taking them more than being in them19:40
diablo_rojobut if you want a photo I can stand there awkwardly19:40
*** lpetrut has quit IRC19:40
diablo_rojoI created the etherpad for the forum session19:41
SotKI don't have a strong desire for one, lets just not have one if you prefer taking them :)19:41
SotKnice, do you have a link for it?19:41
diablo_rojo#link https://etherpad.openstack.org/p/storyboard-pain-points Etherpad19:41
diablo_rojoIts towards the end of the day Monday19:42
diablo_rojoAs for the massive bug triage we are planning at the PTG19:42
diablo_rojoI think a corner of the infra room Thursday morning?19:42
fungiyeah, i was a photographer's assistant for years, not really that into being in front of the camera but happy to jump i a photo if folks want19:42
diablo_rojo#decision no photo :)19:43
SotKdiablo_rojo: corner of the infra room sounds good19:43
diablo_rojoI didnt think we needed an etherpad for the PTG activities, but I think we should email the discuss list with the plan19:44
SotKyeah we probably should19:45
SotKwould you like to do it or shall I?19:45
diablo_rojoSotK, go for it ;)19:45
SotKalright then, I'll get it sent sometime in the next day or two19:45
diablo_rojoSounds good.19:45
SotK#topic In Progress Work19:46
*** openstack changes topic to "In Progress Work (Meeting topic: storyboard)"19:46
SotKI have about a million patches to review19:47
SotKI'll try to get some of it done over the long weekend19:47
diablo_rojoHeh yeah you do.19:47
SotKI've been super busy elsewhere recently so have fallen rather behind on it again19:48
diablo_rojoI also have a lot to review19:48
diablo_rojoIts alright. I started single core approving the smaller ones19:48
diablo_rojoI will probably do another round of that today.19:48
SotKI noticed that, thanks :)19:48
diablo_rojoTrying to leave the ones I think you might have an opinion on.19:48
mkarrayI am currently no longer working on making new features as my term has come to a close, though I'll still be around until my patches get pushed to completion19:49
diablo_rojomkarray, awesome19:49
SotKmkarray: thanks for your work!19:49
diablo_rojoYes thank you!19:50
mkarrayMy pleasure :)  You guys have been very helpful19:50
diablo_rojoWe hope you'll stick around as much as you can19:50
fungiyour presence has been a huge help, even just answering folks questions in irc19:50
diablo_rojoMaybe you can do the next round of outreachy after this summer round?19:50
diablo_rojoThat too19:50
SotK+1, I really appreciate it :)19:51
mkarrayI'll definitely make the effort to apply, once again I had a great time helping out19:51
SotK#topic Open Discussion19:52
*** openstack changes topic to "Open Discussion (Meeting topic: storyboard)"19:53
* diablo_rojo doesnt have anything 19:54
fungiyeah, i have to get back to scripting a few thousand git commits for friday19:55
*** bobh has quit IRC19:56
diablo_rojoHave fun with that :)19:56
SotKheh, sounds exciting19:57
SotKthanks for coming folks!19:57
SotK#endmeeting19:57
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"19:57
fungithanks SotK!19:57
openstackMeeting ended Wed Apr 17 19:57:27 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:57
openstackMinutes:        http://eavesdrop.openstack.org/meetings/storyboard/2019/storyboard.2019-04-17-19.00.html19:57
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/storyboard/2019/storyboard.2019-04-17-19.00.txt19:57
openstackLog:            http://eavesdrop.openstack.org/meetings/storyboard/2019/storyboard.2019-04-17-19.00.log.html19:57
*** raildo has quit IRC20:02
diablo_rojoThanks SotK!20:05
*** ijw has joined #openstack-meeting20:11
*** ijw has quit IRC20:11
*** ijw has joined #openstack-meeting20:11
*** mjturek has quit IRC20:20
*** e0ne has quit IRC20:31
*** absubram has quit IRC20:35
*** raildo has joined #openstack-meeting20:40
*** mlavalle has left #openstack-meeting20:41
*** pcaruana has quit IRC20:43
*** enriquetaso has quit IRC20:47
*** iyamahat_ has joined #openstack-meeting20:57
*** iyamahat has quit IRC21:00
*** alecuyer has joined #openstack-meeting21:00
*** whoami-rajat has quit IRC21:01
timburke#startmeeting swift21:01
openstackMeeting started Wed Apr 17 21:01:47 2019 UTC and is due to finish in 60 minutes.  The chair is timburke. Information about MeetBot at http://wiki.debian.org/MeetBot.21:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:01
*** openstack changes topic to " (Meeting topic: swift)"21:01
openstackThe meeting name has been set to 'swift'21:01
timburkewho's here for the swift meeting?21:01
claygo/21:01
alecuyerhi o/21:02
*** mkarray has left #openstack-meeting21:02
*** awaugama has quit IRC21:03
rledisezo/21:03
timburkeall right, i'm gonna try to make this quick, since (1) there isn't much new on the agenda and (2) i've got an almost-one-year-old who's still a bit angry that his mattress had to get up and host a meeting21:03
*** zaitcev has joined #openstack-meeting21:04
alecuyerhehe21:04
timburke#topic PTG21:04
*** openstack changes topic to "PTG (Meeting topic: swift)"21:04
timburke#link https://etherpad.openstack.org/p/swift-ptg-train21:04
timburkeeveryone's been doing a great job of filling out the agenda, as well as when they'll be in town21:05
timburkeit looks like most of the active contributors will be there in Denver, which is great!21:05
claygnoice21:05
*** zaitcev_ has joined #openstack-meeting21:06
timburkei don't have much more to say there, but if anyone has anything else to bring up, feel free to add it to the etherpad (or mention it here, or in -swift, or... just bring it up)21:06
timburkemoving on to updates!21:07
timburke#topic updates - py321:07
*** openstack changes topic to "updates - py3 (Meeting topic: swift)"21:07
timburkezaitcev's dlo patch is working its way through the gate21:08
timburkei'm trying to get a py3 dsvm job going21:08
timburkemattoliverau took a stab at tempurl21:08
timburkei'm feeling like getting some gating func tests will be incredibly valuable, so if anyone has time to look at the chain starting at https://review.openstack.org/#/c/645284/ i'd greatly appreciate it21:09
*** zaitcev has quit IRC21:10
timburkeoh yeah, and i did s3api! which covers a *bunch* of unit tests -- once we get that landed, something like 3/4 of tests will be running under py321:10
*** zaitcev_ is now known as zaitcev21:10
zaitcevs3api is on my plate to review. That chain you mentioned looks very familiar, but I forgot about it.21:11
timburkethanks zaitcev!21:11
timburkei know you looked at the next one down, that makes func tests send non-ascii request paths21:12
timburke#topic updates - losf21:12
*** openstack changes topic to "updates - losf (Meeting topic: swift)"21:12
timburkealecuyer, rledisez, how's it going?21:12
alecuyerWe have more machines using LOSF now, I did ops work this week, we found some issues with LOSF and xfs_repair,21:13
alecuyerxfs_repair may remove inodes (volumes or leveldb files) and we do not handle this automatically currently21:13
timburkei *love* finding issues before they hit master! ;-)21:13
alecuyerso, i've put some details here https://docs.google.com/document/d/1YyWyMxNKAYek-wUAps1cv_Bu4guojc2Yu31RVVNxMHw/edit#21:14
timburke#link https://docs.google.com/document/d/1YyWyMxNKAYek-wUAps1cv_Bu4guojc2Yu31RVVNxMHw/edit21:14
timburke(for the logs)21:14
alecuyerSo, no progress to report otherwise :/21:15
rledisezquestion about that: how far should the automatic repair go? is trashing the KV and starting de rebuild ok?21:15
rledisezor should it be an operator action?21:15
rledisezlike running xfs_repair actually21:15
rledisezi'm in favor of automation as far as we know there is no options and there will be no data loss. otherwise, it should be an operator action21:16
timburkemaybe we could quarantine? starting a rebuild as soon as possible seems like a good remediation, at first glance...21:16
*** slaweq has quit IRC21:17
timburkedo we have anything to clear out quarantined data after some amount of time, or do we just let it pile up until the operator removes it manually?21:17
alecuyerI don't think there is anything automatic to clear it at the moment21:18
rledisezright now it piles up, as the current quarantine21:18
rledisezthat's an interesting topic btw, a tool to clean quarantine would be nice21:18
rledisezlike, thi object was corrupted, but I know there is a correct version in the cluster => clean21:19
*** slaweq has joined #openstack-meeting21:19
timburkerledisez, do you feel like you have a good enough idea of what that tool would look like to write up a "bug" (feature request) describing it?21:20
rlediseztimburke: I might start something. maybe on the etherpad first. when we come up to an aggrement on the feature i could move it to a bug21:21
timburkesounds good21:21
timburkeanyone have any other topics that should have an update?21:22
timburke#open discussion21:24
timburkeany other topics in general?21:24
*** slaweq has quit IRC21:24
zaitcevNot me... PTG is still 2 weeks away, so normal work.21:24
timburkeoh! i wrote a client patch for the first time in forever: https://review.openstack.org/#/c/651666/21:26
timburkeso there can be an actual bug fix for its eventual train release ;-)21:26
zaitcevReviewers: Darrel Bishop21:27
zaitcevget real21:27
timburkehe may have been the one to report the issue21:27
zaitcevOh, wow.21:27
zaitcevWaaaaait a momen. I thought that he occupied the DofEng position that John aims for. I was sure he'd go up, to a VP or COO.21:29
timburke*shrug* startup titles are mostly made up anyway21:29
timburkei believe my business cards say "Squasher of Bugs" :P21:29
alecuyersounds good :-)21:30
timburkeall right, i'm'a call it and get this kid some meds to get his fever back down21:30
timburkethank you all for coming, and thank you for working on swift!21:30
timburke#endmeeting21:30
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"21:30
openstackMeeting ended Wed Apr 17 21:30:46 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:30
openstackMinutes:        http://eavesdrop.openstack.org/meetings/swift/2019/swift.2019-04-17-21.01.html21:30
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/swift/2019/swift.2019-04-17-21.01.txt21:30
openstackLog:            http://eavesdrop.openstack.org/meetings/swift/2019/swift.2019-04-17-21.01.log.html21:30
*** alecuyer has left #openstack-meeting21:31
*** zaitcev has left #openstack-meeting21:31
*** rbudden has quit IRC21:31
*** rbudden has joined #openstack-meeting21:31
*** rbudden has quit IRC21:32
*** ijw has quit IRC21:34
*** ijw has joined #openstack-meeting21:34
*** iyamahat__ has joined #openstack-meeting21:37
*** ijw has quit IRC21:40
*** a-pugachev has joined #openstack-meeting21:40
*** slaweq has joined #openstack-meeting21:40
*** iyamahat_ has quit IRC21:40
*** ijw has joined #openstack-meeting21:41
*** slaweq has quit IRC21:45
*** absubram has joined #openstack-meeting21:46
*** ijw has quit IRC21:48
*** slaweq has joined #openstack-meeting21:50
*** hongbin has joined #openstack-meeting21:52
*** slaweq has quit IRC21:55
*** mriedem has quit IRC22:10
*** rbudden has joined #openstack-meeting22:15
*** zhubx has quit IRC22:18
*** ijw has joined #openstack-meeting22:19
*** boxiang has joined #openstack-meeting22:19
*** lbragstad has quit IRC22:33
*** lbragstad has joined #openstack-meeting22:35
*** zigo has quit IRC22:58
*** rbudden has quit IRC23:06
*** raildo has quit IRC23:07
*** jamesmcarthur has joined #openstack-meeting23:07
*** ijw has quit IRC23:16
*** ijw has joined #openstack-meeting23:17
*** igordc has quit IRC23:21
*** jamesmcarthur has quit IRC23:23
*** ijw has quit IRC23:36
*** hongbin has quit IRC23:38
*** ijw has joined #openstack-meeting23:40
*** a-pugachev has quit IRC23:47
*** artom has joined #openstack-meeting23:48
*** mattw4 has quit IRC23:49
*** absubram has quit IRC23:50

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