Thursday, 2020-02-20

seongsoochotimburke:  The swift Meeting logs still link to 2019.   https://wiki.openstack.org/wiki/Meetings/Swift00:14
*** diablo_rojo has quit IRC00:33
*** gyee has quit IRC00:48
*** xiaolin has joined #openstack-swift00:59
openstackgerritMerged openstack/swift master: Revert "Make rolling-upgrade job non-voting until virtualenv problem is solved"  https://review.opendev.org/70871901:02
timburkeseongsoocho, thank! updated02:00
*** openstackstatus has joined #openstack-swift02:56
*** ChanServ sets mode: +v openstackstatus02:56
*** psachin has joined #openstack-swift03:32
*** evrardjp has quit IRC03:42
*** evrardjp has joined #openstack-swift03:45
*** xiaolin has quit IRC03:54
kota_timburke: if you have any pointer for Vancouver Dev Event survey you asked in the meeting today, could you let me know?03:56
kota_I checked my e-mail directory but I couldn't find any info like attendees, whether the project will have the dev meeting there.03:58
zaitcevDoes anyone have a library that parses our log files? I cannot just line.split() because of Referrer having spaces. It's surrounded by quotes.04:33
claygzaitcev: oh no!  we should probably quote that before logging it.04:38
zaitcevtoo late for me though, I'm analyzing some logs from customer site04:39
zaitcevDate has a space too, and it's in square brackets. Consistency is not something we respect.04:39
claygzaitcev: do you know anything about keystone?  https://bugs.launchpad.net/swift/+bug/186368004:55
openstackLaunchpad bug 1863680 in OpenStack Object Storage (swift) "python3 swift-dispersion-report issue" [High,In progress] - Assigned to Sam Morrison (sorrison)04:55
zaitcevclayg: sorry, I don't know anything about it.04:57
zaitcevclayg: smorrison mentioned in the bug that Keystone must be on HTTPS: for this to reproduce.05:03
claygoh, good to know!  I bet the gate could reproduce it 🤔05:04
zaitcevAlso, I seriously doubt that the order of imports is what gets us. I suspect that the change from calling patcher.monkey_patch() with no arguments to the version in swift.common.utils is what does that. Heck, there's even a comment about it in the code.05:05
claygoh, the new comment - I thought I missed something05:05
claygis he online? sorrison ohai!05:05
zaitcevdunno... I typoed his nick with m anyway05:06
zaitcevIf you can reproduce, than you can try leaving patching in main().05:07
claygzaitcev: I think I could just move the swiftclient import under main (after existing patch) and it should work05:07
claygor maybe the "problem" is an import side-effect in swiftclient05:08
*** ccamacho has quit IRC05:17
*** evrardjp has quit IRC05:34
*** evrardjp has joined #openstack-swift05:34
openstackgerritClay Gerrard proposed openstack/swift master: Preserve query params in tempurl  https://review.opendev.org/33333106:41
claygso if we're interested in that change the next step would be a functest so we can enumerate the auth behaviors we care about06:43
*** tesseract has joined #openstack-swift08:05
openstackgerritCharles Hsu proposed openstack/python-swiftclient master: Allow users to list containers/objects by size.  https://review.opendev.org/70807408:24
*** rpittau|afk is now known as rpittau08:26
*** ccamacho has joined #openstack-swift08:32
*** tesseract has quit IRC08:38
*** tesseract has joined #openstack-swift08:39
*** mikecmpbll has joined #openstack-swift08:55
*** tkajinam has quit IRC09:19
*** mvkr has joined #openstack-swift09:24
*** StevenK has quit IRC09:52
*** StevenK has joined #openstack-swift09:52
*** mikecmpbll has quit IRC09:54
*** mikecmpbll has joined #openstack-swift09:57
*** tesseract has quit IRC09:58
*** tesseract has joined #openstack-swift10:11
*** rpittau is now known as rpittau|bbl11:20
*** ccamacho has quit IRC12:14
*** jvisser has joined #openstack-swift12:17
*** theintern_ has joined #openstack-swift12:20
*** jvisser has quit IRC12:26
*** jvisser has joined #openstack-swift12:27
*** jvisser has quit IRC12:47
*** jvisser has joined #openstack-swift12:49
*** psachin has quit IRC12:49
*** jvisser has quit IRC13:00
*** jvisser has joined #openstack-swift13:00
*** jvisser has quit IRC13:01
*** jvisser has joined #openstack-swift13:01
*** rpittau|bbl is now known as rpittau13:07
*** ccamacho has joined #openstack-swift13:17
viks___Hi,I'm checking the logs in SAIO and my local cluster and the swift proxy logs shows `HTTP/1.0` instead of `HTTP/1.1`. i.e. i get some message like the below:13:17
viks___```13:17
viks___Feb 20 14:26:28 saio proxy-server[2878]: 127.0.0.1 127.0.0.1 20/Feb/2020/14/26/28 GET /info HTTP/1.0 200 - curl/7.58.0 - - 1666 - txd554055608e247ebb1d30-005e4e9714 - 0.0009 - - 1582208788.357263088 1582208788.358170986 -13:17
viks___Feb 20 14:26:28 saio proxy-server[2878]: STDERR: 127.0.0.1 - - [20/Feb/2020 14:26:28] "GET /info HTTP/1.1" 200 1899 0.009609 (txn: txd554055608e247ebb1d30-005e4e9714)13:17
viks___Feb 20 14:27:00 saio proxy-server[2878]: STDERR: (2878) accepted ('127.0.0.1', 60684)13:17
viks___```13:17
viks___Why this happens? Is it normal?13:17
*** jvisser has quit IRC13:18
*** jvisser has joined #openstack-swift13:18
*** jvisser has quit IRC13:23
*** psachin has joined #openstack-swift13:37
*** jvisser has joined #openstack-swift14:00
*** diablo_rojo has joined #openstack-swift14:56
*** theintern_ has quit IRC15:06
*** psachin has quit IRC15:22
DHEwell the user agent is curl, so that was curl's decision. for a single request http 1.0 is fine16:11
*** gyee has joined #openstack-swift16:14
*** ccamacho has quit IRC16:32
*** rpittau is now known as rpittau|afk16:53
*** tesseract has quit IRC17:00
openstackgerritTim Burke proposed openstack/swift master: Preserve query params in tempurl  https://review.opendev.org/33333117:16
*** diablo_rojo has quit IRC17:22
*** evrardjp has quit IRC17:34
*** mikecmpbll has quit IRC17:34
*** evrardjp has joined #openstack-swift17:35
*** mikecmpbll has joined #openstack-swift18:04
claygtimburke: wow, I my brain was stuck on "I have a key to generate PUT tempurls" vs "I have been *given* a PUT tempurl"18:15
timburkeclayg, i wonder if we could bake a set of query params into the signature, so the signer would have to know what the tempurl could be used for... i'd be much more on-board with that18:16
claygthe prefix approach sounds interesting, but probably not when you want to create an SLO at "c/big.object" to segments like "c+segments/fooXX"?18:17
claygtimburke: it's still asking a lot of the application developer understand the security implication of "PUT tempurls for SLOs leak data"18:17
claygbut yeah - better than making a hole for ALL PUT tempurls!!!18:18
timburke...maybe? i need to refresh my memory about how much of a prefix you need, and where it starts18:18
claygI almost think it'd be better to put the tempurl sig IN the manifest - just intermingle it all up18:18
claygso generally speaking a PUT tempurl let's you create an object - but unless you have a valid PUT/HEAD sig for the segments you're not going to be able to create your SLO18:19
claygit's alot more coupled that way tho 😬18:19
timburkeoh jeeze 🤮18:19
claygyeah if you can make a prefix of 'foo' that enables PUT/HEAD into all both 'foobar' and 'foobaz' containers that might reasonable for some SLO/MPU workloads!18:20
claygtimburke: also kudos for the pointer to p 65949918:20
patchbothttps://review.opendev.org/#/c/659499/ - swift - WIP: Functests that stress tempurl xlo PUTs - 1 patch set18:20
claygif we can successfully pick a direction I think functests are going to be instrumental to understanding/validating the authorization behaviors we want.18:21
timburke18:25
*** mvkr has quit IRC19:01
claygtimburke: tdasilva: do either of you have the vsaio zipkin support enabled in your vsaio to test -> https://github.com/swiftstack/vagrant-swift-all-in-one/pull/9319:51
clayg^ or kota_ rledisez mattoliverau if you want to see what the distributed tracing with zipkin hubub is all about19:52
*** mikecmpbll has quit IRC20:08
rledisezclayg: can't wait to play with it, it looks interesting (I still need to read that PDF you link yesterday)20:10
timburkeclayg, my vsaio's in a bad state right now, won't come up. stupid https://github.com/aws/aws-cli/issues/482820:12
claygtimburke: oh yeah I hit that when I switched to py3 i think20:12
timburkei'm trying to get to a state that i can repro https://bugs.launchpad.net/swift/+bug/1863680 -- i'm like 99% sure it's not keystone specific and you'd be able to repro w/ https://github.com/swiftstack/vagrant-swift-all-in-one/pull/90/20:14
openstackLaunchpad bug 1863680 in OpenStack Object Storage (swift) "python3 swift-dispersion-report issue" [High,In progress] - Assigned to Sam Morrison (sorrison)20:14
timburkei know i hit similar issues in https://review.opendev.org/#/c/675227/ and https://review.opendev.org/#/c/705579/20:17
patchbotpatch 675227 - swift - py3: Finish porting func tests (MERGED) - 4 patch sets20:17
patchbotpatch 705579 - swift - probe tests: Work when fronted by a TLS terminator - 2 patch sets20:17
timburkehmm... maybe i'm misattributing my error; i guess the real trouble is that (1) something got python3-yaml installed via system packages, providing pyyaml 3.12, and (2) something *else* wants to upgrade that, but pip can't uninstall the system package20:32
*** jvisser has quit IRC20:53
*** jvisser has joined #openstack-swift21:25
claygtimburke: oh it'd be great if the difference was SSL and not keystone!21:28
claygit looks like I'm due for another look @ https://github.com/swiftstack/vagrant-swift-all-in-one/pull/90/ - do you think it's ready to go, or do you have more local changes?21:28
timburkei think it's gtg -- you might be happier if you got https://review.opendev.org/#/c/705579/ (i know *i* am)21:29
patchbotpatch 705579 - swift - probe tests: Work when fronted by a TLS terminator - 2 patch sets21:29
claygawesome!  that looks like a fun rabbit hole 🤣21:30
timburkeit wasn't near as bad as i'd feared -- tho that monkey-patching should maybe only apply to socket21:31
timburkeclayg, sure enough, can repro w/ vsaio+tempauth+TLS21:48
timburkeand i apparently need to template out /etc/swift/dispersion.conf :-/21:48
claygawesome!  are you groking what I was getting at on moving the imports around so we don't monkey patch as a side-effect of importing?  Can you try and validate a different change that fixes the issue?21:49
claygtimburke: ugh yeah, i hate it when i have to move chef file to a template 😡21:50
claygI'm not sure if it's annoying because of something inherent in chef's design or I did something wrong when I setup the project layout 🤔21:51
timburkei almost got good at it as part of that PR ;-)21:51
timburkeok, clayg: which do you dislike more? imports with side-effects, or delayed imports?21:59
claygPort with side effect categorically worse.22:05
mattoliveraumorning22:07
mattoliverauclayg: ooohh nice! Me do wanna play with that hubub :)22:07
*** jvisser has quit IRC22:22
*** tkajinam has joined #openstack-swift22:58
openstackgerritTim Burke proposed openstack/swift master: Delay importing swiftclient until after monkey-patching  https://review.opendev.org/70827423:02

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