Friday, 2015-02-20

*** vinsh has quit IRC00:03
*** dmsimard is now known as dmsimard_away00:05
*** rdaly2 has quit IRC00:18
*** zhill has joined #openstack-swift00:23
*** os1 has quit IRC00:28
zaitcevclayg: There was a patch from one of our Japanese crew guys just recently about this. The old behavior was, if container updater gets 404, just drop the update. His idea was to retry forever. I do not remember what the justification was. Apparently some kind of inconsistency.00:35
zaitcevclayg: I don't remember if it went it. I wasn't a fan.00:35
zaitcevActually....00:35
zaitcevhttps://review.openstack.org/99598 - here it is. It's the younger guy, Takahashi. "for example when all containers are putted at handoff devices", he says.00:37
*** dmorita has joined #openstack-swift00:38
*** lcurtis has quit IRC00:41
claygzaitcev: I'm not sure it's specifically related, I just wanted to retry till reclaim_age - redbo told me recently that he'd seen really old async pendings sneak an object update back into a container long after the object had been tombstoned and the deleted row in the container reaped00:43
zaitcevclayg: well, that makes sense00:44
claygzaitcev: it's sort of a wonky situation, because normally the tombstone would have async'd over the put - the object updater does something to compress those async records - but if the part was also handed off the tombstone record could have gotten processed from another node00:44
claygthen it's a question why this one node's object-updater wasn't doing his asyncs00:45
zaitcevokay, that's a level down. imkarrer is dealing with container updater00:45
claygzaitcev: yeah I think so00:45
*** dmsimard_away is now known as dmsimard00:52
*** david-lyle is now known as david-lyle_afk00:59
*** nellysmitt has joined #openstack-swift01:03
*** nellysmitt has quit IRC01:07
*** zhill has quit IRC01:09
*** zhill_ has joined #openstack-swift01:10
*** abhirc has quit IRC01:17
*** chlong has quit IRC01:40
*** chlong has joined #openstack-swift01:41
*** kajinamit has joined #openstack-swift01:45
*** abhirc has joined #openstack-swift01:53
*** vinsh has joined #openstack-swift02:01
*** vinsh has quit IRC02:21
*** dmsimard is now known as dmsimard_away02:23
*** jrichli has joined #openstack-swift02:29
*** NM has joined #openstack-swift02:32
claygoh wait, so we didn't come to any concensus on publishing the reseller prefix, except that glange and I both think it's weird - and notmyname is out of town till next week.02:51
mattoliverauI haven't properly reviewed that change yet, still trying to install keystone :(02:55
claygmattoliverau: apparently acoles has a script for that?  he said something about using his saio with a stand alone keystone endpoint02:55
claygwhich I like very much except the part where I have to maintain a keystone provisioning script02:56
claygbut if *acoles* maintained it!?!02:56
mattoliverauI'll go back and look at his script.. at first glance it configured keystone not set it up.. but I could be wrong, besides if it does that is still decreases the effort required :)02:57
claygor mattoliverau - I'm not picky - basically anything in the the difference of the set of all people in the world and set([me])02:57
mattoliverauclayg: lol, i like the way you think.. thanks for volunteering to keep it maintained acoles_away :P02:57
claygwell that gist he linked was just about provisioning users against a devstack keystone endpoint since it doesn't come setup will all the service roles and the like by default02:58
claygI think most of my problems with devstack may truely have been just that I *only* provisioned 1GB of memory for the poor thing02:59
mattoliverauSigh.. I don't have the required launchpad rights to do triage or invalidate bugs, I guess I need to go complain to infra02:59
claygwhich seemed like enough since I was only running swift and keystone and I've successfully run saio's on 512 in the past - I had assumed that a keystone deployment would take less memory than swift (oh i'm so silly!)02:59
mattoliverauclayg: lucky I have a rackspace dev account ;)03:00
mattoliveraulol03:00
claygoh yeah, notmyname also swears by saio's in the cloud - I've done that before I suppose03:00
mattoliverauI maybe one of the biggest Sydney region users.. and I don't pay. But its what I do, I keep the syd dcops guys employed :P03:02
*** nellysmitt has joined #openstack-swift03:03
*** nellysmitt has quit IRC03:08
*** NM has quit IRC03:14
*** panbalag has quit IRC03:18
*** vinsh has joined #openstack-swift03:22
*** zhill_ has quit IRC03:22
*** vinsh has quit IRC03:26
*** gyee has quit IRC03:28
*** vinsh has joined #openstack-swift03:53
*** NM has joined #openstack-swift04:20
*** zaitcev has quit IRC04:36
*** SkyRocknRoll has joined #openstack-swift04:40
*** lcurtis has joined #openstack-swift05:04
*** nellysmitt has joined #openstack-swift05:05
*** ppai has joined #openstack-swift05:05
lcurtishello all...for some reason i was reading an article that warned against using built in python web server in swift for larger environments...instead using something else like haproxy or apache...am i mistaken?05:06
*** nellysmitt has quit IRC05:09
*** jrichli has quit IRC05:11
clayglcurtis: all of the largest deployments I know about use the built in python web server - the thing is you can't terminate ssl in it05:22
claygso stud or haproxy for ssl termination with the built in swift/eventlet proxy processes listening on your localhost is generally gunna treat ya05:23
claygfor the backend services, you can just bind stright up to the private/cluster network interfaces05:23
claygi guess I've heard of people doing something with apache, and one time this one guy tried something with nginx but it didn't work out05:23
*** SkyRocknRoll has quit IRC05:26
claygahale: we switched to stud for ssl termination cause like one time syn said it was great, and generally speaking it's been better than haproxy, but stupid poodle was a disaster because of https://github.com/bumptech/stud/pull/138/files not being merged05:26
claygahale: we were gunna fork and repackage (as we do) but swifterdarrell found this crazy shit -> https://github.com/Netfuture/tlsinterposer05:28
claygso you LD_PRELOAD this shim that lets you get the right f'ing SSL_CTX options you want05:28
claygI breifly argued it would be easier to just patch stud like the rest of world, but swifterdarrell had convinced himself it would be a good thing to have around the next time we have some stupid glue app that won't let us setup SSL the way we want05:29
claygi always want to call it the tls-interloper05:32
*** SkyRocknRoll has joined #openstack-swift05:42
*** NM has quit IRC05:42
claygthat moment when you realize your "quick fix" has become an 800 line diff05:44
*** lcurtis has quit IRC05:44
claygi'll see what i can do to chop it up later05:44
claygg'night05:44
*** mrda is now known as mrda-weekend06:01
*** ahonda has quit IRC06:16
*** kajinamit has quit IRC06:26
*** nshaikh has joined #openstack-swift06:44
*** nellysmitt has joined #openstack-swift07:05
*** nellysmitt has quit IRC07:10
*** SkyRocknRoll has quit IRC07:14
*** silor has joined #openstack-swift07:19
*** jamielennox is now known as jamielennox|away07:22
*** nellysmitt has joined #openstack-swift07:23
*** SkyRocknRoll has joined #openstack-swift07:31
*** nshaikh has left #openstack-swift07:53
ahaleoO07:56
*** nshaikh has joined #openstack-swift08:02
*** ahonda has joined #openstack-swift08:08
*** mmcardle has joined #openstack-swift08:09
*** rledisez has joined #openstack-swift08:12
*** madhuri_ has quit IRC08:33
*** jistr has joined #openstack-swift08:46
*** madhuri has joined #openstack-swift08:47
*** ppai has quit IRC09:03
*** madhuri has quit IRC09:10
*** ppai has joined #openstack-swift09:15
*** jordanP has joined #openstack-swift09:19
*** khivin has joined #openstack-swift09:26
*** ppai has quit IRC09:28
*** ppai has joined #openstack-swift09:40
*** acoles_away is now known as acoles09:54
acolesclayg: mattoliverau : so it did cross my mind to script everything from bare VM to swift-config'd-keystone. i could do it while waiting for gerrit to serve pages ;)10:08
*** aix has joined #openstack-swift10:12
acolesclayg: i run keystone in a 1GB vm, devstack in 4GB (lucky choice i guess). what did they use to land on the moon? :o10:18
openstackgerritAlistair Coles proposed openstack/swift-specs: Updates to encryption spec  https://review.openstack.org/15431810:28
*** MasterPiece has joined #openstack-swift10:30
*** SkyRocknRoll has quit IRC10:48
openstackgerritMerged openstack/swift: Update guest VM OS recommendation in SAIO doc  https://review.openstack.org/15653910:56
*** ppai has quit IRC11:11
*** ppai has joined #openstack-swift11:25
*** jasondotstar has joined #openstack-swift11:32
*** openstack has joined #openstack-swift20:23
*** zhill has quit IRC20:24

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