Thursday, 2015-06-25

*** david-ly_ has joined #openstack-swift00:06
*** david-lyle has quit IRC00:08
*** dmorita has joined #openstack-swift00:14
*** esker has quit IRC00:15
*** gyee_ has quit IRC00:17
*** esker has joined #openstack-swift00:25
*** kei_yama has quit IRC00:32
*** kei_yama has joined #openstack-swift00:36
*** nadeem has quit IRC00:44
*** nadeem has joined #openstack-swift00:47
*** nadeem has quit IRC00:52
*** jrichli has joined #openstack-swift00:53
*** wbhuber has joined #openstack-swift01:10
*** Kennan has left #openstack-swift01:11
*** DericHorn-HP has joined #openstack-swift01:16
asettlenotmyname, going through your instructions for my mac now. I"ll let you know how it goes ;)01:16
notmynameasettle: great. I'd appreciate any feedback01:23
asettleWill do :)01:24
notmynameasettle: if you could email them to me, that would be better than pasting them in here. I'll be traveling the next few days, and email will be easier to access01:24
notmynameasettle: me@not.mn01:24
asettleWill do :) so far, so good! :)01:24
asettleNo complaints01:24
asettleOther than the provisioning is going to take another hour :p but that's hardly your fault.01:24
notmynameasettle: yeah, you just gotta get faster internets down under ;-)01:25
asettlenotmyname, don't even start *facepalm* that's a never ending problem.01:26
notmynameasettle: I'm told that the best thing is to ask mikal about the NBN01:27
asettleSure, if you'd like him to start running around screaming and hitting things. mattoliverau am I wrong?! :p01:27
mattoliverauThat's right, that's why definitely mention it to him ;)01:30
*** DericHorn-HP has quit IRC01:31
*** david-ly_ is now known as david-lyle01:36
asettleAlso notmyname Lana was interested to hear what you wanted regarding our email convo :)01:36
mattoliverauasettle: careful I get picked on for shortening works stralian like (re: convo)01:37
mattoliverau*words even01:37
asettle... convo isn't common?01:38
asettleDamn.01:38
asettleI said 'arvo' and 'mate the other day and Andy McCrae laughed at me for 5 minutes.01:38
asettle:(01:39
asettleI never think I'm particularly Australian until I see people from overseas.01:39
mattoliveraulol, yup.. they used to make fun of me in the UK bout that stuff.. but it's my fault, I'd make fun of them too.. and I was in their country :P01:39
mattoliverauLike I do to Americans at swift mid-cycles :P01:39
asettleHeh.01:41
occupantone time I met an australian in a bar and he said "with all these SUVs driving about, it's like I'm in the I cheem". I paused for a momentm, wondering what the fuck he'd just said. Seeing my look of confusion, he said "you know, with Mr. T"01:41
asettleHAHA01:45
asettleOur pronunciation of the alphabet is pretty shocking01:46
asettleI asked one of the US guys to send me over a document so I could 'Take a squiz at it'01:46
asettleI got pulled up because apparently in urban dictionary the definition isn't as savoury as the Australian meaning.01:47
*** darrenc has joined #openstack-swift01:55
*** dontalton has quit IRC01:56
*** asettle is now known as asettle-afk02:02
*** DericHorn-HP has joined #openstack-swift02:11
*** DericHorn-HP has quit IRC02:12
*** DericHorn-HP has joined #openstack-swift02:14
*** DericHorn-HP has quit IRC02:17
notmynamemattoliverau: I just thought aussies weren't bothered by the "savory" meanings as much as americans are02:23
mattoliveraunotmyname: we're just ignorant :P02:25
*** bkopilov has quit IRC02:33
*** amit213 has quit IRC03:12
*** zul has quit IRC03:13
*** amit213 has joined #openstack-swift03:13
*** asettle-afk is now known as asettle03:15
*** blmartin_ has joined #openstack-swift03:16
*** zul has joined #openstack-swift03:16
*** doxavore has quit IRC03:20
asettlenotmyname, Completed the installation without a hitch!03:37
*** kota_ has joined #openstack-swift03:42
*** ChanServ sets mode: +v kota_03:42
*** nexusz99 has joined #openstack-swift03:50
*** bkopilov has joined #openstack-swift03:54
*** wbhuber has quit IRC04:07
*** jrichli has quit IRC04:17
*** esker has quit IRC04:18
*** esker has joined #openstack-swift04:18
*** esker has quit IRC04:23
*** nexusz99 has quit IRC04:23
*** nexusz99 has joined #openstack-swift04:23
blmartin_Good night all. Have a good day04:24
*** blmartin_ has quit IRC04:24
*** nexusz99 has quit IRC04:28
*** DericHorn-HP has joined #openstack-swift04:28
*** madhuri_ has joined #openstack-swift04:33
*** sorrison_laptop has quit IRC04:45
*** amandap_ is now known as amandap04:48
*** blmartin has quit IRC05:00
*** SkyRocknRoll has joined #openstack-swift05:02
*** madhuri has joined #openstack-swift05:04
*** madhuri has quit IRC05:13
*** sorrison_laptop has joined #openstack-swift05:19
*** esker has joined #openstack-swift05:19
*** esker has quit IRC05:32
openstackgerritKota Tsuyuzaki proposed openstack/swift: Add one more test for ssync_receiver  https://review.openstack.org/19451805:35
openstackgerritKota Tsuyuzaki proposed openstack/swift: WIP: Fix missing container update  https://review.openstack.org/18673505:43
*** madhuri_ has left #openstack-swift05:44
claygkota_: i see the commit message is WIP - i'm guessing you either agree with torgomatic and my assment - or have a better plan?05:47
*** nexusz99 has joined #openstack-swift05:48
kota_clayg: agree with torgomatic comments.05:48
claygright oh05:48
kota_clayg: I'm now planning to change my implementation to push the missing container_update instead of just 503 returning.05:49
kota_push into footers05:49
*** nexusz99 has quit IRC05:49
claygkota_: maybe i need to look at the tests closer - it wasn't obvious to me how the initial connections would ever *not* have the full set of outgoing headers (unless you run out of nodes)05:50
kota_I guess, you are right, unless we run out of nodes, it should not happen.05:51
*** asettle has quit IRC05:51
kota_but I guess the available nodes are depends of config...05:52
kota_request_node_counts, maybe05:52
*** zaitcev has quit IRC05:53
kota_s/request_node_counts/request_node_count/05:53
claygyeah - i knew what you ment05:53
claygok, gl05:54
kota_clayg: thx!05:54
claygi still like just sending down data quorum + container quorum updates and callin' it a day - i.e. itertools.islice(itertools.cycle(container_nodes)) in _backend_requests05:59
*** esker has joined #openstack-swift05:59
*** DericHorn-HP has quit IRC06:04
*** tellesnobrega has quit IRC06:05
kota_clayg: ok, let me consider that. And I noticed now you commented before I pushed the rebased patch set.06:06
claygno worries06:06
cschwedeGood Morning!06:12
kota_cschwede: Good morning!06:13
*** esker has quit IRC06:15
claygcschwede: I think today i like x-object-fresh-sysmeta [and x-object-fresh-meta when we get around to implementing updatable object metadata and need some place to stick v1 style post behiavor metadata]06:28
claygsomething about mass ~= en masse doesn't really convey the life cycle of the metadata they way I'd like06:28
claygand I really would rather we not couple metadata lifecycle with use-case so tightly - it's already akward enough that x-object-sysmeta has a sperate life cycle than x-object-meta06:30
claygidk, maybe it's more confusing if for the time being x-object-meta has the same lifecycle as x-object-fresh-sysmeta06:31
clayg... and I don't even know if x-object-fresh-sysmeta replaces pre-eixsting x-object-sysmeta - or if it just adds to it?06:34
*** nexusz99 has joined #openstack-swift06:39
*** ian_brown has quit IRC06:40
*** esker has joined #openstack-swift06:41
claygok - so i don't know about the the massmeta usecase to understand something here06:42
clayg*if* we had updateable object metadata (a la container system metadata handling) - would the encryption metadata stuff that's replaced on PUT or POST want to change with every post?06:43
*** proteusguy has quit IRC06:47
openstackgerritMatthew Oliver proposed openstack/swift-specs: Add Spec Lifecycle Rules to readme  https://review.openstack.org/19006606:53
*** nexusz99 has quit IRC06:54
*** esker has quit IRC06:56
*** aix has joined #openstack-swift06:56
mattoliveraucschwede: morning07:01
*** rledisez has joined #openstack-swift07:16
*** welldannit has joined #openstack-swift07:22
*** welldannit has quit IRC07:22
*** esker has joined #openstack-swift07:23
claygmattoliverau: cschwede is ignoring me07:29
mattoliverauclayg: me too :(07:29
cschwedeclayg: morning/evening! sorry, i’m not ignoring you, just need to wrap my head around it again07:30
cschwedekota_: mattoliverau: morning/evening too :)07:30
mattoliveraulol07:30
mattoliverauswift, where people are too friendly and get feelings hurt if you don't say hi :P07:31
kota_mattoliverau: lol07:32
kota_I'm getting back home, I might get cold this morning so finish up today's work.07:33
kota_see you tommorow07:33
cschwedeclayg: awesome writeup in patch 158401 !07:34
patchbotcschwede: https://review.openstack.org/#/c/158401/07:34
cschwedekota_: have a nice evening!07:34
*** kota_ has quit IRC07:34
claygcschwede: you say that I feel like I have to go re-read what I wrote - I'm not seeing it - I rambled and bitched a little bit - bust mostly just admited there's no obvious answer and this is hard and we probably don't even yet have all the options on the table07:36
claygwhich is a really crappy place to be trying to make a decision from07:36
cschwedeclayg: you don’t have to re-read it, but it’s a really nice summary on what’s going with all the metadatas and that this needs more thought. i think you summarized the situation well!07:37
claygok :\07:37
*** esker has quit IRC07:38
claygi guess if you let middleware set x-object-sysmeta on post you loose two things 1) setting "some" x-object-sysmeta on post doesn't *guarantee* x-object-sysmeta that was set on PUT is cleared 2) if you set some x-object-sysmeta on PUT another piece of middleware could come along later and overwrite your sysmeta on POST with a new value in same key07:41
*** sorrison_laptop has quit IRC07:41
clayg#2 is a paper tiger - middlewares have a potential to conflict07:42
*** jordanP has joined #openstack-swift07:42
clayg#1 is something maybe - but can be solved by making sure you always add a x-object-sysmeta key/value to a POST for the keys that may have been set on a PUT you want wiped out07:44
claygI don't *think* there's really a usecase for "set this one metadata value and wipe out everything else" - it's just a thing our existing crappy user-metadata implemenation *does*07:44
claygbut that existing crappy implementation already allowed *some* metadata with the data file to bleed up through a metadata update - that's why my quick "let post set sysmeta" works - if there's sysmeta down on the datafile it will "pass-through" to a metadata update07:46
cschwedeoh yes, i think we could do better with this, but the challenge will be to don’t break existing implementations.07:46
claygI think this is a totally reasonable behavior07:46
cschwedesometimes i think we’re juggling to many things at the same time07:46
claygjust need another layer of abstraction07:47
claygshit notmyname is OOO tomorrow - maybe I find jirichi online :\07:48
claygif nothing else she might be able to point me down the patch chain at who is expecting massmeta to work and how07:49
claygbah patch 165517 fake footers is the one that really needs some work07:52
patchbotclayg: https://review.openstack.org/#/c/165517/07:52
claygstring the trailing metadata mime document conversation stuff back up into replication07:52
*** geaaru has joined #openstack-swift07:52
claygcschwede: I think you might e right  juggling to many things at the same time07:53
*** sorrison_laptop has joined #openstack-swift07:54
mattoliverauk, I'm going to cook some dinner.. but the wife is away tonight, so probably be back later :)07:56
mattoliverauclayg: I assume you'll finally be in bed by the time I get back, so night.. tho you are clayg and apparently you never need to sleep.07:56
cschwedeehh, i think swiftclient tests are broken on the gate :/07:58
cschwedehttps://review.openstack.org/#/q/status:open+project:openstack/python-swiftclient,n,z07:59
cschwedefailures are always the same07:59
*** esker has joined #openstack-swift08:04
*** lyrrad has quit IRC08:10
*** lyrrad has joined #openstack-swift08:16
*** esker has quit IRC08:20
*** nexusz99 has joined #openstack-swift08:24
*** nexusz99 has quit IRC08:29
*** sorrison_laptop has quit IRC08:30
*** joeljwright has joined #openstack-swift08:33
*** ChanServ sets mode: +v joeljwright08:33
*** haypo has joined #openstack-swift08:39
openstackgerritDaisuke Morita proposed openstack/swift: Improvement of logging for invalid policies  https://review.openstack.org/14123808:41
*** esker has joined #openstack-swift08:46
*** ppai has joined #openstack-swift08:46
openstackgerritClay Gerrard proposed openstack/swift: Fix ValueError in ssync_receiver  https://review.openstack.org/19545708:53
openstackgerritClay Gerrard proposed openstack/swift: Make ssync send a better HTTP client  https://review.openstack.org/19545808:53
claygyou have to *ease* back into these things08:54
claygg'night08:54
*** esker has quit IRC09:01
openstackgerritChristian Schwede proposed openstack/python-swiftclient: Rename `obj` to `name` in *_object wrappers  https://review.openstack.org/18981509:13
openstackgerritMerged openstack/swift: Replace xrange() with six.moves.range()  https://review.openstack.org/18546009:13
joeljwrightcschwede: I think we need to discuss https://review.openstack.org/189815 again09:14
joeljwrightuntil last night I hadn't fully understood the impact this patch could have on people09:15
cschwedejoeljwright: well, yes. though the error in the swiftclient functional tests are not related to that patch, the same happens for multiple swiftclient patches atm: https://review.openstack.org/#/q/status:open+project:openstack/python-swiftclient,n,z09:15
cschwedejoeljwright: yes, i assumed an impact; i didn’t expect it on the gate though :)09:15
joeljwrightshould we save this patch for a larger API tidy up that breaks compatability?09:17
joeljwrightfor now I think it should probably be just a doc update09:18
cschwedeagreed; if you have other api changes in mind we should bundle them, cut a release from that and raise a big red flag then09:21
cschwedebut do you want to include in a doc update? the patch doesn’t update the docs?09:21
joeljwrightwell the 4 names for the same thing is confusing09:21
joeljwrightthe idea of the patch was to clear up confusion09:22
joeljwrightinstead of a code change, this could (for now) be extra docstrings09:22
joeljwrightI don't have any good reason for breaking API compatibility at the moment, but that might change as we improve the swiftclient in the coming months09:24
*** esker has joined #openstack-swift09:28
*** mfalatic has quit IRC09:29
cschwedeah, ok - you mean docstrings. yes, that’s a good idea09:36
*** nexusz99 has joined #openstack-swift09:40
*** dmgweb has joined #openstack-swift09:41
openstackgerritMerged openstack/swift: Add policy support to dispersion tools  https://review.openstack.org/18545909:42
dmgwebhello :)09:42
dmgwebanyone knows because swift can give the following error ? INFO:swiftclient:RESP STATUS: 503 Internal Server Error09:43
dmgwebI'm going crazy , searching in google but I can not solve .09:43
*** esker has quit IRC09:44
*** nexusz99 has quit IRC09:47
openstackgerritDaisuke Morita proposed openstack/swift: object-updater runs for all async_pending directories  https://review.openstack.org/14125209:52
*** dmorita has quit IRC10:06
*** dmgweb has quit IRC10:09
*** esker has joined #openstack-swift10:11
*** husanu3 has joined #openstack-swift10:19
*** husanu3 has quit IRC10:25
*** husanu1 has joined #openstack-swift10:26
*** husanu1 has quit IRC10:28
*** esker has quit IRC10:29
*** husanu2 has joined #openstack-swift10:30
*** husanu2 has quit IRC10:31
*** jasondot_ has joined #openstack-swift10:32
*** jasondot_ is now known as jasondotstar10:37
openstackgerritMichael Barton proposed openstack/swift: go: replicator only read files once  https://review.openstack.org/19551010:39
*** SkyRocknRoll has quit IRC10:51
*** gar has joined #openstack-swift10:51
*** gar has joined #openstack-swift10:51
kragnizjoeljwright: cschwede: yup, I think at least put that patch on hold for a while10:54
*** esker has joined #openstack-swift10:54
joeljwrightkragniz: thanks, I think that's for the best atm10:58
*** breitz has quit IRC11:02
*** breitz has joined #openstack-swift11:02
*** esker has quit IRC11:11
*** SkyRocknRoll has joined #openstack-swift11:15
*** david-lyle has quit IRC11:17
*** david-lyle has joined #openstack-swift11:21
*** nexusz99 has joined #openstack-swift11:31
*** proteusguy has joined #openstack-swift11:32
*** nexusz99 has quit IRC11:36
*** esker has joined #openstack-swift11:37
*** EmilienM|off is now known as EmilienM11:38
*** SkyRocknRoll has quit IRC11:46
*** jasondotstar has quit IRC11:50
*** esker has quit IRC11:54
*** silor has joined #openstack-swift12:06
*** thurloat_isgone is now known as thurloat12:11
*** nexusz99 has joined #openstack-swift12:11
*** gar has quit IRC12:17
*** esker has joined #openstack-swift12:21
*** kei_yama has quit IRC12:26
*** bkopilov has quit IRC12:32
*** david-ly_ has joined #openstack-swift12:35
*** resker has joined #openstack-swift12:36
*** esker has quit IRC12:38
*** david-lyle has quit IRC12:39
*** gar has joined #openstack-swift12:45
*** gar has joined #openstack-swift12:45
*** jasondotstar has joined #openstack-swift12:46
*** husanu5 has joined #openstack-swift12:50
*** husanu5 has quit IRC12:52
*** tellesnobrega_ has joined #openstack-swift12:55
*** resker has quit IRC12:55
*** esker has joined #openstack-swift12:55
*** husanu5 has joined #openstack-swift12:56
*** husanu5 has quit IRC13:00
*** amoturi has joined #openstack-swift13:03
*** km has quit IRC13:04
*** petertr7_away is now known as petertr713:05
*** gar has quit IRC13:08
*** gar has joined #openstack-swift13:11
*** gar has joined #openstack-swift13:11
*** ppai has quit IRC13:11
*** husanux3 has joined #openstack-swift13:13
*** husanux3 has quit IRC13:13
*** barker has joined #openstack-swift13:14
*** husanux0 has joined #openstack-swift13:14
*** husanux0 has quit IRC13:18
*** husanux7 has joined #openstack-swift13:20
*** husanux7 has quit IRC13:21
*** husanux9 has joined #openstack-swift13:25
*** janonymous_ has joined #openstack-swift13:26
*** husanux9 has quit IRC13:29
*** barker has quit IRC13:33
*** barker has joined #openstack-swift13:45
*** tellesnobrega_ has quit IRC13:51
*** tellesnobrega has joined #openstack-swift14:01
*** bkopilov has joined #openstack-swift14:02
*** barker has quit IRC14:03
*** blmartin has joined #openstack-swift14:04
*** peluse has quit IRC14:04
*** tellesnobrega has quit IRC14:11
*** tellesnobrega has joined #openstack-swift14:14
*** jrichli has joined #openstack-swift14:15
*** wbhuber has joined #openstack-swift14:20
*** blmartin_ has joined #openstack-swift14:22
openstackgerritVictor Stinner proposed openstack/swift: Use six to fix imports on Python 3  https://review.openstack.org/18545314:22
*** pgbridge has joined #openstack-swift14:23
*** tellesnobrega has quit IRC14:24
*** esker has quit IRC14:29
*** esker has joined #openstack-swift14:30
*** esker has quit IRC14:35
*** jlhinson has joined #openstack-swift14:42
*** acoles_away is now known as acoles14:49
acolespeluse: looks like mattoliverau and kota got to the dispersion tools review before me14:50
acolesmattoliverau: kota: thanks^^14:50
notmynamehello14:54
notmyname(just checking in before I go pack--I'm traveling to visit my grandparents today. will be there through the weekend)14:54
jrichlinotmyname: could you add the hotel block web link to the hackathon invite?15:00
jrichlihttp://home2suites.hilton.com/en/ht/groups/personalized/A/AUSTDHT-SWI-20150809/index.jhtml?WT.mc_id=POG15:00
*** fifieldt has joined #openstack-swift15:00
notmynameon it15:00
jrichlinotmyname: thanks.  Have fun with the grandparents!15:00
*** david-ly_ is now known as david-lyle15:01
*** fifieldt has quit IRC15:01
*** fifieldt has joined #openstack-swift15:01
notmynamejrichli: done15:02
jrichligreat, thx!15:03
*** lpabon has joined #openstack-swift15:05
*** jasondotstar has quit IRC15:10
jrichliclayg: I am gathering some info about how massmeta is used.  lemme know when u can chat15:14
*** blmartin__ has joined #openstack-swift15:14
acolesjrichli: clayg i am just looking at the massmeta review15:14
jrichliacoles: ok, thanks.  My comment to clayg was re to some things he chatted about last night in channel15:16
acolesjrichli: ok. i'll reply to clayg review comments on gerritt15:17
acolesjrichli: lemme know if we need a skype or whatever to sort it all out15:17
jrichliwill do15:17
*** blmartin has quit IRC15:18
notmynamehttps://bugs.launchpad.net/swift/+bug/146878215:24
openstackLaunchpad bug 1468782 in OpenStack Object Storage (swift) "Swift proxy crashes on CORS request" [Undecided,New]15:24
*** DericHorn-HP has joined #openstack-swift15:27
jrichlinotmyname: I will try Dmitry's fix.  Although I am still learning, so somebody else might want to also be tackling this.15:31
notmynamejrichli: looks fairly straightforward. however, a test will be required. probably a good place to start15:31
jrichligot it15:32
*** mjseger has joined #openstack-swift15:40
*** annegentle has joined #openstack-swift15:40
*** ppai has joined #openstack-swift15:43
*** jasondotstar has joined #openstack-swift15:45
*** annegentle has quit IRC15:52
*** annegentle has joined #openstack-swift15:52
acolesjrichli: i was thinking about reversing the dependency of patch 163806 and patch 158401 so that 163806 could be merged15:59
patchbotacoles: https://review.openstack.org/#/c/163806/15:59
acolespatch 15840115:59
patchbotacoles: https://review.openstack.org/#/c/158401/15:59
acolesjrichli: but that would mean your dependent chain would need to be rebased (although it will anyways once one of those changes)15:59
acolesjrichli: what do you think?16:00
jrichliacoles: sounds good16:00
acolesjrichli: ok16:00
acoleslets see if i can remember how to do this :D16:00
*** nadeem has joined #openstack-swift16:01
*** nadeem has quit IRC16:01
*** SkyRocknRoll has joined #openstack-swift16:01
*** nadeem has joined #openstack-swift16:02
*** lcurtis has joined #openstack-swift16:05
*** ppai has quit IRC16:07
openstackgerritAlistair Coles proposed openstack/swift: Allow middleware to override metadata header checking  https://review.openstack.org/16380616:11
openstackgerritAlistair Coles proposed openstack/swift: Enable middleware to set metadata on object POST  https://review.openstack.org/15840116:11
*** greghaynes has joined #openstack-swift16:12
*** jordanP has quit IRC16:16
*** annegentle has quit IRC16:17
*** DericHorn-HP has quit IRC16:20
*** peluse has joined #openstack-swift16:23
*** petertr7 is now known as petertr7_away16:24
*** esker has joined #openstack-swift16:25
*** esker has quit IRC16:25
*** esker has joined #openstack-swift16:25
*** doxavore has joined #openstack-swift16:35
*** rledisez has quit IRC16:42
*** jasondotstar has quit IRC16:55
*** DericHorn-HP has joined #openstack-swift17:05
*** esker has quit IRC17:05
*** jasondotstar has joined #openstack-swift17:08
claygi'm awake - probably going toward the office soon17:10
claygjrichli: i really want to understand the life cycle of of the "system metadata updated on every post" in an post-updateable-object-metadata world17:11
claygacoles: 1(a) isn't a symantic limitation of sysmeta - it's just a technical limitation - middleware can't change individual items because that's not possible - the question is if middleware *could* make use of what we have implemented and sysmeta seems to have missed the use-case where you want to overwrite a subset of keys via POST that may have been set on PUT (needed for encryption)17:16
*** petertr7_away is now known as petertr717:16
*** nexusz99 has quit IRC17:17
clayg1 (b) is a paper tiger - middleware needs to coordinate on sysmeta namespacing - and since they're in the pipeline they can set whatever sysmeta they want on any PUT or POST17:17
claygif a middleware doesn't want something lost it needs to a) set it on PUT and b) set it on every POST17:17
clayg^ but that's the same as massmeta17:17
claygsysmeta fixed the .data metadata getting lost on a post - if you squint - it's *already* updatable metadata - you just get two timestamps (data & meta) instead of N17:18
openstackgerritCharles Hsu proposed openstack/swift: Fix reconstructor stats mssage.  https://review.openstack.org/19527517:32
acolesclayg: 1(a) agree (I think) its a current technical limitation that today you cannot update individual items of sysmeta on object POST. Let me think some more about how easy/hard it is to overcome that limitation.17:33
*** jasondotstar has quit IRC17:34
acolesclayg: 1(b) we can't let a middleware change *all* sysmeta on a POST because that would blat EC (and crypto) sysmeta (e.g. encrypted etag) that can't be regenerated easily on a POST.17:36
claygohai17:36
acoles1(b) argues that any change to sysmeta on POST must be selective17:36
claygacoles: isn't already if the keys don't collide?17:36
claygacoles: I mean in my curl snippet with the oneline diff to allow sysmeta into .meta files17:37
claygacoles: I set bar to baz on PUT and foo to bar on POST - afterwards I had a merge of the both17:37
claygsubsequent post wipes out foo, and I can overwrite bar with a POST17:37
claygseems to be what crypto needs17:37
claygall it has to do is not overwrite ec metadata that was set on PUT (I think)17:38
*** occupant has quit IRC17:38
acolesclayg: yes. the change you made was ==  "any change to sysmeta on POST must be selective", you didn't replace all sysmeta with the new set.17:38
claygacoles: and that's what crypto needs right?17:38
claygacoles: it's also sorta how you would expect to use updatable object metadata17:39
*** jasondotstar has joined #openstack-swift17:39
acolesclayg: yes but selective changes to sysmeta that was 1(a)and like i said i need think about the implications wrt consistency because you have challenged my status quo on that one :P17:40
claygi'm such a bastard17:40
acolesclayg: like, maybe we can...17:41
acolesheh17:41
claygacoles: I sorta want to just "try it out"17:41
claygacoles: like take jrichli's patch change and rebase it on the oneline let sysmeta into posts and find out what breask?17:41
jrichliclayg, acoles: just got back from lunch.  reading scrollback17:43
*** occupant has joined #openstack-swift17:43
acolesclayg: so it would be "any sysmeta that is ever changed on a POST must either be set again on subsequent POST or it gets lost" ?17:44
claygjrichli: how far up the patch chain do I have to get to for something that is setting massmeta on PUT/POST17:44
acoleshmmm17:44
claygacoles: yeah but that's true already!  I mean - we just called it massmeta17:44
acolesclayg: is that what i did ? :P17:47
clayganyway i'm not sure this life-cycle would exist if we had updatable object metadata - so i'm cautious of making a whole new namespace for it - esspecially since it seems like sysmeta is already really really close to updatable object metadata17:47
claygyou can set sysmeta on a data and it stays with the data unless you overwrite it in the meta - can easily extend to you can set sysmeta and it stays unless you overwrite it17:48
claygacoles: YES!  I'm totally just grabbing your cool thing like a thug and running with it!17:48
claygacoles: anyways - it doesn't have to be answered this morning/evening17:49
claygacoles: you think - and I'll try to get jrichli to get me a patch that I can rebase on expanded lifecycle sysmeta to see if it works17:49
jrichliclayg: https://review.openstack.org/#/c/194191/ uses metadata17:49
claygjrichli: is that the *first* one?  it's sorta deep :\17:50
jrichliforgive me if I am saying something that is obvious or that you already know: one thing about the massmeta is that it is paired with user-meta items17:50
jrichliyes.  the first 3 patches are changes alistair made in core swift - but they dont add any encryption17:51
jrichlithe "life-cyle" of the massmeta (this is used for storing what we have deemed "crypto-meta") has to match that of the corresponding user-meta17:52
jrichlimetadata items are storing off the cypher-alg and nonce - and whatever else is needed to decrypt17:53
claygjrichli: i see 1) add massmeta 2) make fakefooters 3) keymaster 4) crypto 5) encrypter-uses-sys(mass?)-meta17:53
jrichliyes :-)17:54
acolesclayg: there is a difference - massmeta behaves exactly like user-meta, on a POST all existing massmeta is discarded. What you are suggesting is that on a POST only the keys in the posted sysmeta get discarded. SO you get a merge of data file and meta file items. Ain't saying that can't work, but thats the difference I want to ponder wrt eventual consistency.17:54
jrichlithere was one more in there somewhere ...17:54
*** breitz has quit IRC17:54
acoles(had to say the "eventual consistency" words eventually :)17:55
acolesclayg: jrichli i just reordered the chain and +A'd the first - did it land?17:56
claygacoles: i saw the +a17:56
openstackgerritGreg Lange proposed openstack/swift: go: add ability to lock device/drive with file on file system  https://review.openstack.org/19568917:56
*** tellesnobrega has joined #openstack-swift17:56
*** petertr7 is now known as petertr7_away17:57
*** petertr7_away is now known as petertr717:57
acolespatch 163806 no its still in the queue17:57
patchbotacoles: https://review.openstack.org/#/c/163806/17:57
*** NM has joined #openstack-swift17:57
*** breitz has joined #openstack-swift17:57
claygacoles: so that's *1* down ;)17:58
acolesclayg: progresssss :)17:58
claygjrichli: is sysmeta and/or massmeta encrypted?17:59
acolesclayg: ok i supposed to spend time with family this evening apparently. I will think while you run with it!17:59
claygjrichli: you said massmeta lives "with the user-metadata"17:59
jrichlino.  only user-meta, etag, and content-type17:59
claygacoles: sounds like a great plan!17:59
claygacoles: thank you so much17:59
jrichliacoles: thanks17:59
acolesclayg: jrichli : g'nite17:59
acolesclayg: no thank you for challenging the thinking18:00
claygjrichli: so when you go to decrypt user-metadata - it's not akward hving like ec-sysmeta and x-timestamp and stuff in the bag of metadata - you just pick out the user-metadata and use the crypto-meta in the clear to do what you need to do?18:01
claygmaybe I can find that code...18:01
*** SkyRocknRoll has quit IRC18:01
jrichliclayg: yes.18:02
jrichliwhich code?18:02
*** husanu5 has joined #openstack-swift18:02
*** dontalton has joined #openstack-swift18:02
jrichlithe code where crypto-meta is used?18:02
claygthe code that does the decrypting of user-metadata from the crypto-meta stored in massmeta18:02
jrichlione min18:03
jrichliugh, wait:18:03
jrichlithe patch you have for encrpter / decrypter now only uses massmeta for the crypto-meta of the object body18:04
jrichlii split that out from headers encryption to make an easier review18:04
jrichliso right now, you can look at the body_crypto_meta being used.  Is that enough for now?  Or do you want to see the header processing in the "prototype" review?18:05
claygidk - i want to see if extending sysmeta the way i'm suggesting will cover the crypto use-case18:05
*** jasondotstar has quit IRC18:05
claygit seems like the updated crypto metdata on the POST will be important to understanding that interplay18:06
jrichliprob best to look at the prototype with all the functionatlity: https://review.openstack.org/#/c/157907/18:06
claygjrichli: do you know what acoles and I are talking about when we say "updatable object metadata"18:06
*** acoles is now known as acoles_away18:06
jrichliclayg: one reason that we have a crypto-meta for each different user-meta item is that we need a different nonce for each one18:07
claygoh wow - each user-meta item has it's own nonce!18:07
claygthat's good - that will work *better* with updatable object metadata - was that acoles idea?18:08
jrichliyes.  and everytime a given user-meta item is set/updated, it will need to be re-encrypted with a new nonce.18:08
*** esker has joined #openstack-swift18:08
jrichliI know that acoles had said that *someday* there might be updatable object metadata.  I didnt know he was suggesting it now.  i haven't gotten to thoroughly read this scrollback.18:09
claygno he's not suggesting it now18:09
clayghe's suggesting adding a new metadata namespace that we have to live with forever because we don't have updatable object metdata today18:09
jrichlifor furture-proofing, I would suggest not doing something that locks our encrypted objects into never having updatable obj meta18:09
claygi'm suggesting we don't need it because there's not really a usecase for what this new namespace is doing - it's just an enhanced version of sysmeta - that's acctually closer to where we want to go anyway18:10
jrichliwell yes, that part I knew about :-)18:10
jrichlioh wait - read wrong, sorry18:10
clayganyway - this patch with everything is perfect - i think my plan will work18:12
claygit'll probably be annoying to describe the life-cycle of sysmeta++ but it'll be fine18:12
jrichliok, cool.  for me, I just want a way to store this info, have it persisted, and have it updatable when needed :-)18:12
claygthat's what I'm talking about - get shit done ;)18:13
jrichliand to explain a little more on the nonce : its a crypto thing that makes the meta-data require having a different nonce.  if they use the same one, we can start leaking info18:13
claygi got some ec bugs i'm working on too - but since i'm jazzed about this idea I'll try to get some cycles on it - maybe we present to acoles next week - like monday am skype or something?18:14
jrichlisounds good.18:14
*** husanu5 has quit IRC18:14
* jrichli I guess I will need to install skype on my new mac18:14
petertr7Is it possible to remove/delete headers from objects such as X-delete-at?18:16
*** jasondotstar has joined #openstack-swift18:19
jrichliclayg: oh, and yes - I am pretty sure I know what you mean by updatable obj data.  you mean b/c on a POST, if you update any of user-meta, then the whole set gets replaced with what is in that POST request18:21
jrichliso updatable would mean that you could update one piece - and not have to provide the whole set?18:21
mjsegerclayg: are you aware of issues in which connection,py is not included with the requests library and as a result nagel isn't being disabled?  I just discovered this in 14.04 and am seeing 1K PUTs more that 2X slower than 2K PUTs18:22
hurricanerixpetertr7: you should be able to just supply a empty 'x-delete-at' header.  http://pastebin.com/68phbTzP18:22
mjsegerif I update requests, performance becomes what it should18:22
petertr7hurricanerix, Thanks! I'm going to try that18:25
*** geaaru has quit IRC18:26
petertr7hurricanerix, I actually get this error when I attempt to pass in an empty header "400 Bad Request Non-integer X-Delete-At"18:27
petertr7I'm using python-swiftlicent post_object and passing in the empty string18:27
tdasilvaanybody know of a flag to disable deletes on ssbench? I'd like to leave the data on the cluster, not just the initial data18:28
hurricanerixpetertr7: ahh, let me take a look at the client.18:28
tdasilvaswifterdarrell: ^^^18:28
*** annegentle has joined #openstack-swift18:28
swifterdarrelltdasilva: ya there's a flag for that18:28
swifterdarrellone sec18:29
swifterdarrelltdasilva: -k, --keep-objects    Keep all uploaded objects in cluster;18:29
swifterdarrelltdasilva: for "ssbench-master run-scenario ..."18:30
swifterdarrelltdasilva: (used that when benchmarking the server-per-port stuff, actually) :)18:30
tdasilvaswifterdarrell: thanks! i'm actually looking to test object expiration. Saw the flag for x-delete-after, but then the data was actually getting deleted ;)18:31
*** DericHorn-HP has quit IRC18:31
swifterdarrelltdasilva: heh18:31
hurricanerixpetertr7: Actually, I am pretty sure if you just do "swift post container object" it will remove all headers from the object.  (since existing custom metadata does not persist, when posting new metadata)18:31
hurricanerix*all user-added metadata18:31
swifterdarrelltdasilva: I didn't add the delete-after bit and haven't used it, if that matters18:31
tdasilvaswifterdarrell: it seems to be working correctly....18:32
tdasilvarunning some tests now18:32
swifterdarrelltdasilva: nice!18:32
petertr7Ohh that's so easy. Thanks hurricanerix!18:33
hurricanerixpeluse: np18:33
hurricanerixpetertr7: np18:34
openstackgerritMerged openstack/swift: go: check for empty path parts in object server  https://review.openstack.org/19478918:34
hurricanerixpetertr7: you can also find more info here: http://developer.openstack.org/api-ref-objectstorage-v1.html#updateObjectMeta18:34
hurricanerix(just click "detail" below the one that says "POST")18:35
petertr7Thank you, this is such a conveniently compact page for the api!18:35
openstackgerritMerged openstack/swift: go: make use of filepath.Join() in objectserver main  https://review.openstack.org/19527118:39
*** dontalton has quit IRC18:44
mjsegerdoes anyone want to know why 1K puts are twice as slow of 2K puts?18:45
*** annegentle has quit IRC18:45
*** jasondotstar has quit IRC18:47
*** rbrooker has joined #openstack-swift18:52
*** lastops has joined #openstack-swift18:54
*** lastops has quit IRC18:54
*** hemanthm has joined #openstack-swift19:01
*** jasondotstar has joined #openstack-swift19:07
torgomaticmjseger: I thought you just said it was TCP_NODELAY not being set by an old version of requests library19:07
torgomaticis it something else? that'd be interesting19:07
torgomatic(not that requests's behavior is uninteresting, but it is known)19:08
mjsegertorgomatic: it's complicated, I think.  on a new 14.04 installation, requests is preinstalled, but only some of it, not the urllib3 substree19:08
mjsegerwhen you setup.py install swiftclient, the urllib subtree IS populated BUT connection.py is left off and he's the guy who disables nagel19:09
mjsegerif I manually install requests everyone is happy19:09
mjsegervery odd19:09
*** tellesnobrega has quit IRC19:10
*** blmartin has joined #openstack-swift19:11
*** blmartin_ has quit IRC19:13
*** blmartin__ has quit IRC19:13
mjsegertorgomatic: when you say requests's behavior is known, can you elaborate?19:15
torgomaticmjseger: I thought that old versions of requests did not set TCP_NODELAY, but at some point they added it in19:15
mjsegerahh, right.  this is something very different.  let me try again19:16
mjsegertorgomatic: if you install a brand new 14.04 and clone swiftclient, the right version of requests is indeed there - 2.2.1 - BUT it's missing connection.py.  if you reinstall, you get it, but reinstallation is NOT straightword19:17
torgomaticmjseger: so ubuntu has broken packages? :sadface:19:17
* torgomatic is getting hauled into a meeting; sorry about that19:18
mjsegertorgomatic: I'm not sure.  If I do pip install requests-2.2.1 it tells me it's already installed.  if I try to uninstall it, it tells me it can't because owned by the o/s19:18
mjsegerperhaps a conversation for another day?19:18
*** blmartin has quit IRC19:21
*** tellesnobrega has joined #openstack-swift19:29
*** peluse has quit IRC19:33
*** tellesnobrega has quit IRC19:35
*** blmartin has joined #openstack-swift19:44
*** DericHorn-HP has joined #openstack-swift19:50
*** esker has quit IRC19:54
*** janonymous_ has quit IRC19:56
*** gar has quit IRC19:59
*** thurloat is now known as thurloat_isgone20:01
*** blmartin has quit IRC20:05
openstackgerritVictor Stinner proposed openstack/swift: Get StringIO and cStringIO from six.moves  https://review.openstack.org/18545720:06
openstackgerritVictor Stinner proposed openstack/swift: Replace StringIO with BytesIO in ssync  https://review.openstack.org/18607320:06
openstackgerritVictor Stinner proposed openstack/swift: Replace StringIO with BytesIO for file  https://review.openstack.org/18607220:06
openstackgerritVictor Stinner proposed openstack/swift: Replace StringIO with BytesIO for WSGI input  https://review.openstack.org/18607120:06
openstackgerritMinwoo Bae proposed openstack/swift: EC Reconstructor: Do not reconstruct existing fragments.  https://review.openstack.org/19327920:08
minwoobclayg: I've updated what I currently have, for the rebuilding fragments patch. It is now down to only 1 failing test, of the 5 that were originally failing. I've also added in the unit test for making sure that the reconstructor does not fail when it finds the fragment to be rebuilt.20:14
*** amoturi has quit IRC20:14
minwoobIt now just needs a test for testing duplicates.20:14
claygI didn't do it20:14
minwoobclayg: No worries. I'm working on it now.20:15
claygminwoob: that's great!20:15
claygminwoob: nice work!20:15
claygminwoob: is there anything I can do to help you today?20:15
claygshould I look at what you have?  debug the test failure?  cheer from the sidelines?20:15
minwoobclayg: Possibly taking a look at the 1 remaining failing test, if you have the time.20:15
claygright on!20:15
minwoobclayg: Cool! Thanks!20:15
minwoobclayg: I'll be uploading another patch set soon, for the duplicates.20:16
openstackgerritVictor Stinner proposed openstack/swift: Fix Python 3 issues  https://review.openstack.org/18545020:16
claygminwoob: so it's +6 lines of code and ~100 of test changes - and you're only part way done with tests20:19
claygsounds bout right20:19
claygminwoob: ah interesting - looks like test_reconstruct_fa_with_mixed_old_etag only failures 9/10 times!20:21
claygfor i in {1..10}; do nosetests swift/test/unit/obj/test_reconstructor.py:TestObjectReconstructor.test_reconstruct_fa_with_mixed_old_etag &> /dev/null; echo $?; done20:21
minwoobclayg: Do they normally fail all the time, when they fail?20:22
clayg... to good ones do20:23
claygtests that fail only sometimes are super annoying :'(20:23
minwoobAh.20:23
claygbut 9/10 failures is better than 1/10 failures20:23
minwoobclayg: Right ... because then you might not catch it ...20:24
minwoobuntil it fails in production.20:25
claygwell a lot of times they're just shotty tests20:25
claygbut yeah sometimes there's a real bug there20:26
claygmore often the bugs lurk where there is NO test coverage because no one even thought to write a test for that failure!20:26
*** peluse has joined #openstack-swift20:27
minwoobBy that, I assume you mean cases where no one could think a simple part could fail ...20:29
claygsomething like that - or "how on earth did we end up with *no* data on primaries" or "why would a tombstone that's 6 months hold suddenly show up?" - when you do something a billion times that non-zero aspect of improbable things start to pop up20:31
*** peluse has quit IRC20:32
claygone time the json guy - doug something - came to a company i was working for and talked about software engineering in broard strokes - one thing he said I loved "Saying 'that would rarely happen' is exactly the same as saying 'that happens'"20:32
minwoobclayg: Lol.20:33
claygok, i got it failing 10/10 now20:33
*** jasondotstar has quit IRC20:39
*** silor has quit IRC20:44
*** peluse has joined #openstack-swift20:47
*** peluse_ has joined #openstack-swift20:48
*** peluse__ has joined #openstack-swift20:49
*** peluse has quit IRC20:52
claygminwoob: ok you have to be careful with those calls to next(ts)20:57
claygit's an iterator - so moving where they are called in the test changes their value20:58
claygwhen I get confused I tend to say "t0 = next(ts)" and "t1 = next(ts)" and then use t0 and t1 where I need them20:58
claygbut *sometimes* i just cheat and call next(ts) inline w/o naming it - which is when you have to be careful about moving it before/after another call or inside of a loop20:59
*** ChanServ sets mode: +v peluse__20:59
minwoobclayg: That's interesting. I've also noticed that mixed_new_etag is very similar in this regard, but I have not seen it fail so far.21:02
minwoobclayg: mixed_new_etag the test*21:03
claygyeah - i think that one is like an expected failure condition - a negative test if you will21:03
*** annegentle has joined #openstack-swift21:03
claygminwoob: there was a typo in that gist - i updated it21:04
*** peluse_ has quit IRC21:05
*** petertr7 is now known as petertr7_away21:07
*** DericHorn-HP has quit IRC21:08
*** DericHorn-HP has joined #openstack-swift21:11
*** amoturi has joined #openstack-swift21:13
claygminwoob: yeah mixed_new_etag assertRaises DiksFileError21:14
claygin fact I think when you changed mixed_old_etag to make the bad_requests ts newer - it sort of *became* mixed_new_etag and raised diskfile error just like mixed_new_etag was expected to do :P21:14
minwoobYeah, that's what it looks like.21:18
openstackgerritMinwoo Bae proposed openstack/swift: EC Reconstructor: Do not reconstruct existing fragments.  https://review.openstack.org/19327921:20
minwoobI saw a failure in test.unit.obj.test_updater.TestObjectUpdater21:21
minwoobLooking into it now.21:21
*** jrichli has quit IRC21:24
*** ian_brown has joined #openstack-swift21:41
*** ian_brown has quit IRC21:48
*** annegentle has quit IRC21:58
timburkejoeljwright: thanks for looking at some patches! it makes me sad that global requirements seems to have busted the gate, though21:58
*** anteaya has joined #openstack-swift22:04
anteayaanyone know what return 137 means in the swift-dsvm-funtional job?22:05
anteayawe can't find any logs22:05
anteayaand it is kind of blocking a patch that we would like to merge22:05
anteayahttps://review.openstack.org/#/c/195213/22:05
anteayaI am stuck on how to get more information about why/how this is failing22:05
*** sc68cal has joined #openstack-swift22:06
*** NM has quit IRC22:07
*** pberis has joined #openstack-swift22:08
anteayanotmyname mattoliverau ^^22:09
claygreturn 137?22:10
claygmaybe lits like 1337-speak?22:10
clayganteaya: wow - that just looks like *all* the tests failed!?22:12
claygswift must not be very happy :'(22:12
claygwow - new to me!  HTTPException: got more than 100 headers (txn: tx92bb01cf831142dd9e827-00558c3723)22:14
claygin the proxy logs22:14
claygi wonder what version of python 2.7 this is?22:16
clayg2.7.6-8ubuntu0.2 - seems reasonable22:17
mattoliverauYeah according to the logs, the > 100 headers error starts appearing on reposnses from the container server.. Then it looks like it gets error limited. Is it like a header dict that isn't cleaned up.22:22
claygmattoliverau: i'm not sure why I folow that >100 headers is not reasonable?22:23
joeljwrighttimburke: shame about the gate :(22:23
claygand I can't find any reference to MAXHEADER in my /usr/lib/python2.7/httplib.py22:23
claygjoeljwright: timburke: you get used to it22:23
claygjoeljwright: timburke: plus the first time you find the bug that *fixes* the gate you feel sorta like a hero22:24
mattoliverauI saw something about the rfc822.Message constructor.. So a limit there maybe22:24
joeljwrighttimburke: maybe you could have a look at this patch for me… https://review.openstack.org/#/c/171692/22:24
joeljwrightnow, time for sleep22:24
mattoliverauclayg ^22:24
mattoliverauA limit in that module I mean22:25
claygbut am i mis reading the traceback?  should be in line 279 of httplib.py22:25
mattoliverauOh yeah22:26
timburkejoeljwright: i like that idea! i'll put it on my list. will probably get to it some time next week22:26
*** asettle has joined #openstack-swift22:28
clayglol@  * SECURITY UPDATE: denial of service in multiple servers22:29
clayg    - debian/patches/CVE-2013-1752-httplib-2.patch: limit amount of headers22:29
clayg      in Lib/httplib.py, added test to Lib/test/test_httplib.py.22:29
claygi'm sure we can monkey patch it to 1000 or something22:30
*** jlhinson has quit IRC22:30
* clayg does all the updates22:30
mattoliverauclayg: nice find22:31
claygi can so imagine someone sitting there thinking "yeah I'm pretty sure you don't need more than 100 headers - I mean - that's two zeros for christ's sake"22:31
*** dontalton has joined #openstack-swift22:32
mattoliverauinstead they dos us by making a container server in testing error limitted. That is teh suck.22:34
claygoh wait - timburke - is this the thing that's breaking the gate!?22:34
claygyay!  there it is :)22:35
clayg_MAXHEADERS = 10022:35
timburkeclayg: what, header limits? no. it's something with global dependencies adding requirements that our gate can't parse22:35
claygoh neat - so multiple brokens - that's what Im talking about22:36
mattoliverauThats a great way to start a Friday morning :P22:36
claygis it Friday already?22:36
mattoliverauyeah.. well here it is.22:37
timburkeclayg: see http://logs.openstack.org/87/190887/5/check/check-swiftclient-dsvm-functional/1d3cad1/console.html#_2015-06-24_02_48_27_036 for an example22:37
peluse__hell, I'm outta here then22:37
mattoliveraupeluse__: lol, it is only 8:30am.. so a little too early to call it quits. :P22:37
peluse__damn in22:38
peluse__it22:38
claygtimburke: what the crap is that crap!?22:38
*** peluse__ is now known as peluse22:38
*** thurloat_isgone is now known as thurloat22:39
timburkeclayg: i've been advised by our PTL to "head down to the pub for a pint until it all blows over"22:39
claygtimburke: PTL is good like that22:39
joeljwrighttimburke: sounds like adive you should listen to :)22:40
joeljwrightadvice even22:40
claygtimburke: OTOH, I ignore his sage advice more often than most22:40
claygyou could always just dive in and see what sort of rukus you can cause?22:40
mattoliveraubut it's too early to start drinking!!!... but if the PTL says its ok :P22:40
timburkeclayg: yeah, yeah; after the release22:40
*** lcurtis has quit IRC22:41
notmynamehello. I'm sitting in DFW for a few hours22:41
notmynamecatching up on scrollback...22:41
claygmattoliverau: lol!  "PTL said i could" is my answer for all my bad decisions now22:41
claygtest_bad_metadata3 seems to be the test that maxheaders love to hate22:41
*** joeljwright has quit IRC22:41
mattoliveraulol, sounds like a great t-shirt22:42
timburkeclayg: mattoliverau: in notmyname's defense, it was like 10PM local time when he gave me that advice :P22:45
notmynameseems like I logged in at just the right time ;-)22:45
mattoliveraunotmyname: your PTL sense was tingling :P22:45
*** DericHorn-HP has quit IRC22:45
*** dontalton has quit IRC22:45
*** pberis1 has joined #openstack-swift22:46
*** pberis has quit IRC22:46
notmynameso everything is broken because a CVE added a limit to headers in httplib2?22:51
notmynameand the other broken thing about requirements parsing is still broken? ( timburke?)22:52
mattoliveraulooks like it in both counts22:53
timburkenotmyname: can't speak to the headers, but yes, requirements stuff is still broken22:54
notmynameoh, goody22:54
notmynametimburke: did you go to the pub for a pint?22:54
notmynamebecause clearly it hasn't blown over yet22:54
*** thurloat is now known as thurloat_isgone22:54
timburkenotmyname: *that's* why it's still busted! i was never very good at following directions...22:55
notmyname:-)22:55
claygthat moment when you realize you have no idea how eventlet manages it's monkey patching of stdlib modules22:55
openstackgerritMerged openstack/swift: Allow middleware to override metadata header checking  https://review.openstack.org/16380622:56
*** wbhuber has quit IRC22:57
*** annegentle has joined #openstack-swift22:59
*** nadeem has quit IRC23:00
notmynamethat moment when you see a bot say a patch was merged, but you have no idea what the patch does ;-)23:02
* notmyname looks at openstackgerrit23:02
notmynamecool. it was a crypto patch. glad to see progress there :-)23:05
*** annegentle has quit IRC23:05
claygnotmyname: yeah acoles_away comes back for one day and shows us all up23:05
mattoliveraulol23:08
mattoliverauso acoles_away is why we ever get anything done.. I see that now23:09
*** rbrooker has quit IRC23:22
*** kei_yama has joined #openstack-swift23:27
openstackgerritMerged openstack/swift: go: check for content length parse error on gets in object server  https://review.openstack.org/19527323:32
*** doxavore has quit IRC23:44
*** esker has joined #openstack-swift23:46
*** pberis1 has quit IRC23:46
*** esker has quit IRC23:46
*** esker has joined #openstack-swift23:47
clayghurricanerix: is creith like still "around"?23:48
claygI sort of imagine he may have been one of three people on the planet that acctully had some notion of how eventlet patching worked :'(23:48
clayghttps://gist.github.com/clayg/3b8fb343786efe1b1e3423:48
clayg^ redbo23:48
claygstill waiting on the eventletdev ML post to show up in the archive so i can link that too23:51
anteayaclayg mattoliverau yes thanks for taking a look at that for me23:54
anteayasorry I'm at the neutron mid-cycle23:54
anteayaabout to leave for dinner will be looking at this again in about 16 hours23:55
anteayaany thoughts appreciated23:55
*** esker has quit IRC23:57
clayghere we go -> https://lists.secondlife.com/pipermail/eventletdev/2015-June/001213.html23:59

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