Monday, 2018-12-10

*** itlinux has quit IRC02:29
*** psachin has joined #openstack-swift02:59
*** rcernin has quit IRC07:23
*** gkadam has joined #openstack-swift07:52
*** ccamacho has joined #openstack-swift07:55
*** openstackgerrit has joined #openstack-swift09:38
openstackgerritmelissaml proposed openstack/swift master: fix a typo in docstring  https://review.openstack.org/62403409:38
*** e0ne has joined #openstack-swift10:03
*** e0ne has quit IRC10:30
*** e0ne has joined #openstack-swift10:36
*** e0ne has quit IRC11:58
*** e0ne has joined #openstack-swift12:00
*** e0ne has quit IRC12:00
*** mahatic has joined #openstack-swift12:01
*** ChanServ sets mode: +v mahatic12:01
*** NM has joined #openstack-swift12:11
*** jistr is now known as jistr|medchk12:57
*** psachin has quit IRC13:05
*** jistr|medchk is now known as jistr13:56
*** e0ne has joined #openstack-swift14:15
*** openstackstatus has joined #openstack-swift14:18
*** ChanServ sets mode: +v openstackstatus14:18
*** gkadam has quit IRC14:24
*** mvkr has quit IRC14:55
*** mvkr has joined #openstack-swift15:25
*** itlinux has joined #openstack-swift15:44
*** itlinux has quit IRC15:46
*** NM has quit IRC16:12
*** openstackgerrit has quit IRC16:35
*** psachin has joined #openstack-swift16:42
*** gyee has joined #openstack-swift16:47
*** ccamacho has quit IRC16:52
*** itlinux has joined #openstack-swift16:56
notmynamegood morning17:06
*** openstackgerrit has joined #openstack-swift17:19
openstackgerritTim Burke proposed openstack/swift master: s3api: Stop mangling Authorization header for v4 signatures  https://review.openstack.org/59186217:19
*** e0ne has quit IRC17:22
*** e0ne has joined #openstack-swift17:23
*** e0ne has quit IRC17:23
*** e0ne has joined #openstack-swift17:26
notmynamehooray! all the s3api patches have landed!17:26
timburkeyup! i'm excited :-)17:26
timburkeif you wanted to get a couple more small ones in, though, there's https://review.openstack.org/#/c/621055/ and https://review.openstack.org/#/c/617043/17:27
patchbotpatch 621055 - swift - s3api: Look for more indications of aws-chunked up... - 3 patch sets17:27
patchbotpatch 617043 - swift - s3token: Add an underscore to the end of reseller_... - 1 patch set17:27
timburkeor https://review.openstack.org/#/c/591862/ or https://review.openstack.org/#/c/609168/ ...17:29
patchbotpatch 591862 - swift - s3api: Stop mangling Authorization header for v4 s... - 6 patch sets17:29
patchbotpatch 609168 - swift - We don't have to keep the retrieved token anymore - 2 patch sets17:29
timburkei'm hoping to get https://review.openstack.org/#/c/603529/ reviewed today...17:29
patchbotpatch 603529 - swift - s3 secret caching - 10 patch sets17:29
timburkenotmyname: i guess what i'm trying to say is, i can always find you more patches to approve :P17:29
notmynamelol, I got distracted in the office and couldn't type "but timburke will tell me there's a bunch more ready to land" ;-)17:29
*** e0ne has quit IRC18:09
*** e0ne has joined #openstack-swift18:11
*** psachin has quit IRC18:23
cwrightHi, we have a vendor who is trying to integrate with our S3 compatible Swift cluster (pike/2.15.1).18:31
cwrightThe vendor has working integrations with many other S3 compatible object stores, but their integration tests are failing against our cluster.18:31
cwrightOur logs show `BadSwiftRequest: Metadata value longer than 256: x-object-meta-X-Amz-Key`, and I can see in the request that the value is a base64 encoded value that is 345 bytes.18:31
cwrightDigging through the Swift source code I've found that it defaults to a limit of 256 bytes, but seems to be configurable via `max_meta_value_length` in `[swift-constraints]`.18:31
cwrightFor comparison, the Amazon S3 documentation states "User-defined metadata can be as large as 2 KB".18:31
cwrightI'd like to understand the implications of raising this limit. Has anyone else here needed to raise `max_meta_value_length`?18:31
cwrightOr can anyone explain what I may need to consider if I raise this to 2 KB?18:31
notmynameraising it is fine. also look out for the overall max metadata length to see if you need to raise that18:31
notmynamethere's a config value for the max single key size and the overall total size18:32
notmynameultimately, more metadata will end up using more overhead in the xfs file system. that's really the "risk"18:32
notmynamewell, also the metadata size is *not* part of the overall reported bytes used for the account18:33
notmynamebut if you're aware of those issues as the operator, you can take appropriate steps18:33
notmynameeg more ram and potentially on-disk bytes (or just more memory monitoring) for the higher inode usage.18:34
*** e0ne has joined #openstack-swift18:34
cwrightnotmyname: thanks so much.  Would you recommend I raise the `max_meta_overall_size` setting by the same amount I raise `max_meta_value_length`?18:35
notmynameit's totally possible to build a fuse filesystem on top of swift where you use zero-byte objects and just store the data in the object metadata fields. it would be horribly slow and terrible for the ops running the cluster, but the customer wouldn't have any bytes used reported and could therefore have it for "free"18:35
timburkecwright: fwiw, the clusters i deploy go with swift_max_meta_name_length=2048, swift_max_meta_value_length=2048, swift_max_meta_overall_size=4096 by default18:35
notmynamethat's one of the reasons we originally implemented the limits ;-)18:35
cwrighttimburke: that is very helpful, thanks so much18:35
notmynamecwright: no, they don't need to be the same. it's really just a knob to influence how customers organize the data. do you want them to use many metadata keys? or just one big one?18:36
notmynameTBH, I have no idea why you'd want them to do one over the other. but you have the knobs in the system18:36
notmynamecwright: oh! how's the promethius stuff working out?18:36
cwrightnotmyname: this is the only issue related to metadata length we've had so far, so we aren't exactly sure how many metadata keys they will need to use. This one in particular is important for their client side encryption integrations18:37
cwrightnotmyname: I forked the prometheus exporter project to begin updating the paths in the code and systemd configs but got slowed down trying to figure out how to build the project.  I know beggars can't be choosers but just some simple build docs would be tremendously helpful :)18:38
notmynamecwright: that's fair. I'll pass it along18:39
cwright(I don't have any experience with Go yet)18:39
cwrightnotmyname: that would be great, thanks again, I really appreciate it18:41
timburke"client side encryption integrations" <-- yes! that's right, i'm pretty sure that was a motivating factor for why *we* increased it, too ;-)18:43
cwrighttimburke: that makes me feel even better :)18:44
openstackgerritTim Burke proposed openstack/swift master: Treat all invalid frag indexes the same  https://review.openstack.org/61599018:48
*** e0ne has quit IRC19:06
*** mvkr has quit IRC19:09
openstackgerritMerged openstack/swift master: fix a typo in docstring  https://review.openstack.org/62403420:10
*** mvkr has joined #openstack-swift20:16
*** e0ne has joined #openstack-swift20:28
*** e0ne has quit IRC20:28
openstackgerritMerged openstack/swift master: Py3: Use BytesIO when we want bytes  https://review.openstack.org/62137722:07
*** itlinux has quit IRC22:43
*** rcernin has joined #openstack-swift22:59
*** itlinux has joined #openstack-swift23:48

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