Friday, 2014-12-05

*** physcx has joined #openstack-swift00:08
*** Masahiro has joined #openstack-swift00:10
notmynameglange_: this looks like something you'd find useful http://www.linuxjournal.com/content/autokey-shorthand-typists?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+linuxjournalcom+%28Linux+Journal+-+The+Original+Magazine+of+the+Linux+Community%2900:12
*** sungju has joined #openstack-swift00:12
*** Masahiro has quit IRC00:14
tdasilva_does anybody have a suggestion for an irc client for ios?00:16
*** openstackgerrit has quit IRC00:18
*** openstackgerrit has joined #openstack-swift00:19
notmynametdasilva_: I have LimeChat on my phone. I rarely use it, but when I do it seems sufficient00:19
jokke_tdasilva_: no, I tend not to irc from the switches ;)00:19
mattoliverautdasilva_: I use quassel, you install the server somewhere (rackspace cloud for me) and then you can install clients on what ever you want and you can access the same session  from anywhere. Laptop, phone etc. I use an android client on my phone, but there is an iphone one i think.00:20
notmynametdasilva_: but I'm also pre-disposed to that one since I also use LimeChat on OSX00:20
notmynamemattoliverau: that sounds like an irc bouncer00:20
mattoliveraunotmyname: yeah it is.. but easier to set up :)00:20
tdasilva_thanks for all the tips...i've thought about setting up an irc bouncer, but haven't got to do that yet00:21
mattoliveraubut it does mean my phone buzzes when pinged even when on my laptop :P00:22
tdasilva_mattoliverau: what's the cost of running a vm for that on a rackspace cloud?00:22
notmynametdasilva_: get a bouncer! ;-)00:23
notmynameI use znc00:23
tdasilva_notmyname: do you run it on ec2 or rackspace?00:24
glange_notmyname: that looks interesting00:25
mattoliverautdasilva_: I'd have to look it up. You could use my quassel vm.. but it's in an Oz region, so might be a little slow for you.00:26
mattoliverautdasilva_: if you want to have a play, I can give you an account on the VM so you can set a username and password in the quassel server, the server is easy, its irc.oliver.net.au :)00:28
notmynametdasilva_: I have znc running my a RAX server (only because I have credit there)00:29
tdasilva_mattoliverau: I will take a look at setting up znc, but thanks for the offer! :-)00:30
mattoliverautdasilva_: nps00:32
*** dmorita has joined #openstack-swift00:36
openstackgerritXiang Hui proposed openstack/swift: Fix getaddrinfo if dnspython is installed.  https://review.openstack.org/11661800:37
*** physcx has quit IRC00:51
openstackgerritXiang Hui proposed openstack/swift: Fix getaddrinfo if dnspython is installed.  https://review.openstack.org/11661800:52
*** bkopilov has joined #openstack-swift00:53
*** Masahiro has joined #openstack-swift01:06
*** jwang__ has joined #openstack-swift01:11
claygirssi in screen on my aws tiny gets me by and by01:16
claygnot recommended01:16
*** yuanz has quit IRC01:32
*** yuanz has joined #openstack-swift01:32
*** peluse__ has joined #openstack-swift01:32
*** addnull has joined #openstack-swift01:33
*** peluse_ has quit IRC01:35
*** bill_az has quit IRC01:46
*** nosnos has joined #openstack-swift01:52
*** haomaiwang has joined #openstack-swift01:59
*** kajinamit has joined #openstack-swift01:59
openstackgerritMatthew Oliver proposed openstack/swift: Add concurrent reads option to proxy  https://review.openstack.org/11771002:17
*** Masahiro has quit IRC02:22
*** Masahiro has joined #openstack-swift02:24
*** addnull has quit IRC02:35
*** lpabon has quit IRC02:36
*** nosnos has quit IRC02:48
notmynamemattoliverau: just trying to grok the high-level thing you've done with that patch02:50
notmynameif concurrent_reads is on, then wait concurrent_timeout (default: 0) between subsequent calls to _make_node_request02:51
notmynameand as soon as you get any response, then stop iterating and do cleanup and return the answer02:52
notmynamemattoliverau: is that right?02:52
mattoliveraunotmyname: yup02:53
mattoliverauthat's about right :)02:53
mattoliverauAs soon as you get a good answer (source)02:54
notmynameare you using self.sources as an instance variable so that you create it in method A, modify it in calls to B, and read it back in A?02:58
notmynamecause it seems to work, but also seems like it might be something left over from refactoring out the new method?02:58
openstackgerritHisashi Osanai proposed openstack/swift: Enable Object Replicator's failure count in recon  https://review.openstack.org/13834203:00
notmynamemattoliverau: I don't mean that as a negative review at this point. I just looked at it and that was my first impression03:01
notmyname(the "fun" with text-based communication)03:01
notmynameI'm more curious, actually03:01
mattoliverauYeah, so the green threads can place the reponses. So it has now become and instance variable. The GetOrHeadHandler is created per request so it should be "safe"03:02
mattoliverauI could dump them in results, but newest requires a return value.. I could rework it I guess :)03:04
notmynamemattoliverau: no, don't go do that at this point. I'm only looking at the diff one file at a time03:04
notmynamelike I said, I'm more curious and just trying to understand03:04
notmynamemattoliverau: ok, next question about it...03:06
mattoliveraushoot03:06
notmynamelet's just assume (for the sake of typing) that concurrent_timeout is 003:06
notmynameso you concurrently request up to replica_count nodes. so normally 3. and then only ask for more on a node_timeout basis (10 sec IIRC)03:07
notmynameoh. wait. I get it03:08
notmynameok, so if one of the primary nodes fails fast, you'll still quickly go to a handoff. ie its the faster of however long it takes to return from .waitall() and the node_timeout03:08
mattoliveraunotmyname: clayg noticed that if a, in this case, 4th request was sent, it would get stuck in the queue and result in a 404, whereby putting the timeout in once the queue is full will hopefully elievate this.. this probably needs more testing.03:09
notmynamepoint is, if a primary is offline (drive or server), then it will very quickly ask a handoff as well. and actually, it just keeps replica_count connections going at any one time03:09
notmynameah ok03:09
mattoliverauyup03:10
notmynameand in the case of defaults and a missing file, it will pretty much ask for 3, 3, 3 (primary + 2*primary handoffs = 9). so 3 batches of 3 in a healthy cluster03:11
mattoliverauyeah, depending on the speed of the reponse, but yeah due to node_time, should be batches of 3, which is better then batches of 1 :P03:12
notmyname"better" ;-)03:12
mattoliverauwe could increase the window to be replicas *2 or something03:13
mattoliveraubut its replicas atm03:13
notmynamereplicas makes sense to me03:13
notmynamebut I have zero numbers to back up one way over another03:14
mattoliverauYeah me too, can always make it tunable if thats what the people want later ;)03:14
notmynameless tunable == better (n general)03:14
mattoliverauOr we could implement the TCP windowing protocal and wait to lost requests.. how could that fail :P03:15
mattoliverau*s/to/for03:15
notmynamewhy don't we just use raw sockets and have our own protocol. it could be so much more efficient!03:15
mattoliveraulol, perfect, I'll get on that :P03:16
claygreplica count is the correct answer, but I don't think the requests end up being as batchy as you might imagine, and the 404 node_timeout thing was really about making subsequent requests after you select your source, the async pile always limited you to having replica count in fligth at one time03:16
notmynameI hadn't sussed out the 404 edge case you're talking about yet. you're way ahead of me03:17
claygnotmyname: i think matt already fixed it03:17
mattoliverauclayg has spoken... do you guys ever sleep?03:17
notmynameok, way way ahead of me ;-)03:17
notmynamemattoliverau: heh, I'm at home03:18
notmynameclayg: and your family just left my house, so you should head that way too ;-)03:18
notmynamemattoliverau: I'm just happy to be in front of IRC at some time when we're both awake and I'm not in some meeting ;-)03:18
notmynamemattoliverau: it's only about 7:20pm here03:19
mattoliveraunotmyname: same here :) but LCA is coming up soon, so we can add beer to the mix ;)03:19
notmynamewhat could go wrong?!03:19
mattoliverauwe solve all the things!03:19
mattoliverauclayg: I've been working on a baked in container sharding approach (cause I didn't believe in holidays apparanetly) based on what we talked about at summit, once I flesh it out some more I'd love if you could take a gander to point and laugh and my failings :)03:21
claygheh03:21
claygmattoliverau: maybe a spec would better for hashing out some of the highlevel stuff, unless you just prefer to type up the code and see what sticks... did your reverse listing thing ever merge?  I know everyone was pretty down on the filter by dates and content-types and such?03:22
claygmattoliverau: I think it was notmyname that said that things like the versioned objects middleware could acctually use reverse listings with limits as an optimization...03:23
*** gyee has quit IRC03:25
mattoliverauclayg: yeah, I have a braindump I plan to turn into a spec :) but I also like hacking to see if I'm talking nonsense :P03:25
mattoliverauthe reverse listings is good (?), but not merged. Sitting there without reviews, I'd better poke it and make sure is actaully still works. The other releted patch was just extra stuff that people mentioned would be good in passing in reivews... but aren't indexed, so I think that change can probably go bye byes, I think it's soon to be in the abandoned list if it isn't already :)03:28
claygmattoliverau: well wtf has the reverse listing been showing up on my review dashboard...03:28
notmyname /kidswerescreaminginthebathtub03:29
notmyname /wifewasyellingformetoo03:29
notmynameclayg: ya, I want to play with the dashboard tools some to see what I can do to make a better one :/03:30
mattoliverauclayg: its a magic change apparently, it's quite old, I might rebase it which might bring it more life :)03:30
notmynamemattoliverau: http://littlemexico.co.nz advertises "the largest collection of tequila in Auckland"03:30
claygomg i still have kota's patch on my list too!03:30
mattoliveraunotmyname: nice, sounds like a place that should be visited ;)03:31
clayga'ight i'm offline for a bit03:31
mattoliveraunotmyname: mikal has organised an openstack ATC meetup on the Sunday before LCA (I probably wont arrive in NZ until sunday arvo I think [still haven't got my flights])03:32
mattoliverauclayg: night.. unless you come back :)03:33
*** tellesnobrega_ has quit IRC03:33
*** sungju has quit IRC03:34
claygmattoliverau: if concurrent reads and inflight > nodes: concurreny else node maybe?03:35
claygidk either way is probably fine03:35
mattoliverauoh yeah, though inflight < nodes would work better :P03:37
*** Masahiro has quit IRC03:38
notmynamemattoliverau: ya, I land sunday early am, and I registered for the meetup. I likely go03:43
notmyname*I'll likely go03:44
*** Masahiro has joined #openstack-swift03:44
mattoliverauI will too, as I have registered for it, but I may be late.. depending on flights03:45
notmynamemattoliverau: nice. that restaurant is right next to the uni and walking distance from my hotel03:45
notmynamemattoliverau: are you staying on campus or on a hotel?03:46
notmynameI opted for a hotel this time03:46
mattoliveraunotmyname: I think us Aussie rackers are planning on staying at some serviced apartments somewhere close by. So the hotel route as well :)03:47
notmynamenice03:47
notmynamealthough I think part of the "charm" of LCA is the dorm housing, after 2 years I figured I'll get a hotel and have my own bathroom this time :-)03:48
mattoliveraunotmyname: lol, I totally agree, out of the last 6 years of LCA I've been too, I've done hotel only once, cause the dorms are fun. :)03:49
*** Masahiro has quit IRC03:49
notmynamemattoliverau: thanks for helping me understand the high-level of the concurrent reads. and thanks for working on it03:51
openstackgerritJeremy Stanley proposed openstack/python-swiftclient: Workflow documentation is now in infra-manual  https://review.openstack.org/13938403:51
openstackgerritJeremy Stanley proposed openstack/swift: Workflow documentation is now in infra-manual  https://review.openstack.org/13939303:52
openstackgerritJeremy Stanley proposed openstack/swift-specs: Workflow documentation is now in infra-manual  https://review.openstack.org/13939403:52
mattoliveraunotmyname: my pleasure, it was fun and was interesting to work with a more core part of the swift code :)03:52
notmynameI'm out for a while. good night03:53
mattoliverauLooks like fungi is patching infra-manual which touches our docs :)03:53
mattoliveraunotmyname: kk, night, thanks for keeping me company in channel :)03:54
*** addnull has joined #openstack-swift03:58
*** Masahiro has joined #openstack-swift03:59
*** ppai has joined #openstack-swift04:11
*** ahonda has quit IRC04:15
*** ahonda has joined #openstack-swift04:22
openstackgerritMatthew Oliver proposed openstack/swift: Workflow documentation is now in infra-manual  https://review.openstack.org/13939304:30
openstackgerritMatthew Oliver proposed openstack/python-swiftclient: Workflow documentation is now in infra-manual  https://review.openstack.org/13938404:33
mattoliverau^^ Fixed up the url link and some documentation on behalf of fungi04:34
*** sungju has joined #openstack-swift04:48
*** addnull has quit IRC04:57
*** addnull has joined #openstack-swift05:12
*** Masahiro has quit IRC05:12
*** Masahiro has joined #openstack-swift05:27
*** kopparam has joined #openstack-swift05:37
mattoliverauRight, well it's friday arvo, so I'm going to take an early mark, have a great weekend all.05:37
*** addnull has quit IRC05:49
openstackgerritHisashi Osanai proposed openstack/swift: Fix the behavior of swift-ring-builder list_parts before rebalance  https://review.openstack.org/13952306:00
openstackgerritHisashi Osanai proposed openstack/swift: Fix the behavior of swift-ring-builder list_parts before rebalance  https://review.openstack.org/13952306:09
*** kopparam has quit IRC06:28
*** kopparam has joined #openstack-swift06:30
*** Masahiro has quit IRC06:35
*** Masahiro has joined #openstack-swift06:39
*** reed has quit IRC06:39
*** addnull has joined #openstack-swift06:40
*** sungju has quit IRC06:41
*** openstackgerrit has quit IRC06:49
*** openstackgerrit has joined #openstack-swift06:49
*** zul has quit IRC07:14
*** addnull has quit IRC07:20
*** addnull has joined #openstack-swift07:26
*** SkyRocknRoll has joined #openstack-swift07:44
*** SkyRocknRoll has joined #openstack-swift07:44
*** SkyRocknRoll has quit IRC07:48
*** SkyRocknRoll has joined #openstack-swift07:48
*** SkyRocknRoll has joined #openstack-swift07:48
*** tellesnobrega_ has joined #openstack-swift08:00
*** tellesnobrega_ has quit IRC08:04
*** zul has joined #openstack-swift08:07
*** rledisez has joined #openstack-swift08:18
*** bkopilov has quit IRC08:20
*** bkopilov has joined #openstack-swift08:22
*** Masahiro has quit IRC08:36
*** kopparam has quit IRC08:39
*** oomichi has quit IRC08:41
*** Masahiro has joined #openstack-swift08:47
openstackgerritHisashi Osanai proposed openstack/swift: Fix the behavior of swift-ring-builder list_parts before rebalance  https://review.openstack.org/13952308:52
*** ppai has quit IRC08:53
*** jordanP has joined #openstack-swift09:00
*** sluo_wfh has quit IRC09:02
*** kopparam has joined #openstack-swift09:05
*** sluo_wfh has joined #openstack-swift09:14
*** jistr has joined #openstack-swift09:14
*** sluo_wfh has quit IRC09:20
*** addnull has quit IRC09:29
*** dmorita has quit IRC09:32
*** tellesnobrega_ has joined #openstack-swift09:35
*** foexle has joined #openstack-swift09:45
*** tellesnobrega_ has quit IRC10:00
*** kopparam has quit IRC10:04
openstackgerritMerged openstack/python-swiftclient: Workflow documentation is now in infra-manual  https://review.openstack.org/13938410:12
*** aix has joined #openstack-swift10:16
*** acoles_away is now known as acoles10:19
*** Masahiro has quit IRC10:33
*** haomaiwang has quit IRC10:37
*** kopparam has joined #openstack-swift10:56
*** Masahiro has joined #openstack-swift11:34
*** Masahiro has quit IRC11:39
*** sandywalsh has quit IRC12:02
*** sandywalsh has joined #openstack-swift12:05
*** kopparam has quit IRC12:14
*** dmsimard_away is now known as dmsimard12:18
*** mahatic has joined #openstack-swift12:24
*** mahatic has quit IRC12:25
*** mahatic has joined #openstack-swift12:28
*** ahonda has quit IRC12:29
*** kopparam has joined #openstack-swift12:42
*** SkyRocknRoll has quit IRC12:53
*** Masahiro has joined #openstack-swift13:08
*** Masahiro has quit IRC13:13
mandarineGood morning13:24
mandarineI think I have a question about "partition power" when creating the ring files13:25
mandarineI know of http://rackerlabs.github.io/swift-ppc/ to calculate the right number ... BUT how comes it doesn't depend on the size of my drives ?13:25
mandarineI have 8 drives and ~3.5TB per device.13:26
mandarineI am about to put a partition power to 20 ... but I'm not even sure13:29
ahalemorning, partition power is more about prtitions of the md5 hash space than disk partition size13:31
mandarineYeah, but it's used as a unit for replication and I'm not much into rsyncing 5Go each time I have to do a partition replica ?13:36
mandarineGB*13:37
*** miqui_ has joined #openstack-swift14:04
tdasilva_mandarine: I believe that's where the device's weight comes in, check out this link: http://docs.openstack.org/developer/swift/overview_ring.html14:11
mandarineThe weight is relative to the number of partitions on a specific device. But the number of partition of the cluster is defined while creating the ring.builder file with the <part_power> argument14:15
mandarineI shall put a 20 in here, even if I'm not quite sure.14:15
openstackgerritThiago da Silva proposed openstack/swift: versioned writes middleware  https://review.openstack.org/13434714:16
jbonjeanCould someone tell me if this patch would some side effects http://pastebin.com/4nvaRvL8 ? Basically it makes the proxy treat connection timeouts as errors14:47
jbonjeanI don't understand why it is not the default behaviour14:48
*** gfidente has joined #openstack-swift14:54
gfidentehi guys, pardon the stupid question14:54
gfidenteis there something I can use to monitor the status of a cluster as in how many nodes are making up a cluster, which service is running on which node or things like that?14:55
gfidente(something bundled with swift I mean)14:55
*** Masahiro has joined #openstack-swift14:57
*** Masahiro has quit IRC15:01
swifterdarrellnotmyname: fyi https://bugs.launchpad.net/python-swiftclient/+bug/139967815:30
glange_gfidente: nothing like that bundled with swift15:32
gfidenteglange_, I am seeing something interesting with swift-ring-builder15:33
gfidentebut it is not good for monitoring I suppose15:33
*** reed has joined #openstack-swift15:34
glange_with the ring builder you are "telling" swift about the systems that make up a cluster15:35
gfidenteyeah but it can show that too15:40
gfidentethe nodes making up a ring at least15:41
glange_true15:42
ahalerecon is probably the closest thing in swift core to something that returns info about nodes in the cluster15:43
gfidenteI'll check that too, thanks15:44
*** mahatic has quit IRC15:46
*** mahatic_ has joined #openstack-swift15:46
notmynamegood morning16:07
mahatic_good morning16:11
*** rdaly2 has joined #openstack-swift16:23
notmynamemahatic_: how's it going? do you have any questions about what you're working on?16:31
mahatic_notmyname, hey. I was not working for the past couple of days. Had to wrap up some things at work. I'm done with that now. So back here :)16:34
notmynamemahatic_: great!16:35
notmynamemahatic_: do you want to schedule an official "office hours" time every week, or would you prefer to leave it ad-hoc for now? what will work best for you?16:37
openstackgerritOpenStack Proposal Bot proposed openstack/python-swiftclient: Updated from global requirements  https://review.openstack.org/8925016:40
*** mahatic_ has quit IRC16:41
*** mahatic_ has joined #openstack-swift16:41
*** Masahiro has joined #openstack-swift16:46
*** Masahiro has quit IRC16:50
*** sfineberg has joined #openstack-swift17:03
*** erlon has quit IRC17:09
*** rledisez has quit IRC17:18
*** mahatic_ has quit IRC17:23
*** mahatic_ has joined #openstack-swift17:23
*** pberis has joined #openstack-swift17:23
*** mahatic_ has quit IRC17:23
*** mahatic_ has joined #openstack-swift17:24
mahatic_notmyname, the coming up Wednesday, 10th, I have a plan to travel that night to my hometown, is it possible we shift the 1 hour sometime in the week?17:25
notmynamemahatic_: yes. if we don't talk before then, I'll find you later17:29
mahatic_notmyname, alright, you'll find me before and after :)17:30
*** jordanP has quit IRC17:30
*** foexle has quit IRC17:35
*** jistr has quit IRC17:45
*** tellesnobrega_ has joined #openstack-swift17:54
*** david-lyle has joined #openstack-swift17:57
*** tellesnobrega_ has quit IRC17:59
ctennisIs there a reason the replicators scan over all suffixes and rsync them by individual name vs. just rsyncing the partition directory and letting it grab the suffixes as part of the sync process?18:11
notmynamectennis: there can be a lot of objects in a partition (and suffix) directory, so syncing suffix dirs allows dividing up the work into smaller chunks18:14
ctennisok, I don't see where it actually divides it up though18:15
peluse__ctennis, look un update() where the suffixes list is created based on differnces in hashes.pkl files, just the subset that different is sync18:16
peluse__ctennis, FYI I'm in the middle of doing the EC reconstructor and picking these things apart so its fresh if you wanna walk through any of it w/me :)18:17
ctennisok, I see it in update now..looks like update_deleted doesn't use that though?18:17
peluse__udpate_deleted moves partitions that don't belong on the current node (not individual suffix dirs)18:18
ctennisat least, it just uses the whole suffix list I mean18:18
peluse__so you're reading it correctly... when moving data is part by part, when sync'ing between nodes that are supposed to have the same copy its suffix dir by suffix dir18:19
ctennispeluse__: right..however, if we're going to sync the whole partition and could avoid looping over all of the suffixes, it would help performance there18:19
peluse__ctennis, which loop are you looking at?18:19
ctennispeluse__: I'm diving into this a bit after fighting a customer cluster who had way out of whack replication18:19
ctennispeluse__: "tpool_get_suffixes"18:20
notmynameline 189 I think18:20
peluse__I'm looking at my EC branch, which file/function?18:20
peluse__ahh, thats not a loop.  that's trying to avoid moving stuff that's not a suffix dir18:21
peluse__well, its a list comprehensision so yeah its proc time...18:21
ctennispeluse__: I know, but os.listdir(path) can be very expensive on a burdened system18:21
peluse__one sec...18:21
*** kopparam has quit IRC18:21
notmynamectennis: "is very expensive." FTFY ;-)18:22
*** kopparam has joined #openstack-swift18:22
ctennisOn this one system, where there should be about 16k partitions on the node spread across 36 disks there were almost 600,000.  the replicator would take almost 6 hours just to startup.18:22
ctennisI know that doesn't impact this particular place, it just has me looking for some places to improve the cycle times in general18:23
*** gyee has joined #openstack-swift18:23
peluse__heh, so I've changed some things on the branch I'm looking at.  let me pull up master and refresh my memory on a few things... give me a couple of mins18:24
peluse__ctennis, and your customer is using rsync right?18:24
ctennispeluse__: yeah18:25
*** gyee has quit IRC18:25
*** gyee has joined #openstack-swift18:25
*** rdaly2 has quit IRC18:27
*** rdaly2_ has joined #openstack-swift18:27
peluse__ctennis, so yeah if you look at rsync() it takes a suffix list that it loops on which is needed for how update() works so that's likely why update_delete() is building a list and passing it in.  Seems like there could be an oppt to have update_delete() use the part dir instead with not too many tweaks18:27
peluse__opportunity that is (not sure where oppt came from)18:28
ctennisok sounds good peluse__ - I'm going to try and see if there's an real gain or advantage to doing it that way, I would think rsync may be a little more optimal by specifying one source argument vs potentially hundreds.18:28
ctennisbut certainly I think we'd benefit by not doing the os.listdir if we can help it there18:29
peluse__ctennis, certainly worth looking into w/what I know about it at least :)  The EC stuff will always use ssync so I may jot down a note to look clser there once the rest of it is working... cool18:29
*** peluse__ is now known as peluse18:31
*** ChanServ sets mode: +v peluse18:31
*** kopparam has quit IRC18:33
*** Masahiro has joined #openstack-swift18:35
*** gyee has quit IRC18:35
*** gyee has joined #openstack-swift18:38
*** gyee has quit IRC18:38
*** gyee has joined #openstack-swift18:39
*** Masahiro has quit IRC18:39
openstackgerritAlistair Coles proposed openstack/swift: Update container on fast-POST  https://review.openstack.org/13538018:53
openstackgerritAlistair Coles proposed openstack/swift: Make ssync compatible with fast-post meta files  https://review.openstack.org/13849818:53
acolesclayg: ^^ mainly backfilling tests for ssync patch, next i will add the triple timestamp stuff18:54
*** acoles is now known as acoles_away18:58
*** rdaly2_ has quit IRC18:58
*** lpabon has joined #openstack-swift19:00
*** nshaikh has joined #openstack-swift19:01
*** gfidente has quit IRC19:10
peluseclayg, I'm taking off for a liquid lunch but FYI the changes we talked about are looking pretty cool... excited to spend some time this weekend or Mon on them...19:10
*** tellesnobrega has quit IRC19:29
openstackgerritThiago da Silva proposed openstack/swift: versioned writes middleware  https://review.openstack.org/13434719:32
*** gyee has quit IRC19:34
*** zaitcev has joined #openstack-swift19:44
*** ChanServ sets mode: +v zaitcev19:44
claygpeluse: acoles_away: ok, i'll take a look as soon as I can - maybe torgomatic could peek too19:49
*** gordc has joined #openstack-swift20:07
gordchad a random q about proxy server... in icehouse, the etc/swift/proxy-server.conf has a pipeline like this: http://logs.openstack.org/42/130142/5/check/check-tempest-dsvm-full/e732515/logs/etc/swift/proxy-server.conf.txt.gz but for some reason, in actual proxy log, it's noticeably different: http://logs.openstack.org/42/130142/5/check/check-tempest-dsvm-full/e732515/logs/screen-s-proxy.txt.gz20:09
gordcis the pipeline not taken from proxy-server.conf in icehouse?20:09
notmynamegordc: it would seem that there is some other config file that it was actually started with.20:14
notmynamebut let me check one thing20:14
gordcnotmyname: cool cool. i could just be misunderstanding it and the logging is just renaming middlewares when it prints20:16
notmynamegordc: ya, that's what I was checking. that is possible20:16
openstackgerritJesse J. Cook proposed openstack/python-swiftclient: Do not override specified URL or token  https://review.openstack.org/13972820:19
notmynamegordc: I think I know what's happening. testing20:20
*** lpabon has quit IRC20:21
gordcnotmyname: awesome. thanks for looking at it.20:21
*** Masahiro has joined #openstack-swift20:23
notmynamegordc: nope. not what I thought20:24
notmynamebut yeah, it seems like it might be the names getting printed differently. but I couldn't duplicate that in my saio20:25
gordc:( i'll try debugging it. just seemed really strange that they were different.20:26
*** nshaikh has left #openstack-swift20:26
notmynamegordc: the changes are cache->memcache, keystoneauth->big, ceilometer->swift, and proxy-server->proxy20:26
*** Masahiro has quit IRC20:27
gordcnotmyname: hmm.. yeah i'll take a look and see why those changed...20:28
*** NobodyCam has joined #openstack-swift20:28
openstackgerritMerged openstack/swift: Fix the behavior of swift-ring-builder list_parts before rebalance  https://review.openstack.org/13952320:29
NobodyCamgood afternoon all, I have a question: can I set Temp-url-key in a conf file vs the "post -m" example20:30
notmynameNobodyCam: no, it's stored on the account metadata (2 keys actually, so you can do rotations)20:30
NobodyCam:) thank you :)20:30
*** rdaly2 has joined #openstack-swift20:38
*** tellesnobrega_ has joined #openstack-swift20:43
*** tellesnobrega_ has quit IRC20:43
*** cdelatte has joined #openstack-swift21:05
*** cdelatte has quit IRC21:28
claygmattoliverau: latest changeset on concurrent reads looks pretty good!  I think I'll probably have a diff on the unittests, but you may have the right idea.21:33
claygtorgomatic: you were asking about fun ones?  https://review.openstack.org/#/c/117710/1421:33
claygtdasilva_: thanks for doing all those reviews as of late!  I had remembered talking to notmyname that one usecase of reverse container listings would be something like object versions, so when I remembered I've been needing to look at https://review.openstack.org/#/c/120709/ I thought of you too!21:36
*** kopparam has joined #openstack-swift21:57
*** gordc has left #openstack-swift21:57
*** gyee has joined #openstack-swift22:03
*** rdaly2 has quit IRC22:04
*** Masahiro has joined #openstack-swift22:12
mattoliverauclayg: cool, thanks I look forward to seeing the diff :)22:15
*** Masahiro has quit IRC22:17
claygmattoliverau: don't hold your breath/you should badger torgomatic for a review22:26
torgomaticbadger badger badger xattr22:29
*** kopparam has quit IRC22:29
mattoliverautorgomatic: badger badger badger concurrent reads :p22:31
torgomaticbadgebabadgeradgrer22:31
notmynamesnake!22:31
mattoliverauLol, you tube has ruined us all :p22:33
notmynamemattoliverau: did you see that youtube had a video that broke the 32 bit limit for the views counter?22:34
mattoliverauHaha, really! Awesome, geeky awesome, but awesome none the less ;p22:36
claygnotmyname: I thought that was sort of a myth, that they went to 64bit ints long before psy's video ever acctually rolled over?22:38
notmynamedon't confuse us with facts!22:38
notmynameactually I have no idea22:38
notmynamesaw it somewhere last week maybe?22:39
notmynameclayg: nat according to BBC (and the liked official youtub google+ page) http://www.bbc.com/news/world-asia-3028854222:40
notmyname"a couple months ago" is when they fixed it22:41
notmynamewow. doesn't look like I can type22:41
notmyname*the *not *linked22:41
claygoh yeah the bbc knows22:41
mattoliverauLol22:41
mattoliverauSorry for slow responses, is Saturday and I'm in the middle of an archery field. Yay tech22:42
notmynamemattoliverau: maybe not the "middle"?22:42
claygtorgomatic: can more than one policy use the same instance of an obj_ring?  I guess you could copy object to object-1 if you really wanted the same nodes, but under the hood I think the StoragePolicyCollection is going to have two different Ring instances in hand...22:43
notmynamecool! I figured out how to set my calendar to have the right time for the swift team meetings, even with the time change shenanigans22:43
torgomaticclayg: yeah, they'll be different instances22:43
notmynameif your calendar doesn't allow setting an event in UTC, then set it to Icelandic time. they are GMT+0 and don't do a time change22:44
mattoliverauWell not in the middle except for when collecting arrows... Which is when I ignore irc :p22:44
notmyname(and then subscribe to icelandic news and learn icelandic to see if they start observing some daylight savings time thing)22:44
mattoliverauLol, yeah that's much easier :p I just remember its either 5am or 6am :p22:47
claygnotmyname: which do you think will happen first a) everyone uses metric system b) everyone uses UTC?22:48
notmynameUTC. who doesn't use UTC on their servers today?22:48
notmynameI'm mean, honestly?22:49
claygyeah... god that's sad22:49
claygmattoliverau: you bushmen use metric right?  is the us the only hold out?22:49
notmynameclayg: https://twitter.com/joe_jag/status/51004864648289484822:49
notmyname^ what with the recent news of NASA sending humans to Mars...22:50
claygnotmyname: so is UTC the same on mars or only within the light cone?22:50
notmynamewell, it calls itself "universal coordinated time". so I'm guessing it's got to be for everyone everywhere. it says so right there in the name!22:51
notmynamealso, the phrase "light cone" is cool22:51
claygnotmyname: well maybe that's only between universes that can coordinate with entangled particles - otherwise I just don't see how it would even be possible22:52
notmynameheh22:52
notmynameclayg: ya, UTC is dependent on a 24 hour day. not true on mars22:52
* notmyname proposes s/UTC/ETC/g22:52
mattoliverauYup, metric all the way, makes life so much easier!22:52
notmynameheh22:54
notmyname"This abbreviation arose from a desire by the International Telecommunication Union and the International Astronomical Union to use the same abbreviation in all languages. English speakers originally proposed CUT (for "coordinated universal time"), while French speakers proposed TUC (for "temps universel coordonné"). The compromise that emerged was UTC"22:54
*** tkay has joined #openstack-swift22:59
torgomaticanyone have a system with a weird filesystem on it that can test something for me? like ZFS, UFS2... basically not XFS and not ext423:02
torgomaticbasically, run this https://gist.github.com/smerritt/a415008402d82b03ceb4 and tell me what it says23:03
openstackgerritMerged openstack/swift: Workflow documentation is now in infra-manual  https://review.openstack.org/13939323:05
torgomaticnotmyname: don't you have some ZFS thingy around somewhere?23:05
notmynametorgomatic: running it now on that23:05
torgomatic:)23:05
*** dmsimard is now known as dmsimard_away23:07
openstackgerritClay Gerrard proposed openstack/swift: ec get for the lolz  https://review.openstack.org/13975223:07
notmynametorgomatic: I just gotta figure out the best way to get xattr installed on open illumos23:07
torgomaticnotmyname: ooh... yeah23:07
notmynametorgomatic: hey remember that time (yesterday) when clayg was talking about how hard EC get would be and it would take a long time for him to submit a patch about it?23:08
torgomaticnotmyname: no, the gin helps with that23:08
*** quack_quack_ has joined #openstack-swift23:08
claygnotmyname: this one is only for the lolz23:08
claygbut the md5 matched so I say ship it!23:08
claygwhere ship it ~= type git review and get read for the party tonight!23:09
claygwhoot whoot!23:09
notmynametorgomatic: I'm going to file this under "No". xattr depends on cffi, which means I'd have to figure out how to build that on this crazy old system23:15
torgomaticnotmyname: fair enough. thanks for trying!23:16
notmynametorgomatic: FWIW, on OSX (which I'm sure you already "tested"), FS supports really big extended attributes (over 1 MiB)23:17
notmynamebriancline: do you have any ZFS boxes around? to test out torgomatic's thing?23:17
notmynametorgomatic: what have you tested so far?23:19
torgomaticnotmyname: got XFS and ext4. I have a vagrant freebsd box attempting to come up, but the base box download is slooooooowwwww23:20
torgomaticso that'll get me ZFS, I believe23:20
torgomaticI figure that XFS, ZFS, ext4, and UFS2 are about all anyone will really care about, and I'm not sure about UFS223:21
* notmyname gets nervous when asked "How many lines of code make up Swift?"23:23
notmyname"enough"?23:23
notmynameI wonder if the only reason people track line count is because all our editors have the number conveniently printed next to every line. so someone looked over a dev's shoulder at one point and though it was a god thing to track23:26
torgomaticwell, you can't count quality, but you can count lines23:31
notmynameand more importantly, you can count how many change23:32
*** mahatic_ has quit IRC23:46

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