Monday, 2014-05-05

*** mmcardle has joined #openstack-swift00:19
*** bach has joined #openstack-swift00:19
*** shakamunyi has joined #openstack-swift00:23
*** zhiyan_ is now known as zhiyan00:26
*** yuan has quit IRC00:27
*** mmcardle has quit IRC00:30
*** peluse has joined #openstack-swift00:33
*** ams0 has joined #openstack-swift00:38
*** ams0 has quit IRC00:43
*** shakamunyi has quit IRC00:48
*** bach has quit IRC00:51
*** shakamunyi has joined #openstack-swift01:13
*** saschpe has quit IRC01:22
*** saschpe has joined #openstack-swift01:24
*** mmcardle has joined #openstack-swift01:27
*** ams0 has joined #openstack-swift01:38
*** mmcardle has quit IRC01:39
*** ams0 has quit IRC01:43
*** bach has joined #openstack-swift01:44
*** mmcardle has joined #openstack-swift02:36
*** mmcardle has quit IRC02:49
*** praveenkumar has joined #openstack-swift02:55
*** shakamunyi has quit IRC02:57
*** piousbox_ has quit IRC03:34
*** tzumainn has quit IRC03:36
*** ams0 has joined #openstack-swift03:39
*** ams0 has quit IRC03:43
*** mmcardle has joined #openstack-swift03:46
*** mmcardle has quit IRC04:00
*** ppai has joined #openstack-swift04:26
*** haomaiwang has joined #openstack-swift04:31
*** haomaiwang has quit IRC04:32
*** haomaiwang has joined #openstack-swift04:33
*** mmcardle has joined #openstack-swift04:56
*** ams0 has joined #openstack-swift05:08
*** mmcardle has quit IRC05:10
*** mlipchuk has joined #openstack-swift05:11
*** nshaikh has joined #openstack-swift05:15
*** haomai___ has joined #openstack-swift05:22
*** haomaiwang has quit IRC05:22
*** ams0 has quit IRC05:26
*** haomaiwang has joined #openstack-swift05:26
*** chandan_kumar has joined #openstack-swift05:26
*** ams0 has joined #openstack-swift05:26
*** haomai___ has quit IRC05:29
*** ams0 has quit IRC05:30
*** ams0 has joined #openstack-swift05:56
*** mmcardle has joined #openstack-swift06:06
*** mmcardle has quit IRC06:19
*** ams0 has quit IRC06:32
*** cheri has joined #openstack-swift06:39
*** bach has quit IRC07:11
*** mmcardle has joined #openstack-swift07:15
*** bach has joined #openstack-swift07:17
*** psharma has joined #openstack-swift07:23
*** jamie_h has joined #openstack-swift07:24
*** jamie_h has quit IRC07:25
*** RockKuo_Office has joined #openstack-swift07:26
*** mmcardle has quit IRC07:27
*** a1|away is now known as JelleB07:37
*** ams0 has joined #openstack-swift07:38
*** bach has quit IRC07:43
*** openstackgerrit has quit IRC07:53
*** nacim has joined #openstack-swift08:00
*** Diddi has quit IRC08:14
*** Diddi has joined #openstack-swift08:14
*** mmcardle has joined #openstack-swift08:16
*** foexle has joined #openstack-swift08:19
*** ams0 has quit IRC08:27
*** tzumainn has joined #openstack-swift08:34
*** ams0 has joined #openstack-swift08:34
*** ams0 has quit IRC08:39
*** ams0 has joined #openstack-swift08:40
*** ams0 has quit IRC08:44
*** ams0_ has joined #openstack-swift08:47
*** mmcardle has quit IRC08:48
*** ams0_ has quit IRC08:59
*** ams0 has joined #openstack-swift09:00
*** nacim has quit IRC09:03
*** ams0 has quit IRC09:05
*** ams0 has joined #openstack-swift09:05
*** ams0_ has joined #openstack-swift09:07
*** ams0 has quit IRC09:10
*** mmcardle has joined #openstack-swift09:16
*** nacim has joined #openstack-swift09:17
*** haomaiwang has quit IRC09:25
*** mmcardle has quit IRC09:27
*** mkollaro has joined #openstack-swift09:33
*** mmcardle has joined #openstack-swift10:25
*** mmcardle has quit IRC10:37
*** cheri has quit IRC10:52
*** ppai has quit IRC10:57
*** ams0_ has quit IRC11:02
*** tdasilva has joined #openstack-swift11:02
*** ams0 has joined #openstack-swift11:02
*** RockKuo_Office has quit IRC11:04
*** ams0 has quit IRC11:06
*** bvandenh has joined #openstack-swift11:09
*** ppai has joined #openstack-swift11:15
*** haomaiwa_ has joined #openstack-swift11:21
*** bvandenh has quit IRC11:26
*** mmcardle has joined #openstack-swift11:33
*** ppai has quit IRC11:42
*** mmcardle has quit IRC11:44
*** ppai has joined #openstack-swift11:55
*** ppai has quit IRC12:00
*** ams0 has joined #openstack-swift12:00
*** ams0_ has joined #openstack-swift12:02
*** ams0 has quit IRC12:06
*** peluse has quit IRC12:15
*** ams0_ has quit IRC12:15
*** ams0 has joined #openstack-swift12:16
*** ams0_ has joined #openstack-swift12:30
*** ams0 has quit IRC12:33
*** bvandenh has joined #openstack-swift12:35
*** mmcardle has joined #openstack-swift12:42
*** mmcardle has quit IRC12:52
*** mlipchuk has quit IRC13:13
*** foexle has quit IRC13:13
*** foexle has joined #openstack-swift13:19
*** zul has joined #openstack-swift13:31
*** openstackgerrit has joined #openstack-swift13:35
*** mmcardle has joined #openstack-swift13:49
*** openstackgerrit has quit IRC13:51
*** ams0_ has quit IRC13:54
*** ams0 has joined #openstack-swift13:54
*** ams0 has quit IRC13:57
*** ams0 has joined #openstack-swift13:57
*** ams0 has quit IRC13:58
*** mmcardle has quit IRC13:58
*** ams0 has joined #openstack-swift13:58
*** nacim has quit IRC14:01
*** ChanServ sets mode: +v dfg_14:10
*** dfg_ is now known as dfg14:11
*** nacim has joined #openstack-swift14:19
*** mmcardle has joined #openstack-swift14:24
*** wasmum has joined #openstack-swift14:27
*** bvandenh has quit IRC14:27
wasmumFrontending Keystone with SSL using Apache mod_wsgi vs Nginx.  Thought, performance issues, concerns?14:28
*** wasmum has quit IRC14:31
*** psharma has quit IRC14:33
*** mmcardle has quit IRC14:39
*** foexle has quit IRC14:45
*** foexle has joined #openstack-swift14:46
*** mwstorer has joined #openstack-swift14:48
*** praveenkumar has quit IRC14:49
*** nacim has quit IRC14:50
*** byeager has joined #openstack-swift14:57
*** nacim has joined #openstack-swift14:58
*** mmcardle has joined #openstack-swift15:07
*** zul has quit IRC15:17
*** mmcardle has quit IRC15:18
*** wklely is now known as wkelly15:18
*** mlipchuk has joined #openstack-swift15:19
*** zul has joined #openstack-swift15:19
*** praveenkumar has joined #openstack-swift15:23
*** zhiyan is now known as zhiyan_15:25
*** haomaiwa_ has quit IRC15:29
*** haomaiwang has joined #openstack-swift15:30
*** foexle has quit IRC15:35
*** haomaiwang has quit IRC15:37
*** haomaiwa_ has joined #openstack-swift15:38
*** openstackgerrit has joined #openstack-swift15:42
*** haomaiwa_ has quit IRC15:43
*** gyee has joined #openstack-swift15:43
*** byeager has quit IRC15:57
*** byeager has joined #openstack-swift15:58
*** byeager has quit IRC15:58
*** byeager has joined #openstack-swift15:59
*** cheri has joined #openstack-swift16:07
*** ams0__ has joined #openstack-swift16:09
*** ams0 has quit IRC16:09
*** mmcardle has joined #openstack-swift16:17
*** chandan_kumar has quit IRC16:19
notmynamegood morning, world16:24
notmynamewasmum isn't here anymore :-(16:25
notmynameportante: good morning. around?16:28
*** mmcardle has quit IRC16:30
*** ams0__ has quit IRC16:31
openstackgerritDavid Goetz proposed a change to openstack/swift: xLO bug with auth tokens expiring during download.  https://review.openstack.org/9216516:39
*** mlipchuk has quit IRC16:41
notmynamedfg: nice16:45
dfgnotmyname: well- wait for comment :)16:46
*** piousbox_ has joined #openstack-swift16:46
*** zaitcev has joined #openstack-swift16:46
*** ChanServ sets mode: +v zaitcev16:46
notmynameoh I haven't looked at the code yet, but the commit message sounds good!16:46
notmyname(+2 ship it!)16:46
*** xiaowei-swift has joined #openstack-swift16:58
*** nacim has quit IRC16:59
*** tdasilva has left #openstack-swift17:01
*** xiaowei-swift has left #openstack-swift17:03
*** shri has joined #openstack-swift17:14
*** wkelly has quit IRC17:20
*** openstackgerrit has quit IRC17:20
*** wkelly has joined #openstack-swift17:22
notmynameif you are leading a summit session or giving a swift-related conference talk next week, please come to today's team meeting at 1900UTC17:23
notmynamehttps://wiki.openstack.org/wiki/Meetings/Swift17:23
notmynameI want to make sure you have everything you need and are ready for next week17:24
*** openstackgerrit has joined #openstack-swift17:24
*** zul has quit IRC17:24
*** nshaikh has quit IRC17:24
portantenotmyname: now I am!17:24
notmynameerr. not today's meeting. this week's meeting17:24
* notmyname normally does prep for the wednesday meeting on wednesday. not monday17:24
portantenotmyname: phew, that I was going to miss today's meeting17:25
portanteI plan on attending Wednesday, FWIW17:25
notmynameportante: not related to the meeting, but what's up with the in-process func tests in the gate? I haven't looked at the logs, but I saw a lot of emails saying that it failed17:25
*** mlanner has quit IRC17:25
*** zul has joined #openstack-swift17:25
*** mlanner has joined #openstack-swift17:28
portanteyes, the underlying mechanism is using run-unittests.sh, which does not actually support what we want to do, but I am told there is a way to do what we want using run-tox.sh instead17:28
portantehowever, I have not made further progress on that. :( Sorry17:28
portantenotmyname:17:28
notmynameno worries (in general). is there any time-frame for getting it working (either from your end or from -infra--I'm not sure who would do a "fix")?17:29
notmynameportante: will it be this week or after the summit is the biggest question17:29
notmynameportante: IMO, sooner is better because I don't want to train ourselves to ignore the results17:30
portantenotmyname: this week, at least that is what I think can be done17:31
portantebut I thought it was doable last week, but not knowing how the -infra code actually works, that did not pan out17:31
*** zul has quit IRC17:31
notmyname:-)17:32
notmynameportante: I'm pretty busy with summit prep this week, but let me know if there is anything you need from me17:32
portantewill do, thanks17:32
*** klrmn has joined #openstack-swift17:36
klrmnchmouel: swifterdarrell suggested you might be able to loan me a clue about swift + keystone. i got x-container-read to work with '_member_', but x-container-write doesn't appear to be working17:38
*** lpabon has joined #openstack-swift17:39
*** cheri has quit IRC17:47
* creiht shakes his fist at pbr 18:00
creihtagain18:00
creihtheh18:00
*** byeager has quit IRC18:01
*** byeager has joined #openstack-swift18:01
portantenotmyname: I have filed a new commit to try to get things going for the in-process functional tests, but I feel it is just a stab in the dark, so hopefully the -infra team will help out18:02
notmynameok18:02
notmynamecreiht: what, specifically?18:02
creihtjust a little thing18:02
portantenotmyname:  https://review.openstack.org/9217418:02
portantepatchbot p 9217418:02
patchbotportante: https://review.openstack.org/#/c/92174/18:02
*** byeager has quit IRC18:02
*** byeager_ has joined #openstack-swift18:02
creihtnotmyname: where does the rc1 come from in the version number when we are in release candidate phase?18:03
creihtwe last built packages during rc phase18:04
creihtso version number was 1.13.1.rc1.2518:04
creihtcurrent version is 1.13.1.6218:04
creihtrc1 > 62 for versions18:04
* notmyname joins creiht in fist-shaking18:05
creihtlol18:05
notmynameso, ya, that looks really bad. and probably a bug. but I'm not sure if it's in pbr or in the process (probably process)18:05
notmynamecreiht: pbr looks for the first signed tag that is an ancestor of the current branch18:06
creihtyeah I was thinking the same, but I like blaming everything on pbr ;)18:06
notmynameheh18:06
notmynameso what happens is that at the openstack release time (six month time), the milestone-proposed branch is created and the rc1 signed tag is created18:07
notmynamesince there are no commits on m-p, then the rc1 tag is an ancestor of any subsequent commits that land on master18:07
notmynameso...18:08
notmynameonce the final version is approved, the m-p branch is tagged with the final release number and then merged to master18:08
notmynamewhen then makes any patches landing on master after the merge commit use the final tag18:09
notmynamethis happens in every swift release, but in the openstack cycle releases this takes a lot longer (ie weeks)18:09
creihtnotmyname: can you just push a 1.13.2 release? ;)18:09
notmyname(one) downside of this process is that the "master" version is wrong until the m-p branch is merged18:10
notmynamebut it also seems that the rc version itself is a major problem since a later tag is getting released with an older version number18:11
notmynamecreiht: ya, I think that a 1.13.2 tag is probably the only way to fix this18:11
notmynamecreiht: what is the version compare tool that shows how they compare?18:11
notmynamethe debian package thing18:11
creihtdch18:11
creihtI think?18:11
notmyname$ sudo apt-get install dch18:13
notmynameReading package lists... Done18:13
notmynameBuilding dependency tree18:13
notmynameReading state information... Done18:13
notmynameE: Unable to locate package dch18:13
notmynamepandemicsyn: ? swifterdarrell: ?18:13
creihtdevscripts18:13
creihtor something like that is the pkg18:13
creihtif you type dch in the command line it will tell you18:13
notmynamedpkg --compare-versions18:14
creihtbut dch may not be the right thing18:14
*** bvandenh has joined #openstack-swift18:15
notmynamecreiht: also, I think you should probably always be using the env vars to set the version number when you build packages. that may have avoided the issue. (the issue here being that the version tagged for rc is clearly wrong)18:18
creihtheh... well we don't use pbr when building packages18:19
creihtother than to determine what the current verion is18:19
notmynamecreiht: so in the mean time, you should use the env vars. I doubt I can get ttx to tag something new by the end of the day today (he may still be on vacation). I'll see what I can do18:20
creihtyeah no worries, we will figure something else out short term18:21
notmynamecreiht: http://docs.openstack.org/developer/pbr/packagers.html <-- use pbr (ie don't fork setup.py) but don't use pbr's versions18:21
creihtexcept pbr will hose our build system18:21
*** bach has joined #openstack-swift18:22
notmynamecreiht: please write that down in as much detail that you can and email it to me.18:22
creihtheh18:22
creihtit has been a while18:22
creihtbut we have been through that before with those that should not be named18:23
creiht:)18:23
creihtlast time it boiled down to "We don't support Lucid"18:26
notmynamecreiht: I know that it's a sore spot. please ignore "those that should not be named" and give me the tools to help. I've seen both arguments presented, and frankly both side have done a _terrible_ job at giving clear arguments18:26
*** zul has joined #openstack-swift18:26
creihtI'm just kinda tired of it18:29
creihtWe have our workarounds18:29
creihtwe can live with it18:29
notmynameas do we at swiftstack (using the env vars)18:29
creihtat the end of the day it also boils down to a difference in philosophy18:29
notmynamecreiht: I'm trying to talk in-person next week to some -infra team members, and this would be a great topic. but unfortunately there are more than technical reasons for pbr (I know you despise that). and right now, both sides have pretty much said "well I don't agree with the other guy because he doesn't have my use case".18:29
creihtand you can never "win" those discussions18:30
notmynameit's not about winning18:30
notmynameunless "winning" is something other than "I will never talk to those people again"18:31
creihtwell I use the term win loosely18:31
notmynamewhich is where I think things are now. which is terrible18:31
creihtmeh18:31
creihtI've resided to the fact that none of that stuff is ever going to get better18:31
notmynameand you're right that there are philosophical differences. which is also why IRC is a terrible medium for discussing it18:31
creihtand try to focus on trying to make things good where I can18:32
creihtthat add more value18:32
creihtas long as there are very conflicting philosophies I doubt you will ever come to a happy medium18:32
creihtif you can awesome18:33
creihtbut I've decided that it isn't work the effort18:33
creihtfor me at least18:33
claygwell it just sucks, because now that trusty is out we're going to be having the same fights for precise - they can't just keep saying "oh that's two or three years old we don't support that anymore"18:34
creihtheh18:34
creihtwell and lucid is still good for another year18:35
notmynameactually that's why I'd love to get very specific details from you. so that you don't have to worry about it and I can make arguments beyond "well that tool doesn't work for deployer X"18:35
notmynameclayg: ++18:35
*** sunglasses has quit IRC18:35
creihtnotmyname: but that is the problem... the last time it boiled down to us telling them to try installing it on lucid, and getting told it wasn't supported18:36
creihtnot sure how it can be any more clear18:36
*** sunglasses has joined #openstack-swift18:36
notmynamecreiht: so dump a screen session of installing it on lucid and email it to me. rather than "just go try it an you'll see it's hard". you've already got that I think, since you've run in to the problems. basically a bug report. not "it's busted"18:37
openstackgerritClay Gerrard proposed a change to openstack/swift: Make PBR based setup completely optional  https://review.openstack.org/7709118:37
clayg^ still think thats pretty reasonable18:38
creihtnotmyname: but that is the problem... go through the effort to get it marked as invalid18:38
creihtbecause it isn't "supported"18:38
sunglassesHi everyone! I was wondering what does Swift do in the background when someone requests to read data and while the client is reading the object, another client starts sending request to modify the same object. The proxy server does not spool any data. From my tests, I have not had any issue w/ it. Just curious if this is always guaranteed.18:38
notmynamecreiht: also, to be clear, the arguments for keeping pbr are very bad too (basically, "it makes installing from source easier for -infra") and the resistance to something other than a one-size-fits-all solution is huge18:39
sunglassesAlso, what happens in a similar situation when the reading client flags the query to return the latest ojbect.18:39
claygsunglasses: that's just how file systems work?  get a open file handle and then delete the file - see what you get when you read off the open file handle18:39
claygsunglasses: well X-newest isn't really as atomic as you might imagine, but whatever is available when the request starts is what's going to come out...18:40
sunglassesExcellent. That's what I had assumed. I just wanted to make sure.18:40
claygsunglasses: then you should test it - don't believe some random johnny on the internet - unless it's creiht... he's pretty smart.  you can trust him.18:41
creihthah18:41
creihtsunglasses: well the new upload spools to a tmp dir until it is complete and then moved18:41
creihtthen unlinks the older versions18:41
creihtso depends on what the os does with the read to the unlinked file descriptor18:42
creihtwhich I'm not really sure off the top of my head :)18:42
clayg^ sunglasses nm - ask redbo... he's pretty smart.  you can trust him.18:43
claygoh oh - or portante!18:43
creihthehe18:43
clayg;)18:43
redboIt's what you said.  We dpmIf you have an open filehandle and you're reading from it, then someone else unlinks the file, you can keep reading from it until you close your file handle.18:45
redboer.. hit enter while editing.  We don't modify files in-place.18:45
* clayg closes google.com?dpmIf tab18:46
*** rturk-away is now known as rturk18:58
*** rturk has quit IRC18:59
pandemicsynclayg: heh google tried to autocorrect that for me to something very nsfw19:00
redboI think it takes search history into account when autocorrecting19:01
glangeI thought "google.com?dpmIf" was the german word for mother?19:02
creihtthis isn't going anywhere good19:03
*** bvandenh has quit IRC19:05
*** scotticus has joined #openstack-swift19:36
sunglassesokay thhanks19:38
*** mkollaro has quit IRC19:39
*** mkollaro has joined #openstack-swift19:43
*** ams0 has joined #openstack-swift20:01
*** wer has quit IRC20:10
*** ams0 has quit IRC20:11
*** wer has joined #openstack-swift20:13
*** fbo_away has joined #openstack-swift20:15
*** physcx has quit IRC20:16
*** tdasilva has joined #openstack-swift20:22
*** tnewsome has joined #openstack-swift20:22
*** occup4nt is now known as occupant20:22
*** wer has quit IRC20:23
tnewsomeHow do I list all the objects in a container?20:23
tnewsomeEg. 'swift list' only gives me 10,000 of them.20:24
*** wer has joined #openstack-swift20:24
claygi thought the cli would do the marker queries?20:24
tnewsomeMaybe my CLI is too old.20:25
clayghrmm... code sure does look like it wants to... while True and all that...20:25
tnewsomeIs there a doc about the kind of queries I need to do?20:25
tnewsomeI don't actually want to use the CLI. I just used it as a convenient example.20:25
claygyou just make the GET /v1/account/container?marker=<last-object-in-the-previous-GET>20:25
*** lpabon has quit IRC20:25
tnewsomeclayg: Will do. Thank you.20:26
tnewsomeclayg: Is there any indication in a response that more queries are required?20:27
*** ams0 has joined #openstack-swift20:28
claygnope, when doing container listings you always wanna make another request with the last object as the marker until you get back an empty list20:28
claygthen you only have to worry about objects that were uploaded while you were doing the listings ;)20:28
tnewsomeI'm not worried about those.20:29
*** bach has quit IRC20:29
*** bach has joined #openstack-swift20:29
tnewsomeclayg: Works perfectly.20:39
*** physcx has joined #openstack-swift20:43
openstackgerritClay Gerrard proposed a change to openstack/swift: cleanup policy parsing a bit more  https://review.openstack.org/8707820:47
*** ams0 has quit IRC20:54
*** ams0 has joined #openstack-swift21:13
*** ams0 has quit IRC21:24
openstackgerritA change was merged to openstack/swift: Add Storage Policy Support to Recon Middleware  https://review.openstack.org/8738721:24
*** ams0 has joined #openstack-swift21:24
*** ams0_ has joined #openstack-swift21:30
*** ams0 has quit IRC21:30
*** ams0_ has quit IRC21:35
peluse_^ that had to be a record on rechecks at least recently anyway21:35
*** tdasilva has left #openstack-swift21:37
tnewsomeWhat's the best way to delete 100k objects? Multiple threads sending requests?21:40
physcxare you deleting a specific 100k objects or are you removing all objects stored?21:41
tnewsomeSpecific objects.21:42
tnewsomeBasically delete-at isn't flexible enough for my application, and I'm expiring based on a different database.21:42
tnewsomeWith my naive implementation I'm deleting about 260 objects/minute.21:42
tnewsomeI suspect I could get to at least 1000 with multi-threading, but I haven't tested it.21:43
tnewsome(I'm not using http keep-alive because I'm limited to an ancient requests library currently.)21:43
physcxsorry I don't have any advice for that, I'm doing performance testing on some changes and routinely need to clear out all data so depending on how much is in there we either rm -rf on the disk or reformat as fastest way but thats not gonna help you lol21:44
shridoesn't bulk delete have ability to delete 1000 objects with just one request?21:44
shrireduces rtts21:44
tnewsomeshri: That sounds promising.21:45
notmynametnewsome: ya, bunk delete + concurrency + time21:46
tnewsomenotmyname: Is there any point to concurrency if bulk delete can do 1k at once?21:47
notmynameyes, if you want to do 2k at once ;-)21:47
tnewsomenotmyname: I assume that it would keep the db locked while processing.21:47
notmynamesorry, not meaning to be snarky :-)21:47
notmynameconcurrency is to make sure your network stays saturated21:47
tnewsomenotmyname: Snark is fine. :-)21:48
tnewsomenotmyname: I just figured my network would become relatively insignificant if the bulk is large enough.21:48
notmynametnewsome: ya, you've obviously got to balance the network saturation with your cpu saturation and your internal network congestion21:48
notmynametnewsome: so I guess it's actually bulk delete + time [+ concurrency]21:50
tnewsomeThe docstring for bulk.py is far more insightful than the manual online.21:51
tnewsomeAnd it does sound awesome. :-)21:51
notmynameya, I was just reminded that we need better client docs for the bulk middleware21:52
claygnotmyname: can we just give out dfg's cell phone number?21:52
notmynametnewsome: the docstring is automatically at http://docs.openstack.org/developer/swift/middleware.html#module-swift.common.middleware.bulk21:52
notmynameclayg:  :-)21:53
tnewsomenotmyname: Google sent me to http://docs.openstack.org/trunk/config-reference/content/object-storage-bulk-delete.html21:55
*** ams0 has joined #openstack-swift21:55
*** ams0 has quit IRC21:58
*** csd has joined #openstack-swift21:58
*** ams0 has joined #openstack-swift21:58
*** ams0 has quit IRC22:03
*** zul has quit IRC22:03
*** krtaylor has quit IRC22:10
portantenotmyname: not sure I am actually doing anything useful with this in-process functional test stuff, perhaps we can/should ask chmouel to help me here?22:11
portanteSee https://review.openstack.org/9217422:12
openstackgerritA change was merged to openstack/swift: Adding functional tests for Storage Policy  https://review.openstack.org/8726522:21
notmynameportante: I see it, but I don't think I have any more insights that you on it22:21
portantenotmyname: k thanks22:21
*** zul has joined #openstack-swift22:24
* notmyname was hoping portante would have it all figured out soon so notmyname could learn how to set up the community qa cluster stuff from him22:24
portante;)22:24
portantegood luck with that22:24
*** ams0 has joined #openstack-swift22:26
notmynameI've had that on my todo list for a while now, but other things have kept me busy.22:27
*** zul has quit IRC22:39
*** fbo_away is now known as fbo22:46
*** byeager has joined #openstack-swift22:47
*** byeager_ has quit IRC22:48
openstackgerritClay Gerrard proposed a change to openstack/swift: cleanup policy parsing a bit more  https://review.openstack.org/8707822:55
*** byeager_ has joined #openstack-swift23:01
*** byeager has quit IRC23:01
*** byeager_ has quit IRC23:01
*** mkollaro has quit IRC23:10
*** ams0_ has joined #openstack-swift23:13
*** ams0_ has quit IRC23:15
*** ams0_ has joined #openstack-swift23:15
portantenotmyname: thanks for jumpin there23:17
*** ams0 has quit IRC23:17
notmynameportante: looks like clarkb may have fixed it?23:17
portantecool23:19
*** ams0_ has quit IRC23:20
openstackgerritA change was merged to openstack/swift: Fix X-Backend-Storage-Policy-Index requests  https://review.openstack.org/9092923:24
openstackgerritA change was merged to openstack/swift: Fix recursive Policy patching  https://review.openstack.org/9093023:24
openstackgerritA change was merged to openstack/swift: Cleanup container update headers in obj server tests  https://review.openstack.org/9093123:24
claygpeluse_: oh yeah, the container_sync test... i'm trying fix that up now - I think it was just a merge race.23:37
*** nmap911 has joined #openstack-swift23:41
nmap911Evening23:41
nmap911Is there a swift mailing list?23:42
claygfolks mostly just use openstack-dev put [swift] in the subject or w/e23:42
nmap911Is that mailing list ment mainly for code/development discussion? I'd like to get some feedback on performance results im getting out of my dev deployment, to confirm whether its whats expected23:44
*** bill_az has joined #openstack-swift23:46
openstackgerritA change was merged to openstack/swift: Fix coverage report for newer versions of coverage  https://review.openstack.org/9014423:46
nmap911I just found ask.openstack - i think i'll stick it up there. thanks for your time23:47

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