Friday, 2014-06-13

openstackgerritSamuel Merritt proposed a change to openstack/swift: Fix SLO test with old simplejson  https://review.openstack.org/9980500:06
torgomaticclayg: so after I s/json.JSONDecodeError/ValueError/g, the probetests are all passing for me (one skip, not sure what it is)00:16
*** matsuhashi has joined #openstack-swift00:19
portantetorgomatic: did you look at the stack trace I posted above?00:26
torgomaticportante: nope00:27
portantethe one where file not found for /tmp?00:27
torgomaticyeah, have you got /srv/1/node/sdb1/tmp/ ?00:27
portantels -ld /srv/*/node/*/tmp: No such file or directory00:29
portantebut all tmp-1 exist00:29
torgomaticwacky; isn't the object server supposed to create those if it needs to?00:29
torgomaticoh, so it's using the wrong tempdir00:29
portanteyes00:29
torgomaticwelp00:29
portantethe code has a hard-coded 0 in async_update() call in delete_at I believe00:30
portantebut I was not sure I understood the code right00:30
portantethe code used to not care what tmpdir it uses00:31
torgomaticyeah, it used to share quarantine and tmp dirs between all policies, but we changed that00:34
torgomaticthe quarantine one is certainly a good idea IMO; if stuff's mistakenly quarantined, I want to know where to put it back to00:34
torgomaticthe tmp one, I dunno. I have no strong opinion either way.00:34
claygtorgomatic: well either way, the change that you and peluse_ worked on didn't do the get_policy_dir bits for the tmp dir and it only showed up for me in probetests00:36
claygportante: but even in the traceback you pasted it looked like the call to get_policy_dir was in there, unless i'm mis-reading?00:36
claygtorgomatic: you skip is probably container-sync - and you should set that up00:36
torgomaticI don't see any failures, but maybe that's because I have a policy 0 defined00:36
claygtorgomatic: i thought portante did as well?  i'm assuming he'd try to get something working before he tried to break it - dunno if he fixed the 2x ring tho - peluse_ confirmed that's not gunna work00:37
*** haomaiwang has joined #openstack-swift00:38
portanteclayg: yes, but delete_at appears to hard-code a 0 in the call to async_update()00:39
portanteclayg, torgomatic: i have the storage policies defined as in the SAIO, so a 0 and a 100:40
torgomaticportante: hm, maybe just bad luck for you then? something something test ordering?00:40
portanteI have resetswift multiple times and get the same thing though00:40
portantesomething else in my environment that is leaking into the tests?00:41
portantefukshima?00:41
portantesomething I ate?00:41
torgomaticsure, maybe it's the order that the test files come out of readdir() so they run in a different order than on my box00:41
torgomaticdunno00:41
portantetorgomatic: I though the tests were sorted?00:43
portanteby name that is00:43
* torgomatic is not a nose expert00:43
*** dmorita has joined #openstack-swift01:16
*** nosnos has joined #openstack-swift01:21
*** NM has joined #openstack-swift01:29
*** NM has quit IRC01:35
*** mkollaro has quit IRC01:39
*** haomaiwang has quit IRC01:46
*** haomaiwa_ has joined #openstack-swift01:53
*** kajinamit has joined #openstack-swift01:54
*** haomaiwa_ has quit IRC01:57
claygportante: yeah system accounts are always policy 0, hell most of them don't even have any "real" objects so it doesn't matter - there's not a comment that says that?02:00
claygportante: no, not sorted by name, nose is all pretty random like that02:04
claygportante: but the tests themselves shouldn't care the order they're run in :)02:04
claygportante: oh oh oh, the async pickle for the delete-at - christ, yeah i'll try to track that down - nice catch!02:05
*** nsquare has quit IRC02:19
claygacoles: so I think the fixed with hex offset will work fine for the content-type updates, but I agree that the offset there should be based on the x-timestamp of the POST02:26
claygacoles: you just need to convert the x-timestamp of the post to an integer and then we need to pick a maximum width to maintain string order sorting02:28
claygacoles: but I think storing the timestamp offset string as a decimal is wasteful of our bits when we have hex just *right there* ;)02:31
openstackgerritKota Tsuyuzaki proposed a change to openstack/swift: Efficient Replication for Distributed Region  https://review.openstack.org/9982402:39
openstackgerritKota Tsuyuzaki proposed a change to openstack/swift: Efficient Replication for Distributed Regions  https://review.openstack.org/9982402:44
*** zhiyan_ is now known as zhiyan02:45
*** dmorita has quit IRC02:59
claygacoles: if you do int(post.ts) - int(data.ts) you get about 136 years out of 8 hex digits - but you loose metadata update resolution below a second which seems sorta crappy03:01
claygacoles: if you take resolution out to a centi-microsecond (which seems not terrible) you only get like a month to do a POST before you have to overflow into the datafile timestamp - which is cirtainly long enough that you're outside of the consitency window and overflowing into the datafile timestamp would probably still end up working out as correct, but you loose the transparency of the update03:04
claygOTOH if we take another 4 bytes and store 12 digit offsets you could have deca-microsecond resolution for 89 years before overflowing into the datafile timestamp and 10 times that if you go with centi-microseconds03:06
claygso i'm inclined to bump the width on the resolution out to 12 digts - but I think we should leave the math up to the update code, and go with fixed with hex for the data format03:09
* clayg briefly ponders an integer serialization encoding that would still be string sortable and uses more ascii chars03:10
*** nosnos has quit IRC03:16
*** gyee has quit IRC03:19
claygacoles: so if we go with a 64 digit base instead of 16, we could near century deca-microsecond resolution out of 8 digts - i recommend an alphabet of digits + letters + '$&' :D03:35
*** nosnos has joined #openstack-swift03:52
claygoh nm, & is a terrible character to copy and paste around - maybe %03:53
clayg... or we could just use 12 hex digts03:53
*** openfly has quit IRC03:59
*** matsuhas_ has joined #openstack-swift04:03
*** matsuhas_ has quit IRC04:04
*** matsuhas_ has joined #openstack-swift04:05
*** matsuhashi has quit IRC04:05
*** matsuhas_ has quit IRC04:12
*** matsuhashi has joined #openstack-swift04:13
*** madhuri has quit IRC04:16
*** haomaiwa_ has joined #openstack-swift04:31
*** haomaiw__ has joined #openstack-swift04:33
*** haomaiwa_ has quit IRC04:37
*** psharma has joined #openstack-swift04:41
*** kashyapk has joined #openstack-swift04:41
openstackgerritA change was merged to openstack/swift: Add debug logging to container sync requests  https://review.openstack.org/9591104:47
*** zhiyan is now known as zhiyan_05:06
*** ppai has joined #openstack-swift05:08
*** kashyapk has quit IRC05:10
*** kashyapk has joined #openstack-swift05:10
*** zhiyan_ is now known as zhiyan05:13
*** mkollaro has joined #openstack-swift05:32
*** nthacker_ has joined #openstack-swift05:39
*** nthacker has quit IRC05:42
*** kashyapk has quit IRC05:43
*** kashyapk has joined #openstack-swift05:44
*** zaitcev has quit IRC05:49
*** matsuhashi has quit IRC05:52
*** matsuhashi has joined #openstack-swift05:57
*** openfly has joined #openstack-swift05:57
*** zhiyan is now known as zhiyan_06:32
*** jamiehannaford has joined #openstack-swift06:48
*** jamiehan_ has joined #openstack-swift06:52
*** jamiehannaford has quit IRC06:54
*** zhiyan_ is now known as zhiyan07:00
*** kashyapk has quit IRC07:01
*** kashyapk has joined #openstack-swift07:02
*** kashyapk has quit IRC07:06
*** jamiehan_ has quit IRC07:11
*** jamiehannaford has joined #openstack-swift07:12
*** jamiehan_ has joined #openstack-swift07:21
*** haomaiw__ has quit IRC07:22
*** haomaiwang has joined #openstack-swift07:23
*** jamiehannaford has quit IRC07:24
*** haomaiwang has quit IRC07:27
*** jamiehan_ has quit IRC07:29
*** jamiehannaford has joined #openstack-swift07:30
*** mkollaro has quit IRC07:35
*** matsuhas_ has joined #openstack-swift07:36
*** matsuhashi has quit IRC07:36
*** jamiehan_ has joined #openstack-swift07:39
*** jamiehannaford has quit IRC07:39
*** kashyapk has joined #openstack-swift07:41
*** zhiyan is now known as zhiyan_08:10
*** zhiyan_ is now known as zhiyan08:30
*** haomaiwa_ has joined #openstack-swift08:34
*** haomaiw__ has joined #openstack-swift08:37
*** haomaiwa_ has quit IRC08:38
*** haomaiw__ has quit IRC08:41
*** haomaiwa_ has joined #openstack-swift08:42
*** kashyapk has quit IRC08:43
*** kashyapk has joined #openstack-swift08:43
*** zhiyan is now known as zhiyan_08:52
*** mmcardle has joined #openstack-swift08:52
*** matsuhas_ has quit IRC08:57
*** zhiyan_ is now known as zhiyan09:00
*** zhiyan is now known as zhiyan_09:09
*** d0ugal has quit IRC09:09
*** d0ugal has joined #openstack-swift09:10
*** zhiyan_ is now known as zhiyan09:10
*** matsuhashi has joined #openstack-swift09:12
openstackgerritMatthew Oliver proposed a change to openstack/swift: When a filesystem does't support xattr return a 507  https://review.openstack.org/9988309:21
mattoliverauWell I worked late, time to call it a day. Have a great weekend all. notmyname I hope your recovering well.09:26
*** mkerrin has quit IRC09:26
*** mkerrin has joined #openstack-swift09:33
*** matsuhashi has quit IRC09:43
*** kajinamit has quit IRC09:49
*** itarchitectkev has joined #openstack-swift09:51
*** haomaiwa_ has quit IRC09:52
itarchitectkevHey folks. An AWS announcement about S3 and encryption came my way today and naturally I'm getting asked about Swift's capabilities/developments in at-rest encryption. I saw Mirantis taking a stab at this a while back, where's Swift's stance on this?09:52
*** haomaiwa_ has joined #openstack-swift09:54
itarchitectkev(noting that encryption in S3 has been there for a while of course!)09:55
*** ccorrigan has quit IRC09:57
ahaleimo its pointless to do encryption like that, if you want to encrypt data do it before giving it to a third party09:57
ahalebut i heard barbican project believe otherwise and were working on something, or something09:58
ahaledunno what the actual swift stance is though09:58
itarchitectkevyeah, traditionally doing it in client before uploading has been ok, some folks seem to want this more transparent. users, who'd have them eh?10:03
ahalei guess if they care more about a checkbox on a security list and less about the reality then.. its a great idea10:03
*** zhiyan is now known as zhiyan_10:06
*** haomai___ has joined #openstack-swift10:06
itarchitectkevIt's more than that. Policy enforcement can be done server side, and not relying on a client. There are lots of reasons for this.10:06
*** omame has joined #openstack-swift10:06
*** haomaiwa_ has quit IRC10:09
*** NM has joined #openstack-swift10:15
*** mkollaro has joined #openstack-swift10:15
*** haomai___ has quit IRC10:21
*** haomaiwang has joined #openstack-swift10:21
*** NM has quit IRC10:22
*** haomaiwang has quit IRC10:22
*** haomaiwa_ has joined #openstack-swift10:23
*** haomaiw__ has joined #openstack-swift10:24
*** haomaiw__ has quit IRC10:25
*** kashyapk has quit IRC10:25
*** haomaiwa_ has quit IRC10:25
*** haomaiwa_ has joined #openstack-swift10:26
*** nosnos has quit IRC10:26
*** kashyapk has joined #openstack-swift10:26
*** Longgeek_ has joined #openstack-swift10:27
openstackgerritChristian Schwede proposed a change to openstack/swift: Fix object auditor recon and logging  https://review.openstack.org/9990010:29
*** kashyapk has quit IRC10:30
*** haomai___ has joined #openstack-swift10:32
openstackgerritChristian Schwede proposed a change to openstack/swift: Fix object auditor recon and logging  https://review.openstack.org/9990010:33
*** nosnos has joined #openstack-swift10:34
*** NM has joined #openstack-swift10:34
*** mkollaro has quit IRC10:35
*** haomaiwa_ has quit IRC10:35
itarchitectkevthanks ahale about Barbican. Probably enough for now to stave off some of the customer questions.10:36
*** kashyapk has joined #openstack-swift10:38
*** nosnos has quit IRC10:39
*** haomaiwang has joined #openstack-swift10:40
*** haomaiwang has quit IRC10:41
*** haomai___ has quit IRC10:41
*** haomaiwa_ has joined #openstack-swift10:42
*** NM has quit IRC10:43
*** haomai___ has joined #openstack-swift10:46
*** haomaiwa_ has quit IRC10:46
*** haomaiwang has joined #openstack-swift10:48
*** haomai___ has quit IRC10:51
*** chandan_kumar has joined #openstack-swift10:51
*** mkollaro has joined #openstack-swift10:51
*** NM has joined #openstack-swift10:51
*** kashyapk has quit IRC10:52
*** chandankumar has quit IRC10:52
*** kashyapk has joined #openstack-swift10:52
*** NM has quit IRC10:54
*** chandan_kumar has quit IRC10:56
*** chandan_kumar has joined #openstack-swift10:56
*** kashyapk has quit IRC10:57
*** jamiehan_ has quit IRC11:00
*** kashyapk has joined #openstack-swift11:00
*** NM has joined #openstack-swift11:00
*** jamiehannaford has joined #openstack-swift11:00
*** NM has quit IRC11:07
*** kashyapk has quit IRC11:10
*** kashyapk has joined #openstack-swift11:10
*** kashyapk has quit IRC11:15
*** zul has quit IRC11:36
*** kashyapk has joined #openstack-swift11:41
*** foexle has joined #openstack-swift11:53
*** mmcardle has quit IRC11:56
*** ppai has quit IRC12:04
*** kashyapk has quit IRC12:06
*** jamiehannaford has quit IRC12:15
openstackgerritEamonn O'Toole proposed a change to openstack/swift: Parallel object auditor  https://review.openstack.org/5977812:17
*** jamiehannaford has joined #openstack-swift12:23
*** haomaiwang has quit IRC12:27
*** haomaiwang has joined #openstack-swift12:27
portanteclayg: I did not catch the 0, the probe tests did! :)12:29
*** foexle has quit IRC12:32
*** haomaiw__ has joined #openstack-swift12:35
*** NM has joined #openstack-swift12:36
*** haomaiwang has quit IRC12:38
*** mmcardle has joined #openstack-swift12:42
*** kashyapk has joined #openstack-swift12:55
*** kashyapk has quit IRC12:56
*** kashyapk has joined #openstack-swift12:57
*** itarchitectkev_ has joined #openstack-swift13:15
*** itarchitectkev has quit IRC13:18
*** kashyapk has quit IRC13:21
*** foexle has joined #openstack-swift13:23
acolesclayg: yeah, i thought some more and agree a relative offset from original timestamp should be sufficient for the content-type updates13:28
acolesclayg: so, a 64 base isn't too crazy to code but harder to debug ;)13:30
*** zul has joined #openstack-swift13:32
acolesclayg: re. 12 digit hex deca-microseconds (89 year delta) - if we add 0xa000000000000 to every offset and ditch the _ separator (split on a-f) then we get another digit for free13:34
acolesclayg: e.g. 1234567890.01234af9f9f9f9f9f9 . that gets us to 6 x 89 years13:37
*** dmsimard_away is now known as dmsimard13:49
*** psharma has quit IRC13:51
*** blinky_ghost has joined #openstack-swift13:51
*** kashyapk has joined #openstack-swift14:01
openstackgerritKota Tsuyuzaki proposed a change to openstack/swift: Efficient Replication for Distributed Regions  https://review.openstack.org/9982414:04
*** lpabon has joined #openstack-swift14:09
*** kashyapk has quit IRC14:11
blinky_ghosthi all, is it possible to use swift as mountpoint in my linux client box?14:14
*** kevinc_ has joined #openstack-swift14:14
*** tdasilva has joined #openstack-swift14:26
*** IRTermite has joined #openstack-swift14:27
*** kevinc_ has quit IRC14:27
*** zhiyan_ is now known as zhiyan14:46
*** kashyapk has joined #openstack-swift14:53
lpabonblinky_ghost, :-) Check out swiftonfile (previously known as Gluster-swift)14:56
creihtlpabon: I don't think that is exactly what he is looking for14:57
*** Longgeek_ has quit IRC14:57
creihtblinky_ghost: there is cloudfuse but it has some bugs, and I think there is a pyfuse based one as well14:57
creihtcould look into those14:57
*** itarchitectkev_ has quit IRC14:58
creihtclayg: I thought you said you were going to change the headers back to strings? :)15:00
*** itarchitectkev_ has joined #openstack-swift15:04
*** zhiyan is now known as zhiyan_15:09
*** zul has quit IRC15:12
*** zul has joined #openstack-swift15:12
blinky_ghostcreiht: thanks :)15:14
*** zul has quit IRC15:14
*** zul has joined #openstack-swift15:15
creihtblinky_ghost: if you don't mind me asking, what were you planning on using it for?15:15
blinky_ghostcreith: I have some remote endpoints (linux boxes) on a WAN and want to them to archive data on my datacenter storage. So I was thinking to setup Swift and use a mountpoint on the linux boxes, to put/delete/get data.15:19
*** zul has quit IRC15:25
*** annegentle has quit IRC15:29
*** foexle has quit IRC15:33
*** kashyapk has quit IRC15:47
*** kashyapk has joined #openstack-swift15:48
*** kashyapk has quit IRC15:52
*** zul has joined #openstack-swift15:53
*** gyee has joined #openstack-swift15:58
openstackgerritDonagh McCabe proposed a change to openstack/swift: Add swift-checker utility for use by monitoring tools  https://review.openstack.org/9996116:02
*** mwstorer has joined #openstack-swift16:04
*** zul has quit IRC16:14
*** NM has quit IRC16:24
claygcreiht: you know that is one haven't gotten around to yet16:39
creihtahh16:40
claygportante: i knew there was a reason i wrote those, i got it all fixed up too, with some unittests and such - just testing all of the rebase - i did a bunch of stuff yesterday16:40
claygacoles: hehehhehehe16:41
peluse_clayg:  BTW, once I fixed my config probe is passing for me with one ring 3x and one 2x.  is there a specific test you thought would/should fail w/2x?16:44
claygpeluse_: i sorta thought they all would16:44
claygpeluse_: never got around to esting it for myself, torgomatic said his second ring was a cp of object.ring.gz, mine are all built with 316:45
*** zul has joined #openstack-swift16:47
peluse_clayg:  yeah, that works fine.  Ran 3 times in a row last night with one 3x and one 2x and just ran again (VM just sat there overnight) and now one test fails.  Sheesh16:47
*** kashyapk has joined #openstack-swift16:47
claygheheheh16:47
portanteclayg: great!16:47
peluse_test_object_expirer_split_brain seems to be intermittent for me... will look into it a bit more and let ya know what I find16:50
claygportante: i'm at a real loss on what to do with some of your comments bro?  yesterday I ended up doing a lot of hand-wringing trying to figure out what to do about some of your concerns around docs and tests.16:50
claygpeluse_: that's the one that portante discovered the delete_at tmp dir bug on - fixed in the next rebase (coming up shortly)16:50
*** kashyapk has quit IRC16:51
claygportante: e.g. "Are there probe or functional tests that show that all "musts" are enforced properly?" re: policy parsing16:51
*** NM has joined #openstack-swift16:51
peluse_ahhh, cool16:52
claygportante: i guess the answer is "no", although the unittests that write a file on disk and then hand it to the function that reads is and watches it blow up are about as close as you want to get to "functional" IMHO16:52
claygportante: but those tests are right there in the same diff that you commented on, so I'm guessing you saw them and deamed them insufficient, and you're asking if better tests come later and .... i don't know what a better test would look like?  a probetests that checks config parsing?  a functional tests that can... i don't even know exactly.16:54
claygportante: so I ponder and worry that I'm missing something obvious - and don't know how to respond16:54
* portante is catching up, sec ...16:54
*** shri has joined #openstack-swift16:55
portanteclayg: I think I see your concerns, I don't think I have explained myself well enough16:55
portanteMost of what I am concerned about is from an end user, and not a developer16:56
peluse_portante:  have an example if you guys don't mind be jumping in here?16:56
portanteso as an end user, while reading the docs I am told that steps 1 - 5 will tell you if a swift cluster is setup and running correctly16:56
claygportante: yeah that's great!  I mean if you're using storage polices and you see something that's not implemented in a client friendly way we gotta suss it up!16:57
claygportante: oh this back on the saio docs - those aren't for "end users" by any strech?16:57
portanteso what I'd like to see, and don't want to gate anything by this, is a set of functional/probe tests that correspond to the assertiions we are documenting to users16:57
peluse_portante:  which specific assertions?16:58
portanteall the steps that say: "curl ..." and you should get this, "curl ..." that and you get that16:58
portanteso I pointed a bunch out in the various guides I was reading16:59
peluse_portante:  ahhhh.  I can add those post merge.16:59
claygportante: we have a QA Engineer, shes a real baddass, and she has some "doc driven" tests that run against our product - I guess it'd be pretty great if swift could have something similar16:59
portanteyes, agreed16:59
portantepeluse_: great16:59
portanteclayg, peluse_: while I am pointing them out, I am not using a -1 to indicate we need them, just that I wanted to record them so that we can work to make that happen later. this kind of thing seems worth to do in general, not just for sp17:00
portanteneed them for sp, such that sp merge would be gated by them17:01
*** fbo is now known as fbo_away17:01
*** kashyapk has joined #openstack-swift17:02
*** kashyapk has quit IRC17:07
claygcreiht: is gholt not hanging out in here on purpose?17:18
creihtclayg: long story17:18
creihtbut when he's here, he's at the computer :)17:19
claygI think one of his comments says "yeah except (Exception, Timeout) will be fine" - but I'm not sure but he didn't exactly say that, it almost sounded like "I don't really care but other people care so i'm just saying"17:19
creihtlol17:19
creihtwhich review?17:19
creihtI think he mumbled something about that yesterday17:19
creihtsomething about bare excepts17:20
clayghttps://review.openstack.org/#/c/96044/ - he was responding to me asking to confirm how i should phrase my pokemon excepts17:20
claygcreiht: well in a couple places someone managed to let some really silly bare excepts sneak in - there's a lot of new code in cli/info.py that is just catching WAY too much - so those I just cleaned up17:20
creihtyeah I think his basic stance is (which I share)17:21
creihtif we are doing a basic try: except Exception: block17:21
claygcreiht: oh oh oh get it out quick my last tests just passed I'm about to push push push!17:21
creihtit is usually a good idea to catch timeout there as well17:22
creihtas if you are catching except Exception, you are trying to catch anything bad that might happen17:22
claygcreiht: well yeah, the db queries all raise timeout17:22
creihtand while there may not be code that throws timeouts right now, that doesn't mean that someone will not add them down the road17:23
claygcreiht: *exactly* - it's almost like we just want to say... oh... i don't know... if on there was something that would just like catch *everything*, it's weird that python doesn't have that for just this situation...17:23
creihtahh17:24
creihtyeah17:24
claygcreiht: i'm just joshin'17:24
creihtI'm looking at the code now17:24
creihtI remember a while back having bare excepts causing some wacky issues17:24
claygcreiht: I'm way way way fine with (Exception, Timeout) that is close enough to everything for me - i've just grown sour on it over after we had those bugs that "fixed" bare excepts17:25
creihtbut can't remember exactly what17:25
creihtheh17:25
claygcreiht: oh... that is new17:25
claygcreiht: ok - so but except (Exception, Timeout) is what we're looking for there?17:25
creihtyeah I think that is reasonable17:25
claygtotally down - thanks!17:25
creihtcool17:25
claygoh shit... here it comes!17:26
claygoh... nevermind - there was a commit message I wanted to clean up - and fix authorship - 5 more mins :P17:27
creihthaha17:27
creihtI think the thing that bit us a while back, is that we had some bare exceptions hiding some really bad bugs17:27
creihtso we got jaded, and got very anti- bare except :)17:28
claygcreiht: eheheh, were they not logging the exceptions?  cause that's a rule i made up as a good idea when you catch everything17:28
creihtclayg: yeah17:28
creihtthings like17:29
creihtexcept: pass17:29
creiht:)17:29
creihtclayg: and I'm on board with it being fairly pragmatic that if you are going to do something like that make sure you log something17:29
creihtbut then others might see that code and think, oh I can just put a bare except here17:30
creihtso it is just easier to be consistently explicit17:30
creiht </soapbox>17:31
creiht:)17:31
*** mmcardle has quit IRC17:32
*** GoJkoRs has joined #openstack-swift17:37
GoJkoRsHey guys.  I have a problem with Swift in horizon.  Can someone point me to an guide about the integration of the two?  I click on objects and it says "Error: Unable to retrieve container list."17:38
GoJkoRsSwift at the CLI works just fine.17:38
*** zul has quit IRC17:43
*** zul has joined #openstack-swift17:43
*** gyee has quit IRC17:45
*** chuck__ has joined #openstack-swift17:47
*** zul has quit IRC17:47
*** NM has quit IRC18:00
claygok, I think i'll really do it this time18:04
openstackgerritClay Gerrard proposed a change to openstack/swift: Fixes probe tests with non-zero default storage policy  https://review.openstack.org/9635318:04
openstackgerritClay Gerrard proposed a change to openstack/swift: Add two vector timestamps  https://review.openstack.org/9931518:04
openstackgerritClay Gerrard proposed a change to openstack/swift: Add Storage Policy Support  https://review.openstack.org/9602718:04
openstackgerritClay Gerrard proposed a change to openstack/swift: Add Storage Policy Documentation  https://review.openstack.org/9602618:04
openstackgerritClay Gerrard proposed a change to openstack/swift: Add Storage Policy support to Containers  https://review.openstack.org/9602918:04
openstackgerritClay Gerrard proposed a change to openstack/swift: Update FakeRing and FakeLogger  https://review.openstack.org/9602818:04
openstackgerritClay Gerrard proposed a change to openstack/swift: Add Storage Policy support to Object Server  https://review.openstack.org/9603018:04
openstackgerritClay Gerrard proposed a change to openstack/swift: Fix object-expirer for missing objects  https://review.openstack.org/9851118:04
openstackgerritClay Gerrard proposed a change to openstack/swift: Add functional tests for Storage Policy  https://review.openstack.org/9604218:04
openstackgerritClay Gerrard proposed a change to openstack/swift: Update bin scripts to be storage policy aware  https://review.openstack.org/9604318:04
openstackgerritClay Gerrard proposed a change to openstack/swift: Merge container storage_policy_index  https://review.openstack.org/9604018:05
openstackgerritClay Gerrard proposed a change to openstack/swift: Add Storage Policy Support to Accounts  https://review.openstack.org/9604118:05
openstackgerritClay Gerrard proposed a change to openstack/swift: Add Storage Policy Support to list_endpoints  https://review.openstack.org/9604618:05
openstackgerritClay Gerrard proposed a change to openstack/swift: Add Storage Policy Support to Container Sync  https://review.openstack.org/9604718:05
openstackgerritClay Gerrard proposed a change to openstack/swift: Enqueue misplaced objects during container replication  https://review.openstack.org/9604418:05
openstackgerritClay Gerrard proposed a change to openstack/swift: Add LRUCache to common.utils  https://review.openstack.org/9604518:05
openstackgerritClay Gerrard proposed a change to openstack/swift: Add Storage Policy Support to ssync  https://review.openstack.org/9603418:05
openstackgerritClay Gerrard proposed a change to openstack/swift: Put X-Backend-Timestamp in object 404 responses  https://review.openstack.org/9603518:05
openstackgerritClay Gerrard proposed a change to openstack/swift: Add Storage Policy Support to the Auditor  https://review.openstack.org/9603218:05
openstackgerritClay Gerrard proposed a change to openstack/swift: Add storage policy support for the Replicator  https://review.openstack.org/9603318:05
openstackgerritClay Gerrard proposed a change to openstack/swift: Add container-reconciler daemon  https://review.openstack.org/9603818:05
openstackgerritClay Gerrard proposed a change to openstack/swift: Add reconciler probetest outline  https://review.openstack.org/9603918:05
openstackgerritClay Gerrard proposed a change to openstack/swift: Extend interface on InternalClient  https://review.openstack.org/9603618:05
openstackgerritClay Gerrard proposed a change to openstack/swift: Extend direct_client  https://review.openstack.org/9603718:05
openstackgerritClay Gerrard proposed a change to openstack/swift: Add Storage Policy support to the Account Reaper  https://review.openstack.org/9604918:05
openstackgerritClay Gerrard proposed a change to openstack/swift: Add Storage Policy Support to Recon Middleware  https://review.openstack.org/9604818:05
openstackgerritClay Gerrard proposed a change to openstack/swift: Add Storage Policy support to Object Updates  https://review.openstack.org/9997918:05
*** chuck__ is now known as zul18:09
claygacoles: so I think the split on 'a-f' will end up sorta janky compared to an explicit seperater18:09
*** zul has quit IRC18:09
*** zul has joined #openstack-swift18:09
*** kashyapk has joined #openstack-swift18:09
claygGoJkoRs: you may have to ask the Horizon guys - don't think many of use it.18:10
claygacoles: I also think that you'll proably have to code up the overflow code (rollup the data file ts a deca-micro and buy yourself another few years of time delta)18:12
GoJkoRsOk.  Thank you18:12
*** gyee has joined #openstack-swift18:13
*** blinky_ghost has quit IRC18:16
claygacoles: yeah I think the 12 digit fixed is the way to go, 8's just no enough to encode a reasonable number of deca-microseconds - and what's 4 bytes amoung internal use-cases18:17
*** mkollaro has quit IRC18:22
claygk, i'm offline for a bit18:22
*** zaitcev has joined #openstack-swift18:23
*** ChanServ sets mode: +v zaitcev18:23
*** kashyapk has quit IRC18:32
*** uksysadmin has joined #openstack-swift18:33
*** kashyapk has joined #openstack-swift18:33
creihtJust saw this on the eventlet mailing list, they are calling people to test the .15 pre-release18:34
creihthttps://lists.secondlife.com/pipermail/eventletdev/2014-June/001164.html18:35
*** itarchitectkev_ has quit IRC18:35
creihtwhich looks like includes a py3 branch18:35
*** kashyapk has quit IRC18:37
*** uksysadmin has quit IRC18:38
torgomatichuh, looks like we might actually have to start accepting all those py3 patches18:38
*** uksysadmin has joined #openstack-swift18:39
creihthehe18:43
*** chuck__ has joined #openstack-swift18:49
*** nthacker__ has joined #openstack-swift18:50
*** NM has joined #openstack-swift18:50
*** zul has quit IRC18:51
*** GoJkoRs has left #openstack-swift18:52
*** nthacker_ has quit IRC18:53
portantecreiht: great news18:56
*** lpabon has quit IRC18:56
portanteAlex_Gaynor: curious, where are we at with PyPy and Swift?18:57
portanteI have been using pypy for major speedups in my python code outside of swift and am liking how well it has worked so far18:57
*** lpabon has joined #openstack-swift18:58
*** tdasilva has quit IRC18:58
*** tdasilva has joined #openstack-swift19:01
portanteclayg: are you going to try to get gerrit ID 100000 for the final storage policy set? :)19:02
peluse_wonder if there's a prize for that...19:03
creihthaha19:04
portanteprobably already taken by now19:04
peluse_there's goes the free toaster :(19:06
Alex_Gaynorportante: it works. I think it's not gatinf for side silly reason, will find our next week19:06
*** bsdkurt has quit IRC19:14
*** gholt has joined #openstack-swift19:16
*** ChanServ sets mode: +v gholt19:16
gholtohai!19:17
*** tdasilva has quit IRC19:18
portanteAlex_Gaynor: thanks19:22
*** chuck__ has quit IRC19:26
*** uksysadmin has quit IRC19:26
*** jamiehan_ has joined #openstack-swift19:29
*** tdasilva has joined #openstack-swift19:30
*** jamiehannaford has quit IRC19:31
*** torgomatic has quit IRC19:47
*** torgomatic has joined #openstack-swift19:54
*** ChanServ sets mode: +v torgomatic19:54
*** otoolee has quit IRC19:55
*** DisneyRicky has quit IRC19:57
claygwhy isn't gerrit testing our stuff?19:59
*** zul has joined #openstack-swift19:59
*** shri has quit IRC20:03
*** shri has joined #openstack-swift20:03
*** otoolee has joined #openstack-swift20:10
torgomaticclayg: with the latest version of 96026 (#11), everything seems to be working for me FYI20:11
torgomaticdunno about gerrit; maybe it's backed up?20:11
torgomaticclayg: looks like it's testing to me; I'm getting emails containing "FAILURE" and "tempest-dsvm-blahblah" in close proximity20:15
torgomatic(notice "testing", not "working")20:15
*** lpabon has quit IRC20:22
*** DisneyRicky has joined #openstack-swift20:24
*** miqui has quit IRC20:25
*** shri1 has joined #openstack-swift20:36
*** shri has quit IRC20:37
gholtMaybe "consuming electricity" is better.20:38
*** jamiehan_ has quit IRC20:39
serverascodeHi, does anyone know if there any negative repercussions to setting object_post_as_copy = false in the proxy server configuration?21:02
*** gholt has quit IRC21:05
*** tdasilva has left #openstack-swift21:06
creihtserverascode: the main thing is that you can't change the content-type by a post21:07
creihtthe client would have to change it by COPY instead21:07
serverascodeok thanks :)21:08
creihtnp21:08
creihtcontainer sync will not be able to sync POST updates21:08
creihtgif you happen to use that21:09
serverascoderight, yeah we don't use container sync21:09
creihtcool21:09
*** jamiehannaford has joined #openstack-swift21:15
*** haomaiw__ has quit IRC21:21
anticwcreiht: if POST does a copy it will21:31
* anticw didn't read back more than 3 lines :)21:31
creihthaha21:34
anticwi was thinking later on we can make it update the container-servers as well for POST21:35
anticwonce the basics are working well21:35
creihtanticw: we talked about the possibility of doing that at the hackathon21:35
anticwgholt isn't here, so i think we should expect that of him21:35
*** kashyapk has joined #openstack-swift21:35
creihtso someone may be attempting something like that in the nearish future21:36
*** kashyapk has quit IRC21:40
*** fbo_away is now known as fbo21:48
*** NM has quit IRC21:55
*** acoles has quit IRC22:03
*** acoles has joined #openstack-swift22:09
*** ChanServ sets mode: +v acoles22:09
*** jamiehannaford has quit IRC22:19
*** j_king has quit IRC22:19
*** kashyapk has joined #openstack-swift22:30
*** kashyapk has quit IRC22:35
*** dmsimard is now known as dmsimard_away22:51
openstackgerritOpenStack Proposal Bot proposed a change to openstack/python-swiftclient: Updated from global requirements  https://review.openstack.org/8925022:57
openstackgerritOpenStack Proposal Bot proposed a change to openstack/swift: Updated from global requirements  https://review.openstack.org/8873622:57
*** fbo is now known as fbo_away23:07
*** NM has joined #openstack-swift23:21
*** kashyapk has joined #openstack-swift23:33
*** kashyapk has quit IRC23:38
*** mwstorer has quit IRC23:46
*** NM has quit IRC23:59

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