Friday, 2015-05-01

*** zhill has quit IRC00:07
*** breitz has quit IRC00:09
*** breitz has joined #openstack-swift00:09
mattoliverauho: morning00:12
*** dmorita has joined #openstack-swift00:23
mattoliveraudmorita: morning to you too :)00:29
*** annegentle has joined #openstack-swift00:37
homattoliverau: morning! thanks!00:40
dmoritamattoliverau: morning :)00:43
*** annegentle has quit IRC00:43
*** annegentle has joined #openstack-swift00:54
*** jrichli has joined #openstack-swift01:26
*** annegentle has quit IRC01:26
*** annegentle has joined #openstack-swift02:13
*** gyee has quit IRC02:15
hoI checked the summit schedule and I have a conflict.  Pete's presenation will be held on Wed 11:00-11:40 and we have a working session at same time.02:27
*** annegentle has quit IRC02:27
hohttp://paste.openstack.org/show/214093/02:29
*** annegentle has joined #openstack-swift02:35
*** wbhuber has joined #openstack-swift02:53
*** wbhuber has quit IRC03:16
*** annegent_ has joined #openstack-swift03:17
*** annegentle has quit IRC03:21
*** fifieldt has joined #openstack-swift03:25
*** panbalag has quit IRC03:29
openstackgerritJanie Richling proposed openstack/swift: WIP - working on the encryption feature.  https://review.openstack.org/15790703:31
*** tsg_ has quit IRC03:38
*** fifieldt has quit IRC03:59
*** esker has joined #openstack-swift04:02
*** annegent_ has quit IRC04:18
*** jrichli has quit IRC04:21
openstackgerritMinwoo Bae proposed openstack/swift: The hash_cleanup_listdir function should only be called when necessary.  https://review.openstack.org/17831704:27
*** NM has joined #openstack-swift04:43
*** NM1 has joined #openstack-swift04:56
*** NM has quit IRC04:57
*** NM1 has quit IRC04:59
*** bkopilov has quit IRC05:08
mattoliverauWoo, sharding _seems_ to be working, sharding daemon is behaving as expected and GET of a sharded and non sharded container are identical.. not to start bigger testing. Attempt 1:  find an english world list and load it up as object names.. what could possibly go wrong :P05:34
mattoliveraus/not/now05:34
*** zaitcev has quit IRC06:13
*** chlong has quit IRC06:21
*** chlong has joined #openstack-swift06:35
*** zul has joined #openstack-swift06:43
*** chlong has quit IRC07:02
*** bkopilov has joined #openstack-swift07:18
*** zul has quit IRC07:25
*** zul has joined #openstack-swift07:25
*** chlong has joined #openstack-swift07:26
*** chlong has quit IRC07:37
*** chlong has joined #openstack-swift07:49
*** chlong has quit IRC07:53
*** chlong has joined #openstack-swift07:54
*** chlong has quit IRC08:01
*** zul has quit IRC08:02
*** zul has joined #openstack-swift08:09
*** acoles_away is now known as acoles08:13
*** chlong has joined #openstack-swift08:18
*** silor has quit IRC08:28
*** silor1 has joined #openstack-swift08:28
*** zul has quit IRC08:31
*** chlong has quit IRC08:40
openstackgerritAlistair Coles proposed openstack/python-swiftclient: Fix --skip-identical to allow identical xLO to replace non-xLO  https://review.openstack.org/17917509:02
*** zul has joined #openstack-swift09:07
openstackgerritMichael Barton proposed openstack/swift: initial import of go code  https://review.openstack.org/17885109:24
*** dmorita has quit IRC09:55
*** chlong has joined #openstack-swift10:14
*** theanalyst has quit IRC10:30
*** theanalyst has joined #openstack-swift10:31
*** zul has quit IRC10:44
*** chlong has quit IRC11:01
*** chlong has joined #openstack-swift11:04
*** chlong has quit IRC11:15
*** panbalag has joined #openstack-swift11:16
*** delatte has joined #openstack-swift11:49
*** ho has quit IRC11:51
*** cdelatte has quit IRC11:52
*** delattec has quit IRC11:52
*** portante has quit IRC12:01
*** ndk has quit IRC12:01
*** cdelatte has joined #openstack-swift12:06
*** delatte has quit IRC12:07
*** proteusguy has quit IRC12:17
*** portante has joined #openstack-swift12:18
*** proteusguy has joined #openstack-swift12:29
*** zul has joined #openstack-swift12:30
*** zul has quit IRC12:35
*** mahatic has joined #openstack-swift12:46
*** esker has quit IRC12:47
*** annegentle has joined #openstack-swift12:54
*** mahatic has quit IRC13:16
openstackgerritAlistair Coles proposed openstack/swift: Make SSYNC receiver return 5xx when initial checks fail  https://review.openstack.org/17783613:30
openstackgerritAlistair Coles proposed openstack/swift: Remove _ensure_flush() from SSYNC receiver  https://review.openstack.org/17783713:30
openstackgerritAlistair Coles proposed openstack/swift: Cleanup and extend end to end ssync tests  https://review.openstack.org/17937913:30
*** mahatic has joined #openstack-swift13:32
openstackgerritAlistair Coles proposed openstack/swift: Make SSYNC receiver return a reponse when initial checks fail  https://review.openstack.org/17783613:36
*** openstackgerrit has quit IRC13:51
*** openstackgerrit has joined #openstack-swift13:51
*** doxavore has joined #openstack-swift13:59
doxavorei'm probably just not seeing this option in the manpage, but is there a "dry run" option for `swift-ring-builder rebalance` that just tells you how many partitions would be moved?14:00
*** esker has joined #openstack-swift14:04
glangeI don't think it does and I don't think that's even possible because of how it works -- it uses random numbers to guide what it does and those random actions wouldn't be the same across two runs (unless, I guess the random seed was the same)14:05
*** minwoob__ has joined #openstack-swift14:08
*** minwoob has quit IRC14:10
*** jrichli has joined #openstack-swift14:20
*** wbhuber has joined #openstack-swift14:26
*** vinsh has joined #openstack-swift14:44
*** ndk has joined #openstack-swift14:50
*** minwoob__ has quit IRC14:59
*** lpabon has joined #openstack-swift15:01
*** minwoob has joined #openstack-swift15:30
*** jd__ has quit IRC15:38
*** gyee has joined #openstack-swift15:42
*** lpabon has quit IRC15:43
*** annegentle has quit IRC16:04
openstackgerritTim Burke proposed openstack/python-swiftclient: Always decode command-line arguments as UTF-8  https://review.openstack.org/17694516:06
*** jd__ has joined #openstack-swift16:19
*** tsg_ has joined #openstack-swift16:21
*** acoles is now known as acoles_away16:33
*** HenryG is now known as floccinaucinihil16:54
*** floccinaucinihil is now known as HenryThe8th16:55
claygglange: I think there is a seed option17:01
claygdoxavore: you can always copy the builder to a temporary location and play with it there - thats what I always do when I'm not sure what's going to happen.17:02
*** annegentle has joined #openstack-swift17:04
openstackgerritMerged openstack/swift: Fix incorrect passing of file object to fsync()  https://review.openstack.org/17852817:06
notmynamegood morning17:07
*** welldannit has quit IRC17:27
*** zhill has joined #openstack-swift17:30
*** spudly has quit IRC17:32
*** tsg_ has quit IRC17:33
*** tsg_ has joined #openstack-swift17:34
*** spudly has joined #openstack-swift17:43
*** annegentle has quit IRC17:50
*** doxavore has quit IRC17:54
*** doxavore has joined #openstack-swift18:02
*** annegentle has joined #openstack-swift18:07
*** annegentle has quit IRC18:10
*** annegentle has joined #openstack-swift18:11
*** tsg_ has quit IRC18:23
*** tsg_ has joined #openstack-swift18:24
*** tgohad has joined #openstack-swift18:26
*** tsg_ has quit IRC18:29
glangeclayg: you are right, there is a seed option18:37
*** Keli has joined #openstack-swift18:39
KeliHi, I am running some ssbench tests in a cluster with 10 object servers and 3 proxy servers. The object size is 4KB and only 600 objects are there. When I run the tests for 2 minutes, first 70 seconds it works properly then suddenly it slows down. I send 50-50 read/write requests. After slowing down proxy error log contains records saying Object PUT returning 503, 1/3 required connections and ERROR with Object server 172.31.0.118:43
KeliAnybody have any suggestion for me to rectify this behaviour?18:44
glangedo you maybe have the rate limiting middleware on?18:56
glangewell, that wouldn't explain the error message though (I didn't read that far :)18:59
KeliNo, there is no middleware running as far as I know19:05
Kelibut all the servers are connected to a single switch19:05
Kelican it be a problem? Like network conguession?19:06
*** bkopilov has quit IRC19:21
*** bkopilov has joined #openstack-swift19:32
*** bkopilov has quit IRC19:39
*** annegentle has quit IRC19:43
mahatichi, just a quick question reg summit: Why doesn't the room layout for technical sessions list out Monday? There are no tech sessions on Monday?19:48
*** HenryThe8th has quit IRC19:50
*** bkopilov has joined #openstack-swift19:51
*** HenryG has joined #openstack-swift19:54
*** jrichli has quit IRC19:55
*** HenryG has quit IRC19:55
*** HenryG has joined #openstack-swift19:56
claygdfg_: so what do you think - since it's just a feature branch go ahead and merge?  today?19:57
*** bkopilov has quit IRC19:57
claygdfg_: the lack of conf.d support in go-ini threw me, i'm looking at gocfg and robif/config too20:00
claygrobif/config seems to support a "merge" method that might work for conf.d - but I havn't had a chance to implement it - but that would be a dependent or follow up patch anyway20:01
claygdfg_: but re the initial merge - do you want to try and iterate on *anything* in this patch?  like should the tld be "hummingbird" or just "go"?20:01
claygdfg_: one think I find myself thinking about is how we're going to dry stuff out down the road?  stuff like the utils package implementation of the python utils Timestamp class - seems like the common denominator between go and python is going to end up being plain C20:02
minwoobHi. Have there been any plans drawn out for implementing Local Parity Groups for EC? or would that not be necessary (e.g., library support)?20:05
*** mahatic has quit IRC20:09
*** mahatic has joined #openstack-swift20:09
claygminwoob: seems like it'd just be a plugin to liberasure20:09
dfg_clayg: um- yes as its a feature branch i just want to go ahead and just merge it20:09
claygdfg_: a'ight i'm cool with that I think20:10
*** annegentle has joined #openstack-swift20:10
dfg_i just kinda want it as is to give us a starting point- i figured it would just simplify things with multiple people working on it20:11
dfg_its just this once20:11
claygdfg_: yeah I think that makes sense, unless we realize we want to change something big like the tld and then all the changes need some frustrating rebase?20:12
dfg_clayg: as to the drying of things out down the road (whatever that means :p ) i guess we'll just have to see...20:12
dfg_oh- about the directpry name- ya i guess we should finalize that nopw20:13
dfg_anything like that i guess we should decide. but that internal changes refactors I thought it would be easier for multiple people working on it to have something to work out of20:14
claygdfg_: ok, well I think breaking things up by language name makes more sense than by "sub-project-codename"; but maybe it could be argued the other way esspecially if the hummingbard[-init] utility thing is going to be the plan going forward?20:14
claygdfg_: yeah I think we're in violent agreement there - that was nice of Dave to give it once over like that - but there's probably lots of harding stuff that would be best to take on in smaller chunks during the life of the feature-branch20:15
dfg_pretty sure the hummingbird init is going to be way forward20:16
dfg_do we really have to think about opther languages being added to swift?20:16
*** HenryG has quit IRC20:16
dfg_2's company. 3s a crowd :)20:16
dfg_ya- i hope he didn't think we were not blowing off his review. he just want to make a quick switch20:17
dfg_thats really bad typing...20:18
dfg_ya- i hope he didn't think we were blowing off his review. we just want to make a quick switch20:18
claygdfg_: i've found the number 2 is rarely a thing in software design, there tends to be 0, 1 or n20:19
dfg_is that what i've been doing wrong this whole time?20:20
claygdfg_: and I honestly thing that the co-ordinating language of go and python is c - fairly convinced we'll eventually tire of maintaining common infrastructure classes that need to be accessed from two implementations and we'll eventually just devole to the common demnominator20:20
*** HenryG has joined #openstack-swift20:21
claygdfg_: ?  :)  I don't think you're doing anything wrong!20:21
claygdfg_: not entirely - just in places where we have to write the same thing in two places20:22
claygdfg_: anyway - adding a some common c code would be discussed *way* down the road - but I do think it adds weight to the argument that organization by language makes at least as much sense as a hummingbird tld20:23
clayg^ anyone else have feelings on this?  redbo?  glange?20:23
claygwhich as you said, maybe the *one* thing we should fight for consensus on with this change - then as you said - let the rest slide into iterative work20:24
dfg_clayg: alright- i'll add a comment on the commit to not approve it just yet20:26
dfg_i just kinda wanted to get it over with :)20:26
claygdfg_: ok, well it *is* an 8K diff - as much as I can appreciate your enthusiasm - leaving it up for a week while people digest what's going on doesn't seem so bad :)20:27
dfg_its just a feature branch- i thought thats how they worked20:27
claygdfg_: yeah I'm down!20:28
dfg_we just want to keep things rolling.20:29
claygdfg_: I guess at least you and redbo think the hummingbird tld makes the most sense?  if glange or some other core agrees that's good enough for me!20:29
dfg_clayg: maybe swift/go/hummingbird ?20:29
claygdfg_: I really do think i'm in agreement with you20:29
dfg_i'll add a comment20:29
claygmaybe?  idk...20:30
claygit's probably just that i havn't been living with the hummingbird namespace for the past year so I'm not really attached to it20:30
dfg_well- adding a new directory should be taken care of now if we're going to do it20:30
*** wbhuber has quit IRC20:31
redbowe can move it to go/ that's easy20:36
redbowell medium easy20:36
claygheh!20:37
claygredbo: well - what do you think makes the most sense?  maybe it doesn't matter at all?20:37
notmynamecool. I get back from lunch, and I'm happy to see you talking about this :-)20:38
redbonaming it go probably makes more sense20:38
claygredbo: when you *do* decide to add those nim and rust implemenations as long as you can keep coming up with cute bird names then it should be fine for all us to remeber - ah yeah bluejay is erlang, and robin is ruby (obviously)20:38
notmynameinitially I was thinking like clayg said and letting it sit a few days before landing (to beat off any obvious sharp edges). but yeah, landing soon-ish makes sense to then iterate20:39
notmyname(yay nim!)20:39
claygthe thing with nim and rust while both nice - is they don't have goroutines built in - from what I've been able to digest I think go is going to be pretty sharp :)20:40
claygredbo: a'ight well maybe it does - idk, it's all so overwhelming I'm inclined to just go with whatever you guys think is best - but maybe some smarter people that have some idea about go and packaging and managing builds of projects with multiple lanages would have some reasonable insight to make21:01
claygredbo: you might hold off on moving anything until someone smarter than me has a comment about it - but you *could* maybe poke at a few people to get comments in next week?21:02
claygnotmyname: do you think we're going to end up having to wait until the wednesday meeting?  I know acoles_away and cschwede and mattoliverau and petez are all interested - but I tend to maybe agree with dfg that it's just a feature branch - stuff can change pretty cheaply21:03
claygand I 100% agree this isn't the review to iron out every docstring and error handling nit - not by a long shot - that would be terrible21:04
redboI think we know what we need to do21:07
*** esker has quit IRC21:09
*** silor1 has quit IRC21:09
openstackgerritMichael Barton proposed openstack/swift: initial import of go code  https://review.openstack.org/17885121:15
redboOkay, I think that's.. not terrible.21:17
*** Nadeem has joined #openstack-swift21:18
notmynameyeah, I was thinking of the stuff like being able to build it outside of rax and the tld and etc. the stuff that people have pointed out and redbo has been good about keeping up to date21:19
notmynameredbo: dfg_: if you're both ok with waiting until monday to land it (so that the EU-ians can look too), I think that would be great. if you feel super strongly about what's there right now, we can land it now21:20
*** Keli has quit IRC21:20
redboThat's fine.  I did do all the directory renames I think we need.21:22
notmynamethanks :-)21:22
dfg_i'm fine with waiting til monday. i guess i misunderstood what a feature branch was? i still want people to check it out and review the code after this commit gets in.21:25
notmynamedfg_: oh totally!21:25
notmynameI don't think your understanding of a feature branch is wrong at all21:25
redboI want to get some sort of CI going on the go parts.  We did have drone set up to run go unit tests and swift functional tests, but I guess now I'll have to figure out how jenkins works.21:25
notmynameredbo: I can do that next week21:26
notmynamedfg_: yeah, I don't want (at all) to wait for everything to be "perfect" before landing it. but as an initial import, I think there could be some obvious stuff that solving up front can avoid some needless big code churn (like a top level dir rename)21:27
notmynameredbo: I was planning to turn off the existing tests for that branch. we'll probably need a new job for functests since we want it to run against the go object server (the current test would only run against the python object server)21:29
notmynameredbo: what you could do is update the tox.ini file in that branch to include a definition of another test. then we'll make a job to run only that test on that branch21:29
redbookay, I'll look at that21:31
notmynamethanks21:31
*** mahatic has quit IRC21:34
*** Nadeem has quit IRC21:44
*** mahatic has joined #openstack-swift21:54
*** mahatic has quit IRC21:58
*** mahatic has joined #openstack-swift21:59
*** Nadeem has joined #openstack-swift21:59
*** doxavore has quit IRC22:06
*** bkopilov has joined #openstack-swift22:08
*** breitz has quit IRC22:11
*** breitz has joined #openstack-swift22:12
*** bkopilov has quit IRC22:13
*** bkopilov has joined #openstack-swift22:14
*** bkopilov has quit IRC22:21
*** bkopilov has joined #openstack-swift22:21
*** Nadeem has quit IRC22:21
*** bkopilov has quit IRC22:33
*** annegentle has quit IRC22:36
*** tgohad has quit IRC22:36
*** bkopilov has joined #openstack-swift22:40
*** bkopilov has quit IRC22:46
*** bkopilov has joined #openstack-swift22:47
*** bkopilov has quit IRC23:04
*** bkopilov has joined #openstack-swift23:11
*** minwoob has quit IRC23:20
*** zhill has quit IRC23:29
*** gyee has quit IRC23:35
*** pberis has joined #openstack-swift23:37
*** panbalag has quit IRC23:45

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