Friday, 2019-03-22

*** gyee has quit IRC00:11
*** irclogbot_3 has joined #openstack-swift00:17
*** mikecmpbll has quit IRC01:20
*** itlinux has joined #openstack-swift01:34
*** psachin has joined #openstack-swift02:48
openstackgerritMerged openstack/swift master: py3: port formpost middleware  https://review.openstack.org/63950202:55
*** zaitcev has quit IRC04:06
*** coreycb has quit IRC04:31
*** fyx has quit IRC04:31
*** spsurya has quit IRC04:31
*** clayg has quit IRC04:31
*** hogepodge has quit IRC04:32
*** nottrobin has quit IRC04:33
*** clayg has joined #openstack-swift04:34
*** ChanServ sets mode: +v clayg04:34
*** coreycb has joined #openstack-swift04:34
*** spsurya has joined #openstack-swift04:34
*** fyx has joined #openstack-swift04:34
*** hogepodge has joined #openstack-swift04:35
*** nottrobin has joined #openstack-swift04:36
*** tkajinam has quit IRC05:59
*** tkajinam has joined #openstack-swift05:59
*** psachin has quit IRC06:20
*** psachin has joined #openstack-swift06:25
*** rcernin has quit IRC07:07
*** pcaruana has joined #openstack-swift07:27
*** hseipp has joined #openstack-swift08:13
*** tkajinam has quit IRC08:34
*** mikecmpbll has joined #openstack-swift08:51
*** rdejoux has joined #openstack-swift10:13
*** spsurya has quit IRC10:59
*** spsurya has joined #openstack-swift11:01
*** notmyname has quit IRC11:28
*** notmyname has joined #openstack-swift11:30
*** ChanServ sets mode: +v notmyname11:30
*** pcaruana has quit IRC11:53
*** MooingLe1ur has joined #openstack-swift12:10
*** MooingLemur has quit IRC12:14
*** hseipp has quit IRC12:30
*** mikecmpbll has quit IRC12:35
*** mikecmpbll has joined #openstack-swift12:36
*** pcaruana has joined #openstack-swift12:54
*** irclogbot_3 has quit IRC13:01
*** altlogbot_0 has quit IRC13:01
*** irclogbot_2 has joined #openstack-swift13:02
*** altlogbot_1 has joined #openstack-swift13:02
*** henriqueof has joined #openstack-swift14:35
henriqueofHow does replication works on Swift, per server or disk? I have a server with three disks, does it mean that if one disk fails I have replicas on the other two?14:36
henriqueofSorry if this is a simple question, I can find clear info on the docs.14:37
tdasilvahenriqueof: that's a very simple example, but yes. normally you would not build a production cluster with just one node tho. So when you add more more nodes swift would make sure that replicas are stored in different nodes too, not just different disks. Swift has a concept of failures domains, so it always which basically goes like: disks, nodes, zones and regions. As you deploy your cluster with all those failures14:52
tdasilvadomains well defined it will attempt to store replicas in different failure domains14:52
tdasilvathis is an old video but it explains pretty well: https://youtu.be/LzaQKKp58JI14:52
henriqueoftdasilva: Thank you!14:54
henriqueofSo this also means that I have the storage space available of just one disk, right?14:55
*** _david_sohonet has quit IRC14:58
tdasilvahenriqueof: yeah, if your entire cluster consists of 3 identical disks and you setup for 3 replicas, then your available space is just one disk size15:11
*** altlogbot_1 has quit IRC15:21
openstackgerritSean McGinnis proposed openstack/swift master: Fix lower-constraint deps handling  https://review.openstack.org/64562415:24
*** altlogbot_3 has joined #openstack-swift15:26
*** irclogbot_2 has quit IRC15:30
*** irclogbot_1 has joined #openstack-swift15:33
*** irclogbot_1 has quit IRC15:36
*** irclogbot_1 has joined #openstack-swift15:38
*** _david_sohonet has joined #openstack-swift15:53
notmynamegood morning16:09
timburkehenriqueof, though as you add more disks, you can use the weight in the ring to ensure you get to use all available capacity. so if you had 5 drives for a three replica policy, 3x 4TB then you upgrade and add 2x 12TB, you should be setting the weights for the new drives to 3x the old drives' weights, and data will get rebalanced so each 12TB drive should be responsible for one replica, and the three 4TB drives will divide the work of being16:39
timburkeresponsible for the remaining replica on a per-object basis16:39
timburke(note that you'd want to do such an upgrade well before the 4TB drives get full, though; rebalances can take a while, and you *definitely* don't want to let the drives completely fill up)16:43
*** e0ne has joined #openstack-swift16:48
*** e0ne has quit IRC16:59
timburkewtf? http://logs.openstack.org/24/645624/1/check/swift-tox-lower-constraints/b06abcd/job-output.txt.gz#_2019-03-22_15_49_06_63542817:06
*** mikecmpbll has quit IRC17:06
*** psachin has quit IRC17:48
*** gmann is now known as gmann_afk17:52
*** mikecmpbll has joined #openstack-swift18:01
*** gmann_afk is now known as gmann18:11
timburkesome interaction between cryptography and openssl apparently...18:12
*** renich has joined #openstack-swift18:20
openstackgerritTim Burke proposed openstack/swift master: Fix lower-constraint deps handling  https://review.openstack.org/64562418:43
timburke^^^ is interesting... i think it might give me a framework to get those py3 func tests running in the gate without too much pain...18:44
*** pcaruana has quit IRC18:45
notmynametimburke: where are we with patches for a release right now?18:47
notmynameI know I need to renofy the changelog, but I think it's ready for that18:47
notmynameI'll be doing that after lunch18:47
*** rchurch has quit IRC18:48
timburkei'd still like to see the crypto patches land, particularly https://review.openstack.org/#/c/633671/18:56
patchbotpatch 633671 - swift - Fix decryption for broken objects - 8 patch sets18:56
timburkeidk that we've got time, though18:56
timburkecschwede, tdasilva, clayg, anybody got bandwidth for a review there? i know zaitcev had looked at it once, anyway...18:58
openstackgerritJohn Dickinson proposed openstack/swift master: authors/changelog update for 2.21.0 release  https://review.openstack.org/64532519:01
notmynamewell maybe right before lunch :-)19:01
openstackgerritTim Burke proposed openstack/swift master: Add py37 func test job  https://review.openstack.org/64585619:28
timburkefeh, the constraints thing didn't work as well as i hoped. will JIT install from master instead; not actually much worse to think about, but i *really* don't want to have to do that for any more deps...19:31
*** rdejoux has quit IRC19:35
timburke:D http://logs.openstack.org/56/645856/1/check/swift-tox-func-py37/a3bcf3b/job-output.txt.gz#_2019-03-22_19_41_42_91696519:43
*** renich has quit IRC20:40
*** renich has joined #openstack-swift21:29
*** henriqueof has quit IRC21:33
openstackgerritTim Burke proposed openstack/swift master: py3: Bring functional/test_object.py under test; add func-ec-py37 job  https://review.openstack.org/64589521:48
timburkethis chain's getting a little long...21:49
*** e0ne has joined #openstack-swift21:54
openstackgerritMerged openstack/swift stable/rocky: Imported Translations from Zanata  https://review.openstack.org/63737122:13
timburkethanks, clayg!22:21
openstackgerritMerged openstack/swift master: Fix decryption for broken objects  https://review.openstack.org/63367122:31
*** e0ne has quit IRC22:36
*** _david_sohonet has quit IRC23:04
*** thurloat1 has joined #openstack-swift23:17
*** thurloat has quit IRC23:20
openstackgerritJohn Dickinson proposed openstack/swift master: authors/changelog update for 2.21.0 release  https://review.openstack.org/64532523:53

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