Wednesday, 2018-12-12

openstackgerritTim Burke proposed openstack/swift master: s3token: Add an underscore to the end of reseller_prefix if not present  https://review.openstack.org/61704300:02
*** itlinux has joined #openstack-swift00:06
openstackgerritTim Burke proposed openstack/swift master: s3api: Stop mangling Authorization header for v4 signatures  https://review.openstack.org/59186200:16
openstackgerritTim Burke proposed openstack/swift master: We don't have to keep the retrieved token anymore  https://review.openstack.org/60916800:16
*** itlinux_ has joined #openstack-swift00:25
*** itlinux has quit IRC00:28
*** itlinux_ has quit IRC00:49
kota_good morning01:09
kota_it's super cool in Tokyo.01:09
*** psachin has joined #openstack-swift03:27
kota_ah, okay. the key stopper for swift 2.20.0 was https://review.openstack.org/#/c/592231/ and it got merged by clayg so that no blocker found anymore on s3api04:07
patchbotpatch 592231 - swift - s3api: Include '-' in S3 ETags of normal SLOs (MERGED) - 6 patch sets04:07
kota_perhaps, https://review.openstack.org/#/c/610747/ is nice to have tho04:08
patchbotpatch 610747 - swift - s3api: Stop relying on container listings during m... - 4 patch sets04:08
*** dhellmann has quit IRC05:19
*** dhellmann has joined #openstack-swift05:20
*** itlinux has joined #openstack-swift05:21
*** itlinux has quit IRC05:51
*** nguyenhai_ has quit IRC06:47
*** nguyenhai has joined #openstack-swift07:07
*** e0ne has joined #openstack-swift07:13
rledisezclayg: about p 611614: while working on p 613987, I was thinking "I'll need to do something about partition lock to make it works". surprisingly, I had nothing to do, it was a bug! :)07:27
patchbothttps://review.openstack.org/#/c/611614/ - swift - Fix SSYNC concurrency on partition (MERGED) - 5 patch sets07:27
patchbothttps://review.openstack.org/#/c/613987/ - swift - SSYNC: enable multiple SSYNC connections per job - 2 patch sets07:27
rledisezfor the record, I had issues with the multiple ssync patch, because replicators/reconstructors were hanging with no visible reasons. i'll try again with p 62336007:28
patchbothttps://review.openstack.org/#/c/623360/ - swift - Make GreenAsyncPile not hang - 1 patch set07:28
*** openstackgerrit has quit IRC07:29
*** rcernin has quit IRC07:30
rlediseztimburke: the bug fixed by p 619502 should impact all versions since 2.18, so it might be of interest to backport it (we had the issue while deploying 2.18)07:32
patchbothttps://review.openstack.org/#/c/619502/ - swift - Use eventlet.patcher.original to get Python select... (MERGED) - 2 patch sets07:32
kota_rledisez: o/07:53
*** hseipp has joined #openstack-swift07:55
rledisezkota_: hi o/08:09
kota_rledisez: i just sent you an E-mail in my morning please check it out.08:10
kota_and /me is interested the patches above :)08:10
*** e0ne has quit IRC08:31
*** ccamacho has joined #openstack-swift08:37
rledisezkota_: yeah, I saw your mail. I'll arrange everything so that /me and alecuyer are here with you.09:08
*** psachin is now known as psachin|session09:35
mattoliverauHey all, sorry was off work today. It's the wife's bday tomorrow so might not make the meeting. My morning will be a little busy me thinks.09:40
*** gkadam has joined #openstack-swift10:05
*** gkadam has quit IRC10:05
*** e0ne has joined #openstack-swift10:08
*** NM has joined #openstack-swift10:54
*** e0ne has quit IRC11:30
*** NM has quit IRC11:37
*** NM has joined #openstack-swift11:38
*** NM has quit IRC11:59
*** NM has joined #openstack-swift12:05
*** NM has quit IRC12:39
*** hseipp has quit IRC12:46
*** hseipp has joined #openstack-swift12:50
*** hseipp has quit IRC13:00
*** hseipp has joined #openstack-swift13:02
*** NM has joined #openstack-swift13:18
*** NM has quit IRC13:43
*** NM has joined #openstack-swift13:44
*** NM has quit IRC13:59
*** NM has joined #openstack-swift14:02
*** NM has quit IRC14:05
*** NM has joined #openstack-swift14:07
*** NM has joined #openstack-swift14:18
*** NM has quit IRC14:25
*** NM has joined #openstack-swift14:31
*** irclogbot_2 has quit IRC14:32
*** e0ne has joined #openstack-swift14:38
*** irclogbot_2 has joined #openstack-swift14:43
*** irclogbot_2 has quit IRC14:52
*** hseipp has quit IRC14:57
zigoA quick question, after I did a big mistake.14:59
zigoDoes swift-ring-builder add some kind of ramdom thing when it builds the object ring for object placement?14:59
zigoI thought it was kind of deterministic, but it's not.14:59
zigoWe had to recover from a backup of the ring.14:59
DHEit's sorta random in terms of assignment, but it's careful about assignments in general. assuming you set min_part_hours=24 it will try to not modify a partition by more than 1 replica every 24 hours15:03
DHEhow old is your backup?15:05
*** irclogbot_2 has joined #openstack-swift15:07
*** hseipp has joined #openstack-swift15:16
notmynamezigo: there is also a randomness component. you can set the random seed when rebalancing so you can get the same result when building a ring in multiple places15:24
notmynamethe `--seed` option15:26
DHEthere is a "swift-ring-builder <existingringfile.gz> write_builder" command to try making a new builder file using an existing ring.15:27
DHEif you haven't made ring changes in 24 hours otherwise, it's likely safe15:28
*** gyee has joined #openstack-swift16:19
zigonotmyname: Is there a way to get the seed of my previously created ring then?16:31
DHEzigo: if you can use the write_builder command, this should be a non-issue. you can just take your live ring file(s) and convert them back to builders which should be sufficient, yes?16:36
zigoDHE: What I am trying to do, is to get my deployment software to always produce the same ring files, starting from scratch.16:37
zigoSo best would be if I could find out the --seed option ...16:37
zigoBecause now it's too late, as I didn't use it.16:38
zigo(and we're already in production)16:38
DHEokay, I thought this was just a case of recovering from a lost builder file16:39
tdasilvazigo: if you can backup your builder file, you should not need to use --seed16:42
notmynamezigo: yeah, that's a great question. earlier I'd done a quick check and it doesn't show in the ring-builder output. but maybe it's stored somewhere. I'm about to commute, but if you don't have an answer, I can check when I can get to the office16:42
notmynamemaybe clayg knows off the top of his head16:42
zigoCheers.16:48
*** itlinux has joined #openstack-swift16:53
*** mikecmpbll has joined #openstack-swift17:17
*** psachin|session has quit IRC17:20
*** e0ne has quit IRC17:21
*** hseipp has quit IRC17:24
*** mikecmpbll has quit IRC17:35
*** ianychoi has joined #openstack-swift17:38
*** mikecmpbll has joined #openstack-swift17:44
*** NM has quit IRC18:39
notmynamezigo: follow-up: no, it does not look like the random seed is stored. however, it doesn't really *need* to be stored. it only matters for a single rebalance run. it's not something that matters for one rebalance to another or translating a builder to a ring.gz18:54
notmynamethe purpose of the --seed option is to be able to run the same ring operation on different nodes and get the same resulting ring18:55
notmynameinstead of the more common operation of centrally doing the ring operation and distributing the resulting ring18:55
notmynamesounds like it may be what you need for your automation, though18:55
*** e0ne has joined #openstack-swift19:20
*** e0ne_ has joined #openstack-swift19:27
*** openstackgerrit has joined #openstack-swift19:27
openstackgerritCyril Roelandt proposed openstack/swift master: Python3: fix test_xprofile.py  https://review.openstack.org/62479119:27
*** e0ne has quit IRC19:27
*** e0ne_ has quit IRC19:30
*** e0ne has joined #openstack-swift19:34
*** NM has joined #openstack-swift19:37
*** e0ne_ has joined #openstack-swift19:39
openstackgerritCyril Roelandt proposed openstack/swift master: Py3: Add working tests to tox.ini  https://review.openstack.org/62479219:40
*** e0ne has quit IRC19:41
*** e0ne has joined #openstack-swift19:44
*** e0ne_ has quit IRC19:45
*** e0ne has quit IRC19:45
*** e0ne has joined #openstack-swift19:46
*** e0ne has quit IRC19:54
*** itlinux_ has joined #openstack-swift20:14
*** itlinux has quit IRC20:15
*** e0ne has joined #openstack-swift20:15
*** e0ne has quit IRC20:16
*** NM has quit IRC20:28
kota_morning20:58
notmynamekota_: good morning20:59
notmynamekota_: for some reason I thought you were at kubecon this week20:59
kota_notmyname: o/20:59
kota_notmyname: me too but it's false ;)21:00
notmyname:-)21:00
notmynamekota_: mattoliverau: rledisez: clayg: tdasilva: timburke: zaitcev: meeting time in openstack-meeting21:00
*** zaitcev has joined #openstack-swift21:05
*** ChanServ sets mode: +v zaitcev21:05
zaitcevIs community meeting on today?21:06
zaitcevOh.21:06
*** rcernin has joined #openstack-swift21:06
*** itlinux_ has quit IRC22:00
*** itlinux has joined #openstack-swift22:00
openstackgerritCyril Roelandt proposed openstack/swift master: Py3: Add working tests to tox.ini  https://review.openstack.org/62479222:06
*** mpasserini has quit IRC22:29
*** rledisez has quit IRC22:29
*** godog has quit IRC22:29
*** itlinux has quit IRC22:35
*** mahatic has quit IRC23:38
notmynameworking on the changelog, I've noticed that there are a *lot* of commit subjects that start with the category of stuff they change. eg "s3api: ..." or "ssync: ..." or "py3: ..."23:52
notmynameit is *extremely* helpful23:52

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