Wednesday, 2014-11-19

*** dmsimard is now known as dmsimard_away00:00
*** david-lyle is now known as david-lyle_afk00:06
*** rmcall has joined #openstack-swift00:06
*** tdasilva has quit IRC00:17
*** dmorita has joined #openstack-swift00:29
*** sungju has joined #openstack-swift00:39
*** oomichi has joined #openstack-swift00:43
*** rmcall has quit IRC00:47
*** rmcall has joined #openstack-swift00:49
*** rmcall has quit IRC00:49
openstackgerritTushar Gohad proposed openstack/swift: EC: Allow tuning ec_object_segment_size per policy  https://review.openstack.org/13238901:01
*** gyee has quit IRC01:40
*** haomaiwang has quit IRC01:47
* charz Testing stackforge/swift3 and fujita/swift3 with s3test01:51
*** nomad411 has joined #openstack-swift01:58
*** tamizh_geek has joined #openstack-swift01:58
*** nosnos has joined #openstack-swift02:02
*** tamizh_geek has quit IRC02:03
*** haomaiwang has joined #openstack-swift02:06
openstackgerritTushar Gohad proposed openstack/swift: EC: Allow tuning ec_object_segment_size per policy  https://review.openstack.org/13238902:07
openstackgerritTushar Gohad proposed openstack/swift: WIP EC: HTTP PUT/HEAD changes for object size/etag reporting  https://review.openstack.org/13548802:11
*** tsg has quit IRC02:13
*** NM has joined #openstack-swift02:24
*** X019 has quit IRC02:32
*** tamizh_geek has joined #openstack-swift02:38
*** X019 has joined #openstack-swift02:41
*** km has joined #openstack-swift02:46
*** km is now known as Guest3089202:47
*** exploreshaifali has joined #openstack-swift02:58
*** nomad411 has quit IRC03:02
*** nomad411 has joined #openstack-swift03:06
*** tamizh_geek has quit IRC03:06
*** miqui has joined #openstack-swift03:07
*** nomad411 has quit IRC03:10
*** tkay has quit IRC03:14
*** tkay has joined #openstack-swift03:14
*** tkay has quit IRC03:17
*** nosnos has quit IRC03:20
*** tsg has joined #openstack-swift03:21
*** exploreshaifali has quit IRC03:22
*** tsg has quit IRC03:30
*** tsg has joined #openstack-swift03:31
*** NM has quit IRC03:31
*** tsg_ has joined #openstack-swift03:40
*** tsg has quit IRC03:40
*** X019 has quit IRC03:47
*** X019 has joined #openstack-swift03:51
*** exploreshaifali has joined #openstack-swift03:56
*** exploreshaifali has quit IRC03:59
*** rmcall has joined #openstack-swift04:03
*** X019 has quit IRC04:05
*** X019 has joined #openstack-swift04:08
*** nosnos has joined #openstack-swift04:12
*** flwang has quit IRC04:21
*** aswadr has joined #openstack-swift04:22
*** exploreshaifali has joined #openstack-swift04:24
*** flwang has joined #openstack-swift04:24
*** panbalag has quit IRC04:41
*** tellesnobrega has quit IRC04:44
*** zaitcev has quit IRC05:06
*** rmcall has quit IRC05:07
*** ppai has joined #openstack-swift05:34
*** tsg_ has quit IRC05:37
*** miqui has quit IRC05:44
*** mahatic_ has quit IRC05:44
*** k4n0 has joined #openstack-swift05:52
*** rmcall has joined #openstack-swift05:55
*** david-lyle_afk has quit IRC06:12
*** nshaikh has joined #openstack-swift06:34
*** k4n0 has quit IRC06:39
*** judd7 has quit IRC06:43
*** k4n0 has joined #openstack-swift06:53
*** rmcall has quit IRC07:13
*** kevinbenton has quit IRC07:22
*** k4n0 has quit IRC07:31
*** mmcardle has joined #openstack-swift07:35
*** k4n0 has joined #openstack-swift07:44
*** exploreshaifali has quit IRC07:46
*** nellysmitt has joined #openstack-swift07:53
*** SkyRocknRoll has joined #openstack-swift07:54
*** sungju has quit IRC08:02
*** exploreshaifali has joined #openstack-swift08:05
*** exploreshaifali has quit IRC08:06
*** exploreshaifali has joined #openstack-swift08:08
*** geaaru has joined #openstack-swift08:34
*** Guest30892 has quit IRC08:41
*** jordanP has joined #openstack-swift08:49
*** NM has joined #openstack-swift08:50
*** rawat_vedams has joined #openstack-swift08:53
*** NM has quit IRC08:54
*** dmorita has quit IRC09:03
*** nosnos has quit IRC09:07
*** rawat_vedams has quit IRC09:08
*** nosnos has joined #openstack-swift09:08
*** oomichi has quit IRC09:16
*** acoles_away is now known as acoles09:29
fifieldt_notmyname, looks like the translation proposal is failing for swift at the moment -- https://jenkins.openstack.org/job/swift-propose-translation-update/63/console09:31
*** ppai has quit IRC09:32
fifieldt_it's looking for a locale directory that doesn't exist09:32
*** nshaikh has quit IRC09:33
fifieldt_probably because it moved from local to swift/locale09:33
fifieldt_so, that's a bug in the i18n script09:33
fifieldt_I'm lodging that now09:33
*** tamizh_geek has joined #openstack-swift09:33
*** joeljwright has joined #openstack-swift09:35
*** nshaikh has joined #openstack-swift09:36
fifieldt_https://bugs.launchpad.net/openstack-i18n/+bug/1394120 there's the bug link. also posted on the i18n ML09:36
*** brnelson has quit IRC09:37
*** brnelson has joined #openstack-swift09:37
*** ppai has joined #openstack-swift09:45
*** exploreshaifali has quit IRC09:51
*** geaaru has quit IRC09:55
*** tamizh_geek has quit IRC10:00
*** geaaru has joined #openstack-swift10:08
*** Anticimex has quit IRC10:12
*** dmsimard_away is now known as dmsimard10:17
*** Anticimex has joined #openstack-swift10:18
*** aix has joined #openstack-swift10:23
*** X019 has quit IRC10:28
*** tellesnobrega has joined #openstack-swift10:38
*** tamizh_geek has joined #openstack-swift10:41
*** flwang has quit IRC10:44
*** tellesnobrega has quit IRC10:56
*** xianghui_ is now known as xianghui10:58
*** X019 has joined #openstack-swift11:04
*** erlon has joined #openstack-swift11:07
*** haomaiwang has quit IRC11:19
*** tamizh_geek has quit IRC11:32
*** haomaiwang has joined #openstack-swift11:37
*** tellesnobrega has joined #openstack-swift11:40
*** dmsimard is now known as dmsimard_away11:43
*** ekarlso- has quit IRC11:44
*** ekarlso- has joined #openstack-swift11:49
*** aswadr has quit IRC11:50
*** aix has quit IRC11:52
*** nellysmitt has quit IRC12:05
*** Anticimex has quit IRC12:13
*** panbalag has joined #openstack-swift12:15
*** tamizh_geek has joined #openstack-swift12:17
*** dmsimard_away is now known as dmsimard12:18
*** Anticimex has joined #openstack-swift12:19
*** ppai has quit IRC12:35
*** tdasilva has joined #openstack-swift12:35
*** tdasilva has quit IRC12:39
*** a1|away is now known as AbyssOne12:39
*** mahatic has joined #openstack-swift12:41
*** tellesnobrega has quit IRC12:42
*** aix has joined #openstack-swift12:42
*** ekarlso- has quit IRC12:50
*** ekarlso- has joined #openstack-swift12:50
*** flwang has joined #openstack-swift12:52
*** mmcardle has quit IRC13:05
*** tamizh_geek has quit IRC13:11
*** SkyRocknRoll has quit IRC13:14
*** NM has joined #openstack-swift13:15
*** exploreshaifali has joined #openstack-swift13:20
*** nellysmitt has joined #openstack-swift13:34
*** mmcardle has joined #openstack-swift13:37
*** tellesnobrega has joined #openstack-swift13:40
*** tellesnobrega has quit IRC13:40
*** miqui has joined #openstack-swift13:51
*** jistr has joined #openstack-swift13:53
*** jistr is now known as jistr|mtg13:53
*** exploreshaifali has quit IRC14:02
openstackgerritDaniel Wakefield proposed openstack/python-swiftclient: Fix misplaced check for None in SwiftUploadObject.  https://review.openstack.org/13310714:06
*** panbalag has quit IRC14:12
openstackgerritAndreas Jaeger proposed openstack/swift: Fix translation setup  https://review.openstack.org/13560614:13
fifieldt_^^ that's a simple fix for the translation import problem we were discussing yeserday notmyname14:16
*** mahatic has quit IRC14:20
*** mahatic has joined #openstack-swift14:30
*** openstackgerrit has quit IRC14:33
*** openstackgerrit has joined #openstack-swift14:34
*** zul has joined #openstack-swift14:35
*** SkyRocknRoll__ has joined #openstack-swift14:37
*** nellysmitt has quit IRC14:41
*** pberis1 has quit IRC14:46
*** openstackgerrit has quit IRC14:49
*** openstackgerrit has joined #openstack-swift14:50
*** nosnos has quit IRC14:52
*** geaaru has quit IRC14:52
*** exploreshaifali has joined #openstack-swift14:54
*** zul has quit IRC14:55
*** nellysmitt has joined #openstack-swift15:00
*** tamizh_geek has joined #openstack-swift15:02
*** fbo has quit IRC15:04
*** bill_az has joined #openstack-swift15:05
*** geaaru has joined #openstack-swift15:05
*** fbo has joined #openstack-swift15:10
*** zul has joined #openstack-swift15:16
*** pberis1 has joined #openstack-swift15:20
*** zaitcev has joined #openstack-swift15:29
*** ChanServ sets mode: +v zaitcev15:29
*** judd7 has joined #openstack-swift15:36
*** tdasilva has joined #openstack-swift15:49
*** lpabon has joined #openstack-swift16:01
zaitcevHave we found a sponsor and location for the next Hackathon?16:04
*** tamizh_geek has quit IRC16:14
*** rmcall has joined #openstack-swift16:15
*** tamizh_geek has joined #openstack-swift16:26
*** nshaikh has quit IRC16:30
*** nellysmitt has quit IRC16:39
*** SkyRocknRoll__ has quit IRC16:42
*** gyee has joined #openstack-swift16:45
*** tamizh_geek has quit IRC16:49
openstackgerritAlistair Coles proposed openstack/swift-specs: Spec for at-rest encryption.  https://review.openstack.org/12322016:50
acolestorgomatic: ^^ just a rebase to new dir structure16:51
*** tamizh_geek has joined #openstack-swift16:53
*** k4n0 has quit IRC16:56
notmynamegood morning16:57
notmynamefifieldt_: thanks. I'll look at it this morning16:57
mahaticgood morning16:57
notmynamezaitcev: not yet. I was waiting until I got back from the summit. it's something I need to do soon16:57
notmynamereminder to all that the meeting today is in 2 hours16:58
zaitcevnotmyname: thanks. As usual there are some budgetary issues and I'm being poked about it.16:58
notmynamezaitcev: of course16:58
zaitcevI heard the M summit is slated for Tokyo16:58
zaitcevI'll be there even if I have to pay my way16:59
pelusemorning16:59
notmynamezaitcev: next 2 are vancouver and tokyo16:59
notmynamehow do I find the gerrit patch from the jenkins output? I want to look at the translation patch17:05
notmynamefifieldt_: ^17:05
*** tkay has joined #openstack-swift17:08
*** IRTermite has quit IRC17:09
*** IRTermite has joined #openstack-swift17:09
*** NM has quit IRC17:10
*** NM has joined #openstack-swift17:10
NMNext summits are going to be on Vancouver and Tokyo?17:13
eikkeyes17:18
*** gvernik has joined #openstack-swift17:19
eikkeswifterdarrell: should I put that bindings code in swift.common.utils as it is now, or create a new module? (it's > 3200 lines now, that module)17:22
*** atan8 has joined #openstack-swift17:35
*** tamizh_geek has quit IRC17:37
*** geaaru has quit IRC17:38
*** tamizh_geek has joined #openstack-swift17:41
swifterdarrelleikke: I'd put it in utils, but that's open for debate17:42
swifterdarrelleikke: if you did pull it out, I'd probably expect all the ctypes-wrappers-for-syscall/glibc-functions to be in that new file17:43
swifterdarrelleikke: with some name that reflects that17:43
eikkehmh, k. I called it 'swift.common.splice' for now, and will push it like that, but that's open for debate, I won't bikeshed over this (but I do think having a proper module is the way to go)17:44
* swifterdarrell shrugs17:45
swifterdarrellI think one file per callable function (e.g. splice()) is a bit much, but I agree it's not worth bikeshedding over ;)  I'll +2 it as you did it17:46
*** jordanP has quit IRC17:56
*** aix has quit IRC17:57
*** erlon has quit IRC17:59
*** rmcall has quit IRC18:01
*** rmcall has joined #openstack-swift18:01
*** nshaikh has joined #openstack-swift18:03
notmynamereminder that the swift meeting is in 50 minutes18:10
notmyname(I keep saying things because this is the first meeting since the US time change)18:10
*** tamizh_geek has quit IRC18:11
*** mmcardle has quit IRC18:11
*** Guest99387 has joined #openstack-swift18:22
*** Guest99387 is now known as linuxaddicts18:22
*** exploreshaifali has quit IRC18:23
*** tdasilva has quit IRC18:31
*** zul has quit IRC18:31
linuxaddictshi, i want to scale test swift as a glance back end.18:36
linuxaddictswill uploading few 100 images, creating boot volume and booting off these volumes be a good start? how would this really test swift?18:37
clayglinuxaddicts: well that would test a lot of things - do you have another glance backend you'd be able to repeat the test and compare the results with?18:40
linuxaddictssure, the other one would be the default18:41
zaitcevI'm pretty sure Swift will lose.18:43
notmynamezaitcev: so full of cheer and hope18:43
clayglinuxaddicts: the default is what... a local file system?18:44
zaitcev100 of 10G images is merely 1TB, so for this test all you need to do is buy a $110 2T hybrid drive and plop it into Glance node, format it with XFS, done.18:44
linuxaddictsclayg, yes the default is the local file system.18:45
zaitcevTo make a Swift this small, you need a ton of processes started, integrate it with your auth. I know beginners keep blowing stuff up doing that.18:45
zaitcevBut most importantly, Swift will keep 3 copies and will send all the traffic through gazillion processes on the same CPU and will lose in performance.18:46
*** tdasilva has joined #openstack-swift18:46
zaitcevIt basically is one of those silly micro-benchmarks at which we're very bad18:46
claygstupid ec has too many words18:47
claygso an object is a fragment archive, so that means it holds a number of fragments, one for each segment18:47
zaitcevNow if linuxaddicts had 1000 clients all uploading and launching VMs on 100 compute nodes, then we would crush Glance's default backend into a bloody pancake due to scalability18:48
notmynamelinuxaddicts: zaitcev is right and you mentioned "scale". in the swift world, "scale" is generally though of in billions of objects and PB of data. not 100.18:48
notmynamelinuxaddicts: what is it you're trying to test of find out? do you have a specific use case you're building for?18:48
claygbut the metadata name is "x-object-sysmeta-ec-segment-size" - isn't that the size of the fragment?  or do I have to back calculate from the segment-size how much I need to read off the object to get one fragment from this object that is needed to rebuild the segment?18:49
zaitcevIf we're interested winning comparos like the one linuxaddicts was proposing, we ought to accelerate the "in-process" Swift that portante was proposing. IMHO though.18:51
notmynamezaitcev: you mean tdasilva?18:52
swifterdarrellclayg: at least one of peluse's summit talks had a whole slide (IIRC) for a terminology glossary...18:52
claygswifterdarrell: yeah well, i'm not sure we're internally consistent18:52
zaitcevI didn't think if tdasilva was going to write it himself18:52
zaitcevBut yeah, those two :-)18:52
swifterdarrellclayg: *nod* if so, surely everyone would agree that's undesirable18:53
notmynamezaitcev: tdasilva and ignacio were talking about it. the single-process swift idea has some disadvantages. like mixing net io with disk io and eventlet not really working well there18:54
claygswifterdarrell: well it may be that there's more than one way to look at it, or it may be that the ec-metadata *is* the segment-size and I need to use math to get the fragment-size - in which case it seems less convienent to store the segment-size, but at least it's consistent use of the words18:54
swifterdarrellzaitcev: notmyname: optimizing Swift to serve 1T of data from one server well, just doesn't seem interesting to me...18:54
notmynameswifterdarrell: :-)18:55
zaitcevswifterdarrell: as long as you guys keep winning deals that start with 2 racks and go up, I can see why18:55
swifterdarrellclayg: *nod* I have no idea, myself, but a single glossary page *somewhere* for Swift EC stuff would be helpful if it doesn't already exist, to keep everything in line18:55
linuxaddictsnotmyname, the use case i have in mind is to see how swift will behave in a scale environment. and since you clarified the data set will be huge and 100's may not really be worthwhile.18:55
notmynameswifterdarrell: http://specs.openstack.org/openstack/swift-specs/specs/in_progress/erasure_coding.html#terminology18:56
swifterdarrellzaitcev: there's a lot of room between "2 racks" and "1 2T disk"...18:56
swifterdarrellzaitcev: but I can understand the allure of hyperbole ;)18:56
notmynameswifterdarrell: are you saying that hyperbole is the best thing ever?18:57
linuxaddictsthe next question is what will the above test i mentioned really infer if i were to run it?18:57
swifterdarrellnotmyname: oh, gosh, I wouldn't go *that* far18:57
notmynamelinuxaddicts: most of the time people try out swift by building asmaller cluster (eg 10-20% of what they want) and then putting a similar percentage of their target workload to it18:57
zaitcevyeah18:58
*** nshaikh has left #openstack-swift18:59
notmynamelinuxaddicts: there's a lot of differences in a local disk and swift (beyond perf differences for a give workload). swift is designed to provide durable storage that's always available and scales really well. in your proposed test, as described, it's more of a works vs doesn't work. then you have to make a choice based on cost, requirements, etc19:00
notmynamelinuxaddicts: but as zaitcev pointed out, you might in fact just be testing glance's ability to handle your use case19:00
notmynameswift meeting time in #openstack-meeting19:00
linuxaddictsnotmyname, thanks for confirming. i believe the same it will be more of a glance test rather than swift.19:01
peluseso the EC design spec is that single glossary you guys are speaking of19:01
pelusewill send link after meeting19:01
claygpeluse: notmyname already sent http://specs.openstack.org/openstack/swift-specs/specs/in_progress/erasure_coding.html#terminology19:05
claygpeluse: but it didn't really say what x-object-sysmeta-ec-segment-size was exactly19:05
claygalthough I think interestingly enough it is the segment-size, and I need to use get_segment_info to figure out the fragment_size :\19:07
peluseclayg, we already read the whole object when doing a reconstruction and buffer up fragments to get a segment size to feed to pyeclib19:08
pelusewhy do you need to know fragment size?19:09
claygyup that did it19:11
peluseBTW it does look like the metadata section in the design spec needs to be updated in that area...19:11
claygpeluse: i'm looking at the decode path, I don't think we want the proxy to read the whole object when doing a GET ;)19:12
claygpeluse: it seems like you need to figure out the fragment_size when building up your fragment_payloads for decode19:13
claygpeluse: i.e. how much to i read from each node before handing it off the list of fragments to pyeclib to generate the segment which I can send out to the client19:13
pelusea segment_szie worth19:14
claygpeluse: nope, a fragment_size worth19:14
claygi started reading a segment size and I kept getting garbage back from decode19:14
*** tkay has quit IRC19:14
peluseoh yeah, sorry was thinking encode19:15
claygyeah I think we're pretty solid on encode19:15
claygbut since sam is on vacation this week I thought I'd look at decode a bit more so hopefully I'll be able to contribute to a working GET path19:16
*** tkay has joined #openstack-swift19:16
claygalso on my list is that concurrent GET review you posted on priority reviews19:16
pelusesweet19:17
pelusethink I'm gonna head home and work from there after the meeting, if you have time for a quick phone call would like to chat a little about current reconstructor updated_deleted() stuff19:18
claygpeluse: link me some context?19:19
peluseyup https://review.openstack.org/#/c/131872/ and am currently working on update()19:20
claygpeluse: but yeah I can chat, now or soon (w/i ~2-3 hours) would good19:20
*** jordanP has joined #openstack-swift19:20
peluseOK, it will take me about 30 min to get home after the swift meeting, will ping you when I'm back online19:20
claygk19:22
*** bkopilov has quit IRC19:25
*** zul has joined #openstack-swift19:26
*** rcrit has quit IRC19:29
*** rcrit has joined #openstack-swift19:30
*** exploreshaifali has joined #openstack-swift19:38
mattoliverauCools well I'm going back to my holiday, have fun peoples19:53
* portante comes out with the sound of Lurch from the Adams Family TV show ...19:53
portantezaitcev: you rang?19:53
acolesmattoliverau: take it easy19:53
zaitcevportante: mentioned you in conjunction with in-process something.19:53
notmynameportante: just missed the meeting19:54
portantestory of my life19:54
acolesportante: its not a bad way to live :)19:54
portante:)19:55
acolesnotmyname: here's another brown bag talk for your youtube index https://www.youtube.com/watch?v=EMLK5XsU0_819:57
notmynamethanks19:58
*** zul has quit IRC19:59
*** acoles is now known as acoles_away19:59
*** cutforth has joined #openstack-swift19:59
*** tdasilva has quit IRC20:00
*** gvernik has quit IRC20:00
*** zul has joined #openstack-swift20:10
*** tdasilva has joined #openstack-swift20:13
*** dmsimard is now known as dmsimard_away20:16
cebrunsHi - new to Swift, and I am looking for a way to determine the amount of capacity a cluster has.  Free/Used/etc - is there a command that provides that?20:25
notmynamecebruns: do you already have a swift cluster, or are you asking in general?20:26
claygdoesn't recon have something for doing a a distributed df - like for doing drive distribution histograms?20:26
cebrunsI'm hacking around with a SAIO installation.20:26
notmynameya, recon has a good way to see capacity used/available on individual drives20:27
cebrunsYeah - I tried swift-recon on the SAIO and it reports "Error. No drive info available" - I imagine it's because they're loopback devices, but wasn't sure.20:28
notmynamecebruns: ya20:29
peluseclayg, ready when you are.  call me at 480 554 3688 or I can call you - either way20:29
clayglemme find a phone - you don't skype right?20:29
peluseclayg, I can probably make that work if you can't find a phone.  I use Lync w/softphone20:29
notmynamecebruns: so in that case, swift usage, what with all the complexities of replication etc, is really 2 sums (depending on what you're looking for)20:29
notmynamecebruns: the first is the sum of `df` on all of the drives. that gives you the total capacity used in your cluster: all replicas, all metadata, all filesystem overhead20:30
notmynamecebruns: the second is the sum of the "bytes-used" in every account. that's the total of the usable capacity used in the cluster (ie what you probably do billing on)20:31
*** linuxaddicts has quit IRC20:31
claygpeluse: facebook:clay.gerrard <- me skype20:31
cebrunsnotmyname: That makes sense.  Thanks!  Guess I need to install some "real drives" to check it out.20:32
*** nomad411 has joined #openstack-swift20:33
*** NM has quit IRC20:34
claygthanks paul!20:47
peluseno, thank you!20:47
*** rcrit has quit IRC20:50
*** rcrit has joined #openstack-swift20:55
tdasilva  hi, i have a question about versioned writes: lwhat should be the behavior if during a PUT the COPY of the previous obj to the 'versions' container  was successful, but the actual PUT failed20:57
tdasilvawe don't remove the copy that was made right?20:58
notmynametdasilva: what's the current behavior?20:58
tdasilvanotmyname: sorry, i believe that is the current behavior, just wanted to confirm that i wasn't missing something20:59
tdasilvanotmyname: I guess my follow up question would be was the the intended purpose or just something that was overlooked, do we care in other words?21:01
notmynametdasilva: IIRC that was the intended purpose (but that was years ago)21:01
tdasilvanotmyname: ok, I'm not going to be concerned with that for now then21:03
peluseclayg so wrt the hashes.pkl notion, actually the implementation I was pursuing was using the fact that I, as the local reconstructor, know what I'm interested in from my partners, the FI that matches my node index, so that I can21:05
pelusenow pass that on via get)hashes and the hashes.pkl will only be caluclated for relevant .data files21:05
pelusemeaning on hashes.pkl format and set of related functions... but requires the stamp file thing still.21:05
pelusenot a ton of code to do it this way so will complete it and then we can look closer21:05
peluseon=one there one post ago....21:06
peluse"one hashes.pkj format"21:06
*** shakamunyi_ has joined #openstack-swift21:11
*** jasondotstar has joined #openstack-swift21:12
openstackgerritOpenStack Proposal Bot proposed openstack/swift: Updated from global requirements  https://review.openstack.org/8873621:12
*** jasondotstar has quit IRC21:13
*** cutforth has quit IRC21:13
*** jasondotstar has joined #openstack-swift21:14
claygpeluse: maybe if hashes.pkl is {fragment_index: {suffix: hash}}21:15
claygpeluse: then you're still only decode_hashes_pkl.keys() away from your list of stamps21:16
claygpeluse: and maybe also there's an oppertunity to optomize the number of dirs to traverse if you have 10K si[3]'s and only 1 si[2]21:17
claygpeluse: but it's fine, start with something that works21:17
peluseyeah, I think I might have to go that route anyway.  think I'm about to run into an issue with how I was trying to do it.... will keep you posted21:21
*** gyee has quit IRC21:26
*** bill_az has quit IRC21:26
openstackgerritpaul luse proposed openstack/swift: SAIO updates to support EC development environment.  https://review.openstack.org/12815421:27
*** gyee has joined #openstack-swift21:28
*** gyee has quit IRC21:28
*** gyee has joined #openstack-swift21:29
*** gyee has quit IRC21:29
*** gyee has joined #openstack-swift21:30
*** gyee has quit IRC21:31
claygman i am having terrible luck with gerrit today :\21:38
*** exploreshaifali has quit IRC21:39
*** shakamunyi_ has quit IRC21:59
*** rmcall has quit IRC22:05
*** rmcall has joined #openstack-swift22:07
*** zul has quit IRC22:07
*** miqui has quit IRC22:09
*** openstackgerrit has quit IRC22:10
*** openstackgerrit has joined #openstack-swift22:10
*** zul has joined #openstack-swift22:11
*** jasondotstar has quit IRC22:24
*** mahatic has quit IRC22:33
*** jistr|mtg has quit IRC22:42
*** zul has quit IRC22:43
*** rmcall has quit IRC22:47
*** rmcall has joined #openstack-swift22:49
*** gyee has joined #openstack-swift22:55
*** gyee has quit IRC22:55
*** jasondotstar has joined #openstack-swift23:08
*** nomad411 has quit IRC23:14
*** jordanP has quit IRC23:17
*** gyee has joined #openstack-swift23:18
*** jasondotstar has quit IRC23:33
*** jasondotstar has joined #openstack-swift23:36
*** judd7 has quit IRC23:39
openstackgerritMerged openstack/swift: Adds v1 API documentation to doc/source/api  https://review.openstack.org/13510223:39
openstackgerritMerged openstack/swift: Fix translation setup  https://review.openstack.org/13560623:41
openstackgerritNicolas Trangez proposed openstack/swift: Rework `splice` and `tee`  https://review.openstack.org/13531923:43
eikkeswifterdarrell: ^^ (you asked me to ping when I made the changes)23:45
*** zul has joined #openstack-swift23:47
eikke94% test coverage on the module ^_^ (and the remaining 6 lines would need some really old glibc)23:48
notmynameeikke: nice :-)23:53
peluseanyone seen/heard from gholt latelt?  Was looking for an old blog series he did on consistent hashing but can't seem to find it (last known location http://greg.brim.net/page/building_a_consistent_hashing_ring.html)23:53
eikkenotmyname: ty23:55
eikketime for a series episode & sleep now, 1am here23:55
*** joeljwright has quit IRC23:55
*** sungju has joined #openstack-swift23:55
notmynamepeluse: seems all the domain names I've known him to use no longer respond.23:57
notmynameahale: dfg: do you know where gholt's blog went?23:57
ahalenope no idea sorry23:58
*** tdasilva has quit IRC23:59

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