Thursday, 2015-09-17

*** chsc has quit IRC00:02
*** sneti has quit IRC00:03
*** devlaps has quit IRC00:15
*** zhill has quit IRC00:21
kota_wow, bug #1496636 seems what I wanted to dig about chunked transfer protocol between proxy and object-server.00:22
openstackbug 1496636 in OpenStack Object Storage (swift) "EC: Chunked transfer/commit protocol is *not* HTTP" [Undecided,New] https://launchpad.net/bugs/149663600:22
*** zhill has joined #openstack-swift00:31
*** breitz has quit IRC00:35
*** zhill has quit IRC00:35
*** hezhiqiang has joined #openstack-swift00:38
claygkota_: yeah you totally turned me on to it with the test gists you did for peluse's patch00:41
*** m_kazuhiro has joined #openstack-swift00:41
claygkota_: way to point out that everything we think is wrong!00:41
claygbriancline: whoot - just got your recon fixups on master - congrats!00:42
kota_clayg: yey, seems I had do good work? But awsome you found it in detail!!00:43
*** hezhiqia_ has joined #openstack-swift00:44
claygkota_: all you brother - awesome work00:44
*** garthb has quit IRC00:45
*** hezhiqiang has quit IRC00:48
*** nakagawamsa has joined #openstack-swift00:54
claygwho are the guys working on py3 in swift - it's like janonymous and the python core guy01:03
claygvictor01:03
claygayway - i'm getting annoyed about never knowing which file is going to want print 'blah' vs print('blah') - I wish there was only one way to do it in the whole swift code base so I could get used it already!01:04
*** baojg has joined #openstack-swift01:29
*** sneti has joined #openstack-swift01:33
mattoliverauclayg: this multplie patches that hit everything every now and again is frustrating, we kinda just want to line up all py3 patches, apply them all and be done with it.01:35
* mattoliverau thinks this could just be me being fedup being sick01:36
claygmattoliverau: no way - that is a totally reasonable thing to do!01:36
mattoliverauthen only one more rebase for all patches and it's done01:37
*** baojg has quit IRC01:38
mattoliverauOnce we're py3 compat we can go tell someone to go investigate asyncio and see if it is better then greenlet ;)01:39
claygmattoliverau: done that - it's not01:40
mattoliveraudamn01:40
claygmattoliverau: golang!01:41
mattoliverau\o/ golang01:41
*** 7F1AALPHR has joined #openstack-swift01:43
*** chlong has joined #openstack-swift01:46
*** chlong_ has joined #openstack-swift01:53
*** baojg has joined #openstack-swift01:54
*** 7F1AALPHR has quit IRC02:01
*** haomaiwang has joined #openstack-swift02:01
*** barker has joined #openstack-swift02:02
*** thurloat is now known as thurloat_isgone02:06
openstackgerritKota Tsuyuzaki proposed openstack/swift: Add a client disconnect test at multhiphase commit  https://review.openstack.org/22438702:19
claygkota_: did you just beat me to it?  I was about to attach a failing test to the bug :)02:20
kota_clayg: Are you already working?02:21
kota_clayg: I was reading your comment for missing container updates.02:21
claygkota_: nm, we're working on differnt things - i was writing a failing test for lp bug #149663602:21
openstackLaunchpad bug 1496636 in OpenStack Object Storage (swift) "EC: Chunked transfer/commit protocol is *not* HTTP" [Undecided,New] https://launchpad.net/bugs/149663602:21
clayg... and you're looking at container updates :)02:21
claygto team swift!02:21
kota_clayg: And i noticed I got misunderstading for object-server behavior.02:22
kota_oh, you mean that chunked transfer, wait...02:22
claygdoes patch 224387 prove my comments on the container-update change wrong?02:22
patchbotclayg: https://review.openstack.org/#/c/224387/02:22
kota_no, you are true on the container-update change.02:23
claygdamn02:23
kota_What I was misunderstanding is "object-server can update container when .data lands"02:24
kota_but it's wrong.02:24
kota_object-server updates the container only when .durable landed correctly.02:24
claygyeah because the object server doesn't know how many *other* servers successfully wrote the data02:24
kota_patch 224387 is for making sure the behavior.02:25
patchbotkota_: https://review.openstack.org/#/c/224387/02:25
claygsending the container update from one node (if he was the only one that got the bytes) is almost as bad ad missing the update :'(02:25
claygkota_: cool - descriptive tests are always *so* welcome02:25
kota_clayg: exactly02:25
kota_And I will update my patch for container updates according to your comment.02:26
claygbrute force!02:27
kota_maybe ndata + quorum_size(conainer_updates) might be good?02:27
kota_to push the header into object-server, anyways, I'll add comments during today.02:28
claygkota_: maybe indeed!  If the one and only object server that acked was the only one that successfully wrote the container async and his disk dies02:29
claygthe other's could propogate the .durable - but the container may never be updated :'(02:29
clayg%^&* it - just send it to all of em!02:29
kota_that's too simple :\02:30
claygLOL!02:31
clayggrep -i simple CONTRIBUTING.md ;)02:31
kota_LOL02:32
*** david-lyle has joined #openstack-swift02:34
*** barker has quit IRC02:36
*** barker has joined #openstack-swift02:37
claygshit - wrong bug :'(02:37
*** mahatic has joined #openstack-swift02:40
kota_clayg: which one?02:40
claygi was working on a test for lp bug #1496205 - but attached it to the commit transfer is not HTTP bug02:40
openstackLaunchpad bug 1496205 in OpenStack Object Storage (swift) "EC: Client Disconnect leaves inaccessible data on disk" [Undecided,New] https://launchpad.net/bugs/149620502:40
claygalthough - I think it's all the same bug - we're going to fix everything in patch 211338 ;)02:41
patchbotclayg: https://review.openstack.org/#/c/211338/02:41
kota_clayg: I see, thx.02:42
claygI *hope* that the object server can detect if the "end" (really the middle) of the chunked request isn't a MIME document boundary it can know it was disconnected02:42
kota_yup02:43
claygit may even be possible to fix eventlet to yeild out the chunks of a chunked transfer as it recieves them instead of that buffer up and block until network read size or eof nonsense it has now that caused all that silly content_length/0\r\n\r\n nonsense in the first place02:43
claygbut I don't know when we'll get to take out self.queue.put('') from the proxy since object servers with old eventlet would hang forever waiting for 0\r\n\r\n before sending the commit confirm headers02:44
*** patchbot has quit IRC02:44
claygI mean... not forever - node_timeout would tear down the connection - hopefully only a few requests would 503 while you're restarting your object servers - we'll have to patch eventlet first tho02:45
claygoh well - done for tonite i 'spose02:45
*** patchbot has joined #openstack-swift02:46
claygshit - i still need to work on that ring change02:46
mahaticjrichli: extended weekend here, we have a holiday today, taking off on Friday. Will be on and off. Will update if there is anything on trello.02:46
claygI'm sorta boo berries on it now that I know how often we're making these crap rings now tho :'(02:46
mahaticclayg: and review my patch :P kidding, no hurry02:47
*** barker has quit IRC02:50
kota_makes me sense about eventlet thing02:50
*** chlong_ has quit IRC02:50
*** haomaiw__ has joined #openstack-swift02:52
*** haomaiwang has quit IRC02:53
*** jkugel has quit IRC02:54
*** haomaiw__ has quit IRC03:01
*** mahatic has quit IRC03:02
*** haomaiwa_ has joined #openstack-swift03:02
*** bill_az has quit IRC03:02
notmynamegood evening03:03
notmynamejust got through reading over the day's playback buffer03:03
mattoliveraunotmyname: o/03:03
notmynamenow for the 209 unread emails....03:05
*** kota_ has quit IRC03:06
*** baojg has quit IRC03:18
*** baojg has joined #openstack-swift03:23
*** baojg has quit IRC03:23
*** kei_yama has quit IRC03:27
*** kei_yama has joined #openstack-swift03:28
*** baojg has joined #openstack-swift03:33
*** sneti has quit IRC03:35
notmynamegreat that the per disk rsync landed!03:40
*** zhill has joined #openstack-swift03:43
*** zhill has quit IRC03:48
*** trifon has quit IRC03:59
*** haomaiwa_ has quit IRC04:01
*** haomaiwa_ has joined #openstack-swift04:02
*** wbhuber has joined #openstack-swift04:07
*** zhill has joined #openstack-swift04:11
*** wbhuber has quit IRC04:11
*** zhill has quit IRC04:15
*** chlong has quit IRC04:16
claygmahatic: which one?04:24
claygyay per-disk rsync!04:24
*** chlong has joined #openstack-swift04:33
*** baojg has quit IRC04:39
*** kota_ has joined #openstack-swift04:43
*** ChanServ sets mode: +v kota_04:43
*** baojg has joined #openstack-swift04:43
*** SkyRocknRoll has joined #openstack-swift04:44
*** baojg has quit IRC04:47
*** chlong has quit IRC04:48
*** baojg has joined #openstack-swift04:48
openstackgerritKota Tsuyuzaki proposed openstack/swift: Add a client disconnect test at multhiphase commit  https://review.openstack.org/22438704:50
*** baojg has quit IRC04:54
*** SkyRocknRoll has quit IRC04:57
*** breitz has joined #openstack-swift05:00
*** haomaiwa_ has quit IRC05:01
*** haomaiw__ has joined #openstack-swift05:04
*** breitz has quit IRC05:05
*** SkyRocknRoll has joined #openstack-swift05:10
*** haomaiw__ has quit IRC05:15
*** haomaiwang has joined #openstack-swift05:15
*** hrou has quit IRC05:20
eranromkota_, Greetigs, good time to discuss EC global multi-region05:27
*** trifon has joined #openstack-swift05:28
kota_eranrom: hello05:29
kota_eranrom: I have an hour to stay at IRC.05:30
kota_eranrom: so what's up?05:30
eranromkota_: all is good. thanks05:31
*** zhill has joined #openstack-swift05:32
eranromkota_: So the first question I have is whether you have made up your mind whether to use container sync or to extend the 'placement' mechanism to make sure fragments are disctributed appropriately between regions.05:32
eranroms/disctributed/distributed05:32
kota_I'd like to bet later one, right now.05:33
kota_I'm writing a poc code for expanding placement mechanism05:33
eranromkota_: sounds resonable to me, IMO its the right way to go.05:34
kota_but not yet enough testing whether it's really fitting to actuall use case.05:34
kota_quickly, reporting05:34
kota_I've done small testing my code with normal statement.05:35
kota_(05:35
kota_(no failure case)05:35
kota_my poc code worked well and GET performance increased around 2x05:35
eranromsounds good!05:35
eranromwhat code are you using?05:35
kota_but PUT performance I assumed 3x increasement resuleted in what I expected.05:35
kota_around 1.2~1.3x increasement.05:36
kota_currently digging the reason.05:36
kota_wait05:36
*** zhill has quit IRC05:36
kota_eranrom: here, https://review.openstack.org/#/c/219165/05:36
kota_note that it is still WIP code, no enough error handling.05:37
*** baojg has joined #openstack-swift05:39
*** baojg has quit IRC05:41
kota_ah, I got mistake to write down, PUT result doesn't fit the expected result.05:41
eranromsure, actually my question is on a higher level (I am not currently familiar with the EC at all so I am not in a position to review it), I am trying to understand what is the right code to be used for e.g. 2 regions vs. 3 regions etc.05:43
eranromand probably suggest that in terms of performance tests it would be good to concentrate on codes that are suitable for the global situaltion05:44
eranrome.g. for 3 regions you may want to have a 6:6 code05:44
kota_eranrom: sure05:45
kota_eranrom: my recomendation for 3 region is 11:705:45
eranromand for 2?05:45
kota_I don't think so.05:46
eranromI mean what would you recommend for 2 regions?05:46
kota_ah...nice question.05:46
kota_around 10:4 * 2?05:47
eranromyou mean replicate 10:4?05:47
kota_if we can take more ndata, 20:4 * 2 is more efficient.05:47
kota_depends on use case.05:47
kota_If we don't consider about DR, I mean DR is a region might be gone completely.05:48
eranromI am not sure I understand what you mean by 10:4 * 2? (what's the *2 means)05:48
eranrom?05:48
*** zhill has joined #openstack-swift05:48
kota_we must set enough parities more than 2x of original data, i.e. 6:6:, 10:10 or so.05:48
kota_*2 is what I am developing for global ec cluster.05:49
*** zhill has quit IRC05:49
kota_sorry05:49
eranromreplication?05:49
kota_that means 10:18 if setting as parities.05:49
eranromok gotcha05:50
kota_but the data volume will be 2.8x of original data on it.05:51
kota_almost similar with triple replicated.05:51
eranromI was just about to say that :-)05:51
kota_if we can employ 20:4 *2 i.e. 20:2805:52
kota_that will be 2.4x of original.05:52
kota_seems reasonable.05:52
kota_However, increasing ndata is expensive for erasure coding calculation.05:54
kota_(increasing ndata and nparity, strictly)05:55
kota_And currently PyECLib support k+m up to 32.05:55
eranromright. In the spec you were mentioning a mechanism that will be aware of the fragment index and place accordingly. From the codes you mention it seems that you are not going that way - Am I right? I mean with such a mechanism you could also do sonething like 7:10 - Am I missing something?05:57
kota_That is why I propose new scheme like encoding 10:4 and place 28 (10:4 * 2(duplicated replicas)) fragments into Swift.05:57
kota_I am writing according specs...05:59
kota_according to05:59
kota_Coud you point out the weird point in my code by ... like making a comment on gerrit?06:00
*** haomaiwang has quit IRC06:01
eranromNothing weird here :-) and it might be my EC ignorance. Do you mean point witha comment in the spec?06:01
*** haomaiwang has joined #openstack-swift06:01
kota_code and spec, either is fine.06:01
kota_we can ask/answer anytime in gerrit :-)06:02
eranromsure will do, I could not find the spec yesterday. Any chance you have the link?06:02
eranromI guess I need to sharpen my search capabilities...06:03
kota_Oh, the spec landed, wait creating new thread...06:03
openstackgerritKota Tsuyuzaki proposed openstack/swift-specs: Add questions section into global_ec_cluster  https://review.openstack.org/22443906:05
kota_done06:05
eranromThanks!!!  and thanks for your time. I hope I am not waisting your time with EC ignorance :-)06:05
kota_eranrom: no problem. Thanks for bringing up it.06:06
*** zhill has joined #openstack-swift06:06
kota_eranrom: anytime I'm waiting comments to improve my spec and codes ;)06:07
*** zhill has quit IRC06:07
kota_It's time to leave here. See you tomorrow.06:17
*** kota_ has quit IRC06:17
*** chlong has joined #openstack-swift06:17
*** baojg has joined #openstack-swift06:18
*** baojg has quit IRC06:23
*** baojg has joined #openstack-swift06:26
*** silor has joined #openstack-swift06:37
*** haomaiwang has quit IRC06:51
*** dmorita has joined #openstack-swift06:52
*** haomaiwang has joined #openstack-swift06:53
*** zhill has joined #openstack-swift06:54
*** haomaiwang has quit IRC07:01
*** haomaiwang has joined #openstack-swift07:01
*** chenhuayi has joined #openstack-swift07:36
chenhuayihello, I have meet a problem about query with 'delimiter'.07:37
chenhuayicurl -k -i -X GET -H 'X-Auth-Token: TEMPAUTH_tk253eee65cac64ea097f4494aeee194e3' http://127.0.0.1:8080/v1/TEMPAUTH_test/testcontain2?delimiter=a07:38
chenhuayiHTTP/1.1 200 OK07:38
chenhuayiContent-Length: 3007:38
chenhuayiX-Container-Object-Count: 907:38
chenhuayiAccept-Ranges: bytes07:38
chenhuayiX-Storage-Policy: Policy-007:38
chenhuayiX-Container-Bytes-Used: 9128707:38
chenhuayiX-Timestamp: 1442473867.6703107:38
chenhuayiContent-Type: text/plain; charset=utf-807:38
chenhuayiX-Trans-Id: tx352861a0605242528163f-0055fa6d8307:38
chenhuayiDate: Thu, 17 Sep 2015 07:36:35 GMT07:38
chenhuayi107:38
chenhuayi1207:38
chenhuayi12307:38
chenhuayi207:38
chenhuayiLICENSE07:38
chenhuayia07:38
chenhuayiab07:38
chenhuayiabc07:38
chenhuayib07:38
chenhuayiset the delimiter=a, but the result return all the objects.07:39
chenhuayiAnybody can help? thanks07:40
*** rohit_ has quit IRC07:40
*** rledisez has joined #openstack-swift07:55
*** haomaiwang has quit IRC08:01
*** haomaiwa_ has joined #openstack-swift08:01
-openstackstatus- NOTICE: Gate is currently stuck, failing grenade upgrade tests due the release of oslo.utils 1.4.1 for Juno.08:02
*** geaaru has joined #openstack-swift08:06
*** jistr has joined #openstack-swift08:20
*** silor has quit IRC08:22
*** silor has joined #openstack-swift08:23
*** acoles_ is now known as acoles08:25
*** slo_ has joined #openstack-swift08:29
*** slo_ has quit IRC08:29
acolesclayg: http://make-everything-ok.com/08:39
acolesnotmyname: new link for channel topic ^^ :-)08:39
* acoles tries new gerrit screen08:39
* acoles reverts to old08:40
* acoles discovers gerrit option 'show person name in review category'08:42
mattoliverauacoles: lol08:50
*** hezhiqia_ has quit IRC08:52
*** zhill has quit IRC08:53
*** silor has quit IRC08:56
*** chenhuayi has quit IRC08:57
*** jordanP has joined #openstack-swift08:59
*** haomaiwa_ has quit IRC09:01
*** haomaiwang has joined #openstack-swift09:01
*** silor has joined #openstack-swift09:04
mattoliverauchenhuayi: the delimiter isn't counted if its the first character of the object so delimiter=b or 2 should work in your example. Further, please use a paste.openstack.org, gist etc rather then pasting the whole output into irc. :)09:05
acolesmattoliverau: +1 i was just looking at that too. i guess the intent may have been to roll up dir objects named 'a/b', 'a/c' to a single listing 'a' by using delimiter = '/'. but yeah it doesn't work on the first char.09:12
*** aix has quit IRC09:14
mattoliverauacoles: and the find(delimilter, len(prefix)) worries me, it might need to be find(delimiter, max(len(prefix),1))09:19
mattoliverauThere might be an edge case bug there09:19
acolesmattoliverau: so the swiftclient usage for delimiter says 'go read the swift API doc' and the swift API doc is kinda vague about it :)09:23
mattoliverauLol, I feel a doc bug coming.. But I guess we need to decide the correct behaviour first09:24
*** flwang has quit IRC09:27
acolesmattoliverau: yup. maybe one of the old-timers will remember the intent.i'm away for a bit.09:32
*** bkopilov has quit IRC09:40
*** flwang has joined #openstack-swift09:41
*** luksaur has joined #openstack-swift09:41
*** silor has quit IRC09:42
*** silor has joined #openstack-swift09:43
*** hezhiqiang has joined #openstack-swift09:43
*** aix has joined #openstack-swift09:45
luksaurhi, i'm thinking in deploy my swift environment in a cloud infrastructure, i did not find any case of a swift production deployment in virtual machines on internet09:45
*** silor has quit IRC09:46
luksaurnoting that I'll use this environment as a backend-storage for a local docker-registry, so high performance is really not a problem here09:46
*** silor has joined #openstack-swift09:46
luksaurI just need a distributed and reliable env to place the docker images09:46
luksaurhas someone using swift like that?09:47
luksauroh, forgot to say, it is a private cloud structure, everything on the same local network :-)09:49
*** bkopilov has joined #openstack-swift09:49
*** silor1 has joined #openstack-swift09:54
*** silor has quit IRC09:55
*** silor1 is now known as silor09:55
*** bkopilov has quit IRC09:58
*** silor has quit IRC10:00
*** silor has joined #openstack-swift10:01
*** haomaiwang has quit IRC10:01
*** haomaiwang has joined #openstack-swift10:01
*** silor has quit IRC10:05
*** silor has joined #openstack-swift10:10
*** bkopilov has joined #openstack-swift10:11
*** nakagawamsa has quit IRC10:12
*** silor has quit IRC10:13
*** silor has joined #openstack-swift10:14
-openstackstatus- NOTICE: Gate back to normal, thanks to the backlisting of the problematic version10:16
*** silor has quit IRC10:18
*** haomaiwang has quit IRC10:18
*** haomaiwang has joined #openstack-swift10:18
*** baojg has quit IRC10:22
*** baojg has joined #openstack-swift10:24
*** baojg has quit IRC10:28
*** silor has joined #openstack-swift10:29
*** silor has quit IRC10:30
*** silor has joined #openstack-swift10:31
*** silor1 has joined #openstack-swift10:37
*** silor has quit IRC10:37
*** silor1 is now known as silor10:37
*** mfalatic_ has quit IRC11:00
*** mfalatic has joined #openstack-swift11:00
*** haomaiwang has quit IRC11:01
*** haomaiwang has joined #openstack-swift11:01
*** KLuka__ has joined #openstack-swift11:09
*** slo__ has joined #openstack-swift11:10
*** jordanP has quit IRC11:40
*** m_kazuhiro has quit IRC11:45
*** haomaiwang has quit IRC11:54
*** silor has quit IRC12:14
openstackgerritOpenStack Proposal Bot proposed openstack/swift: Updated from global requirements  https://review.openstack.org/8873612:17
*** km has quit IRC12:19
*** haomaiwang has joined #openstack-swift12:23
*** silor has joined #openstack-swift12:30
*** jkugel has joined #openstack-swift12:52
*** aix has quit IRC12:56
*** janonymous has joined #openstack-swift12:58
*** dustins has joined #openstack-swift12:58
*** aix has joined #openstack-swift12:59
*** haomaiwang has quit IRC13:01
*** haomaiwang has joined #openstack-swift13:01
*** haypo has joined #openstack-swift13:14
*** kei_yama has quit IRC13:19
*** KLuka__ has quit IRC13:22
*** janonymous has quit IRC13:22
*** hrou has joined #openstack-swift13:23
*** wbhuber has joined #openstack-swift13:26
*** jrichli has joined #openstack-swift13:30
*** bill_az has joined #openstack-swift13:30
*** openstackgerrit has quit IRC13:31
*** openstackgerrit has joined #openstack-swift13:31
*** tongli has joined #openstack-swift13:31
*** oddsam91 has joined #openstack-swift13:31
*** jsuchome has joined #openstack-swift13:48
*** pberis has joined #openstack-swift13:48
jsuchomehi, could anyone please take a look at https://review.openstack.org/#/c/189258/ ?13:49
*** Fin1te has joined #openstack-swift13:49
*** slo__ has quit IRC13:54
*** oddsam91 has left #openstack-swift13:56
*** lcurtis has joined #openstack-swift14:00
*** haomaiwang has quit IRC14:01
*** 5EXAB5K66 has joined #openstack-swift14:01
*** sneti has joined #openstack-swift14:07
*** Fin1te has quit IRC14:09
*** pberis has quit IRC14:20
*** pberis has joined #openstack-swift14:23
*** barker has joined #openstack-swift14:27
*** jordanP has joined #openstack-swift14:27
*** esker has joined #openstack-swift14:30
*** amoturi has joined #openstack-swift14:32
*** jlhinson has joined #openstack-swift14:36
*** trifon has quit IRC14:40
*** tsimp06 has quit IRC14:40
*** minwoob has joined #openstack-swift14:42
*** barker has quit IRC14:43
*** nadeem has joined #openstack-swift14:53
*** nadeem has quit IRC14:55
*** nadeem has joined #openstack-swift14:56
*** nadeem has quit IRC14:57
*** 5EXAB5K66 has quit IRC15:01
*** haomaiwang has joined #openstack-swift15:01
*** hezhiqiang has quit IRC15:01
*** nadeem has joined #openstack-swift15:05
*** janonymous has joined #openstack-swift15:07
*** mc_nair has joined #openstack-swift15:16
*** DericHorn-HP has joined #openstack-swift15:18
*** tongli has quit IRC15:19
*** mfalatic_ has joined #openstack-swift15:36
*** mfalatic has quit IRC15:36
*** tongli has joined #openstack-swift15:39
*** mc_nair has quit IRC15:40
*** devlaps has joined #openstack-swift15:40
*** aix has quit IRC15:43
*** annegentle has joined #openstack-swift15:47
*** annegentle has quit IRC15:52
*** annegentle has joined #openstack-swift15:53
*** mc_nair has joined #openstack-swift15:54
*** haomaiwang has quit IRC16:01
*** haomaiwang has joined #openstack-swift16:01
*** Fin1te has joined #openstack-swift16:07
*** evilrob has joined #openstack-swift16:11
*** bkopilov has quit IRC16:16
*** tsimp06 has joined #openstack-swift16:21
*** bkopilov has joined #openstack-swift16:23
tsimp06is there a way to use the swift CLI with a swift compatible API on the backend?  I have nova pointing to the compatible api, but can't find where my 404's are being generated from16:24
*** silor has quit IRC16:24
*** silor1 has joined #openstack-swift16:25
*** silor1 has quit IRC16:29
tsimp06nvm, figured it out.16:29
*** rledisez has quit IRC16:30
*** jordanP has quit IRC16:33
*** garthb has joined #openstack-swift16:33
*** jistr has quit IRC16:35
*** david-lyle has quit IRC16:36
openstackgerritAlistair Coles proposed openstack/swift: Enable object server to return non-durable data  https://review.openstack.org/21527616:38
*** david-lyle has joined #openstack-swift16:47
*** DericHorn-HP has quit IRC16:47
*** breitz has joined #openstack-swift16:48
*** acoles is now known as acoles_16:50
claygacoles_: thanks for that link16:50
claygminwoob: while the make-everything-ok button is in progress is there anything I can merge that would make ec better?16:52
*** DericHorn-HP has joined #openstack-swift16:56
*** jsuchome has quit IRC16:56
*** sneti has quit IRC16:57
wbhuberclayg: minwoob is out for lunch, but should be back shortly.16:58
claygwbhuber: what about you - got any patches for me!?16:58
wbhuberclayg: actually i'm working on the dancing etag bug that you opened not so long ago16:59
claygwbhuber: heh, great description!16:59
*** haomaiwang has quit IRC17:01
*** haomaiwa_ has joined #openstack-swift17:01
*** hezhiqiang has joined #openstack-swift17:02
*** david-lyle has quit IRC17:03
*** Fin1te has quit IRC17:04
*** hezhiqiang has quit IRC17:06
*** SkyRocknRoll has quit IRC17:20
*** SkyRocknRoll has joined #openstack-swift17:21
*** geaaru has quit IRC17:23
*** SkyRocknRoll has quit IRC17:24
*** SkyRocknRoll has joined #openstack-swift17:24
clayggah, this resetting of content-length by set_hundered_continue_headers is making it terribly difficult to demonstrate the behaviors I want to see in tests (as in the tests are instead demonstrating that our services do not have the behaviors we want) :'(17:26
*** SkyRocknRoll has quit IRC17:27
*** SkyRocknRoll has joined #openstack-swift17:28
*** haomaiwa_ has quit IRC17:28
*** abaranos has joined #openstack-swift17:29
*** zhill has joined #openstack-swift17:30
abaranosI'm able to connect to our Swift instance using the swift command client, but having trouble connecting via raw HTTP. (The application is in Clojure so needs to be able to hit the http API directly)17:30
*** chsc has joined #openstack-swift17:31
abaranosThis is what I'm doing w/ the swift client:17:32
abaranosexport OS_AUTH_URL=https://us-texas-3.foo.com:5000/v2.017:32
abaranosexport OS_TENANT_ID=asdasdasdsadsdadadasdsaddasdasd17:32
abaranosexport OS_TENANT_NAME="my-tenant-nae"17:32
abaranosexport OS_USERNAME=$SWIFT_ACCOUNT17:32
abaranosexport OS_PASSWORD=$SWIFT_KEY17:32
abaranosexport OS_REGION_NAME="us-texas-3"17:32
claygwhoa - good morning17:32
abaranosswift list  ## => foo17:32
claygabaranos: well all of those options are for keystone - which is a distinct REST service from Swift with it's own api to deliver the storage-url and token17:33
*** mfalatic_ has quit IRC17:33
abaranosclayg: that's what confuses me: I thought keystone was swift version 2+17:33
claygI think the command line client has a --debug flag - it might show you something about the keystone api requests17:33
abaranosbut nowhere is OS_AUTH_VERSION set to 217:34
claygabaranos: well it figures it out based on all the other options being there17:34
clayge.g. the v2.0 in the auth url17:34
claygbut that's just the keystone api version - swift only has v117:34
abaranosclayg: ugh. I read through the client code for 40 minute probably combined, and couldn't find that inference . lol. figured it must be17:34
abaranosclayg: yup v2 in url was very suspicious :)17:35
claygI mean I think mainly swiftclient just passes all of that off to the keystone client to get the storage-url and api-token17:35
claygso I don't really know for sure what sort of sillyness it's doing17:35
claygbut w/o the ST_[AUTH|USER|KEY] options it's not going to be able to make a v1 auth request - so if it's working it's definately passing the OS_* options of to keystone and from there the keystone client just magics!17:36
abaranosclayg: ok, then if I had to authenticate with a v2.0 url what might that look lik eit raw http?17:36
claygabaranos: but I'm sure Keystone has some api docs somewhere that will show you how to make a v2 auth request and get back the stuff you need to talk to swift17:36
claygabaranos: it's sorta crappy - you hve to POST some json - well that's not *too* crappy17:37
claygbut like I don't do it with curl that much ;)17:37
*** mragupat has joined #openstack-swift17:37
ctennisabaranos: just add "-v --debug" to your swift command it will show the curl commands it's using behind the scenes17:37
abaranosctennis: I add --verbose and it showed me nothing17:38
claygabaranos: maby this?  http://developer.openstack.org/api-ref-identity-v2.html#authenticate-v2.017:38
ctennisabaranos: add --debug too17:38
claygabaranos: yeah I think --d ^ what ctennis said17:38
*** trifon has joined #openstack-swift17:39
minwoobclayg: We could try to close these out17:41
minwoobhttps://review.openstack.org/#/c/196848/17:41
minwoobhttps://review.openstack.org/#/c/221956/17:41
*** janonymous has quit IRC17:41
jrichliclayg: patch 218490 would probably be a quick review.  it has a -1 for a race condition, which will be fixed.  but your feedback would be great to have!17:42
patchbotjrichli: https://review.openstack.org/#/c/218490/17:42
claygminwoob: ok17:42
*** abaranos has quit IRC17:42
ajiangIs it safe to use 2.4 ring builder to add weight  to take advantage of https://github.com/openstack/swift/commit/2328983b7535d24d08942e62095b4346f2626566  and push the ring to the 2.2.2 cluster?17:42
claygjrichli: i'm not sure i'll get to that one today - really trying to move the needle on EC :'(17:42
jrichliclayg: ok, np17:43
claygjrichli: but it looks like an awesome patch!  thanks for pointing it out!  Would be very nice to have indeed!17:43
claygminwoob: jrichli: thanks17:43
*** breitz has quit IRC17:43
minwoobclayg: Actually for the first one that I posted, there is probably a better way to check that a frag has completely reverted (sanity check that none of the .data, .durable files exist anymore).17:44
*** sneti has joined #openstack-swift17:45
*** breitz has joined #openstack-swift17:45
wbhuberclayg: are you looking into merging all EC-related patches out there or looking for a specific patch from minwoob (i.e. a helper method that takes lisdirs and groups files, etc.)?17:45
evilrobin connecting to our VPN, abaranos got disconnected.  He wanted me to thank you clayg and ctennis for responding.  The -v --debug shows him exactly what he needed.  Thanks17:46
*** pberis has quit IRC17:47
*** pberis1 has joined #openstack-swift17:47
ctennisevilrob: cool, thanks17:47
evilrobI guess now I have to teach him about IRC bouncers17:47
evilrob:)17:47
*** pberis1 is now known as pberis17:49
ajiangSorry to ask it again:  Is it safe to use 2.4 ring builder to add weight  to take advantage of https://github.com/openstack/swift/commit/2328983b7535d24d08942e62095b4346f2626566  and push the ring to the 2.2.2 cluster?17:50
claygwbhuber: I've got a couple of EC issues I'm tracking and frustrated with my progress so I'm looking for some other things that "make EC better" that I've been ignoring so I can feel like we made some progress this week.17:50
claygajiang: bah!  sorry I missed it - yup17:51
claygajiang: on disk ring format hasn't changed *in a while*17:51
ajiangclayg:  Thanks for confirmation !17:51
claygajiang: but I guess it *sorta* depends on just how old your current cluster is17:51
claygoh 2.2.2 - no you're fine17:51
ajiangclayg: thanks!17:51
minwoobclayg: I've been looking through peluse and acoles_ make-everything-ok patches to try to help push those along.17:52
claygminwoob: much appreciated17:52
claygminwoob: I haven't heard from peluse in awhile - I think he must be elbow deep in graphs17:53
claygminwoob: but he had a banch trying to catch some ValueErrors that needs some tighting up17:53
*** sneti has quit IRC17:53
claygminwoob: all of acoles_ stuff is pretty far out there - maybe the simple DiskFile refactors would help17:53
minwoobclayg: It seems that the low and medium EC bugs on LP wouldn't be release blockers or anything, so have been focusing on reviewing for those big ones.17:53
minwoobI see.17:54
claygminwoob: yeah I've been trying to focus on the big stuff as well17:54
claygminwoob: there was one I had for fixing revert jobs of tombstones or something?17:54
claygminwoob: I don't know if it just needs more reviews or testing or a rebase - I haven't checked on it17:54
claygminwoob: thanks for the help!  good luck today!17:54
minwoobclayg: Yeah, if there are any other release blocker ones then please send them to me. I'm hoping to finish the review for peluse pretty soon.17:57
*** sneti has joined #openstack-swift18:00
*** rohit_ has joined #openstack-swift18:00
*** jamielennox is now known as jamielennox|away18:05
*** Fin1te has joined #openstack-swift18:13
tsimp06is swift sending the POST of /v1/tokens, or is keystone?18:21
*** NM has joined #openstack-swift18:37
*** Fin1te has quit IRC18:38
brianclineit's up to the user to get a token, but swift will ask keystone to verify it if swift doesn't have it cached18:42
*** Fin1te has joined #openstack-swift18:46
*** greghaynes has quit IRC18:49
cschwedebecause of the DHT this reminds me a *lot* to Swift: https://ipfs.io/ipns/ipfs.io/18:54
cschwedelike giving read-access directly to storage nodes18:54
tsimp06my problem was that I had overridden the endpoint to a non-keystone box, and it was still sending a /v1/tokens request, which was failing, but routing through keystone and v2, it works fine19:00
*** Fin1te has quit IRC19:04
*** devlaps has quit IRC19:08
*** david-lyle has joined #openstack-swift19:11
*** trifon has quit IRC19:14
*** trifon has joined #openstack-swift19:15
*** delattec has joined #openstack-swift19:19
*** cdelatte has quit IRC19:22
*** david-lyle has quit IRC19:25
wbhuberpeluse: clayg: with the graphs ready, would we use them to determine EC is awesome or say EC needs more work? or we'd ship EC as is regardless of the indicators in the graphs?19:25
*** nadeem has quit IRC19:27
*** delatte has joined #openstack-swift19:43
*** delattec has quit IRC19:46
*** nadeem has joined #openstack-swift19:48
claygwbhuber: I don't think graphs will provide a deciscive impact on EC readiness like that - it's just one input19:49
claygwbhuber: that said - I'm very much looking forward to peluse's collective thoughts and experiences from his work - I'm sure it will be facisnating and provide invaluable input to the community!19:49
claygfurther, because I value peluse's objective technical evaluation so highly - his opinion of EC readiness based on his work in the lab is much more likely to have an impact on my views regarding our current progress with EC than his ability to demonstrate excicting things with pictures (same to ctennis!)19:52
claygso far both of them have told me - "fix the bugs" - more than "make the graphs look better"19:52
* clayg goes back to hole19:52
*** barker has joined #openstack-swift19:54
openstackgerritMichael Barton proposed openstack/swift: go: add a way to terminate replication cleanly  https://review.openstack.org/22488119:57
*** sneti has quit IRC19:57
*** sneti has joined #openstack-swift19:57
*** amoturi has quit IRC20:00
*** mc_nair has quit IRC20:00
*** dustins has quit IRC20:06
*** rubal has joined #openstack-swift20:11
rubalhi.. i am new to swift20:11
rubali would like someone's guidance on the installation procedure20:11
eranromrubal: Are you looking at an installation for dev & tests or trying a real deployment install?20:12
rubaleranrom : i am using a book,  by oreilly20:13
rubaland trying on my vm20:13
rubalevery thing went well, until getting the verification on the account20:14
eranromrubal: details?20:15
*** proteusguy_ has quit IRC20:15
rubaleranrom : i am receiving a 404 error to the query curl -v -H 'X-Storage-Token: AUTH_mytoken'  http://127.0.0.1:8080/v1/AUTH_myaccount/20:16
*** trifon has quit IRC20:18
rubaleranrom: i got a 200 acknowledgement before for trying out with my username and password20:19
*** fifieldt has quit IRC20:19
eranromrubal: and I assume that along with that 200 you also got the X-Auth-Token and X-Storage-Url right?20:19
eranromrubal, that is in the response headers20:20
rubaleranrom: yes, and i used the same for my next query20:20
rubaleranrom: for which i received 40420:20
*** fifieldt has joined #openstack-swift20:20
eranromrubal: your curl shows X-Storage-Token shouldn't it be X-Auth-Token?20:21
rubaleranrom: The book said Storage, i have also tried using Auth, it returned the same response20:22
rubaleranrom: 40420:22
eranromrubal: Also, AFAIK, curl with no -X <method> defauts to POST, and I assume that in this case you wanted to do -X HEAD (that is to do the verification)20:22
claygeranrom: without a body default is GET20:23
claygeranrom: id you do the auth request again - did you get back the same token?20:24
rubalyeah, we are trying to retrieve the status of the account with that20:24
rubaleranrom: i should recieve 20420:24
claygrubal: well the -v will show you the response headers so that's about good enough20:24
rubaleranrom: not 40420:24
eranromclayg, good to know...(GET default)20:25
claygrubal: if you do the auth request again - did you get back the same token?20:25
rubal+clayg: yes, same token. memcache is working fine20:25
rubalclayg: what can cause this error?20:28
rubalanyclue?20:28
*** proteusguy_ has joined #openstack-swift20:28
*** haomaiwang has joined #openstack-swift20:29
*** mragupat has quit IRC20:29
*** SkyRocknRoll has quit IRC20:30
*** gyee has joined #openstack-swift20:31
eranromrubal: I wonder if this can be a problem with the device. Can you identify the swift device and see if it has an account created on it at all? look for an 'account' dir and look under it20:31
*** trifon has joined #openstack-swift20:33
*** haomaiwang has quit IRC20:33
*** barker has quit IRC20:34
*** mac_ified has joined #openstack-swift20:36
*** rubal_ has joined #openstack-swift20:38
*** esker has quit IRC20:41
*** rubal_ has quit IRC20:42
*** Fin1te has joined #openstack-swift20:52
*** annegentle has quit IRC20:52
*** tongli has quit IRC20:55
rubaleranrom: okey20:57
rubaleranrom: lemme check20:57
openstackgerritTim Burke proposed openstack/swift: Add the ability to specify ranges for SLO segments  https://review.openstack.org/21172620:58
*** dipe has quit IRC21:04
*** david-lyle has joined #openstack-swift21:06
*** david-lyle has quit IRC21:09
*** sneti has quit IRC21:12
tsimp06does swift work with keystone v3?21:16
hroutsimp06, yep!  But from the swift client you need to specify the version through '-V 3'21:21
hroue.g. swift -V 3 list21:21
*** jrichli has quit IRC21:21
hrouIt defaults to V221:22
tsimp06ok, thanks21:22
hrounp!21:22
*** jamielennox|away is now known as jamielennox21:24
openstackgerritMinwoo Bae proposed openstack/swift: EC GET path: support use of alternate fragments on object servers  https://review.openstack.org/21314721:25
tsimp06what is the most common swift load generation tool?21:26
tsimp06what i have is swift cli using keystone to validate the user and writing to cleversafe storage21:28
tsimp06which works, but i don't know which endpoint to use for continuous I/O21:28
*** wbhuber has quit IRC21:43
*** jst_ has joined #openstack-swift21:44
*** jst_ has quit IRC21:48
*** rubal has quit IRC21:50
*** pberis has quit IRC21:51
*** Fin1te has quit IRC21:54
*** DericHorn-HP has quit IRC21:54
*** pberis has joined #openstack-swift21:57
*** pberis has quit IRC21:58
claygtsimp06: swift-bench was sorta 'standard' albiet not very sophisticated, the industry wants cosbench to be the thing because it isn't swift specific per-say (but every time I know someone use it it ends up not generating the load they expected), ss-bench came out of SwiftStack's requirements for a decent load generation tool - and it is in fact... pretty decent as far as these things go.22:00
*** fbo has quit IRC22:03
*** fbo has joined #openstack-swift22:04
pelusetsimp06, I've been using both for the last month or so... have been able to confirm same results w/either and there are pros and cons to both depending on what you are trying to do and personal preference22:07
*** annegentle has joined #openstack-swift22:08
*** jkugel has quit IRC22:09
*** lcurtis has quit IRC22:17
*** man-a-nickname has joined #openstack-swift22:22
*** hezhiqiang has joined #openstack-swift22:23
tsimp06+clayg: Thanks, I have cosbench, don't have an endpoint that's not internal to our application to point it to, I'll check out ss-bench22:24
*** mfalatic has joined #openstack-swift22:25
man-a-nicknameI am using keystone auth;  Can a user with read/write (does not have a role in operator_roles) to a container list the containers in the account?22:26
peluse   tsimp06 you'll point either to your proxy22:26
pelusetsimp06, but you'll likely get more swift specific support using ssbench... and you are likely to find it easier to setup and get running as well22:27
pelusesupport meaning people helping you use it :)22:27
*** delatte has quit IRC22:28
mattoliverauMorning22:28
man-a-nicknameThe account DB is would need (part of) the metadata of the container in the listing, I guess.22:28
*** hezhiqiang has quit IRC22:28
tsimp06alrighty :)22:28
*** annegentle has quit IRC22:30
man-a-nicknameany ideas?22:31
tsimp06man-a-nickname is it not working?  i would assume list containers requires the admin role22:32
tsimp06unless you own the container that is22:33
man-a-nickname+tsimp06 There is a header to set for the "owner" of that container?22:36
*** annegentle has joined #openstack-swift22:37
openstackgerritClay Gerrard proposed openstack/swift: Fix client disconnect during multhiphase commit  https://review.openstack.org/22438722:38
clayg^ kota: I sorta ransacked your change :\22:38
claygkota: but it was a really great idea!22:38
claygMOAR TESTS!22:39
*** dipe has joined #openstack-swift22:40
peluseclayg, nice - will check it out!22:40
claygpeluse: oh thanks bro!22:42
claygpeluse: I think the ChunkReadError is key - I'm going to look at adding that over the ValueError catching change - I need to track down all the calls to wsgi_input.read and make sure IOError/ValueError get translated - then I think we're golden to find except ClientDisconnect and make it (ClientDisconnect, ChunkReadError) - maybe?  torgomatic?22:43
claygpeluse: but I'm probably not going to get to that this afternoon :\22:43
peluseclayg, still running the EC perf tests on the last ver... once I get another run done I can update as it would hit these errors quite frequently based on load22:44
torgomaticisn't ClientDisconnect what *we* raise when we get a ChunkReadError?22:44
claygpeluse: a) I have an idea for lp bug #1496205 that I want to flesh out22:44
openstackLaunchpad bug 1496205 in OpenStack Object Storage (swift) "EC: Client Disconnect leaves inaccessible data on disk" [Undecided,New] https://launchpad.net/bugs/149620522:44
torgomaticChunkReadError just means "hey, there was supposed to be some chunked-encoding stuff here and now there's not, so, uh, wtf"22:44
claygpeluse: b) I want to see if I can get a +2 on minwoob's changes22:44
claygpatch 19684822:44
patchbotclayg: https://review.openstack.org/#/c/196848/22:44
claygpatch 22195622:44
patchbotclayg: https://review.openstack.org/#/c/221956/22:44
peluseclayg, I saw that fly by but haven't read it yet, have been sucked away from work almost entirely for the last week or so22:44
man-a-nickname+tsimp06 I as a non-admin can HEAD/GET the container just fine. But cannot GET/HEAD the account to find out what containers I have to GET/HEAD. Am I missing something here?22:45
*** hrou has quit IRC22:45
peluseman, a lot has happened lately :)22:45
claygtorgomatic: I don't know for sure where we raise ClientDisconnect from?  maybe I"m saying it wrong - maybe we catch mostly ChunkReadTimeout22:45
torgomaticclayg: that'd make sense22:46
claygtorgomatic: that's probably it - but sometimes instead of ChunkReadTimeout we get some bs protocol error because - well I guess because sock.recv can return ''?  that doesn't sound quite right either... make it's all the makefile stuff that eventlet.wsgi does to get readline - and then readline will return '' to indicate EOF and eventlet.wsgi is just stupid22:47
peluseclayg, we were raiing ValueError because that's what the older (still not up to date for us I don't think) eventlet would do when wsgi input went away in the middle of a ready22:47
claygtorgomatic: there's also some IOError that it raises - I remember seeing that22:47
torgomaticclayg: could be an error if someone's counting bytes and doesn't get enough22:47
claygtorgomatic: maybe - i sorta think that *would* end up looking like a ChunkReadTimeout - I mean read(network_chunk_size) is going to block if there's nothing on the wire - fuck I forget how makefile works22:48
claygtorgomatic: anyway I have some really good (IMHO) real socket tests in patch 224387 - if you could review that'd be like steller!22:48
patchbotclayg: https://review.openstack.org/#/c/224387/22:48
torgomaticI think makefile() just dup()-s the file descriptor and wraps a Python file wrapper around it22:48
claygtorgomatic: yeah but there has to be some symantic difference with a raw socked and wrapped file for EOF and re: read and readline22:49
torgomaticyeah, probably22:49
clayghrm.. I don't think patch 224387 had an up-to-date rebase - I'm going to carry on work/fix for lp bug #1496205 ontop of it anyway tho22:53
openstackLaunchpad bug 1496205 in OpenStack Object Storage (swift) "EC: Client Disconnect leaves inaccessible data on disk" [Undecided,New] https://launchpad.net/bugs/149620522:53
patchbotclayg: https://review.openstack.org/#/c/224387/22:53
tsimp06man-a-nickname check out http://docs.openstack.org/developer/swift/overview_auth.html  it states that read/write can't access account info22:53
tsimp06i'm not sure what the affects of not having the role will do to the requests22:54
man-a-nicknameIt will just let you have r/w to the objects in the container and GET/HEAD of the container. But the user must know the container exists first.22:55
tsimp06in that case, wouldn't the user who created the container provide that info?22:56
*** [1]eranrom has joined #openstack-swift22:58
*** eranrom has quit IRC22:58
*** [1]eranrom is now known as eranrom22:58
man-a-nicknameIn this case it would be two parts of an application. The parts that works on the containers cannot go discover them; it has to be told.22:58
*** jlhinson has quit IRC22:59
*** david-lyle has joined #openstack-swift22:59
man-a-nicknameTo have a scoped container listing would be kind of expensive for swift to do.23:00
*** eranrom has quit IRC23:02
*** annegentle has quit IRC23:03
*** km has joined #openstack-swift23:04
*** DericHorn-HP has joined #openstack-swift23:04
*** breitz has quit IRC23:04
claygtorgomatic: you know pyeclib stuff - would it be possible for the auditor to do some sort of checks on the ec frags in the archive to validate some of the EC metadata (like X-Object-Sysmeta-Ec-Frag-Index or right now I'd be most inerested in X-Object-Sysmeta-Ec-Content-Length)23:04
torgomaticclayg: what kind of validations? -Ec-Content-Length is just the length of the original object, so all you could really validate is that it's >= 0, right?23:05
torgomaticor I guess you could take the fragment archive's size and turn that into a bound on the object's size, ± half a segment23:06
claygtorgomatic: yeah that's what I'm talking about!23:06
*** breitz has joined #openstack-swift23:07
torgomaticclayg: what are you trying to do?23:07
claygworking on lp bug #1496205 staring at these objects that obviously are too small to solve the X-Object-Sysmeta-Ec-Content-Length - but the auditor don't care - Content-Length matches os.stat so he's happy23:07
openstackLaunchpad bug 1496205 in OpenStack Object Storage (swift) "EC: Client Disconnect leaves inaccessible data on disk" [Undecided,New] https://launchpad.net/bugs/149620523:07
peluseclayg, wonder if it makes sense to dust off the algebraic signature stuff we talked about a long long time ago.... would confirm integrity of a frag set and not just spot check length23:09
*** zhill has quit IRC23:10
torgomaticclayg: does the fragment archive's etag match its md5sum?23:11
claygyeah swift-object-info says it's valid23:12
claygpeluse: that requires talking to the other nodes right?23:12
torgomatichuh, wacky; sounds like the proxy goofed up when writing it23:12
claygpeluse: could be useful as an out of band tool23:12
peluseclayg, yeah but HEAD only I believe23:12
pelusebut we never fully explored it23:12
claygpeluse: I'd still be worried about the connections per object in a background process - even if it was just stat the file and read metadata - no way we could just do that all the time23:13
claygpeluse: but as a out of band ops tool like swift-object-info or something like that it'd probably be pretty sweet23:13
claygI love those kinds of tools for digging around on stuff on live data23:14
claygtorgomatic: yeah I think i'm troubleshooting a proxy bug - but having the auditor able to protect against this kind of invalid data would be useful at least in this case23:15
claygtorgomatic: like peluse's pointed out I'm curious what other sort of validation we might ahve available if we went looking for it23:15
peluseclayg, we have some old trello discussions on it, I'll check it out.23:16
peluseneed to read that bug report / patch as well, curious how things got messed up23:16
pelusehaving dinner with your execs tonight though so maybe tomorrow :)23:17
claygtheir generally friendly folks - have a good time23:18
peluseyeah, I think I've broken bread with most at one point or another...23:19
peluseclayg, are you still banging on the kinetic stuff now and again?23:20
claygpeluse: now and again23:22
peluseclayg, FYI trying to get us signed up for the new Open Kinetic working group thingy under the foundation.  having some legal challenges (go figure) so curious how hot that stuff has been for you lately... can chat later23:24
peluseclayg, torgomatic, notmyname - please see email23:26
*** kei_yama has joined #openstack-swift23:29
*** chsc has quit IRC23:30
*** breitz has quit IRC23:37
*** man-a-nickname has quit IRC23:37
*** CR7 has joined #openstack-swift23:39
openstackgerritMinwoo Bae proposed openstack/swift: EC GET path: support use of alternate fragments on object servers  https://review.openstack.org/21314723:40
claygman, stupid proxy is so stupid23:50
*** DericHorn-HP has quit IRC23:52
*** hezhiqiang has joined #openstack-swift23:55
*** nadeem has quit IRC23:56
*** minwoob has quit IRC23:58

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