Thursday, 2019-01-31

zaitcevI don't know about you guys, but suddenly tox started throwing errors in s3api unit tests00:06
zaitcevFAIL: test_object_multipart_upload_complete_failure_with_heartbeat (test.unit.co00:06
zaitcevmmon.middleware.s3api.test_multi_upload.TestS3ApiMultiUpload)00:06
zaitcevAssertionError: '<Error><Code>InvalidRequest</Code><Message>some/object: 403 Forbidden</Message><Status>400 Bad Request</Status></Error>' is not false00:06
zaitcevHow did we stuff that through the gate, I wonder.00:06
timburkesome trouble with the time mocking in the test? i've not seen that failure, but it sounds kind of familiar...00:10
timburkewe *do* expect there to be a 403 Forbidden error... we just want some whitespace *first* :-/00:12
*** gyee has quit IRC01:33
*** mikecmpbll has quit IRC01:39
*** psachin has joined #openstack-swift03:01
*** openstackgerrit has joined #openstack-swift03:02
openstackgerritPete Zaitcev proposed openstack/swift master: py3: port the container sharder  https://review.openstack.org/57032003:02
*** gkadam-bmgr has joined #openstack-swift03:34
*** e0ne has joined #openstack-swift06:12
*** e0ne has quit IRC07:05
*** ccamacho has joined #openstack-swift07:15
*** takamatsu has joined #openstack-swift07:46
*** tkajinam has quit IRC08:14
*** mikecmpbll has joined #openstack-swift09:06
*** e0ne has joined #openstack-swift09:15
*** psachin has quit IRC09:40
*** jistr is now known as jistr|chat10:31
*** e0ne has quit IRC10:46
*** e0ne has joined #openstack-swift10:52
*** jistr|chat is now known as jistr11:05
*** e0ne has quit IRC11:24
*** mrjk_ has quit IRC11:33
*** e0ne has joined #openstack-swift11:34
*** mrjk has joined #openstack-swift11:35
*** nguyenhai has quit IRC11:56
*** nguyenhai has joined #openstack-swift11:56
*** nguyenhai has quit IRC12:00
*** nguyenhai has joined #openstack-swift12:00
*** ybunker has joined #openstack-swift12:01
*** ybunker has quit IRC12:14
*** e0ne has quit IRC13:01
*** e0ne has joined #openstack-swift13:04
tdasilvarledisez: https://github.com/benfred/py-spy13:04
*** gkadam-bmgr is now known as gkadam13:15
*** gkadam has quit IRC13:20
*** e0ne has quit IRC13:25
*** jistr is now known as jistr|call13:25
*** ybunker has joined #openstack-swift13:28
ybunkerI inherit the following configuration for the object-expirer.conf file (http://pasted.co/b1e486ad)13:29
*** e0ne has joined #openstack-swift13:29
ybunkerand its only running on one of the proxy nodes (account and containers) are running on the data nodes13:29
*** e0ne has quit IRC13:30
*** jistr|call is now known as jistr13:31
*** e0ne has joined #openstack-swift13:32
ybunkeris this correct? or it should be configured on the data nodes? and on each of the nodes?, also each node has 9 data disks for objects and 3 disks for account/container13:33
ybunkershould i configure processes option too, right?13:33
*** e0ne has quit IRC13:34
*** e0ne has joined #openstack-swift13:35
*** hseipp has joined #openstack-swift13:48
DHEhttps://docs.openstack.org/swift/latest/overview_expiring_objects.html "Usually, just one instance of the swift-object-expirer daemon needs to run for a cluster"13:52
*** pcaruana has quit IRC13:52
DHEyou could run it anywhere, doesn't really matter as long as it has the config and ring files it needs13:52
*** egallen has joined #openstack-swift13:53
*** takamatsu has quit IRC13:54
ybunkerDHE: oh excellent!, thanks a lot for the help, will leave it on the proxy, regarding the processes option parameter, if i would like to not burn the disks, should i use processes = 9?14:01
*** pcaruana has joined #openstack-swift14:02
tdasilvaybunker, DHE this is still probably early still and not 100% set in stone (since it hasn't merged) but one patch that is getting more attention are related to changes to the expirer which will require it to run on the object servers. just a heads up14:10
tdasilvahttps://review.openstack.org/#/c/601950/14:11
patchbotpatch 601950 - swift - Enable to configure object-expirer in object-serve... - 11 patch sets14:11
tdasilvahttps://review.openstack.org/#/c/517389/4014:11
patchbotpatch 517389 - swift - Add object-expirer new mode to execute tasks from ... - 40 patch sets14:11
ybunkertdasilva, thanks for the news :)14:12
*** e0ne has quit IRC14:13
kota_tdasilva: https://en.oui.sncf/en/14:25
kota_maybe14:25
tdasilvakota_: thanks!14:25
*** e0ne has joined #openstack-swift14:45
*** egallen has left #openstack-swift14:59
*** mvkr has quit IRC15:00
*** mvkr has joined #openstack-swift15:13
tdasilvarledisez, alecuyer: not sure you have seen this before, but it's a good read: https://bugs.launchpad.net/swift/+bug/145065615:25
openstackLaunchpad bug 1450656 in OpenStack Object Storage (swift) "tmp directory causing Swift slowdown" [Undecided,Fix released] - Assigned to Shri Javadekar (shrinand)15:25
kota_ok, it seems that I succeeded to build the https://github.com/alecuyer/swift/tree/master-losf environment in my saio vm, by hand.15:30
DHEinteresting...15:33
DHEmy upcoming swift cluster is going to make EXTENSIVE use of object expiration...15:34
kota_what's up DHE?15:35
DHEwaiting for the budget for said cluster to come through... supposed to be this quarter15:36
kota_alecuyer: probably we should write down protobuf-compiler>=3 to support proto3 at https://github.com/alecuyer/swift/blob/master-losf/go/swift-rpc-losf/README.md15:37
kota_even tho, we might have compiled protocol buffer files.15:38
kota_interesting15:39
* kota_ is rolling back the logs15:39
*** ccamacho has quit IRC15:41
openstackgerritThiago da Silva proposed openstack/swift master: Change how O_TMPFILE support is detected  https://review.openstack.org/63364615:50
*** ccamacho has joined #openstack-swift15:50
kota_ok, swift functional tests worked w/o 58 skipped ones.15:57
kota_I'm still wondering how we could manage golang code in the python repo.16:19
kota_A. maintain at the same repo and make a doc how to build/install the go code, or B. separate golang code to another repo like liberasurecode.16:20
kota_either of those has pros/cons tho.16:20
kota_tdasilva: perhaps, sort of what pyeclib is doing could be useful? likely, https://github.com/openstack/pyeclib/blob/master/setup.py#L78-L11416:33
kota_extend the python setup to build other language modules.16:34
*** edausq has joined #openstack-swift16:34
* kota_ is not sure if current Swift can follow the way tho.16:35
*** e0ne has quit IRC16:46
*** spsurya has quit IRC16:54
kota_or perhaps, creating Makefile like as ProxyFS is doing?17:07
kota_would be easy to install?17:07
*** ccamacho has quit IRC17:13
*** takamatsu has joined #openstack-swift17:14
*** gyee has joined #openstack-swift17:19
*** hseipp has quit IRC17:26
*** mikecmpbll has quit IRC17:37
*** ccamacho has joined #openstack-swift17:53
timburkekota_: i'd vote A, assuming the amount of work to get to either is comparable18:15
claygI like the Open Infrastructure initiative/direction for the foundation - I still don't know what starlingx or airship or kata are building - but it seems like they're trying to do it in a way that doesn't reinvent the parts of open project development that aren't broken 👍18:15
claygtimburke: having pyeclib and libec be separate repos was wrong in hindsight IMHO - but I think not having them in swift was good.  Not sure if there's anything to learn there.18:17
timburkeclayg: yeah, i think i agree on both those points. the lesson to learn is probably, "if these components are expected to release and upgrade together in lockstep, put them in the same repo"18:18
openstackgerritTim Burke proposed openstack/swift master: Change how O_TMPFILE support is detected  https://review.openstack.org/63364618:35
*** mvkr has quit IRC18:35
*** e0ne has joined #openstack-swift18:39
*** e0ne has quit IRC18:48
openstackgerritTim Burke proposed openstack/swift master: Fix socket leak on object-server death  https://review.openstack.org/57525419:07
openstackgerritCyril Roelandt proposed openstack/swift master: Python3: fix test/unit/obj/test_replicator.py  https://review.openstack.org/63364519:13
*** pcaruana has quit IRC19:30
*** ybunker has quit IRC19:36
*** mikecmpbll has joined #openstack-swift20:29
openstackgerritTim Burke proposed openstack/swift master: Python3: fix test/unit/obj/test_replicator.py  https://review.openstack.org/63364520:33
openstackgerritTim Burke proposed openstack/swift master: py3: proxy some logger properties in LogAdapter  https://review.openstack.org/63430420:33
timburkezaitcev: idk -- the py36 job made it seem like there might've just been the two left...20:40
timburkeas much as anything, i wanted to see whether the CPython LoggerAdapter backports would fix up the py35 job to look more like the py36 one20:41
zaitcevYeah, fascinating.20:41
timburkei wonder who i ought to be poking to get https://github.com/python/cpython/pull/7932 landed...20:43
timburkeso far so good on p 633645 ... py35 passed, py27 is running, and py36 is queued20:48
patchbothttps://review.openstack.org/#/c/633645/ - swift - Python3: fix test/unit/obj/test_replicator.py - 3 patch sets20:48
openstackgerritTim Burke proposed openstack/swift master: Address some review comments  https://review.openstack.org/62757420:56
openstackgerritTim Burke proposed openstack/swift master: s3api: fix up flakey LastModified assertions  https://review.openstack.org/63431821:36
openstackgerritTim Burke proposed openstack/swift master: docs: clean up Object Versioning page  https://review.openstack.org/63432021:55
mattoliveraumorning22:02
zaitcevGeh22:06
zaitcevfloating failures22:06
zaitcevmattoliverau: did you see https://review.openstack.org/570320 ? It's holding up progress in container.22:07
patchbotpatch 570320 - swift - py3: port the container sharder - 13 patch sets22:07
zaitcevmattoliverau: we had some item there which was not entirely clear, like is it possible to have _own_ shard range that had other shard ranges instead of bonds?22:08
*** ccamacho has quit IRC22:10
timburkei was a little surprised by this failure: http://logs.openstack.org/54/575254/6/check/swift-probetests-centos-7/e8b151e/job-output.txt.gz#_2019-01-31_21_52_10_56494322:12
timburkebut then i saw https://github.com/openstack/swift/blob/2.20.0/swift/proxy/controllers/container.py#L277-L278 ... should that be HTTPServiceUnavailable instead?22:12
mattoliverauzaitcev: I started looking last night, but ran out of steam (lack of sleep due to 2 little monsters). I'll continue this morning after my morning stand up :)22:13
*** tkajinam has joined #openstack-swift22:56
openstackgerritTim Burke proposed openstack/swift master: sharding: Make replicator logging less scary  https://review.openstack.org/63434223:22
timburketdasilva: fwiw, that most-recent lower-constraints failure on p 633646 shouldn't be an issue after p 63431823:27
patchbothttps://review.openstack.org/#/c/633646/ - swift - Change how O_TMPFILE support is detected - 5 patch sets23:27
patchbothttps://review.openstack.org/#/c/634318/ - swift - s3api: fix up flakey LastModified assertions - 1 patch set23:28
openstackgerritTim Burke proposed openstack/swift master: Allow "harder" symlinks  https://review.openstack.org/63309423:48

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