Sunday, 2015-03-29

*** sandywalsh_ has joined #openstack-swift03:34
*** sandywalsh has quit IRC03:34
*** Gues_____ has quit IRC03:57
openstackgerritMonty Taylor proposed openstack/python-swiftclient: Add socket-level timeout parameter  https://review.openstack.org/16867305:42
*** bkopilov has joined #openstack-swift07:48
*** chlong has joined #openstack-swift08:38
*** bkopilov has quit IRC12:41
*** EmilienM|PTO is now known as EmilienM12:42
*** silor has joined #openstack-swift13:24
*** silor1 has joined #openstack-swift13:45
*** silor has quit IRC13:48
*** silor has joined #openstack-swift14:21
*** silor1 has quit IRC14:25
*** dmsimard has quit IRC14:43
*** dmsimard has joined #openstack-swift14:45
*** gsilvis has quit IRC15:00
*** gsilvis has joined #openstack-swift15:01
openstackgerritMonty Taylor proposed openstack/python-swiftclient: Add socket-level timeout parameter  https://review.openstack.org/16867315:04
*** bkopilov has joined #openstack-swift16:26
*** khivin has joined #openstack-swift16:54
*** sandywalsh_ has quit IRC17:03
*** panbalag has joined #openstack-swift17:04
*** sandywalsh has joined #openstack-swift17:05
*** panbalag has quit IRC17:38
*** zaitcev has joined #openstack-swift18:02
*** ChanServ sets mode: +v zaitcev18:02
*** chlong has quit IRC18:15
*** panbalag has joined #openstack-swift18:37
*** panbalag has joined #openstack-swift18:39
*** mmcardle has joined #openstack-swift18:39
*** panbalag has quit IRC18:40
*** barra204 has quit IRC19:04
*** shakamunyi has quit IRC19:04
*** silor has quit IRC19:12
*** david-ly_ has joined #openstack-swift19:21
*** david-lyle has quit IRC19:23
clayghey guys20:04
claygtorgomatic: i thought we stopped getting those weird error limit things when we took the counts out of the rhings20:05
claygmaybe... we have some of the real socket tests that re-use the application between tests doing some failure injection now?20:05
claygbirthday!20:06
claygnoone ever rebases *my* patches :'(20:06
zaitcevmaybe they respect your authorship too much20:09
claygzaitcev: !  hi!20:11
*** Gu_______ has joined #openstack-swift20:11
claygok, so some stuff got merged - that's good - i'll try to audit what we have outstanding and make sure it's all mergable20:12
zaitcevwhat backend do we use under liberasurecode, realistically speaking? jerasure, I presume?20:13
*** Gu_______ has quit IRC20:17
*** Gu_______ has joined #openstack-swift20:19
*** jamielennox is now known as jamielennox|away20:58
mattoliverauMorning21:01
notmynameclayg: mattoliverau: I'm going to eat something, then I'll be looking at what's outstanding, too21:37
openstackgerritClay Gerrard proposed openstack/swift: Fix AttributeError and logging in ECAppIter  https://review.openstack.org/16854321:43
claygwhat happend in bug #143787021:46
openstackbug 1437870 in OpenStack Object Storage (swift) "python-swiftclient 2.4.0 broke WAL-E" [Undecided,New] https://launchpad.net/bugs/143787021:46
openstackgerritClay Gerrard proposed openstack/swift: Add Fragment Index filter support to ssync  https://review.openstack.org/16518821:52
clayg^ missed it by *this* much!21:52
openstackgerritClay Gerrard proposed openstack/swift: wip: ec reconstructor probe test  https://review.openstack.org/16429121:53
openstackgerritClay Gerrard proposed openstack/swift: Erasure Code Reconstructor  https://review.openstack.org/13187221:53
openstackgerritClay Gerrard proposed openstack/swift: Guard against invalid Policy  https://review.openstack.org/16854822:00
claygmattoliverau: good catch on the storage_policy key leaking between tests - but I think it's a more general problem with the setup just attaching the mutable class attribute to each test methods's self.app directly instead of a fresh copy for each test22:01
claygmattoliverau: I think fixing the setup to not do something so likely to cause problems is better than any amount of cleanup we could hope to achive in the indvidual test cases22:01
clayggood eye though - i was totally thinking each test got a fresh app with a fres container_info dict :\22:02
notmynamehere22:07
claygnotmyname: i rebased everyhting and now nothing is verfiedy for merge :P22:08
claygnotmyname: I suppose i'm mostly thinking that I'm going to start trying to pull apart the first few changes for the rebased merge chain22:08
claygeither that or review the reconstructor and see what I can do help peluse with a head start on Monday22:09
clayg... probably both22:09
claygok take a break and go play with kids for awhile :P22:09
notmynameI'm more worried about the reconstructor than the patch chain at this point. maybe just because the reconstructor has gotta be in there22:10
claygok that's good direction - THANKS!22:11
notmynameclayg: you need an ec_review feature branch, right? is that what we decided last week?22:11
claygyeah that's what we came up with in the end22:11
notmynameI'm getting my head around the patches outstanding right now, then I'm going to start looking at any chain leading to the reconstructor22:11
claygbut remember you shoudln't ask me - as cschwede - you and he were the only ones that seemed to remmeber correctly how it worked last time22:11
notmynamelol22:11
notmynameok, I'll get that in the morning (the feature branch) from -infra or ttx22:12
claygnotmyname: yeah np, the first one in the chain up to the reconstructor is pretty great obvious cleanup - should be easy22:12
claygthe ssync frag index support may need more tests - i need a critical review on it22:12
claygthe reconstructor change is great - but probably isn't in it's final form TBH22:12
notmyname-2! (there. that's critical)22:12
claygwell - you have to have constructive critisim too :P22:13
claygit may be fine - i haven't really given it a "review" perspective - and I don't think i'm hte only one who's been working on it22:13
*** jamielennox|away is now known as jamielennox22:20
notmynametorgomatic: I don't know if this uses multi-range requests or just single ranges, but it seems possible that it uses multi-ranges. http://www.flussonic.com/forums/content.php?155-Streaming-files-from-HTTP-storage22:21
notmynametorgomatic: ...in answer to your question about "who cares about multi range anyway"22:21
mattoliverauclayg: yeah fair enough (re: setup refreshing object rather then copying mutable). Sorry Monday morning email, meeting boring stuff.. Back to proper work now.22:22
mattoliverau(Well until an 11 am meeting)22:22
notmynameok, starred patches cleaned up22:31
notmynameultimately, I'd love to see https://review.openstack.org/#/c/164291/ land in the beta (ec probe test)22:31
claygpepAAAAAAAATE!22:31
claygi *litterally* exercise that code in tests - how is that a namerror?22:32
notmynameI'm unsure about https://review.openstack.org/#/c/168254/. the commit message sounds like a pretty important piece of functionality22:33
claygoh heh - nope not *that* line :P22:33
claygnotmyname: no, i don't think so22:34
notmynameack22:34
claygI think yaun may not realize how much error handling torgomatic managed to get into the proxy (he should look at test.unit.proxy.controller.test_obj) - or I'm drastically misunderstanding what he's trying to accomplish with that patch22:35
notmynameok. that was my confusion. I thought it had been handled already by torgomatic22:35
notmynameI'll ignore it until torgomatic is around to comment on it22:36
claygidk, we might have to let tsg or kevin what are the tradeoffs/advantages of feeding decode k or k + m fragments22:38
notmynamethat sounds like a wonderful thing to suss out in a beta ;-)22:38
claygI think that if you can connect to the first k nodes there's absoluately zero value in waiting for the other m nodes to hand you the parity bits - because decode is going to throw them away22:38
claygotoh if you have a say 8 + 6 schema or something and only 7 data nodes come in - there may be some significant advantage to having all of the parity bits available instead of just one?22:39
notmynameit might be a more generic thing with other EC stuff. eg I know kota has their own NTT lib that they'll be using. not sure if it's same algo with faster math like isa-l or if it's whole new algos, though22:39
notmynames/stuff/encodings/22:39
claygnotmyname: if it's going to be that specific (per lib) we may just make the the ec_ndata configurable and idk - validate it's great than k or something?22:40
*** Gu_______ has quit IRC23:03
mattoliverauclayg: I wouldn't have thought that wrapping the container_info dict in a dict() would fix what was happening here.. nice one.23:23
*** kei_yama has joined #openstack-swift23:24
*** annegentle has joined #openstack-swift23:26
*** jrichli has joined #openstack-swift23:32
claygmattoliverau: well it creates a new dict with the same keys and values - which is mostly good enough to prevent anything a test does to self.app.container_info from manipulating the state in the next test run - *technially* I probably should deepcopy or whatever it's called - i can never remember23:33
claygright now I'm being all bitter about functools.partialmethod having only been added in python3.423:33
mattoliverauclayg: meh, it worked! jenkins likes it, and it passed on my local machine, so it does enough :)23:33
claygbha - what a, it's a freaking property descriptor (of course) - i don't want to backport all tha tnoise23:34
notmynamehttps://review.openstack.org/#/c/168076/ landing23:35
mattoliverauclayg: it's a weekend and getting later in the day.. that means it's not frowned apon to start drinking :P23:35
notmynameec is there a list of stuff for probe tests?23:43
notmynameie a list of things in ec that need probe tests?23:43
notmynames/ec/clayg23:43
notmynamewait wait. let me start over23:44
notmynameclayg: is there a list of stuff in ec that still needs probetests?23:44
claygpshshshhs not23:53
claygthe cally me ec23:54
claygbah fixing tests is *so* borning23:56
openstackgerritJohn Dickinson proposed openstack/swift: Guard against invalid Policy  https://review.openstack.org/16854823:57
mattoliverauoff to a meeting, bbs23:57
notmyname^^ fixed the docstring nit and approved23:59
claygyeah looks good!23:59

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