Tuesday, 2016-01-26

*** nadeem has quit IRC00:00
*** haomaiwa_ has quit IRC00:01
*** haomaiwang has joined #openstack-swift00:01
*** Jeffrey4l has joined #openstack-swift00:02
mattoliveraunotmyname: yeah not as hot as Perth :) its been a milder summer but with some hot days thrown in. But that's Melbourne ;) in fact the next week in Melbourne looks like its going to be especially mild. Looks like low to mid twenties. Tho weather in this city can change quickly and could be 40 before you know it.00:12
*** zhill has quit IRC00:12
*** lcurtis_ has quit IRC00:12
*** ho_ has joined #openstack-swift00:15
ho_good morning!00:16
*** arch-nemesis has quit IRC00:19
*** chlong has quit IRC00:20
*** chlong has joined #openstack-swift00:20
*** zhill has joined #openstack-swift00:21
*** zhill has quit IRC00:25
*** baojg has joined #openstack-swift00:25
*** diogogmt has quit IRC00:28
*** zhill has joined #openstack-swift00:31
*** mingdang1 has joined #openstack-swift00:32
*** awelleck has quit IRC00:37
*** chlong has quit IRC00:41
*** chlong has joined #openstack-swift00:41
*** baojg has quit IRC00:41
*** sgundur has left #openstack-swift00:42
openstackgerritMerged openstack/swift: Fixed docs: Title underline too short  https://review.openstack.org/27218900:42
openstackgerritMerged openstack/swift: Ring Overview updates  https://review.openstack.org/24441200:42
*** david-lyle has joined #openstack-swift00:42
notmynameclayg: ring docs updated ^ ;-)00:43
*** baojg has joined #openstack-swift00:46
kota_good morning00:46
*** dmorita has quit IRC00:46
*** baojg has quit IRC00:46
*** chlong has quit IRC00:48
*** dmorita has joined #openstack-swift00:48
*** chlong has joined #openstack-swift00:48
*** m_kazuhiro has joined #openstack-swift00:49
*** chlong has quit IRC00:53
*** chlong has joined #openstack-swift00:53
*** pgbridge_ has joined #openstack-swift00:57
*** haomaiwang has quit IRC01:01
*** pgbridge has quit IRC01:01
*** haomaiwa_ has joined #openstack-swift01:01
*** garthb has quit IRC01:03
takashiho_, kota_: good morning01:03
kota_ho_, takashi: o/01:03
*** mrmoje has joined #openstack-swift01:05
*** xiangxinyong_ has joined #openstack-swift01:07
ho_kota_: takashi: morning!01:08
*** peterlisak has quit IRC01:10
*** kaleta has quit IRC01:11
*** kaleta has joined #openstack-swift01:11
*** onovy has quit IRC01:12
*** peterlisak has joined #openstack-swift01:12
*** onovy has joined #openstack-swift01:12
*** haomaiwa_ has quit IRC01:17
*** diogogmt has joined #openstack-swift01:24
*** mingdang1 has quit IRC01:25
*** kaleta has quit IRC01:38
*** kaleta has joined #openstack-swift01:38
*** peterlisak has quit IRC01:39
*** peterlisak has joined #openstack-swift01:39
*** xiangxinyong_ has quit IRC01:44
charz_Morning! kota_01:52
charz_Morning! ho_ and takashi01:53
kota_charz: o/01:53
*** chlong has quit IRC01:55
*** chlong has joined #openstack-swift01:55
*** rminmin has joined #openstack-swift02:00
*** david-lyle has quit IRC02:05
*** baojg has joined #openstack-swift02:06
ho_charz_: morning! did you get big snowing?02:10
charz_ho_: YEAH! That's REALLY big, we got snow in many places includes my parent'02:15
*** klrmn has quit IRC02:15
openstackgerritKota Tsuyuzaki proposed openstack/swift: CompositeRing Support  https://review.openstack.org/27192002:15
*** mingdang1 has joined #openstack-swift02:16
charz_s/parent'/parents' house02:16
charz_That's crazy.02:17
ho_charz_: are you and your family safe?02:17
charz_ho_: They're good! Thanks!02:17
ho_charz_: good to hear it :-)02:18
charz_ho_: How about weather in your places? still snowing?02:18
ho_charz_: yeah, but i live in north part of japan so i have a lot of experience for snowing :-)02:21
*** haomaiwang has joined #openstack-swift02:24
charz_ho_: cool! You can play snowboard/ski in the winter season.02:24
*** diogogmt has quit IRC02:28
*** thumpba has joined #openstack-swift02:29
*** rminmin has quit IRC02:30
*** wanghua has joined #openstack-swift02:35
kota_ho_: still?02:47
kota_ho_: i am starting to see patch 202411 and a bit confused about the patch.02:48
patchbotkota_: https://review.openstack.org/#/c/202411/ - swift - Add functional test for access control (RBAC) with...02:48
*** chlong has quit IRC02:49
*** chlong has joined #openstack-swift02:49
kota_ho_: i wanna make sure you ware working on keystone's reseller admin on that patch, right?02:50
*** baojg has quit IRC02:50
*** superflyy has joined #openstack-swift02:50
kota_ho_: Do we need another work for tempauth (or not)?02:50
kota_ho_: test configuration in the patch told me as "Account must have a role for reseller_admin_role(keystoneauth)" but the concept of  "reseller_admin" exists all over swift so I am wondering if we could have such kinds of functional test for every authentication.02:53
kota_i might be missing something, though.02:53
kota_and got failures with tempauth account6 which has reseller_admin :/02:54
kota_seems only keystone supported...02:55
kota_ho_: what do you think of?02:55
*** daemontool has quit IRC02:56
*** haomaiwang has quit IRC03:01
*** haomaiwang has joined #openstack-swift03:01
*** d0m has quit IRC03:03
*** dmorita has quit IRC03:04
claygnotmyname: what was wrong with the ring doc the way it was!?03:13
claygoh, you ment "updated" as it's now avialable at swift.openstack.org - nice03:14
claygYES!  http://docs.openstack.org/developer/swift/overview_ring.html#partition-replica-terminology03:14
claygyou people let me put that last sentence of the last paragraph in the official docs - suckers03:14
clayghell you probably shouldn't have even let me merge any of it03:15
claygtoo late now tho!!! ahahaha03:15
*** bill_az has quit IRC03:16
*** diogogmt has joined #openstack-swift03:17
*** chlong has quit IRC03:17
*** chlong has joined #openstack-swift03:18
*** chlong has quit IRC03:19
*** chlong has joined #openstack-swift03:19
*** dmorita has joined #openstack-swift03:24
*** david-lyle has joined #openstack-swift03:25
*** baojg has joined #openstack-swift03:45
*** baojg has quit IRC03:59
*** SkyRocknRoll has joined #openstack-swift04:00
*** haomaiwang has quit IRC04:01
*** superflyy has quit IRC04:01
*** haomaiwa_ has joined #openstack-swift04:01
*** klrmn has joined #openstack-swift04:05
jrichlitimburke: looks like your +2 was lost to a rebase of https://review.openstack.org/#/c/259410/.  it would be good to have it back - and to have another reviewer :-)04:06
ho_kota_: i'm back. did you get failures for account6? i think this func test skip cases if there is no configuration for keystone (skip_if_not_v3).04:08
kota_ho_: 1 sec, make sure my setup again...04:10
*** dmorita has quit IRC04:13
*** sgundur has joined #openstack-swift04:14
kota_ho_: tests looks skiped but an error happened (looks like tearDown?)04:17
*** silor has joined #openstack-swift04:18
notmynameclayg: yeah. just meant that the patch had landed :-)04:18
kota_i just copied test/sample.conf to /etc/swift/test.conf and remove comment out for account604:18
kota_ho_: and then, run "nosetests test/functional/test_access_control.py"04:19
ho_kota_: ./.functest also same result?04:20
ho_kota_: i will create own env and check the behavior.04:20
kota_wait, some server process seems not running04:20
kota_probably my bad04:20
kota_ho_: i tried again, finished successfuly, sorry04:21
ho_kota_: nice!04:22
kota_ho_: i mean all of rbac skipped04:22
kota_ok, that's runnable. I need keystone setup for them, though.04:23
ho_kota_: thanks! i answered your question. this test is only for keystone now.04:23
ho_kota_: to run with tempauth, it is necessary to adapt the cases for it.04:24
*** sgundur has left #openstack-swift04:24
kota_ho_: all right04:24
notmynamegoal for tonight: finish my LCA presentation on erasure codes04:28
ho_notmyname: can i read it after your presentation in LCA?04:30
notmynameho_: it should be recorded (and mattoliverau said it will actually be live-streamed)04:30
ho_notmyname: cool!!!04:30
kota_ho_: perhaps, it requires keystone v3 too?04:36
ho_kota_: yep04:38
ho_kota_: ^^^ i don't understand how to write the underscore...04:38
kota_oh, god. my script to setup for swift3 is for v2.004:39
ho_kota_: v2 is not recommended from swift point of view. it's good change to shift v3 :-)04:40
ho_kota_: s/change/chance/04:40
kota_ho_: hehe :/04:41
kota_ho_: and it's good to write down the rbac tests are for v3 specific as well as fourth test account :/04:42
ho_kota_: do you use vsaio?04:42
kota_ho_: yes, but older one because i forked it to use my AWS setup.04:43
ho_kta04:43
*** mrmoje has quit IRC04:43
ho_kota_: i updated vsaio to vsaio with keystone and eranrom has a good script to setup keystone. https://gist.github.com/eranrom/7c4c398ca4b7bb196fed04:44
kota_i know04:44
ho_kota_: ok. just fyi :-)04:44
kota_i have subsription of github04:44
*** mrmoje has joined #openstack-swift04:45
kota_ho_: but, thanks04:46
ho_kota_: no i have to say "thanks for the review" :-)04:47
*** stevemar has quit IRC04:47
timburkejrichli: good call. i've been meaning to circle back on that04:51
*** diogogmt has quit IRC04:56
*** stevemar_znc has joined #openstack-swift04:57
*** haomaiwa_ has quit IRC05:01
*** haomaiwang has joined #openstack-swift05:01
*** dmorita has joined #openstack-swift05:02
timburkekota_: would it be worth having two keystone functests? one using v2 on an old version of keystone, the other using v3 and tip of master. or maybe just most recent release? not sure i like the idea of depending on keystone's stability on master...05:06
*** cebruns has quit IRC05:06
kota_timburke: +100!05:07
*** dmorita has quit IRC05:07
*** cebruns has joined #openstack-swift05:08
timburkei definitely like the idea of checking that both versions work05:12
timburkeanyway, i should be paying attention to my wife. g'night!05:16
ho_timburke: kota_: difference b/w v2/v3 is a domain concept support and this difference takes care of keystoneauth so if we make tests for v3, it also can cover swift (server side) behavior05:26
ho_timburke: good night!05:26
kota_timbirke: have a good night ;)05:27
*** nadeem has joined #openstack-swift05:36
notmynameho_: here's my slides (just finished v1 of them) http://d.not.mn/lca2016_ec_in_swift.pdf05:38
openstackgerritTim Burke proposed openstack/swift: Add delete markers to versioned_writes middleware  https://review.openstack.org/21492205:38
ho_notmyname: thanks!05:39
notmynameho_: like most of my presentation decks, this is supporting material rather than primary material. there will be a lot of words said around all the pictures05:39
notmynamebut you should be able to get the basic idea, I think05:40
notmyname(also, because you know swift very well ;-)05:40
ho_notmyname: i know your style and yeah i would like to get basic idea. btw the cat is so cute :-)05:41
notmynameheh05:41
notmynameho_: I've got a coworker who gets mad at me (jokingly) about my presentation style. he asks me, "you gave a presentation on this topic. can I see your slides, because I'm building something similar for someone". then I give him like one big, full-screen picture, and he's like, "what do i do with this?!"05:42
timburkenotmyname: what's the -1 on the graphs? 1MB segment size?05:42
*** trifon has joined #openstack-swift05:43
notmynametimburke: the graphs? on the math-y part?05:43
ho_notmyname: lol.05:43
kota_ho_: it seems done to setup keystone v3 in my env, but still rbac skipped.05:43
timburkeperformance graphs05:43
notmynameoh05:43
kota_ho_: any thought?05:43
timburkei suppose i should have said *-105:44
timburkeor xxx-105:44
notmynametimburke: yes. those were all 1MB segment sizes. (these are exactly the same things presented in tokyo with peluse_ on EC)05:44
*** nadeem has quit IRC05:45
notmynametimburke: it's the info doug produced with tests in our office lab05:45
timburkecool. just checking. bunch of labels for different EC modes, wanted to confirm what they meant05:45
notmynameyeah. refer back to "supporting info. john will say a lot of words"05:45
timburkenow i'm really going05:45
notmynamel-)05:45
notmynameme too. slides done enough that I need some wife time before I leave for 10 days ;-)05:45
notmynamegood night, all05:45
ho_kota_: did you comment out for all account in sample.conf?05:46
kota_notmyname: good night :-)05:46
kota_ho_: no?05:46
kota_ho_: just account605:46
kota_ho_: is it neccesarry to setup all accunts?05:47
ho_kota_: yep. the condition is L1068/L1078 in https://review.openstack.org/#/c/202411/20/test/functional/test_access_control.py05:48
ho_notmyname: good night!05:48
kota_which line?05:49
kota_ho_:^^05:49
ho_kota_: L1069 and L 107805:49
kota_ho_: gotcha05:50
ho_kota_: L75-89 is a list for users05:51
kota_i see05:52
kota_getting understand overview05:53
*** klrmn has quit IRC05:54
kota_ho_: do you have a plan to add docs like "access control tests requires all accounts through account1-6"?05:55
kota_ho_: otherwise, newbees seems to fall down same hole with me by just enabling account6 for access control test.05:56
kota_ho_: exactly, if reading code, we can find the condition but... not all.05:57
kota_not all developpers (or operaters, newbees)05:57
kota_just imho :P05:59
ho_kota_: i see. this explanation is only in test_access_control.py. it's better to have the explanation in sample.conf.06:00
*** haomaiwang has quit IRC06:01
kota_ho_: +106:01
*** haomaiwa_ has joined #openstack-swift06:01
ho_kota_: so far i don't have any plan for it but i will add it06:01
ho_kota_: s/don't/didn't/06:02
kota_thx :-)06:02
kota_now i'm setting up more users for testing =v=06:03
*** zarric has joined #openstack-swift06:03
*** dmorita has joined #openstack-swift06:04
*** ChubYann has quit IRC06:05
zarricHi Stackers, can I ask your help? Is it possible for swift to have one openstack user read-only access for the container while another user can do read-write(both users under same tenant)?06:06
kota_zarric: i think so06:08
kota_zarric: docs is here, http://docs.openstack.org/developer/swift/overview_auth.html06:08
*** dmorita has quit IRC06:08
*** trifon has quit IRC06:08
kota_but might depends on auth system.06:08
*** trifon has joined #openstack-swift06:09
kota_The included TempAuth also has the concept of admin and non-admin users within an account. Admin users can do anything within the account. Non-admin users can only perform operations per container based on the container’s X-Container-Read and X-Container-Write ACLs.06:09
kota_that is a line of the doc.06:09
zarric@kota, thanks for help. I ever tried with set the acl for the container to its owner tenant: self, the other user seems can still delete that container06:09
kota_non-admin user cannot do anything if he is not allowed to operate on specific container.06:10
zarricyes, the auth system I am using is Keystone06:10
zarricso for non-admin users can view the container objects?06:10
zarricif non-admin and admin both in the same tenant.. sorry for the silly question, I am new to swift.06:11
kota_i think, "cannot" but wait a minutes to make sure the code06:12
kota_looks like it's impossible to see both object-list and objects themselvs for non-admin user.06:15
kota_confirmed by tempauth, though.06:15
kota_sorry i'm not so familier with keystone.06:16
zarricthanks. I will try the keystone06:16
*** trifon has quit IRC06:18
kota_zarric: you could see around http://docs.openstack.org/developer/swift/overview_auth.html#access-control-using-keystoneauth06:19
kota_By default the only users able to perform operations (e.g. create a container) on an account are those having a Keystone role for the corresponding Keystone project that matches one of the roles specified in the operator_roles option.06:19
*** trifon has joined #openstack-swift06:19
kota_zarric: you could try some oparation with an user not in a projecto which have perator_roles.06:20
zarriclooks the normal user can delete the container created by other user if they are under the same project06:21
zarricoh, let me check the roles06:21
zarrica question, if the user's role is not belonging to any operator role, is he expect to see everything except creation?06:23
kota_not sure, but i didn't think so.06:24
kota_instuitively, an user which doesn't have operator role means equals to non-admin user...06:25
kota_ho_: thought?06:26
ho_kota_: oh, keystone related questions!06:27
kota_ho_: you know in detail rather than me :-)06:28
ho_kota_: ok, i will check questions.06:28
*** thumpba has quit IRC06:29
ho_zarric: "looks the normal user can delete the container created by other user if they are under the same project". i think it depends on roles which user has.06:30
*** trifon has quit IRC06:30
zarricho_, thank you. The non-admin role not list in operator roles can view only, correct?06:31
*** mrmoje has quit IRC06:31
ho_zarric: wait a minute. i'm in meeting :-)06:32
*** mrmoje has joined #openstack-swift06:33
*** thumpba has joined #openstack-swift06:34
*** trifon has joined #openstack-swift06:34
zarrictried with creation a new role (not list in operator), and user with that role seems would not able to view or create containers.. Will try grant the ACL06:35
*** gyee has quit IRC06:37
ho_zarric: it's not possible to view info. i think.06:38
zarricho_: even by certain configuration to allow to that tenant and user?06:40
zarrichmm...that seems to be not flexible, do you know any other approach that can make certain container read-only for the user under same account06:41
ho_zarric: sorry, i would like to say "it's not possible to view ..." for " The non-admin role not list in operator roles can view only, correct?"06:41
ho_zarric: if you use container acl, non-admin role can view container and objects.06:42
zarricok, let me try. thank you06:44
zarricho_: btw, do you know if there is some permission settings that can disallow the operator role to delete the container within the swift account06:45
zarricho_: I tried to use acl swift post "bbb" -r "6e5361c5a89f4841aeaba7d19637fee3:eb16568e11424cb1880f2d304feb579a,.rlistings" in the operator role to grant the non-admin role ,but the non-admin role fail to get the container name "bbb"06:48
kota_my openstack client doesn't support --domain option...06:52
*** rcernin has joined #openstack-swift06:53
kota_oh my. the newest 2.0.0 still doesn't have.06:54
ho_zarric: i'm not familier with swiftclient but it should be worked exectes swift post "bbb" -r "<project-id>:*,.rlistings" with operator_role then access the container/object with other users in same project06:55
zarricho_: I tried that either, but seems not work. If they are in different project(account), that seems work06:59
*** haomaiwa_ has quit IRC07:01
*** haomaiwang has joined #openstack-swift07:01
*** mrmoje has quit IRC07:03
ho_zarric: can i see your container setting (X-Container-Read after you set acl)?07:03
kota_ho_: sorry during answering, do you know how to set domain to keystone?07:04
*** mrmoje has joined #openstack-swift07:05
*** thumpba has quit IRC07:05
kota_ho_: openstack client doesn't look to support --domain option used in https://gist.github.com/eranrom/7c4c398ca4b7bb196fed07:05
*** dmorita has joined #openstack-swift07:06
*** thumpba has joined #openstack-swift07:06
kota_so i stuck at account4 setting...07:06
ho_kota_: i usually use cURL for it. few weeks ago I can not setup keystone with openstack-client so I switched to cURL07:07
kota_ho_: meh, ok. thx07:07
*** thumpba has quit IRC07:09
*** dmorita has quit IRC07:10
ho_kota_: you are welcome!07:11
zarrichi ho_, sorry for the delay. DEBUG:swiftclient:REQ: curl -i http://10.113.16.71:8080/v1/AUTH_6e5361c5a89f4841aeaba7d19637fee3/bbb -X POST -H "Content-Length: 0" -H "X-Auth-Token: 3a6e7da84f4b4ea386b3144145d5b0d8" -H "X-Container-Read: 6e5361c5a89f4841aeaba7d19637fee3:*,.rlistings"07:12
zarricDEBUG:swiftclient:RESP STATUS: 204 No Content07:12
ho_zarric: thanks. can i have head for the container?07:13
zarricNFO:requests.packages.urllib3.connectionpool:Starting new HTTP connection (1): 10.113.16.7107:14
zarricDEBUG:requests.packages.urllib3.connectionpool:"HEAD /v1/AUTH_6e5361c5a89f4841aeaba7d19637fee3/bbb HTTP/1.1" 204 007:14
zarricDEBUG:swiftclient:REQ: curl -i http://10.113.16.71:8080/v1/AUTH_6e5361c5a89f4841aeaba7d19637fee3/bbb -I -H "X-Auth-Token: a829c3717cf64bc69a571d3c5f3eab59"07:14
zarricDEBUG:swiftclient:RESP STATUS: 204 No Content07:14
zarricDEBUG:swiftclient:RESP HEADERS: [('Content-Length', '0'), ('X-Container-Object-Count', '0'), ('Accept-Ranges', 'bytes'), ('X-Container-Read', '6e5361c5a89f4841aeaba7d19637fee3:*,.rlistings'), ('X-Storage-Policy', 'Policy-0'), ('X-Container-Bytes-Used', '0'), ('X-Timestamp', '1453790251.80519'), ('X-Trans-Id', 'tx5c33018ad675460d8827f-0056a71cc6'), ('Date', 'Tue, 26 Jan 2016 07:14:15 GMT'),...07:14
zarric...('Content-Type', 'text/plain; charset=utf-8')]07:14
zarriclooks the format is a mess...sorry07:15
*** cbartz has joined #openstack-swift07:15
ho_zarric: then you executed get a object in the container with user who belongs to same project. right?07:16
ho_zarric: format is no problem. i could check ('X-Container-Read', '6e5361c5a89f4841aeaba7d19637fee3:*,.rlistings')07:17
zarricyes, the 403 is raise if I use another user in this project.07:18
zarricClientException: Account GET failed: http://10.113.16.71:8080/v1/AUTH_6e5361c5a89f4841aeaba7d19637fee3?format=json 403 Forbidden  [first 60 chars of response] <html><h1>Forbidden</h1><p>Access was denied to07:18
zarricwe are using kilo code base, does it matter?07:19
ho_zarric: the code is not change from kilo to master. it's not a problem. maybe problem is my understanding. let me check the code.07:23
ho_zarric: sorry, did you execute get account or get object?07:29
ho_zarric: i checked the code this case (get object) should work with the line (https://github.com/openstack/swift/blob/master/swift/common/middleware/keystoneauth.py#L389)07:29
zarrichi ho_, the file can be downloaded ...07:31
ho_zarric: does it mean worked as expected?07:32
zarricoh, looks swift list will fail, but swift list bbb can be success07:33
ho_zarric: :-)07:33
zarricthanks ho_, do you know if any way to restrict the operator role to delete some thing07:34
*** dmorita has joined #openstack-swift07:35
ho_zarric: i think swift doesn't have it. but in the future you can control the behavior per methods. maybe it solves your problem.07:37
zarricok, is there a BP in place? if convenient, maybe you can share to me?07:38
*** dmorita has quit IRC07:39
ho_zarric: this patch is abandoned but i will restore soon: https://review.openstack.org/#/c/149930/07:41
*** zaitcev has quit IRC07:42
zarricThank you ho_. Wish it be accepted soon07:45
ho_zarric: thanks!07:46
*** arnox has joined #openstack-swift07:48
*** mrmoje has quit IRC07:53
*** mrmoje has joined #openstack-swift07:55
kota_gave up, couldn't set available domain for my keystone...07:55
ho_oh, no....07:56
ho_kota_: this might help you (https://github.com/osanai-hisashi/vagrant-swift-all-in-one/blob/keystone-auth/scripts/register_keystone_data.sh)07:57
*** zhill has quit IRC07:59
*** haomaiwang has quit IRC08:01
*** haomaiwang has joined #openstack-swift08:01
*** hseipp has joined #openstack-swift08:08
*** thumpba has joined #openstack-swift08:08
*** thumpba has quit IRC08:09
*** rledisez has joined #openstack-swift08:11
*** geaaru has joined #openstack-swift08:23
*** mrmoje has quit IRC08:24
*** mrmoje has joined #openstack-swift08:26
*** dmorita has joined #openstack-swift08:47
*** natarej_ has joined #openstack-swift08:48
*** natarej has quit IRC08:49
*** jmccarthy has quit IRC08:49
*** jmccarthy has joined #openstack-swift08:50
*** dmorita has quit IRC08:51
*** haomaiwang has quit IRC09:01
*** haomaiwa_ has joined #openstack-swift09:01
*** joeljwright has joined #openstack-swift09:07
*** ChanServ sets mode: +v joeljwright09:07
*** jistr has joined #openstack-swift09:19
*** trifon has quit IRC09:27
*** trifon has joined #openstack-swift09:29
*** trifon has quit IRC09:36
*** trifon has joined #openstack-swift09:40
*** jordanP has joined #openstack-swift09:42
*** wer has quit IRC09:49
*** wer has joined #openstack-swift09:49
*** dmorita has joined #openstack-swift09:59
*** haomaiwa_ has quit IRC10:01
*** haomaiwang has joined #openstack-swift10:01
*** dmorita has quit IRC10:03
*** silor has quit IRC10:04
*** jamielennox is now known as jamielennox|away10:15
*** jamielennox|away is now known as jamielennox10:25
*** aix_ has quit IRC10:32
openstackgerritKota Tsuyuzaki proposed openstack/swift: CompositeRing Support  https://review.openstack.org/27192010:32
openstackgerritKota Tsuyuzaki proposed openstack/swift: WIP: Support EC duplication factor at reconstructor  https://review.openstack.org/23786710:40
openstackgerritKota Tsuyuzaki proposed openstack/swift: WIP: PUT/GET path for global ec cluster  https://review.openstack.org/21916510:40
*** ho_ has quit IRC10:42
*** acoles_ is now known as acoles10:47
*** SkyRocknRoll has quit IRC10:49
*** dmorita has joined #openstack-swift10:51
*** dmorita has quit IRC10:55
*** haomaiwang has quit IRC11:01
*** haomaiwang has joined #openstack-swift11:01
*** chlong has quit IRC11:05
openstackgerritAlistair Coles proposed openstack/swift: Merge branch 'master' into feature/crypto  https://review.openstack.org/27220111:05
*** chlong has joined #openstack-swift11:10
*** admin0 has joined #openstack-swift11:12
admin0any devs around :)11:12
admin0i got a question11:12
admin0if I add 1GB to a running swift cluster, does it mean shuffling around 1 gb to balance the 1gb added, or multiple GBs11:12
*** aix_ has joined #openstack-swift11:13
openstackgerritAlistair Coles proposed openstack/swift: Fix handling of "Permission Denied" error from NamedTemporaryFile function  https://review.openstack.org/27060711:28
*** km has quit IRC11:28
*** silor has joined #openstack-swift11:35
*** zmielna has joined #openstack-swift11:37
*** admin0 has quit IRC11:39
*** kei_yama has quit IRC11:41
*** m_kazuhiro has quit IRC11:41
*** admin0 has joined #openstack-swift11:49
*** haomaiwang has quit IRC12:01
*** haomaiwa_ has joined #openstack-swift12:01
*** dmorita has joined #openstack-swift12:03
*** mingdang1 has quit IRC12:07
*** dmorita has quit IRC12:07
*** daemontool has joined #openstack-swift12:14
*** admin0 has quit IRC12:19
*** admin0 has joined #openstack-swift12:24
admin0f I add 1GB to a running swift cluster, does it mean shuffling around 1 gb to balance the 1gb added, or multiple GBs12:26
tdasilvajrichli: around?12:32
*** mrmoje has quit IRC12:34
admin0tdasilva: are you a dev ? do you know about rebalancing ?12:43
admin0my question is if I add 1GB to a running swift cluster, does it mean shuffling around 1 gb to balance the 1gb added, or multiple GB12:43
admin0and if I add 1 more gb , does the reshuffeling of the same objects take place or different12:44
admin0is there a chain reaction ?12:44
*** daemontool has quit IRC12:55
*** mrmoje has joined #openstack-swift12:58
*** mingdang1 has joined #openstack-swift13:00
*** haomaiwa_ has quit IRC13:01
*** haomaiwang has joined #openstack-swift13:01
*** bill_az has joined #openstack-swift13:02
*** admin0 has quit IRC13:04
*** admin0 has joined #openstack-swift13:06
tdasilvaadmin0: the amount of data movement also depends on other factors as I understand it. for example, how much data in currently in the system. Generally, yeah, as you add more capacity, there will be data movement, but I don't think it will ever be more then the amount of data added, unless you screw up the ring configuration.13:09
*** mrmoje has quit IRC13:09
tdasilvaadmin0: here's some good reading on capacity mgmt: https://swiftstack.com/blog/2012/04/09/swift-capacity-management/13:09
tdasilvaadmin0: what objects get moved is really dependent on the ring13:10
tdasilvaadmin0: http://docs.openstack.org/developer/swift/overview_ring.html13:10
*** dmorita has joined #openstack-swift13:15
*** haomaiwang has quit IRC13:18
*** dmorita has quit IRC13:19
*** admin0 has quit IRC13:42
*** mingdang_ has joined #openstack-swift13:43
*** mingdang1 has quit IRC13:43
*** jordanP has quit IRC13:55
*** diogogmt has joined #openstack-swift13:57
*** aix_ has quit IRC14:00
*** aix has joined #openstack-swift14:02
*** admin0 has joined #openstack-swift14:03
*** proteusguy has quit IRC14:04
*** MVenesio has joined #openstack-swift14:07
*** haomaiwang has joined #openstack-swift14:10
*** jordanP has joined #openstack-swift14:11
openstackgerritMerged openstack/swift: Merge branch 'master' into feature/crypto  https://review.openstack.org/27220114:14
*** proteusguy has joined #openstack-swift14:16
openstackgerritMerged openstack/swift: Fix handling of "Permission Denied" error from NamedTemporaryFile function  https://review.openstack.org/27060714:17
*** diogogmt has quit IRC14:20
*** dslevin1 has quit IRC14:20
*** daemontool has joined #openstack-swift14:24
*** bill_az has quit IRC14:34
*** yarkot has quit IRC14:35
*** mingdang_ has quit IRC14:38
*** dmsimard is now known as dmsimard|afk14:39
*** daemontool has quit IRC14:43
*** coreycb` is now known as coreycb14:44
*** sgundur has joined #openstack-swift14:47
*** daemontool has joined #openstack-swift14:47
mahatic_acoles: hello, are you here14:55
mahatic_?*14:55
acolesmahatic_: hi14:57
mahatic_acoles: I was looking at this card, https://trello.com/c/v5koQkms/70-protect-against-imcomplete-read, I was wondering if you have more information on that?14:58
mahatic_acoles: Not sure if it helps, but I am encountering an IncompleteRead issue with encryption (while looking at some SLO test that was failing). But I can't figure why14:59
*** haomaiwang has quit IRC15:01
*** haomaiwang has joined #openstack-swift15:01
acolesmahatic_: looking15:01
*** dmorita has joined #openstack-swift15:02
mahatic_acoles: ok, thanks15:02
*** blmartin has joined #openstack-swift15:04
acolesmahatic_: that comment is on a stale review but still applies to this line https://github.com/openstack/swift/blob/feature/crypto/swift/common/middleware/encrypter.py#L115-11515:06
*** dmorita has quit IRC15:06
acolesmahatic_: the concern is that if readchunk never returns an empty chunk then the plaintext etag is never transformed to its hexdigest. i.e. if the caller for some reason does not call readchunk to consume all the body.15:07
mahatic_acoles: yeah, I did go the said review and looked at the line. Did it mean that line is expected to throw an IncompleteRead at some point?15:07
acolesmahatic_: no, i don't believe so. if the scenario occurred it would result in an invalid plaintext etag15:08
acolesmahatic_:  also remember this is in the PUT path - where is your test seeing an IncompleteRead?15:09
mahatic_acoles: https://github.com/openstack/swift/blob/master/test/functional/tests.py#L2709 -> if I remove "seg_info['seg_c']" from there, it throws me an IncompleteRead15:12
*** esker has quit IRC15:12
mahatic_acoles: also, if I do the same, without encryption in pipeline, it doesn't throw an error. It works fine15:12
*** aix has quit IRC15:12
*** esker has joined #openstack-swift15:13
*** aix has joined #openstack-swift15:13
mahatic_acoles: I am not sure as to when/why an IncompleteRead would occur15:13
*** esker has quit IRC15:14
*** zmielna has quit IRC15:14
*** esker has joined #openstack-swift15:14
acolesmahatic_: what throws the error? which func test and where? that line is in common setup for a bunch of slo tests15:15
mahatic_acoles: ah sorry, hold on15:15
mahatic_acoles: https://github.com/openstack/swift/blob/master/test/functional/tests.py#L280415:16
acolesmahatic_: ok, but is the error raised in the test client, or in the decrypter middleware, or proxy?15:19
acolesis it in a log file or in the func test error ?15:19
mahatic_acoles: test client. It is a func test error. Let me paste that15:20
acolesmahatic_: back in 5 mins15:20
mahatic_acoles: sure, thanks for looking. Here it is: http://paste.openstack.org/show/485015/15:21
*** lcurtis has joined #openstack-swift15:22
*** esker has quit IRC15:22
pchngmahatic_: I think the Swift server runs into the same or similar error I was getting when that test line is commented out. Let me post some server logs when I commented out that test line15:25
pchngThis is what I see from the Swift logs when I comment out that line in tests.py to remove seg_info['seg_c'] from the ranged-submanifest:15:26
pchnghttp://paste.openstack.org/show/485018/15:26
mahatic_pchng: that happens without commenting out anything as well right?15:27
pchngI have not debugged yet, but it looks like the same error I was getting with that functest before, i.e. the multipart functions in utils.py have trouble parsing the multiparts/byterange encrypted response15:28
pchngmahatic_: Correct, I see the same error in Swift logs without commenting out the line in tests.py, but the functests still fail. Let me post the original functest error15:29
pchngmahatic_: Here are the functest and Swift logs for that test ( test_slo_get_ranged_submanifest) without the line (seg_c) commented out: http://paste.openstack.org/show/485019/15:31
mahatic_pchng: yes, but if you look at my latest patch (decrypt multipart mime), I do the 'read' in it and multiparts/byterange is parsed ok. but if you test this https://github.com/openstack/swift/blob/master/test/functional/tests.py#L1661 without that patch, you'd see the same error as you are now with the func test error15:31
pchngslightly different Swift error, but same problem, "content-range" header can't be extracted from a part of the multipart/byteranges document.15:32
mahatic_pchng: but how come, I mean it is erroring out in test client itself, but logs show it's erroring in decrypter?15:33
pchngmahatic_: I have your latest patch I think15:33
*** mragupat has joined #openstack-swift15:33
pchngmahatic_: I think in both cases, the Swift server error causes the test to error, i.e. it doesn't even get to the point where it can assert/fail15:34
pchngWhen I debugged into this late last week (with your latest patch), it looked like utils._MultipartMimeFileLikeObject.read() was not returning the proper parts of the (encrypted) multipart document15:35
acolespchng: are you pastebin's from swift master or feature/crypto?15:36
pchngI don't know whether utils._MultipartMimeFileLikeObject.read() has trouble finding the boundaries when there is encrypted (i.e. raw bytes) in there15:36
pchngacoles: From feature/crypto with mahatic_ 's patch 248377. But I haven't pulled the latest from feature/crypto that has the merge from master this morning.15:36
patchbotpchng: https://review.openstack.org/#/c/248377/ - swift (feature/crypto) - Decrypt multipart mime doc15:36
acolesmahatic_: idk for sure but your IncompleteRead might be due to an incorrect content-length header which causes the client to attempt to read more data than there is to read??15:37
acolesmahatic_: pchng the other thing i notice is that func test uses a manifest that has one segment followed by sub-manifests, so the line you delete changes it to a manifest that only container sub-manifests15:38
acolesonly has*15:39
mahatic_acoles: hmm, why is it expecting more? It wasn't w/o encryption..15:39
acolesbah, "the line you delete changes it to a manifest that only contains sub-manifests"15:39
acolesmahatic_: a bug in the patch?15:40
pchngacoles: That's correct. We were investigating this functest failure: test_slo_get_ranged_submanifest(), I believe Mahatic was removing that segment just to see if it was the issue.15:40
pchngacoles: It's kind of complicated, but that test (test_slo_get_ranged_submanifest) results in a multi-range GET that is quite peculiar15:40
mahatic_acoles: :) content-length maybeed some probing15:41
mahatic_may need*15:41
pchngacoles: And that multi-range get is the one that fails when I debugged in. Basically there is an object of length 1048576 and the multi-range get asks for "all bytes and the last byte again"15:41
mahatic_acoles: it won't throw that error, if I remove anything else from that manifest except seg_info['seg_c'] , which is a bit confusing15:42
pchngI think the response to that ranged request (Range: bytes=0-1048575,1048575-), for some reason it isn't being parsed correctly by utils._MultipartMimeFileLikeObject.read()15:42
pchngI've put most of my notes on this here: https://trello.com/c/rPjrIefY/61-fix-functests-failures-in-slo-ranged-gets15:43
*** awelleck has joined #openstack-swift15:43
* mahatic_ is stepping away for a bit15:50
*** nadeem has joined #openstack-swift15:50
acolespchng: thanks, nice notes15:50
pchngacoles, mahatic_ : My notes can be kind of verbose and wandering. Let me know if something's unclear and I'll clarify it.15:51
acolesmahatic_: pchng how about putting some logging of the multipart headers at line 253 here https://review.openstack.org/#/c/248377/10/swift/common/middleware/decrypter.py before the call to parse_content_range, since it looks like the content-range header value is bad?15:52
acolesor perhaps the header is missing?15:53
pchngacoles: It's missing, basically none of the part's headers get returned by that iterator15:54
acolespchng: oic. and only when the segment content is encrypted?15:54
pchngUltimately, utils._MultipartMimeFileLikeObject.read() is responsible for parsing out the "pieces" of the multipart document, and when I debugged in, it appeared that it was not returning anything for the second part of the document, which results in the calling functions returning empty headers/body15:55
mahatic_acoles: pchng the value is none. But w/o encrption, it seems to take a range like this '0-0' well15:55
pchngacoles: It happens when encryption is enabled and this test passes without encryption I believe.15:55
*** garthb has joined #openstack-swift15:55
mahatic_pchng: note that the same function is responsible without encryption as well: https://github.com/openstack/swift/blob/master/swift/common/request_helpers.py#L41915:57
mahatic_that is called in SLO15:57
pchngacoles: I am sort of wondering whether the code in utils._MultipartMimeFileLikeObject.read() has trouble finding the boundaries when there is encrypted content (i.e. "raw" bytes) in the response: https://github.com/openstack/swift/blob/feature/crypto/swift/common/utils.py#L335615:57
mahatic_slo middleware*15:57
mahatic_pchng: well, in patch 248377 ,  utils._MultipartMimeFileLikeObject.read() seems to parse encrypted content15:58
patchbotmahatic_: https://review.openstack.org/#/c/248377/ - swift (feature/crypto) - Decrypt multipart mime doc15:58
pchngacoles, mahatic_: Do you know if this code would have any trouble/weirdness if `input_buffer` had raw bytes in it? `boundary_pos = self.input_buffer.find(self.boundary)`15:58
*** haomaiwang has quit IRC16:01
*** haomaiwa_ has joined #openstack-swift16:01
mahatic_in the submanifest, removing anything else other than seg_info['seg_c'], seems to pass the test. Which makes me wonder if there is any overlap?16:06
*** nadeem has quit IRC16:10
*** dmorita has joined #openstack-swift16:14
mahatic_acoles: you were asking about checking headers, this is what happens when I tried. I tried to summarize in a comment here from line 8 - 12: http://paste.openstack.org/show/485037/16:14
*** dmorita has quit IRC16:19
*** SkyRocknRoll has joined #openstack-swift16:19
acolesmahatic_: pchng so here's a hunch (well, I stared at the code a bit :)...how about if the decrypter does not read all the content of the first mime part? i.e. the first _MultipartMimeFileLikeObject is not fully read? the next instance of _MultipartMimeFileLikeObject to be yielded shares the same wsgi_input as the first, so will carry on yielding content from wherever the read got to on the first, which will not be where t16:20
acoleshe next boundary is expected (we didn't read that far)...16:20
acolesso the second call to parse_mime_headers will try to parse some of the first part's body :( and presumably not find any headers??16:20
*** admin0 has quit IRC16:22
acolesAnd then I see that in https://review.openstack.org/#/c/248377/10/swift/common/middleware/decrypter.py there is just one call to read() the mime part body and it only reads 65536 bytes, which doesn't seem right?16:22
*** tongli has joined #openstack-swift16:22
acolesline 257 in https://review.openstack.org/#/c/248377/10/swift/common/middleware/decrypter.py looks wrong - I'd expect to see repeated reads of the body until it is exhausted i.e. read returns ''16:24
*** mrmoje has joined #openstack-swift16:24
*** cbartz has quit IRC16:25
*** diogogmt has joined #openstack-swift16:26
acolesmahatic_: pchng its a complicated call path but at the bottom of this all there is a single wsgi input with a single read pointer and i think that when a _MultipartMimeFileLikeObject is instantiated there's a (reasonable) assumption that the read pointer has been left at the end of the last document part.16:26
*** geaaru has quit IRC16:27
* acoles thinks torgomatic would know16:27
*** chlong is now known as chlong_zzz16:28
pchngacoles, mahatic_ : i think that might be it, i.e. line 257 in https://review.openstack.org/#/c/248377/10/swift/common/middleware/decrypter.py, I think body.read() aka utils._MultipartMimeFileLikeObject.read() needs to be repeatedly called16:30
pchnguntil exhausted, otherwise the next utils._MultipartMimeFileLikeObject won't "start" at the right location16:31
pchngi.e. because of this: https://github.com/openstack/swift/blob/feature/crypto/swift/common/utils.py#L343216:32
pchngThe next _MultipartMimeFileLikeObject is based on the current state of input_buffer, if the previous _MultipartMimeFileLikeObject.read() wasn't called enough and didn't advance all the way, I'm not sure the next _MultipartMimeFileLikeObject() starts off properly.16:33
mahatic_sorry, I was away. Reading now16:34
acolespchng: yeah. you said it more succinctly ;)16:34
*** zaitcev has joined #openstack-swift16:35
*** ChanServ sets mode: +v zaitcev16:35
mahatic_acoles: pchng great! that sounds about (more than) correct16:37
*** stevemar_znc is now known as stevemar16:38
*** arch-nemesis has joined #openstack-swift16:38
notmynamegood morning16:40
mahatic_pchng: acoles but  instead of "utils._MultipartMimeFileLikeObject.read() needs to be repeatedly called", I think it should be corrected in the way it is only reading 65536 bytes in  line 257 in https://review.openstack.org/#/c/248377/10/swift/common/middleware/decrypter.py16:41
mahatic_?16:41
pdardeau:q16:42
*** arch-nemesis has quit IRC16:43
*** arch-nemesis has joined #openstack-swift16:43
*** diazjf has joined #openstack-swift16:44
acolesmahatic_: you will need to call it repeatedly with some reasonable chunk read size until there's no more to read. You don't want to call it once with the expected doc part length because that could be large and you don't want to read it all in one piece.16:46
acolesmahatic_: if you want to confirm my hunch then i guess you could change 65536 for some bigger number (> expected part length) to see if the test then passes. But that doesn't feel like the correct way to go.16:48
mahatic_acoles: yeah. sure, I'll just do that to test it out. Of course, won't be the fix :)16:49
pchngacoles, mahatic_: Maybe make def decrypt_part_iter() yield the decryption of each chunk of body.read()?16:50
pchnggood idea to test it first though by reading everything16:50
*** mrmoje has quit IRC16:50
pchng(i.e. put the body.read() call inside of decrypt_part_iter )16:51
acolespchng: +1 that method doesn't look like a generator right now, should probably take the doc body and yield decrypted chunks16:51
mahatic_pchng: yup16:51
mahatic_acoles: confirmed your hunch :)16:57
*** trifon has quit IRC16:57
acolesmahatic_: cool!16:58
mahatic_pchng: ^16:58
pchngmahatic_, acoles: Nice!!!16:58
*** haomaiwa_ has quit IRC17:01
*** haomaiwang has joined #openstack-swift17:01
*** Jeffrey4l has quit IRC17:02
*** diazjf has quit IRC17:03
*** diazjf1 has joined #openstack-swift17:03
*** diogogmt_ has joined #openstack-swift17:04
*** garthb_ has joined #openstack-swift17:05
*** garthb has quit IRC17:07
*** stevemar has quit IRC17:07
*** diogogmt has quit IRC17:07
*** diogogmt_ is now known as diogogmt17:07
*** zaitcev has quit IRC17:07
*** zaitcev has joined #openstack-swift17:07
*** ChanServ sets mode: +v zaitcev17:07
*** stevemar_znc has joined #openstack-swift17:08
*** jordanP has quit IRC17:15
*** rledisez has quit IRC17:16
*** openstackgerrit has quit IRC17:17
*** openstackgerrit has joined #openstack-swift17:17
*** SkyRocknRoll has quit IRC17:23
*** jmccarthy has quit IRC17:24
*** jmccarthy has joined #openstack-swift17:24
*** stevemar_znc has quit IRC17:30
*** sw3 has quit IRC17:30
*** dmsimard|afk has quit IRC17:30
*** EmilienM has quit IRC17:30
*** aix has quit IRC17:30
timburkegood morning17:32
*** dmsimard has joined #openstack-swift17:34
*** stevemar_znc has joined #openstack-swift17:34
*** EmilienM has joined #openstack-swift17:34
*** sw3 has joined #openstack-swift17:37
tdasilvatimburke: o/17:37
*** dmorita has joined #openstack-swift17:42
*** dmorita has quit IRC17:43
*** diogogmt has quit IRC17:44
*** klrmn has joined #openstack-swift17:51
openstackgerritMahati Chamarthy proposed openstack/swift: Decrypt multipart mime doc  https://review.openstack.org/24837717:51
mahatic_acoles: pchng ^^17:51
openstackgerritMerged openstack/swift: Port swift.common.utils.Timestamp to Python 3  https://review.openstack.org/23701517:51
*** diazjf1 has quit IRC17:52
mahatic_okay, I'm off to bed17:54
*** nadeem has joined #openstack-swift17:55
*** nadeem has quit IRC17:56
*** dmorita has joined #openstack-swift17:56
*** nadeem has joined #openstack-swift17:57
*** diogogmt has joined #openstack-swift17:58
*** haomaiwang has quit IRC18:01
*** haomaiwang has joined #openstack-swift18:01
acolesmahatic_: g'night18:04
pchngmahatic_: Thanks! have a good night!18:06
*** jistr has quit IRC18:11
*** arnox has quit IRC18:15
*** mgarza has joined #openstack-swift18:19
*** stevemar_znc is now known as stevemar18:20
*** hseipp has quit IRC18:40
*** ChubYann has joined #openstack-swift18:43
*** mrmoje has joined #openstack-swift18:47
*** admin0 has joined #openstack-swift18:57
*** diazjf has joined #openstack-swift18:58
*** haomaiwang has quit IRC19:01
*** haomaiwang has joined #openstack-swift19:01
*** zhill has joined #openstack-swift19:02
sgundurwith the current repo of Swift , upon python setup.py develop getting the error -19:15
sgundurpkg_resources.RequirementParseError: Expected ',' or end-of-list in dnspython>=1.12.0;python_version<'3.0' at ;python_version<'3.0'19:15
sgundurhttp://paste.openstack.org/show/485062/19:15
sgunduranyone come across similar issues?19:15
admin0if i add 1gb storage to an existing openstack network, does it reshuffle just 1gb around or does it fire a chain reaction ?19:15
admin0[7:58pm]19:15
jrichlisgundur: update pip pbr setuptools and make sure there is not a version owned by the OS that eclipses the more recent version19:19
sgundurjrichli: thanks, I ll try that19:20
ahaleadmin0: your 1GB would have a weight in proportion to other storage, and the weight would decide how many "partitions of ring" that 1GB gets assigned, then one replica of that many partitions would get moved to the new storage from across the rest of the drives in the cluster.19:21
admin0ahale: if i paste you my ring privately, would you be able to guide ?19:21
ahalenot really, its pretty late and im getting drunker by the moment!19:22
admin0:)19:22
admin0i need to drop 100TB to an existing ring .. and i am looking for the best options19:22
*** MVenesio has quit IRC19:24
claygpeluse_: boooooooooh19:24
ahaleah fun times :) hmm yeah the docs dont really talk much about best practices etc19:24
claygahale: stupid docs19:24
ahalei learnt recenty having unbalanced zone weights is pretty bad19:24
ahaleclayg: yah indeed if only some ops guy would write some more19:25
claygahale: can we change the docs to "before you do anything *stupid* - you should check with ahale"19:25
ahale!19:25
* glange seconds19:25
ahalei do plenty stupid :) see comment ^^ about unbalanced zones19:25
admin0ahale: sent you a PM with the current weights19:26
admin0yeah so my only worry is that if I drop 1 TB, it starts doing a chain reaction from everywhere19:26
notmynamewhen dealing with unbalanced zones, it's a good idea to use the latest versions of the code. clayg fixed/improved a lot of that recently19:27
*** okdas has quit IRC19:27
*** okdas has joined #openstack-swift19:27
*** okdas has joined #openstack-swift19:27
notmynameadmin0: best practice is to add that gradually (in proportion to the rest of the cluster -- eg 1TB in a 10TB cluster is a big deal, not so much in a 50PB cluster)19:27
ahalenotmyname: i experimented with master as of friday :)19:28
notmynameand it's awesomer right? ;-)19:29
ahalewelll...19:29
ahalehandoff is quite ugly :)19:29
notmynamebut is it worse?19:30
ahalei think its the same19:30
notmynamewinnig!19:30
ahalethe maths matches my prod graphs19:30
notmynameahale: you're coming to bristol, right? we need you to knock us in the head a bit ;-)19:31
ahaleim not yet, i'd like to19:32
*** trifon has joined #openstack-swift19:32
ahalei wasnt sure if i would be in the way or anything, not being awesome at code - and then saw ireg was closed19:34
*** diogogmt has quit IRC19:35
claygacoles: nice work on patch 270607 - a fixup and a +A that's how to get shit done19:37
patchbotclayg: https://review.openstack.org/#/c/270607/ - swift - Fix handling of "Permission Denied" error from Nam... (MERGED)19:37
*** daemontool_ has joined #openstack-swift19:39
claygahale: having unbalanced zone weights where # of zones == # of replicas is *terrible*19:40
ahalei would maybe go as far as TERRIBLE19:40
claygnotmyname: is right that the latest ring fixes were specifically going after problems that we saw as a result of unbalanced failure domains - and I think it acctually does the absolute very best possible thing - the replica_part_planner sort of enumerates what the "optimum" placement would be for a given topology even before we start putting parts out there19:41
ahaleso my example - 5 zones. 4 have 2 nodes,  z1 has 1 node. all boxes have same weight. node in z5 goes down. amount of handoff going to z1 is same as handoff to z2 despite half aggregate zone weight19:41
claygso unless we change the definition of what's the best possible placement - the current code is correct (I'm not sure that can be said for any previous version of balancing)19:42
ahaleah good point , i should def rebalance with latest patch tho and retest19:42
claygahale: that's weird about the handoffs acctually :\19:43
*** daemontool has quit IRC19:43
notmynamethat's separate than balance19:43
claygahale: handoffs should be proportionate to the number of parts assigned in the that failure domain19:43
notmyname /undo19:44
claygnotmyname: well maybe torgomatic should enlighten us - he just looked at that code - but when he *explained* it to me it sounded like you sort of psudeo-randomly grab a part and see if the device assigned for that replica is "suitable" (i.e. in a zone you haven't used yet)19:46
notmynameyeah, I think that's true too19:46
acolesclayg: heh. once I see it my OCD makes me just have to fix it19:46
claygacoles: i *love* me some acoles OCD!19:46
notmynameI was thinking that it's separate from balance, because maybe get_more_nodes is doing something different (eg not respecting weights or soemthing). but if it's "just" a walk around the ring, then yeah it's also what you said--proportional to the weight of that failure domain19:47
notmynameor maybe both things are true ;-)19:47
acolesclayg: btw had a 'murican colleague here today giving me 1:1 tutoring on usage of the word 'down' :P19:48
*** diogogmt has joined #openstack-swift19:49
ahaleyah honestly not sure what its doing , or if all that is still valid - its not a super recent ring-builder generated ring19:49
*** joeljwright has quit IRC19:50
notmynameyeah it would different with a different ring (ie rebalance with new code should give better/different results)19:51
claygacoles: I would have been down to here that, i'm feelings on using slang in irc have been fairly down lately19:52
admin0trying to use swift-dispersion-populate and I get this: AttributeError: 'NoneType' object has no attribute 'rsplit'19:53
claygadmin0: stupid None's they *never* seem to have the attribute's you need19:55
claygI could fix like 99% of of all python tracebacks if I could implement getattribute on None, sigh19:56
notmynameI suppose a very evil code obfuscation would be to replace None with a magicmock19:56
claygnotmyname: you get total hacker creds if you could make that happen __builtins__ maybe?19:57
notmynameyeah, the "is" might be tricky. but the result would be totally evil19:58
notmynameie worth it ;-)19:58
*** rcernin has quit IRC19:58
notmynameit's nothing. it's everything. it's anythign you want. it would be very zen19:58
admin0ERROR: swiftclient missing, only auth v1.0 supported19:59
admin0boo19:59
admin0hmm ..19:59
*** pgbridge_ has quit IRC19:59
claygi would have swore someone fixed swift-dispersion to work with keystone (probably chmouel)20:00
admin0i do not have v1.0 of the api20:00
claygadmin0: can you install swiftclient?20:00
admin0i can try20:00
*** haomaiwang has quit IRC20:01
admin0pip install openstack-swiftclient ?20:01
admin0python:)20:01
*** haomaiwang has joined #openstack-swift20:01
claygwerd20:01
admin0its installed20:02
admin0now ?20:02
admin0its installed in my laptop inside a virtualenv and I have auth using my credentials20:02
admin0can i still do the disperson thing ?20:03
sgundurjrichli: thanks, that solved the issue and tests passed too!20:03
claygsure give it a shot - you need your rings tho - i'm not sure 100% running from your laptop is the best plan - but who knows20:03
claygadmin0: you might try to do all of this in a swift-all-in-one first20:03
claygadmin0: i'm not 100% sure that swift-dispersion isn't an entirely flakey beast20:04
admin0i installed python-swiftclient .. can’t find that command :20:04
notmynamesgundur: did you run into that based on the SAIO docs? if so, we should update them20:04
admin0pip freeze:  python-openstackclient==2.0.0   python-swiftclient==2.7.020:05
*** dmorita has quit IRC20:05
claygsgundur: oh yeah we know the saio docs are broken - because I just had to do stuffto like pin pip and shit20:05
clayg... on vsaio20:05
notmynameclayg: ah ok.20:06
notmynamethat needs to be written down somehwere. I'm happy to do it (but I'm not going to right this moment)20:07
openstackgerritMerged openstack/swift: Update AUTHORS  https://review.openstack.org/27102720:07
admin0installed pip installed siwft as well .. dispersion tool still missing20:07
admin0humm.. tryign hard20:07
notmynameworst patch ever20:07
claygnotmyname: yeah we talked about it in channel - maybe with pchng or zaitcev - not sure who or what happened20:08
ZyricGood morning20:08
notmynamehello Zyric20:08
admin0figured out what to do .. isntalling :)20:09
claygoh, or maybe the part that was busted was like swift-bench or somebody had some old version of pbr in it's requirements some how?20:10
zaitcevI continue to endeavour to package everything for users, so they should never need pip, so their /usr is never polluted and issues with requirements.txt do not matter.20:10
claygswifterdarrell: looks like https://github.com/pypa/pip/issues/3384 has been fixed/closed testing w/ pip 8.0.2 now20:10
claygzaitcev: you're doing the lords work my friend20:11
sgundurclayg: yeah, I had seen that pbr update soln here https://review.openstack.org/#/c/207790/ but till jrichli pointed , didn't occur20:11
zaitcevclayg: it may be an obsolete approach in the age of containers20:11
*** diazjf has quit IRC20:11
claygzaitcev: oh gosh - you don't believe that20:11
admin0guys, what module am I missing here ? http://pastebin.com/5iwF5LmU20:12
claygzaitcev: you're just trying to be provocative20:12
claygadmin0: a module named internal_client obviously20:12
zaitcevclayg: Indeed I don't use containers for development when I hack on Swift, but users ask often about some kind of Docker images or other. Apparently it's convenient and I do not presume to know better.20:13
claygadmin0: so swift-dispersion-populate needs to have *swift* installed - which is a disator because you're going to have to get pyeclib installed too - which is going to need to have liberasure's .so - which on a laptop/mac you'll probably have to compile by hand20:13
Zyricswift20:13
admin0i am going to fire up a vagrant ubuntu and try from there20:14
claygadmin0: vagrant you say!?  http://docs.openstack.org/developer/swift/associated_projects.html#developer-tools20:15
admin0:D20:15
* clayg be big p1mpin'20:15
*** pgbridge_ has joined #openstack-swift20:16
claygtdasilva: you still working on the ansible swift stuff?  I was starting up an unrelated project the other day and needed some provisioning foo...20:16
claygtdasilva: I ended up going with chef (devil you know) but I was *really* tempted to dive into some ansible20:17
claygtdasilva: I think you said you didn't have much experience with chef - but IME now one who uses it really *loves* it - which I'm not sure is the case for ansible users20:17
ahaleclayg: if you want to live dangrously i believe openstack-ansible installs chef to isntall swift20:17
claygahale: of course it does20:18
admin0slow download :)20:20
ahaleoh no it actually looks a bit smarter now, thats good :)20:20
*** diazjf has joined #openstack-swift20:31
*** dmorita has joined #openstack-swift20:32
admin0auth_user = test:tester  — is this tenantID:username ?20:32
*** rcernin has joined #openstack-swift20:32
onovyhi, patch 258158 anyone? :)20:32
patchbotonovy: https://review.openstack.org/#/c/258158/ - swift - Keystone middleware deprecated option is_admin rem...20:32
claygadmin0: I think it mostly just works however swiftclient works20:33
admin0http://pastebin.com/HRc5BnbP — new error20:34
admin0sorry my mistake20:35
admin0single space in front of the variables20:35
admin0yay20:36
clayglol20:36
admin0the command works20:36
admin0but .. is the dispersion-report immediate ?20:36
claygwat?20:36
admin0http://pastebin.com/1cbSTtwm20:37
admin0the populate and report20:37
admin0openstack contailer list — i can see that the dispersion_0_x  containers are created20:39
admin0how long does it take for the report to find it out ?20:39
admin0oh20:40
admin0oh20:40
admin0 i did a —debug20:40
admin0its creating in public opestack, querying local disks for it20:41
admin0doh!20:41
openstackgerritAlistair Coles proposed openstack/swift: Copy more headers when copying object  https://review.openstack.org/27272420:43
claygMOAR20:43
admin0how do I tell swift-dispursion-report in aio to not query locally, but read the /etc/swift/dispursion.conf file ?20:43
admin0http://pastebin.com/JJwShLwV  — the report is querying locally .. not reading the values in the conf20:44
claygUsage: swift-dispersion-populate [options] [conf_file]20:45
claygmaybe?20:45
admin0the populate worked .. it created in the right cluster20:45
claygcongradulations?20:45
admin0not yet .. report is not working :)20:46
admin0so yes, they are created ..20:46
admin0but i cannot see the reports20:46
acolestdasilva: this patch 272724 relates to what you are doing with versioning in patch 26017920:46
patchbotacoles: https://review.openstack.org/#/c/272724/ - swift - Copy more headers when copying object20:46
patchbotacoles: https://review.openstack.org/#/c/260179/ - swift - decouple versioned writes from COPY20:46
admin0because the report is not reading the config file and just querying locally20:46
acolestdasilva: because your decoupled version copying should probably also copy more headers than master does right now20:47
admin0clayg:  swift-dispersion-populate  did it work, but swift-dispersion-report polls locally only  .. so 1/2 happy :)20:49
*** acoles is now known as acoles_20:51
*** zul has quit IRC20:52
admin0anyone can help me further .. on how to get dispersion-report on saio query/read from the conf file ?20:54
*** diazjf has quit IRC20:54
claygdid you try passing the config file to the script on the command line as an arg as described in the --help?20:56
admin0clayg: yes20:58
admin0but it still queries local20:58
admin0http://pastebin.com/fZfX3LdD20:58
claygadmin0: what is the 'swift_dir' in the conf (defaults to /etc/swift) - and what is the output of swift-ring-builder <ring.builder> for the rings in that dir?21:00
*** daemontool has joined #openstack-swift21:00
claygfwiw it's not dispersion-report that makes up those 127.0.0.1 address - those comes from rings - not sure if it's the rings you want to use or not21:00
*** haomaiwang has quit IRC21:01
admin0clayg: this aio is inside my virtualbox .. i just passed around the URL21:01
admin0oh21:01
*** haomaiwang has joined #openstack-swift21:01
admin0so popupate works with just the 4 lines in dispersion.conf and populates remotely, but  report needs access to the ring-builder21:02
admin0does it also need ssh access to the machines ?21:02
admin0or just the ring builder files ?21:02
claygadmin0: it needs to talk to the backend storage services - that's what it does - why are you using this tool?21:02
claygadmin0: not ssh - just the ip/ports of the storage servers - it would live in the same space as your proxies21:03
claygwell except probably not attached to the outward facing network21:03
admin0clayg: i need to add 4 new storage-servers to a already 20+ node cluster .. so before adding, I want to use this tool to check the process21:03
*** daemontool_ has quit IRC21:03
admin0“clayg: admin0: not ssh - just the ip/ports of the storage servers - it would live in the same space as your proxies”  — this makes it much clear21:04
claygok, great - have you read http://docs.openstack.org/developer/swift/admin_guide.html?highlight=dispersion#cluster-health carefully?  i feel like it gives a good overview and says "These tools need direct access to the entire cluster and to the ring files (installing them on a proxy server will probably do)."21:05
*** diazjf has joined #openstack-swift21:06
mattoliveraumorning21:07
*** daemontool_ has joined #openstack-swift21:07
pdardeaugood morning mattoliverau21:07
*** esker has joined #openstack-swift21:08
*** silor has quit IRC21:10
*** daemontool has quit IRC21:10
admin0clayg: my proxy gives: ./swift-dispersion-report AttributeError: 'NoneType' object has no attribute 'rsplit'21:11
admin0account = url.rsplit('/', 1)[1]21:13
admin0so i was trying to use the remote keystone url as well21:16
admin0i switched to localip:port where the proxy was listening to21:16
admin0and now checking21:16
admin0clayg: i have the error output and the ring output here: http://pastebin.com/GfbvfMU621:20
*** bsdkurt has quit IRC21:22
admin0nvm .. i was doing it wrong21:24
admin0the dispursion-populate was done on the saio, so the report was getting it wrong21:25
admin0thank you guys .. this tool is finally working for me :)21:26
claygwell, the output from your -report is showing me that it's not getting account name from the auth_url correctly - i'm not sure exactly what your keystone endpoint is returning storage_url wise21:26
claygit looks like maybe it's not robust to a storage_url that ends in a slash21:26
claygadmin0: yeah it's not terribly ergonomic - and in almost all cases whatever tracebacks you're seeing point to some error handling that needs to be improved21:27
claygadmin0: you could pay back the favor by filing bugs -> https://bugs.launchpad.net/swift/+filebug21:27
*** rcernin has quit IRC21:28
claygadmin0: also if there's any wording that could be strengthend in the doc (patches would be most appreciated) -> https://github.com/openstack/swift/blob/master/doc/source/admin_guide.rst#cluster-health21:29
claygyou can get started here -> http://docs.openstack.org/developer/swift/first_contribution_swift.html21:30
claygadmin0: glad you got it working21:30
admin0not fully .. the command works21:30
admin0report still shows the same error like i pasted, but now 5000x times21:31
admin0becasue its now doing Created 5242 containers for dispersion reporting, 1m, 0 retries21:31
claygadmin0: if you do a `swift stat -v` does your StorageURL end in a /21:31
admin0the swift tool is not installed in the proxy virtualenv :21:33
claygadmin0: then how are you hitting the auth v2.0 endpoint?21:33
admin0in the dispersion.conf, i changed the url to point the local ip and port where swift-proxy was listening on21:34
admin0coz i could not reach the v221:34
claygadmin0: I don't think that configuration is supported - it's currently expecting to get the account name from the auth details returned from the auth endpoint21:35
admin0this cluster is not recent .. icehouse21:36
claygadmin0: I don't really know if that's relevant, the swift-dispersion-* tools are ancient21:38
claygadmin0: so did you find some auth creds that work against the proxy directly - or are you still authing against your keystone - i'm confused21:38
admin0against the proxy directly21:39
admin0but using the keystone user/pass/tenant setting21:39
claygthat doesn't make sense21:40
admin0clayg: here is my config: http://pastebin.com/5PWGHvxV21:41
claygthere's no good reason for the /auth end point on your proxy to respond to anything if you're using keystone21:42
claygadmin0: do you have tempauth installed in the pipeline as well - or swauth or something?  grep pipeline /etc/swift/proxy-server.conf21:42
admin0pipeline = catch_errors healthcheck cache swift3 s3token basicauth authtoken keystone staticweb formpost tempurl proxy-logging proxy-server21:43
claygadmin0: so i'd guess basicauth is responding to the request with some sort of storage url - that's not stock code tho - you should debug with curl21:44
admin0so for this to work correctly, i need to install swift client also21:44
admin0to use v2 auth21:44
claygadmin0: the swift-dispersion-* tools don't really care what account you use - but you need either a valid auth v1.0 or v2.0 response21:45
admin0ok21:45
claygyou're getting *something* from the v1.0 endpoint on your cluster (probably from whatever basicauth is) - you can probably adapt to use that21:45
claygcurl -i -H "X-Auth-User: <USERNAME>" -H "X-Auth-Key: <PASSWORD>" <AUTH_URL> <- fill in with what you have in your conf, see what comes back21:46
admin0HTTP/1.1 401 Not Authorized Invalid credentials    :D21:47
claygi wonder if simpleclient's get_auth could be so stupid21:48
admin0my mistake .. got somethign back: http://pastebin.com/5tRvNvmW21:49
claygidk, urllib seems like it would raise a HTTPError for 40121:53
claygwtf, that's not auth v1.021:54
admin0that is what i got back .21:54
claygadmin0: well go find a developer and hit them on the head - having something answer a v1.0 auth request with something other than a v1.0 auth response is an asshole move21:55
clayg'https://xxx.public.url/'.rsplit('/', 1)[1] == ''21:55
clayg^ explains the "missing" account21:55
claygadmin0: can you *use* that token it's giving you to head your account (the storage url returned from the keystone server)21:56
admin0to head my account :D ?21:56
admin0how does that translate to in curl :D ?21:56
clayghttp://developer.openstack.org/api-ref-objectstorage-v1.html#showAccountMeta21:57
admin0aha :)21:57
claygyou can get the $publicURL as the StorageURL returned from `swift stat -v` on a host that can hit your Keystone endpoint21:58
claygadmin0: you might could also ask whoever wrote basicauth if there's a way to get it to return a realistic storage url with an account prefix?21:58
admin0i was able to do swift stat -v from my client22:00
*** haomaiwang has quit IRC22:01
claygyou might have this -> https://github.com/CloudVPS/swift-basicauth/blob/master/swift_basicauth/middleware.py ???22:01
claygmaybe the storage_url_template config option is boo-berries22:01
*** 21WAAWT67 has joined #openstack-swift22:01
clayghrmm... seems undocumnted - i don't really know what's going on with that middleware22:02
admin0this is swift stat -v http://pastebin.com/q4eTYsWy22:03
openstackgerritJanie Richling proposed openstack/swift: Support for http footers - Replication and EC  https://review.openstack.org/23739322:05
claygok, yeah that StorageURL is not compatible with the account parsing in the swift-dispersion-* tools22:06
claygadmin0: neat trick getting the account in the hostname tho22:06
*** diazjf has quit IRC22:07
admin0hmm.. so is there any other way for me to use the swift-dispersion-tools ?22:07
*** mrmoje has quit IRC22:08
claygadmin0: you could try something like this patch to make the account parsing work with your crazy auth schema -> https://gist.github.com/clayg/61db02d7aa82d06c8f2922:09
claygI'm not even sure how to address that in the general sense :\22:09
*** diazjf has joined #openstack-swift22:10
admin0clayg: it helped in the sense it did not break .. result: http://pastebin.com/xmQseb1222:13
admin0how do I cleanup a populate ?22:14
admin0beause i used the aio and this , i think there is this overlap22:14
admin0nvm, using a loop to delete them22:17
*** daemontool has joined #openstack-swift22:23
*** daemontool_ has quit IRC22:27
*** trifon has quit IRC22:29
admin0clayg and ahale : thank you sirs :)22:33
claygnotmyname: admin0's storage_url was configured to return just 'https://<account>.host.name/' - i can't even imagine how many places something has assumed storage_urls were always in the form https://storage.example.com/v1/<account> - but on the other hand there's probably just as many places we assume authenticated requests go to <storage_url>/<container>/<object> - i'm not sure which assumption is wrong - does v1.0 api requ22:39
*** daemontool_ has joined #openstack-swift22:39
claygor does v1.0 api treat storage_url as a opaque endpoint that serves as the root of your account?22:40
clayg*surely* the /v1 part is part of the api spec?  and it's just a happy coniencidence that most clients treat is an opaque root?22:41
admin0clayg: question is for me or notmyname ?22:41
*** daemontool has quit IRC22:42
notmynamehmmm22:49
admin0this might be interesting for you guys: http://pastebin.com/sSwxfiaS    openstack object list container-name —debug22:49
notmynamethere's a ton of places in the code where we split_path to get back version, account, container, obj22:49
notmynameand yeah. wasn't there a patch within the past year about making sure that part of the path is actually a valid string?22:49
claygnotmyname: oh good point - how is that even working - clients aside - swift should balk at that!22:50
notmyname /v1/ is very much part of the api, IMO22:50
admin0i use the python-openstackclient .. just my auth .. do swift operations and it seem to work just fine with our url scheme .. i do not see the v1/v2 anywhere22:51
admin0like i listed in the paste above ^^22:51
*** mragupat has quit IRC22:53
claygnotmyname: myabe something with the cname resolver is doing path manipulation?22:53
*** awelleck has quit IRC22:53
clayg[21:57]       admin0 | pipeline = catch_errors healthcheck cache swift3 s3token basicauth authtoken keystone staticweb formpost tempurl  proxy-logging proxy-server22:55
claygnotmyname: ^ dunno pipeline looks sane except for whatever basicauth is doing?22:56
claygnotmyname: I found https://github.com/CloudVPS/swift-basicauth/blob/master/swift_basicauth/middleware.py but i'm not sure that's the same thing as admin0 is running22:56
admin0i can look .. how/were do i verify that ?22:56
clayganyway it doesn't seem to do anything with evn['PATH_INFO'] that would "fix" the path coming in w/o the /v122:57
claygpython -c 'import swift_basicauth; print swift_basicauth' maybe?22:57
*** asettle has joined #openstack-swift22:58
admin0<module 'swift_basicauth' from '/usr/local/virtualenvs/swift-proxy/local/lib/python2.7/site-packages/swift_basicauth/__init__.pyc'>22:59
admin0is the output22:59
*** forcebanana has joined #openstack-swift23:00
claygadmin0: maybe head /usr/local/virtualenvs/swift-proxy/local/lib/python2.7/site-packages/swift_basicauth/middleware.py - see if its about the same as https://github.com/CloudVPS/swift-basicauth/blob/master/swift_basicauth/middleware.py23:00
*** 21WAAWT67 has quit IRC23:01
claygadmin0: although like I said - that CloudVPS thing doesn't seem to doing everything that would be needed to make your storage_urls work the way they do - so it's sort of confusing23:01
*** haomaiwang has joined #openstack-swift23:01
*** dmorita has quit IRC23:04
admin0md5sum matches :)23:04
admin0its the exact23:04
openstackgerritDarrell Bishop proposed openstack/swift: Allow IPv6 addresses/hostnames in StatsD target  https://review.openstack.org/27099123:04
claygadmin0: well i guess that answers that question - idk, maybe in icehouse it works somehow - very strange - you say the dispersion tools worked for you?  You're good?23:05
admin0the dispersion-populate worked23:05
admin0the report did not23:06
clayglol23:06
*** dmorita_ has joined #openstack-swift23:06
admin0so yes, i have containers and objects all over the cluster .. but no clue how to check status when i add nodes , remove nodes etc :)23:06
claygmaybe my little diff/hack didn't quite cut the mustard23:06
*** blmartin has quit IRC23:06
admin0it helped that it at least tried to work , but still does not find23:07
claygwhat the delta was for report - wasn't it?23:07
admin0http://pastebin.com/xmQseb1223:07
admin0yes.. it passed on and did not break looking for account23:07
admin0but i think it still expects the storage path with someting /v1 etc which we do not have ?23:08
*** km has joined #openstack-swift23:10
*** tongli has quit IRC23:11
claygadmin0: yeah idk, direct_client path normally looks like HEAD /sdb2/996/AUTH_test/foo - maybe in your system it's different?  you're probably too far off the rails23:12
clayg... you could check your storage logs23:13
torgomaticpop quiz... when you see some stupid behavior in the code, do you (a) fix it, (b) fix it and write a test, or (c) write a test ensuring that the stupidity persists?23:13
*** tongli has joined #openstack-swift23:13
torgomaticTRICK QUESTION! I'm in here ranting, so you know the answer must have been C!23:13
claygtorgomatic: hehe, how stupid we talking about here?23:15
torgomaticthis particular example is small, but obvious... you make a call to get_container_info(..., swift_source='MC') and then assert that the logged swift sources were ['GET_INFO', 'MC']23:15
torgomaticand it's obvious that some plumbing is missing since that GET_INFO thing is just a default23:16
torgomaticit's more that I've been unhosing all the get_*_info functions and my brain is fried23:16
claygtorgomatic: I would have swore we had a reasonable fix somewhere?  it all started with using the response directly to set the cache info in the env - instead of the cache data set in the req environment when handling the response - from there it should just be a mole-whack to remove the setting on the way out altogether until tests pass?23:18
claygit was that one stupid bug something with auth - container tempurls maybe?23:19
torgomaticclayg: yeah, I resurrected the swift.infocache stuff out of launchpad, but that didn't move things out of GETorHEAD_base and into the get_*_info functions. I'm working on the latter now.23:21
*** diazjf has quit IRC23:22
claygtorgomatic: yeah i had a diff on there somewhere - do you have the lp bug #23:26
torgomaticclayg: one sec...23:26
torgomaticclayg: in bug 1501939 you reference bug 1449212 which has the patch in there somewhere23:27
openstackbug 1501939 in OpenStack Object Storage (swift) "get_info environ caching is leaky and brittle" [Medium,Confirmed] https://launchpad.net/bugs/150193923:27
openstackbug 1449212 in OpenStack Object Storage (swift) kilo "Container level temp URLs can unintentionally leak data." [Undecided,Fix committed] https://launchpad.net/bugs/144921223:27
claygnotmyname: I *love* me some wishlist bugs!  I have no idea who this cat is or if we'll acctually get a patch out of the deal - but he is *on* it!  lp bug #153787923:27
openstackLaunchpad bug 1537879 in OpenStack Object Storage (swift) "proxy.controllers.base should use swob.HeaderKeyDict" [Wishlist,New] https://launchpad.net/bugs/1537879 - Assigned to Ben Keller (bjkeller)23:27
admin0clayg:  HEAD /sdb2/996/   seems to be missing .. example:  HEAD http://objectstore.internal/v1/AUTH_3760c6c750a94a5ab9b869e933734481/xxx/yyy/4/2016/01/26/ZZZ.mp323:27
notmynameclayg: :-)23:28
admin0that is from log on the storage server23:28
torgomaticalso, 10 points to Gryffindor for making the openstack bot catch multiple bug numbers in one message23:28
*** darrenc is now known as darrenc_afk23:28
openstackgerritOpenStack Proposal Bot proposed openstack/swift: Updated from global requirements  https://review.openstack.org/8873623:29
*** kei_yama has joined #openstack-swift23:30
* clayg comes back from know your meme23:30
admin0bye guys .. thanks for everything .. will come back tomorrow23:36
*** darrenc_afk is now known as darrenc23:36
*** admin0 has quit IRC23:36
claygtorgomatic: yeah I got scared fo the test fallout trying to remove it - but this worked for setting it in the right place IIRC -> https://gist.github.com/clayg/72f9ae5bf5d94fa6dd1f23:37
*** ho_ has joined #openstack-swift23:51
*** lcurtis has quit IRC23:54

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