Thursday, 2015-11-05

*** haomaiwa_ has quit IRC00:01
*** zhill has quit IRC00:01
*** haomaiwang has joined #openstack-swift00:01
*** okdas has quit IRC00:04
*** eranrom has joined #openstack-swift00:09
*** lpabon has joined #openstack-swift00:20
*** jrichli has joined #openstack-swift00:21
*** wbhuber_ has quit IRC00:24
*** wbhuber has joined #openstack-swift00:25
*** okdas has joined #openstack-swift00:27
*** okdas has joined #openstack-swift00:27
*** wbhuber has quit IRC00:29
*** tongli has quit IRC00:30
*** jerrygb has joined #openstack-swift00:31
*** jerrygb has quit IRC00:32
*** eranrom has quit IRC00:33
claygwhoa - did you know that argparse automatically lets you use short aliases for arguments?  I added an option to ring-check for --save-builder and accidently envoked it with --save but it totally *works*00:40
*** lpabon has quit IRC00:40
klrmn1argparse is pretty smart. it often does what you mean it to do, even when you didn't say it right00:41
*** m_kazuhiro has joined #openstack-swift00:41
*** diogogmt has quit IRC00:42
*** haomaiwang has quit IRC00:45
*** sileht has quit IRC00:48
*** willsama has joined #openstack-swift00:52
*** gyee has quit IRC00:59
*** km has joined #openstack-swift01:02
*** km is now known as Guest3314401:02
*** Guest33988 has quit IRC01:03
jrichliquestion: if there is now only one key, can we still have the keymaster interface allow for 3 different keys: object, container, and account levels?01:04
jrichlithe encrypter and decrypter middleware use the container key to encrypt what will be in the container listing01:04
jrichliif we take that away, it means that you cannot plug-in a keymaster with more keys01:05
notmynamejrichli: I could imagine container_key = sha1_hmac(container_name, cluster_key) or something like that. not sure if an hmac would actually be needed, but my point is the ability to make a contianer key from the cluster key01:05
jrichlioh, right01:06
notmynameprobably would mix in the account key at some point too01:06
jrichlii am sorry.  getting mixed up01:06
notmynamecontainer_key = cluster_key + account_key  # or something01:06
jrichliof course01:06
notmynamecontainer_key = cluster_key + account_name + container_name  # or something01:06
notmynamethat's what I meant ;-)01:06
*** hrou has joined #openstack-swift01:07
jrichliso, I am starting to wonder why one cluster key in config file is better than what the trivial_keymaster does now. maybe i am missing something simple ...01:10
jrichlioh, nevermind01:11
jrichliit was silly.01:11
jrichliok, i am gonna stop talking in channel now01:11
hrouNoo don't stop ; )  Well it was one key for every cluster in the entire world ; )  That'd be cool for us though.01:13
jrichlihrou: seriously, lets not talk about my silliness from tonight01:13
jrichlihrou: i am just clearly having an air-head sort of night01:13
hroujrichli, oh my bouncer died a day or so ago, did I miss other entertaining comments ? : )01:14
*** blmartin has quit IRC01:15
jrichlihrou: just 2 silly thoughts.01:15
*** willsama has quit IRC01:17
pchng_jrichli: I welcome your silly thoughts, since I am still learning how different keys are derived in Swift :)01:18
jrichliwell, technically, it wouldn't be one key for every cluster, just derived (predictable) from the path name.01:18
pchng_btw, thank you for the welcome yesterday hrou :)01:19
jrichlibut we will change that to have an actual SECRET from the config file01:19
hrouYea jrichli  is right, we had an older key master that had just one hard coded yet01:19
jrichlimaybe some wrapping scheme later at some level, but first patch will not have wrapping.01:19
*** pchng_ is now known as pchng01:19
hroupchng, oh anytime !  I think I learned your desk is across from mine ; )01:20
*** badari has quit IRC01:21
pchnghrou: Yep, we're both in A2!01:23
*** badari has joined #openstack-swift01:23
pchngPossibly naive/noob question: I was looking at the fast-POST functionality, and was wondering why POST was used only for create/update object metadata and PUT was used to create or replace object data and metadata?01:31
*** diogogmt has joined #openstack-swift01:33
claygpchng: well in REST the PUT is a pretty good way to describe "here is the whole version of the resource that belongs at this uri"01:35
hroupchng, there are no silly questions ! (Only jrichli asks those ; ) jk, we showed her question wasn't silly at all):    More of a http PUT generally is the entire object and POST to update it (and in swift its metadata per say)01:36
claygpchng: there's not really a good verb for "modify the resource a just a little bit" - but we do have POST - which means "i have no idea wft is even going on with this verb - it's anything the app wants to do"01:36
claygso that seemed like we could make it work for "update metadata"01:36
*** hezhiqiang has joined #openstack-swift01:37
pchngclayg, hrou: Thanks for the explanations. I've read various arguments between PUT vs POST and the exact semantics so this makes sense01:37
*** janonymous__ has joined #openstack-swift01:37
hrouYea you could in theory have defined an API that uses POST instead really, its more of a swift specific implementation but you'll find many http api's are quite similar01:38
pchngThe documentation shows a clear delineation between what PUT and POST does so there's no ambiguity, was just wondering why01:38
*** jlhinson has quit IRC01:40
*** yuan has quit IRC01:40
*** yuan has joined #openstack-swift01:40
*** km has joined #openstack-swift01:41
*** Guest33144 has quit IRC01:41
*** km is now known as Guest9546501:41
*** eranrom has joined #openstack-swift01:58
*** Guest95465 has quit IRC01:59
*** garthb has quit IRC02:00
*** breitz1 has joined #openstack-swift02:08
*** breitz has quit IRC02:11
*** breitz2 has joined #openstack-swift02:11
*** klrmn1 has quit IRC02:12
*** breitz1 has quit IRC02:13
*** janonymous__ has quit IRC02:14
*** wbhuber has joined #openstack-swift02:17
*** dmorita has quit IRC02:17
*** badari has quit IRC02:29
*** badari has joined #openstack-swift02:46
*** haomaiwang has joined #openstack-swift02:55
*** haomaiwang has quit IRC03:00
*** rohit_ has quit IRC03:04
*** badari has quit IRC03:10
*** haomaiwang has joined #openstack-swift03:19
*** jrichli has quit IRC03:30
*** haomaiwang has quit IRC03:48
*** wbhuber has quit IRC04:07
*** wbhuber has joined #openstack-swift04:07
*** aagrawal has joined #openstack-swift04:09
*** SkyRocknRoll has joined #openstack-swift04:11
*** wbhuber has quit IRC04:11
*** badari has joined #openstack-swift04:23
*** links has joined #openstack-swift04:26
*** janonymous has quit IRC04:27
*** mahatic has joined #openstack-swift04:27
*** haomaiwa_ has joined #openstack-swift04:32
*** hezhiqiang has quit IRC04:42
*** sileht has joined #openstack-swift04:44
*** janonymous has joined #openstack-swift04:59
*** haomaiwa_ has quit IRC05:01
*** haomaiwa_ has joined #openstack-swift05:01
*** hezhiqiang has joined #openstack-swift05:08
*** badari has quit IRC05:31
*** km has joined #openstack-swift05:32
*** km is now known as Guest6038305:33
*** haomaiwa_ has quit IRC05:44
*** venkat_p has joined #openstack-swift06:19
*** sileht has quit IRC06:25
*** sileht has joined #openstack-swift06:42
openstackgerritHisashi Osanai proposed openstack/swift: Add functional test for access control (RBAC) with Keystone  https://review.openstack.org/20241106:48
*** hrou has quit IRC06:57
*** asettle has quit IRC06:59
*** pchng_ has joined #openstack-swift06:59
*** pchng has quit IRC07:03
*** mac_ified has quit IRC07:05
*** haomaiwang has joined #openstack-swift07:11
*** sileht has quit IRC07:15
*** eranrom has quit IRC07:17
*** eranrom has joined #openstack-swift07:20
*** ppai has joined #openstack-swift07:22
*** aagrawal has quit IRC07:32
*** aagrawal has joined #openstack-swift07:32
*** hseipp has joined #openstack-swift07:50
*** hseipp has quit IRC07:50
*** hseipp has joined #openstack-swift07:50
*** zigo has quit IRC07:53
*** jamielennox is now known as jamielennox|away07:54
*** jamielennox|away is now known as jamielennox07:54
*** zigo has joined #openstack-swift07:56
*** jamielennox is now known as jamielennox|away07:57
*** sileht has joined #openstack-swift07:59
*** haomaiwang has quit IRC08:01
*** haomaiwang has joined #openstack-swift08:01
*** hseipp has quit IRC08:01
*** hseipp has joined #openstack-swift08:02
*** aagrawal has quit IRC08:10
*** janonymous has quit IRC08:14
*** openstackgerrit has quit IRC08:16
*** openstackgerrit has joined #openstack-swift08:16
*** rledisez has joined #openstack-swift08:17
*** peterlisak has joined #openstack-swift08:24
*** mfalatic has quit IRC08:27
*** mfalatic has joined #openstack-swift08:28
*** openstack has joined #openstack-swift08:35
*** jordanP has joined #openstack-swift08:39
*** ho has quit IRC08:43
*** venkat_p has quit IRC08:44
*** haomaiwang has quit IRC09:01
*** venkat_p has joined #openstack-swift09:01
*** haomaiwa_ has joined #openstack-swift09:07
*** janonymous has joined #openstack-swift09:08
*** acoles_ is now known as acoles09:16
acolesgood morning09:20
acolesho: looks like that latest version of patch 202411 has all the scenarios added in one patch?09:22
patchbotacoles: https://review.openstack.org/#/c/202411/ - Add functional test for access control (RBAC) with...09:22
*** jmccarthy has joined #openstack-swift09:23
*** jistr has joined #openstack-swift09:24
acolesmahatic: hi. you here?09:35
mahaticacoles: hello, yes09:35
acolesmahatic: did you have any more comments on patch 20331009:35
patchbotacoles: https://review.openstack.org/#/c/203310/ - Encrypting/Decrypting object metadata09:35
*** venkat_p has quit IRC09:36
acolesjust wondering if you are looking at it still?09:36
mahaticacoles: ah, could you give me a few mins? Looking right away09:37
acolesmahatic: i can give you a few hours :)09:37
acolesmahatic: no rush, but if we can merge it this week that would be good.09:38
mahaticacoles: :D cool! I was trying to update the spec actually, (with the content-type crypto metadata change) but found a few more things that maybe need to be corrected. Will push something and put comments i think09:38
mahaticacoles: yes sure, I just want to take a look mainly at the encrypter/decrypter changes09:38
acolesok thanks09:39
*** hseipp has quit IRC09:41
*** hseipp has joined #openstack-swift09:43
*** haomaiwa_ has quit IRC09:46
*** haomaiwang has joined #openstack-swift09:46
mahaticacoles: done. Also, we're not using this anywhere anymore right? -> X-Object-Sysmeta-Crypto-Content-Type09:52
mahaticI like the idea of appending etag crypto metadata to the header as well. Don't see why we shouldn't. Make it simpler and also avoids that conflict in question09:55
mahaticMakes*09:55
*** hezhiqiang has quit IRC09:57
*** haomaiwang has quit IRC10:01
*** haomaiwang has joined #openstack-swift10:01
*** jamielennox|away is now known as jamielennox10:01
*** haomaiwang has quit IRC10:04
*** aagrawal has joined #openstack-swift10:06
*** zaitcev has quit IRC10:23
openstackgerritCatherine Northcott proposed openstack/swift: Add support for storage policies to have more than one name  https://review.openstack.org/24197810:38
*** jerrygb has joined #openstack-swift10:58
*** Guest60383 has quit IRC11:04
*** aagrawal has quit IRC11:16
*** aagrawal has joined #openstack-swift11:17
*** venkat_p has joined #openstack-swift11:20
*** hezhiqiang has joined #openstack-swift11:24
venkat_pHi all11:28
venkat_pplease review this change11:28
venkat_phttps://review.openstack.org/#/c/241527/611:28
*** venkat_p has quit IRC11:35
*** kei_yama has quit IRC11:38
*** lpabon has joined #openstack-swift11:42
*** SandeepBazar has joined #openstack-swift11:47
*** SandeepBazar has left #openstack-swift11:48
*** lpabon has quit IRC11:48
*** lpabon has joined #openstack-swift11:48
acolesmahatic: makes sense12:03
mahaticacoles: yay, two more patches +2'd! Thanks for your work!12:03
acolesprogress!12:04
mahaticyup :)12:04
*** jerrygb has quit IRC12:10
*** jordanP has quit IRC12:18
*** jordanP has joined #openstack-swift12:18
*** jordanP has quit IRC12:19
openstackgerritMerged openstack/swift: Get rid of contextlib.nested() for py3  https://review.openstack.org/23823712:20
*** jordanP has joined #openstack-swift12:20
openstackgerritAlistair Coles proposed openstack/swift: Update container on fast-POST  https://review.openstack.org/13538012:24
*** mahatic_ has joined #openstack-swift12:27
*** 17SADZP6R has joined #openstack-swift12:27
*** sileht has quit IRC12:28
*** SkyRocknRoll has quit IRC12:29
*** mahatic has quit IRC12:30
*** haypo has joined #openstack-swift12:32
haypoacoles: hi. i'm sorry, i'm unable to reproduce your issue with old versions of pbr & tox, for the review https://review.openstack.org/#/c/217423/12:32
acoleshaypo: thanks for looking into it.12:34
haypoacoles: i expected that we all use tox :)12:35
acoleshaypo: sure, i use tox for tests12:37
acoleshaypo: setup.py to install. i'll play with it some more12:38
*** sileht has joined #openstack-swift12:39
haypoacoles: since it looks like you don't care of being synchronized with openstack global requirements, we can probably start with pbr>=1.012:40
haypoacoles: and maybe even leave setup.py unchanged12:40
haypoacoles: what do you think?12:40
openstackgerritPeter Lisák proposed openstack/swift: swift-init return codes  https://review.openstack.org/23035212:41
haypoacoles: the purpose of the patch is not to upgrade pbr, it's to install dnspython3 on python3, but we need to the support for environment markers for that12:41
acoleshaypo: i'm confused. the commit messsage says we need pbr>=1.8 to support environment markers in requirements, for dnspython. if so how does pbr>=1.0 work?12:44
acoleshaypo: afk12:44
*** m_kazuhiro has quit IRC12:48
*** daemontool has quit IRC12:49
openstackgerritVictor Stinner proposed openstack/swift: On py3, use dnspython3 dependency, not dnspython  https://review.openstack.org/21742312:49
haypoacoles: ^^ here you have, it would be great if you could test it12:52
*** jistr has quit IRC12:52
*** 17SADZP6R has quit IRC13:01
*** haomaiwang has joined #openstack-swift13:01
*** arnox has joined #openstack-swift13:03
*** jamielennox is now known as jamielennox|away13:08
*** mahatic__ has joined #openstack-swift13:09
*** jistr has joined #openstack-swift13:11
*** jerrygb has joined #openstack-swift13:11
*** mahatic_ has quit IRC13:13
*** eranrom has quit IRC13:16
*** jerrygb has quit IRC13:16
*** pdardeau has joined #openstack-swift13:25
*** NM has quit IRC13:33
*** hrou has joined #openstack-swift13:34
*** pdardeau has quit IRC13:48
*** pdardeau has joined #openstack-swift13:49
*** pdardeau has quit IRC13:54
*** pdardeau has joined #openstack-swift13:54
*** daemontool has joined #openstack-swift13:59
*** haomaiwang has quit IRC14:01
*** links has quit IRC14:01
*** haomaiwa_ has joined #openstack-swift14:01
*** jerrygb has joined #openstack-swift14:04
*** pdardeau has quit IRC14:06
*** NM has joined #openstack-swift14:06
*** david-lyle has joined #openstack-swift14:08
*** hseipp has quit IRC14:09
*** diogogmt has quit IRC14:13
*** aagrawal has quit IRC14:14
*** daemontool has quit IRC14:15
*** daemontool has joined #openstack-swift14:16
*** diogogmt has joined #openstack-swift14:16
*** ppai has quit IRC14:30
*** diogogmt has quit IRC14:31
*** janonymous_ has joined #openstack-swift14:32
*** badari has joined #openstack-swift14:39
*** dustins has joined #openstack-swift14:39
*** kota_ has quit IRC14:42
*** amandap has quit IRC14:43
*** cebruns has quit IRC14:43
*** janonymous has quit IRC14:43
*** cebruns has joined #openstack-swift14:44
*** janonymous_ has quit IRC14:45
*** amandap has joined #openstack-swift14:45
*** dfg_ has quit IRC14:46
acoleshaypo: jenkins doesn't like your last change :( its the change in pbr that caused me problems, the pbr version in requirements is ok i think14:46
acolesargh. its the change in pbr *in setup.py* that caused me problems14:46
*** petertr7_away is now known as petertr714:46
*** dfg has joined #openstack-swift14:46
*** peluse_ has quit IRC14:47
*** kota_ has joined #openstack-swift14:48
*** peluse has joined #openstack-swift14:51
haypoacoles: vm-saio-probe looks to use an old version of pip -- https://8b86aea46fb38e6450f2-0e5f4c086da474abc1df58826577db2f.ssl.cf1.rackcdn.com/217423/731/probetests/console.txt14:52
haypoRequirementParseError: Expected ',' or end-of-list in dnspython>=1.12.0;python_version<'3.0' at ;python_version<'3.0'14:52
haypoit doesn't support environment markers14:52
haypoacoles: i don't think that changing setup.py would fix vm-saio-probe14:53
acoleshaypo: i was referring to gate-swift-requirements14:54
acoles vm-saio-probe isn't voting14:54
haypoacoles: ah14:54
acoleshaypo: its weird that failure doesnt show in the top level jenkins report14:55
acolesso you have to look in the comment14:55
openstackgerritVictor Stinner proposed openstack/swift: On py3, use dnspython3 dependency, not dnspython  https://review.openstack.org/21742314:56
openstackgerritAlistair Coles proposed openstack/swift: Re-organise ssync tests  https://review.openstack.org/22019814:56
acolesreview, merge, rebase, repeat...14:56
haypoacoles: jenkins failed because i wrote "pbr>=1.0" whereas global requirements require to write "pbr>=1.6"14:56
acolesyes14:57
haypoacoles: i restored "pbr>=1.6" in requirements.txt14:57
haypoacoles: i wrote pbr>=1.0 because you wrote that you got issues with an older version pbr version, but you had pbr >= 1.014:57
*** pdardeau has joined #openstack-swift14:57
haypoacoles: in fact, i have no idea of what i'm doing :-D i'm trying random changes until it works...14:58
*** hezhiqiang has quit IRC14:58
acoleshaypo: ah, good, so its not just me that has no ideas :)14:58
haypohaha14:58
haypoacoles: pbr is a blackbox for me14:58
haypo(distutils, setuptools, pip, pbr)14:58
acoleshaypo: so, i agree we need pbr>=1.0 to get the env marker support, and openstack dictates therefore it must be pbr>=1.6.0 in requirements.txt14:59
acoleshaypo: ditto!14:59
acoleshaypo: i don't understand the pbr>=1.8.1 requirement in setup.py, i just know it broke omm.15:00
*** haomaiwa_ has quit IRC15:01
*** haomaiwang has joined #openstack-swift15:01
acoleshaypo: after playing some more, the pbr>=1.8.1 requirement in setup.py breaks when i have pbr==1.6.015:02
acolesor older15:02
acolesso it seems incompatible with having pbr>=1.6 in requirements.txt. either that or i am dumb!15:04
*** david-lyle has quit IRC15:06
haypoacoles: lifeless tried once to explain me this issue. in short, setuptools is unable to update itself. so indirectly setup.py cannot update pbr15:06
haypoacoles: it's not an incompatibility in requirements, but an annoying issue: you have to update _manually_ pbr on your system15:07
*** janonymous has joined #openstack-swift15:09
acoleshaypo: so it seems. i am just aware that swift doc recommends sudo pip install -r requirements.txt ; sudo python setup.py develop and that may no longer be sufficient15:11
*** janonymous_ has joined #openstack-swift15:11
acoleshttp://docs.openstack.org/developer/swift/development_saio.html#getting-the-code15:11
*** rohit_ has joined #openstack-swift15:12
acoleswhich makes me wonder (like cschwede did on the review) why requirements.txt does not have same pbr version as setup.py15:12
haypoacoles: "why requirements.txt does not have same pbr version as setup.py" it's mandatory, see global requirements15:13
openstackgerritMerged openstack/swift: Encrypting/Decrypting object metadata  https://review.openstack.org/20331015:13
haypoacoles: initially, i just ran "tox -e update ../swift" from the requirements project15:13
*** blmartin has joined #openstack-swift15:14
*** wbhuber has joined #openstack-swift15:16
acoleshaypo: http://docs.openstack.org/developer/requirements/ doesn't help me undertand what goes into setup.py15:17
*** sanchitmalhotra has joined #openstack-swift15:22
*** sanchitmalhotra has quit IRC15:24
*** jrichli has joined #openstack-swift15:27
*** lcurtis has joined #openstack-swift15:28
haypoacoles: it looks like setup.py is simply hardcoded here, https://github.com/openstack/requirements/blob/master/openstack_requirements/cmds/update.py#L3815:30
*** NM has quit IRC15:31
acoleshaypo: interesting. thanks for link15:33
*** NM has joined #openstack-swift15:34
*** hseipp has joined #openstack-swift15:35
*** hseipp has quit IRC15:35
*** hseipp has joined #openstack-swift15:36
*** diogogmt has joined #openstack-swift15:37
*** juzuluag has joined #openstack-swift15:38
*** diogogmt has quit IRC15:49
*** diogogmt has joined #openstack-swift15:49
*** jlhinson has joined #openstack-swift15:51
*** peterlisak has quit IRC15:53
*** jistr is now known as jistr|afkmtg15:53
*** janonymous has quit IRC15:58
*** vinsh has quit IRC16:00
*** haomaiwang has quit IRC16:01
jrichliacoles: thanks for the merge!16:01
*** haomaiwang has joined #openstack-swift16:01
acolesjrichli: ok. i am just working on the container listing patch16:01
jrichliacoles: you rock!16:02
hroujrichli, so I was half way through and with just 1 silly comment, so +1 great work ; )  If anything interesting I'll just propose a patch16:02
acoleshrou: ah, half way through which?16:03
hrouacoles, oh the big one you just did patch 203310 (but really don't worry at all, it looked great)16:04
patchbothrou: https://review.openstack.org/#/c/203310/ - Encrypting/Decrypting object metadata16:04
acoleshrou: oh sorry, yeah just propose patches now.16:04
brianclineeven in the sid packages?16:04
brianclineoops16:04
brianclinewrong window16:04
hrouacoles, yep!  Oh no worries at all, its really great work16:04
jordanPnotmyname, hi. Any chance you had time to review https://review.openstack.org/#/c/235933/ (Fix testing issues) ?16:05
*** minwoob has joined #openstack-swift16:05
acoleshrou jrichli it beats filing expenses!16:05
jrichliyea, I still gotta do that too16:06
hroujrichli, acoles errrr don't remind me, its actually a pretty big pain because of all the silly subway recites I have : )  The rest is pretty easy16:07
hrougiven we do per diem16:08
*** jerrygb has quit IRC16:13
*** tongli has joined #openstack-swift16:14
*** klrmn1 has joined #openstack-swift16:15
*** jerrygb has joined #openstack-swift16:15
*** janonymous has joined #openstack-swift16:16
*** jerrygb has quit IRC16:31
*** jerrygb has joined #openstack-swift16:31
*** jrichli has quit IRC16:34
haypoacoles: i'm not sure that i understood your last comment on my patch set 5, but the patch set 6 got a +1 for Jenkins: https://review.openstack.org/#/c/217423/16:38
notmynamegood morning16:40
brianclinedoes anyone else see the memcache client in proxy-server irreversibly crapping out under high load, and only fixed with a proxy reload?16:41
hayponotmyname: hi. today i noticed that for the case of cinder, we have the complete list of patches to port cinder to python 3: https://blueprints.launchpad.net/cinder/+spec/cinder-python316:41
hayponotmyname: maybe it can give you a better estimation of how much work is required to port swift. cinder is almost fully ported to py3 (at least, unit tests)16:42
notmynamethanks16:42
haypohum, it looks like i'm working on porting cinder to py3 since june, so 6 months16:43
haypomost changes are small. today i wrote a change which only adds a single line :)16:43
haypohttps://review.openstack.org/#/c/242142/1/cinder/tests/unit/test_tintri.py16:43
janonymousi could register a blueprint just for tracking purpose if it's ok ?16:44
*** ahale_ has joined #openstack-swift16:51
*** chrisnelson_ has joined #openstack-swift16:52
*** _hrou_ has joined #openstack-swift16:52
notmynamejanonymous: I'm not sure if that would help at this point.16:52
*** nadeem has joined #openstack-swift16:53
*** dosaboy_ has joined #openstack-swift16:54
*** nadeem has quit IRC16:54
*** balajir has joined #openstack-swift16:54
*** torgomatic_ has joined #openstack-swift16:54
*** StevenK_ has joined #openstack-swift16:54
*** hrou has quit IRC16:54
*** nadeem has joined #openstack-swift16:55
*** diazjf has joined #openstack-swift16:56
*** barra204 has joined #openstack-swift16:58
*** aerwin3_ has joined #openstack-swift16:59
*** dhellmann_ has joined #openstack-swift17:00
*** diazjf has quit IRC17:00
*** haomaiwang has quit IRC17:01
janonymousOkay.17:01
*** haomaiwang has joined #openstack-swift17:01
*** chsc has joined #openstack-swift17:03
*** dhellmann has quit IRC17:04
*** aerwin3 has quit IRC17:04
*** balajir_ has quit IRC17:04
*** chrisnelson has quit IRC17:04
*** torgomatic has quit IRC17:04
*** StevenK has quit IRC17:04
*** dosaboy has quit IRC17:04
*** shakamunyi has quit IRC17:04
*** ahale has quit IRC17:04
*** dhellmann_ is now known as dhellmann17:05
*** hseipp has quit IRC17:06
*** garthb has joined #openstack-swift17:08
*** hseipp has joined #openstack-swift17:09
*** lpabon has quit IRC17:11
*** jistr|afkmtg is now known as jistr17:14
*** minwoob has quit IRC17:15
*** rledisez has quit IRC17:24
claygheyoh!17:31
*** jordanP has quit IRC17:32
mahatic__hello!17:32
claygbriancline: how high a load - I think there's some error limiting17:33
claygbriancline: there's some timeouts that are adjustable now too17:33
claygbriancline: tracebacks?17:33
claygbriancline: no17:33
*** CaioBrentano has joined #openstack-swift17:33
mahatic__acoles: 232572 is failing at the gate because the metadata dict is ordering itself into this {"cipher": "AES_CTR_256", "iv": base64.b64encode(iv)} and failing the assertion.17:33
claygacoles: bah expense reports :\17:34
claygmahatic__: assert on sorted(dict.items()) ??17:34
mahatic__clayg: we don't want it sorted. It should be this {"iv": base64.b64encode(iv), "cipher": "AES_CTR_256"}17:35
acolesmahatic__: yeah there's a bad test in there #willfix17:35
mahatic__acoles: :) maybe using the crypto meta directly in the assertion i guess?17:36
acolesmahatic__: i don't think we can know the order of the dumped dict17:36
mahatic__acoles: actually it orders itself even before the dumps17:36
mahatic__>>> {"iv": base64.b64encode(iv), "cipher": "AES_CTR_256"} will result in {"cipher": "AES_CTR_256", "iv": base64.b64encode(iv)}17:37
acolesmahatic__: ? where's that17:38
mahatic__acoles: just on the console17:38
mahatic__apparently "Items stored in a dictionary do not have any inherent order. The order they are printed out is entirely down to the hash values for each of the keys and the other items in the dictionary."17:39
acolesmahatic__: exactly. and the order may vary from machine to machine17:39
mahatic__acoles: oh, so that's the reason it passed the first time and didn't the second!17:39
acolesso works omm but not jenkins.17:39
mahatic__works on my machine too17:39
acolesi guess!17:40
acolesmahatic__: i haven't had chance to look at the detail but something like what clayg said is likely to be the fix17:41
*** wbhuber_ has joined #openstack-swift17:41
acolesmahatic__: i want to get the container listing patch clean and pushed before end of day, i'll look at that failing test tomorrow (if you don't fix it first :D)17:42
mahatic__clayg: I now get what you said :D my bad! (I completedly blinded out 'assert on')17:43
mahatic__acoles: sure! good luck on the container listing goal :D17:44
acolesmahatic__: its looking good so far...17:44
*** wbhuber has quit IRC17:44
mahatic__nice17:45
acolesugh, xml :(17:47
mahatic__yup, that's the tricky part17:48
claygi think today is the day to review fast-POST - wish me luck17:50
notmynamegood luck!17:50
mahatic__good luck17:51
*** arnox has quit IRC17:55
*** diazjf has joined #openstack-swift17:58
*** marcusvrn_ has joined #openstack-swift17:59
*** jistr has quit IRC18:00
*** haomaiwang has quit IRC18:01
*** haomaiwang has joined #openstack-swift18:01
*** wbhuber_ has quit IRC18:02
*** wbhuber has joined #openstack-swift18:02
*** wbhuber has quit IRC18:07
*** wbhuber has joined #openstack-swift18:08
*** daemontool has quit IRC18:09
lifelessacoles: you could add pbr to your requirements.txt which would address that18:09
lifelessacoles: but also be aware that we've been recommending to use pip install -e . rather than setup.py develop for a year or more now18:10
acoleslifeless: pbr is in requirements.txt. the piece thats confusing me (and maybe others) is why we have (proposed) pbr>=1.6 in requirements.txt and pbr>=1.8 in setup.py18:11
acoleslifeless: ack re. pip install -e18:12
lifelessacoles: ah, because setup.py describes build requirements, and requirements.txt describes the runtime API18:12
lifelessacoles: the runtime API hasn't had bugfixes since 1.618:13
notmynameisn't pbr just a build-time requirement?18:13
lifelessnotmyname: not for many projects. It has both a runtime and build time API18:14
lifelessnotmyname: the runtime API abstracts out the difference between pkg_resources version metadata (used for installed cases) and git based version metadata (used for uninstalled cases)18:14
lifelessnotmyname: [and needless to say, super stable because of its use everywhere....]18:15
* mahatic__ calls it a night18:15
* acoles wishes clayg luck, and braces himself18:15
notmynamemahatic__: good night18:15
acolesmahatic__: g'night18:16
notmynamemahatic__: oh wait a sec18:16
lifelessnotmyname: we're working on the issue with setup-requires in setuptools with the new build system PEP for Python18:16
mahatic__thanks, good day/evening18:16
mahatic__notmyname: what's up?18:16
*** nadeem has quit IRC18:16
notmynamemahatic__: pm sent18:16
lifelessnotmyname: once thats done everything should work a -whole lot- better18:16
*** diazjf has quit IRC18:19
clayganyone care about useless micro-optimization bike-shedding want to sanity check that my results that everything in python is slower than you expect -> https://review.openstack.org/#/c/241527/18:24
claygacoles: yeah pip install -e is the bomb?  what is this setup.py you speak of?18:24
clayglike I mean there was this one time (it was more like a decade) the entire python community got by with setup.py develop - but then openstack came to python - and the world had to move18:26
clayg^ redbo for you bra18:26
notmynamemy muscle memory still uses `python ./setup.py develop`18:27
*** mahatic__ has quit IRC18:27
*** haomaiwa_ has joined #openstack-swift18:27
*** haomaiwang has quit IRC18:28
acolesnotmyname: our docs do too http://docs.openstack.org/developer/swift/development_saio.html#getting-the-code18:34
acolesclayg: i'm so last year ;)18:35
*** proteusguy_ has quit IRC18:36
*** mzhou has joined #openstack-swift18:36
notmynameclayg: https://gist.github.com/notmyname/19a9ff6c8a037f471e8718:37
*** petertr7 is now known as petertr7_away18:37
claygnotmyname: do you know what any of that means!?18:39
notmynameclayg: I just updated it so the any() call is a little more clear in the disassembly18:40
claygi mean the any one looks like less instructions - but i'm pretty sure my timeit demonstrates it's slower?18:40
notmynameie split it into more lines18:40
notmynameyeah18:40
notmynameBUILD_TUPLE and MAKE_CLOSURE and especially the 2 CALL_FUNCTION look really suspicious for the slow any()18:41
lifelessnotmyname: so the issue with that isn't coming from pbr btw18:41
notmynameclayg: received wisdom for python is that "function calls are slow"18:42
lifelessnotmyname: its a general upstream python packaging consensus18:42
*** amoturi has joined #openstack-swift18:44
*** zhill has joined #openstack-swift18:44
*** dabukalam has quit IRC18:45
*** hseipp has quit IRC18:45
claygnotmyname: yeah I guess you've got the <genexp>.__next__ called multiple times?18:45
*** mandarine has quit IRC18:46
claygnotmyname: hey and I know since iterating generators is super fast let's build a co-routine runtime around the idea!18:46
*** dabukalam has joined #openstack-swift18:46
*** mandarine has joined #openstack-swift18:46
claygnotmyname: so which do you find more readable?18:46
notmynameclayg: cool! and maybe we could have a convenient short name for it. every()? or all_of_them()? or any_of_them()? surely there's a shorter one ;-)18:47
claygnotmyname: I think if you make it a helper function it goes back to being the same as any :\18:49
*** proteusguy_ has joined #openstack-swift18:49
notmynameyeah :-)18:49
notmynamethat's a good short name18:49
clayglol18:50
notmynameI don't have any preference between any() or the for loop. if forced, I'd probably slightly prefer the for loop, but I really don't think it matters18:53
notmynamebut looking at that patch, the any() is probably worse if it's actually calling unquote() multiple times (ie len(forbidden chars) times)18:53
*** mfalatic_ has joined #openstack-swift18:56
*** jerrygb has quit IRC18:57
*** jerrygb has joined #openstack-swift18:58
*** mfalatic has quit IRC19:00
*** haomaiwa_ has quit IRC19:01
*** haomaiwang has joined #openstack-swift19:01
claygI don't think it's a lambda there - it only gets invoked once19:01
notmynamewow19:02
notmyname$ python ./speed.py test_loop19:02
notmyname0.83502817153919:02
notmyname$ python ./speed.py test_any19:02
notmyname1.4545989036619:02
claygoh... no - it's probably every time19:02
notmyname$ pypy ./speed.py test_loop19:02
notmyname0.17444109916719:02
notmyname$ pypy ./speed.py test_any19:02
notmyname0.42309689521819:02
claygwell that's an order of magnitude19:03
*** jerrygb has quit IRC19:03
claygwell - i guess not quite19:03
claygI CAN MATH!19:03
notmynamethat was with pypy 2.2.1. installing pypy 4.0.0 now19:04
claygi guess in either case it'd be useful to assign the unquoted path to temp var19:05
acolesnotmyname: clayg i think i know what you are discussing, i nearly dinged that patch for having the unquote(req.path) in the any, maybe i should have :/19:05
notmynameyeah. I added an identity function to do just that in my test19:05
claygacoles: lol!19:06
notmynamepypy 4 is about 2x faster than pypy 2.2.119:06
claygacoles: this code was working *fine* before - why is *this* keeping me from fast-POST!  WHYYYYY?!19:06
notmynameon the any()19:06
clayg(hontestly i'm planing with my ring-check spread sheets - but still)19:07
notmyname$ pypy ./speed.py test_loop19:07
notmyname0.14086890220619:07
notmyname$ pypy ./speed.py test_any19:07
notmyname0.20367908477819:07
notmynamenot too much difference between the two with latest pypy. or at least not nearly as much as with python or earlier pypy19:07
*** diazjf has joined #openstack-swift19:07
notmynameall tests run on my mac19:08
*** dustins has quit IRC19:08
*** jrichli has joined #openstack-swift19:10
claygwhat does STM buy you again?  When you do a thread they can both run on different cpus at the same time or something?19:16
lifelessyes19:17
lifelessthe idea is you run speculatively and throw away invalidated results19:18
*** _hrou_ is now known as hrou19:19
acolesjrichli: with the container listing patch, did you see additional func test failures?19:19
* acoles hopes for a yes19:20
jrichliI haven't tested with the latest container listing patch yet.  is that what you mean?  or do you want to know the number of failures before you started working on it?19:20
acolesjrichli: i see container listing func tests fail. i know why, i'm just not sure if i broke them with my changes or it was always the case. i suspect always the case, but idk19:22
jrichlithe last time I had tested that patch, it did not break more tests from the patch it depended on.19:23
jrichlibut there had been several rebases since then19:23
acolesoh yes!19:23
jrichlieureka!19:23
jrichli:-)19:23
acolesjrichli: ? what happened?19:24
clayggoal #3 for STM sounds interesting - http://pypy.org/tmdonate2.html#goal-3 - transparently adapting to evented framework to managed threads for multi-core parallelization19:24
jrichliacoles: nothing, just in the spirit of the "oh yes"19:24
jrichlisorry to get you excited19:24
acolesjrichli: i was saying 'oh yes there have been many rebases (sigh)'19:25
jrichli:-) that is one bad thing about not having the new middleware in the gate.  but then everything will fail anyway.  is there a way to give the gate a baseline number of failures :-p19:26
acolesjrichli: so the way we append crypto_meta to content-type as a param breaks in the container server, because it tries to parse the content-type and throws out bad param fields.19:28
acolesmeaning the crypto_meta gets lost from the listing response :/19:28
jrichliacoles:  if I recall, there is some logic somewhere in the backend that removes anything after a ";" in content-type19:29
brianclineis that prioritized right? it's only got 218 objects in there...19:29
brianclineack19:29
brianclinewrong window again19:29
acolesbriancline: heh twice today ;)19:29
brianclineacoles: yeah, I'm doing great with computers today19:30
jrichliacoles: i mean in the proxy obj controller19:31
jrichliacoles: nm. i think that is only for startswith('swift_bytes=')19:33
*** petertr7_away is now known as petertr719:34
acolesjrichli: ^^ yes but in container server. while parsing and looking for swift_bytes it throws away our crypto_meta :/ so all we see in listing is "<content-type>;meta="19:34
jrichlidarn swift_bytes!19:35
pdardeauclayg: what is STM?19:39
claygpdardeau: http://doc.pypy.org/en/latest/stm.html#software-transactional-memory19:40
pdardeauclayg: ah, nice. thx19:40
openstackgerritAlistair Coles proposed openstack/swift: Decrypting Container Listing  https://review.openstack.org/21443819:44
acolesjrichli: ^^ thats as far as i got for today, will have to revisit the meta handling tomorrow. there will be a way.19:44
jrichliacoles: ok, thanks.  i will think about the content-type formating19:45
acolesjrichli: its still worth reviewing the patch, it should be otherwise sane and ready.19:47
acoleshrou mahati ^^19:47
hrouacoles, this time I will review before anyone else lol probably not19:47
jrichligot it, will do19:47
*** dustins has joined #openstack-swift19:51
*** acoles is now known as acoles_19:51
*** jerrygb has joined #openstack-swift19:53
*** sujit has joined #openstack-swift19:56
openstackgerritPaul Dardeau proposed openstack/swift: Add unit tests to cover print_item_locations  https://review.openstack.org/24096119:57
*** sujit is now known as sfs_19:59
*** sfs_ is now known as suythf_19:59
*** haomaiwang has quit IRC20:01
*** haomaiwang has joined #openstack-swift20:01
*** alejandrito has joined #openstack-swift20:02
*** jrichli has quit IRC20:16
openstackgerritOndřej Nový proposed openstack/swift: Compare Swift config checksum in swift-recon --all  https://review.openstack.org/24072220:18
*** jrichli has joined #openstack-swift20:20
openstackgerritOndřej Nový proposed openstack/swift: Compare Swift config checksum in swift-recon --all  https://review.openstack.org/24072220:21
*** janonymous has quit IRC20:21
*** daemontool has joined #openstack-swift20:22
*** rohit_ has quit IRC20:24
*** diazjf has quit IRC20:25
*** jlhinson_ has joined #openstack-swift20:30
*** jlhinson has quit IRC20:30
*** suythf_ has quit IRC20:32
*** CaioBrentano has quit IRC20:33
*** janonymous has joined #openstack-swift20:35
*** amoturi has quit IRC20:37
claygi really need to come up with a way to "find a part that can go in this hole" - instead of gather up some random parts form devices that have too many and then try and see if you can fit them somewhere better than where you got them from20:44
claygI'm sure I can come up with replica2part2dev that will never balance if you only gather the parts from full devices - like there is *no* part on a full device that could possibly fit onto the hungry dev w/o giving up dispersion20:45
claygI think20:45
claygmaybe *sure* is too strong20:46
clayganyway - in my dataset I've got ~25 stupid rings that won't balance (worst is at %7 and the required overload is %4 so it's not a great topology) - but it keeps reassinging %5 of it's parts every crank and not really making any progress20:47
clayg*generally* this is fine, if the balance doesn't improve by > %1 you won't even save the changes w/o -f20:48
claygbut it just bothers me to no end :'(20:49
claygalso the real values are stupid low - that %3 difference on the worst device from the required overload and the current balance works out to ~11 parts across the entire cluster that "could" be on better homes.20:52
openstackgerritPaul Dardeau proposed openstack/swift: Added unit tests for ringbuilder command-line utility  https://review.openstack.org/24007620:53
claygno wait... I think i'm counting that wrong :\20:55
*** lpabon has joined #openstack-swift20:56
openstackgerritPaul Dardeau proposed openstack/swift: Add unit tests to cover print_item_locations  https://review.openstack.org/24096120:59
*** haomaiwang has quit IRC21:01
*** haomaiwang has joined #openstack-swift21:01
*** mzhou_ has joined #openstack-swift21:03
*** mzhou has quit IRC21:03
*** mzhou_ is now known as mzhou21:03
*** NM has quit IRC21:09
openstackgerritBill Huber proposed openstack/swift: Add unit tests for swift.account.reaper  https://review.openstack.org/23910521:20
*** diazjf has joined #openstack-swift21:21
*** NM has joined #openstack-swift21:27
openstackgerritPaul Dardeau proposed openstack/swift: Added unit tests for ringbuilder command-line utility  https://review.openstack.org/24007621:34
*** mwheckmann has joined #openstack-swift21:37
notmynameclayg: do you have a --force-save-this-even-if-not-much-moved option in your version of the balancer? I know wer21:39
notmynameI know we've talked about it before21:39
claygnotmyname: it's already in there21:40
claygnotmyname: and I didn't break it21:40
notmynameah, cool21:40
*** NM has quit IRC21:40
mwheckmannhi all. I'm in process of upgrading to Liberty and needed to make some ring changes. I'm seeing that errors in swift-ring-builder rebalance:21:41
*** NM has joined #openstack-swift21:42
mwheckmannFile "/usr/lib/python2.7/site-packages/swift/common/ring/builder.py", line 1065, in _gather_reassign_parts for tier in tfd[dev['id']]:21:42
mwheckmannTypeError: 'NoneType' object has no attribute '__getitem__'21:42
mwheckmannThis is what my account ring looked like:21:45
mwheckmann             0       1     1     172.16.0.11  6002     172.16.0.11              6002      SSD1 100.00     196608    0.0021:45
mwheckmann             1       1     1     172.16.0.12  6002     172.16.0.12              6002      SSD2 100.00     196608    0.0021:45
mwheckmann             2       1     1     10.131.0.13  6002     10.131.0.13              6002      SSD3   0.00          0    0.0021:45
mwheckmannThe only change I made was to set the weight of the SSD3 device to 25 (I also tried other weights but no difference).21:46
mwheckmannI can't seem to find any known/related bug in launchpad21:48
notmynamemwheckmann: are the errors with the upgraded code or the old code? and what version of swift are you using?21:49
mwheckmannnotmyname: It's from the RDO Liberty packages: openstack-swift-2.5.0-1.el7.noarch21:50
notmynameok21:50
mwheckmanndo you want a Launchpad bug for this?21:51
openstackgerritBill Huber proposed openstack/swift: ObjectControllers return application errors as 499 on bad read  https://review.openstack.org/23600721:52
notmynamemwheckmann: you added the drive with a zero weight, then you tried to set the weight up. is that right?21:52
wbhuberclayg: ^^ i think the same that we need to leave timeout there until further review21:53
notmynameI want to try to duplicate it21:53
mwheckmannnotmyname: close. I decreased the weight to get data off so that I could re-add it with another IP address.21:53
mwheckmannHowever, remove doesn't seem to work.21:54
mwheckmannI then discovered the "set_info" command and used that to change the IP.21:54
mwheckmannboth IPs (replication + regular)21:54
mwheckmannAll I wanted to do now was re-add weight and re-balance21:55
notmynameok, I've got a 3-device ring locally now. you set the weight to zero, rebalanced, then set it higher again and then the rebalance failed?21:58
mwheckmannexactly but with an IP change using set_info before setting the weight higher21:58
mwheckmannnotmyname: replica count is 321:59
* clayg wonders if this bug is already fixed on fix-rings-for-realz22:00
claygmwheckmann: can you publish your builder?22:00
*** lpabon has quit IRC22:00
*** haomaiwang has quit IRC22:01
mwheckmannclayg: sure. Where should I do that?22:01
*** haomaiwang has joined #openstack-swift22:01
claygmwheckmann: good question22:01
mwheckmannI'll just do it on my Google Drive22:01
claygnotmyname: ^ ?22:01
mwheckmanngive me a minute22:02
notmynamenope. I don't know. google drive is fine22:02
notmynamemaybe if you had a swift cluster.... ;-)22:02
notmynamemwheckmann: FWIW, my first attempt to recreate it didn't have any errors22:02
claygnotmyname: oh that's an ok point - I could make a PUT tempurl22:02
notmynameaside from "hey you want 3 replicas but now you only have 2 drives"22:03
claygnotmyname: mwheckmann: the only way that dev's end up being None is if you *remove* them setting to zero weight shouldn't have been sufficient to trigger that bug22:03
claygacoles_: I don't understand the TODO in the commit about allowed_headers metadata - if it gets written to the .meta file it should be fine (the e.g. content-disposition should be written to the .meta file)22:06
*** petertr7 is now known as petertr7_away22:07
mwheckmannnotmyname: https://goo.gl/pIR5Z5 --> On Swift :)22:10
mwheckmannclayg: notmyname: I did attempt to remove the device as well. But after running rebalance the device was still in the ring with zero weight as before.22:12
claygmwheckmann: idk, sounds broken22:13
notmynamemwheckmann: yup. rebalance on that one locally gives me an error22:14
mwheckmanngood. I'm not crazy :)22:15
*** jrichli has quit IRC22:16
*** wbhuber has quit IRC22:17
*** petertr7_away is now known as petertr722:17
*** wbhuber has joined #openstack-swift22:17
claygmwheckmann: well the device is definately marked for deletion :\22:20
*** daemontool has quit IRC22:21
claygit's getting removed and things go nuts22:21
mwheckmannok. That would explain it. Then the real bug is the fact that it doesn not actually get removed during rebalance22:21
notmynameI've got a meeting in about 5 minutes, so I won't be able to look at this for much longer22:21
*** wbhuber has quit IRC22:22
*** mzhou has quit IRC22:22
mwheckmannI'm about to go pick up my kids. But I don't mind catching up later.22:22
claygmwheckmann: you have 2 more mins?22:23
mwheckmannyes22:23
mwheckmannat least 15 more :)22:23
claygmwheckmann: well it *does* get removed, that's what causes the bug :\22:23
claygI think maybe you tried to rebalance after the remove and things went south because the current code doesn't prevent 3 replicas with 2 devices22:23
claygthat left the ring in a wonky state22:23
mwheckmannok.22:24
mwheckmannbut on my object.builder where I have many more devices, I could not remove the device either22:24
clayganyway - to work around it you need to let it get remvoed - but you'll probably have a add a dummy device22:24
claygmwheckmann: why not?  same traceback?22:25
mwheckmannI didn't try re-adding some weight yet. Shall I ?22:25
*** mzhou has joined #openstack-swift22:25
mwheckmannI'm just pointing out that after running rebalance (after removing the devices), they still showed up in the list22:26
*** yuan has quit IRC22:26
*** dustins has quit IRC22:26
mwheckmannlet me try to add some weight to my object ring22:27
claygwell - what I had to do was add a new device with ip 10.131.0.14 then rebalance to let 10.131.0.13 remove (and parts get assigned to 10.131.0.14)22:27
claygthen I fixed 10.131.0.14 with set_info22:27
mwheckmannwhat to you mean by "fixed 10.131.0.14 with set_info" ?22:28
claygswift-ring-builder test.builder set_info --id 3 --change-ip 10.131.0.1322:28
mwheckmannok. Got it.22:28
mwheckmannsame error in the object ring :(22:29
claygthe NoneType thing?22:29
mwheckmannyes.22:29
claygok - let me pull down your ring again and switch baack to master22:30
mwheckmanneven though I have 24 devices that are available.22:30
mwheckmannI'm assuming that a fix for the object ring would be to add 12 dummy devices and do the same as you did with the account ring?22:30
*** gyee has joined #openstack-swift22:32
claygdid you *remove* 12 devices?22:33
mwheckmannyes.22:34
claygidk, doesn't look the dummy fix works on master22:34
mwheckmannshit.22:34
mwheckmannI tried to remove the 12 devices because I thought that would be the only way to change the IP of a device. That was before I discovered "set_info"22:35
claygmwheckmann: ok it worked for me - let me start over from scratch and capture in a paste bin22:35
mwheckmannok. cool. Much appreciated22:35
claygmwheckmann: something like this strategy may work for the other ring with the 12 devices -> https://gist.github.com/clayg/6b1ffbb0fec28344ff5022:38
openstackgerritMerged openstack/swift: Optimize the code performance  https://review.openstack.org/24152722:39
*** badari has quit IRC22:40
*** badari has joined #openstack-swift22:40
mwheckmannclayg: this was on master?22:40
claygwhere's that swiftclient change that outputs content-type with -l already!22:40
claygmwheckmann: oh crap... yeah I think so?22:40
*** petertr7 is now known as petertr7_away22:40
claygmwheckmann: reflog says it was -> aae5810 HEAD@{0}: checkout: moving from master to review/alistair_coles/p-fast-post-rebase22:41
*** alejandrito has quit IRC22:41
mwheckmannok. I will try it later on this evening. I must go.22:41
mwheckmannthanks for your help!22:41
clayggl22:42
claygnotmyname: fix-rings-for-real messed up on the has three devices but one of them is going to be removed rebalance22:43
*** diogogmt has quit IRC22:44
claygi added a commit for the fix, but I need to write a test.22:45
clayg... but I'm reviewing fast-POST GD!22:45
claygwell acctually I just udpated content-type with a POST that didn't have to do a copy and the upate made it's way into the object listing - so I think I'm done right?22:45
clayg:shipit:22:45
hrouHey clayg for bug 1509429 we ended up writing some func tests to validate most of the APIs (namely the headers returned), would you like to see those uploaded to swift, some unit / func tests to validate some of these headers but these would be a bit more clearer I'd wager ?22:47
openstackbug 1509429 in OpenStack Object Storage (swift) "X-Timestamp missing from object PUT/COPY response headers" [Low,Confirmed] https://launchpad.net/bugs/150942922:47
*** mwheckmann has quit IRC22:48
clayghrou: I love me some functests!22:48
hrouclayg, awesome and the only other little debate we were having is if unit tests were more appropriate in this context ?22:49
*** klrmn2 has joined #openstack-swift22:50
*** klrmn1 has quit IRC22:50
*** asettle has joined #openstack-swift22:51
claygfunctest is fine - it's not something that's so likely to regress as much as it's good documentation of the expected behaviors of the api22:51
clayghrou: if we had some direct to storage server blackbox tests I'd probably... well idk... if it's going out to the client functests are fine22:51
clayghrou: just push up what you have and then ask me to look at it - it's hard speaking in abstracts22:52
hrouclayg, gotcha yea that makes sense, but nah its all the external APIs really so all through proxy, and agreed they're not likely to change / regress much.22:52
hrouthanks!22:52
claygthanks for working on it!22:52
hrouclayg, anytime!, not me personally though, new hire on our team ; )22:54
*** km has joined #openstack-swift22:55
*** km is now known as Guest719022:55
*** gyee has quit IRC22:57
*** jamielennox|away is now known as jamielennox22:59
*** jlhinson_ has quit IRC22:59
*** haomaiwang has quit IRC23:01
*** haomaiwa_ has joined #openstack-swift23:01
*** jerrygb has quit IRC23:08
openstackgerritPaul Dardeau proposed openstack/swift: Added unit tests for ringbuilder command-line utility  https://review.openstack.org/24007623:10
*** pdardeau has quit IRC23:11
*** zaitcev has joined #openstack-swift23:12
*** ChanServ sets mode: +v zaitcev23:12
*** diazjf has quit IRC23:14
*** diazjf has joined #openstack-swift23:15
*** janonymous has quit IRC23:15
*** blmartin has quit IRC23:19
*** gyee has joined #openstack-swift23:19
*** StevenK_ is now known as StevenK23:21
*** diazjf has quit IRC23:22
*** kei_yama has joined #openstack-swift23:24
*** hrou has quit IRC23:25
*** jerrygb has joined #openstack-swift23:33
mattoliverauHey all from Takayama Japan, yup still here :)23:35
*** ujjain- has quit IRC23:38
*** chsc has quit IRC23:39
*** ujjain has joined #openstack-swift23:39
*** ujjain has joined #openstack-swift23:39
brianclineclayg: oops, just saw your question. i'll grab a sample of the tracebacks and error messages23:41
*** daemontool has joined #openstack-swift23:46
*** lcurtis has quit IRC23:47
*** jrichli has joined #openstack-swift23:47
*** tongli has quit IRC23:48
*** jerrygb_ has joined #openstack-swift23:49
*** jerrygb has quit IRC23:50

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