Friday, 2015-11-06

*** haomaiwa_ has quit IRC00:01
*** haomaiwang has joined #openstack-swift00:01
*** wbhuber has joined #openstack-swift00:02
claygbriancline: np00:05
*** pchng_ghost has joined #openstack-swift00:10
*** pchng_ has quit IRC00:13
jrichliacoles_ : I now remember having the same issue before with the content-type in container listing becoming "<content-type>;meta=".   I got around that by encoding the content-type value00:16
jrichliacoles_ hrou: and I think I now remember hrou asking about that extra encoding, and I just didn't remember why it was there.  It was removed.  Now I think we have discovered why ;-)00:17
claygour current part-placement algo sucks:00:23
claygTier                           Parts      %    Max     0     1     2     300:23
clayg--------------------------------------------------------------------------00:23
claygr1z3-127.0.0.1/sdb3              668  14.97      1   356   568   100     000:23
claygsomeone should really fix that00:23
claygacoles_: I might need you to explain to me why ssync needs to keep two .meta's around00:24
wbhuberclayg: uve a launchpad bug for that?00:24
claygacoles_: i saw that when I had a server who had the latest metadata but needed the ctype - it got a duplciate meta file with a bigger -<ctime> delta00:25
claygacoles_: it was happy to leave both files on disk until it needed to move the part00:25
claygvery strange...00:25
claygwell, maybe not - i guess creating a new meta file for the ctype is probably no worse that creating a new meta with the combined info and removing the old - maybe it's even better a little00:26
claygjust weird to have to obj dirs that represent the same information but have different on disk representations (maybe?)00:26
claygwbhuber: lp bug #1452431 and patch #24157100:27
openstackLaunchpad bug 1452431 in OpenStack Object Storage (swift) "some parts replicas assigned to duplicate devices in the ring" [High,Confirmed] https://launchpad.net/bugs/1452431 - Assigned to Samuel Merritt (torgomatic)00:27
*** diogogmt has joined #openstack-swift00:29
serverascodedoes anyone have recommendations on what documentation I can look at that will help me understand what happens when I add a region to a swift cluster? like how much data will move around and such?00:34
claygserverascode: i'm not sure that's well documented00:39
serverascodeyeah I'm having a hard time trying to figure out what will happen00:40
claygserverascode: you take your prod rings into a temp dir and play around with adding the devices and see whats-what with "dispersion -v"00:40
claygserverascode: well same thing that happens when you add a zone, except if you have more replicas than regions a lot of parts are going to *want* to move - but maybe won't be able to (yet) until you add more capacity (weight) to the remote region00:42
serverascodeclayg: thanks, ok, I will look into that :)00:42
*** m_kazuhiro has joined #openstack-swift00:43
claygok, i'm pretty happy working through the failure modes on fast-POST functionally00:44
claygcontainers and object trees all seem to consistent stuff up - POST is doing it's thing with the asyncs00:44
*** jamielennox is now known as jamielennox|away00:46
claygoh - i guess I didn't do anything with different data files on disk - let me see what I can cook up there00:46
kota_good morning00:47
*** jamielennox|away is now known as jamielennox00:47
*** daemontool has quit IRC00:48
*** daemontool has joined #openstack-swift00:48
claygoh i totally forgot about swift-init *-replicator status00:52
*** jamielennox is now known as jamielennox|away00:58
*** haomaiwang has quit IRC01:01
*** haomaiwang has joined #openstack-swift01:01
*** jamielennox|away is now known as jamielennox01:06
*** badari has quit IRC01:06
jrichlikota_ : good morning01:07
kota_jrichli: :-)01:07
*** mzhou has quit IRC01:08
*** cschwede has quit IRC01:17
*** badari has joined #openstack-swift01:18
*** badari has quit IRC01:24
*** zhill has quit IRC01:24
*** garthb has quit IRC01:25
*** asettle has quit IRC01:36
claygacoles_: phew - that was fun!01:37
openstackgerritKota Tsuyuzaki proposed openstack/swift: Add missing docs for ring.builder.rebalance  https://review.openstack.org/24229501:41
openstackgerritSivasathurappan Radhakrishnan proposed openstack/swift: Added unit test cases for server Added three unit test cases for REPLICATE and __call_ magic methods in account and container  https://review.openstack.org/24230001:52
*** badari has joined #openstack-swift01:53
*** janonymous has joined #openstack-swift01:57
*** haomaiwang has quit IRC02:01
*** haomaiwang has joined #openstack-swift02:01
*** janonymous has quit IRC02:09
*** breitz2 has quit IRC02:11
*** breitz has joined #openstack-swift02:12
*** asettle has joined #openstack-swift02:27
*** gyee has quit IRC02:31
*** mahatic has joined #openstack-swift02:45
mahaticgood morning02:50
*** hrou has joined #openstack-swift02:54
openstackgerritMerged openstack/swift: Device marked to be removed in info about the ring.  https://review.openstack.org/23891703:00
*** haomaiwang has quit IRC03:01
*** haomaiwang has joined #openstack-swift03:02
janonymous_morning03:08
*** aagrawal has joined #openstack-swift03:21
*** badari has quit IRC03:25
*** wbhuber has quit IRC03:38
*** wbhuber has joined #openstack-swift03:39
*** wbhuber has quit IRC03:47
*** wbhuber has joined #openstack-swift03:48
*** haomaiwang has quit IRC03:51
*** wbhuber has quit IRC03:55
*** links has joined #openstack-swift03:59
kota_mahatic, janonymous: good morning03:59
openstackgerritMerged openstack/swift: Add unit tests for utils.validate_hash_path  https://review.openstack.org/23190504:00
janonymous_kota_ : o/04:01
*** hrou has quit IRC04:11
*** ppai has joined #openstack-swift04:19
openstackgerritBill Huber proposed openstack/swift: ObjectControllers return application errors as 499 on bad read  https://review.openstack.org/23600704:23
*** mwheckmann has joined #openstack-swift04:32
*** wuhg has joined #openstack-swift04:43
*** jrichli_ has joined #openstack-swift05:02
*** m_kazuhiro has quit IRC05:03
*** jrichli has quit IRC05:05
*** zhill has joined #openstack-swift05:08
*** jrichli_ has quit IRC05:10
*** klrmn1 has joined #openstack-swift05:11
*** klrmn2 has quit IRC05:11
*** zhill has quit IRC05:15
*** jerrygb_ has quit IRC05:18
*** klrmn1 has quit IRC05:26
*** asettle has quit IRC05:27
*** jlhinson has joined #openstack-swift05:27
*** venkat_p has joined #openstack-swift05:30
*** mahatic_ has joined #openstack-swift05:50
*** mahatic has quit IRC05:54
*** jlhinson has quit IRC06:01
*** mwheckmann has quit IRC06:02
*** m_kazuhiro has joined #openstack-swift06:14
*** haomaiwang has joined #openstack-swift06:20
*** openstackgerrit has quit IRC06:31
*** openstackgerrit has joined #openstack-swift06:31
*** zhill has joined #openstack-swift06:32
*** david-lyle has joined #openstack-swift06:40
*** peterlisak has joined #openstack-swift06:44
*** david-lyle has quit IRC06:45
*** mahatic_ has quit IRC06:47
*** mahatic has joined #openstack-swift06:49
*** jamielennox is now known as jamielennox|away06:59
*** haomaiwang has quit IRC07:01
openstackgerritKota Tsuyuzaki proposed openstack/swift: Read the response body, if response status is greater than 300.  https://review.openstack.org/18389907:01
*** haomaiwang has joined #openstack-swift07:01
*** zhill has quit IRC07:20
clayggreat patch 241571 is in conflict07:20
patchbotclayg: https://review.openstack.org/#/c/241571/ - Put part-replicas where they go07:20
openstackgerritClay Gerrard proposed openstack/swift: Put part-replicas where they go  https://review.openstack.org/24157107:35
claygcould have been worse, we'll see what gerrit says07:35
*** SkyRocknRoll has joined #openstack-swift07:37
*** cschwede has joined #openstack-swift07:51
*** ChanServ sets mode: +v cschwede07:55
*** arnox has joined #openstack-swift08:00
*** haomaiwang has quit IRC08:01
*** haomaiwang has joined #openstack-swift08:01
hugokuonot sure if this is a bug or my mistake...    How will you use POST to add header on an manifest file ?  Let's say add X-Delete-At on a manifest file08:07
hugokuoWhile issue a POST to manifest file, it pulls all segments and store it as a single object in server side.08:07
*** haomaiwang has quit IRC08:11
hugokuobtw... it's for DLO08:17
*** rledisez has joined #openstack-swift08:20
mahatichugokuo: https://bugs.launchpad.net/swift/+bug/1487791 - this might be relevant08:22
openstackLaunchpad bug 1487791 in OpenStack Object Storage (swift) "POST to DLO squashes data without fast-POST" [Undecided,New]08:22
*** geaaru has joined #openstack-swift08:24
hugokuo@mahatic yes... it is. thx08:25
claygwooo look at mahatic knows all the bugs08:30
mahaticclayg: :D no, I kinda stumbled onto it (when the other day I was asking about slo dlo)08:31
claygoh wtf ever cli tests!08:34
claygwho merged that crap?!08:34
claygkota_'s gotta update the doc strings08:34
claygi have a bunch of Replica count of 3.0 requires more than 2 devices failures that aren't even in the tests that are supposed to test ring building - they're just checking stupid cli output08:35
clayggrrrr08:35
kota_what's08:35
claygkota_: do you have a patch to fix the doc string on rebalance cause the return got changed?08:35
*** venkat_p has quit IRC08:36
kota_clayg: just docs change i have08:36
*** hseipp has joined #openstack-swift08:36
*** zigo has quit IRC08:37
claygkota_: it's no big deal "swift-ring-builder can't remove a device with zero weight" has bit me like three times now; but the chance was fine; shit happens; i'm just being whiny08:38
clayg*ignore me*08:39
mahatichow do you debug a functional test again? (not print but trace)08:39
kota_patch 233096?08:39
patchbotkota_: https://review.openstack.org/#/c/233096/ - swift-ring-builder can't remove a device with zero...08:39
claygmahatic: pdb?08:42
claygpdb.set_trace()08:42
*** zigo has joined #openstack-swift08:42
mahaticdoesn't work in func08:42
mahaticthat works for unit tests08:42
claygoh... well you can use inprocess08:42
claygi think..08:42
claygit may be that when it gets to that point I write a unittest08:42
kota_ah, the conflicted one might be patch 23891708:42
patchbotkota_: https://review.openstack.org/#/c/238917/ - Device marked to be removed in info about the ring.08:42
kota_clayg: sorry I added +A for that.08:42
claygkota_: oh yeah that one too08:42
claygno it's also a good change08:42
claygoh was that the one that added these cli tests?08:42
claygno...08:42
*** openstackstatus has quit IRC08:42
kota_that one added cli/ring_buider test for making sure the output.08:42
openstackgerritMerged openstack/swift: Read the response body, if response status is greater than 300.  https://review.openstack.org/18389908:44
claygoh08:47
mahaticclayg: maybe a unittest. not sure of inprocess - an option in set_trace?08:48
*** jordanP has joined #openstack-swift08:51
claygmahatic: I dont' even remember how to run inprocess func tests - I think you can just set an env flag08:54
claygor something with tox?08:54
mahaticyeah, i'm looking at it. thanks!08:54
clayggood merge that interal client fix - thanks kota!08:58
kota_clayg: :)08:58
openstackgerritClay Gerrard proposed openstack/swift: Put part-replicas where they go  https://review.openstack.org/24157108:59
*** venkat_p has joined #openstack-swift08:59
claygmahatic: where was the first place you looked for "SWIFT_TEST_IN_PROCESS=true .functests"09:02
claygor is that even what you came up with?09:02
claygmahatic: we should do a doc update09:02
claygi checked the README - then searched the saio docs - then I looked in test/functional/__init__.py (and eventually backed into the env var)09:04
claygbut i was advanaged knowing that in process functests were even a thing...09:04
mahaticclayg: true. saio can have a doc update maybe. or the first contribution09:05
claygmahatic: but fwiw pdb.set_trace totally worked09:05
mahaticclayg: and I didn't come up with that :) I was toggling with pycharm capabilities09:05
claygi'm up in my debug on an object server in the middle of a functional tests09:05
claygthose things are crazy09:06
claygpython is amazingawesomesause09:06
mahaticclayg: really? the console just stops when I put set_trace in func/tests.py09:06
clayg-vsx (nose tries to capture stdout by default)09:06
clayghow do you invoke the tests?09:06
claygpycharm magic?09:06
mahatichaha, nope. In this case nosetests /test/functional/tests.py09:07
claygsweet!09:07
claygyeah just -s (--no-capture)09:07
mahaticclayg: awesome! that works!09:08
claygwerd09:10
*** links has quit IRC09:11
claygnext time some one sees pdardeau we need tell him to get a bouncer setup09:11
claygpdardeau: patch 151376109:12
clayger... lp bug #151376109:12
openstackLaunchpad bug 1513761 in OpenStack Object Storage (swift) "in-process functests are not documented" [Undecided,New] https://launchpad.net/bugs/151376109:12
clayg^ cc portante09:12
mahaticcool, you raiseda  bug09:13
*** jistr has joined #openstack-swift09:19
mahaticclayg: it's actually documented here: http://docs.openstack.org/developer/swift/development_guidelines.html09:20
claygwell there you go!09:22
*** jmccarthy has quit IRC09:22
mahaticlesson leanrt: keep a tab of three docs - saio, first_contribution, development_guidelines (unless there are more?)09:23
*** jmccarthy has joined #openstack-swift09:24
claygheh09:24
claygi can tell which git review was for fast-POST because the number is so damn low09:25
*** acoles_ is now known as acoles09:26
acolesclayg: good morning09:27
* acoles comments on launchpad before connecting to irc :)09:27
claygacoles: I think we cross posted - i marked it as invalid - problem wasn't the information wasn't written down - just that I coudln't find it - happens all the time09:28
acolesclayg: true09:31
acolesclayg: thanks for the review!! i owe you a whisky or two!09:32
claygfor doing my job?09:33
claygit's fine - i owe you a whisky or two as well I'm sure09:33
claygacoles: I'm acctually still on about this ssync thing...09:33
acoleswell i'm always up for beers but you never want to stop talking work :P09:33
clayglook at these .meta's -> https://gist.github.com/clayg/a378a6ac4405d81d0aa309:33
acolesclayg: yeah i need to go and ponder that09:34
acolesclayg: so do you observe 94116-29010c.meta created *after* 94116.meta in same dir?? (i realise maybe its hard for you to know the order)09:36
claygno not hard - that's exactly what I see for sure09:38
acoles94116.meta *should* get removed - that may be a bug if it is not. Its contents would be same as  94116-29010c.meta except for the content-type09:38
acolesso its redundant once  94116-29010c.meta is written09:38
acoleshmmm09:38
claygconfirmed with swift-object-info the metadata from 94116 makes its way into 94116-29010c along with the older content-type09:40
*** haomaiwa_ has joined #openstack-swift09:40
clayg94116 has no conent-type (but it was the newest user metadata) - 94116-29010c has the new user metadata (but also the older content type update that was missing in 94116)09:41
claygacoles: do you expect hash_listdir_cleanup to sweep it out?  maybe it's just a < vs <= thing on the .meta time portion of the timestamp09:41
acolesright. so is suspect its a glitch in determining which .metas are obsolete, maybe i'm only comparing the primary timestamps, which are equal09:41
acolesclayg: yeah exactly what i am suspecting09:42
claygwell it's definately a problematic bug because it causes ssync partitions to have different hashes :\09:42
clayg(updated the gist)09:42
acolesneed a <= in place of <, or perhaps needs a comparison of ctype time09:43
claygacoles: I'll try to write you a test09:43
acolesclayg: thanks!09:44
*** haomaiwa_ has quit IRC09:45
claygacoles: https://gist.github.com/clayg/6a455fd71943256023fb09:51
claygI think something that exposes how ssync can end up shipping a combined udpate to a node that already has the newest meta would be a little more behavior driven09:52
claygbut if possible, it'd help with abstractions and holding it all in your head if you could count on hash_listdir_cleanup to just "do the right thing" no matter how the .meta files got in there09:53
acolesclayg: this ssync test *ought* to expose this, its probably just not asserting the dir contents - test/unit/obj/test_ssync_sender.py:245309:57
acolesclayg: yeah, agree, HCL should do the right thing. I'll look into it today.09:57
clayg/tmp/tmpOmC5V7/tmp_test_ssync_receiver/dev/objects/9/3d1/4f6587504178bff82772d66708d083d1/1446804093.00000-186a0.meta10:02
clayg/tmp/tmpOmC5V7/tmp_test_ssync_receiver/dev/objects/9/3d1/4f6587504178bff82772d66708d083d1/1446804093.00000.meta10:02
clayg^ rx_testdir - wtg test_content_type_sync10:03
claygacoles: ^10:03
claygok, so you've got two good tests to work from10:03
acolesclayg: got it10:03
acolesclayg: k, i have the baton, nice catch10:03
claygacoles: awesome - do you need me to ding you on the review?10:03
claygacoles: ok, great, yeah np - it was totaly luck10:04
claygg'night10:04
acolesi'll WIP it10:04
acolesyou too!10:04
*** joeljwright has joined #openstack-swift10:08
*** ChanServ sets mode: +v joeljwright10:08
*** venkat_p has quit IRC10:11
*** dabukalam has quit IRC10:12
*** mitz has quit IRC10:12
*** dabukalam has joined #openstack-swift10:13
*** mfalatic has joined #openstack-swift10:13
*** mitz has joined #openstack-swift10:14
*** mfalatic_ has quit IRC10:15
*** venkat_p has joined #openstack-swift10:24
openstackgerritAlistair Coles proposed openstack/swift: Guess content-type on PUT  https://review.openstack.org/23257210:40
acolesmahatic: you around? could you check the change i made to the tests ^^?10:40
mahaticacoles: sure, looking. I thought you'd have a simpler version of it - like a 2 line change or something :)10:42
acolesmahatic: is that a challenge - to compress it to 2 lines? :)10:43
mahaticacoles: nope :D, my version of it looked complicated (more line changes and a possible use of ast) which is why I didn't push10:44
mahaticacoles: happy to see your change also involved quite a few line change though ;) Thanks! Looks good, will run it on my local10:45
mahaticacoles: not sure if json.loads(param[5:]) won't result differently on diff machines10:49
*** jamielennox|away is now known as jamielennox10:49
mahaticwill have to wait for jenkins I guess10:49
acolesmahatic: which part? json.loads will return a dict. dict comparison is independent of how the keys might be ordered in the dicts.10:51
mahaticacoles: oh yeah, alright. nevermind10:51
acolesmahatic: the problem we ran into is when comparing serializations of dicts when the items get serialized in unpredictable order.10:52
acolesmahatic: a similar pitfall is to assert dict1.keys() == [a,b,c]  - it may be [c,a,b] or whatever.10:54
mahaticacoles: correct. dict1.keys() == similar_dict1.keys() wouldn't be a prob i think10:55
acolesmahatic: i think that's safe, i'd want to check before trusting my life on it though ;)10:57
mahaticacoles: heh, sure11:02
openstackgerritAlistair Coles proposed openstack/swift: Decrypting Container Listing  https://review.openstack.org/21443811:03
acoles^^ thats just a rebase11:03
mahaticokay11:05
*** aix has quit IRC11:07
*** jamielennox is now known as jamielennox|away11:11
*** lpabon has joined #openstack-swift11:43
*** aagrawal has quit IRC11:50
*** jerrygb has joined #openstack-swift11:54
*** kei_yama has quit IRC11:58
*** joeljwright has quit IRC11:59
*** joeljwright has joined #openstack-swift12:00
*** ChanServ sets mode: +v joeljwright12:00
* portante causes too much trouble!12:27
*** Guest7190 has quit IRC12:30
*** wuhg has quit IRC12:31
acolesportante: howdy!12:31
*** SkyRocknRoll has quit IRC12:34
*** zigo has quit IRC12:36
*** zigo has joined #openstack-swift12:37
*** weihan has joined #openstack-swift12:38
portanteacoles: how are things?12:38
kota_fyi, I'll be offline until next Tuesday for a vacation. just notification.12:44
*** venkat_p has quit IRC12:49
*** SkyRocknRoll has joined #openstack-swift12:51
*** weihan has quit IRC12:51
*** m_kazuhiro has quit IRC12:56
*** SkyRocknRoll_ has joined #openstack-swift12:58
*** NM has quit IRC13:28
*** NM has joined #openstack-swift13:28
*** aix has joined #openstack-swift13:29
acoleskota_: have fun13:36
acolesportante: good thanks13:36
kota_acoles: thx13:38
*** NM has quit IRC13:39
*** peterlisak has quit IRC13:40
*** peterlisak has joined #openstack-swift13:41
*** peterlisak_ has joined #openstack-swift13:42
*** pchng_ghost is now known as pchng13:46
*** peterlisak has quit IRC13:47
*** peterlisak_ is now known as peterlisak13:47
*** peterlisak13 has joined #openstack-swift13:47
*** mwheckmann has joined #openstack-swift13:48
*** diogogmt has quit IRC13:49
*** peterlisak has quit IRC13:51
*** peterlisak has joined #openstack-swift13:51
*** diogogmt has joined #openstack-swift13:53
*** peterlisak has quit IRC13:53
*** ppai has quit IRC13:54
*** hrou has joined #openstack-swift13:59
*** rohit_ has joined #openstack-swift14:01
*** dustins has joined #openstack-swift14:03
*** badari has joined #openstack-swift14:04
*** diazjf has joined #openstack-swift14:07
*** NM has joined #openstack-swift14:10
*** jrichli has joined #openstack-swift14:16
*** vinsh has joined #openstack-swift14:20
*** jlhinson has joined #openstack-swift14:21
*** diogogmt has quit IRC14:21
*** diogogmt has joined #openstack-swift14:26
*** petertr7_away is now known as petertr714:27
*** diazjf has quit IRC14:29
hroumahatic, I saw the convo earlier about testing !  I think some info about unit/func test debugging in the first contribution guide is still a great idea, I know often that's one of the first things people ask here !14:32
*** jlhinson has quit IRC14:43
*** diazjf has joined #openstack-swift14:49
*** pdardeau has joined #openstack-swift14:56
*** NM1 has joined #openstack-swift14:58
*** NM has quit IRC14:58
*** okdas has quit IRC14:59
*** okdas has joined #openstack-swift14:59
*** okdas has joined #openstack-swift14:59
*** blmartin has joined #openstack-swift15:00
*** alejandrito has joined #openstack-swift15:04
*** blmartin has quit IRC15:07
*** amoturi has joined #openstack-swift15:08
*** wbhuber has joined #openstack-swift15:10
hurricanerixy15:10
hurricanerixwhoops, wrong window :)15:10
mahatichrou: yeah, i think so. Or at least improve what is in development_guidelines15:12
acolesmahatic: you're still here! are you +1 on https://review.openstack.org/232572 ? just checking cos you are the author :)15:15
mahaticacoles: I was just notified by jrichli's comment and was wondering if I can +1 it :)15:15
jrichliunit test question: How are the number of nodes determined for ObjectController tests in unit/proxy/controllers/test_obj.py?15:16
mahaticacoles: there you go,  I +1'd it15:16
mahaticthanks for checking15:17
acolesmahatic: thanks15:17
*** NM1 has quit IRC15:20
*** NM has joined #openstack-swift15:20
*** tongli has joined #openstack-swift15:20
*** diogogmt has quit IRC15:32
*** sileht has quit IRC15:32
peterlisak13Hi, I made a patch 241342 to add content-type in swiftclient list of container content. Is there someone who parses that output and can be potentially affected by the change?15:34
patchbotpeterlisak13: https://review.openstack.org/#/c/241342/ - Add content-type in list of container content15:34
peterlisak13I'm deciding between new option like --content-type or adding to existing --long (IMO quite generic and suitable).15:34
*** NM has quit IRC15:36
*** hseipp has left #openstack-swift15:37
*** juzuluag has quit IRC15:38
*** diogogmt has joined #openstack-swift15:38
clayggood morning15:40
wbhuberjrichli: if i understand your question correctly, i'd say the number of nodes is determined by the config file that the unit test picks up15:41
mahaticclayg: good morning (already!)15:43
claygmahatic: acoles: prettysure dict.keys() == [a, b, c] runs the risk that dict.keys() returns [c, a, b]15:43
claygmahatic: acoles: use sets15:43
claygos sorts15:43
*** wbhuber has quit IRC15:44
*** wbhuber has joined #openstack-swift15:44
*** jlhinson has joined #openstack-swift15:44
mahaticclayg: yes, or json?15:45
*** venkat_p has joined #openstack-swift15:47
*** SkyRocknRoll_ has quit IRC15:49
claygmahatic: I think even if d1 == d2 you can't be sure dumps(d1) == dumps(d2)15:49
mahaticclayg: oh I see15:52
*** mzhou has joined #openstack-swift15:53
openstackgerritGanesh Maharaj Mahalingam proposed openstack/swift: Unit tests for account/backend.py  https://review.openstack.org/24061315:55
*** garthb has joined #openstack-swift15:57
openstackgerritBill Huber proposed openstack/swift: ObjectControllers return application errors as 499 on bad read  https://review.openstack.org/23600715:57
wbhuberclayg: ^^ this should be it15:58
*** nadeem has joined #openstack-swift15:58
*** nadeem has quit IRC15:58
*** nadeem has joined #openstack-swift15:59
notmynamegood morning16:00
mahaticgood morning16:02
notmynamejust checking in before I get on the bus16:02
*** trifon has joined #openstack-swift16:13
*** petertr7 is now known as petertr7_away16:14
*** klrmn1 has joined #openstack-swift16:16
*** klrmn1 has quit IRC16:17
*** venkat_p has quit IRC16:18
*** SkyRocknRoll has quit IRC16:25
serverascodeclayg: sorry to bother you again, but yesterday you mentioned "dispersion -v", is that swift-dispersion-report?16:28
*** nadeem has quit IRC16:28
openstackgerritAlistair Coles proposed openstack/swift: Update container on fast-POST  https://review.openstack.org/13538016:29
jrichliwbhuber: thx.  I do see there are factors such as the policy used in the test, and the number can be changed.  Specifically, I am not getting the right number of "nodes" in the node iterator passed to _make_request in controllers/base.py16:29
*** rjaiswal has joined #openstack-swift16:33
*** petertr7_away is now known as petertr716:36
*** bobby2 has quit IRC16:37
*** HenryG has quit IRC16:37
*** bobby2 has joined #openstack-swift16:38
*** HenryG has joined #openstack-swift16:39
*** sileht has joined #openstack-swift16:41
openstackgerritAlistair Coles proposed openstack/swift: Update container on fast-POST  https://review.openstack.org/13538016:44
*** pdardeau has quit IRC16:45
haypohey. is someone available to review my dnspython3 patch? https://review.openstack.org/#/c/217423/ acoles already put his +2 ;)16:47
*** NM has joined #openstack-swift16:50
*** gyee has joined #openstack-swift16:52
*** petertr7 is now known as petertr7_away16:53
*** pdardeau has joined #openstack-swift16:53
*** jmccarthy has quit IRC16:53
claygserverascode: swift-ring-builder <something>.builder dispersion -v16:56
serverascodeclayg: ah ok thanks again16:56
claygswift-dispersion-report is great too - but it's more of a cluster health thing16:57
*** diazjf has quit IRC16:59
tdasilvawbhuber: hello17:03
acolesclayg: i fixed what we discussed earlier but I think you have shone a light on a wider issue - see my comments on patch 135380 :/17:03
patchbotacoles: https://review.openstack.org/#/c/135380/ - Update container on fast-POST17:03
*** trifon has quit IRC17:03
acolesjrichli: ping17:06
haypoacoles: oh cool, cschwede approved the pbr change ;)17:06
acoleshaypo: :)17:06
hayponext step: https://review.openstack.org/#/c/199034/ (fix tox -e py34) which may have to wait for pyeclib 1.117:06
haypoany idea of the status of the pyeclib 1.1 bump?17:06
haypo(i have to go, i will check messages later)17:07
notmynamehaypo: yeah, I'm the blocker there17:07
hayponotmyname: what's the cheat code to unblock you? lol17:07
openstackgerritGanesh Maharaj Mahalingam proposed openstack/swift: Add unit tests for direct_client  https://review.openstack.org/24129117:07
hayponotmyname: no serisouly, what's the status? is 1.1 already in global requirements?17:07
notmynamehaypo: AFAIK, no. there was an upgrade issue. getting it straightened out is in the top few things on my TODO list17:08
notmynamehaypo: my goal is to have it resolved middle of next week17:09
claygI *like* this Jordan Pittier guy - i don't know who he is - but he gets it -> patch 23879917:10
patchbotclayg: https://review.openstack.org/#/c/238799/ - Change schedule priority of daemon/server in config17:10
*** garthb has quit IRC17:10
claygacoles: *no* wider issues - only merging17:10
*** mfalatic has quit IRC17:11
*** ChanServ sets mode: +v timburke17:11
notmynameI'd like to welcome timburke to swiftclient core!17:12
claygwhoot!  welcome!17:12
timburkethanks notmyname!17:13
gmmahacongrats timburke17:13
hroucongrats timburke !17:13
tdasilvatimburke: congrats!17:13
acolestimburke: welcome!17:14
jrichliacoles: ack17:14
acolesjrichli: about the content-type meta encoding - can you track down the version where it *was* being encoded?17:15
acolesjrichli: i do remember seeing the whole header being base64 encoded, but I don't think that is a solution.17:15
hrou^ Yea I thought all content type was base64 encoded at some point ?17:15
jrichliacoles: i will take a look17:15
claygacoles: I also thought about making the suffix hashing use timestamps instead of filenames17:15
acolesclayg: right. that's another way.17:16
acolesclayg: i'm kicking myself so hard i didn't spot this before :/17:16
claygmeh17:16
claygthis isn't a problem in the container listsings because they always merge timestamps down yeah?17:17
claygacoles: I need to imagine how rsync replciation can get itself into this state - because ssync replciation can probably work around it17:18
acolesclayg: no problem there. its just inconsistent filenames.17:18
jrichliacoles hrou: you both are probably right that the whole value was encoded.17:18
hroujrichli, you were trying to find the patch-set # where that was the case ?17:19
claygacoles: yeah I just mean that when containers replicate they always merge - there's no chance to have to same info represented two ways - if you merge things down to a single timestamp (with deltas) there's always a canonical form17:19
*** blmartin has joined #openstack-swift17:20
acolesclayg: when i first looked at the ssync_sender test i thought they were unrealistic starting conditions, but concurrent POST requests could get you two valid meta files.17:20
jrichlihrou: havent done that yet - actually in a meeting now. but i just assume if you both remember that, its probalby right :-)17:20
acolesjrichli: well leave the meeting!!! :P :P17:20
hrouacoles, +1, clearly jrichli, that's the only sensible thing to do ; )17:21
jrichliacoles: its prob bad enough i am dividing my attention ;-)17:21
acolesclayg: plus i got thinking about clusters running a mix of rsync and ssync, or transitioning from one to the other.17:22
*** joeljwright has quit IRC17:22
acolesjrichli: sorry, we'll leave you in peace17:22
jrichliacoles: np, really!17:22
*** rjaiswal has quit IRC17:22
*** rjaiswal has joined #openstack-swift17:23
*** nadeem has joined #openstack-swift17:26
*** rjaiswal has quit IRC17:27
*** rjaiswal has joined #openstack-swift17:29
*** peterlisak13 has quit IRC17:29
*** subscope has joined #openstack-swift17:30
openstackgerritMerged openstack/swift: Guess content-type on PUT  https://review.openstack.org/23257217:32
acoleswoohoo mahatic ^^17:33
*** diazjf has joined #openstack-swift17:37
*** jordanP has quit IRC17:37
jrichliyay!17:38
acolesnotmyname: i'll be around less next week, jury service.17:40
*** rledisez has quit IRC17:41
notmynameacoles: right. thanks for the reminder17:41
notmynameI hope you don't get picked :-)17:41
acolesclayg: ^^ if you have any thoughts please leave on gerrit, i may miss stuff in scrollback17:41
acolesnotmyname: i read through the docs but there was no section on being 'de-selected'. will have to wait and see how it works.17:42
notmynameI'm goign to be interested to hear about your experience and compare it to my own17:42
hrouacoles, at least in Canada both lawyers (on both sides) along with the judge have the right to refuse a juror for whatever reason, and if that happens you've done your service.17:43
hrouYou just need to be undesirable to one of the sides, which can mean many different things depending on the context : )17:43
notmynamesame here in the US17:43
acoleshrou: i've always tried to make "being undesirable" one of my strengths ;D17:44
notmynameeg like the lady who said she couldn't give an impartial judgement based on the facts presented because she "had certain views on race"17:44
acolesnotmyname: yeah, i noted that line.17:44
*** mfalatic has joined #openstack-swift17:44
notmynameor the other lady who was getting "psychic impressions" telling her to go one way or another17:45
notmyname(also, san francisco is weird ;-)17:45
hrouacoles, so just be your self ; - ) jk  - its not being "unlikeable" though, usually its some sort of perceived bias17:45
hrouacoles, wait I'm not implying you're "unlikeable" : )17:45
acoleshrou: stop digging man.. :)17:45
hrounotmyname, haha its funny in Canada they're good at catching people who just say something crazy to get out of it, you need to be somewhat genuine : )17:46
notmynamehrou: I live in the city where "is that a costume or do you just wear that normally" is a totally valid question17:46
*** arnox has quit IRC17:47
*** arnox has joined #openstack-swift17:48
hrounotmyname, I really really want to visit one day, its on my list;  Mind you there were parts of Tokyo I saw that I imagine people may ask the same question : )17:48
blmartinwhat like batman costumes?17:48
notmynameblmartin: with all the vigilante-justice batmans around, crime is low17:49
*** arnox has quit IRC17:49
blmartinbut are they the heros you deserver?17:49
notmyname(seriously, though, crime isn't low, so there maybe should be more batmans around)17:49
notmynamelol17:49
blmartindeserve*17:49
*** garthb has joined #openstack-swift17:50
*** zhill has joined #openstack-swift17:51
*** petertr7_away is now known as petertr717:53
*** geaaru has quit IRC17:53
*** jrichli has quit IRC17:54
*** jistr has quit IRC17:54
*** peterlisak13 has joined #openstack-swift17:56
notmynamesummit recap email sent to the dev mailing list17:57
*** peterlisak13 has quit IRC18:03
*** klrmn1 has joined #openstack-swift18:03
*** acoles is now known as acoles_18:05
*** wbhuber_ has joined #openstack-swift18:07
*** wbhuber_ has quit IRC18:07
*** wbhuber_ has joined #openstack-swift18:07
pdardeaunotmyname: i'll be around very little next 3 weeks (training)18:08
*** diazjf has quit IRC18:09
*** wbhuber has quit IRC18:10
haypotimburke: "I'd like to welcome timburke to swiftclient core!" oh congrats!18:11
timburkehaypo: thanks! also, thanks gmmaha, hrou, tdasilva, and acoles_!18:13
*** pdardeau has quit IRC18:21
*** pdardeau has joined #openstack-swift18:22
notmynamepdardeau: you're with the intel/rax thing right?18:26
openstackgerritTim Burke proposed openstack/python-swiftclient: Add --decode-content option  https://review.openstack.org/18495718:31
*** mplex has left #openstack-swift18:37
*** proteusguy_ has quit IRC18:37
pdardeaunotmyname: yes, that's correct18:47
*** proteusguy_ has joined #openstack-swift18:49
*** janonymous has joined #openstack-swift18:52
tdasilvathere's something about Fridays and #openstack-swift channel18:52
tdasilvapretty funny stuff18:52
*** diazjf has joined #openstack-swift18:55
*** jrichli has joined #openstack-swift18:56
gmmahanotmyname: are there plans to get openstackclient equipped to be the primary away frm the swift client?18:57
*** wbhuber has joined #openstack-swift18:58
*** diazjf has quit IRC19:00
*** wbhuber_ has quit IRC19:00
* notmyname is back from meeting19:04
notmynamepdardeau: are they making you go to rookie-o?19:05
notmynamegmmaha: I'm having some trouble parsing that question19:05
claygacoles_: so do you have a failing test in place for the thing you're imaging for inconsistent dir listings?19:06
pdardeaunotmyname: yeah, that's the one19:08
* notmyname wonders what RAX rookie-o is like without sugar bear19:09
*** aix has quit IRC19:15
mwheckmannnotmyname: clayg: the workaround for my broken rings worked beautifully. Thanks again for your help on that!19:21
notmynameIIRC I ran away to a meeting and clayg actually helped ;-)19:22
mwheckmannsure, but you still stepped up to help while you could.19:23
*** mahatic has quit IRC19:25
claygacoles_: oh, it looks like maybe https://gist.github.com/alistairncoles/7fa16e567cbacd12a7a6 is the failing test I was looking for19:26
claygnotmyname:  the starred list is huge already - and so many are -1'd :\19:27
notmynameclayg: what's huge is the list of "stuff that just needs one more +2"19:29
notmynameyeah, the issue with the starred list is if *I* want to track something, you end up seeing it too ;-)19:31
notmynameeg the stable/kilo one, the testr one, and the pyeclib one19:31
*** openstackstatus has joined #openstack-swift19:36
*** ChanServ sets mode: +v openstackstatus19:36
-openstackstatus- NOTICE: Gerrit will be offline at 20:00-20:15 UTC today (starting 20 minutes from now) for scheduled project rename maintenance19:41
gmmahanotmyname: i meant to ask whether we are shifting focus to make the openstackclient the primary client for swift or we support both for long19:41
notmynamegmmaha: ah ok19:41
notmynamegmmaha: we tried to shift focus. and we just ended up not focusing on anything19:41
gmmaha:D19:41
notmynamegmmaha: so the current plan is that we will still improve python-swiftclient19:42
openstackgerritMerged openstack/swift: On py3, use dnspython3 dependency, not dnspython  https://review.openstack.org/21742319:42
notmynamegmmaha: and other work will happen in openstackclient (separately from work on swiftclient)19:42
notmynamegmmaha: with the expectation that both will likely be a thing used for quite some time19:42
gmmahanotmyname: aah cool..19:42
gmmahayeah the fade over being long is what i thought19:43
gmmahathanks.. i was going to start writing some test coverage on the swiftclient and wanted to check if at all i should be doing that19:43
claygoh nice - i forgot about needs final approval - it's been so long since I made it past priority reviews I forgot what else was down there!19:43
notmynamegmmaha: awesome! yes, you should definitely do that! :-)19:44
gmmahanotmyname: :) for sure.. thanks19:44
claygnotmyname: bah - most of them are py319:44
notmynamebriancline: if you could take patch 241571 and run your rings through it, that would be great!19:44
patchbotnotmyname: https://review.openstack.org/#/c/241571/ - Put part-replicas where they go19:44
notmynamehurricanerix: redbo: ^ same for the RAX rings19:45
notmynamekota_: ^ and NTT19:45
notmynamedonagh: ^ and HP19:45
claygnotmyname: can will single core +A py3 changes?  I figure if cschwede or acoles_ or torgomatic_ or kota_ are going to take the time to look them over we may as well just get 'em in?19:45
clayg... maybe that's insane19:45
notmynameclayg: the rule's always been "use your judgement" :-)19:45
hurricanerixnotmyname: lol, too bad there isn't a @everyone (or maybe there is, i only know enough irc to get by) =)19:46
notmynameIMO small py3 stuff is probably just fine for a single core to +A19:46
notmynamehurricanerix: yeah, what do you think this is? slack?!19:46
hurricanerixhehe19:46
claygnotmyname: yeah but everyone's judgement normally says that the risk of merging stomething stupid isn't worth the cost of just waiting for another core to see it19:46
notmynameclayg: which is why that's a safe rule ;-)19:46
* notmyname wonders how many people in here end up using slack too19:47
clayg... but with stuff like doc typo fixes we've had to socialize the idea that the cost is higher than you might think when the risk is so low19:47
*** daemontool has quit IRC19:47
claygnotmyname: I aggree we should single core +A "simple" py3 fixups - I'd like to bring that up next week19:48
nottrobinhurricanerix: everyone may not be official, but my IRC is setup to ping me when someone uses it =)19:49
notmynameclayg: yeah, but it's ok if you start doing that now and then ask for "permission" later19:49
claygnotmyname: my avoidance of py3 changes is purposeful - hence wanting people to merge them faster to get them out of my way19:50
*** peterlisak13 has joined #openstack-swift19:52
*** peterlisak13 has quit IRC19:57
pdardeaunotmyname: on the topic of py3, is there a recommended approach for individual developers to easily shift across py2/py3? (without causing too many headaches)19:59
mwheckmannI think I found another small bug in the ring builder: For some reason, I can't use "--id" as a search key for set_info when the id value I want to use is '0'. I works for id's larger than 0.20:00
mwheckmannI had to use another search key as a workaround.20:00
notmynamepdardeau: not that I know20:00
mwheckmannThis is with 2.5.0.20:00
notmynamemwheckmann: that sounds familiar. as if I've seen a patch recently for that20:02
mwheckmannok. Anyway, it's easily worked around.20:02
mwheckmannI also noticed that the use of '--id' is not documented in the help output for the ring builder.20:03
-openstackstatus- NOTICE: Gerrit is offline until 20:15 UTC today for scheduled project rename maintenance20:04
*** ChanServ changes topic to "Gerrit is offline until 20:15 UTC today for scheduled project rename maintenance"20:04
notmynamewhelp. guess it's time for lunch then20:04
*** diazjf has joined #openstack-swift20:06
claygmwheckmann: you get "Invalid <search-value>: '--id'"20:07
mwheckmannyup.20:07
*** jroll is now known as tjroll20:07
claygmwheckmann: could I trick you into filing a bug that has something like that in the title on https://bugs.launchpad.net/swift/+filebug20:08
mwheckmannsure.20:09
claygthe exact syntax of the commands you ran with the observed output and the expected output would be super ideal20:09
claygYES!20:09
claygthanks!20:09
mwheckmannNP20:09
mwheckmannclayg: https://bugs.launchpad.net/swift/+bug/151395520:19
openstackLaunchpad bug 1513955 in OpenStack Object Storage (swift) ""swift-ring-builder set_info" command doesn't recognize 0 as a search value when "--id" is used as a key" [Undecided,New]20:19
*** janonymous has quit IRC20:19
jlhinsonHas anyone else been having trouble with the unit tests?20:25
jlhinsonhttp://paste.openstack.org/show/478214/20:25
jlhinsonupgrading six to 1.10.0 solved my problem20:25
gmmahajlhinson: think a colleague of mine saw that error as well.. He had to do a upgrade install ( think six package) to get past it20:27
jlhinsonI wasn't sure if we needed to update requirements.txt, or if it was just my local copy of six that was bad20:27
*** tongli has quit IRC20:33
*** ChanServ changes topic to "Review Dashboard: https://goo.gl/iLt6Ld | Summit etherpads: https://wiki.openstack.org/wiki/Design_Summit/Mitaka/Etherpads#Swift | Summit schedule: http://mitakadesignsummit.sched.org/type/swift | Logs: http://eavesdrop.openstack.org/irclogs/%23openstack-swift/"20:37
*** daemontool has joined #openstack-swift20:52
jlhinsonI'm also unable to parse requirements.txt now...20:53
*** lpabon has quit IRC20:55
claygmwheckmann: that's awesome!20:57
notmynamejlhinson: haven't seen that yet. I've been messing with pip install -r requirements to do the pyeclib updates. seems to be working for me20:58
notmynamejlhinson: this is on master?20:58
jlhinsonyep20:59
jlhinsonjrichli ran into the same problem20:59
notmynamefinishing a test run now. if it goes well, I'll look at that in  few minutes21:00
jlhinsonsounds good21:00
*** mzhou_ has joined #openstack-swift21:01
*** openstackgerrit has quit IRC21:01
*** openstackgerrit has joined #openstack-swift21:01
brianclinenotmyname: having a look at the placement patch. do you just want me to try a rebalance?21:02
claygbriancline: that'd be something!21:03
*** mzhou has quit IRC21:03
*** mzhou_ is now known as mzhou21:03
claygbriancline: if you think the results are "better" or "no worse" or "worse" you should put that on there too21:03
claygbriancline: if you got *really* crazy you could try moving some devices/weights around and see if the results make sense - or even compare the results of the same operations on master.21:04
claygbriancline: experimental observations + analysis (from operataional perspective/experience) would be at least as helpful as going over the code changes line by line and offering nits.21:05
brianclineclayg: ok, yeah, we're about to make ring changes and have recently been generating stats about what the movement looks like each time. can run the same scenario for the next one using this version to see how much those stats change21:06
*** NM has quit IRC21:07
clayg@everyone: *but* - for those who feel more comfortable going over the code/test chnages and offering nits - those are welcome too!21:07
notmynamebriancline: thanks :-)21:08
* clayg considering reverse listings, concurrent gets, and more fast-POST for this afternoon21:09
*** petertr7 is now known as petertr7_away21:14
*** petertr7_away is now known as petertr721:15
*** mzhou has quit IRC21:19
*** mzhou has joined #openstack-swift21:20
notmynamejlhinson: I'm not seeing anything21:36
notmynamebut I may have inadvertently gotten past it with an upgrade at some point21:36
*** subscope has quit IRC21:39
jlhinsonI was wrong about the version of six causing a problem21:39
jlhinsonbut I am still having an issue parsing requirements.txt21:39
claygsudo pip install --upgrade pip21:40
claygthe new bugs are always better than the old bugs21:40
notmynameanyone else getting "WARNING: default min_part_hours may not match the value in the lost builder." printed on unit test runs?21:41
claygnotmyname: i see that sometimes!21:41
jlhinsonnotmyname: I've seen that before21:41
pdardeaunotmyname: yes21:42
jlhinsonclay: lol, trying that now21:42
claygnotmyname:  you gunna track it down and square it for us?21:42
pdardeaunotmyname: that's because of calls to stderr.write21:42
claygpdardeau: better mock that shit21:42
notmynameclayg: yeah, maybe after I figure out this other test failure I'm seeing ;-)21:42
pdardeaui wrote up a bug on it last week21:42
notmynamesee? pdardeau is already all over it :-)21:42
clayg*my* bad21:43
notmynamefeels nice being back in a terminal and code editor interface instead of presentation software and emails ;-)21:43
clayglol @ PTL!21:43
notmyname"This is code! I *know* this"21:44
notmynamehttps://www.youtube.com/watch?v=dFUlAQZB9Ng21:45
claygerror in setup command: 'install_requires' must be a string or list of strings21:45
clayg^ this is the failing?21:45
*** jerrygb has quit IRC21:46
*** jerrygb has joined #openstack-swift21:47
haypo[5~[5~[6~21:49
haypo2.21:49
haypooops, sorry21:49
clayghaypo: happens to me all the time21:49
timburkenotmyname: i think there may be a reason you run unopposed...21:49
notmynamelol21:49
claygtimburke: it's because he's so funny and charming21:49
notmynameclayg: it's because I make you nice tshirts21:50
timburkeclayg: well that's *also* true. but *you're* funny and charming, too, so watch out!21:50
haypoclayg: i'm using a PLC adapter for my LAN and it became very common that I loose the internet connection :-(21:50
haypoclayg: i was trying to kill the SSH connection when IRC just came back /o\ fail21:51
* clayg thinks back to one of the working sessions when notmyname (rightfuly frustrated by the devolution of some topic to bike sheading) went on a tear about us needed to come back to the problem at hand and make progress ( and in the middle he slipped in something about be tired cranky and hungry or something)21:51
haypo"A PLC connection has many advantages to a wireless connection, however the quality of the connection will still depend on the quality of the domestic electrical system. Improper wiring and circuit breakers in between the connected cables can negatively affect the performance, and can cause connection interruptions."21:51
notmynamethat was fun. good times21:51
*** jerrygb has quit IRC21:51
clayggood times21:52
claygthis unable to parse requirements.txt - NOT good times - wtf is going on?21:52
claygJESUS!  I'M ON PIP *SEVEN*21:52
claygwhat are you guys doing?!21:52
claygyou know what - backwards compatibility is hard - let's just *ALWAYS* increment the major version number21:53
clayg*washes hands*21:53
*** peterlisak13 has joined #openstack-swift21:53
haypoclayg: i really like the transparent binary wheel cache introduced in pip 6, tox is much faster with that21:53
clayghaypo: sounds fancy21:53
claygi probably don't like it21:53
notmynametimburke: clayg is being funny and charming again ;-)21:54
haypoclayg: my pbr requirement was merged into swift, but i don't see how it's related to pip in your case (i guess that you are talking about something different?)21:54
claygfunny is probably debable - but it's definately not charming - I like to put it all out there so others can vent through me vicariously and only *one* of us has to come across as an a#$%^&ole21:55
claygExpected ',' or end-of-list in dnspython>=1.12.0;python_version<'3.0' at ;python_version<'3.0'21:55
clayg^ doubt it's *unrelated*21:56
*** alejandrito has quit IRC21:56
timburkeclayg: yep, need to upgrade one or more of pip, setuptools, and pbr21:56
clayglooks to be my favorite :)21:56
notmynamehaypo: what pbr patch did you have?21:56
openstackgerritMerged openstack/swift: bug/1270114. Missing documentation for Bulk Middleware.  https://review.openstack.org/23268821:57
*** mwheckmann has quit IRC21:57
claygI'm going to add `pip install --upgrade setuptools pbr pip` to my .bashrc21:57
hayponotmyname: i'm trying to always get the latest versions of pbr, tox and pip :) for pbr, it's simply not installed on my system21:57
claygoh i'm sorry - were trying to get some work done!?21:57
*** peterlisak13 has quit IRC21:58
hayponotmyname: it's only installed inside tox venvs21:58
*** amoturi has quit IRC21:58
haypoclayg: i can try to help you, but i don't understand your issue. what are you doing, what is the error message?21:58
haypoclayg: acoles_ had issues because he had an old version of setuptools and/or pbr, sorry i don't recall and i was unable to reproduce his issue :-(21:59
hayporight now on my fedora 23, i have setuptools (18.2), tox 1.8, pip 7.1.2, (pbr is not installed)21:59
clayghaypo: `pip install --upgrade pbr` was the fix for me22:00
notmynameI'm listening to someone give an intro to swift talk (yes, while I'm looking at this test failure). first, it's probably a bad idea to talk about the CAP theorem in an intro swift talk. second, instead of "eventually consistent" I'm going to start saying "highly available"22:00
haypoclayg: i guess that you are not using tox, but setup.py directly?22:00
haypoclayg: because tox should now take care of the pbr version, i added "pbr>=1.6" in requirements.txt22:00
claygwhat does tox have to do with anything?22:01
haypoclayg: usually, i use tox to run tests, i never install anything on my system22:01
claygTHEN HOW DO YOU KNOW IT WORKS22:02
clayglol22:02
notmynameclayg: we've tried nothing, and it works every time22:03
clayglook - i'm up and running again - in a few minutes someone will try to test out branch that's been rebased on master and thye'll have the same problem I did - we'll all say - "oh yeah someone made something better, everyone is broken until everything is upgrade" and they'll go back to work - it's fine22:03
haypoclayg: i expected that setup.py and tox have the same behaviour, but it looks like setup.py is unable to upgrade itself pbr :-/22:04
claygthen later we'll all have to *package* this mess and curse again for a little while and once we get it working we'll forget that pain too and move on22:04
claygit's great22:04
notmynameah. that's why I'm not seeing these problems. I didn't have the very latest code!22:04
claygnotmyname: "oh yeah someone made something better, everyone is broken until everything is upgrade"22:04
*** petertr7 is now known as petertr7_away22:05
notmynameso wait. why did we add pbr to requirements.txt?!? we spent a *lot* of effort on making sure it was a build-only dependency22:05
claygnotmyname: who cares22:05
claygnotmyname: it's over22:05
claygnotmyname: we lost22:05
claygnotmyname: all of python lost22:06
claygnotmyname: just package pbr every other week, and pip install -e .22:06
hayponotmyname: "why did we add pbr to requirements.txt?!?" i'm not sure that pbr is required at runtime, but i added pbr>=1.6 to ensure that we have at least pbr 1.0 to support environment markers22:08
notmynamehaypo: wasn't that handled in the setup.py stanza?22:08
notmynamethe cap on the version there was removed a long time ago so it would get the latest22:09
*** jerrygb has joined #openstack-swift22:09
hayponotmyname: if you run "tox -e update ../swift", setup.py is updated to add "pbr>=1.8"22:10
hayponotmyname: but acoles_ got issues with this change, so i tried to remove this requirements to fix his usecase22:10
claygnotmyname: you can try to dig into it if you want, but eventually you'll find out no one pushing all this pain out onto the entire python ecosystem *cares* - you didn't blow away your entire deployment and install everything fresh from the very latest version?! wow.22:10
*** jerrygb_ has joined #openstack-swift22:10
notmynameand it looks like probe tests in the community cluster failed too22:11
claygLOL22:11
notmynamehaypo: what sort of meta-deployment magic is this? we're supposed to run deployment code to generate/edit deployment files?22:11
notmynamewhat happened to explicit is better than implicit?22:11
haypoif i recall correctly, putting a requirements in setup.py is not enough. but sorry, i don't recall all minor details of python packaging. for me, it's just a big mess22:12
* clayg remembers when all we hade was setuptools0.6c11 and we *made due*22:13
*** jerrygb has quit IRC22:14
hayponotmyname: sorry, i don't understand your point. my goal is to install dnspython3 on python 3 and dnspython on python 2. the best way to do that (for many reasons) is to use environment markers22:14
hayponotmyname: so somehow, we need to ensure that everything used to package and install swift support environment markers22:14
hayponotmyname: maybe pbr>=1.6 in requirements.txt is not the best way to do that, but i recall vaguely some corner cases with pbr not explicitly required in requirements.txt22:15
haypomy expert for pbr is lifeless who understand these things much better than me :)22:15
clayg:)22:16
haypoi hate pbr, but i don't know anything better, so...22:16
claygonce openstack took over pip and setuptools didn't the *need* for pbr to work around upstream issues decrease dramatically?  why is it still a thing?22:18
haypoclayg: python packaging evolves very slowy, i mean it takes years to fix issues22:20
haypoclayg: but IMHO pip made huge progress last months, it's really impressive22:20
notmynamenew version of something complains about /tmp being writable22:20
*** vinsh has quit IRC22:21
*** vinsh has joined #openstack-swift22:22
blmartinring balancing question: if I add many devices to a ring and rebalance, is it expected and natural that my partitions may not be equally distributed across all devices?22:23
haypoclayg, notmyname : so do you think that we need to change something for pbr? or is it ok?22:23
blmartinor is there a doc I need to read22:23
notmynamehaypo: dealing with another patch, I ended up upgrading my saio  before I got this patch, so it's hard for me to explicitly test the upgrade path right now22:26
*** vinsh has quit IRC22:26
*** August1914 has joined #openstack-swift22:26
timburkefwiw on the env marker stuff, there was a bug for something similar in swiftclient... https://bugs.launchpad.net/python-swiftclient/+bug/147658522:27
openstackLaunchpad bug 1476585 in python-swiftclient "Error when installing python-swiftclient release version 2.5.0 : error in setup command: 'tests_require' must be a string or list of strings containing valid project/version requirement specifiers" [Medium,Fix released] - Assigned to Christian Schwede (cschwede)22:27
timburke(not that we can use the same solution - remove the need for env markers - here, though)22:27
*** rjaiswal has quit IRC22:27
hayponotmyname: ok. don't hesitate to come back to me if you have issues. according to acoles_ & clayg, upgrading pbr fixes the issue22:27
notmynamehaypo: I think my frustration is that there is an issue. not that it's fixable22:28
notmynametimburke: yeah, i thought we had environ markers somewhere else22:29
openstackgerritBill Huber proposed openstack/swift: ObjectControllers return application errors as 499 on bad read  https://review.openstack.org/23600722:29
wbhubertdasilva: your comments tended to ^^22:29
haypotimburke: it looks like the fix was to... remove environment markers :-)22:30
*** dustins has quit IRC22:33
torgomatic_upgrading pbr is never fast for me22:34
torgomatic_it always drags in newer dependencies, and then stuff breaks and I have to figure out why, and I sometimes just end up rebuilding my SAIO VM22:35
claygtorgomatic_: you didn't blow away your entire deployment and install everything fresh from the very latest version?! wow.22:36
torgomatic_clayg: and I'm not even using docker. I think that makes me a dinosaur.22:37
claygRAWARRRR22:37
* clayg has choosen reverse listings22:39
claygstep #0 create a container with 25K objects22:40
*** blmartin has quit IRC22:50
*** jlhinson has quit IRC22:55
*** nadeem has quit IRC23:02
notmynametorgomatic_: we've got simplejson in requirements.txt. can that be removed now?23:04
*** haypo has left #openstack-swift23:04
torgomatic_notmyname: nope; I still get a bunch of hits from `git grep simplejson`23:04
notmynametorgomatic_: oh you haven't fixed all those yet? ;-)23:04
notmynameok yeah. I see them too. should have looked there first :-)23:05
torgomatic_it's subtle; each change requires some careful thought23:05
notmynamejust teasing :-)23:05
timburkenotmyname: torgomatic_: it's that what zackmdavis_'s patch 240596 is for?23:06
patchbottimburke: https://review.openstack.org/#/c/240596/ - remove remaining simplejson uses23:06
*** diazjf has quit IRC23:09
*** hrou has quit IRC23:12
*** wbhuber has quit IRC23:18
*** pdardeau has quit IRC23:33
openstackgerritMerged openstack/swift: Re-organise ssync tests  https://review.openstack.org/22019823:43
*** jerrygb_ has quit IRC23:56

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