Tuesday, 2015-04-21

*** MVenesio has joined #openstack-swift00:02
*** annegentle has quit IRC00:04
*** thumpba_ has quit IRC00:16
*** openstackgerrit has quit IRC00:22
*** openstackgerrit has joined #openstack-swift00:22
*** kota_ has joined #openstack-swift00:24
kota_I'm now back (to office)00:25
kota_notmyname: still here?00:26
claygkota_: he just walked out I think00:26
kota_notmyname: I'm just now realizing we might need patch 175325 to land to stable/kilo00:26
patchbotkota_: https://review.openstack.org/#/c/175325/00:26
kota_clayg: morning! and thanks to work patch 17529900:27
patchbotkota_: https://review.openstack.org/#/c/175299/00:27
kota_notmyname, clayg: 175325 is for a validation of k, m (number of data fragments and parity fragments)00:27
*** zhill has quit IRC00:28
kota_notmyname, clayg: PyECLib 1.0.7 still have an decoding issue when the number of parity fragments is equals to or greater than the number of data fragments.00:28
kota_notmyname, clayg: i.e. k=10, m=1100:29
claygkota_: seems reasonable - but i'm skeptical of it as a requirement for rc2 - notmyname is trying to get all that locked down tonite00:29
kota_clayg: yeah, sounds ok. I don't have strong opinion to land it to rc2.00:29
kota_clayg: Thanks to look at :D00:31
*** openstack has joined #openstack-swift00:36
*** tsg has quit IRC00:37
*** gyee has quit IRC00:46
*** vinsh has quit IRC01:03
*** theanalyst has quit IRC01:04
*** theanalyst has joined #openstack-swift01:07
notmynamepatch 17532501:16
patchbotnotmyname: https://review.openstack.org/#/c/175325/01:16
notmynamekota_: clayg: you tell me on that one for RC201:17
*** MVenesio has quit IRC01:19
*** _joel has joined #openstack-swift01:22
*** vinsh has joined #openstack-swift01:31
*** vinsh has quit IRC01:38
*** vinsh has joined #openstack-swift01:39
mattoliveraunotmyname: it seems we are all asking this one by one... so my turn.. EC lib version numbers get confusing.. so on PyPi  pyeclib 1.0.7 isn't bundled with liberasurecode 1.0.7.. only 1.0.5. Is this going to be fixed in PyPi before the release, if it is, then I assume patch 175325 isn't needed in RC2.. if it isn't and only liberasurecode 1.0.5 is bundled and installed then it will be required (at least if we suspect that01:42
mattoliverau people will test EC with more parity fragments then data). In a beta that might just be an edge case, so _could_ be added later.01:42
patchbotmattoliverau: https://review.openstack.org/#/c/175325/01:42
*** Hongtao has joined #openstack-swift01:45
Hongtaowho?01:45
Hongtaowho have debuged the openstack swift with pycharm?01:46
HongtaoI need help ,thank you...01:46
notmynamemattoliverau: what I'm told is that they are still bundled on pypi.01:47
HongtaoIs there anybody?01:47
notmynamemattoliverau: or at least from a "packaging" standpoint (for whatever that means in pypi)01:47
notmynamemattoliverau: and if you don't have liberasurecode, pyeclib from pypi will install it01:48
notmynameHongtao: what are you trying to find?01:48
HongtaoTo develop middleware in swift.01:48
HongtaoSo I should know how to debug it.01:49
mattoliveraunotmyname: yeah, but at the moment (when I install pyeclib).. and I don't have librasurecode installed.. it installs liberausecod 1.0.5 (so assume 1.0.5 if bundled) (unless I've screwed something up). If 1.0.7 was bundled then that would be better01:49
*** vinsh has quit IRC01:49
notmynamemattoliverau: that's not what happened on my machine earlier today. I got 1.0.701:50
*** vinsh has joined #openstack-swift01:50
mattoliveraunotmyname: lol, ok, maybe I've broken something :P01:50
mattoliverauor maybe the Oz pypi mirrors are crap :P01:50
mattoliverauif so I'll go complain to richard jones (in my team) as he runs the cheeseshop (pypi).01:51
notmynameHongtao: you've already read http://docs.openstack.org/developer/swift/development_middleware.html01:51
HongtaoAlmost out of my mind....01:51
notmynameHongtao: how do you normally use PyCharm to debug python server processes?01:51
Hongtaoyeah.I have read it.01:52
* notmyname doesn't use pycharm01:52
HongtaoI can debug .py file with pycharm.But it doesn't work on swift.01:53
*** bkopilov has quit IRC01:53
mattoliverauHongtao: I use pycharm to debug swift.. so you can, but depends on how you are doing it, swift is a bunch of services, so you either need to have each service running in pycharm, or you need to have SAIO running locally and then run the service you want to debug in pycharm.01:53
notmynamemattoliverau to the rescue ;-)01:53
notmyname /dinner time01:54
HongtaoReally ?01:54
HongtaoCan you give me some advices?01:54
mattoliverauHongtao: sure01:54
*** vinsh has quit IRC01:54
mattoliveraunotmyname: pycharm, once working, is a great way to actually debug tests, as you can step through nicely ;)01:55
HongtaoI searched on the internet . and I also don't know the correct way to configure.01:56
mattoliverauHongtao: so you can't just debug a .py file.. cause to debug nicely you need to run the service in question. So I set up a run/debug configuration to run the swift/bin/<script> in question.01:57
kota_I'm back again, I had a meeting.01:58
mattoliverauHongtao: so on my development desktop, I run a SAIO (swift all in one) cluster.01:59
Hongtaowhat should i do now?01:59
mattoliverauHongtao: I then start all the SAIO service I am about to debug. And create a run configuration for it in mycharm.02:00
HongtaoI also run a SAIO. when I have changed some code in swift.I run the command "swift-init all restart"02:01
mattoliverauHongtao: say I want to run the swift-proxy-server.. try and run swift/bin/swift-proxy-server in pycharm02:01
HongtaoIs there any documents?02:01
mattoliverauHongtao: that will fail, as you need to start it with the patch to swift.conf02:01
mattoliverauHongtao: but now that you have tried to run the proxyserver when you goto edit configurations swift-proxy-server will be there, so you can add the parameter.02:02
kota_notmyname, mattoliverau: Once I was talking with clayg I agreed patch 175325 is not needed in RC2 because it is a corner case and we could maintain it at the master.02:03
patchbotkota_: https://review.openstack.org/#/c/175325/02:03
mattoliveraunext time you try and run swift-proxy-server (or debug) it sould work, just add your break points and away you go.02:03
mattoliverauHongtao: ^^02:03
Hongtaowhat parameters?02:03
mattoliverauHongtao: it tells you in the error (failed to start), you just add the path to the proxy config file.02:04
*** lcurtis has joined #openstack-swift02:05
mattoliverauwhiich should be /etc/swift/swift-proxy.conf02:06
mattoliverauif you have setup the SAIO02:06
mattoliverauHongtao: ^02:06
mattoliverauHongtao: if you just used swift-init restart all, then the proxy will fail to start cause you started a proxy via swift-init, so stop the proxy service first (if your debugging proxy)02:07
mattoliverauHongtao: swift-init proxy stop02:07
mattoliverauHongtao: then run/debug in pycharm so it can bind to the right port.02:07
Hongtaooh02:09
mattoliverauHongtao: depending on what you are debugging you don't need to start all daemons. I.E if you are just testing the object-server, then you can make a run configuration and run it, then hit it will curl or whatever.02:10
HongtaoIf  I want to debug the swift.and I should close the proxy and run swift-init proxy stop?02:10
HongtaoOh  i know .Thank you very much!02:11
mattoliverauHongtao: so long sotry short, you need to setup a run configuration on the actual scripts in bin/ but swift is a cluster with a bunch on daemons, so depending on what you are debugging then SAIO or setting up a bunch of run configurations might be in order to get a working environment02:12
mattoliverauHongtao: but running a unit test is as simple as rightclicking on the test method/class or file in pycharm and saying run.02:13
*** spudly has joined #openstack-swift02:22
*** _joel has quit IRC02:34
*** _joel has joined #openstack-swift02:37
Hongtaomattoliverau : can you write a document for us who don't know how to handle.02:39
mattoliverauHongtao: when I have some free time, maybe I'll turn it into a blog post, so everyone can read it :)02:40
*** vinsh has joined #openstack-swift02:40
HongtaoVery very  thank you! where can  I Contact your02:42
Hongtaowhere can  I contact you directly02:42
mattoliverauHongtao: you can always reach me here in channel, or email me at matt@oliver.net.au if you email me, I'll ping you back once I've had a chance to blog it.. I really need to get back into blogging anyway :P02:44
HongtaoOk  thank you02:45
openstackgerritJanie Richling proposed openstack/swift: WIP - working on the encryption feature.  https://review.openstack.org/15790702:47
*** vinsh has quit IRC03:11
*** vinsh has joined #openstack-swift03:11
*** vinsh has quit IRC03:15
*** silor has joined #openstack-swift03:16
*** bkopilov has joined #openstack-swift03:19
*** vinsh has joined #openstack-swift03:32
*** vinsh has quit IRC03:32
*** vinsh has joined #openstack-swift03:32
*** vinsh has quit IRC03:37
openstackgerritMerged openstack/swift: Bump PyECLib version from 1.0.3 to 1.0.7  https://review.openstack.org/17422503:47
kota_great, PyECLib bump landed to master.03:50
mattoliverauwoo04:00
kota_mattoliverau: I wonder if you could put workflow +1 patch 175299?04:02
patchbotkota_: https://review.openstack.org/#/c/175299/04:02
mattoliverauI can now that the recheck passed ;)04:03
mattoliveraukota_ done04:04
kota_mattoliverau: thanks! :)04:05
*** _joel has quit IRC04:09
openstackgerritMerged openstack/swift: Included step in development_saio.rst for installing dependencies in requirements.txt.  https://review.openstack.org/17559404:11
openstackgerritMerged openstack/swift: SAIO instructions: ensure ~/bin exists before copying into it  https://review.openstack.org/17561304:20
*** SkyRocknRoll has joined #openstack-swift04:46
*** SkyRocknRoll has joined #openstack-swift04:46
openstackgerritMerged openstack/swift: Use reconstruct insetad of decode/encode  https://review.openstack.org/17529904:48
*** lcurtis has quit IRC04:52
*** root has joined #openstack-swift05:03
*** root is now known as Guest8204905:04
*** tsg has joined #openstack-swift05:05
*** Guest82049 has quit IRC05:08
*** Hongtao has quit IRC05:08
*** ds_ has joined #openstack-swift05:09
*** ds_ has quit IRC05:11
*** hbhdytf has joined #openstack-swift05:11
*** rsFF has quit IRC05:12
*** rsFF has joined #openstack-swift05:12
*** zaitcev has quit IRC05:20
*** hbhdytf has quit IRC05:32
cschwedeGood Morning!05:55
kota_cschwede: morning!05:59
cschwedekota_: Hello Kota!05:59
*** proteusguy has joined #openstack-swift06:05
mattoliveraucschwede: guten morgen!06:09
cschwedemattoliverau: Hello Matthew!06:10
*** kota_ has quit IRC06:11
*** proteusguy has quit IRC06:14
*** krykowski has joined #openstack-swift06:29
*** jamielennox is now known as jamielennox|away06:34
*** pcaruana has quit IRC07:11
*** bill_az has quit IRC07:14
*** slo_ has joined #openstack-swift07:26
*** geaaru has joined #openstack-swift07:41
*** jamielennox|away is now known as jamielennox07:43
*** jistr has joined #openstack-swift07:47
*** foexle has joined #openstack-swift07:58
*** jordanP has joined #openstack-swift08:16
*** acoles_away is now known as acoles08:31
*** nottrobin has quit IRC08:57
*** nottrobin has joined #openstack-swift08:59
openstackgerritRomain LE DISEZ proposed openstack/swift: Support of the Linux socket option SO_REUSEPORT  https://review.openstack.org/13765909:04
*** krykowski has quit IRC09:09
acolesnotmyname: just catching up - did we cut RC2? re revert-y patches 175076 and 174875, like clayg said in my scrollback, i am comfortable with those issues being addressed during liberty09:18
acolesclayg: yeah, i agree there is almost certainly going to be some case (e.g. a race creating diskfiles) when we will be glad to have multi frag indexes.09:22
acolesso nothing wasted09:23
acolesclayg: i'd like to see that star trek quote in a commit message :)09:25
openstackgerritPrashanth Pai proposed openstack/swift: versioned writes middleware  https://review.openstack.org/13434710:01
*** thurloat has quit IRC10:04
*** thurloat has joined #openstack-swift10:04
*** silor has quit IRC10:07
*** krykowski has joined #openstack-swift10:37
*** jistr has quit IRC11:02
*** jistr has joined #openstack-swift11:04
*** kei_yama has quit IRC11:09
*** silor has joined #openstack-swift11:14
*** km has quit IRC11:28
*** tsg has quit IRC11:30
*** MVenesio has joined #openstack-swift11:34
*** MVenesio has quit IRC11:56
*** bkopilov has quit IRC12:12
*** aix has joined #openstack-swift12:21
*** MVenesio has joined #openstack-swift12:35
*** jistr has quit IRC12:42
*** jistr has joined #openstack-swift12:43
*** SkyRocknRoll has quit IRC12:55
*** bill_az has joined #openstack-swift12:56
*** jistr is now known as jistr|mtg13:01
*** sandywalsh has quit IRC13:11
*** sandywalsh has joined #openstack-swift13:15
*** esker has joined #openstack-swift13:26
openstackgerritAlistair Coles proposed openstack/swift: Fix tempauth acl checks when simplejson has no speedups  https://review.openstack.org/15953013:37
*** EmilienM has quit IRC13:40
*** EmilienM has joined #openstack-swift13:41
openstackgerritAlistair Coles proposed openstack/swift: Merge branch 'master' into feature/crypto  https://review.openstack.org/17586613:44
*** imkarrer_ has joined #openstack-swift13:51
*** tsg has joined #openstack-swift13:56
*** Fin1te has joined #openstack-swift14:01
*** petertr7 has joined #openstack-swift14:05
*** jrichli has joined #openstack-swift14:06
*** lcurtis has joined #openstack-swift14:10
*** annegentle has joined #openstack-swift14:10
*** bkopilov has joined #openstack-swift14:12
*** jistr|mtg is now known as jistr14:26
*** vinsh has joined #openstack-swift14:26
*** fanyaohong has joined #openstack-swift14:28
*** annegentle has quit IRC14:28
*** annegentle has joined #openstack-swift14:28
*** vinsh_ has joined #openstack-swift14:29
*** vinsh has quit IRC14:31
*** wbhuber has joined #openstack-swift14:34
*** _joel has joined #openstack-swift14:39
*** _joel has left #openstack-swift14:41
*** Fin1te has quit IRC14:49
*** tsg has quit IRC14:52
*** sileht has quit IRC14:57
*** breitz has joined #openstack-swift14:58
*** vinsh_ is now known as Vinsh15:02
*** Fin1te has joined #openstack-swift15:10
*** krykowski has quit IRC15:14
*** BaconIsKing has joined #openstack-swift15:16
*** jigsaw has joined #openstack-swift15:16
jrichliHi everyone.  Has there ever been talk about adding a "slowdown" tunable for the replicator process much15:19
jrichlilike the updater has a slowdown feature?15:19
*** breitz has quit IRC15:20
*** breitz has joined #openstack-swift15:20
openstackgerritMerged openstack/swift: Merge branch 'master' into feature/crypto  https://review.openstack.org/17586615:22
*** MVenesio has quit IRC15:23
*** MVenesio has joined #openstack-swift15:24
*** thumpba has joined #openstack-swift15:25
*** david-lyle has quit IRC15:36
*** thumpba_ has joined #openstack-swift15:38
*** thumpba has quit IRC15:41
*** Fin1te has quit IRC15:48
*** gyee has joined #openstack-swift15:50
*** tsg has joined #openstack-swift15:54
*** Vinsh_ has joined #openstack-swift15:56
*** sileht has joined #openstack-swift15:57
*** BaconIsKing has quit IRC15:58
*** Vinsh has quit IRC15:59
*** david-lyle has joined #openstack-swift16:02
notmynamegood morning16:06
notmyname9:06am and I've already had 2 meetings16:06
lcurtisHey notmyname16:07
notmynametoday I'll be working on getitng RC2 squared away. the goal is to have a commit SHA on stable/kilo by EoD so ttx can tag RC216:07
*** lpabon has joined #openstack-swift16:17
hurricanerixmorning16:17
lcurtisall...would i be better off using ext4 over xfs for small objects (4k and under)?16:18
*** lpabon has quit IRC16:21
*** jistr has quit IRC16:21
notmynamelcurtis: normally the reason xfs is chosen is because it performs better when there are a lot of inodes on the device (eg as disks get full).16:22
notmynamehurricanerix: hello16:22
lcurtisThanks notmyname16:24
*** jordanP has quit IRC16:29
*** fanyaohong has quit IRC16:39
claygacoles: so you have the plan to combine the handoff revert fixes with the 409 ssync fixes and make everything amazing and rainbows!?16:41
claygujjain: morning!16:43
acolesclayg: right now i am drowning in merge conflicts on my fast-post reviews so a rainbow would be good :P16:44
acolesclayg: are you referring to my option 3b comment?16:44
claygFAST-POST!  liberty is going to be the best development cycle yet.16:44
claygacoles: yeah16:44
acolesliberty!! i'm waiting for 'p'=='post' cycle!16:45
claygacoles: i had some notion that the solution wasn't like neither a nor b - but rather some of a AND b16:45
claygacoles: oh no, l m n o p - it's no far off i guess :P16:45
notmynamejrichli: sort of. and it's sort of there today with the run_pause/rsync options/concurrency options16:46
claygjrichli: I think the auditor has some crazy rate limit turning - what does the updater do now?16:46
notmynamejrichli: but, no there's not anything like "only process this many parts per unit time"16:47
acolesm for 'maybe', n for 'nearly', 'o' for 'oh-so-close'...16:47
*** annegentle has quit IRC16:47
acolesclayg: just going back to read 3a and 3b again...16:47
claygso slowdown is like a small sleep on each top level dir in the async folder16:48
acolesclayg: so my 3b was meant as a superset of 316:49
acolesotherwise it would be 4  :P16:49
acolesclayg: so fix the KeyError, take the 409 on the chin, make ssync tell us what *did* get sync'd, clean those up, no duplicates16:50
claygacoles: nah it's take the one good idea I had (don't keyerror) and add in the important don't blow up ssync entirely on 409 from your fix16:51
claygacoles: I think maybe (False, {hash=>ts_in_sync}) will capture most of want we want right?16:51
claygacoles: you think there's any hope the reciever might be able to eat the 409 and continue syncing the rest of the objects?  Is there anything in the protocol for the reciever to return individual errors on files?16:53
*** Vinsh_ has quit IRC16:54
*** Vinsh has joined #openstack-swift16:54
acolesclayg: I think we have to be careful about eating the 409 and not letting the sender know that we did, and no nothing in protocol now to return individual status :/16:55
acolesclayg: sender must NOT delete frags that got 409 on receiver, so ideally receiver would send back individual status, or list of all successful sync'd hashes16:56
acolesbut thats a protocol change16:56
acolesclayg: and i didn't build allowance for *that* protocol change into EC16:57
*** portante_ is now known as portante16:59
claygacoles: ic, yeah that's a rub :\16:59
acolesclayg: we get part way with  (False, {hash=>ts_in_sync}) where the dict at least has all objs the rx did not want to sync17:00
acolesclayg: that allows cleanup of dups on seconf pass17:00
acolessecond17:00
claygacoles: so there is a space in the reciever's response to include *an* error - it could probably be updated with something like the missing check protocol to include per hash errors17:03
claygbut I don't quite follow - how a 409 becoming a failure would let us clean up stuff on the second pass?17:05
clayglike you could maybe cleanup everythign that synced *before* the 409, but if the 409 blows up everything how would we skip it and make progress?17:06
claygyeah it's definately not in-sync, but their may be other stuff in the part that could sync17:07
*** geaaru has quit IRC17:08
*** david-lyle has quit IRC17:08
acolesclayg: its more complicated that i fisrst thought, ...the rx 409 don't cause the updates to stop until a threshold failure count is reached,17:08
claygi might try to have reciever send back a <hash status> line for errors and let sender pop from the insync map17:08
acolesclayg: so some 409s will be tolerated, updates continue, but at end of updates rx will raise an error to sender so we always get False, {} back to reconstructor17:09
acoles^^ on master that is17:09
acoleslots of 409s will cause updates to blow up early if i read it correctly17:10
claygacoles: it's weird - saw that code - but i guess it's not really important unless you have lots of objects - the reciever will say "i blew up" on self.failures17:10
acolesso the thing about 2nd pass and dups is...17:10
claygacoles: yeah - violently agree17:10
acolesany 409 will cause False,{} return from sender :(17:10
acolesso we never get to cleanup stuff that is in sync before updates even started17:11
acolesbut it would be easy to return False, {stuff rx never even wanted}17:11
claygacoles: oh interesting - so even tho revert doesn't do a pre-flight suffix check - it *does* do the missing check before building requests17:12
acolesclayg: yes (remember me whining about that being wasted work when suffixes are equal :P)17:13
claygacoles: which part - the missing check is wasted effort - oh or the whole revert?17:14
acolesso at end of missing check we can populate can-delete-objs or whatever with objs in sync17:14
acolesthe missing check17:14
*** EP77 has joined #openstack-swift17:15
claygacoles: i'm not sure which part is wasted17:16
claygon a part forklift like a rebalance it's pretty stupid17:16
acolesclayg: ok that comment was a red herring sorry! IF we had rechecked suffixes for reverts, and if they had matched, then calling ssync_sender would cause a wasted missing_check that would result in nothing being missing - but we didn't do that, i was just wandering off topic.17:17
claygheheheh17:17
acolesso back on track...17:18
claygyeah17:18
claygacoles: so i'm going to play around with having ssync reciever return per hash errors - seems simple enough17:18
claygor useful17:18
claygor something like that17:18
claygacoles: my only reservation is that ssync missing_check ... why are we even trying to send a object that's just going to 409!?17:20
acolesclayg: +1 like there is a 'phase of handshakes' there just begging for it : rx sends UPDATES START, UPDATES END but we could insert a list of hash->status in between those, or even just successful hashes, just like the MISSING CHECK responses17:20
claygwant = df.timestamp < timestamp17:20
acolesgood point!17:21
acolesclayg: because in missing_check rx tries to open the diskfile with the frag-index-to-revert, which does not exist, but in updates it gets a 409 because another frag exists17:23
acolesclayg: but rx could just try to open *any* frag...17:23
acolesduring missing_check, then we'd avoid the 40917:24
clayginteresting - but we'd probably also delete it - since it never *wanted* it - it'd be considered in-sync :\17:24
acolesoh yeah, oops :P17:25
acolesi have another idea brewing....17:25
claygacoles: but you're right about hte frag index thing17:25
acolesclayg: so for fast-post, i change missing check responses to include hash *and timestamps* of meta, content-type, so sender can figure out if it needs to do a PUT or a POST or both...17:27
claygacoles: yeah I love that17:27
acolesclayg: so we add to the missing-check response a 'want-but-can't-accept' flag17:28
acolesclayg: or somehow represent that semantic17:28
claygok17:28
claygmy mind is a little blown17:28
acolesclayg: then sender knows (a) its not in sync but (b) don't bother sending17:28
claygyes, i have to admit that does seem to be *exactly* what we need to solve the issue at hand17:29
acolesclayg: so i'm making this up as i go now...17:29
claygacoles: you should call it quits already like an hour ago!17:29
acolesclayg: but maybe rx includes a list of frag indexes that it has along with timestamps it has17:29
claygacoles: I'm glad I caught you tho17:29
acolesoh, i forgot, i have really exciting merge conflicts to resolve... :P17:30
claygacoles: that *would* be very ec specific17:30
claygacoles: it's a really situation to say - yeah I'd love to have that, but I can't hold it right now - can you just hang onto it for me17:30
acolesclayg: ummm, so it would,. we could call them node indexes or wotnot :P17:30
claygi need to stew - you've given me a lot to chew on - thank you17:31
acolesclayg: ok, so maybe not return frag indexes, but there would be a way to say 'not in sync but don't send now'17:32
acolesclayg: sure, i'll stew some more too...17:32
*** annegentle has joined #openstack-swift17:32
claygI'm heading in17:33
claygacoles: thanks again - talk to you later17:33
acolesclayg; k i may be gone but around tomorrow17:34
claygacoles: yeah of course - give me time to stew ;)17:34
*** aix has quit IRC17:37
*** annegentle has quit IRC17:38
*** annegentle has joined #openstack-swift17:39
*** thumpba_ has quit IRC17:48
*** EP77 has left #openstack-swift17:50
*** EP77 has quit IRC17:50
*** annegentle has quit IRC17:53
*** jigsaw_ has joined #openstack-swift17:54
jrichlinotmyname: clayg: thanks for the info.  When you talked of rsync options, do you mean the rsync bwlimit?  Also, is there a reason that slowdown makes sense for updater, but not replicator?18:03
*** annegentle has joined #openstack-swift18:05
jrichlioh, well I guess the replicator has a sleep between run loops, while the updater has a sleep between processing objects18:08
*** annegentle has quit IRC18:10
notmynamejrichli: yeah, the rsync options in the object replicator config, but also configuring rsync itself (like the max_connections settion)18:14
notmyname*setting18:14
jrichliok18:15
notmynamebe right back18:16
*** patchbot has quit IRC18:16
*** notmyname has quit IRC18:16
*** notmyname has joined #openstack-swift18:17
*** ChanServ sets mode: +v notmyname18:17
notmynamedid you miss me?18:17
*** patchbot has joined #openstack-swift18:18
*** bsdkurt has quit IRC18:27
notmynamerd18:30
notmynameI'm running a last sanity check on the 4 patches for RC218:31
notmynamethen I'll push those and land them on stable/kilo18:31
notmynameanything else need to be in RC2? this is the chance to say something18:32
claygback18:36
notmynameclayg: I'm finishing up rc2 stuff now18:36
claygnotmyname: well what do we have?18:36
notmynamethe 4 listed on https://wiki.openstack.org/wiki/Swift/PriorityReviews18:36
claygetag pop fix, pyeclib 1.0.7, reconstruct-hack-removal18:37
notmynameand a translation one18:37
claygoh wow - super important18:37
notmyname:-)18:37
*** openstackgerrit has quit IRC18:37
*** Fin1te has joined #openstack-swift18:37
*** openstackgerrit has joined #openstack-swift18:37
*** acoles is now known as acoles_away18:38
notmynameI post-facto created the LP bugs for them for the rc2. and updated commit messages. as soon as tests finish running locally, I'll push them to gerrit18:38
notmynameand I'm thinking I'll jsut go ahead and land them18:38
notmynameclayg: any objections?18:38
*** david-lyle has joined #openstack-swift18:39
claygnotmyname: no i don't think so18:39
notmynameok18:42
*** jigsaw has quit IRC18:42
*** jigsaw_ has quit IRC18:43
*** david-ly_ has joined #openstack-swift18:46
*** david-lyle has quit IRC18:46
*** imkarrer__ has joined #openstack-swift18:50
*** imkarrer_ has quit IRC18:53
notmynameok, patches pushed to gerrit and into the gate queue18:53
notmynamehttps://review.openstack.org/#/q/status:open+project:openstack/swift+branch:stable/kilo+topic:rc2patches,n,z18:53
*** silor1 has joined #openstack-swift19:03
*** silor has quit IRC19:05
*** slo___ has joined #openstack-swift19:12
*** david-ly_ has quit IRC19:18
*** BaconIsKing has joined #openstack-swift19:18
*** gyee has quit IRC19:23
*** Fin1te has quit IRC19:37
*** MVenesio has quit IRC20:04
*** MVenesio has joined #openstack-swift20:04
*** imkarrer__ has quit IRC20:10
*** silor1 has quit IRC20:10
*** imkarrer has joined #openstack-swift20:10
*** BaconIsKing has quit IRC20:14
*** david-lyle has joined #openstack-swift20:21
*** zaitcev has joined #openstack-swift20:31
*** ChanServ sets mode: +v zaitcev20:31
*** Gu_______ has joined #openstack-swift20:32
*** imkarrer has quit IRC20:39
*** imkarrer has joined #openstack-swift20:40
*** Fin1te has joined #openstack-swift20:43
*** openstackgerrit has quit IRC20:52
*** openstackgerrit has joined #openstack-swift20:52
*** foexle has quit IRC20:52
*** imkarrer__ has joined #openstack-swift20:52
*** Fin1te has quit IRC20:55
*** imkarrer has quit IRC20:56
*** haomaiwang has quit IRC21:07
*** haomaiwang has joined #openstack-swift21:07
claygnotmyname: there's one call in the reconstrctor that uses node['ip instead of node['replication_ip21:14
notmynameclayg: gate seems wedged with some other issue, so we could land it on master and then in rc2 if we do it quickly21:15
claygnotmyname: thanks gate wedge!21:20
*** haomaiwang has quit IRC21:35
*** haomaiwang has joined #openstack-swift21:36
openstackgerritClay Gerrard proposed openstack/swift: Use node's replication_ip to GET fragments during rebuild  https://review.openstack.org/17609021:37
notmynameclayg: thanks for doing the LP bug!!21:38
claygnotmyname: i thought you'd like that ;)21:39
*** haomaiwang has quit IRC21:40
*** haomaiwang has joined #openstack-swift21:42
notmynameah, this is the issue on the gate https://bugs.launchpad.net/openstack-gate/+bug/144684721:45
openstackLaunchpad bug 1446847 in OpenStack-Gate "stable/juno gate is busted on stevedore/cliff releases on 4/21" [Undecided,New]21:45
notmynamefishbowl sessions will have something like 150-200+ seats. working sessions have around 3021:56
mattoliverauMorning21:56
notmynamemattoliverau: hi21:57
notmynamemattoliverau: can you check out https://review.openstack.org/#/c/176090/ please?21:58
mattoliverauYup, sure thing21:58
torgomaticso we have a session called something like "Erasure Coded Cryptography in Your Global Swift Cluster" in a fishbowl, and while all the code tourists are there, we go have a couple working sessions and get things done21:59
torgomaticnotmyname: that's how it works, right?21:59
notmynametorgomatic: actually yes. and every working session will have the same title on the schedule21:59
torgomaticnotmyname: nice!21:59
notmynameand we'll have an etherpad or something to map sessions to what we're covering21:59
*** slo___ has quit IRC22:00
notmyname(but you forgot "docker" in the fishbowl session)22:00
* torgomatic wishes he could forget Docker22:00
*** gyee has joined #openstack-swift22:01
zaitcevAttributeError: 'Input' object has no attribute 'send_hundred_continue_response'22:05
zaitcevOh, brother22:05
zaitcevThe pace of progress is taking its toll on my body.22:05
notmynamezaitcev: old eventlet?22:06
zaitcevnotmyname: you bet22:07
*** Vinsh has quit IRC22:08
*** imkarrer__ has quit IRC22:11
jrichli150-200+ seats => (*_*)22:15
notmynamejrichli: no worries22:16
jrichlieasy for you to say.  You are good at public speaking22:16
jrichlibut I guess I will live through it :-)22:17
zaitcevA number of community colleges in the U.S. have open enrollment programs where you can take public speaking courses. Just FYI. I'm saying it as an immigrant who's not a native speaker.22:18
jrichlizaitcev: thanks.  I have had practice, and I guess I do ok.  I will just always get nervous, that's all!22:21
notmynamethe community cluster failures are spurious. the networking is being redone on them, and they weren't silenced before that started. I've turned the jobs off, so shouldn't be getting errors any more22:27
notmynamemattoliverau: go ahead and +A. don't wait for jenkins. that way we know what needs to happen as soon as it's available22:28
claygnotmyname: so the gate has been let go?  or you just fixed the glitch?22:28
mattoliverauHai22:28
notmyname(and jenkins is a computer. no need to be nice and give "him" a break)22:28
*** jrichli has quit IRC22:29
notmynameclayg: the community qa cluster? I "fixed" it by disabling all 3 jobs22:29
zaitcevheh22:29
claygso it'll just work itself out naturally - We always like to avoid confrontation, whenever possible - Problem is solved from your end.22:29
notmynamewhenever mlanner gets done redoing the networking, I'll turn it on. or he will. or someone will. point is, it'll get turned back on22:30
notmynameok, I'll cherry-pick that patch to rc222:31
*** annegentle has joined #openstack-swift22:32
openstackgerritJohn Dickinson proposed openstack/swift: Use node's replication_ip to GET fragments during rebuild  https://review.openstack.org/17611022:33
notmyname(also, yay. the change to report on all of our branches now works)22:34
claygheh22:34
*** annegentle has quit IRC22:38
*** lcurtis has quit IRC22:38
zaitcevI always save these e-mail reminders to review something interesting "when I get back from a store" and then I always find them merged already.22:40
mlannersorry about that. i'm hurrying as fast as i can, trying to break as little as possible.22:40
notmynamemlanner: no worries at all :-)22:41
notmynamedon't rush it. it's fine22:41
notmynamezaitcev: the obvious solution is that you no longer go to the store22:41
*** wbhuber has quit IRC22:43
*** km has joined #openstack-swift22:44
*** haomaiwang has quit IRC22:46
*** annegentle has joined #openstack-swift22:46
*** haomaiwang has joined #openstack-swift22:47
*** haomaiwang has quit IRC22:49
*** haomaiwang has joined #openstack-swift22:50
*** petertr7 has quit IRC22:51
*** annegentle has quit IRC23:00
*** kota_ has joined #openstack-swift23:08
kota_good morning23:08
notmynamehello23:09
notmynametsg: what's the ec helper tool? where can I find that?23:09
*** Gu_______ has quit IRC23:13
claygthe ec helper tool is a lie!23:14
notmynamewell ok then!23:14
notmynamethat answers that23:15
tsgnotmyname: pyeclib_conf_tool.py is part of pyeclib23:15
claygtsg: no it's not - i have pyeclib installed and I have no such script23:17
notmynameditto23:17
notmynamebut it's in the tools dir of the source23:17
*** zhill has joined #openstack-swift23:18
tsgnotmyname: that's correct - included with source only at the moment23:18
notmynametsg: I have no idea how to use this23:18
notmynametsg: I've got a 5 node cluster. each with 12 drives. (60 total). what ec numbers do I use?23:19
mattoliveraukota_: morning23:19
kota_mattoiverau: morning23:20
tsgnotmyname: the only "guidance" it can provide today is around the available EC backends and how those backends would perform (bytes/second)23:20
tsgnotmyname: keving was in the middle of adding support for providing better guidance around data durability - I will check with him on the status23:23
notmynametsg: what does "perf rank #10" mean? it's the 10th fastest? it's the faster? does it have anything to do with speed?23:26
kota_tsg: Once, I wrote a script to calcurate durability, here https://github.com/bloodeagle40234/DurabilitySimulator/blob/master/simulator.py23:28
tsgnotmyname: rank0 is the fastest - this is compute performance only though23:29
kota_tsg: but it is needed to update the description for users, yet :P23:29
tsgnotmyname, kota_: let me see keving can shed some light23:29
notmynametsg: mostly I'm starting with my question (5 servers, 12 drives, etc) and want to know how to configure it. eg I'd default to 10+4 but *only* because I've been using that in my head as a placeholder for the last 2 years23:30
notmynameI really don't know what's best or how to tell people what to test or what to test myself23:30
*** kei_yama has joined #openstack-swift23:32
kota_tsg: ok, FYI, cshwede also have a simulator script with GUI for replica model build by javascrit.23:33
tsgnotmyname: valid point - let me see if I can come up with a draft for a guideline that we can turn into a doc section23:33
notmynametsg: cool, that would be great!23:33
tsgkota_: that's cool .. link?23:34
*** bill_az has quit IRC23:34
kota_tsg: wait...I'm now looking for it in my watching list...23:34
kota_tsg: found, here https://github.com/enovance/swift-durability-calculator23:35
tsgkota_: ok .. let's see if we can extend this23:36
*** bill_az has joined #openstack-swift23:38
kota_tsg: yup, I guess cshwede's one seems good to understand intiatively. For now, I'm planning to extend it with my calculartion model (but not started yet)23:38
*** esker has quit IRC23:38
*** Vinsh has joined #openstack-swift23:48
*** Vinsh has quit IRC23:56

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