Monday, 2018-05-07

*** NM has quit IRC00:14
*** links has joined #openstack-swift02:17
kota_hello02:30
kota_oic02:32
kota_i wonder why the patch 566421 can modify swift golang code at the master but i noticed that depends on the patch 560480 adding golang code for losf02:34
patchbothttps://review.openstack.org/#/c/566421/ - swift - Cleanups for LOSF RPC server02:34
patchbothttps://review.openstack.org/#/c/560480/ - swift - Initial LOSF RPC commit02:34
kota_that makes me sense.02:34
*** psachin has joined #openstack-swift02:42
*** mingyu has joined #openstack-swift03:28
*** mingyu has quit IRC03:48
*** cshastri has joined #openstack-swift03:57
*** threestrands has joined #openstack-swift04:04
*** gyankum has joined #openstack-swift04:10
*** SkyRocknRoll has joined #openstack-swift04:37
*** SkyRocknRoll has quit IRC04:38
*** silor has joined #openstack-swift04:47
*** hoonetorg has quit IRC05:07
*** hoonetorg has joined #openstack-swift05:20
*** mingyu has joined #openstack-swift05:57
*** pcaruana has joined #openstack-swift06:02
*** geaaru has quit IRC06:06
*** armaan has quit IRC06:34
*** armaan has joined #openstack-swift06:35
*** armaan has quit IRC06:42
*** armaan has joined #openstack-swift06:43
*** armaan has quit IRC06:58
*** armaan has joined #openstack-swift06:58
*** hseipp has joined #openstack-swift07:16
*** thegrif has quit IRC07:23
*** silor has quit IRC07:28
*** silor has joined #openstack-swift07:34
*** threestrands has quit IRC07:39
*** ntt has quit IRC07:43
*** ntt has joined #openstack-swift07:45
*** geaaru has joined #openstack-swift08:03
*** timss- is now known as timss08:29
*** timss has quit IRC08:32
*** timss has joined #openstack-swift08:33
*** armaan has quit IRC09:38
*** armaan has joined #openstack-swift09:40
*** silor1 has joined #openstack-swift09:57
*** silor has quit IRC09:59
*** silor1 is now known as silor09:59
*** afazekas is now known as afazekas|pto09:59
kota_swift-cores: sorry, i couldn't manage my time to review at the deep-review, probably I will have that tomorrow.10:08
*** armaan has quit IRC10:45
*** armaan has joined #openstack-swift10:45
openstackgerritHajime Kondo proposed openstack/slogging master: First commit of devstack directory  https://review.openstack.org/56470810:54
*** guimaluf has quit IRC11:15
*** kei_yama has quit IRC12:01
*** hseipp has quit IRC12:02
*** NM has joined #openstack-swift12:30
*** cshastri has quit IRC12:46
*** vinsh has joined #openstack-swift12:57
*** psachin` has joined #openstack-swift13:04
*** links has quit IRC13:05
*** remix_tj has joined #openstack-swift13:06
remix_tjhello! I'm looking for some information on how to write a middleware for filtering some operations on some files. Where is  the most appropriate place to insert the middleware? Proxy Server?13:07
*** zigo_ has joined #openstack-swift13:07
remix_tjAnd the other question is: are operations swift.proxy.controllers.base.get_container_info and swift.proxy.controllers.base.get_object_info the best functions to get the metadata set on  a container and an object respectively?13:08
*** ktsuyuzaki has joined #openstack-swift13:09
*** ChanServ sets mode: +v ktsuyuzaki13:09
*** armaan has quit IRC13:09
*** armaan has joined #openstack-swift13:10
*** psachin has quit IRC13:11
*** openstackgerrit has quit IRC13:11
*** zigo has quit IRC13:11
*** kota_ has quit IRC13:11
*** vinsh has quit IRC13:12
acolesremix_tj: the proxy is appropriate for most middlewares, there's some docs here https://docs.openstack.org/swift/latest/development_middleware.html13:12
remix_tjyes, it's exactly where i was looking at.13:12
*** vinsh has joined #openstack-swift13:12
*** ktsuyuzaki has quit IRC13:13
acolesget_object_info does an object backend HEAD, so may or may not be useful depending on whether you need to fetch the object anyway, or if some other middleware gas already fetched info during the current request. get_container_info may return cached info (from memcache) or do a backend HEAD.13:15
acoless/gas/has/13:15
*** kota_ has joined #openstack-swift13:16
*** ChanServ sets mode: +v kota_13:16
remix_tji want to check if a given metadata is set on object and given the value to decide if an operation can be performed13:16
remix_tjif the metadata is not set on object, i want to lookup for "global setting" looking into container's metadata.13:18
remix_tjacoles: last stupid questions: if i try to access the data through S3api, can i invoke the middleware? how?13:20
acolesremix_tj: I was just looking for an example of how get_object_info is used but only see it in tests. should do the job though. be aware of the docstring re. internal info requests being pre-authed.13:20
acolesremix_tj: you mean invoke your own middleware?13:21
remix_tjyes13:21
acolesI'm not too familiar with the s3api but as far as I know it is compatible with other middlewares13:23
*** psachin` has quit IRC13:24
remix_tjacoles: maybe is enough to add my middleware in the pipeline after the s3api middleware?13:27
*** neonpastor has quit IRC13:27
acolesyes I'd guess it needs to be after (to the right of) in the pipeline13:27
remix_tjso i'm expected to have the s3 calls converted into swift calls?13:30
acolesinternally the proxy server only handles swift requests so that is what I'd expect to be handling to the right of s3api. there may be some nuances but you'd need to check with others - try asking later in US daytime or even later in Japan daytime.13:33
*** armaan has quit IRC13:34
*** NM has quit IRC13:34
*** armaan has joined #openstack-swift13:34
remix_tjacoles: i start to develop my middleware with only swift support and then, if is the case, i'll try to expand with s3 support13:35
*** NM has joined #openstack-swift13:36
*** NM has quit IRC13:40
*** gyankum has quit IRC14:05
*** Supun has joined #openstack-swift14:10
*** NM has joined #openstack-swift14:10
*** NM has quit IRC14:11
*** armaan has quit IRC14:16
*** armaan has joined #openstack-swift14:17
*** armaan has quit IRC14:20
*** armaan has joined #openstack-swift14:21
*** NM has joined #openstack-swift14:25
*** NM has quit IRC14:27
*** hseipp has joined #openstack-swift14:30
*** NM has joined #openstack-swift14:33
*** NM has joined #openstack-swift14:39
*** NM has quit IRC14:39
*** NM has joined #openstack-swift14:43
*** NM has joined #openstack-swift14:45
*** NM has quit IRC15:07
*** pcaruana has quit IRC15:09
*** Supun has quit IRC15:17
*** ukaynar has joined #openstack-swift15:28
*** Supun has joined #openstack-swift15:41
*** armaan has quit IRC15:49
*** gyee has joined #openstack-swift16:03
notmynamegood morning16:17
*** Supun has quit IRC16:21
*** openstackgerrit has joined #openstack-swift16:21
openstackgerritAlistair Coles proposed openstack/swift feature/deep-review: Add ShardRange class  https://review.openstack.org/56574316:21
openstackgerritAlistair Coles proposed openstack/swift feature/deep-review: Add support for sharding in ContainerBroker  https://review.openstack.org/56574416:21
openstackgerritAlistair Coles proposed openstack/swift feature/deep-review: Add shard range support to container server  https://review.openstack.org/56574516:21
openstackgerritAlistair Coles proposed openstack/swift feature/deep-review: Enable proxy to build listings from shards  https://review.openstack.org/56574616:21
openstackgerritAlistair Coles proposed openstack/swift feature/deep-review: Redirect object updates to shard containers  https://review.openstack.org/56574716:21
openstackgerritAlistair Coles proposed openstack/swift feature/deep-review: Add sharder daemon, manage_shard_ranges tool and probe tests  https://review.openstack.org/56574816:22
openstackgerritAlistair Coles proposed openstack/swift feature/deep-review: Add container sharding documentation  https://review.openstack.org/56574916:22
acoles^^ first round of revisions16:22
notmynameacoles: thanks!16:22
*** hseipp has quit IRC16:23
acolesThis is a better link for seeing the deep-review chain (excludes abandoned patches) https://review.openstack.org/#/q/branch:feature/deep-review+status:open16:25
*** NM has joined #openstack-swift16:52
*** cshastri has joined #openstack-swift17:07
*** silor has quit IRC17:21
*** ccamacho has quit IRC17:27
notmynameI've been thinking about who's around in the swift community and how we measure "sufficient" reviews on feature/deep-review17:49
notmynamewith the limited number of people we have, how do we get enough reviews on the feature branch, especially when considering who's been contributing code to it17:50
notmynamefor that matter, what is "enough reviews"?17:51
notmynamehere's what I've thought through17:51
notmynamea reviewer needs to answer a few questions: (1) do I understand the overall design and think it's a good way to solve the stated problem? (2) is the proposed code maintainable? is it tested? does it avoid obviously bad code smells? (3) is there a single area of the review chain you've looked at in more depth and you've done a full review on?17:53
notmynameI think that if we have that sort of mindset, it will allow us to make more progress than the mindset of "I must start at the beginning and go to the end and leave either a -1 or +2"17:53
notmynameand if we're all doing that, then collectively we've done reviews on the full proposed chain17:54
notmynameI think it's a lot to ask of everyone to load several years of work into your head and understand all of the nuance and give approval or not, all in the next 2 weeks17:55
notmynameinstead, look at the high level design and goals, look for code maintainability, look for obvious wrong things, and answer the question "is this code that solves problems for users and that I'm willing to maintain?"17:55
notmynamethe hard part, of course, is the interactions between different parts. acoles has done a great job breaking the feature into a patch chain of logical parts17:56
notmynamebut it's still a lot easier to look at a class or daemon and say it looks good without seeing the issues that arise from interactions with other parts of the system17:57
*** geaaru has quit IRC17:57
notmynamemattoliverau wrote a lot of the initial work, acoles wrote the largest part of the proposed patch, clayg and timburke made significant code contributions18:00
notmynameof the 8 patches in the chain, if I reviewed 1 and 6-8 and tdasilva reviewed 1-4 and kota_ reviewed 3-7 and mattoliverau reviewed 4, 6, and 8 and clayg review 1-2 and 5-7 and etc etc for everyone else, then we've got a way to make reasonable progress on reviewing a really big feature18:01
notmynamesorry for the big wall of text. I think I'm just about done :-)18:02
notmynamemostly, in summary, I don't want people to feel overwhelmed by the scope and therefore feel like they can't make any progress at all18:03
notmynameI want to know your thoughts on this, too. that's what I've been thinking18:05
*** Supun has joined #openstack-swift18:08
*** NM has quit IRC18:17
*** ukaynar has quit IRC18:18
*** mvenesio has joined #openstack-swift18:19
*** ukaynar has joined #openstack-swift18:20
mvenesioHi Guys, how are you,  is there any script to synchronize accounts between two swift clusters ( keystone based authenticated ) ?18:21
notmynametimur: ^^18:21
notmynamemvenesio: yes. there's a project at https://github.com/swiftstack/swift-s3-sync that can do exactly that18:23
notmyname(the name comes from the original scope of that project. it's expanded in scope since then, and will be renamed soon [this week, if I can get to it])18:24
mvenesioHi John, Thanks man18:25
mvenesionotmyname: i'll try it18:25
notmynamemvenesio: please feel free to ask questions in here about it. either of myself or timur18:25
mvenesionotmyname: i'll do it for sure, thanks again18:26
timurmvenesio: the keystone auth will require merging the keystone auth PR. It's not merged yet, as I haven't had time to do the final review of it18:28
notmynamehttps://github.com/swiftstack/swift-s3-sync/pull/2318:28
timurpatch: https://github.com/swiftstack/swift-s3-sync/pull/1618:28
notmynamethanks timur :-)18:28
mvenesiotimur: great, i'll need that18:28
timuryea, we should merge one of those -- we were going back and forth on formatting, hence the two PRs. I think it may need to be rebased and merge conflicts fixed up :\18:29
mvenesiotimur: when do you think could be merged ?18:32
*** Supun has quit IRC18:37
notmynamemvenesio: it might be tricky to get it merged this week.18:39
mvenesionotmyname: ok not problem18:40
*** ukaynar has quit IRC18:40
notmynamemvenesio: what is it you're trying to do? wht's the overall goal/problem?18:40
mvenesionotmyname: basically we have a client with a swift redhat cluster installed, and we recently installed a brand new cluster , and we have to migrate all the data since the old one is getting out of space.18:42
mvenesionotmyname: both uses keystone to authenticate18:42
notmynameare you moving away from the redhat cluster? is there a reason you can't add capacity to the existing cluster?18:42
mvenesionotmyname: i think its something about pricing18:43
mvenesionotmyname: and support18:43
notmynameok. I wanted to make sure you weren't under the impression that swift clusters had a static size and couldn't be expanded :-)18:44
mvenesionotmyname: no, this isn't that case, but thanks for asking18:46
*** cshastri has quit IRC18:49
*** Supun has joined #openstack-swift18:58
*** ukaynar has joined #openstack-swift19:03
*** Supun has quit IRC19:08
*** ukaynar has quit IRC19:28
*** NM has joined #openstack-swift19:29
*** ukaynar_ has joined #openstack-swift19:35
*** NM has quit IRC19:39
*** NM has joined #openstack-swift19:43
*** ukaynar_ has quit IRC20:06
*** ukaynar has joined #openstack-swift20:10
*** mvenesio has quit IRC20:38
*** mvenesio has joined #openstack-swift20:39
*** geaaru has joined #openstack-swift20:40
*** lxkong_ has joined #openstack-swift20:45
notmynamelatest eventlet, 0.23.0 release yesterday, breaks swift. https://bugs.launchpad.net/swift/+bug/176974920:46
openstackLaunchpad bug 1769749 in OpenStack Object Storage (swift) "eventlet 0.23.0 breaks swift's unicode handling" [Undecided,New]20:46
notmynamenote that the gate is currently capped at 0.20.020:46
*** szaher_ has joined #openstack-swift20:48
*** mvenesio has quit IRC20:53
*** lxkong has quit IRC20:53
*** mvk has quit IRC20:53
*** zaitcev has quit IRC20:53
*** szaher has quit IRC20:53
*** lxkong_ is now known as lxkong20:53
*** mvk has joined #openstack-swift20:54
*** kota_ has quit IRC20:55
*** kota_ has joined #openstack-swift20:58
*** ChanServ sets mode: +v kota_20:58
*** NM has quit IRC21:30
*** gholt has joined #openstack-swift21:43
gholtAnybody noticed any oddities recently with Unicode decoding? We're getting this in our Travis builds today. https://pastebin.com/gxrNwPxP21:47
gholtI figure it's some weird combo of a bad library version or Python version or something. But I figured I'd ping you guys in case it was "known" before I spent a bunch of time trying to figure it out. :)21:48
gholtThat trace is from the proxy processing a request from the test: test_dlo_post_with_manifest_header (test.functional.test_dlo.TestDloUTF8)21:51
gholtBut it has a similar issue with a lot of tests today.21:51
gholtIn case the URL matters, it was ResponseError: 500: 'Internal Error' ('PUT' '/v1/AUTH_test/794551b2041240ba94db630bb0df022d/%E0%A4%82%EB%8C%8B%E0%A4%83%E8%94%88%ED%88%90%EB%8C%8D%E1%A0%83%EB%8C%8B%E1%A0%82%E0%A4%83%E0%A4%80%ED%88%8E%EF%84%91%E9%90%89%E0%A4%80') txid=tx01f5b124a6f34273a717a-005af0c5c321:52
notmynamegholt: we just found out last night's eventlet broke some unicode stuff22:00
notmyname0.23.022:00
notmynamehttps://bugs.launchpad.net/swift/+bug/176974922:00
gholtAh okay!22:00
openstackLaunchpad bug 1769749 in OpenStack Object Storage (swift) "eventlet 0.23.0 breaks swift's unicode handling" [Undecided,Confirmed]22:00
notmynameopenstack gate is pinned at 0.20.0 currently, so haven't seen issues there22:01
gholtI'm happy I asked then!22:01
gholtI'll check into that for us.22:01
gholtShould the requirements.txt be updated?22:05
notmynameyes, but no not yet22:06
gholtOkay, I'll try a sed -i for our Travis builds22:07
claygwell, you know how it is - everyone is constantly trying to figure out the most efficient way to maintain requirements.txt over the years.  pinning works as long as you update it, looser restrictions work as long to keep you apprised of problematic releases.22:07
notmynameit may be that there's a relatively simple fix for it. someone here suggested perhaps an update to swob may fix it. but I don't know yet22:08
*** ukaynar has quit IRC22:08
claygin the case of eventlet OpenStack has this storied history of having to blacklist eventlet releases - but I think we all finally agreed to work with temoto and try to make OpenStack and eventlet releases cohabitate more - i'm not sure what broke down this time exactly.22:09
gholtHehe, np.22:10
gholtI'm just really glad I asked because who knows how long I'd have spun my wheels researching areas I simply do not know anymore. :)22:10
clayggo team!22:10
*** ukaynar has joined #openstack-swift22:11
gholtIt's funny that at conferences Swift is still my only claim to fame. ;^) And then I get asked all sorts of questions I can't answer anymore.22:12
gholtDangit, == versus =. Time to wait for Travis again.22:15
*** ukaynar has quit IRC22:15
clayg🤣 You're very famous gholt, the kids all ask me if I really knew THE gholt 😉22:17
notmyname50 years from now, an old man sits in a rocking chair. sunlight coming in through the windows. The peacefulness of the afternoon is suddenly broken as 5 small children rush in, shouting. "Grandpa Clay! Grandpa Clay! Tell us the stories of the olden times. The before times. Did you really know gholt? THE gholt?!"22:19
clayg☝️22:20
claygOf course they know I knew notmyname - EVERYONE knows notmyname22:20
notmyname"We don't talk of that subject"22:21
gholtnot.mn22:21
gholtYay, green builds!22:22
gholtty guys22:22
notmynamegholt: \o/22:23
*** rcernin has joined #openstack-swift22:25
openstackgerritGage Hugo proposed openstack/python-swiftclient master: WIP - Migrate to using keystoneauth session  https://review.openstack.org/56013822:34
*** klamath_ has joined #openstack-swift22:49
*** klamath has quit IRC22:49
-openstackstatus- NOTICE: Any devstack job failure due to rsync errors related to tripleo-incubator can safely be rechecked now22:58
openstackgerritMerged openstack/slogging master: First commit of devstack directory  https://review.openstack.org/56470822:58
mattoliveraumorning23:08
*** kei_yama has joined #openstack-swift23:14
*** geaaru has quit IRC23:18
*** cloudnull is now known as cloudkiller23:20
*** cloudkiller is now known as cloudnull23:21
openstackgerritClay Gerrard proposed openstack/swift feature/deep-review: Add config option shard_replication_quorum  https://review.openstack.org/56636223:51
openstackgerritKeiichi Hikita proposed openstack/slogging master: This commit remove dead link in Readme  https://review.openstack.org/56676223:55
openstackgerritClay Gerrard proposed openstack/swift feature/deep-review: Add config option shard_replication_quorum  https://review.openstack.org/56636223:56

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