Monday, 2015-08-24

*** haomaiwang has quit IRC00:01
*** haomaiwang has joined #openstack-swift00:01
*** Kennan2 is now known as Kennan00:02
openstackgerritMatt Riedemann proposed openstack/python-swiftclient: Update from global requirements  https://review.openstack.org/21578600:28
*** dmorita has joined #openstack-swift00:28
openstackgerritMatt Riedemann proposed openstack/python-swiftclient: Update from global requirements  https://review.openstack.org/21578600:44
*** lyrrad has joined #openstack-swift00:54
*** lyrrad has quit IRC00:58
*** lyrrad has joined #openstack-swift00:59
*** haomaiwang has quit IRC01:01
*** haomaiwang has joined #openstack-swift01:02
*** ccavanna_ has joined #openstack-swift01:04
*** ccavanna has quit IRC01:06
*** haomaiwang has quit IRC01:16
*** abhirc has joined #openstack-swift01:43
*** haomaiwang has joined #openstack-swift01:54
*** haomaiwang has quit IRC01:54
*** haomaiwang has joined #openstack-swift01:54
*** haomaiwang has quit IRC02:01
*** haomaiwang has joined #openstack-swift02:02
*** Kennan has quit IRC02:02
*** Kennan has joined #openstack-swift02:02
openstackgerritKazuhiro MIYAHARA proposed openstack/swift: Fix dispersion-reports error message  https://review.openstack.org/21369702:10
*** jamielennox is now known as jamielennox|away02:20
*** abhirc has quit IRC02:23
*** jamielennox|away is now known as jamielennox02:32
*** nakagawamsa has joined #openstack-swift02:53
*** haomaiwang has quit IRC03:01
*** haomaiwang has joined #openstack-swift03:02
*** dododo has quit IRC03:11
*** openstackgerrit has quit IRC03:31
*** openstackgerrit has joined #openstack-swift03:31
*** haomaiwang has quit IRC04:01
*** jrichli has quit IRC04:01
*** haomaiwang has joined #openstack-swift04:02
*** ppai has joined #openstack-swift04:09
*** silor has joined #openstack-swift04:36
*** SkyRocknRoll has joined #openstack-swift04:39
*** silor has joined #openstack-swift04:40
*** SkyRocknRoll has quit IRC04:41
*** SkyRocknRoll has joined #openstack-swift04:42
*** silor1 has joined #openstack-swift04:43
*** silor has quit IRC04:45
*** silor1 is now known as silor04:45
*** SkyRocknRoll has quit IRC04:46
*** SkyRocknRoll has joined #openstack-swift04:46
*** haomaiwang has quit IRC05:01
*** haomaiwang has joined #openstack-swift05:02
*** hrou has quit IRC05:02
*** SkyRocknRoll has quit IRC05:08
jith_janonymous: Thanks05:18
*** mahatic has joined #openstack-swift05:18
*** pberis has joined #openstack-swift05:30
jith_hi all i am getting an error "ImportError: No module named pbr.version " when i do swift-init all restart.. all services except proxy server got restarted.. can anyone guide me pls?05:31
mahaticjith_: did you run this? sudo pip install -r swift/test-requirements.txt05:44
mahaticand also the requirements?05:44
*** jamielennox is now known as jamielennox|away05:47
*** haomaiwang has quit IRC06:01
jith_mahatic: yes i did06:01
*** haomaiwang has joined #openstack-swift06:02
jith_when i try to install pbr again.. It populated a msg " sudo pip install pbr06:02
jith_Requirement already satisfied (use --upgrade to upgrade): pbr in /home/stack/python-swiftclient/pbr-1.5.0-py2.7.egg06:02
jith_Cleaning up..."06:02
mahaticwhich os are you using?06:03
*** pberis has quit IRC06:15
jith_not ubuntu.. it is debian based flavor.. but its almost equivalent to ubuntu 14.0406:22
*** iepupp has joined #openstack-swift06:25
jith_mahatic:06:29
jith_uname -a06:29
jith_Linux ajitha 3.16.0-4-amd64 #1 SMP Debian 3.16.7-2 (2014-11-06) x86_64 GNU/Linux06:29
*** xnox has joined #openstack-swift06:33
*** remix_tj has joined #openstack-swift06:35
openstackgerritNakagawa Masaaki proposed openstack/swift: SAIO on Ubuntu 14.04 can not pass unittest.  https://review.openstack.org/20779006:44
*** SkyRocknRoll has joined #openstack-swift06:47
*** akle has joined #openstack-swift06:51
*** haomaiwang has quit IRC07:01
*** 7JTAAJDYR has joined #openstack-swift07:02
*** rledisez has joined #openstack-swift07:04
*** haigang has joined #openstack-swift07:05
*** haigang has quit IRC07:06
*** I has joined #openstack-swift07:06
*** I is now known as Guest6305707:07
*** Guest63057 has quit IRC07:07
*** haigang has joined #openstack-swift07:07
*** haigang has quit IRC07:09
*** haigang has joined #openstack-swift07:10
*** SkyRocknRoll has quit IRC07:16
onovyhi, almost "one liner" change review, someone? :) https://review.openstack.org/#/c/210736/ thanks07:26
openstackgerritMerged openstack/swift: Enable Object Replicator's failure count in recon  https://review.openstack.org/13834207:32
*** jordanP has joined #openstack-swift07:51
*** mahatic has quit IRC07:52
*** 7JTAAJDYR has quit IRC08:01
*** haomaiwang has joined #openstack-swift08:02
*** haigang has quit IRC08:06
*** mahatic has joined #openstack-swift08:15
*** jistr has joined #openstack-swift08:17
*** geaaru has joined #openstack-swift08:18
*** joeljwright has joined #openstack-swift08:25
*** ChanServ sets mode: +v joeljwright08:25
*** dmorita has quit IRC08:32
*** silor1 has joined #openstack-swift08:37
*** silor has quit IRC08:39
*** silor1 is now known as silor08:39
*** jistr has quit IRC08:45
*** jistr has joined #openstack-swift08:47
*** sanchitmalhotra has joined #openstack-swift08:48
*** sanchitmalhotra has quit IRC08:51
*** sanchitmalhotra has joined #openstack-swift08:57
mahaticacoles: hello! around?09:00
*** haomaiwang has quit IRC09:01
*** haomaiwang has joined #openstack-swift09:01
*** sanchitmalhotra1 has joined #openstack-swift09:06
acolesmahatic: hi09:07
*** jistr has quit IRC09:08
*** sanchitmalhotra has quit IRC09:08
mahaticacoles: where would I set a default value for a header? (for encrypt flag in keymaster). Right now, if I add a header in one of the failing tests and check in keymaster for the header, it works. But I need to set it to a defualt value - so that I don't have to modify existing tests (like you've suggested)09:10
mahaticdoes it sound out of the blue? :)09:12
acolesmahatic: i guess you would need to set the default value where you need to read the value, so keymaster perhaps?09:13
acolesmahatic: also, just a guess, but you might find the config_true_value method useful in utils09:14
acolesmahatic: swift/common/utils.py:27209:16
janonymousjith_ : Sure, no problem.09:17
acolesmahatic: its a useful helper to accept any true-like string from a value, in this case possibly your header value09:17
mahaticacoles: right, thanks. Looked at that. I don't think I can set the header value in keymaster itself, I check the incoming headers from req and verify it's value09:19
acolesmahatic: so, if the header is not found in the req can you not then assume a default value09:20
*** aix has joined #openstack-swift09:20
acolesmahatic: something like req.headers.get('MY-Header-Name', my_default_value) ??09:20
mahaticacoles: oh maybe my question should be, how do I add a default header to a req? or is not necessary?09:20
mahaticacoles: okay, I could try the default value you mentioned. I was just wondering, if I need to introduce a header - is there a specific common place for it? or is it just according to my need (like what I'm doing now)09:24
acolesmahatic: there is no canonical list of all swift headers. you don't need to add a default to the request class, just handle the default where you use the header.09:29
mahaticacoles: okay, great. thanks! yes, the default thing seems to be working (I'm running tests)09:31
acolescool09:31
mahaticacoles: how's your monday coming by? Do you work out of an office or home?09:34
acolesmahatic: ok thanks, today i'm in office, most days the same09:36
mahaticah okay09:37
acolesmattoliverau: you make it home?09:37
mattoliverauacoles: yup home safe and sound :)09:38
mahaticmattoliverau: good evening!09:38
mattoliveraumahatic: o/09:39
acoleshmmm, swiftclient tox -e pep8 is no longer enforcing max line length ?!?09:41
acolessince hacking version got bumped09:42
mahaticoh, interesting (didn't know it was because of hacking)09:48
* mahatic is off for a while - be back in an hour or so09:48
*** mahatic has quit IRC09:49
acolescorrelation != causation, but...09:49
openstackgerritOpenStack Proposal Bot proposed openstack/swift: Updated from global requirements  https://review.openstack.org/8873609:53
openstackgerritAlistair Coles proposed openstack/python-swiftclient: Add minimal working service token support.  https://review.openstack.org/18264009:54
*** haomaiwang has quit IRC10:01
*** haomaiwang has joined #openstack-swift10:02
*** SkyRocknRoll has joined #openstack-swift10:05
*** Kennan has quit IRC10:09
*** Kennan has joined #openstack-swift10:10
*** kei_yama has quit IRC10:11
*** aix has quit IRC10:15
*** marzif has joined #openstack-swift10:31
*** ekarlso has quit IRC10:32
*** ekarlso has joined #openstack-swift10:32
*** km has quit IRC10:35
*** aix has joined #openstack-swift10:48
*** donagh has quit IRC10:50
*** jamielennox|away has quit IRC10:50
*** jistr has joined #openstack-swift10:52
*** sudorandom has quit IRC10:56
*** SkyRocknRoll has quit IRC10:56
*** zul has quit IRC10:56
*** CrackerJackMack has quit IRC10:56
*** zacksh has quit IRC10:56
*** jroll has quit IRC10:56
*** zacksh has joined #openstack-swift10:58
*** bkopilov has quit IRC10:59
*** bkopilov has joined #openstack-swift11:00
*** haomaiwang has quit IRC11:01
*** sudorandom has joined #openstack-swift11:01
*** CrackerJackMack has joined #openstack-swift11:01
*** haomaiwang has joined #openstack-swift11:02
*** jroll has joined #openstack-swift11:02
*** jamielennox|away has joined #openstack-swift11:04
*** jamielennox|away is now known as jamielennox11:04
*** donagh has joined #openstack-swift11:05
openstackgerritAlistair Coles proposed openstack/python-swiftclient: Make tox -e pep8 check for lines being too long  https://review.openstack.org/21619211:05
*** abhirc has joined #openstack-swift11:18
*** lpabon has joined #openstack-swift11:19
*** iepupp has quit IRC11:28
*** nakagawamsa has quit IRC11:42
*** haomaiwang has quit IRC11:55
*** ppai has quit IRC12:02
*** ppai has joined #openstack-swift12:12
*** abhirc has quit IRC12:22
*** lpabon_ has joined #openstack-swift12:24
*** lpabon has quit IRC12:24
*** ppai has quit IRC12:26
*** daemontool__ has joined #openstack-swift12:27
*** daemontool_ has quit IRC12:29
*** jrichli has joined #openstack-swift12:30
*** jistr has quit IRC12:31
*** jistr has joined #openstack-swift12:33
*** petertr7_away is now known as petertr712:37
*** zul has joined #openstack-swift12:39
*** dustins has joined #openstack-swift12:42
openstackgerritAlistair Coles proposed openstack/python-swiftclient: Stop Connection class modifying os_options parameter  https://review.openstack.org/21624012:43
*** chlong has joined #openstack-swift12:47
*** mahatic has joined #openstack-swift12:49
*** chlong has quit IRC12:54
*** annegentle has joined #openstack-swift13:05
*** lpabon_ has quit IRC13:08
*** annegentle has quit IRC13:08
*** annegentle has joined #openstack-swift13:08
*** dustins has quit IRC13:10
*** dustins has joined #openstack-swift13:11
*** hrou has joined #openstack-swift13:11
*** chlong has joined #openstack-swift13:13
*** dustins has quit IRC13:18
*** ccavanna_ has quit IRC13:18
*** dustins has joined #openstack-swift13:19
*** haomaiwa_ has joined #openstack-swift13:21
*** jroll has quit IRC13:23
*** dustins has quit IRC13:25
*** jith_ has quit IRC13:25
*** jamielennox has quit IRC13:26
*** donagh has quit IRC13:26
*** SkyRocknRoll has joined #openstack-swift13:27
*** bapalm_ has joined #openstack-swift13:28
*** dustins has joined #openstack-swift13:29
*** wbhuber has joined #openstack-swift13:31
*** links has joined #openstack-swift13:31
*** jordanP has quit IRC13:34
*** petertr7 is now known as petertr7_away13:36
*** jroll has joined #openstack-swift13:37
*** donagh has joined #openstack-swift13:40
*** jamielennox|away has joined #openstack-swift13:43
*** jamielennox|away is now known as jamielennox13:43
mahaticacoles: get_container and head_container (in swift client - client.py) do not accept headers, do you know if I could add them? or is there a process for it? (I'm aware swift-client has a diff core)13:46
acolesmahatic: you can add them, just propose a patch to swifclient.13:47
mahaticacoles: okay, thanks13:47
acolesmahatic: swiftclient cores are superset of swift cores13:47
mahaticacoles: ah okay13:47
*** petertr7_away is now known as petertr713:57
*** haomaiwa_ has quit IRC14:01
*** haomaiwang has joined #openstack-swift14:02
*** sanchitmalhotra1 has quit IRC14:05
*** ccavanna has joined #openstack-swift14:07
*** lpabon has joined #openstack-swift14:07
*** jamielennox has quit IRC14:08
*** jordanP has joined #openstack-swift14:10
*** jamielennox|away has joined #openstack-swift14:10
*** jamielennox|away is now known as jamielennox14:11
*** marzif has quit IRC14:11
*** lpabon has quit IRC14:11
*** marzif has joined #openstack-swift14:12
*** petertr7 is now known as petertr7_away14:20
*** kairo has joined #openstack-swift14:25
*** petertr7_away is now known as petertr714:25
*** jlhinson has joined #openstack-swift14:33
*** jlhinson has quit IRC14:35
*** alejandrito has joined #openstack-swift14:37
*** bapalm_ has quit IRC14:41
*** pgbridge has quit IRC14:44
*** bapalm- has joined #openstack-swift14:45
*** pgbridge has joined #openstack-swift14:49
*** annegentle has quit IRC14:52
*** haomaiwang has quit IRC15:01
*** haomaiwa_ has joined #openstack-swift15:02
*** minwoob has joined #openstack-swift15:02
*** flwang has joined #openstack-swift15:04
flwangcschwede: ping15:04
cschwedeflwang: pong15:08
flwangcschwede: hi, there is Feilong from zaqar team. just want to chat about this https://review.openstack.org/#/c/196755/15:09
flwangthe notification middleware of swift15:09
flwangcschwede: are you still working on that? do you need any help from our side?15:09
cschwedeflwang: yes, still working on it. going to send another update this week15:10
flwangcschwede: awesome, and we will also keep an eye on that and provide feedback from our side. thanks for working on this15:11
cschwedeflwang: thanks, i appreciate it :)15:13
*** zaitcev has joined #openstack-swift15:21
*** ChanServ sets mode: +v zaitcev15:21
*** haomaiwa_ has quit IRC15:22
*** mfalatic has joined #openstack-swift15:24
*** annegentle has joined #openstack-swift15:25
*** lyrrad has quit IRC15:35
*** nadeem has joined #openstack-swift15:35
*** jistr has quit IRC15:35
*** david-ly_ is now known as david-lyle15:38
*** jistr has joined #openstack-swift15:38
*** SkyRocknRoll has quit IRC15:48
*** alejandrito has quit IRC15:53
*** gyee has joined #openstack-swift15:54
*** petertr7 is now known as petertr7_away15:56
*** jlhinson has joined #openstack-swift15:57
*** links has quit IRC16:08
*** thumpba has joined #openstack-swift16:12
*** jistr has quit IRC16:13
*** marzif has quit IRC16:18
minwoobAll right -- so I know that EC policy is counter-productive when object size is less than the chunk size, but does that apply to objects larger than the chunk size, but still small in size?16:19
minwoobBasically, is the lower bound that is acceptable for EC actually higher than the specified chunk size?16:20
minwoobAnd is there an actual (formulaically definable) limit, or none?16:23
*** jordanP has quit IRC16:24
minwoob(This is for anyone who wants to participate in coming up with an auto-tiering strategy based on size).16:24
*** BAKfr has quit IRC16:25
*** BAKfr has joined #openstack-swift16:26
*** lpabon has joined #openstack-swift16:27
*** rledisez has quit IRC16:28
egonminwoob: how are you using "chunk size" in this context? I mean, how does it relate to block length and message length?16:29
minwoobegon: I mean the size of a segment before it gets encoded.16:29
minwoobegon: If you apply EC to such an object, you get more storage overhead than if you were to have used replication.16:30
minwoobegon: At the very least, it requires padding to the object with the current implementation.16:30
egonYes, it's the same problem as file sizes below a filesystem block size.16:31
peluseminwoob, I think you mean segment size there wrt your very first comment16:31
*** lpabon has quit IRC16:31
notmynamegood morning16:31
pelusenotmyname, morning!16:31
egonnotmyname: morning!16:31
minwoobnotmyname: Good morning!16:31
peluseminwoob, terminology in the EC implementation is pretty specific and if you use the wrong word (liek we did many times early on) it can get very confusing16:31
minwoobpeluse: Yes, exactly.16:31
minwoobpeluse: Yeah, what I meant was segment size in that comment above.16:32
peluseminwoob, we don't pad to segment size though and it is configurable.  We're running some tests this week to help characterize segment size vs object size wrt performance/efficiency16:34
wbhuberpeluse: with the same definition files that Bill G. sent to us awhile ago?16:34
wbhuberpeluse: do your tests include saturating the network while the workloads are running to see how the policies handle storing objects?16:37
pelusewbhuber, yup16:37
pelusewbhuber, the yes was to your first question, not sure I understand the 2nd16:38
wbhuberpeluse: for example full cluster16:40
wbhuberwith the disks at full capacity (prob same effects as replica though)16:40
pelusewbhuber, all: basically what we're doing w/EC this week in Phx i doing baseline stress testing of various sizes on a 16 node clsuter (2 proxy 1 LB 14 SN).  Making sure things work, testing some of the outstanding patches, testing some eror scenarios (as many as we can get to)16:41
peluse...and then leaving the working cluster for our benchmarking team to run repl vs Ec tests (which they tried to do before but ran into too many issues)16:41
peluseso if anyone has any suggestions (like wbhuber just did) please let us know!16:42
pelusewbhuber, doubt we'll do a cluster full test this week.  focusing on (1) heavy load w/o failure (2) heavy load w/node failures (3) reconstructor scenarios (4) some parm tuing (like segment size)16:43
wbhuberpeluse: noticed that in your cluster config, what do you expect from an LB?  handling network bottlenecks?16:44
pelusewbhuber, we expect it to balance traffic over our 2 proxies :)16:44
egonwe're not playing with EC yet, and are running an older version of swift, but we have 8 proxy nodes.16:45
*** marcusvrn_ has joined #openstack-swift16:45
egonand same here, we expect to balance traffic16:45
*** barker has joined #openstack-swift16:53
wbhuberpeluse: are those nodes straight bare metal (i.e. not VMs)?17:01
*** barker has quit IRC17:01
*** kevinc_ has joined #openstack-swift17:05
*** marzif has joined #openstack-swift17:12
*** barker has joined #openstack-swift17:12
*** mahatic has quit IRC17:13
*** marzif has quit IRC17:17
*** petertr7_away is now known as petertr717:20
*** aix has quit IRC17:20
*** bi_fa_fu has joined #openstack-swift17:23
*** jrichli has quit IRC17:24
*** barker has quit IRC17:24
*** barker has joined #openstack-swift17:26
*** barker has quit IRC17:33
pelusewbhuber, yes, no VMs anywhere17:41
pelusectennis will post pics of our config here shortly17:43
*** geaaru has quit IRC17:44
*** bkopilov has quit IRC17:44
*** bkopilov has joined #openstack-swift17:45
ctennishttp://i.imgur.com/FS8o5Uh.png17:48
clayggood morning17:55
peluseclayg, yo!17:55
ctennisand http://i.imgur.com/Vt7wuRb.png17:57
*** bi_fa_fu has quit IRC17:58
claygctennis: both of those setups look great!17:58
claygctennis: can you plug them both *together*!?17:59
egonctennis: is that the intel reference deployment?17:59
ctennisyes17:59
peluseclayg, yeah its going well.  we are currently running patch 199043 on all nodes17:59
patchbotpeluse: https://review.openstack.org/#/c/199043/17:59
claygpeluse: yeah that's a nice fix - we really need to get that one in :\18:00
peluseclayg, they are 2 different clusters totally.  we are using the xeon one right now18:00
claygpeluse: what about the etag_buckets change - that one is pretty good too!18:00
egonctennis: the backend is straight swift, not ceph, or something?18:00
peluseclayg, I will be ready to +2 it with a little bit of back history :)  Its super tiny but I don't totally understand it18:00
ctennisyeah this is straight swift18:01
torgomaticminwoob: what do you mean by padding? there's some EC headers, but just because you use a 1 MiB EC chunk size doesn't mean all your stuff gets padded to 1 MiB18:01
peluseclayg, we are going to run with the etag buckets patch after we get done running a bunch of baseline stress testing - will fire that up probably after lunch18:02
claygpeluse: ah ok - cool!18:02
peluseclayg, because that's when we'll start inducing some failures and need it...18:03
claygpeluse: hehe18:06
peluseBTW cluster running almost nonstop since yesterday morning, various workloads, no exceptions/errors to report so far...18:08
*** bkopilov has quit IRC18:08
claygwhy does swiftclient still get to have a whitelist of H checks?  https://review.openstack.org/#/c/21619218:09
claygand why doesn't it have Flake8 checks (select = F) ???18:10
*** corvus is now known as jeblair18:13
acolesclayg: i have no idea what is going on with those flake tests. i was just 'how did this merge?'!!18:15
*** bapalm- is now known as bapalm_18:19
openstackgerritClay Gerrard proposed openstack/swift: Use correct Storage-Policy header for REPLICATE requests  https://review.openstack.org/21585718:20
timburkeclayg: it shouldn't, the whitelist doesn't work right. go review https://review.openstack.org/#/c/202909/ if you want swiftclient to have a sane pep8 check :P18:22
openstackgerritAlistair Coles proposed openstack/swift: Enable object server to return non-durable data  https://review.openstack.org/21527618:22
acolestimburke: darn i didnt spot that patch18:24
openstackgerritClay Gerrard proposed openstack/swift: Make handoffs_first a more useful "mode"  https://review.openstack.org/21586718:25
acolespeluse: clayg: i lost track where patch 212187 is at - shoudl i be reviewing what is there or is there a change in the works?18:27
patchbotacoles: https://review.openstack.org/#/c/212187/18:27
claygacoles: I think peluse is busy this week and it's not quite ready for merge18:28
claygacoles: there's a couple of fix ups in patch 21536018:29
patchbotclayg: https://review.openstack.org/#/c/215360/18:29
claygacoles: maybe sanity that diff for me and I'll squash it down into the other for a proper review18:29
claygacoles: what's the status on patch 215276 - ready for review?18:29
patchbotclayg: https://review.openstack.org/#/c/215276/18:29
*** jrichli has joined #openstack-swift18:30
claygit looks like it's two or three changes down the line from master - so there's probably gunna be some rebases - if you're happy with the changes and I break it during your overnight I'll try to keep it rebased for you18:31
claygacoles: if you're still working on it anyway I'll probably just leave it busted for you18:31
acolesclayg:  patch 215276 is ready for review. its not much use without the corresponding proxy changes but you can at least tell me it sucks :P18:32
patchbotacoles: https://review.openstack.org/#/c/215276/18:32
claygacoles: full-ack18:33
acolesclayg: i'm done for today and happy to rebase. i'll look at 215360 tomorrow, sorry if idint notice that18:33
claygacoles: can you star patch 215317 too - it's a cheap one18:33
patchbotclayg: https://review.openstack.org/#/c/215317/18:33
minwoobtorgomatic: I see. If that's the case, then yeah, padding is not an issue.18:33
acoless/if idint/i didnt/18:33
claygacoles: no it's ok, don't worry about that - i'm pretty sure *I* like it better at least - i'm going to squash it over patch 212187 and change etag_buckets to timestamp_buckets anyway18:34
patchbotclayg: https://review.openstack.org/#/c/212187/18:34
acolesclayg: sure18:34
acolesclayg: sure re 215317 but tomorrow sorry18:35
acolesclayg: yeah i'm pretty convinced we should be comparing timestamps across the frag set18:35
claygmattoliverau: the commit message on patch 117710 sounds great!18:36
patchbotclayg: https://review.openstack.org/#/c/117710/18:36
acolesclayg: even if etags match the metadata could be different on different time'd frags18:36
claygacoles: ok i'll do it then - have a good night18:36
claygacoles: thanks for working late for the handoff!  get out of there!18:37
openstackgerritMichael Barton proposed openstack/swift: go: O_TMPFILE  https://review.openstack.org/21637518:39
joeljwrightIs there any chance of some people casting their eyes over patch 130339 and patch 171692 please18:43
patchbotjoeljwright: https://review.openstack.org/#/c/130339/18:43
joeljwrightjust for patchbot patch 17169218:43
patchbotjoeljwright: https://review.openstack.org/#/c/171692/18:43
joeljwrightthey've been sitting around for some time18:43
joeljwrightwould like to get them done and merged18:44
joeljwrightbut I'm aware that not many people have looked too hard at them18:44
claygredbo: wohoooo O_TMPFILE!18:45
acolesjoeljwright: ack will try to find some time18:46
claygredbo: can I trick anyone at the rax into looking at matts' patch for concurrent gets?  patch 11771018:46
patchbotclayg: https://review.openstack.org/#/c/117710/18:46
joeljwrightacoles: thanks18:46
acolesgood night18:47
redboI don't know how tricky you can be!18:48
*** DericHorn-HP has joined #openstack-swift18:50
tdasilvaredbo, clayg: or maybe patch 162243 ???18:53
patchbottdasilva: https://review.openstack.org/#/c/162243/18:53
tdasilva:D18:53
*** bkopilov has joined #openstack-swift18:59
*** acoles is now known as acoles_19:01
*** bkopilov has quit IRC19:09
*** bkopilov has joined #openstack-swift19:11
*** annegent_ has joined #openstack-swift19:12
claygredbo: fine don't review it - see if I care19:16
* clayg tries reverse trickery19:16
*** annegentle has quit IRC19:16
redboI bet you don't even know how to review it19:16
claygredbo: I've reviewed it once before - it was a bunch of work - i had to setup dfg's slowdown (https://github.com/dpgoetz/slowdown)19:21
claygredbo: but that's how I found the first round of bugs - maybe some of them are fixed - idk19:21
claygI sorta don't want to look - if it's still broken I'll just have to -1 it - and *then* what did I accomplish?19:22
* clayg thinks he's not selling this review work to redbo very well :\19:22
*** petertr7 is now known as petertr7_away19:25
*** petertr7_away is now known as petertr719:29
redboI mean we could just blindly approve it, then we'll find all the problems 6 months or a year from now when we actually deploy the current code.19:35
claygredbo: ok, well this was fun - nm19:35
clayg:)19:35
*** zul has quit IRC19:49
*** kutija has joined #openstack-swift20:03
*** bkopilov has quit IRC20:03
*** annegent_ has quit IRC20:07
*** bkopilov has joined #openstack-swift20:07
*** annegentle has joined #openstack-swift20:07
*** silor has quit IRC20:15
*** DericHorn-HP has quit IRC20:20
openstackgerritMerged openstack/swift: Fix the missing SLO state on fast-post  https://review.openstack.org/18256420:22
*** jlhinson_ has joined #openstack-swift20:22
*** jlhinson has quit IRC20:25
*** akle has quit IRC20:31
*** jerrygb has joined #openstack-swift20:33
*** jerrygb is now known as test0rz20:34
*** test0rz is now known as asd112z20:34
*** petertr7 is now known as petertr7_away20:42
*** dustins has quit IRC20:47
*** ccavanna has quit IRC20:59
*** then3rd has joined #openstack-swift21:01
then3rdIt appears that telemetry meters storage.objects.{incoming,outgoing}.bytes. My question: is there any way to measure bandwidth per object in each container?21:02
claygthen3rd: post-facto log processing21:03
claygthen3rd: like, you don't *really* want a metric name per object do you?  ... maybe you do21:03
then3rdI would imagine that many metrics could become quite cumbersome.21:04
claygok, just checking21:04
then3rdI'm sort of spitballing ideas right now. Being so new to swift/openstack, I'm not sure where to start first. What logging mechanisms can gather what I need for processing?21:06
*** nadeem has quit IRC21:07
claygproxy access logs - most folks keep 'em around "forever" (normally compressed and put back into swift) - you can pull them out and split them up (or index them) - it's a stable form => http://docs.openstack.org/developer/swift/logs.html#proxy-logs21:08
claygthe "request_path" part will have the /account/container/object - the bytes_[sent|recvd] has the 'bandwidth" stuff you were looking for21:09
openstackgerritTim Burke proposed openstack/swift: Fix use of delimiter in account listings  https://review.openstack.org/21642721:09
claygthen3rd: still - anything in swift "per object" is a large amount of keys :\21:10
*** jodah has joined #openstack-swift21:11
*** rook][ has joined #openstack-swift21:13
then3rdclayg: Awesome, I belive that gives me something to run with. I'll probably be back with more questions sooner or later. :) Thanks!21:13
claygthen3rd: absolutely!  come on by anytime!21:14
claygtimburke: I think maybe the fix from patch 28069 circa 2013 was just never extended to accounts?  Like maybe, it didn't regress - it just never worked?  re patch 21642721:20
patchbotclayg: https://review.openstack.org/#/c/28069/21:20
*** hrou has quit IRC21:20
*** nadeem has joined #openstack-swift21:21
*** trifon has joined #openstack-swift21:23
timburkeclayg: oh yeah, you might be right...i'll fix up the commit message21:33
openstackgerritTim Burke proposed openstack/swift: Fix use of delimiter in account listings  https://review.openstack.org/21642721:34
*** rook][ has quit IRC21:40
*** abhirc has joined #openstack-swift21:47
*** abhirc has quit IRC21:47
*** abhirc has joined #openstack-swift21:48
notmynamethen3rd: https://github.com/notmyname/slogging is something you could look at for processing swift logs21:57
*** chlong has quit IRC22:00
*** pgbridge has quit IRC22:03
*** ujjain has quit IRC22:04
*** ujjain has joined #openstack-swift22:07
*** ujjain has joined #openstack-swift22:07
*** joeljwright has quit IRC22:10
mattoliverauMorning22:13
*** ccavanna has joined #openstack-swift22:13
*** marcusvrn_ has quit IRC22:15
*** chlong has joined #openstack-swift22:15
*** ho has joined #openstack-swift22:16
notmynamegood morning mattoliverau22:16
briancline+1 for slogging22:17
brianclineit has aged well ;-)22:17
notmynamebriancline: good to hear :-)22:17
notmynamebriancline: are you using it too?22:18
*** jrichli has quit IRC22:18
brianclinenotmyname: yep, we are22:18
notmynamecool22:18
hogood morning!22:23
*** hrou has joined #openstack-swift22:24
*** kairo_ has joined #openstack-swift22:25
*** asd112z has quit IRC22:25
*** kairo has quit IRC22:27
mattoliverauho: morning22:33
homattoliverau: morning! and thanks for the review. it took 8 month :-)22:35
*** jlhinson_ has quit IRC22:35
*** nadeem has quit IRC22:36
mattoliverauLol22:37
*** chlong has quit IRC22:40
*** thumpba has quit IRC22:42
homattoliverau: hehe. thanks again!22:43
openstackgerritSamuel Merritt proposed openstack/swift: Make the object auditor's run-once mode run once.  https://review.openstack.org/21644922:43
*** minwoob has quit IRC22:43
*** hrou has quit IRC22:44
*** dmorita has joined #openstack-swift22:48
openstackgerritSamuel Merritt proposed openstack/swift: Disable pep8 check E127  https://review.openstack.org/21645022:48
*** chlong has joined #openstack-swift22:52
openstackgerritHisashi Osanai proposed openstack/swift: Fix typo of a comment in replicator  https://review.openstack.org/21645322:54
hoI read this: http://www.openkinetic.org/index.php?title=Kinetic_Open_Storage_Group . interesting! and swiftstack and redhat are members for it. do you have any info? (what is the relation with swift?)23:01
*** tongli has joined #openstack-swift23:02
notmynameho: (at swiftstack) we've worked on making swift work with kinetic drives23:11
honotmyname: cooool!!!!!23:11
honotmyname: Does swiftstack have the drives in your lab?23:13
notmynameho: yeah23:17
*** annegentle has quit IRC23:19
honotmyname: thanks! it's really cool!23:19
*** kei_yama has joined #openstack-swift23:25
*** lyrrad has joined #openstack-swift23:27
*** km has joined #openstack-swift23:34
*** EmilienM has quit IRC23:34
*** EmilienM has joined #openstack-swift23:37
*** flwang has quit IRC23:39
*** morganfainberg is now known as morgan23:42
claygtorgomatic: nice merge -> https://review.openstack.org/#/c/216453/23:46
clayg^ cc: anyone whos ever asked when is it ok for single core +A23:46
claygalso ho - thanks!23:46
notmynameho: nice! keystone in vSAIO :-)23:51
honotmyname: I won this race :-)23:52
honotmyname: I would like to do more update on it later.23:53
*** tongli has quit IRC23:54

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