Tuesday, 2014-04-29

notmynamezaitcev: go go gadget notmyname http://d.not.mn/EC_swift_proxy_design.pdf00:00
zaitcevnotmyname: thanks00:00
zaitcevand right in the root? Nice.00:00
notmynamezaitcev: d.not.mn is my dropbox container in cloud files. http://programmerthoughts.com/programming/simple-script-to-upload-content-to-cloud-files/00:01
notmynamejsut a cname to the CDN url00:01
zaitcevIt's like the whole new world. You don't program Swift on your iPad by any chance00:02
notmynameuse some ssh ios app to do remote coding on my server somewhere. now that would be a neat trick00:03
zaitcevI thought about it, but I cannot bring myself to trust iPad with any passphrases... I imagine Apple can keylog anything there.00:04
zaitcev"Why trello? Mostly because Launchpad isn't sufficient to have discussions around the design, and gerrit only supports discussion around a particular piece of code." -- Ironically written in an e-mail message to a mailing list.00:06
*** occupant has quit IRC00:07
*** occupant has joined #openstack-swift00:08
*** tzumainn has left #openstack-swift00:12
zaitcevI ordered my hotel for Hackathon today. Decided to stay in a motel by freeway. $90/night. On-site hotels are $150-200.00:13
notmynameoh yeah. I need to book hotel/travel too00:14
zaitcevnotmyname: I see "Given 10+4 RS coding parameters, EC Quorum is 11 volumes". How did you arrive to the value of 11?00:43
zaitcevRS(10,4) can tolerate 2 failures at the most, isn't that right?00:44
zaitcevOr not?00:44
*** shri1 has quit IRC00:44
*** Honghui_ has joined #openstack-swift00:52
*** Honghui_ has quit IRC01:03
*** gyee has quit IRC01:13
*** Honghui has joined #openstack-swift01:22
*** gyee has joined #openstack-swift01:42
*** bach has joined #openstack-swift01:42
*** zhiyan_ is now known as zhiyan01:52
*** Honghui has quit IRC01:55
*** bach has quit IRC01:57
*** Honghui has joined #openstack-swift02:05
*** shakamunyi has quit IRC02:11
*** Honghui has quit IRC02:45
*** bach has joined #openstack-swift02:45
*** Honghui has joined #openstack-swift02:45
*** praveenkumar has joined #openstack-swift02:51
*** Honghui__ has joined #openstack-swift02:58
*** Honghui has quit IRC03:00
*** haoma____ has quit IRC03:07
*** bach has quit IRC03:09
*** haomaiwang has joined #openstack-swift03:09
*** bach has joined #openstack-swift03:15
*** bach has quit IRC03:17
*** Honghui__ has quit IRC03:48
*** Honghui has joined #openstack-swift03:49
notmynamezaitcev: AFAIK RS(10,4) can tolerate 4 failures. but I'm no EC expert. the idea of "one plus minimum" is what I meant there. eg with 3 replicas, quorum is 2.03:56
*** gyee has quit IRC04:04
*** chandan_kumar has joined #openstack-swift04:05
*** haomaiwang has quit IRC04:08
*** haomaiwang has joined #openstack-swift04:10
*** Honghui has quit IRC04:12
*** Honghui has joined #openstack-swift04:15
*** ppai has joined #openstack-swift04:17
*** haomai___ has joined #openstack-swift04:22
*** haomaiwang has quit IRC04:25
*** Honghui has quit IRC04:29
*** Honghui has joined #openstack-swift04:52
*** ppai has quit IRC05:03
zaitcevnotmyname: thanks, I see. I thought that for a regular EC tolerance is half, e.g. 2t = n - k.05:07
notmynamezaitcev: whatever the number is, the proposal in that original pdf is basically just saying "one more than that" so that there must be 2 drive failures (ie >1) before data is lost05:09
zaitcevnotmyname: makes sense05:09
*** ppai has joined #openstack-swift05:16
*** cheri has joined #openstack-swift05:20
*** zaitcev has quit IRC05:24
*** ppai has quit IRC05:24
*** nshaikh has joined #openstack-swift05:26
*** ppai has joined #openstack-swift05:36
*** chandan_kumar has quit IRC06:01
*** gvernik has joined #openstack-swift06:03
*** ppai has quit IRC06:14
*** madhuri has joined #openstack-swift06:15
*** chandan_kumar has joined #openstack-swift06:16
*** Honghui has quit IRC06:21
*** chandan_kumar has quit IRC06:22
*** cheri has quit IRC06:26
*** bvandenh has joined #openstack-swift06:31
*** bvandenh has quit IRC06:31
madhuriHow all services are being tracked in Swift? What happens when a service lets say an object server goes down?06:34
*** psharma has joined #openstack-swift06:35
*** haomai___ has quit IRC06:36
*** haomaiwang has joined #openstack-swift06:36
claygthat kind of monitoring is implemented outside of swift, either with some custom tooling, something like zenos, or a proprietary product.06:36
madhuriYeah I have looked for zenos and nagios too06:38
madhuriThat provides support for swift06:38
madhuriThe healthcheck is also kind of monitoring tool for proxy server only??06:39
claygit's really there for load balancers06:39
*** ppai has joined #openstack-swift06:39
*** chandan_kumar has joined #openstack-swift06:40
madhuriSo health check is just for load balancers. Right?06:40
claygwell... it's there... it does what it does... you can use it however you like?  But the orignal usecase I'm pretty sure had loadbalancers in mind - that's how we use it as a tool to control rolling swift upgrades.06:41
*** Manish_ has joined #openstack-swift06:41
madhuriOk.06:42
madhuriCan't it be used at storage service level?06:42
madhurimeans account, container, object server??06:43
claygwell the proxy implements it's own notion of error limiting, but as a piece of middleware I would imagine you could stick in the pipeline if you were keen on that?06:43
madhurierror limiting is also kinda monitoring at proxy server level?06:47
claygwell you're not really alerted to it - which would be a defining factor of something I called "monitoring" - it's just a built in property of the proxy that it will work around failures associated with a individual storage node that is not responding in a timely fashion06:48
madhuriThanks clayg06:52
*** Honghui has joined #openstack-swift06:53
madhuriIs there any documentation available for nagios or zenos integration with swift?06:54
*** haomaiw__ has joined #openstack-swift07:02
hugokuoDid anyone ever produce a document about the compatibility between S3 and Swift(swift3) ?  Am working on it hope that's not a re-do works in the community07:04
*** haomaiwang has quit IRC07:05
clayghugokuo: you've seen https://github.com/fujita/swift3/issues/307:07
hugokuoclayg: That's awesome !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!07:11
hugokuoclayg: You save my time .. appreciate07:12
hugokuothanks fifieldt...07:12
*** mmcardle has joined #openstack-swift07:15
openstackgerritClay Gerrard proposed a change to openstack/swift: Keep status_changed_at up-to-date with status changes.  https://review.openstack.org/8671407:27
openstackgerritClay Gerrard proposed a change to openstack/swift: Extend direct_client  https://review.openstack.org/8814407:27
openstackgerritClay Gerrard proposed a change to openstack/swift: Add write_fake_ring helper to test.unit  https://review.openstack.org/8815107:27
openstackgerritClay Gerrard proposed a change to openstack/swift: Add container-reconciler daemon  https://review.openstack.org/8590807:27
openstackgerritClay Gerrard proposed a change to openstack/swift: Convert POLICIES to list for random.choice  https://review.openstack.org/8815007:27
openstackgerritClay Gerrard proposed a change to openstack/swift: Extend interface on InternalClient  https://review.openstack.org/8815207:27
openstackgerritClay Gerrard proposed a change to openstack/swift: Merge container storage_policy_index values.  https://review.openstack.org/8672007:27
openstackgerritClay Gerrard proposed a change to openstack/swift: Expose container info on deleted containers.  https://review.openstack.org/8670807:27
openstackgerritClay Gerrard proposed a change to openstack/swift: Fix X-Backend-Storage-Policy-Index requests  https://review.openstack.org/9092907:27
openstackgerritClay Gerrard proposed a change to openstack/swift: Fix recursive Policy patching  https://review.openstack.org/9093007:27
openstackgerritClay Gerrard proposed a change to openstack/swift: Cleanup container update headers in obj server tests  https://review.openstack.org/9093107:27
openstackgerritClay Gerrard proposed a change to openstack/swift: Update FakeLogger with better log level handling  https://review.openstack.org/9093207:27
openstackgerritClay Gerrard proposed a change to openstack/swift: Make FakeRing a use more real code  https://review.openstack.org/9093307:28
openstackgerritClay Gerrard proposed a change to openstack/swift: Add reconciler probetest outline  https://review.openstack.org/9093407:28
openstackgerritClay Gerrard proposed a change to openstack/swift: Add Storage Policies to container.backend  https://review.openstack.org/9093507:28
openstackgerritClay Gerrard proposed a change to openstack/swift: Add Storage Policy to container put/delete object  https://review.openstack.org/9093607:28
openstackgerritClay Gerrard proposed a change to openstack/swift: Enqueue misplaced objects during container replication  https://review.openstack.org/9093707:28
openstackgerritClay Gerrard proposed a change to openstack/swift: Add LRUCache to common.utils  https://review.openstack.org/9093807:28
*** chalcedony has quit IRC07:28
omameclayg: go to sleep ;)07:28
*** cheri has joined #openstack-swift07:32
fifieldtlol hugokuo07:43
fifieldtsadly I have not had time to work on this recently07:43
* hugokuo am going to conduct the tests on 1.13 here07:44
fifieldtthat would be very interesting :)07:51
*** foexle has joined #openstack-swift07:53
*** Honghui has quit IRC08:05
*** joeljwright has joined #openstack-swift08:12
*** Honghui has joined #openstack-swift08:14
*** psharma has quit IRC08:17
*** jamie_h has joined #openstack-swift08:23
*** psharma has joined #openstack-swift08:23
*** chalcedony has joined #openstack-swift08:28
*** mmcardle has quit IRC08:30
openstackgerritJoel Wright proposed a change to openstack/python-swiftclient: Add importable SwiftService incorporating shell.py logic  https://review.openstack.org/8545309:03
*** chandan_kumar has quit IRC09:14
*** chandan_kumar has joined #openstack-swift09:15
*** mmcardle has joined #openstack-swift09:34
*** haomaiw__ has quit IRC09:34
*** haomaiwa_ has joined #openstack-swift09:35
*** haomaiwa_ has quit IRC09:55
*** haomaiwang has joined #openstack-swift09:56
*** [1]gvernik has joined #openstack-swift10:31
*** gvernik has quit IRC10:33
*** [1]gvernik is now known as gvernik10:33
*** Honghui has quit IRC10:47
*** [1]gvernik has joined #openstack-swift11:01
*** gvernik has quit IRC11:03
*** [1]gvernik is now known as gvernik11:03
*** fifieldt_ has joined #openstack-swift11:16
*** fifieldt has quit IRC11:17
*** Manish_ has quit IRC11:35
*** haomaiwang has quit IRC11:42
*** haomaiwang has joined #openstack-swift11:43
*** cheri has quit IRC11:58
*** mkollaro has quit IRC12:03
*** mkollaro has joined #openstack-swift12:03
*** mkollaro has quit IRC12:05
*** mkollaro has joined #openstack-swift12:05
*** mkollaro has quit IRC12:06
*** mkollaro has joined #openstack-swift12:06
*** mkollaro has quit IRC12:11
*** cheri has joined #openstack-swift12:16
*** mkollaro has joined #openstack-swift12:17
*** zhiyan is now known as zhiyan_12:23
*** cheri has quit IRC12:32
openstackgerritEamonn O'Toole proposed a change to openstack/swift: Parallel object auditor  https://review.openstack.org/5977812:33
*** mmcardle has quit IRC12:35
*** ppai has quit IRC12:36
openstackgerritPeter Portante proposed a change to openstack/swift: In-process swift server for functional tests  https://review.openstack.org/6610812:45
*** cheri has joined #openstack-swift12:45
*** mkollaro1 has joined #openstack-swift12:45
*** mkollaro has quit IRC12:45
*** Trixboxer has joined #openstack-swift12:46
portantedfg: interested in taking https://review.openstack.org/66108 for a spin?12:46
*** tongli has joined #openstack-swift12:55
*** jamie_h has quit IRC13:01
*** jamie_h has joined #openstack-swift13:01
*** fifieldt_ is now known as fifieldt13:03
*** mmcardle has joined #openstack-swift13:05
*** gvernik has quit IRC13:11
*** psharma has quit IRC13:31
*** lpabon has joined #openstack-swift13:46
*** lpabon has quit IRC13:50
*** cheri has quit IRC13:59
*** tdasilva has joined #openstack-swift14:02
*** pconstantine has joined #openstack-swift14:03
openstackgerritEamonn O'Toole proposed a change to openstack/swift: Sleep between object ZBF process forks  https://review.openstack.org/9103714:11
luisbgmorning14:15
*** zhiyan_ is now known as zhiyan14:23
*** changbl has quit IRC14:27
*** praveenkumar_ has joined #openstack-swift14:47
*** praveenkumar has quit IRC14:49
*** praveenkumar_ is now known as praveenkumar14:51
*** Longgeek_ has joined #openstack-swift15:01
*** tongli has quit IRC15:14
*** jamie_h has quit IRC15:17
*** jamie_h has joined #openstack-swift15:18
*** kevinc_ has joined #openstack-swift15:19
*** shakamunyi has joined #openstack-swift15:21
*** haomaiw__ has joined #openstack-swift15:26
*** haomaiwang has quit IRC15:28
*** zhiyan is now known as zhiyan_15:31
openstackgerritEamonn O'Toole proposed a change to openstack/swift: Sleep between object ZBF process forks  https://review.openstack.org/9103715:38
*** foexle has quit IRC15:38
otooleegholt: portante: Thanks for the rapid review of the ZBF sleep change.  I've posted a revised patch set with unit tests that actually pass this time15:40
*** mwstorer has joined #openstack-swift15:40
*** zhiyan_ is now known as zhiyan15:42
*** Longgeek_ has quit IRC15:49
*** kevinc_ has quit IRC15:57
*** kevinc_ has joined #openstack-swift15:59
*** mwstorer has quit IRC16:02
*** joeljwright has quit IRC16:05
*** zhiyan is now known as zhiyan_16:11
notmynamegood morning16:13
physcxgood afternoon16:14
notmynamelooks like San Francisco has one of the latest average workday start times. http://fivethirtyeight.com/datalab/which-cities-sleep-in-and-which-get-to-work-early/ :-)16:16
physcxnotmyname: we did track down the cause of the problem with chunked transfer-encoding and how to duplicate it on vagrant-- will post a write up about it later16:17
physcxalso a fix16:17
notmynameah, nice. thanks16:17
*** chandan_kumar has quit IRC16:19
openstackgerritEamonn O'Toole proposed a change to openstack/swift: Sleep between object ZBF process forks  https://review.openstack.org/9103716:22
*** joeljwright has joined #openstack-swift16:36
*** nshaikh has quit IRC16:36
*** joeljwright has quit IRC16:48
peluse_ FYI, a few storage policy patches to wrap up support for modules that we missed previously.  Available for review now... especially for cores who have not looked too much into Policies:16:56
peluse_Add Storage Policy Support to Container Sync https://review.openstack.org/#/c/86469/16:56
peluse_Add Storage Policy Support to Recon Middleware https://review.openstack.org/#/c/87387/16:56
peluse_Add Storage Policy support to the Account Reaper https://review.openstack.org/#/c/88098/16:56
*** shri has joined #openstack-swift16:56
*** krtaylor has quit IRC16:56
peluse_notmyname:  on the reaper, clayg and I talked last week and feel like its OK to add policy support as it is in this patch and deal with the internal client comment later... hope that's cool w/you16:57
*** gvernik has joined #openstack-swift16:59
notmynamepeluse_: ah, cool. I haven't had a chance to catch up on that since last week, but it's on my todo list for today and tomorrow17:00
peluse_notmyname:  no prob - just trying to lobby for some of these misc patches to get merged so we can focus on reviee of clayg's reconciler here very soon17:01
*** zaitcev has joined #openstack-swift17:06
*** ChanServ sets mode: +v zaitcev17:06
*** rcleere has joined #openstack-swift17:18
*** chandan_kumar has joined #openstack-swift17:20
*** gyee has joined #openstack-swift17:23
*** changbl has joined #openstack-swift17:23
*** shri1 has joined #openstack-swift17:29
*** shri1 has quit IRC17:29
portanteotoolee: you are welcome, and I will take a look in a bit17:30
*** shri has quit IRC17:31
*** openstackgerrit has quit IRC17:32
*** openstackgerrit has joined #openstack-swift17:32
*** gvernik has quit IRC17:33
*** mmcardle has quit IRC17:35
*** kevinc_ has quit IRC17:38
*** kevinc_ has joined #openstack-swift17:38
*** gvernik has joined #openstack-swift17:39
*** joeljwright has joined #openstack-swift17:44
*** lpabon has joined #openstack-swift17:47
*** chandan_kumar has quit IRC17:49
*** joeljwright has quit IRC17:49
luisbgzaitcev, you reviewed the previous iteration of this positively: https://review.openstack.org/#/c/90103/18:00
luisbghave a minute to see the new patch (based on a suggestion from Christian)18:00
zaitcevluisbg: I might18:01
*** shri has joined #openstack-swift18:01
luisbgzaitcev, thank you :)18:01
*** gvernik has quit IRC18:02
* notmyname is figuring out the new gerrit stuff18:17
claygpeluse_: notmyname: reconciler is done, i'm cleaning up some tests/pep8 in the patch chain them i'm going to be doing reviews18:17
notmynamewoot18:18
claygpeluse_: notmyname: I'm going to try and get through all of the pending ec changes and review some stuff on master too - clear out the queue ahead of the sp-rebase chain18:18
*** gvernik has joined #openstack-swift18:21
openstackgerritClay Gerrard proposed a change to openstack/swift: Keep status_changed_at up-to-date with status changes.  https://review.openstack.org/8671418:27
openstackgerritClay Gerrard proposed a change to openstack/swift: Extend direct_client  https://review.openstack.org/8814418:27
openstackgerritClay Gerrard proposed a change to openstack/swift: Add reconciler probetest outline  https://review.openstack.org/9093418:27
openstackgerritClay Gerrard proposed a change to openstack/swift: Add Storage Policies to container.backend  https://review.openstack.org/9093518:27
openstackgerritClay Gerrard proposed a change to openstack/swift: Update FakeLogger with better log level handling  https://review.openstack.org/9093218:27
openstackgerritClay Gerrard proposed a change to openstack/swift: Add container-reconciler daemon  https://review.openstack.org/8590818:27
openstackgerritClay Gerrard proposed a change to openstack/swift: Make FakeRing a use more real code  https://review.openstack.org/9093318:27
openstackgerritClay Gerrard proposed a change to openstack/swift: Add LRUCache to common.utils  https://review.openstack.org/9093818:27
openstackgerritClay Gerrard proposed a change to openstack/swift: Add Storage Policy to container put/delete object  https://review.openstack.org/9093618:27
openstackgerritClay Gerrard proposed a change to openstack/swift: Enqueue misplaced objects during container replication  https://review.openstack.org/9093718:27
openstackgerritClay Gerrard proposed a change to openstack/swift: Merge container storage_policy_index values.  https://review.openstack.org/8672018:27
dfgportante: ya i'll check out that patch18:30
portantedfg: thanks18:36
luisbgnotmyname, some of the new gerrit stuff is cool18:39
luisbgI like it18:39
luisbgclayg, whoa. busy? :P18:40
cschwedecschwede18:41
claygit was ust a rebase18:41
luisbgclayg, yeah :)18:43
physcxQuestion about submitting to gerrit (doing my first one): I have a change to DiskfileWriter's write method and a rather lengthy write-up explaining the reason for it as well as some performance metrics of before and after. The write-up is roughly 250 lines at 80 col width -- is that too large to use within the commit description? Is there a preferred way to attach the lengthy description to...18:44
physcx...the patch?18:44
notmynamephyscx: as long as you have a summary at the top of the commit message, I don't mind long commit messages. but if it's info that's good for ongoing cluster operations, then it could go in the docs18:45
*** joeljwright has joined #openstack-swift18:45
claygwell... there's bound to be *some* limit - and 250 lines has got to be close?18:46
portantephyscx: interested in that patch, can you add me?18:46
portanteYou can always post it work-in-progress as well18:46
clayghell dfg's cors commit was only 11018:47
notmynameheh, that's the one I was thinking of :-)18:47
physcxportante: do I add you after i push with git review?18:48
notmynamephyscx: alternatives are to provide a good summary in the commit message and then give details in the review comments18:48
claygphyscx: you might see if you can cut it down to ~100 lines and post additional information in the comments (just review +0 your change with some notes or a link to a gist/paste or something)18:49
dfgi made the commit msg that long so people would just get bored and hit Approved without looking at the code.18:49
physcxalright I'll go that route, ty18:49
portantephyscx: that will work18:49
*** joeljwright has quit IRC18:50
notmynamedfg: you shouldn't have made the message so entertaining then "...since the purpose of CORS is to annoy people..."18:51
dfg:)18:51
creihtlol18:55
*** bsdkurt has joined #openstack-swift18:56
openstackgerritShaun McDowell proposed a change to openstack/swift: Buffer DiskfileWriter writes  https://review.openstack.org/9113318:59
*** jamie_h has quit IRC18:59
cschwedeLook at that patch - now this is quite cool for new contributors ^^19:00
physcxwell thats no good... the comment section had no respect for spacing what-so-ever19:04
creihtheh19:04
creihtphyscx: yeah it is annoying19:04
physcxis there even a way to delete it?19:04
creihtphyscx: it uses some sort of markup but doesn't really indicate that to you19:04
portantephyscx: that is why I put that stuff in the commit message, since it pertains to the nature of the commit19:04
zaitcevIs anyone here familiar with our EC? I have a simple question: do we have a segment size for reconstruction and if yes, how big is it?19:04
zaitcevNot sure if I use our terminology right but basically what we call "chunk" works like a very long codeword.19:05
peluse_zaitcev: so we have lots of terms...19:06
peluse_zaitcev: I'll send you an email as its too much to type in here19:07
zaitcevSo I'm wondering, is it possible to stream inside the chunk (in which case chunk can be as long as we need, but its length has to be recorded in metadata somewhere).19:07
zaitcevpeluse_: thanks a lot, although I'm going to have a meeting with Intel in 53 minutes where I should know it19:07
peluse_zaitcev:  so things still stream through the proxy and we buffer up what we call a 'segment'.  then we EC that segment and send those 'frgaments' out to the nodes. The default segment size is 1MB19:08
zaitcevpeluse_: makes sense, thanks. What's a chunk, then?19:08
*** gvernik has quit IRC19:09
peluse_zaitcev:  we don't use chunk on purpose to avoid confusing with http chukning.  You'll hear it used in other EC implementations though and the equivalent for us is fragment (the output of the encoder)19:10
zaitcevpeluse_: got it19:10
peluse_zaitcev:  there are some slides in your inbox, feel free to hit us up w/questions or if you need something real time for your upcoming call ping me and we can chat on the phone if needed19:11
claygphyscx: so what was the speed the difference of using the 64k disk write vs 2-5MB write?  It's not clear to me why the larger is faster - it's buffered fileio - we only sync every 512MB by default?19:11
zaitcevpeluse_: do you happen to know the Subject: by any chance19:12
peluse_clayg:  thanks for taking a look at the recon thing - I'll go check out the cli that you mention since right now I don't understand your comment :)19:12
peluse_zaitcev:RE: Sync up on Swift19:12
claygwell... it's just that in cli.recon it does this thing where it set's like a "ring_file" var - and then it keys into the response from that19:13
peluse_zaitcev:  wait.. sorry... "RE: Swift EC tree"19:13
claygpeluse_: it needs to like look at all the rings in the response and then decide if it shold check them or not or something?19:13
zaitcevpeluse_: ah, I got that. It's 2 images that Tushar sent me. Thanks.19:13
zaitcevpeluse_: admittedly one of them has Segment_Size mentioned.19:14
peluse_zaitcev:  yup19:14
peluse_zaitcev:  and as you can see we store a bunch of info in swift visible meta and there's also opaque meta embedded in the segments for use by the EC library itself to aid in all sorta of operations19:14
zaitcevttyl19:15
peluse_clayg:  hell, I didn't even know that was there :)19:15
portantephyscx: I like the concept, how many concurrent writes to multiple objects were performed?19:16
peluse_clayg:  as you saw, I updated the middleware to look at all of the ring files and then added what was previously missing test code for that capabiilties (ring md5 check) which was just a barrel of monkeys with the different gzip header styles between py 26 and 2719:18
physcxclayg: we use a modified version of diskfile that uses DirectIO. We skip the buffered fileio and write 4k aligned straight to disk and under heavy load were getting around a 5x speed up over the os buffered fileio.19:18
claygoic19:19
claygwell then you better buffer in userland hadn't you!19:19
portantephyscx: is that diskfile open source?19:19
physcxyes but we also felt that it was nice to have disk_chunk_size affect the disk read/writes and the network_chunk_size affect the network19:20
physcxportante: yep its submitted to gerrit somewhere i'll dig up a link - we'll probably turn it into it's own diskfile similar to the way mem_diskfile was done but for direct-io19:20
portantephyscx: cool19:21
creihtnotmyname: the other thing that I miss now that we have pbr, is being able to just look at the code and know what version it is19:21
creihtnotmyname: is there an easy way to know what the current version of swift is?19:21
portantecreiht: its the latest verision ,right?19:21
portante;)19:21
creihtheh19:21
physcxportante: are you asking about concurrent writes to multiple objects in our SAIO testing?19:22
portanteyes19:22
physcxjust the default swift-bench --saio settings which i believe is 10 concurrent19:22
*** gholt has quit IRC19:22
portanteso in the past I have measured effects of eventlet concurrency on these operations19:23
portanteone thing I found, which seems to hold still today, is that by lowering the number of concurrent connections per worker and raising the number of worker processes, response times start to smooth out19:24
portantemax_clients & workers parameters19:24
physcxwell we saw the problem with a single connection even19:24
portantewas that with or without the direct io?19:25
physcxwithout19:25
physcxits in that mangled comment19:25
portante;)19:25
portanteyes, that was kinda hard to follow entirely19:25
portante:)19:25
portantewith the single connection that was with chunked transfer?19:25
physcxwant me to email you the unmangled version of that?19:25
portanteyes, please19:26
portantethanks19:26
zaitcevcreiht: does this work  PYTHONPATH=$(pwd) python -c "import swift; print swift.__version__"19:29
zaitcevpeluse_: Do you remember how the mode of storage is called where you do not have the original object stored in the clear? Kevin mentioned it on Trello, but... Like synchronous vs. asynchronous, but different.19:32
creihtzaitcev: well yeah I can do something like that, but I'm not certain it is showing the right version19:32
peluse_zaitcev:  symmetrical I think... one sec I'll double check19:33
zaitcevcreiht: why not if path is correct, my shows 1.13.1.rc1.346.g8dd0aab or 1.12.0-1.z6.el6 in my tests, looks correct19:34
creihtI guess the rc1 thing is throwing me off19:34
creihtbecause that doesn't seem right19:35
creihtnotmyname: what version of swift was the icehouse relese?19:35
peluse_zaitcev:  sorry, systematic is in the clear (versus non-systematic)19:36
zaitcevpeluse_: I'm sorry I sent you away, it's called "systematic" and "non-systematic". He mentioned it in EC Auditor card.19:36
notmynamecreiht: 1.13.119:36
zaitcevpeluse_: got that19:36
notmynamecreiht: checking on something19:36
creihtnotmyname: ok19:36
creihtthx19:36
notmynamebah!!!19:36
claygfucking pbr19:37
notmynameno, not that19:37
claygit's sorta fucked up19:37
creihtlol19:37
peluse_zaitcev:  if you're looking for a good general EC overview:  http://web.eecs.utk.edu/~plank/plank/papers/2013-02-11-FAST-Tutorial.pdf19:37
creihtI was trying hard to not badmouth pbr this time :)19:37
notmynamethe -infra job that is supposed to automatically merge the milestone-proposed branch into master (ie so the tags work ie so the versions work) never got ran19:37
clayglike you get the version of the last thing you installed - unless it's not installed - then just changing the checkout (if you have pbr installed) can sorta figure it out for tags and shas19:37
* notmyname goes to talk in -infra19:37
peluse_zaitcev:  Kevin's done lots of work with him... (Plank, authro of the slides I just sent a link to)19:38
claygand why *is* it rc1?  I have an rc2 tag?  of all complicated things we have to work on - why does version numbers have to be one of them?19:38
notmynameclayg: because the rc1 is an ancestor of the tip of master. sans rc and rc2 both are on the milestone-proposed branch, which is not an ancestor of master19:39
*** gholt has joined #openstack-swift19:46
*** ChanServ sets mode: +v gholt19:46
*** joeljwright has joined #openstack-swift19:47
*** joeljwright has quit IRC19:51
*** krtaylor has joined #openstack-swift19:58
openstackgerritShaun McDowell proposed a change to openstack/swift: Buffer DiskfileWriter writes  https://review.openstack.org/9113320:07
*** fifieldt has quit IRC20:08
*** fifieldt has joined #openstack-swift20:09
shriIn devstack, if I specify the branch for swift as stable/icehouse, shouldn't it install swift version 1.13.1?20:09
shriI did that but inspite of it, I see the version in /info as 1.11.020:10
*** bach has joined #openstack-swift20:12
shrino one uses devstack here?20:13
*** bach has quit IRC20:15
glangemost of us do swift on "hard mode" :)20:16
notmynameshri: ya it should. I'm not sure how it picks the version20:17
claygshri: i've run swift on devstack, but I haven't tried the branch specifier?20:17
notmynameditto20:17
shriI see.. let me try without specifying a branch.20:17
physcxIs there a specific swift wiki for posting long formatted write-ups for submitted patches to gerrit?20:20
physcxnvmd got it20:21
glangephyscx: https://blueprints.launchpad.net/swift <-- maybe ?20:22
notmynamehttps://wiki.openstack.org/wiki/Swift20:23
notmynameand you can proabably add pages under that20:23
glangehttp://paste.openstack.org/ <-- maybe ?20:23
notmynamehttp://paste.ronin.io20:24
notmyname'cause it uses swift itself20:24
* notmyname is trying to build pandemicsyn's user base20:25
glangeI think he just hopes somebody pastes some valuable secrets20:29
*** tsg has joined #openstack-swift20:44
luisbgis it possible Jenkins missed a +2 core review? or is it blocking pushes to Zuul for some other reason?20:46
*** joeljwright has joined #openstack-swift20:48
*** tdasilva has quit IRC20:51
*** joeljwright has quit IRC20:52
*** tdasilva has joined #openstack-swift20:53
notmynameluisbg: what are you seeing?21:16
luisbgnotmyname, https://review.openstack.org/#/c/90103/21:16
luisbghas a +2 from Pete, but it wasn't pushed to Zuul or isn't listed in patches waiting for one core review21:17
luisbgso in a bit of limbo21:17
notmynameluisbg: probably a side effect of the gerrit upgrade (for it not being listed)21:18
luisbgnotmyname, it fell through the cracks then hehehee21:18
*** krtaylor has quit IRC21:18
*** joeljwright has joined #openstack-swift21:18
notmynameah, I bet it's because of the "Verified" "CodeReview" and "Approved" filters21:19
notmynameprobably one of those is different now21:19
notmynameprobably Approved vs the new workflow thing21:19
luisbgnotmyname, yes, I thought of that but I don't know what the differences are now21:19
notmynameme neither21:20
luisbgwhat is Workflow? and probably the list filters in https://wiki.openstack.org/wiki/Swift/PriorityReviews need to be updated21:20
notmynameluisbg: ya, I updated them so that they don't error out, but obviously didn't get all the changes21:22
luisbgnotmyname, if you find some resource where the new changes are explained I can help you update the filters21:25
*** bach has joined #openstack-swift21:27
openstackgerritClay Gerrard proposed a change to openstack/swift: Fixes probe tests with non-zero default storage policy  https://review.openstack.org/8749221:32
*** bach has quit IRC21:35
notmynameluisbg: that would be great! all the "docs" I've seen are https://wiki.openstack.org/wiki/GerritUpgrade. you may need to look at upstream gerrit to find the right incantation21:41
openstackgerritA change was merged to openstack/python-swiftclient: Mock auth_end_time in test_shell.test_download  https://review.openstack.org/9002621:45
Alex_Gaynorwoo, one more patch until all swiftclient tests pass on py3k!21:49
notmynameluisbg: looks like maybe the -infra team is making some dashboards? https://etherpad.openstack.org/p/gerrit-dashboards21:58
*** dosaboy has quit IRC22:03
*** dosaboy has joined #openstack-swift22:04
*** rcleere has quit IRC22:13
*** saschpe has quit IRC22:23
*** joeljwright has quit IRC22:24
*** saschpe has joined #openstack-swift22:26
*** bach has joined #openstack-swift22:28
*** zigo_ has joined #openstack-swift22:35
*** zigo has quit IRC22:37
*** wer has quit IRC22:37
*** wer has joined #openstack-swift22:37
*** changbl has quit IRC22:37
*** bach has quit IRC22:40
*** kevinc_ has quit IRC22:50
*** bach has joined #openstack-swift23:08
*** Trixboxer has quit IRC23:08
*** bach has quit IRC23:14
*** shakamunyi has quit IRC23:14
*** joeljwright has joined #openstack-swift23:15
*** shakamunyi has joined #openstack-swift23:18
*** joeljwright has quit IRC23:19
*** joeljwright has joined #openstack-swift23:24
*** joeljwright has quit IRC23:37
*** matsuhashi has joined #openstack-swift23:38
openstackgerritShaun McDowell proposed a change to openstack/swift: Buffer DiskfileWriter writes  https://review.openstack.org/9113323:43
openstackgerritClay Gerrard proposed a change to openstack/swift: Add Storage Policy support to the Account Reaper  https://review.openstack.org/8809823:43
physcxI've added a much less bad version of the write-up on buffered writes and the problem with chunked transfers for large read sizes at https://wiki.openstack.org/wiki/User:Physcx23:47
notmynamephyscx: great writeup. thanks23:50

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