Wednesday, 2019-05-15

*** gyee has quit IRC00:18
*** yamamoto has quit IRC00:19
*** jamesmcarthur has joined #openstack-meeting00:22
*** dklyle has joined #openstack-meeting00:30
*** b1airo has quit IRC00:32
*** mriedem has quit IRC00:41
*** jamesmcarthur has quit IRC00:46
*** jamesmcarthur has joined #openstack-meeting00:47
*** ricolin has joined #openstack-meeting00:48
*** jamesmcarthur has quit IRC00:52
*** mattw4 has quit IRC00:56
*** jamesmcarthur has joined #openstack-meeting01:11
*** SpamapS has quit IRC01:16
*** rcernin has quit IRC01:16
*** SpamapS has joined #openstack-meeting01:16
*** rcernin has joined #openstack-meeting01:17
*** rcernin has quit IRC01:18
*** rcernin has joined #openstack-meeting01:19
*** baojg has joined #openstack-meeting01:25
*** ttsiouts has joined #openstack-meeting01:29
*** whoami-rajat has joined #openstack-meeting01:34
*** macza has joined #openstack-meeting01:35
*** macza has quit IRC01:39
*** boxiang has joined #openstack-meeting01:48
*** tetsuro has joined #openstack-meeting01:49
*** SpamapS has quit IRC01:52
*** SpamapS has joined #openstack-meeting01:53
*** apetrich has quit IRC01:57
*** ykatabam has joined #openstack-meeting02:00
*** yamahata has quit IRC02:02
*** ttsiouts has quit IRC02:02
*** iyamahat_ has quit IRC02:03
*** cyg has joined #openstack-meeting02:13
*** jamesmcarthur has quit IRC02:14
*** jamesmcarthur has joined #openstack-meeting02:32
*** enriquetaso has joined #openstack-meeting02:35
*** tetsuro_ has joined #openstack-meeting02:37
*** hongbin has joined #openstack-meeting02:39
*** tetsuro has quit IRC02:39
*** enriquetaso has quit IRC02:39
*** tetsuro has joined #openstack-meeting02:42
*** tetsuro_ has quit IRC02:46
*** bbowen has quit IRC02:46
*** ykatabam has quit IRC02:47
*** bbowen has joined #openstack-meeting03:02
*** yamamoto has joined #openstack-meeting03:08
*** SpamapS has quit IRC03:08
*** SpamapS has joined #openstack-meeting03:09
*** yamamoto has quit IRC03:17
*** hongbin has quit IRC03:18
*** ykatabam has joined #openstack-meeting03:20
*** ykatabam has quit IRC03:21
*** ykatabam has joined #openstack-meeting03:21
*** armax has quit IRC03:24
*** SpamapS has quit IRC03:30
*** SpamapS has joined #openstack-meeting03:33
*** SpamapS has quit IRC03:40
*** jamesmcarthur has quit IRC03:40
*** SpamapS has joined #openstack-meeting03:41
*** tris has quit IRC03:41
*** tris has joined #openstack-meeting03:45
*** tetsuro has quit IRC03:50
*** tetsuro has joined #openstack-meeting03:52
*** hemna has joined #openstack-meeting03:53
*** hyunsikyang__ has quit IRC03:53
*** yamamoto has joined #openstack-meeting03:54
*** psachin has joined #openstack-meeting03:56
*** jamesmcarthur has joined #openstack-meeting03:58
*** ttsiouts has joined #openstack-meeting03:59
*** jamesmcarthur has quit IRC04:03
*** imsurit_ofc has joined #openstack-meeting04:05
*** tris has quit IRC04:12
*** diablo_rojo has quit IRC04:15
*** tris has joined #openstack-meeting04:17
*** yamamoto has quit IRC04:18
*** mattw4 has joined #openstack-meeting04:24
*** imsurit_ofc has quit IRC04:26
*** ttsiouts has quit IRC04:31
*** yamamoto has joined #openstack-meeting04:35
*** hemna has quit IRC04:36
*** tetsuro has quit IRC04:37
*** imsurit_ofc has joined #openstack-meeting04:37
*** yamamoto has quit IRC04:38
*** yamamoto has joined #openstack-meeting04:38
*** mattw4 has quit IRC04:39
*** janki has joined #openstack-meeting04:43
*** Luzi has joined #openstack-meeting04:46
*** e0ne has joined #openstack-meeting05:05
*** e0ne has quit IRC05:08
*** yamamoto has quit IRC05:39
*** vishalmanchanda has joined #openstack-meeting05:43
*** yamamoto has joined #openstack-meeting05:44
*** radeks_ has joined #openstack-meeting05:47
*** psachin has quit IRC05:54
*** psachin has joined #openstack-meeting05:57
*** kaisers has joined #openstack-meeting06:24
*** ttsiouts has joined #openstack-meeting06:29
*** e0ne has joined #openstack-meeting06:35
*** apetrich has joined #openstack-meeting06:47
*** yamamoto has quit IRC06:50
*** yamamoto has joined #openstack-meeting06:52
*** yamamoto has quit IRC07:00
*** ttsiouts has quit IRC07:02
*** tssurya has joined #openstack-meeting07:07
*** tesseract has joined #openstack-meeting07:13
*** yamamoto has joined #openstack-meeting07:16
*** rcernin has quit IRC07:25
*** zigo has quit IRC07:28
*** ttsiouts has joined #openstack-meeting07:30
*** yamamoto has quit IRC07:38
*** hyunsikyang__ has joined #openstack-meeting07:39
*** hyunsikyang has quit IRC07:42
*** hyunsikyang has joined #openstack-meeting07:43
*** hyunsikyang__ has quit IRC07:44
*** corvus has quit IRC07:47
*** boxiang has quit IRC07:51
*** corvus has joined #openstack-meeting07:52
*** kopecmartin|off is now known as kopecmartin08:01
*** yamamoto has joined #openstack-meeting08:13
*** lennyb has joined #openstack-meeting08:16
*** yamamoto has quit IRC08:23
*** ykatabam has quit IRC08:26
*** ttsiouts has quit IRC08:34
*** ykatabam has joined #openstack-meeting08:36
*** hyunsikyang__ has joined #openstack-meeting08:38
*** hyunsikyang has quit IRC08:42
*** yamamoto has joined #openstack-meeting08:43
*** a-pugachev has joined #openstack-meeting08:45
*** ralonsoh has joined #openstack-meeting08:46
*** pcaruana has joined #openstack-meeting08:51
*** a-pugachev has quit IRC08:55
*** ykatabam has quit IRC08:56
*** a-pugachev has joined #openstack-meeting09:02
*** a-pugachev has left #openstack-meeting09:19
*** zigo has joined #openstack-meeting09:35
*** yamamoto has quit IRC09:41
*** yamamoto has joined #openstack-meeting09:48
*** ykatabam has joined #openstack-meeting09:52
*** yamamoto has quit IRC09:53
*** ykatabam has quit IRC10:09
*** tesseract has quit IRC10:12
*** tesseract has joined #openstack-meeting10:12
*** jawad_axd has joined #openstack-meeting10:21
*** ykatabam has joined #openstack-meeting10:21
*** zigo has quit IRC10:30
*** ttsiouts has joined #openstack-meeting10:31
*** zigo has joined #openstack-meeting10:41
*** ttsiouts has quit IRC11:04
*** raildo has joined #openstack-meeting11:05
*** njohnston has joined #openstack-meeting11:06
*** carloss has joined #openstack-meeting11:12
*** jawad_axd has quit IRC11:21
*** imsurit_ofc has quit IRC11:44
*** raildo has quit IRC11:51
*** panda is now known as panda|launch12:01
*** janki has quit IRC12:04
*** jamesmcarthur has joined #openstack-meeting12:19
*** mriedem has joined #openstack-meeting12:23
*** dkehn has quit IRC12:25
*** jamesmcarthur has quit IRC12:29
*** _erlon_ has joined #openstack-meeting12:35
*** raildo has joined #openstack-meeting12:37
*** tdasilva has joined #openstack-meeting12:37
*** sridharg has joined #openstack-meeting12:43
*** janki has joined #openstack-meeting12:44
*** hyunsikyang has joined #openstack-meeting12:44
*** hyunsikyang__ has quit IRC12:49
*** jamesmcarthur has joined #openstack-meeting12:50
*** rbudden has joined #openstack-meeting12:53
*** raildo has quit IRC12:53
*** raildo has joined #openstack-meeting13:00
*** ttsiouts has joined #openstack-meeting13:01
*** ykatabam has quit IRC13:03
*** panda|launch is now known as panda13:05
*** baojg has quit IRC13:06
*** artom has quit IRC13:14
*** jchhatbar has joined #openstack-meeting13:15
*** janki has quit IRC13:17
*** lbragstad has joined #openstack-meeting13:18
*** lseki has joined #openstack-meeting13:19
*** tidwellr has joined #openstack-meeting13:23
*** yamamoto has joined #openstack-meeting13:27
*** enriquetaso has joined #openstack-meeting13:29
*** Luzi has quit IRC13:31
*** raildo_ has joined #openstack-meeting13:32
*** raildo has quit IRC13:34
*** ttsiouts has quit IRC13:35
*** vishalmanchanda has quit IRC13:48
*** hyunsikyang__ has joined #openstack-meeting13:57
*** hyunsikyang has quit IRC14:00
*** mlavalle has joined #openstack-meeting14:00
mlavalle#startmeeting neutron_l314:00
openstackMeeting started Wed May 15 14:00:54 2019 UTC and is due to finish in 60 minutes.  The chair is mlavalle. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** openstack changes topic to " (Meeting topic: neutron_l3)"14:00
openstackThe meeting name has been set to 'neutron_l3'14:00
tidwellro/14:01
haleybo/14:01
pandao/ (partially - in another meeting)14:01
mlavallehey panda, I was wondering about you yesterday. Nice to see you here :-)14:02
mlavallegood morning haleyb, tidwellr14:02
ralonsohhi14:03
mlavallehey ralonsoh14:03
tidwellrmlavalle: happy wednesday!14:03
mlavalleok, let's get going14:05
mlavalle#topic Announcements14:05
*** openstack changes topic to "Announcements (Meeting topic: neutron_l3)"14:05
*** sziviani has left #openstack-meeting14:06
mlavalleWe are on our way to the T-1 milestone, June 3 - 714:06
mlavalle#link https://releases.openstack.org/train/schedule.html14:06
mlavalleThese are our photos from the recent PTG:14:07
njohnstono/14:07
mlavalle#link https://www.dropbox.com/sh/fydqjehy9h5y728/AAC1gIc5bJwwNd5JkcQ6Pqtra/Neutron?dl=0&subfolder_nav_tracking=114:07
mlavalleeverybody handsome as usual14:08
mlavalleespecially in the one with the props14:08
mlavalleany other announcements from the team?14:09
mlavalleok, let's move on14:10
mlavalle#topic Bugs14:10
*** openstack changes topic to "Bugs (Meeting topic: neutron_l3)"14:10
mlavalleFirst, we have a critical issue https://bugs.launchpad.net/neutron/+bug/182457114:11
openstackLaunchpad bug 1824571 in neutron "l3agent can't create router if there are multiple external networks" [Critical,Confirmed] - Assigned to Miguel Lavalle (minsel)14:11
mlavalleit was recently promoted to critical by slaweq14:11
mlavalleso I better hurry up with a fix for this14:12
mlavalleI have an environment ready to reproduce the issue14:12
*** jbadiapa has quit IRC14:14
mlavalleNext bug is https://bugs.launchpad.net/neutron/+bug/177445914:14
openstackLaunchpad bug 1774459 in neutron "Update permanent ARP entries for allowed_address_pair IPs in DVR Routers" [High,Confirmed] - Assigned to Swaminathan Vasudevan (swaminathan-vasudevan)14:14
mlavalleWe didn't have a chance to discuss this issue in Denver14:15
*** bobh has joined #openstack-meeting14:15
mlavallecouldn't reach Swami over google hangouts14:15
mlavallebut it seems he is making progress: https://review.opendev.org/#/c/651905/14:16
tidwellrbefore he left Denver he wanted me to just mention he needs reviews14:16
mlavallein the commit message he indicates it is related to the bug14:17
mlavalleare there more patches coming?14:17
tidwellrthere's also https://review.opendev.org/#/c/616272/ that I think is also related14:17
tidwellrand maybe this one too https://review.opendev.org/#/c/601336/14:18
*** bobh has quit IRC14:19
mlavalleyes, these two indicate also in the commit message that are related14:19
* mlavalle leaving a note in the bug pointing to these 2 patches ^^^^14:19
mlavalleLast one I have today is https://bugs.launchpad.net/neutron/+bug/182303814:21
openstackLaunchpad bug 1823038 in neutron "Neutron-keepalived-state-change fails to check initial router state" [High,Confirmed]14:21
mlavallewhich seems to have already fixed14:22
ralonsohnot yet14:22
ralonsohI'm going to propose a patch for it14:23
ralonsohthe agent is now run under neutron-rootwrap14:23
ralonsohand privsep is failing14:23
ralonsohso I'm removing this new code added and keep only the privsep initialization14:23
mlavallecan I assign it to you?14:24
ralonsohI'm just helping Slawek14:24
ralonsohhe knows the status of this patch14:24
mlavalleah ok14:24
ralonsohthat's all14:25
mlavallethanks for the update :)14:25
*** jamesmcarthur has quit IRC14:25
mlavalleany other bugs we should discuss today?14:25
liuyulongOne more https://bugs.launchpad.net/neutron/+bug/182191214:26
openstackLaunchpad bug 1821912 in neutron "intermittent ssh failures in various scenario tests" [High,In progress] - Assigned to LIU Yulong (dragon889)14:26
liuyulongSeems we hit this more more frequently14:26
*** artom has joined #openstack-meeting14:27
mlavalleis it a work around?14:27
liuyulongI have two direction of repair14:27
liuyulongone: https://review.opendev.org/#/c/659009/ wait until the floating IP is active14:28
mlavalleis this a work around? ^^^^14:28
liuyulongIt can be one work around14:29
liuyulongthe another is we can not rely on that nova DB instance status14:29
liuyulongevery time the guest OS is booting, then the test case is trying to login14:30
liuyulongSo I wonder if we can ping the fixed IP first, then try to login it14:30
liuyulongBut seems the tempest now does not allow that14:31
mlavalleso what you are saying is that we don't have an underlying connectivity / authentication problem, but rather a testing problem?14:31
liuyulongI have tried both in this https://review.opendev.org/659009, but now revert back to only have "waiting for floating IP status"14:32
liuyulongIn the recent merged patch, they all have a lot of "recheck", maybe we can increase this bug level too.14:33
mlavallecritical?14:33
*** jchhatbar has quit IRC14:34
liuyulongNot entirely, Slawek mentioned that nova metadata may have something wrong.14:34
mlavalleok, a combination of causes14:35
tidwellrliuyulong: just thinking out loud and maybe it's crazy, but I wonder if there's way to set a static route on the host that would allow us to reach the fixed IP14:35
liuyulongmlavalle,  Slawek and I are now aiming to different direction14:37
*** armax has joined #openstack-meeting14:37
liuyulongI also noticed that l3-agent may have a really long router processing time, 40s+ in some cases.14:38
mlavalleliuyulong: sounds good to. I am also adding a 3rd direction: tcpdump in the namespace14:38
liuyulongtidwellr, I'm not quite sure, but if tempest can only reach the API, the route may not work.14:39
tidwellryep, it's just a thought14:39
liuyulongThis is really a tough one...14:40
mlavalleyes it is14:41
mlavalleanything else on this bug?14:41
liuyulongnot from me14:42
mlavallethanks for the update :-)14:42
mlavalleany other bugs?14:42
haleybmlavalle: there's one in the open agenda section, but if we're in a buggy mood we can discuss now14:43
mlavalleshoot14:43
haleybhttps://bugs.launchpad.net/neutron/+bug/181882414:43
openstackLaunchpad bug 1818824 in neutron "When a fip is added to a vm with dvr, previous connections loss the connectivity" [Low,In progress] - Assigned to Gabriele Cerami (gcerami)14:43
tidwellrI saw the chatter about this in IRC yesterday14:44
haleybIn short, there is a difference between DVR/centralized here14:44
pandaI tried to lay down some solution, but a behavioural decision has to be made before14:44
haleybif an instance is using the default snat IP and a floating is associated, should we be deleting the conntrack entries for the existing connections14:45
haleybi'm inclined to think we should always be cleaning them, since the instance should start using the floating IP14:46
tidwellris there a concrete example of a workload in a VM that is affected by this?14:46
haleybi don't think so.  it's an edge case since in order to trigger something in an instance you need a floating to get in first (or login from another instance on the private network)14:47
liuyulonghaleyb, +1, yes, it should stop the previous connection to save the SNAT node bandwidth.14:48
mlavalleliuyulong always bringing the operator perspective14:48
mlavallenice14:48
tidwellrI'm inclined to agree, once the FIP is associated force all traffic to use it14:48
haleybliuyulong: it doesn't happen with centralized routing today, you can have a connection continue to use the snat IP until it closes.  DVR "breaks" it simply because it forces everything into the fip namespace where it dies14:49
mlavalleI agree with haleyb and tidwellr14:51
haleybso it seems we agree the conntrack entries should have been cleaned.  i think if we make that change soon-ish we'll be able to get some feedback if we break something during the T cycle14:51
mlavalleyes!14:51
mlavalle]the sooner the better14:51
tidwellr+114:51
pandafor bot DVR and non DVR scnarios ?14:51
haleyband i don't think we documented the behavior, so we should do that too14:52
pandain DVR currently the connections just starve, they are not closed14:52
*** bobh has joined #openstack-meeting14:52
haleybpanda: yes, both.  with dvr it's essentially cleaned by the routing change, right?14:52
haleybas you say starved since the connection is broken14:53
pandahaleyb: i'ts not cleaned at all, the package try to follow the new route but they just die somewhere, so the connection clears for the timeout14:53
pandaI'm trying to understand if the need to be explicitly closed instead14:53
liuyulongCould be a bug for centralized router, since we never test that.14:54
mlavalleI'd say explicitely close it14:55
liuyulongFor dvr with centralized floating IPs, what's the hehavior now?14:55
haleybpanda: right, but removing the stale conntrack entries would make the connection fail quickly and not timeout slowly14:55
mlavallegood point14:55
haleybliuyulong: that's a good question, don't know14:55
liuyulongprevious connection may stay, IMO14:56
pandaliuyulong: and have a different behaviour for the two scenarios ? I think the idea here was to look for consistency14:58
pandamy personal preference is to try and maintain the old connection, but just because I found it a good entry point to experiment and learn the code :)14:59
haleybif we had a floating IP assigned and it got removed, conntrack gets cleaned-up, i think we should treat the default snat IP similarly - the (dis)association event flips which is used14:59
mlavallewe are running out of time14:59
mlavalleI lean towards consitency of behavior15:00
mlavalle#endmeeting15:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"15:00
openstackMeeting ended Wed May 15 15:00:13 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_l3/2019/neutron_l3.2019-05-15-14.00.html15:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_l3/2019/neutron_l3.2019-05-15-14.00.txt15:00
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_l3/2019/neutron_l3.2019-05-15-14.00.log.html15:00
mlavallethanks for attending15:00
liuyulongpanda, dvr centralized floating IP and distributed floating IP may have different behavior in such case.15:00
*** ralonsoh has left #openstack-meeting15:00
*** ralonsoh has joined #openstack-meeting15:01
*** vishalmanchanda has joined #openstack-meeting15:01
*** njohnston has left #openstack-meeting15:02
*** rubasov has quit IRC15:04
*** rubasov has joined #openstack-meeting15:05
*** ociuhandu has joined #openstack-meeting15:13
*** rubasov has quit IRC15:14
*** liuyulong has quit IRC15:21
*** rfolco|ruck is now known as rfolco15:22
*** rosmaita has joined #openstack-meeting15:25
*** panda is now known as panda|ruck15:26
*** ttsiouts has joined #openstack-meeting15:32
*** tesseract has quit IRC15:35
*** macza has joined #openstack-meeting15:37
*** sridharg has quit IRC15:46
*** ttsiouts has quit IRC15:50
*** e0ne has quit IRC15:50
*** rubasov has joined #openstack-meeting15:50
*** e0ne has joined #openstack-meeting15:50
*** davidsha has joined #openstack-meeting15:53
*** woojay has joined #openstack-meeting15:59
jungleboyj#startmeeting Cinder16:00
openstackMeeting started Wed May 15 16:00:51 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
whoami-rajatHi16:00
davidshao/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
smcginniso/16:01
_alastor_\o16:01
xyanghi16:01
rajiniro/16:01
jungleboyj@!16:01
_pewp_jungleboyj ( ´ ▽ ` )ノ16:01
gouthamro/16:01
rosmaitao/  -- i like the courtesy ping16:01
jungleboyjrosmaita:  So do I.  :-)16:01
jungleboyjrosmaita:  I miss meetings that don't have it.16:01
rosmaitasame here16:01
woojayhi16:01
jungleboyjLook all these wonderful people showing up.16:02
_erlon_hey16:02
jungleboyjGive people one more minute here.16:02
jungleboyjTake it everyone made it home safely?16:02
smcginnisI made it home dangerously.16:03
jungleboyjsmcginnis:  Nice!16:03
smcginnis:P16:03
rosmaitai made it home eventually16:03
jungleboyjGet the pilot to do some barrel rolls?16:03
e0nehi16:03
jungleboyjrosmaita:  :-(16:03
jungleboyjWell, eventually is better than not at all.16:04
rosmaitayep16:04
jungleboyjMy 6 am flight was brutal.16:04
jungleboyjAnyway, we have a lot to cover, so lets get started.16:04
jungleboyj#topic announcements16:04
*** openstack changes topic to "announcements (Meeting topic: Cinder)"16:04
jungleboyjFirst, we have defined the Week for the Train Mid-Cycle!16:04
jungleboyj#link https://etherpad.openstack.org/p/cinder-train-mid-cycle-planning16:05
jungleboyjIf you are interested in attending in person or remotely please add your name to the etherpad.16:05
*** kopecmartin is now known as kopecmartin|off16:05
jungleboyjI let Lenovo know we are planning to be there again and haven't heard a no.  I am pretty sure we will be ok as I had already budgeted for it.16:06
jungleboyjHope we can get a few more people to attend this time as the last one was really productive.16:06
*** wwriverrat has joined #openstack-meeting16:06
jungleboyjAlso, there is the requirement for drivers to move to Python 3 for their 3rd Party CI.16:07
jungleboyj#link http://lists.openstack.org/pipermail/openstack-discuss/2019-May/006001.html16:07
smcginnisWe said by milestone-2, right?16:07
jungleboyjIf you own a driver and aren't already doing this/thinking about it ... Please start.16:07
jungleboyjCorrect.16:07
jungleboyjI just realized I should add that to the schedule I just proposed.16:07
smcginnisOh, good idea.16:08
whoami-rajatVNX driver specifically ? ^16:08
smcginnisIf they find issues with running under py3 - milestone-3 to get that resolved?16:08
jungleboyjwhoami-rajat:  Is that the one that is currently failing?16:08
smcginnisOr running successfully by milestone-2?16:08
jungleboyjsmcginnis:  ++  I think that is fair.16:08
whoami-rajatjungleboyj:  yes, IIRC16:09
jungleboyjI am ok with giving them a bit to work out the failures.16:09
smcginnisWe will need to disable the VNX unit tests if that is not resolved soon since py3.7 is one of the official runtimes for train.16:09
*** mszwed_ has joined #openstack-meeting16:09
jungleboyjwhoami-rajat:  Ok.  I still have a todo to ping Helen about that.  She isn't in the meeting so I will e-mail her.16:09
mszwed_Hi :-)16:09
whoami-rajatjungleboyj: sounds good. thanks.16:10
enriquetasoo/16:10
jungleboyjIs everyone in agreement to the Python3 dates above?16:10
* jungleboyj marks enriquetaso tardy16:10
enriquetasou.u16:10
smcginnisShould we say py3.7, or is py3.6 enough?16:11
* smcginnis thinks py3.7 really would be the interesting one16:11
jungleboyjsmcginnis: I don't know enough to have a strong opinion.16:11
jungleboyjI defer to your expertise there.16:12
e0neI prefere 3.7 from developer's perspective16:12
whoami-rajatI think py37 would be better16:12
e0nebut it would be good to check with disctros16:12
e0ne#link https://governance.openstack.org/tc/reference/runtimes/train.html16:12
smcginnis3.7 is where they really broke some compatibility, so if we are saying 3.7 is an official runtime for train, then I think the CIs probably should use that version to make sure there are no surprises for end users.16:12
jungleboyjsmcginnis:  ++16:12
rosmaitasmcginnis: ++16:13
jungleboyjThat makes sense with me and then we should be confident that whatever distros are using should be good.16:13
jungleboyjSo, lets call it Py37 then.16:14
smcginnis++16:14
jungleboyjThe people actually impacted are being too quiet.16:14
jungleboyjBut, I can move on.16:15
jungleboyjI have posted the summary of the PTG and Forum:16:15
jungleboyj#link https://wiki.openstack.org/wiki/CinderTrainSummitandPTGSummary#Train_PTG_Summary16:15
mszwed_+16:15
jungleboyjThank you to everyone who came and helped make our time successful.16:15
jungleboyjI have outlined who has action items in there.16:15
jungleboyjPlease take a look and plan to take your action items.  :-)16:16
jungleboyjIf you see any inconsistencies or mis-interpretations please let me know.16:16
jungleboyjFinally, I have proposed the Train release schedule:16:17
rosmaitais it ok if we just edit the wiki?16:17
jungleboyj#link https://review.opendev.org/65933016:17
jungleboyjrosmaita:  Sure, that would be fine.  Just let me know what I did wrong if you can.16:17
jungleboyj:-)16:17
rosmaitaok16:17
_erlon_jungleboyj: nice summary Jay. Thanks a lot!16:17
jungleboyjHave two things to update after the meeting, it sounds like, so I will push up another patch.16:17
_alastor_I notice the 3rd party CIs are supposed to be running the Cinder tempest plugin, but all-plugin has been deprecated in tempest16:17
jungleboyj_erlon_:  Thanks.  Glad to do it.16:18
*** ijw has joined #openstack-meeting16:18
jungleboyj_alastor_:  Yeah, I saw that.  Can we chat about that later in the meeting?16:18
_alastor_yeah np16:19
jungleboyj_alastor_:  Thank you sir.16:19
jungleboyjSo, take a look at the release schedule and please add review comments if you have concerns.16:19
jungleboyjOk.  That was what I had for announcements.  That was quite a bit.16:19
jungleboyj#topic the unwritten rules about same-company approvals16:20
*** openstack changes topic to "the unwritten rules about same-company approvals (Meeting topic: Cinder)"16:20
jungleboyj#link http://lists.openstack.org/pipermail/openstack-discuss/2019-May/005954.html16:20
jungleboyjSo, this is a discussion that has been happening on the ML.16:20
jungleboyjI haven't followed the later updates, honestly, because it started getting a little political and silly.16:20
jungleboyjrosmaita:  Wanted to know our expectations.16:20
rosmaitayeah, it seemed like "don'16:21
rosmaitat have all approvals be from a single company" could be written down16:21
rosmaitaso i was wondering if there was more to it16:21
jungleboyjLong story short, this used to be a bigger issue when we had multiple cores from the same company trying to push features in.16:21
*** tidwellr has left #openstack-meeting16:21
jungleboyjNow, given our current landscape it is less of an issue.16:21
smcginnisI think like how we said trivial things like small doc changes can be single approved, if there is no potential concerns it's OK to approve with two from the same company. Just discourage it in normal practice.16:21
smcginnisI'd only be really concerned if the proposer and both cores were all from the same company.16:22
jungleboyjBut yes, the short answer is, be a good citizen and don't have all the reviews on a patch be from one company.  Especially if it is a feature or something you are pushing.16:22
rosmaitaok, so for bugfixes, not a big deal ... features, think twice16:22
*** diablo_rojo has joined #openstack-meeting16:22
smcginnisrosmaita: I think that's a great way to frame it.16:22
rosmaitaok, cool, thanks16:22
jungleboyjsmcginnis: rosmaita ++16:22
e0nesmcginnis: +116:22
*** yamamoto has quit IRC16:22
jungleboyjI would rather have you ping me on IRC and push the patch in my face.16:23
rosmaitaok, i will keep that in mind!16:23
jungleboyjIt just keeps us looking more credible.16:23
jungleboyjAny other questions around that?16:24
rosmaitanot from me16:24
*** tesseract has joined #openstack-meeting16:24
jungleboyjOk.16:25
jungleboyj#topic dell_emc.vnx.test_adapter.TestCommonAdapter failing py37 tests16:25
*** openstack changes topic to "dell_emc.vnx.test_adapter.TestCommonAdapter failing py37 tests (Meeting topic: Cinder)"16:25
jungleboyjrosmaita:16:25
rosmaitayeah, i just wanted to bring the bug to people's attention16:25
rosmaitai approved rajat's patch adding the py37 job as non-voting16:25
jungleboyj#link https://bugs.launchpad.net/cinder/+bug/179595716:25
openstackLaunchpad bug 1795957 in Cinder "VNX unit tests are not Python 3.7 compatible" [Undecided,Confirmed]16:25
rosmaitaand walter had mentioned that we should make sure some attention is paid to the failing tests16:26
jungleboyjrosmaita:  Right.16:26
rosmaitaso i figured this way we all know about it16:26
rosmaitathat's all16:26
jungleboyjNeed to ping Helen Walsh about that.16:26
jungleboyjI will do that after the meeting.16:26
rajinirrosmaita: the vnx driver team is looking into the unit failures. Helen is vmax16:26
jungleboyjrajinir:  Oh.  Gotcha.16:26
rosmaitarajinir: thanks16:26
jungleboyjrajinir:  Who is VNX?16:27
rajinirjungleboyj: larger team in china, sam and sun hao16:27
jungleboyjrajinir:  Ok.  Thanks.  So it is being worked?16:28
rajinirjungleboyj: I will update them16:28
rajinirjungleboyj: yes,16:28
jungleboyjrajinir:  Great.  Thank you!16:28
whoami-rajati saw ryan liang pushing a lot of patches for VNX recently, not sure if he's on IRC.16:28
whoami-rajatrajinir: thanks for the update.16:28
rajinirryan liang is also part of that hao's team. Time zone issues16:29
jungleboyjYay timezones.16:29
whoami-rajatrajinir: oh ok16:29
jungleboyjOk, so if that is being worked we can move forward.16:29
jungleboyj#topic Move away from courtesy pings?16:29
*** openstack changes topic to "Move away from courtesy pings? (Meeting topic: Cinder)"16:29
rajinircan we assign this bug to ryan https://bugs.launchpad.net/cinder/+bug/179595716:29
openstackLaunchpad bug 1795957 in Cinder "VNX unit tests are not Python 3.7 compatible" [Undecided,Confirmed]16:29
jungleboyjrajinir:  ++16:29
whoami-rajatrajinir: ++16:30
rosmaitarajinir: is ryan at emc.com?16:30
rajinirrosmaita: dell emc is one company now, yes16:30
rosmaitaok, just wanted to make sure i had the correct person16:31
jungleboyj:-)16:31
rajinirrosmaita: ++16:31
*** dklyle has quit IRC16:31
jungleboyjSo, there has been discussion with some groups that Courtesy Pings for meetings are bad form.16:31
jungleboyjThough, it doesn't seem that everyone is in agreement.16:31
jungleboyjFor those of us that use IRC Cloud I have not yet figured out a way to highlight on 'startmeeting <cinder|oslo>' etc.16:32
jungleboyjHighlighting on just Cinder gets me spammed all the time.16:32
jungleboyjSo, I personally think that the pings work nicely for those of us that see meeting reminders, get busy and forget.16:32
rosmaitajungleboyj: ++16:33
rajinirjungleboyj: ++16:33
_erlon_it works for me16:33
bnemecIck. I'm finding that the docs for Quassel's highlight configuration are somewhat lacking too.16:33
jungleboyjI was going to propose that I remove the current ping list as I know there are a number of people on there that don't attend anymore.16:33
jungleboyjIf you want to be pinged, please add your name back in.16:33
e0nejungleboyj: it works better than calendar reminder for me:)16:33
rosmaitawe can call it a "discourteous ping", that would still work for me16:34
smcginnisI agree with Morgan's post that as long as the list is self-managed, there's no reason not to use it.16:34
smcginnisrosmaita: ++ :)16:34
bnemecIt might be worth requiring everyone to re-subscribe each cycle?16:34
jungleboyjI can also send an e-mail to the mailing list so people know.16:34
enriquetasorosmaita++16:34
bnemecI know in Oslo we almost certainly have some stale entries in our ping list.16:34
jungleboyjbnemec:  ++16:34
jungleboyjbnemec:  Yeah, if you lose the pings, I am probably going to miss your meeting more often than not.16:34
mszwed_jungleboyj ++16:35
* bnemec needs to do more than skim the responses to that thread16:35
jungleboyjEspecially on a Monday morning.  :-)16:35
bnemecYeah, no kidding.16:35
bnemecThe PTL should propose a reschedule to a less terrible time. ;-)16:35
jungleboyjOk, so are we in agreement we keep the pings and I am just going to remove the current list in the Train etherpad so that people can add themselves back in if wanted?16:35
rosmaitasounds good16:36
mszwed_You can't satisfy every time zone ;-)16:36
jungleboyjmszwed_:  Sad but true.16:36
bnemecYeah, I'm pretty sure that's why it is when it is.16:36
bnemecThe previous PTL is in China so it was the only time that sort of worked.16:36
mszwed_jungleboyj but send mail with that info16:36
rosmaitawe once tried having different meeting times every other week in glance, but that didn't work, everyone always had the time wrong16:37
jungleboyjmszwed_:  Of course.16:37
*** dklyle has joined #openstack-meeting16:37
jungleboyjrosmaita: ++16:37
enriquetasoI agree with the pings16:38
jungleboyjThis time doesn't work for China unfortunately, but at least we are getting most people.16:38
jungleboyjOk, seems like we more or less have agreement on the pings.16:38
mszwed_In SPDK we are using two time slots: US/China and US/Europe friendly, but it's not the best16:38
*** gyee has joined #openstack-meeting16:38
jungleboyjI have been with groups like that and it seemed to just result in two less useful meetings with a lot of repetition.16:39
jungleboyjAnyway, barring disagreement, lets move on.16:39
mszwed_Exactly16:39
jungleboyj#topic proposal to change stable/pike,queens u-c to address a CVE16:40
*** openstack changes topic to "proposal to change stable/pike,queens u-c to address a CVE (Meeting topic: Cinder)"16:40
* jungleboyj nominates rosmaita as shadow PTL16:40
rosmaitai just can't keep my mouth shut16:40
rosmaitaanyway, this is looking like it may be a non-issue16:40
jungleboyj#link http://lists.openstack.org/pipermail/openstack-discuss/2019-May/005956.html16:40
smcginnisThe requests CVE is something that the requirements team will need to control, but we can provide input on that thread.16:40
jungleboyj#link https://review.opendev.org/#/q/topic:cve-2018-18074+status:open16:40
rosmaitashort version, there was a proposal to change hte upper-constraints for requests to address a CVE16:41
rosmaitaon stable/pike and stable/queens16:41
rosmaitawhich is a pretty unusual thing to do16:41
rosmaitaanyway, i put up some patches to see what would happen to cinder, os-brick, and the cinderclient16:41
jungleboyjThanks for catching that.16:41
jungleboyjrosmaita:  Awesome!16:42
rosmaitathey look ok, except for all the failures on non-voting jobs16:42
*** hemna has joined #openstack-meeting16:42
rosmaitaso it might be a good idea for people to take a quick look if they have any interest in some of the non-voting jobs16:42
rosmaitabut like i said, it's starting to look like the change won't happen16:42
rosmaitabut this is openstack, so you never know16:43
rosmaitathat's all16:43
_erlon_rosmaita: what is the point for not having the change?16:43
jungleboyjCool.  Thank you for bringing that up.16:43
rosmaitathat it destablilizes the branches, and it's up to each consumer to make the update if they want ot16:44
rosmaita_erlon_: ^^16:44
_erlon_rosmaita: hmm, got it16:44
rosmaita_erlon_: the justification is a bit more nuanced, but that's basically it16:45
*** bbowen has quit IRC16:45
*** bbowen has joined #openstack-meeting16:45
jungleboyjrosmaita:  Will you keep an eye at as to whether that looks like it is going to go forward?16:45
jungleboyjLet us know if we need to look closer.16:45
rosmaitajungleboyj: yes, i will follow the action on that16:46
jungleboyjrosmaita:  Cool.  Thanks.16:46
jungleboyjSo, next topic.16:46
jungleboyj#topic Unified limits implementation16:47
*** openstack changes topic to "Unified limits implementation (Meeting topic: Cinder)"16:47
jungleboyjwhoami-rajat:16:47
whoami-rajatI should have probably brought that up at the PTG but anyways16:47
whoami-rajati've encountered bugs in past related to quotas, most of which will (i think) be solved after unified limits implementation.16:47
whoami-rajatnova has already started working on the same,16:47
whoami-rajatin a brief: all quota management will be handled at keystone database and limits will be enforced by the oslo.limits lib.16:48
jungleboyjwhoami-rajat:  I think we touched on this at the PTG and that we did want to make the move.16:48
whoami-rajatI'm willing to work on it if everyone has an agreement to start with the implementation in cinder.16:48
jungleboyjIt was secondary to a discussion that smcginnis started.16:49
jungleboyjwhoami-rajat:  I have no objections16:49
whoami-rajatoh, i was unaware that work has already started on cinder side jungleboyj16:49
smcginnisWe may want to wait until U so we can also remove that nested quota driver, but if it can be done now and worked into the current implementation, that's great.16:49
smcginnisThe work itself hasn't been started, but that was deprecated to try to clean up some of the code before we make any major changes.16:50
jungleboyjwhoami-rajat:  Work hadn't started.  It was just related to smcginnis wanting to remove the nested quota driver.16:50
jungleboyjsmcginnis: ++16:50
bnemecNote that oslo.limit isn't implemented yet. It's just a bare repo.16:50
bnemecWe'd love to have more input on the initial implementation though.16:50
smcginnisThough really, not sure if we need to deprecate that like we do with backend drivers. There will probably be major changes anyway, so since we do a major version bump each cycle, we can make backwards incompatible changes.16:51
smcginnisbnemec: Good point. I didn't think we were quite ready for everyone to jump on unified limits quite yet.16:51
whoami-rajat#link https://review.opendev.org/#/c/602201/816:52
whoami-rajatspec from nova side16:52
smcginnisWould definitely be good to keep an eye on that to make sure things don't end up too nova-centric and have issues for others to adapt to.16:53
jungleboyjsmcginnis:  ++16:53
jungleboyjSo, at this point whoami-rajat  it sounds like your work would to be to keep an eye on how the development of UL is going and make sure it matches with what we will need.16:54
jungleboyjWe do want to move to it and have it fix our quota issues, so it is time well spent.16:54
rosmaitahere's sean's patch deprecating the nested quota driver: https://review.opendev.org/#/c/657511/16:54
whoami-rajatjungleboyj:  ack16:54
smcginnisI think Cinder is the only project (that I know of) that ever tried implementing hierarchical quotas, so Cinder probably would be a better place to start. So I guess it just comes down to someone having the time to push it.16:55
jungleboyjsmcginnis:  ++16:55
jungleboyjSounds like we have a volunteer?16:55
whoami-rajatjungleboyj: can do16:56
jungleboyjwhoami-rajat:  Thank you!16:56
whoami-rajatjungleboyj: mp :)16:56
jungleboyjOk, I had wanted to cover priorities for the release but we are short on time.  I can work on getting things organized for next week and cover it then.16:56
jungleboyj_alastor_:  Tempest.16:57
_alastor_yeah16:57
_alastor_what gives?16:57
*** ociuhandu has quit IRC16:57
jungleboyjSo, is it just our documentation that is out of date?16:57
jungleboyjIs there a different process that needs to be followed?16:57
_alastor_I have no idea.  What I know is when I run tempest with 'all-plugin' in won't run16:58
jungleboyjenriquetaso:  You and Alan have been looking at Tempest some.  RIght?16:58
smcginnisSomeone should ask on the ML or in #openstack-qa what the current correct way is to run the tempest plugins.16:58
jungleboyjsmcginnis: ++16:58
smcginnisI think it might just pick them up and run them as long as the repos are added to the list that gets installed.16:58
jungleboyj_alastor_:  Would you be willing to start that discussion on the ML?16:59
_alastor_sure16:59
jungleboyjAwesome.  Thank you.16:59
*** ociuhandu has joined #openstack-meeting16:59
enriquetasojungleboyj, yup I've been working on cinder tempest17:00
jungleboyjenriquetaso:  Ok, if you have any insights for _alastor_  Can you let him know?17:00
jungleboyjAnd we are at time so lets continue that in the Cinder channel.17:00
enriquetaso'all-plugin' is not working for me neither17:00
jungleboyjThank you to everyone for joining us!17:00
enriquetasojungleboyj, _alastor_ yes, sure17:00
jungleboyjCool.17:01
jungleboyjTalk to you all next week.17:01
jungleboyj#endmeeting17:01
whoami-rajatThanks!17:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"17:01
openstackMeeting ended Wed May 15 17:01:13 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/cinder/2019/cinder.2019-05-15-16.00.html17:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/cinder/2019/cinder.2019-05-15-16.00.txt17:01
openstackLog:            http://eavesdrop.openstack.org/meetings/cinder/2019/cinder.2019-05-15-16.00.log.html17:01
jungleboyjwhoami-rajat:  Thank you!17:01
davidshaThanks17:01
*** woojay has left #openstack-meeting17:01
*** davidsha has left #openstack-meeting17:01
*** ijw has quit IRC17:03
*** rosmaita has left #openstack-meeting17:03
*** ricolin has quit IRC17:07
*** e0ne has quit IRC17:07
*** psachin has quit IRC17:15
*** bobh has quit IRC17:21
*** dklyle has quit IRC17:29
*** ttsiouts has joined #openstack-meeting17:35
*** mattw4 has joined #openstack-meeting17:40
*** yamamoto has joined #openstack-meeting17:41
*** mattw4 has quit IRC17:45
*** tssurya has quit IRC17:47
*** dklyle has joined #openstack-meeting17:49
*** yamamoto has quit IRC17:50
*** dklyle has quit IRC17:56
*** tesseract has quit IRC18:01
*** e0ne has joined #openstack-meeting18:10
*** e0ne has quit IRC18:13
*** dklyle has joined #openstack-meeting18:20
*** ttsiouts has quit IRC18:27
*** ab-a has quit IRC18:40
*** ianychoi has quit IRC18:42
*** ttsiouts has joined #openstack-meeting18:43
*** bbowen has quit IRC18:44
*** ttsiouts has quit IRC18:48
*** vishalmanchanda has quit IRC19:01
*** dklyle has quit IRC19:01
*** tssurya has joined #openstack-meeting19:02
*** bbowen has joined #openstack-meeting19:03
*** mattw4 has joined #openstack-meeting19:09
*** martial has quit IRC19:13
*** mattw4 has quit IRC19:13
*** e0ne has joined #openstack-meeting19:17
*** mszwed_ has quit IRC19:18
*** radeks_ has quit IRC19:18
*** radeks has joined #openstack-meeting19:18
*** dkehn has joined #openstack-meeting19:20
*** iyamahat has joined #openstack-meeting19:30
*** radeks has quit IRC19:47
*** radeks has joined #openstack-meeting19:48
*** radeks_ has joined #openstack-meeting19:51
*** radeks has quit IRC19:53
*** e0ne has quit IRC19:56
*** e0ne has joined #openstack-meeting19:59
*** pcaruana has quit IRC20:14
*** whoami-rajat has quit IRC20:24
*** e0ne has quit IRC20:28
*** diablo_rojo has quit IRC20:31
*** hemna has quit IRC20:35
*** dklyle has joined #openstack-meeting20:39
*** ttsiouts has joined #openstack-meeting20:45
*** ijw has joined #openstack-meeting20:50
*** radeks_ has quit IRC20:50
*** ijw has quit IRC20:52
*** ijw has joined #openstack-meeting20:52
*** hongbin has joined #openstack-meeting20:54
*** alecuyer has joined #openstack-meeting20:55
*** raildo_ has quit IRC20:59
*** patchbot has joined #openstack-meeting20:59
timburke#startmeeting swift21:00
openstackMeeting started Wed May 15 21:00:00 2019 UTC and is due to finish in 60 minutes.  The chair is timburke. Information about MeetBot at http://wiki.debian.org/MeetBot.21:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:00
*** openstack changes topic to " (Meeting topic: swift)"21:00
openstackThe meeting name has been set to 'swift'21:00
timburkewho's here for the swift meeting?21:00
mattoliverauo/21:00
kota_hi21:00
patchbotI'm here!21:00
tdasilvahello21:00
claygo/21:00
alecuyerhello o/21:01
*** diablo_rojo has joined #openstack-meeting21:01
timburke#link https://wiki.openstack.org/wiki/Meetings/Swift21:01
timburkeagenda's got a bunch of stuff we want updates on, and now everybody's had a little break from the PTG so there may have even been some progress ;-)21:01
timburkebut first, what do we think about a libec release?21:02
timburke#topic liberasurecode release21:02
*** openstack changes topic to "liberasurecode release (Meeting topic: swift)"21:02
*** dtrainor has quit IRC21:02
*** dtrainor has joined #openstack-meeting21:02
tdasilvatimburke: what's in it?21:03
* mattoliverau hasn't been keeping an eye on libec. I assume it's been a while. So long as there are some patches landed we want to get out, then yes.21:03
timburkezaitcev's been great about getting some warnings cleaned up, and it looked like someone (prometheanfire, maybe?) was bumping into some issues that are already fixed on master21:03
mattoliverauopps only the first 1/2 of that was suppose to be emoted -ETOOEARLY :P21:04
tdasilvafound this fix: https://github.com/openstack/liberasurecode/commit/7e97b2f808e1115425eef527899b27528f05af3a21:04
timburkethere hasn't been *that much* code that's landed, but it's also been... 9 months or so since our last release21:04
kota_oic. that's long time.21:05
timburketdasilva, the other patch of interest (in my view) is `3564b71 Remove get_chksum to hush warnings (by Pete Zaitcev, 3 months ago)`21:06
timburkeso, i'm thinking we ought to tag a 1.6.121:06
*** stevebaker is now known as steveb21:07
tdasilva+121:07
mattoliveraucrc32 and swift on s390 seems like a good enough reason. Less warning is good too.21:07
mattoliverau+121:07
*** ralonsoh has quit IRC21:07
timburkeand once we get around to reviewing and landing the quadiron stuff, we can do a 1.7.021:07
*** steveb is now known as stevebaker21:07
timburkebut the nice thing is, we can do these basically whenever we want. this was mostly just a heads-up21:07
timburkeon to updates!21:08
timburke#topic updates21:08
*** openstack changes topic to "updates (Meeting topic: swift)"21:08
timburke#topic tempurl restrictions21:08
*** openstack changes topic to "tempurl restrictions (Meeting topic: swift)"21:08
mattoliveraucool21:08
timburkemattoliverau, have you had a chance to look at this yet?21:08
mattoliverauso I almost pushed something up last night. but just fiddling with some SLO tests and want to check with symlinks21:09
mattoliverauI still need to play with symlinks, but can push what I have first21:09
mattoliverauSo when using tempurl prefixes + PUT if you head other containers objects and you always get a 401, if the object exists or not21:10
*** panda|ruck has quit IRC21:10
timburkeis the same true for HEADing objects in the same container but with a different prefix?21:11
mattoliverauwhen you allow X-Object-Manifest you can put what you want (items starting with prefix or not) and a GET to the DLO will get the contents. Which seems like the initial bug..21:11
mattoliverauI think so, I think I have a func test for that too.. but will confirm.21:12
timburkehmm...21:12
timburkewell, good to know. we'll keep an eye out for more tests!21:13
timburke#topic migration to storyboard21:13
*** openstack changes topic to "migration to storyboard (Meeting topic: swift)"21:13
mattoliverauWill push up some initial tests today :)21:13
timburkei know we asked to get a test migration going so we could start playing with the new system -- has that happened yet, or are we still waiting?21:13
mattoliverauI saw diablo_rojo join when the meeting started21:14
*** panda has joined #openstack-meeting21:14
mattoliverauI haven't heard anything, but will follow up with her today (if she's around).21:14
timburke\o/ diablo_rojo!21:14
timburkesounds good21:14
timburkethat was where i expected it to be, just wanted to check21:14
*** dklyle has quit IRC21:14
mattoliverauif summoning diablo_rojo doesn't work, what about diablo_rojo_phon?21:15
diablo_rojoo/21:15
mattoliverau\o/21:15
diablo_rojoHaha21:15
kota_lol21:15
diablo_rojoSo.. last week was not as productive as I would like it to have been, but I literally wrote the test migration down on my todo list for this week.21:15
diablo_rojoI will have it done by the next meeting.21:15
mattoliveraucool21:15
timburkeyay! thanks diablo_rojo!21:15
*** ttsiouts has quit IRC21:16
mattoliverauthanks!21:16
diablo_rojoI can go greate the project now in the dev storyboard if you want to make stories now.21:16
diablo_rojoIt wouldnt interfere with the migration.21:16
timburkei don't think anyone's actually getting impatient for it, i just want to make sure it doesn't fall off our radar :-)21:16
timburkeso, up to you21:16
diablo_rojotimburke, I appreciate that more than I can explain :)21:16
* diablo_rojo logs into the dev site now to make the project + project groups21:17
diablo_rojoprojects + project group21:17
diablo_rojowrong placement of plurality21:17
timburkecool, thanks!21:17
diablo_rojoI'll drop in the swift channel and ping when its done21:17
timburkeexcellent21:17
diablo_rojoshouldn't take me too long though21:17
timburke#topic container building21:17
*** openstack changes topic to "container building (Meeting topic: swift)"21:17
mattoliveraudiablo_rojo: kk, thanks again21:18
timburkeso we had containers building... and pushing to https://hub.docker.com/r/openstackswift/saio ...21:18
kota_yey21:19
timburkebut currently it's busted. -infra's got a patch to fix it... but it brings up a question i had about this:21:19
kota_(no overview available message i see)21:19
tdasilvakota_: yeah, we need to fix that21:20
timburkeshould an inability to build and/or publish container prevent us from merging code?21:20
timburke(the infra fix is https://review.opendev.org/#/c/659296/ which is all black magic to me)21:21
patchbotpatch 659296 - opendev/system-config - Pin skopeo to unbreak skopeo+bubblewrap - 3 patch sets21:21
mattoliverauoh interesting. I'd say for the -latest image.. no.21:21
tdasilvatimburke: IMO no, I was wondering the same thing if we should make those jobs non-voting21:21
mattoliveraubut if/when we get it tied into the release tooling, that should be important.. thought that doesn't prevent code landing. But is when it is a "critical" component21:22
*** Lucas_Gray has joined #openstack-meeting21:22
timburketdasilva, i think i'd be ok with that... but yeah, i've got the same thought as mattoliverau about if/when this gets tied into tag creation21:23
tdasilvatimburke: but even that I'd say can happen out-of-band. Ideally we should be able to go back and build container images for our past releases, no?21:24
mattoliveraulet's say yes? but to be honest I don't know how the release triggering works.21:25
tdasilvaI agree it's a super nice to have, but i'm not super concerned about it. the tooling doesn't exist yet, so we can cross that bridge when we get there???21:25
mattoliverauBut that's something we can donfirm when getting it set up21:25
tdasilvaright21:25
mattoliverautdasilva: +121:25
timburkeyeah, i'd hope so. getting it lined up with an appropriate version of upper-constraints might get interesting (particularly if we want to build images for pre-u-c tags), but surely we can sort it out as a manual thing21:26
tdasilvaI should have added: the tooling doesn't exist yet AFAIK. -infra said they would work on it after PTG21:26
timburkeall right, sounds like we're on board with making container stuff non-voting21:26
tdasilvatimburke: yeah, I was thinking that was the only caveat based on the conversation we had21:26
timburke#topic py321:27
*** openstack changes topic to "py3 (Meeting topic: swift)"21:27
timburketest/unit/proxy/ is done!21:27
timburkethat brings us up to ~83% of unit tests running under py321:27
mattoliverau\o/ nice21:27
timburkemost of the rest is in obj/ iirc21:28
timburkethough there are a few straggling middlewares21:28
timburkeon the func test front, we got some pre-reqs landed, but still no gate job yet21:28
*** dklyle has joined #openstack-meeting21:29
timburkecan anyone volunteer to review (some or all of) the chain starting at https://review.opendev.org/#/c/642520/ ?21:29
patchbotpatch 642520 - swift - Get functional/tests.py running under py3 - 16 patch sets21:29
timburke:-/21:31
mattoliverauI've been distracted with catching up with work stuff. But will try and loop back round to py3 today or tomorrow. So I'll volunteer to take a look, at atleast some21:31
timburkethank you mattoliverau!21:31
tdasilvatimburke: i'll get an environ setup and at least start running tests on those patches21:31
timburkethanks tdasilva21:32
timburkeseparately: at the PTG i set a goal of getting all unit and func tests passing by the end of the month. we're now halfway through May; how are people feeling about the feasibility of that goal?21:32
mattoliveraudepends on the functests. though there are less of them then unit tests.21:33
mattoliverauSo will reserve my comment until I start reviewing it :P21:34
timburkefair enough :-)21:34
timburkei knew it was a fairly aggressive goal, so in my head i put the odds at around 50/50 going in21:35
timburkei just want to get a feeling for how well i can forecast such things21:35
mattoliveraunah it's a good kick in the pants. if we need to push it out fine. but lighting a fire under us I think helps. especually in something like py3, where its tedious21:36
mattoliverauwow, my spelling sucks this morning. sorry :)21:37
timburkeonly other thing i've got on py3 is that i'm going to start prodding eventlet about doing another release. when we declare support, i'd really rather not have to tell people "just go grab whatever's on eventlet master" :P21:37
mattoliveraugood idea. how receptive are they as a community?21:38
* timburke shrugs21:38
mattoliverauie, do we need to start prodding now, last week, or the week before our release :P21:38
timburkethey take my patches, and seem reasonably responsive21:38
mattoliveraucool21:39
timburkei figure i ought to start prodding now, so i can *also* start working the openstack/requirements side sooner rather than later21:39
timburke#topic lots of small files21:40
*** openstack changes topic to "lots of small files (Meeting topic: swift)"21:40
timburkekota_, alecuyer, rledisez how goes it?21:40
kota_now we got the gate running against to losf backend!21:40
timburke\o/21:40
mattoliveraunice21:40
alecuyeryes! :)21:40
kota_everything works fine for now.21:41
timburke"for now" seems ominous :-)21:41
kota_#link https://trello.com/b/xhNxrcLX/losf21:41
kota_alecuyer is still digging some dependency issues21:41
alecuyerstill grpc issues yes21:42
kota_and i've started on some docs and... cleanuping.21:42
alecuyerthe latest version does run functests but it fails with concurrency (real workload). I'll post more details about it21:42
*** mlavalle has left #openstack-meeting21:43
alecuyerso I think I should work on moving to HTTP (I started). And, writing unit tests21:43
kota_with the work to get the gate job, I found some issues like where we should manage the logs, process naming, etc...21:43
kota_so I want to try the works, with stable gate ;)21:44
kota_alecuyer: +121:44
timburkethat all sounds great! is there anything the rest of us should be doing to help?21:45
kota_not so much to me for now, alecuyer do you?21:46
alecuyerNo, not yet I think21:46
timburkeall right. keep us updated!21:47
timburke#topic open discussion21:47
*** openstack changes topic to "open discussion (Meeting topic: swift)"21:47
timburkedoes anyone have anything else to bring up?21:47
*** yamamoto has joined #openstack-meeting21:49
timburkewell, i started to break up https://review.opendev.org/#/c/648263/ into something that might be useful and *not* have the same risk of creating dark data21:50
patchbotpatch 648263 - swift - WIP: s3api: Make multi-deletes async - 5 patch sets21:50
timburke#link https://review.opendev.org/#/c/659162/21:50
patchbotpatch 659162 - swift - Add operator tool to async-delete some or all obje... - 3 patch sets21:50
timburkejust as a heads up21:51
mattoliveraucool21:52
timburkei'd be very interested in alecuyer or rledisez's opinion on it (since i'm claiming it would be useful for an operator)21:52
alecuyerI'll look at the patch tomorrow ,21:52
timburkethanks alecuyer!21:52
alecuyersee if we can try it, and yes it would be useful :)21:52
*** yamamoto has quit IRC21:54
timburkeeventually, i'd kinda like to leverage it into a kind of container-reaper, and let clients do something like DELETE /v1/AUTH/test/c?recursive=true21:54
timburkewell, that's all i've got, and it looks like we're getting to the end of our slot anyway21:54
timburkethank you all for coming, and thank you for working on swift!21:55
alecuyerthank you21:55
timburke#endmeeting21:55
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"21:55
openstackMeeting ended Wed May 15 21:55:31 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:55
openstackMinutes:        http://eavesdrop.openstack.org/meetings/swift/2019/swift.2019-05-15-21.00.html21:55
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/swift/2019/swift.2019-05-15-21.00.txt21:55
openstackLog:            http://eavesdrop.openstack.org/meetings/swift/2019/swift.2019-05-15-21.00.log.html21:55
*** patchbot has left #openstack-meeting21:55
*** mattw4 has joined #openstack-meeting21:56
*** rbudden has quit IRC21:59
*** dklyle has quit IRC22:00
*** mattw4 has quit IRC22:03
*** patchbot has joined #openstack-meeting22:08
*** patchbot has left #openstack-meeting22:08
*** stevebaker has quit IRC22:11
*** artom has quit IRC22:11
*** stevebaker has joined #openstack-meeting22:12
*** ttsiouts has joined #openstack-meeting22:32
*** tdasilva has quit IRC22:43
*** mriedem has quit IRC22:51
*** notmyname has quit IRC22:56
*** macza has quit IRC22:59
*** notmyname has joined #openstack-meeting22:59
*** mattw4 has joined #openstack-meeting23:01
*** ttsiouts has quit IRC23:06
*** Adri2000 has quit IRC23:09
*** rbudden has joined #openstack-meeting23:09
*** Lucas_Gray has quit IRC23:11
*** Adri2000 has joined #openstack-meeting23:12
*** rcernin has joined #openstack-meeting23:14
*** ykatabam has joined #openstack-meeting23:14
*** carloss has quit IRC23:15
*** rbudden has quit IRC23:18
*** mattw4 has quit IRC23:21
*** yamamoto has joined #openstack-meeting23:26
*** panda has quit IRC23:30
*** panda has joined #openstack-meeting23:31
*** tssurya has quit IRC23:32
*** d34dh0r53 has joined #openstack-meeting23:43
*** d34dh0r53 has quit IRC23:58

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