Wednesday, 2019-09-18

*** zaitcev has quit IRC00:03
*** UnfairFunction has joined #openstack-swift00:32
*** gyee has quit IRC00:50
*** BjoernT has joined #openstack-swift02:26
*** baojg has quit IRC02:45
*** baojg has joined #openstack-swift02:45
*** baojg has quit IRC02:53
*** idlemind has quit IRC02:54
*** BjoernT has quit IRC03:01
*** BjoernT has joined #openstack-swift03:02
*** pcaruana has joined #openstack-swift04:46
*** UnfairFunction has joined #openstack-swift04:46
*** BjoernT has quit IRC04:48
*** e0ne has joined #openstack-swift05:14
*** e0ne has quit IRC05:14
*** e0ne has joined #openstack-swift05:16
*** UnfairFunction has quit IRC05:30
*** e0ne has quit IRC05:50
*** e0ne has joined #openstack-swift06:21
*** e0ne has quit IRC06:26
*** rcernin has quit IRC06:57
openstackgerritMatthew Oliver proposed openstack/swift master: Sharding: Clean up old CleaveConext's during audit  https://review.opendev.org/68197007:11
*** e0ne has joined #openstack-swift07:57
*** tkajinam has quit IRC08:04
*** pcaruana has quit IRC08:57
*** pcaruana has joined #openstack-swift09:01
*** tesseract has joined #openstack-swift09:44
*** openstackgerrit has quit IRC10:06
*** pcaruana has quit IRC11:19
*** e0ne_ has joined #openstack-swift11:20
*** e0ne has quit IRC11:23
*** psachin has joined #openstack-swift11:25
*** pcaruana has joined #openstack-swift11:28
*** redrobot has joined #openstack-swift12:26
*** NM has joined #openstack-swift12:32
*** psachin has quit IRC13:33
*** BjoernT has joined #openstack-swift13:48
NMHi timburke. As a workarround for the "too many headers" error (https://bugs.launchpad.net/swift/+bug/1843313) , I changed the max_meta_count (https://github.com/openstack/swift/blob/master/etc/swift.conf-sample#L132)  so I could list the container and use de primaries nodes.14:38
openstackLaunchpad bug 1843313 in OpenStack Object Storage (swift) "Sharding handoffs creates a *ton* of container-server headers" [Undecided,New]14:38
*** gkadam has joined #openstack-swift14:54
*** gkadam_ has joined #openstack-swift14:55
*** gkadam has quit IRC14:56
*** gkadam_ has quit IRC15:04
*** gyee has joined #openstack-swift15:08
*** theintern_ has joined #openstack-swift15:09
*** NM has quit IRC15:44
*** henriqueof has quit IRC16:02
*** ormandj has joined #openstack-swift16:19
ormandjheya folks, when using vhost naming (for s3 access) - how do public buckets work? i couldn't find docs on it. aws s3 handles this by requiring globally unique bucket names16:20
ormandji ask since amazon is deprecating non-virtual style access in s3 in 202016:22
*** gmann is now known as gmann_afk16:23
ormandji'm guessing public access will be via the normal naming scheme only, not allowing virtual host style, but was just curious16:28
*** NM has joined #openstack-swift16:32
ormandj(in the sense that we'll only allow public access via the swift mechanisms)16:37
*** e0ne_ has quit IRC16:50
*** openstackgerrit has joined #openstack-swift16:51
openstackgerritTim Burke proposed openstack/swift master: proxy: Don't trust Content-Length for chunked transfers  https://review.opendev.org/68217316:51
*** tesseract has quit IRC16:53
claygtdasilva: does p 682668 make it so functests pass even when allow_versioned is disabled?  it gets auto inserted in the pipeline right - so I can't take it out?16:57
patchbothttps://review.opendev.org/#/c/682668/ - swift - Skip test when object versioning is not enabled - 1 patch set16:57
tdasilvaclayg: correct. You can't take versioned_writes out of the pipeline, but you can set the `allow_versioned_writes` to False. In that case a container PUT with a 'x-versions-location' will return a 41217:12
timburkeNM, that makes sense as a workaround, thanks for mentioning it. hopefully we can get mattoliverau's patch reviewed and landed soon so you can crank it back down ;-)17:13
tdasilvaclayg: we have that check on the other Test classes, it was just the SLO that was missing: https://github.com/openstack/swift/blob/master/test/functional/test_versioned_writes.py#L7317:14
timburkeormandj, fortunately, we don't have to follow AWS's deprecation policies ;-) *un*fortunately, we don't currently have a way to do anonymous bucket access, since we give each tenant their own bucket namespace17:15
ormandjyeah, that was my suspicion. unfortunately, everyone follows amazon s3 for compatibility, we already ran into an issue a few days back where synology requires virtualhost style support to use s3 api17:16
ormandjluckily we were able to support that17:16
timburketdasilva, will it? i thought the container server simply refused to store the meta...17:17
ormandjso i suspect when 2020 roles around and they disable non-vhost style access, you'll see more and more clients that rely on that behavior by default17:17
ormandjfor public access, not such a big deal luckily17:17
timburkeormandj, we *do* support virtualhost-style naming, though -- look for the storage_domain option: https://github.com/openstack/swift/blob/master/etc/proxy-server.conf-sample#L536-L53817:18
ormandjyeah, i've got it working now17:18
ormandjthat's what i meant when i said we were able to support that, apologies for lack of clarity :)17:19
timburke👍 glad to hear it's working for you17:19
ormandjyeah working well, synology was plug and play afterwards, just got lucky i saw the snippit in the sample config before i went digging through code :)17:20
tdasilvatimburke: https://github.com/openstack/swift/blob/master/swift/common/middleware/versioned_writes.py#L714,L71917:20
timburkethe DNS and wildcard certs make it a bit trickier to set up, of course :-(17:20
ormandjyeah, we had 'fun' with the cert issue, ended up having to define another acceptable domain, luckily we use letsencrypt and have automated cert pushes17:20
ormandjbut it did work17:21
timburketdasilva, oh cool, right -- i was thinking of the auto-inserted case17:21
claygtdasilva: 👍17:26
openstackgerritClay Gerrard proposed openstack/swift master: s3api: Implement object versioning API  https://review.opendev.org/68295317:27
clayg^ i didn't mean that push that up yet, mis-type 😢17:27
claygoh good, i was worried I'd pushed over p 673682 - but it's a fresh patch set17:28
patchbothttps://review.opendev.org/#/c/673682/ - swift - s3api: Implement versioning status API - 3 patch sets17:28
claygso no worries!17:29
NMHelo eeryone. Is it recommend to have a single memcache pool for swift or can I have one for each location? Let's say I have 3 proxies in San Franscisco and 3 in Miami. Is it ok to have two distinct pools for each region?17:37
*** theintern_ has quit IRC17:40
claygNM: distinct pool for each reason is very much a good idea!   there may be some implications for cached auth tokens tho - which auth are you using?17:47
*** e0ne has joined #openstack-swift17:48
*** e0ne has quit IRC17:49
*** theintern_ has joined #openstack-swift17:56
NMclayg: thanks! right now I'm using keystone. My main concern is about the container process using a distinct pool. Because proxies don't talk to each other. But containers does.18:00
claygYeah, but it's just a cache - if there's a miss whatever local process needs the info will just go to swift and get whatever it needs to know sticking it in the cache along the way18:00
openstackgerritMerged openstack/swift master: Add python3 to setup.cfg  https://review.opendev.org/66857818:01
*** e0ne has joined #openstack-swift18:01
clayga region aware cache system would be super hawt - but as it seperate pools work a treat18:01
claygno worries with keystone - a token cached in region A will still have to "go to auth" when a request is made to region B, but thankfully clients don't typically seem to jump back and forth18:02
*** SkyRocknRoll has joined #openstack-swift18:28
*** SkyRocknRoll has quit IRC18:28
*** NM has quit IRC18:32
*** NM has joined #openstack-swift18:33
*** SkyRocknRoll has joined #openstack-swift18:36
*** openstackgerrit has quit IRC18:37
*** SkyRocknRoll has quit IRC18:39
*** NM has quit IRC18:48
*** NM has joined #openstack-swift18:49
*** NM has quit IRC19:28
*** NM has joined #openstack-swift19:29
*** hoonetorg has quit IRC20:01
*** theintern_ has quit IRC20:08
*** pcaruana has quit IRC20:10
claygtdasilva: timburke: so it looks like we do the name check on all requests, not just PUT20:44
claygbut we could certainly change that - letting in null bytes for internal container names was fine20:44
*** openstackgerrit has joined #openstack-swift20:47
openstackgerritThiago da Silva proposed openstack/swift master: WIP: New Object Versioning mode  https://review.opendev.org/68238220:47
timburkemeeting time!21:01
openstackgerritMerged openstack/swift master: versioned_writes: checks for SLO object before copy  https://review.opendev.org/68165621:10
*** NM has quit IRC21:24
*** e0ne has quit IRC21:41
claygrledisez: what's the recommendation?21:59
claygis it like... don't bring anything and buy a phone/laptop when you get there?21:59
claygor maybe that's worse!?21:59
claygyeah I'm really curious21:59
kota_for shanghi?22:00
claygkota_: yeah are you bringing all your regular work equipment and personal phone with you?22:00
rledisezbascially, blank laptop, blank phone. stickers on both to recognise them, no connections to the office (no mail/vpn or whatever). returning the hardware to the helpdesk when coming home22:00
kota_AFAIK, if you bring roaming SIM, it's not so matter to access any internet service like google22:00
mattoliverausome people have been talking about a burner laptop. Ie. something that your happy nuking22:00
rledisezand to not forget that encryption is forbidden there22:00
kota_but if you bought the local SIM, you will be alone.22:00
claygrledisez: I can swing the "blank laptop" - i'll just grab one of my old ones and do a re-install22:01
claygrledisez: but where do I get a "blank phone"!?22:01
kota_clayg: oic.22:01
rledisezclayg: i mean we can't use our profesionnal phone, they are preconfigured with VPN and mails & co. it must be just a SIM card22:02
claygkota_: so you think bring my t-mobile phone number with me?  honestly I've used it all over the world and it's never let me down - i'd be nervous to be overseas without it!?22:02
kota_hmm... i don't think we need blank phones/laptops22:02
kota_but I'll try to ask someone more for preparation22:02
claygkota_: that would be much simpler!  I've never been concerned about traveling with a work laptop before22:03
claygkota_: rledisez: thank you guys for sharing what you know!22:03
timburkeoh! which hotels are people booking? if you're all congregating somewhere already... i ought to do that one, too :-)22:10
kota_timburke: in my memo, my hotel booking is to Courtyard Shanghai Pudong22:17
kota_and my quick survey, the roaming SIM seems to work, but the google map doesn't seem to be updated so the recommendation looks to install baidu map, https://apps.apple.com/jp/app/%E7%99%BE%E5%BA%A6%E5%9C%B0%E5%9B%BE-%E7%A7%91%E6%8A%80%E8%AE%A9%E5%87%BA%E8%A1%8C%E6%9B%B4%E7%AE%80%E5%8D%95/id452186370?ign-mpt=uo%3D422:19
*** tkajinam has joined #openstack-swift23:02
claygtimburke: I was gunna do Marriott23:14
*** rcernin has joined #openstack-swift23:16
*** BjoernT has quit IRC23:30

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