| *** itlinux_ has quit IRC | 00:13 | |
| *** mvkr has joined #openstack-swift | 00:14 | |
| *** itlinux has joined #openstack-swift | 00:18 | |
| timburke | zaitcev, fyi: we can move forward on ssync as long as we've got new enough eventlet: https://github.com/eventlet/eventlet/commit/4b0450b37c26d77cebf58d15f6c07525b5073b72 | 00:35 |
|---|---|---|
| timburke | also, i might be getting close to being able to run some func tests since eventlet landed https://github.com/eventlet/eventlet/commit/f0bc79e1d973806866e2eb74db82adfda64ab1e5 -- gotta use latin1 around https://github.com/python/cpython/blob/v3.7.2/Lib/http/client.py#L1106-L1107 though | 00:36 |
| *** itlinux has quit IRC | 00:44 | |
| *** itlinux has joined #openstack-swift | 01:09 | |
| *** itlinux has quit IRC | 01:11 | |
| *** itlinux has joined #openstack-swift | 01:12 | |
| *** itlinux has quit IRC | 01:18 | |
| *** itlinux has joined #openstack-swift | 01:19 | |
| *** henriqueof has quit IRC | 01:30 | |
| *** itlinux has quit IRC | 01:51 | |
| *** itlinux has joined #openstack-swift | 01:52 | |
| *** itlinux has quit IRC | 01:58 | |
| *** tkajinam has quit IRC | 02:02 | |
| *** tkajinam has joined #openstack-swift | 02:03 | |
| *** tkajinam_ has joined #openstack-swift | 02:05 | |
| *** tkajinam has quit IRC | 02:07 | |
| *** tkajinam_ has quit IRC | 02:10 | |
| *** tkajinam has joined #openstack-swift | 02:10 | |
| *** gyee has quit IRC | 02:42 | |
| *** psachin has joined #openstack-swift | 03:12 | |
| openstackgerrit | Merged openstack/swift master: py3: port object auditor https://review.openstack.org/639198 | 03:51 |
| zaitcev | Oh goodness gracious, at last | 05:03 |
| *** tingjie has joined #openstack-swift | 05:40 | |
| *** tingjie has left #openstack-swift | 05:40 | |
| *** tingjie has joined #openstack-swift | 05:41 | |
| *** tingjie has left #openstack-swift | 05:41 | |
| *** itlinux has joined #openstack-swift | 06:33 | |
| *** itlinux_ has joined #openstack-swift | 06:37 | |
| *** itlinux has quit IRC | 06:40 | |
| *** zaitcev has quit IRC | 07:23 | |
| *** e0ne has joined #openstack-swift | 07:28 | |
| *** itlinux_ has quit IRC | 07:37 | |
| *** gkadam has joined #openstack-swift | 07:37 | |
| *** itlinux has joined #openstack-swift | 07:39 | |
| *** itlinux has quit IRC | 07:55 | |
| *** tkajinam has quit IRC | 08:18 | |
| *** ccamacho has joined #openstack-swift | 08:19 | |
| *** mcape has joined #openstack-swift | 09:35 | |
| mcape | Hi guys! I just read swift upgrade notes from the Ocata - 2.11.0, till Rocky - 2.19.0. I have impression that I can upgrade code of swift directly from Ocata to Rocky passing intermediate versions. | 09:38 |
| mcape | Can anyone confirm that? What are your feelings? :-) | 09:38 |
| mcape | There is a 20+ mln file container in that Ocata deployment, and it is under heavy HEAD load | 10:01 |
| mcape | so, there is a need to figure out how to execute rapid transition to version which supports container sharding | 10:09 |
| *** e0ne has quit IRC | 10:22 | |
| *** e0ne has joined #openstack-swift | 10:23 | |
| *** mcape has quit IRC | 10:29 | |
| *** kazsh has quit IRC | 10:46 | |
| *** kazsh has joined #openstack-swift | 10:52 | |
| *** e0ne has quit IRC | 11:11 | |
| *** e0ne has joined #openstack-swift | 11:14 | |
| *** mcape has joined #openstack-swift | 11:19 | |
| *** e0ne has quit IRC | 11:49 | |
| *** henriqueof has joined #openstack-swift | 11:55 | |
| *** mcape has quit IRC | 12:05 | |
| *** mcape has joined #openstack-swift | 12:10 | |
| *** threestrands has quit IRC | 12:24 | |
| *** ybunker has joined #openstack-swift | 12:39 | |
| ybunker | hi to all, quick question... i just deploy two new data nodes to an already created cluster, and in the rsyncd.log file im getting the following errors messages: | 12:40 |
| ybunker | unknown module 'container' tried from (hostname) xx.xx.xx.xx | 12:40 |
| ybunker | and i notice that objects are written to the disks.. but accounts or containers are not | 12:41 |
| ybunker | also on the account logs i find this: | 12:48 |
| ybunker | account-replicator: Can't find itself 127.0.0.1, ::1, 172.xx.xx.xx, xxxx::xxxx:xxxx:xxxx:xxxx, 10.xx.xx.xx, xxxx::xxxx:xxxx:xxxx:xxxx, 172.xx.xx.xx, xxxx::xxxx:xxxx:xxxx:xxxx with port 4101 in ring file, not replicating | 12:50 |
| *** e0ne has joined #openstack-swift | 12:50 | |
| *** ybunker has quit IRC | 13:03 | |
| *** ybunker has joined #openstack-swift | 13:04 | |
| ybunker | any ideas? | 13:06 |
| *** ybunker has quit IRC | 13:21 | |
| *** ybunker has joined #openstack-swift | 13:25 | |
| ybunker | anyone? | 13:27 |
| *** ybunker has quit IRC | 13:33 | |
| *** ccamacho has quit IRC | 14:33 | |
| *** ccamacho has joined #openstack-swift | 14:34 | |
| *** ccamacho has quit IRC | 14:51 | |
| *** ccamacho has joined #openstack-swift | 14:53 | |
| *** itlinux has joined #openstack-swift | 15:01 | |
| *** itlinux has quit IRC | 15:12 | |
| *** mcape has quit IRC | 15:18 | |
| *** itlinux has joined #openstack-swift | 15:29 | |
| *** itlinux has quit IRC | 15:36 | |
| *** itlinux has joined #openstack-swift | 15:38 | |
| *** jistr is now known as jistr|mtg | 15:38 | |
| *** e0ne has quit IRC | 15:38 | |
| *** e0ne has joined #openstack-swift | 15:39 | |
| notmyname | good morning | 15:50 |
| *** jistr|mtg is now known as jistr | 16:02 | |
| *** e0ne has quit IRC | 16:14 | |
| *** e0ne has joined #openstack-swift | 16:15 | |
| *** e0ne has quit IRC | 16:17 | |
| *** gkadam has quit IRC | 16:27 | |
| openstackgerrit | John Dickinson proposed openstack/python-swiftclient master: authors/changelog updates for release https://review.openstack.org/639474 | 16:33 |
| notmyname | timburke: should be a little more correct and clear ^^ | 16:33 |
| notmyname | timburke: and I've gone ahead and added a +2/+A to get the gate started. yell at me if something is wrong :-) | 16:34 |
| *** psachin has quit IRC | 16:38 | |
| *** itlinux has quit IRC | 16:49 | |
| *** gyee has joined #openstack-swift | 17:04 | |
| timburke | notmyname, worth mentioning p 639777? | 17:39 |
| patchbot | https://review.openstack.org/#/c/639777/ - python-swiftclient - Add py37 check/gate jobs; add py37 to default tox ... (MERGED) - 2 patch sets | 17:39 |
| *** mvkr has quit IRC | 18:02 | |
| *** mvkr has joined #openstack-swift | 18:06 | |
| *** irclogbot_2 has joined #openstack-swift | 18:12 | |
| notmyname | timburke: IMO, not really. if there had been some change we had to make to the code to support py3 (ie it definitely didn't work before), then yes absolutely we'd mention it. but since it's a "now we're actually testing that" but didnt' change anything, it's not as big of a deal to call out | 18:23 |
| *** Chealion has joined #openstack-swift | 18:43 | |
| *** e0ne has joined #openstack-swift | 19:12 | |
| *** e0ne has quit IRC | 19:31 | |
| *** irclogbot_2 has quit IRC | 19:49 | |
| *** irclogbot_2 has joined #openstack-swift | 20:04 | |
| *** e0ne has joined #openstack-swift | 20:05 | |
| *** guimaluf has joined #openstack-swift | 20:37 | |
| *** zaitcev has joined #openstack-swift | 20:39 | |
| *** ChanServ sets mode: +v zaitcev | 20:39 | |
| *** chocolate-elvis has joined #openstack-swift | 20:48 | |
| henriqueof | notmyname: Can I deploy swift using a LVM LV? | 21:09 |
| notmyname | henriqueof: yes, in the sense that it will work. format your LV with one partition, put XFS on it, and you're good to go | 21:09 |
| notmyname | however... | 21:09 |
| notmyname | it's generally not a good idea to run in prod that way. or rather, it's probably not a good idea | 21:10 |
| notmyname | for example, you don't want to have a bunhc of physical volumes in the volume group you're carving logical volumes out of | 21:10 |
| notmyname | it's very important to not hide physical failure domains (drives, servers, racks, DCs) from swift. swift uses that info to make placement decisions to protect durability and availability | 21:11 |
| notmyname | if you start hiding them (eg several logical volumes backed by one physical volume), bad things may happen. for example, swift may place replicas on two separate drives, but if they're backed by the same PV, and it dies, you're in a much worse state than if it just had one replica on it | 21:12 |
| notmyname | so... to set up a dev cluster for some testing? sure, why not? if it makes it easier, go for it. (TBH, I have my dev box set up similarly to this) | 21:13 |
| notmyname | for prod data? I think that's a bad idea | 21:13 |
| henriqueof | Okay, but I have a layer of integrity, I am doing it on a Dell R730xd, it have a RAID controller so if one disk fails it wont affect the deployment immediately. | 21:14 |
| henriqueof | What dou you think? | 21:15 |
| notmyname | I think you're adding a bunch of layers of complexity that will, at best, make debugging hard, and at worst start competing against each other. | 21:17 |
| notmyname | the best way to deploy swift is on bare metal machines with a bunch of direct-attached drives. no raid, no virtualization, no lvm. just a bunch of disks | 21:17 |
| henriqueof | I see, don't get me wrong, I am dealing with a lack of resources, need to work with what I have. :) | 21:18 |
| notmyname | yeah, I understand :-) | 21:19 |
| notmyname | I'm not saying it won't *work* | 21:19 |
| henriqueof | Just need a object storage solution and I don't think Ceph goes well with only one node. | 21:19 |
| notmyname | how many drives do you have in that server? | 21:19 |
| henriqueof | 17 x 1.2T, 10K | 21:20 |
| openstackgerrit | Tim Burke proposed openstack/swift master: py3: fix copying unicode names https://review.openstack.org/640518 | 21:22 |
| openstackgerrit | Tim Burke proposed openstack/swift master: Clean up func tests ahead of py3 https://review.openstack.org/640519 | 21:24 |
| notmyname | henriqueof: are those just data drives? do you have any flash drives in the system? | 21:26 |
| henriqueof | notmyname: All of then are data drives. | 21:27 |
| notmyname | henriqueof: adding all 17 drives with a 2x or 3x replica policy (depending on the durability, overhead you need) will work just fine. no need for adding RAID or LVM or anything like that | 21:31 |
| henriqueof | Well, I need to run Nova and Cinder on this server too. | 21:34 |
| *** irclogbot_2 has quit IRC | 21:38 | |
| henriqueof | How about I remove then from RAID, leave some physical disks for Swift and add the remaining on a big VG? | 21:39 |
| notmyname | ah. um... sure? that will probably work | 21:40 |
| notmyname | you've got a limited set of hardware that you're trying to do a lot of stuff with. so it's all a matter of where you want to make the tradeoffs. | 21:40 |
| notmyname | I mean, everything will function. it's just a question of what you prioritize on the limited hardware | 21:41 |
| *** e0ne has quit IRC | 22:24 | |
| *** henriqueof has quit IRC | 22:27 | |
| openstackgerrit | Merged openstack/python-swiftclient master: authors/changelog updates for release https://review.openstack.org/639474 | 22:29 |
| notmyname | https://review.openstack.org/640549 | 22:39 |
| patchbot | patch 640549 - releases - swiftclient 3.6.1 release - 1 patch set | 22:39 |
| *** nottrobin_ has joined #openstack-swift | 22:45 | |
| *** beisner_ has joined #openstack-swift | 22:45 | |
| *** seongsoocho_ has joined #openstack-swift | 22:45 | |
| *** seongsoocho has quit IRC | 22:52 | |
| *** beisner has quit IRC | 22:52 | |
| *** nottrobin has quit IRC | 22:52 | |
| *** beisner_ is now known as beisner | 22:52 | |
| *** seongsoocho_ is now known as seongsoocho | 22:52 | |
| *** nottrobin_ is now known as nottrobin | 22:52 | |
| *** kazsh has quit IRC | 22:55 | |
| *** kazsh has joined #openstack-swift | 22:59 | |
| openstackgerrit | Tim Burke proposed openstack/swift master: Stop monkey-patching mimetools https://review.openstack.org/640552 | 23:04 |
| *** frickler has quit IRC | 23:06 | |
| *** frickler has joined #openstack-swift | 23:06 | |
| zaitcev | timburke: coincidentally, I had a hand-rolled unquote() in bulk. It was the only way to do it... I'll investigate if I can use your wsgi_unquote in swob. Check this out: https://review.openstack.org/#/c/619303/2/swift/common/utils.py | 23:08 |
| patchbot | patch 619303 - swift - py3: port bulk middleware - 2 patch sets | 23:08 |
| notmyname | timburke: I'm not sure on p 640552. it doesn't seem as reliable. maybe that's because I don't really trust eventlet to keep a totally stable interface there? I cetainly don't have a better idea, especially given that the py2 mechanism just doesn't exist in py3 | 23:10 |
| patchbot | https://review.openstack.org/#/c/640552/ - swift - Stop monkey-patching mimetools - 1 patch set | 23:10 |
| timburke | zaitcev, oh jeez... i think i only got as far as noticing the quote_x()... | 23:11 |
| timburke | notmyname, there's a thing you could monkey patch to have a similar effect... it's just over in email.message, and when you touch it, pkg_resources breaks | 23:11 |
| notmyname | how/why does it break? | 23:12 |
| notmyname | /curious | 23:12 |
| timburke | meanwhile, eventlet hasn't touched https://github.com/eventlet/eventlet/blob/v0.24.1/eventlet/wsgi.py#L646-L652 in ~5years so... yay? | 23:12 |
| notmyname | seems like it's time to touch it!! ;-) | 23:13 |
| timburke | lemme get the traceback... it was extraordinarily not-obvious | 23:13 |
| timburke | notmyname, http://paste.openstack.org/show/746635/ | 23:13 |
| notmyname | yeah, there is nothing in there that says "you changed the email module" | 23:15 |
| timburke | notmyname, the good news is, i reworked https://review.openstack.org/#/c/640552/1/test/unit/proxy/test_server.py to do an end-to-end test, so we'll know if/when it breaks | 23:16 |
| patchbot | patch 640552 - swift - Stop monkey-patching mimetools - 1 patch set | 23:16 |
| timburke | (of course, we'd also get that out of our func tests, but y'know...) | 23:16 |
| notmyname | it would almost seem that there some sort of hashing of dependencies? | 23:17 |
| timburke | it's got soemthing to do with the parsing going on in https://github.com/pypa/setuptools/blob/master/pkg_resources/__init__.py#L2670-L2709 | 23:19 |
| timburke | (i think) | 23:19 |
| timburke | see also: https://github.com/pypa/setuptools/blob/master/pkg_resources/__init__.py#L2969 | 23:20 |
| timburke | personally, i rather like the change. more than twice as many deletions as insertions, change is localized to the bit that actually cares about it... needing to remember to pass the SwiftHttpProtocol in test/unit/helpers.py was a little annoying but ultimately a better mirror of reality. the only real badness is the coupling with eventlet | 23:23 |
| timburke | it's almost like it'd be nice to get off eventlet or something... | 23:23 |
| notmyname | heh | 23:23 |
| zaitcev | What's the alternative? | 23:39 |
| zaitcev | There was something in py3, but I forgot its moniker. | 23:40 |
| zaitcev | Maybe this? http://bottlepy.org/docs/dev/ | 23:41 |
| openstackgerrit | Tim Burke proposed openstack/swift master: py3: port object updater https://review.openstack.org/639201 | 23:41 |
| zaitcev | "Bottle supports Python 2.7 and Python 3." | 23:41 |
| zaitcev | I don't want the cure to be worse than the disease. | 23:42 |
| notmyname | sweventlet, of course ;-) | 23:43 |
| zaitcev | oh go | 23:53 |
| zaitcev | d | 23:53 |
| zaitcev | I think we should have a recheck deadpool. The object auditor took 5 rechecks. So.... Let's give updater 4. | 23:54 |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!