Tuesday, 2015-05-26

*** chlong has joined #openstack-swift00:15
*** mwheckmann has quit IRC00:31
*** marzif has quit IRC01:00
*** tellesnobrega has quit IRC01:16
*** petertr7 is now known as petertr7_away01:25
*** logan2 has joined #openstack-swift01:25
*** tellesnobrega has joined #openstack-swift01:29
*** CaioBrentano has joined #openstack-swift02:16
*** bkopilov_wfh has quit IRC02:18
*** CaioBrentano has quit IRC02:20
*** vjujjuri has joined #openstack-swift02:34
*** kei_yama has quit IRC03:11
*** notmyname has joined #openstack-swift03:13
*** ChanServ sets mode: +v notmyname03:13
*** patchbot has joined #openstack-swift03:14
*** kei_yama has joined #openstack-swift03:15
*** vjujjuri has quit IRC03:45
*** fanyaohong has joined #openstack-swift03:46
*** kota_ has joined #openstack-swift03:47
*** bkopilov_wfh has joined #openstack-swift04:13
*** asettle has joined #openstack-swift04:24
*** links has joined #openstack-swift04:27
*** kota_ has quit IRC05:01
*** logan2 has quit IRC05:08
*** petertr7_away is now known as petertr705:19
*** petertr7 is now known as petertr7_away05:28
*** yuan has quit IRC05:29
*** proteusguy has quit IRC05:37
*** krykowski has joined #openstack-swift05:43
*** asettle has quit IRC05:50
*** proteusguy has joined #openstack-swift05:53
*** fanyaohong has quit IRC06:03
*** SkyRocknRoll has joined #openstack-swift06:10
*** SkyRocknRoll has joined #openstack-swift06:10
*** chlong has quit IRC06:30
*** vjujjuri has joined #openstack-swift06:35
*** kei_yama has quit IRC06:39
*** kei_yama has joined #openstack-swift06:45
*** vjujjuri has quit IRC06:45
*** admin6 has joined #openstack-swift07:06
*** logan2 has joined #openstack-swift07:06
*** petertr7_away is now known as petertr707:07
*** jordanP has joined #openstack-swift07:09
*** ppai has joined #openstack-swift07:13
*** logan2 has quit IRC07:17
*** petertr7 is now known as petertr7_away07:17
*** bkopilov_wfh is now known as bkopilov07:24
*** krykowski has quit IRC07:25
*** ppai has quit IRC07:29
*** jistr has joined #openstack-swift07:39
openstackgerritMerged openstack/swift: Add Swift Inspector to assoicated projects  https://review.openstack.org/18466107:41
*** SkyRocknRoll has quit IRC07:45
*** SkyRocknRoll has joined #openstack-swift07:48
*** SkyRocknRoll has quit IRC07:48
*** SkyRocknRoll has joined #openstack-swift07:48
*** silor has joined #openstack-swift08:01
openstackgerritMichael MATUR proposed openstack/swift: fixup! Patch of "parse_content_disposition" method to meet RFC 2183  https://review.openstack.org/18538908:05
openstackgerritOpenStack Proposal Bot proposed openstack/python-swiftclient: Updated from global requirements  https://review.openstack.org/8925008:09
openstackgerritOpenStack Proposal Bot proposed openstack/swift: Updated from global requirements  https://review.openstack.org/8873608:10
*** flaper87 has joined #openstack-swift08:13
*** mmcardle has joined #openstack-swift08:24
*** joeljwright has joined #openstack-swift08:24
admin6Hi all. I’m just about to test Erasure coding with v2.3. I’m getting this error on the proxy :08:37
admin6ERROR: Invalid Storage Policy Configuration in /etc/swift/swift.conf (Invalid option 'ec_num_parity_fragments' in storage-policy section, for index '4')08:37
admin6 :-)  Sorry for the buzz, I was simply missing  option :  policy_type = erasure_coding08:41
*** hseipp has joined #openstack-swift08:55
*** petertr7_away is now known as petertr708:56
hoadmin6: No problem :-) You solved it before we recoginzed your message.08:59
*** logan2 has joined #openstack-swift09:02
*** leopoldj has joined #openstack-swift09:04
*** petertr7 is now known as petertr7_away09:06
*** aix has joined #openstack-swift09:08
*** hseipp has quit IRC09:15
*** hseipp has joined #openstack-swift09:15
*** haomaiwa_ has quit IRC09:17
openstackgerritMichael MATUR proposed openstack/swift: fixup!Patch of "parse_content_disposition" method to meet RFC2183  https://review.openstack.org/18538909:24
*** haomaiwang has joined #openstack-swift10:06
*** proteusguy has quit IRC10:15
*** goodes has quit IRC10:29
*** acoles_away is now known as acoles10:30
*** marzif has joined #openstack-swift10:39
*** proteusguy has joined #openstack-swift10:42
*** petertr7_away is now known as petertr710:45
*** acoles is now known as acoles_away10:45
*** petertr7 is now known as petertr7_away10:55
*** acoles_away is now known as acoles11:00
*** marcusvrn has joined #openstack-swift11:08
*** aix has quit IRC11:14
*** aix has joined #openstack-swift11:15
*** ho has quit IRC11:30
*** jistr is now known as jistr|class11:33
*** haomaiwang has quit IRC11:40
*** ppai has joined #openstack-swift11:47
*** ChanServ sets mode: +v cschwede12:00
*** km has quit IRC12:10
*** logan2 has quit IRC12:12
*** ekarlso has quit IRC12:16
*** ekarlso has joined #openstack-swift12:16
*** samueldmq has joined #openstack-swift12:17
samueldmqhi, good morning12:18
samueldmqswift doesn't use rbac for authn, does it ?12:18
samueldmqlike other projects in the openstack ecosystem12:19
*** ppai has quit IRC12:21
*** SkyRocknRoll has quit IRC12:23
*** petertr7_away is now known as petertr712:34
*** bkopilov has quit IRC12:34
*** petertr7 is now known as petertr7_away12:43
*** jistr|class is now known as jistr13:00
*** kei_yama has quit IRC13:08
*** CaioBrentano has joined #openstack-swift13:11
*** mwheckmann has joined #openstack-swift13:14
*** logan2 has joined #openstack-swift13:21
*** haypo has joined #openstack-swift13:21
haypohi. i write a first patch serie to port swift to python3: https://review.openstack.org/#/q/status:open+project:openstack/swift+branch:master+topic:py3,n,z13:21
haypotell me if you need more information on them, or on python 3 in general13:22
*** links has quit IRC13:29
*** acoles is now known as acoles_away13:31
*** zynisch_o7 has joined #openstack-swift13:43
*** zynisch_o7 has quit IRC13:45
*** logan2 has quit IRC13:54
*** zynisch_o7 has joined #openstack-swift13:56
*** zynisch_o7 has quit IRC13:57
*** zynisch_o7 has joined #openstack-swift13:58
*** annegentle has joined #openstack-swift13:59
*** zynisch__ has joined #openstack-swift14:01
*** zynisch_o7 has quit IRC14:01
*** zynisch__ has quit IRC14:03
*** minwoob has joined #openstack-swift14:04
*** zynisch_o7 has joined #openstack-swift14:04
*** zynisch_o7 has quit IRC14:11
*** zynisch_o7 has joined #openstack-swift14:13
*** zynisch_o7 has quit IRC14:18
*** bkopilov has joined #openstack-swift14:18
*** annegentle has quit IRC14:19
*** annegentle has joined #openstack-swift14:19
*** breitz has joined #openstack-swift14:20
*** petertr7_away is now known as petertr714:23
*** petertr7 is now known as petertr7_away14:32
*** annegentle has quit IRC14:38
*** zynisch_o7 has joined #openstack-swift14:44
*** proteusguy has quit IRC14:47
*** jrichli has joined #openstack-swift14:50
*** annegentle has joined #openstack-swift14:50
*** proteusguy has joined #openstack-swift14:59
*** geaaru has joined #openstack-swift15:02
*** haomaiwang has joined #openstack-swift15:04
*** annegentle has quit IRC15:11
*** alejandrito has joined #openstack-swift15:14
*** petertr7_away is now known as petertr715:23
*** petertr7 is now known as petertr7_away15:33
*** zaitcev has joined #openstack-swift15:35
*** ChanServ sets mode: +v zaitcev15:35
notmynamegood morning15:37
*** haomaiwang has quit IRC15:37
*** haomaiwang has joined #openstack-swift15:37
*** jistr has quit IRC15:40
*** gyee has joined #openstack-swift15:42
*** vjujjuri has joined #openstack-swift15:44
tdasilvazaitcev: looking for me?15:44
*** leopoldj has quit IRC15:45
zaitcevtdasilva: if you could look over Pai's fixes to your versioned writes middleware, it would be great15:45
zaitcevtdasilva: other than that, keep up the good work :-)15:45
zaitcevhttps://review.openstack.org/13434715:47
tdasilvazaitcev: sounds good. I'm hoping we can put some focus back on versioning and copy middleware15:47
*** slavisa has joined #openstack-swift15:58
*** zynisch_o7 has quit IRC15:58
*** zynisch_o7 has joined #openstack-swift15:58
*** slavisa has quit IRC16:01
*** slavisa has joined #openstack-swift16:01
*** slavisa has quit IRC16:06
vjujjuriHi16:07
vjujjuriI am not getting good perf numbers on swift. What am I doing wrong?16:07
vjujjuridoing 1k writes; I have a 4 node clsuter.16:07
vjujjuri3 storage nodes + 4th one for keystone and proxy; and this is where I am running my tests16:08
vjujjuriLast-byte  latency:  0.042 -   0.061    0.051  (  0.005)    0.059  (    tiny objs)16:08
vjujjuriAverage latency is 51ms for 1k objects16:08
vjujjurimy storage nodes are SSDs and my network is 1gig16:08
vjujjuriobviously I think I am doing something wrong16:09
*** petertr7_away is now known as petertr716:09
vjujjuridirect writes to ssds I get 1ms16:09
vjujjuriI am using ssbench16:09
vjujjurianyone here experimented small objects on SSD with swift?16:09
vjujjuriI am using icehouse16:09
swifterdarrellvjujjuri: the most common mistake when using ssbench is to start with some arbitrarily-chosen concurrency level that is too high for the hardware, saturating something, and getting poor results; what concurrency were you using? did you make sure the server running ssbench wasn't the bottleneck? did you try concurrency of 1 for comparison?16:11
vjujjuri-p 2 -u 216:11
vjujjuriand objects are 10,00016:11
vjujjuriI mean -u2 --workers 216:12
vjujjuriI tried upto 16 parallel16:12
vjujjuriresults did not change much16:12
vjujjuriswifterdarrell: I even tried -u 116:12
vjujjuriand similar numbers16:13
vjujjuribench is on the proxy machine16:13
*** haypo has quit IRC16:13
swifterdarrellvjujjuri: one tack would be to use something else to corroborate the results... like what kind of latencies do you see with PUTs from curl? a single-stream swift-bench?16:14
swifterdarrellvjujjuri: i think ssbench might also record the worst txid, so grepping that in the logs might reveal something16:15
*** vjujjuri_ has joined #openstack-swift16:16
*** vjujjuri has quit IRC16:17
*** vjujjuri_ is now known as vjujjuri16:17
*** admin6 has quit IRC16:17
vjujjuriI tried swift upload even that is not giving great numbers16:19
vjujjurish-4.2# ls -l jv1k16:19
vjujjuri-rw------- 1 root root 1024 May 25 09:25 jv1k16:19
vjujjurish-4.2# set -o vi16:19
vjujjurish-4.2# date; swift upload myfiles jv1k; date16:19
vjujjuriTue May 26 09:18:41 PDT 201516:19
vjujjurijv1k16:19
vjujjuriTue May 26 09:18:42 PDT 201516:19
vjujjuriI put this in a loop16:19
vjujjurito put say 100 objects16:19
vjujjuriit is taking around 50-60 ms16:19
swifterdarrellvjujjuri: swift CLI tool authenticates every ClI invocation, so that's a poor tool for this16:19
swifterdarrellvjujjuri: getting an auth token and then using curl in a loop would be better16:20
*** annegentle has joined #openstack-swift16:20
vjujjuriI don't know how to use authtoken16:20
vjujjuriwhatever swift stat gives?16:20
swifterdarrellvjujjuri: ya... "swift stat -v"16:21
vjujjuriok; I got a multi like auth token16:21
swifterdarrellvjujjuri: then include that in your curl with   -H "X-Auth-Token: <...>"16:21
vjujjuriand how do I use it?16:21
swifterdarrellvjujjuri: oh... v2/keystone or something?16:21
vjujjurilet me put it in pastebin16:22
vjujjurihttp://pastebin.com/nM26fc8Y16:23
vjujjuriswifterdarrell: ^16:23
zackmdavisthat is an admirably high-entropy auth token16:24
vjujjuriI did not do anything special16:25
glangeyou don't get an auth token like that without something special having been done :)16:25
vjujjuriglange: may be I did but not intentional16:26
vjujjuriI just followed directions in the swift page16:26
glangeok16:27
vjujjuriso you guys think my auth is causing the latency?16:27
vjujjurianyway I can avoid or reduce the overhead?16:27
notmynameany chance you can use keystone's uuid tokens?16:28
vjujjurinotmyname: anything is fine. Security is not a great concern I am looking for latency numbers16:28
vjujjuribut I need to know how to get that16:28
vjujjurinew here :)16:29
vjujjurinotmyname: if uuid auth saves sure.. can you tell me how to do that?16:31
*** haomaiwang has quit IRC16:31
notmynameuuid tokens are 32 bytes long, so the per-request transfer overhead is less16:31
glangeif it's authing each request, that is the main cause of bad performance?16:32
*** hseipp has left #openstack-swift16:32
notmynamevjujjuri: http://docs.openstack.org/developer/keystone/configuration.html#token-provider  looks like it has some info on configuring keystone for that16:33
vjujjurinotmyname: if it is just overhead it is negligible ; unless as glange said if auth is taking each request.16:33
*** hseipp has joined #openstack-swift16:33
glangevjujjuri: you could try just doing curl requests in a loop as described here:  http://docs.openstack.org/developer/swift/development_saio.html16:33
vjujjurimay be I just disable auth?16:33
glangeyou get the auth token once and then pass it in on the command line16:33
notmynamepki tokens aren't cacheable, so it has to go back to keystone every time (AIUI)16:33
glangemaybe by setting an env variable16:33
*** hseipp has left #openstack-swift16:34
*** acoles_away is now known as acoles16:37
notmynamevjujjuri: if you want to test to see if it is actually auth that's slowing you down or not, then take keystone out of the proxy server pipeline (in /etc/swift/proxy-server.conf), restart the proxy, and run the test again16:38
*** haomaiwang has joined #openstack-swift16:38
*** zynisch_o7 has quit IRC16:39
*** zynisch_o7 has joined #openstack-swift16:42
*** zynisch_o7 has quit IRC16:42
vjujjurinotmyname: let me try that16:47
vjujjuri[pipeline:main]16:48
vjujjuri#pipeline = healthcheck cache authtoken keystoneauth proxy-server16:48
vjujjuripipeline = healthcheck cache proxy-server16:48
vjujjurinotmyname: is this good?16:48
vjujjuriI took out authtoken and keystonauth both out16:48
notmynamevjujjuri: what version of swift do you havE?16:48
notmynamevjujjuri: yeah, that will work16:49
vjujjuri2.0.316:49
notmynamehmm..I don't think that's right (there's never been a 2.0.3 version of the server-side swift). I think that's the version of the CLI you have16:50
notmynamevjujjuri: do this: `curl http://<swift endpoint>/info | python -m json.tool`16:50
notmynamevjujjuri: that will give you a formatted json output of the capabilities of the cluster, including the version16:51
vjujjurinotmyname I have two end points one with controller:5000 and other with controller:808016:52
notmyname:8080 is likely the swift one. the :5000 one is probably keystone16:52
vjujjurinotmyname: sorry for basic questions.16:54
vjujjurihttp://controller:8080/v1/AUTH_%(tenant_id)s16:54
vjujjurihow do I know what is my tenatnt_id is?16:54
vjujjurithe above one is listed16:54
vjujjuriwith endpoint-list16:54
vjujjuriBTW even after restarting my proxy with keystone deleted from pipeline I still get same numbers16:54
*** acoles is now known as acoles_away17:06
*** harlowja has joined #openstack-swift17:07
*** jordanP has quit IRC17:07
*** annegentle has quit IRC17:09
openstackgerritMerged openstack/swift: Cleanup and extend end to end ssync tests  https://review.openstack.org/17937917:12
notmynamevjujjuri: ah, good question17:12
notmynamevjujjuri: if you don't have any auth, I think the tenant id could be anything17:13
notmynamevjujjuri: for the sake of argument, just use "AUTH_foo" or something like that17:13
vjujjurish-4.2# curl http://controller:8080/v1/AUTH_foo/info17:18
vjujjuri<html><h1>Not Found</h1><p>The resource could not be found.</p></html>sh-4.2#17:18
vjujjurinotmyname: ^17:18
notmynamehttp://controller:8080/info17:18
vjujjuriok17:23
vjujjurithat says17:23
vjujjuriversion": "1.13.1"17:23
notmynamethat's the one :-)17:23
vjujjuriok; so basically disabling auth in pipeline did not improve numbers17:24
vjujjuriyou guys also see these are bad numbers right?17:25
openstackgerritSamuel Merritt proposed openstack/swift: Handle empty suffix dirs the same for EC and replication  https://review.openstack.org/18567917:25
clayggoogle calander - why do you hate UTC so much!?17:31
notmynameclayg: use iceland17:31
claygit's so stupid, I found GMT (no daylight savings) and I put it to 9:00pm and click save17:32
notmynameclayg: reykjavik is UTC with no DST17:33
claygTHEN it moves it forward one hour?  why does it move it!?17:33
claygyeah i tried iceland - same thing17:33
notmynameclayg: yeah, it's really terrible17:33
*** annegentle has joined #openstack-swift17:33
vjujjurinotmyname: Somehow it is still looking for auth; Just for experiment I unset OS_PASSWORD17:33
claygi had to set it 8pm so that it would move it 9pm after save - it makes no sense17:33
vjujjuriand now I cant upload17:33
vjujjuriuth version 1.0 requires ST_AUTH, ST_USER, and ST_KEY environment variables17:33
vjujjurito be set or overridden with -A, -U, or -K.17:33
notmynamevjujjuri: ok. let's back up.17:34
notmynamevjujjuri: also, I'm sorry. i know this must be frustrating17:34
claygi don't get it - google is a big company - and I know they use this app - they must have a workflow that makes sense17:34
notmynamevjujjuri: go ahead and put keystone back in. ideally, you should switch it to uuid tokens. they are much better for swift thank the pki tokens17:35
notmynamevjujjuri: so the problem you're seeing is a 50ms latency on uploading a 1k object?17:35
vjujjuriok; I will put it back; but what surprises me is; when you took it off of backend why is it still asking for OS auth; may be  I am doing something wrong in disabling auth17:35
vjujjurinotmyname: yep 50ms on ssd is pretty high17:36
vjujjurifor 1k objects17:36
vjujjuriI should be seeing 5-6 ms17:36
notmynamevjujjuri: in order to see where the slowdown is, you'll have to do some investigation.17:37
vjujjuriyeah; first step I tough is disabling auth. but I guess not having success there17:38
notmynameI don't run swift on SSDs, so I can't validate what you're seeing17:38
vjujjuriif I run on regular disks17:39
vjujjurithese are directories17:39
notmynamevjujjuri: but with smaller objects, the latency will be dominated by the various network hops in the cluster17:39
vjujjuriI get around 100-150s17:39
vjujjurims17:39
notmynameyou've got 3 servers? how many drives?17:39
vjujjuri3 storage servers. But I have created directories on XFS17:39
vjujjurias i don't have individual spindles17:40
notmynameI don't follow. what do you mean by not having individual spindles?17:41
*** HenryG has quit IRC17:42
vjujjurinotmyname: I have only one HDD and one SSD on each of my machines; Swift's recommendation is to use entire disk as one mount point.17:42
notmynameright17:42
vjujjuriSince I have only one HDD on the machine I creaed directories17:42
vjujjuriSo my object ring contains17:43
vjujjuri9 entries17:43
vjujjuri3 machines; and 3 directories on each machine17:43
vjujjuriand I put mount_check=false17:43
notmynameah. so you have multiple mount points on each server?17:43
vjujjuriin the configuration machine17:43
notmynameok17:43
notmynamedon't do that ;-)17:43
vjujjuriI understand that is not recommended but that is the best I can do with the hardware I have :(17:44
vjujjuriand I will be surprised if that can cause huge perf issue;17:44
notmynameon reason is that swift is placing data across what you tell it in the ring. so it may place replicas across "drives" that are actually the same physical device. so you lose one device and then you're toast17:44
notmynameit's not a problem to have only one mount point per server17:45
notmynameso you'd have 3 in the cluster total in your 3 servers17:45
vjujjurinotmyname: this is just perf testing17:45
vjujjurisetup in my lab17:45
*** HenryG has joined #openstack-swift17:46
notmynameok, but deploying it a way that isn't what you'd see in a prod setup isn't any way to do perf testing17:47
*** thumpba_ has quit IRC17:47
vjujjuriI agree; trying to workout with what is available. don;t have access to production machines.17:49
vjujjuribut just the basic tests17:49
vjujjurishows something wrong may be in my setup17:49
vjujjurias I get 1ms local writes to ssds17:49
vjujjuriand my network is 1gige17:49
*** fthiagogv has joined #openstack-swift17:50
*** fthiagogv has quit IRC17:50
*** fthiagogv has joined #openstack-swift17:50
*** cloudm2 has joined #openstack-swift17:51
*** haomaiw__ has joined #openstack-swift17:51
*** haomaiwang has quit IRC17:52
notmynamevjujjuri: there are 2 things that are next. ie 2 things I'd do if I were you. first, set it up again to only use one mount point per drive. second, you'll have to start measuring various parts of the cluster17:52
*** mmcardle has quit IRC17:52
notmynamefor the second one, I think I heard of some tools last week that people have to do that. maybe hurricanerix_ has something17:53
*** annegentle has quit IRC17:58
*** annegentle has joined #openstack-swift17:59
*** HenryG has quit IRC18:01
*** HenryG has joined #openstack-swift18:01
tdasilvaclayg: I used Ghana (Accra) this morning and it seems to have worked18:05
*** harlowja_ has joined #openstack-swift18:06
*** harlowja has quit IRC18:06
*** aix has quit IRC18:25
*** fthiagogv has quit IRC18:32
*** fthiagogv has joined #openstack-swift18:33
*** gyee has quit IRC18:37
notmynamereminder to everyone: check the channel topic. our meeting time has changed to 2100UTC (this is 2 hours after the previous time)18:38
*** alejandrito has quit IRC18:38
openstackgerritSamuel Merritt proposed openstack/swift: EC: don't 503 on marginally-successful PUT  https://review.openstack.org/18079518:39
*** logan2 has joined #openstack-swift18:47
claygwhat'd I do?18:52
openstackgerritVictor Stinner proposed openstack/swift: Replace dict.iteritems() with six.iteritems(dict)  https://review.openstack.org/18545118:56
claygwhoooo python3!18:58
*** silor has quit IRC19:02
*** annegentle has quit IRC19:15
openstackgerritMichael Barton proposed openstack/swift: go: log 499 on client early disconnect  https://review.openstack.org/18357719:16
*** barra204 has joined #openstack-swift19:16
*** annegentle has joined #openstack-swift19:23
portanteredbo: do you have any performance numbers yet comparing hummingbird to regular swift?19:24
peluse_clayg, yeah I saw that.  Note that if we move to py3 then there's a good chance an Intel team (compiler/interpreter team) will toss us some cpython updates to test perf improvements...19:39
peluse_clayg, headsup I may ned to pick your brain a bit on putting together some sane tests for the EC GET cases we talked about in vancouver, looking for a decent way now so will continue for a while then punt if I have to19:41
openstackgerritpaul luse proposed openstack/swift: Exclude local_dev from sync partners on failure  https://review.openstack.org/17507619:52
*** marcusvrn has quit IRC19:59
*** mcnully has joined #openstack-swift20:02
*** mcnully has quit IRC20:06
*** acampbell has joined #openstack-swift20:08
openstackgerritMerged openstack/python-swiftclient: be more explicit in the --version CLI option  https://review.openstack.org/18289220:09
openstackgerritMerged openstack/swift: Add swift-durability-calculator line to docs  https://review.openstack.org/18531320:09
*** wbhuber has joined #openstack-swift20:11
*** fthiagogv has quit IRC20:13
*** samueldmq has quit IRC20:15
*** gyee has joined #openstack-swift20:28
*** acampbell has quit IRC20:30
*** setmason has joined #openstack-swift20:31
redboportante: no, dfg has some better numbers but he's out today.  I'll see if I can figure out where they live.20:36
portanteredbo: thanks20:36
*** vjujjuri has quit IRC20:40
*** HenryG has quit IRC21:04
claygpeluse_: check out test.unit.proxy.controller.test_obj21:07
*** HenryG has joined #openstack-swift21:07
claygpeluse_: but at leaast part of it is strategy for the moment - it would have been great to run through a matrix high-bandwidth on Friday and look for some general strategies to apply21:08
claygit's unclear to me what to do with a primary connection when we have to throw it out for a duplicate or because it missed a durable - there may be some hidden knowledge on the node we could expose to the proxy with x-backend headers about "other available fragments" - and esspecially since we already have a socket - it may be cheaper than a new connection to a handoff node21:10
peluse_clayg, yeah, I was looking there and also looking at something similar to TestECMismatchedFA and agree wrt strategies, etc.  Right now just trying to get a base test together that allows me to dictate the sceanrios we white boarded.  Have a few ideas so will work on them and ping ya maybe tomorrow sometime if I get stuck21:29
notmynamehas anyone thought about implementing CORS as middleware instead of in the proxy? I don't remember if there's anything in there that requires it to be in the proxy21:30
notmynamethere's a current cross-project spec to have a common cors middleware21:31
peluse_or maybe even a smaller version, CORS light (couldnt resist)21:31
*** peluse_ is now known as peluse21:31
*** ChanServ sets mode: +v peluse21:31
notmynamenice :-)21:32
notmynamewe already had keystone and keystone light21:32
notmynameand PBR21:32
notmynameand now Fernet tokens in keystone21:32
*** swdweeb has quit IRC21:49
*** mwheckmann has quit IRC21:52
*** geaaru has quit IRC21:53
*** joeljwright has left #openstack-swift21:54
openstackgerritMauricio Lima proposed openstack/swift: Uncomment [filter: keystoneauth] and [filter: authtoken] sessions  https://review.openstack.org/18575522:00
*** annegentle has quit IRC22:13
*** kutija has quit IRC22:14
*** wbhuber has quit IRC22:21
claygCORS light - lawl22:23
morganfainbergnotmyname: Fernets!22:26
notmynamemorganfainberg: if I didn't know better, I'd say that openstack likes to drink ;-)22:27
morganfainbergnotmyname: well i mean, we are moving to flask for keystone so we have somewhere to put the fernet22:28
mattoliveraumorning all!22:29
claygmorning mattoliverau22:32
notmynameyo22:34
*** annegentle has joined #openstack-swift22:36
pelusemornin'22:40
*** km has joined #openstack-swift23:04
*** chlong has joined #openstack-swift23:09
*** annegentle has quit IRC23:11
*** asettle has joined #openstack-swift23:12
*** chlong has quit IRC23:15
openstackgerritMerged openstack/swift: EC: don't 503 on marginally-successful PUT  https://review.openstack.org/18079523:16
*** annegentle has joined #openstack-swift23:17
*** jrichli has quit IRC23:18
*** kei_yama has joined #openstack-swift23:18
*** annegentle has quit IRC23:29
*** annegentle has joined #openstack-swift23:33
*** jamielennox is now known as jamielennox|away23:42
*** chlong has joined #openstack-swift23:44
*** annegentle has quit IRC23:45
*** annegentle has joined #openstack-swift23:50
*** ho has joined #openstack-swift23:50
notmynameclayg: turns out that doing the spawn_n for container listing updates works. until you run tests. then you get a whole lotta fun23:56
mattoliveraunotmyname: cool your giving that a go, awesome! One take away from summit.. container listings or object listings, I thnk I need to change my vocab :)23:59
notmynamemattoliverau: heh23:59
notmynamemattoliverau: it's whichever one I mean23:59
clayglol23:59

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