Wednesday, 2020-01-22

*** ykatabam has quit IRC00:06
*** martial has quit IRC00:08
*** mattw4 has quit IRC00:10
*** ykatabam has joined #openstack-meeting00:17
*** ykatabam has quit IRC00:19
*** rbudden has joined #openstack-meeting00:39
*** ayoung has quit IRC00:46
*** ayoung has joined #openstack-meeting00:47
*** rbudden has quit IRC00:57
*** rbudden has joined #openstack-meeting00:57
*** rbudden has quit IRC00:58
*** rbudden has joined #openstack-meeting00:58
*** rbudden has joined #openstack-meeting00:59
*** rbudden has joined #openstack-meeting01:00
*** njohnston_ has joined #openstack-meeting01:00
*** Lucas_Gray has quit IRC01:15
*** rbudden has quit IRC01:15
*** rbudden has joined #openstack-meeting01:16
*** rbudden has joined #openstack-meeting01:16
*** njohnston_ has quit IRC01:17
*** rbudden has quit IRC01:17
*** rbudden has joined #openstack-meeting01:17
*** rbudden has quit IRC01:18
*** rbudden has joined #openstack-meeting01:18
*** rbudden has joined #openstack-meeting01:19
*** rbudden has quit IRC01:19
*** rbudden has joined #openstack-meeting01:20
*** enriquetaso has quit IRC01:21
*** jamesmcarthur has joined #openstack-meeting01:26
*** jamesmcarthur has quit IRC01:38
*** yamamoto has joined #openstack-meeting01:42
*** jamesmcarthur has joined #openstack-meeting01:47
*** yamamoto has quit IRC01:53
*** hyunsikyang__ has joined #openstack-meeting02:02
*** gyee has quit IRC02:04
*** hyunsikyang has quit IRC02:06
*** Liang__ has quit IRC02:06
*** maohongbo has quit IRC02:14
*** maohongbo has joined #openstack-meeting02:14
*** yamamoto has joined #openstack-meeting02:23
*** jamesmcarthur has quit IRC02:50
*** diablo_rojo has quit IRC03:06
*** apetrich has quit IRC03:10
*** jamesmcarthur has joined #openstack-meeting03:13
*** yamamoto has quit IRC03:27
*** jamesmcarthur has quit IRC04:14
*** jamesmcarthur has joined #openstack-meeting04:15
*** jamesmcarthur has quit IRC04:21
*** ayoung has quit IRC04:36
*** jamesmcarthur has joined #openstack-meeting04:45
*** rh-jelabarre has quit IRC04:47
*** jamesmcarthur has quit IRC04:49
*** yamamoto has joined #openstack-meeting04:56
*** links has joined #openstack-meeting05:16
*** artom has quit IRC05:28
*** maohongbo1 has joined #openstack-meeting05:49
*** maohongbo has quit IRC05:51
*** maohongbo1 is now known as maohongbo05:51
*** ociuhandu has joined #openstack-meeting06:15
*** ociuhandu has quit IRC06:20
*** ykatabam has joined #openstack-meeting06:20
*** hyunsikyang__ has quit IRC06:35
*** maohongbo1 has joined #openstack-meeting06:47
*** maohongbo has quit IRC06:48
*** maohongbo1 is now known as maohongbo06:48
*** vishalmanchanda has quit IRC07:24
*** rpittau|afk is now known as rpittau07:37
*** lpetrut has joined #openstack-meeting07:47
*** yaawang has quit IRC07:50
*** ykatabam has quit IRC07:52
*** slaweq_ has joined #openstack-meeting07:59
*** e0ne has joined #openstack-meeting08:00
*** ykatabam has joined #openstack-meeting08:03
*** tesseract has joined #openstack-meeting08:08
*** tesseract has quit IRC08:09
*** tesseract has joined #openstack-meeting08:09
*** bnemec has joined #openstack-meeting08:09
*** davee_ has quit IRC08:14
*** davee_ has joined #openstack-meeting08:14
*** apetrich has joined #openstack-meeting08:17
*** ykatabam has quit IRC08:19
*** ykatabam has joined #openstack-meeting08:20
*** e0ne has quit IRC08:22
*** e0ne_ has joined #openstack-meeting08:23
*** e0ne_ has quit IRC08:23
*** e0ne has joined #openstack-meeting08:23
*** slaweq_ has quit IRC08:33
*** e0ne has quit IRC08:42
*** ralonsoh has joined #openstack-meeting08:51
*** yamamoto has quit IRC09:02
*** brinzhang has quit IRC09:08
*** maohongbo has quit IRC09:31
*** maohongbo has joined #openstack-meeting09:31
*** maohongbo has quit IRC09:33
*** e0ne has joined #openstack-meeting10:13
*** ociuhandu has joined #openstack-meeting10:30
*** ociuhandu has joined #openstack-meeting10:31
*** hyunsikyang has joined #openstack-meeting10:41
*** pcaruana has joined #openstack-meeting11:02
*** dviroel has joined #openstack-meeting11:03
*** ociuhandu has quit IRC11:15
*** ociuhandu has joined #openstack-meeting11:27
*** raildo has joined #openstack-meeting11:37
*** rpittau is now known as rpittau|bbl11:41
*** ociuhandu has quit IRC11:42
*** ociuhandu has joined #openstack-meeting12:00
*** ociuhandu has quit IRC12:08
*** ociuhandu has joined #openstack-meeting12:09
*** jawad_axd has joined #openstack-meeting12:24
*** dmellado has quit IRC12:24
*** dmellado has joined #openstack-meeting12:26
*** zbr has quit IRC12:34
*** zbr has joined #openstack-meeting12:35
*** zbr_ has joined #openstack-meeting12:43
*** zbr has quit IRC12:46
*** zbr_ has quit IRC12:46
*** zbr has joined #openstack-meeting12:48
*** enriquetaso has joined #openstack-meeting12:51
*** yamamoto has joined #openstack-meeting13:08
*** rh-jelabarre has joined #openstack-meeting13:10
*** ociuhandu has quit IRC13:14
*** ociuhandu has joined #openstack-meeting13:18
*** jamesmcarthur has joined #openstack-meeting13:18
*** rpittau|bbl is now known as rpittau13:20
*** ociuhandu has quit IRC13:22
*** zbr has quit IRC13:26
*** zbr has joined #openstack-meeting13:29
*** jamesmcarthur has quit IRC13:34
*** jamesmcarthur has joined #openstack-meeting13:49
*** yamamoto has quit IRC14:01
*** rbudden has joined #openstack-meeting14:02
*** rcernin has quit IRC14:03
*** ykatabam has quit IRC14:08
*** yamamoto has joined #openstack-meeting14:10
*** yamamoto has quit IRC14:10
*** yamamoto has joined #openstack-meeting14:10
*** jamesmcarthur has quit IRC14:14
*** yamamoto has quit IRC14:15
*** ociuhandu has joined #openstack-meeting14:18
*** links has quit IRC14:23
*** Liang__ has joined #openstack-meeting14:33
*** eharney has joined #openstack-meeting14:34
*** ociuhandu has quit IRC14:40
*** ociuhandu has joined #openstack-meeting14:41
*** jamesmcarthur has joined #openstack-meeting14:45
*** jamesmcarthur has quit IRC14:46
*** jamesmcarthur has joined #openstack-meeting14:46
*** priteau has joined #openstack-meeting14:58
*** Liang__ is now known as LiangFang14:59
*** vishalmanchanda has joined #openstack-meeting14:59
*** LiangFang has quit IRC15:05
*** jawad_axd has quit IRC15:08
*** jawad_axd has joined #openstack-meeting15:09
*** ociuhandu has quit IRC15:13
*** jawad_axd has quit IRC15:16
*** priteau has quit IRC15:28
*** ociuhandu has joined #openstack-meeting15:47
*** artom has joined #openstack-meeting15:49
*** ociuhandu has quit IRC16:11
*** ociuhandu has joined #openstack-meeting16:15
*** gyee has joined #openstack-meeting16:16
*** ociuhandu has quit IRC16:20
*** mattw4 has joined #openstack-meeting16:24
*** diablo_rojo has joined #openstack-meeting16:34
*** armax has joined #openstack-meeting16:35
*** rsimai is now known as rsimai_away16:48
*** bnemec has quit IRC16:51
*** ociuhandu has joined #openstack-meeting16:56
*** rpittau is now known as rpittau|afk17:03
*** mattw4 has quit IRC17:12
*** mattw4 has joined #openstack-meeting17:19
*** ociuhandu has quit IRC17:22
*** diablo_rojo has quit IRC17:42
*** jawad_axd has joined #openstack-meeting17:48
*** jawad_axd has quit IRC17:52
*** eharney has quit IRC18:03
*** jamesmcarthur has quit IRC18:05
*** jamesmcarthur has joined #openstack-meeting18:06
*** jamesmcarthur has quit IRC18:07
*** jawad_axd has joined #openstack-meeting18:08
*** eharney has joined #openstack-meeting18:15
*** vishalmanchanda has quit IRC18:17
*** e0ne has quit IRC18:19
*** jawad_axd has quit IRC18:19
*** diablo_rojo has joined #openstack-meeting18:19
*** jamesmcarthur has joined #openstack-meeting18:38
*** tesseract has quit IRC18:40
*** yamamoto has joined #openstack-meeting18:59
*** jamesmcarthur has quit IRC19:00
*** yamamoto has quit IRC19:04
*** ralonsoh has quit IRC19:06
*** jamesmcarthur has joined #openstack-meeting19:13
*** e0ne has joined #openstack-meeting19:38
*** gmann is now known as gmann_afk19:38
*** e0ne has quit IRC19:47
*** eharney has quit IRC20:04
*** gmann_afk is now known as gmann20:18
*** diablo_rojo has quit IRC20:38
*** enriquetaso has quit IRC20:46
*** panda has quit IRC20:49
*** panda has joined #openstack-meeting20:51
*** artom has quit IRC20:52
*** alecuyer has joined #openstack-meeting20:59
timburke#startmeeting swift21:00
openstackMeeting started Wed Jan 22 21:00:00 2020 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
alecuyero/21:00
mattoliverauo/21:00
rledisezo/21:00
*** patchbot has joined #openstack-meeting21:00
tdasilvao/21:00
claygo/21:00
kota_o/21:01
timburkenot too much on the agenda: https://wiki.openstack.org/wiki/Meetings/Swift21:01
timburkemainly i want to talk about21:01
timburke#topic upcoming release21:01
*** openstack changes topic to "upcoming release (Meeting topic: swift)"21:01
timburkep 701497 has merged21:01
patchbothttps://review.opendev.org/#/c/701497/ - swift - py3: Fix formpost unicode filename issues (MERGED) - 3 patch sets21:01
timburkep 701736 is working its way through the gate21:02
patchbothttps://review.opendev.org/#/c/701736/ - swift - Allow bulk to fwd some headers at tar extraction - 3 patch sets21:02
timburkewhich means there's just two (kind of three) bodies of work i'd like to see land before cutting a release21:02
timburkep 70265021:03
patchbothttps://review.opendev.org/#/c/702650/ - octavia-tempest-plugin - Add scenario test for IPv6 VIP and IPv6-only members - 1 patch set21:03
timburkeer, no -- p 70295021:03
patchbothttps://review.opendev.org/#/c/702950/ - swift - Allow Timestamp comparisons against out-of-range v... - 2 patch sets21:03
timburke(and maybe its follow-on, p 703155)21:04
patchbothttps://review.opendev.org/#/c/703155/ - swift - Store normalized x-delete-at on PUT/POST - 3 patch sets21:04
timburkeand versioning21:04
claygso lp bug #1860149 - is there any downside to landing p 70295021:05
openstackLaunchpad bug 1860149 in OpenStack Object Storage (swift) "Large X-Delete-At values cause object-server to 500" [High,In progress] https://launchpad.net/bugs/186014921:05
patchbothttps://review.opendev.org/#/c/702950/ - swift - Allow Timestamp comparisons against out-of-range v... - 2 patch sets21:05
timburkeso first -- can anyone volunteer to review the timestamp patch? i'd kinda like to let seongsoocho's customers access their data again ;-)21:05
claygyeah, i agree lp bug #1860149 is pretty awful21:05
alecuyerouch21:06
timburkeclayg, i don't think so -- i guess the only question left in my mind is whether we should 400 delete-ats that are more than, say, 100 years in the future21:06
claygI mean I can "review" p 702950 - but the only contribution that'll really come out of it is a func test change to follow on and a +A 🤣21:06
patchbothttps://review.opendev.org/#/c/702950/ - swift - Allow Timestamp comparisons against out-of-range v... - 2 patch sets21:06
kota_i'll be back to https://review.opendev.org/#/c/702950/21:06
patchbotpatch 702950 - swift - Allow Timestamp comparisons against out-of-range v... - 2 patch sets21:06
*** slaweq_ has joined #openstack-meeting21:07
*** sfernand has quit IRC21:07
*** pcaruana has quit IRC21:07
timburkethanks clayg and kota_! your input will be invaluable, i'm sure :-)21:07
timburke#topic versioning21:07
*** openstack changes topic to "versioning (Meeting topic: swift)"21:08
timburkeso i think i'd still like this ahead of a release -- does anyone worry that we should tag sooner rather than wait for it?21:08
*** anastzhyr has joined #openstack-meeting21:10
claygtimburke: just to clarify who you're asking - kota_ or alecuyer or seongsoocho, right?  SwiftStack already shipped it - but I hear we're still waiting on the customer to upgrade, so we'd definately like to get a tag on it.21:11
kota_either is fine to me, any tagged point will be acceptable from my org.21:12
alecuyerwaiting until the patches you mentionned are in sounds reasonnable21:12
timburkeclayg, yeah, i suppose so -- though a fresh tag with fresh features would also mean we'll likely see new bug reports that increases *your* support burden, too ;-)21:13
claygtimburke: mostly *yours* but... also it'd be nice to have sweet shiny changelog!21:13
timburkehell yeah it would be!21:14
timburkebetween p 682382 and p 698139 i think the swift API is pretty solid -- the only thing i'm still wavering on is whether/how we ought to deal with primary containers that (for whatever reason) don't have their %00versions%00 container even though they've got metadata thinking that they should21:14
patchbothttps://review.opendev.org/#/c/682382/ - swift - New Object Versioning mode - 74 patch sets21:14
patchbothttps://review.opendev.org/#/c/698139/ - swift - Skip container-sync when versioning enabled - 14 patch sets21:14
claygkota_: alecuyer: I really hope you're gunna like versioning, @timburke and @tdasilva worked really hard on it, and I think it's pretty great21:14
rledisezI don't have the changelog in mind, but the versioning/null sperator seems the bug thing of this release, one is only something if it is enabled, the other I guess is only used by versioning. so having it in the next release does not seem an issue21:14
rledisez*the big thing21:14
timburkeFreudian slip ;-)21:15
rledisezso i guess both options are fine for me21:15
kota_clayg: +100, I support the work. I don't have much time to look the spec for now but I trust the authors.21:16
timburkemy question on the swift api is: should we make sure that case is covered/tested, or does it seem sufficiently unlikely that we'd be ok with addressing it in a follow-up (potentially after a release)21:16
claygtimburke: right it's impossible to say how that situation resolves symantically eventually - so we either leave it undefined or pick how it should be (either way seems reasonable to me)21:17
rlediseztimburke: I *think* (but not have a string opinion for now) I would not enable the new versioning until the container-sync is working with it, because it would create confusion for sure to our customers21:18
tdasilvawe should at least make it possible for ops to fix it, right now i think they would have to delete the primary container all together, which isn't great21:18
claygoh no!  bummer...21:18
claygtdasilva: oh, ideally re-issuing the enable versioning request would soome how make sure the versions container was available for subsequent requests21:19
tdasilvaclayg: +121:20
timburketdasilva, if we're talking ops, they could use a direct client to pop the reserved container back into existence -- but yeah, i'd like it to be something an external client can fix21:20
tdasilvai think it would be nice to fix that21:20
timburkeso, before or after a merge? ;-)21:20
tdasilvaheh, that's the question!21:20
claygahahah, if it's a bug we can demonstrate it should be before!21:21
tdasilvai'd say, let's mere as is, and follow-up patch before release21:21
claygmaybe I'll fix it and merge it before you guys find anymore - then we can start tracking and prioritizing them in launchpad21:21
mattoliveraucan't you just create it on any new put request? But I guess I don't understand the problem. I'd hope if they magically came back (sitting on a power off node) they'd just sync back up.21:21
mattoliveraubut, I'm sure there is something obvious I'm missing. /me will try and take a look at the code now that I'm back home.21:22
claygtdasilva: that's an ok idea - I have merged things while opening new bugs because they seemed sufficiently orthoganal - but it was never a "that's minor" kind of thing21:22
tdasilvamattoliverau: currently no, and that's what needs to be fixed21:22
claygmattoliverau: no, i agree - most likly this out of sync conditions are temporary21:22
tdasilvaclayg: I'm just trying to avoid we get to 100 patchset mark :D21:23
mattoliveraulol21:23
claygbut I suppose it's possible the way it's implemented the client just say what they want and continue on their way - they have to wait for the cluster to fix something at somepoint... and tdasilva and timburke say that should be something a client should be able to fix right away21:23
timburketdasilva, that's still like 25, 26 away! lot's of time :P21:23
*** eharney has joined #openstack-meeting21:23
claygtdasilva: LOL21:23
claygtdasilva: i can really HEAR your voice in my head when you say that!!!  😍21:24
claygtimburke: tdasilva: was that the only issue?21:25
claygtimburke: tdasilva: it sounds like we might be the only ones using it for awahile (like OVH is stuck with container-sync)21:25
tdasilvathat we know of :/21:25
claygwell I just mean that probably makes it easier to merge and just open a bug on lp - you can assign the bug to me if you want21:26
claygI was ready to merge it last week and I'm sure it's only gotten better 👍21:26
timburkei think that's my big blocker. there are a couple other funny things i've found, mostly to do with listings -- very minor things. limit not being respected in some non-happy-path cases, stuff like that21:26
claygtimburke: ok, we'll if you got some stuff in your head already you want to unload before we merge it that's fine - let's get to it21:27
timburkeeh, i'd be fine with fixing up listings in follow-ups21:28
timburkeon the s3 patch 673682 though... i've got a few more worries21:28
patchbothttps://review.opendev.org/#/c/673682/ - swift - s3api: Implement object versioning API - 45 patch sets21:28
timburkei need to get more of that loaded into my head i think21:28
claygoh, ok then!21:28
*** hesonline has joined #openstack-meeting21:28
timburkethat said, though, part of the reason for having them as separate patches was that they're separate (if dependent) features and we could merge to s3 one later21:30
claygtimburke: yeah that's find - do you want to merge versoining; then tag; then probably merge s3api support after that?21:31
timburkeclayg, that's one of the things i'm debating about21:32
tdasilvawon't help with release notes tho21:32
timburkehonestly, i'm not sure21:32
claygok, well step 1 is the versioning - and it sounds like you could use some help - is ther a repro/setup script/test for the split container or listing things?21:33
claygor... just a bunch of review comments somewhere between patch #10-#86?21:33
patchbotNo data found for patch 1021:33
timburkemaybe i should just push up my edits to the s3 patch and let it go in, too21:33
claygwell, you should definately push up your edits :D21:33
*** hesonline has quit IRC21:34
timburkeclayg, enable versioning on a container, then use an internal client or something to go delete the versions container21:34
*** diablo_rojo has joined #openstack-meeting21:34
timburkewe've already got a probe test that exercises the converse; i just haven't gotten around to writing this test yet21:35
timburkeall right, sounds like we've got something of a plan for how what to do next on versioning...21:36
timburke#topic open discussion21:36
*** openstack changes topic to "open discussion (Meeting topic: swift)"21:36
timburkedoes anyone have anything else they'd like to bring up?21:37
*** enriquetaso has joined #openstack-meeting21:39
timburkeall right, then21:40
timburkethank you all for coming, and thank you for working on swift!21:40
timburke#endmeeting21:40
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"21:40
openstackMeeting ended Wed Jan 22 21:40:40 2020 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:40
openstackMinutes:        http://eavesdrop.openstack.org/meetings/swift/2020/swift.2020-01-22-21.00.html21:40
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/swift/2020/swift.2020-01-22-21.00.txt21:40
openstackLog:            http://eavesdrop.openstack.org/meetings/swift/2020/swift.2020-01-22-21.00.log.html21:40
*** alecuyer has left #openstack-meeting21:41
*** Lucas_Gray has joined #openstack-meeting21:41
*** rcernin has joined #openstack-meeting21:50
*** ykatabam has joined #openstack-meeting21:58
*** armax_ has joined #openstack-meeting22:07
*** armax has quit IRC22:12
*** armax_ is now known as armax22:12
*** slaweq_ has quit IRC22:25
*** dviroel has quit IRC22:25
*** jamesmcarthur has quit IRC22:44
*** Lucas_Gray has quit IRC23:00
*** Lucas_Gray has joined #openstack-meeting23:02
*** njohnston has quit IRC23:08
*** njohnston has joined #openstack-meeting23:11
*** rbudden has quit IRC23:27
*** diablo_rojo has quit IRC23:51
*** mattw4 has quit IRC23:51

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