Monday, 2015-11-23

*** sanchitmalhotra has joined #openstack-swift00:06
*** sanchitmalhotra1 has quit IRC00:08
*** changbl has joined #openstack-swift00:17
*** changbl has quit IRC00:17
*** changbl has joined #openstack-swift00:17
*** changbl has joined #openstack-swift00:18
*** changbl_ has joined #openstack-swift00:18
*** changbl has quit IRC00:19
*** sanchitmalhotra1 has joined #openstack-swift00:23
*** sanchitmalhotra has quit IRC00:26
*** changbl has joined #openstack-swift00:29
*** sanchitmalhotra has joined #openstack-swift00:37
*** sanchitmalhotra1 has quit IRC00:39
*** sanchitmalhotra1 has joined #openstack-swift00:43
*** sanchitmalhotra has quit IRC00:45
*** Guest27579 has quit IRC00:50
*** mac_ified has quit IRC00:57
*** sanchitmalhotra has joined #openstack-swift01:20
*** sanchitmalhotra1 has quit IRC01:22
*** asettle is now known as asettle-afk01:34
*** sanchitmalhotra1 has joined #openstack-swift01:38
*** sanchitmalhotra has quit IRC01:40
*** haomaiwang has joined #openstack-swift01:41
*** jerrygb has joined #openstack-swift01:44
*** haomaiwang has quit IRC02:01
*** haomaiwang has joined #openstack-swift02:01
*** jerrygb has quit IRC02:05
*** jerrygb has joined #openstack-swift02:05
*** jerrygb has quit IRC02:10
*** sanchitmalhotra has joined #openstack-swift02:15
*** sanchitmalhotra1 has quit IRC02:17
*** asettle-afk is now known as asettle02:22
*** sanchitmalhotra1 has joined #openstack-swift02:38
*** sanchitmalhotra has quit IRC02:40
*** haomaiwang has quit IRC03:01
*** haomaiwang has joined #openstack-swift03:01
*** jerrygb has joined #openstack-swift03:06
*** venkat_p has joined #openstack-swift03:06
*** proteusguy_ has quit IRC03:08
*** jerrygb has quit IRC03:11
*** sanchitmalhotra has joined #openstack-swift03:22
*** sanchitmalhotra1 has quit IRC03:24
*** proteusguy_ has joined #openstack-swift03:25
*** sanchitmalhotra1 has joined #openstack-swift03:33
*** sanchitmalhotra has quit IRC03:35
*** changbl has quit IRC03:38
*** sanchitmalhotra has joined #openstack-swift03:41
*** sanchitmalhotra1 has quit IRC03:43
*** wuhg has joined #openstack-swift03:55
*** haomaiwang has quit IRC04:01
*** haomaiwang has joined #openstack-swift04:01
*** Zyric1 has quit IRC04:03
*** tsg_ has quit IRC04:06
*** diazjf has joined #openstack-swift04:07
*** changbl has joined #openstack-swift04:07
*** sanchitmalhotra has quit IRC04:10
*** ppai has joined #openstack-swift04:22
openstackgerritMatthew Oliver proposed openstack/swift: Port swift.common.utils.Timestamp to Python 3  https://review.openstack.org/23701504:32
*** venkat_p has quit IRC04:43
*** trifon has joined #openstack-swift04:49
*** haomaiwang has quit IRC05:01
*** trifon has quit IRC05:01
*** haomaiwa_ has joined #openstack-swift05:01
openstackgerritMerged openstack/swift: Ignore Content-Type from client on multipart-manifest=delete  https://review.openstack.org/24818605:06
*** klrmn1 has quit IRC05:22
*** diazjf has quit IRC05:23
*** rcernin has joined #openstack-swift05:36
*** mwheckmann has joined #openstack-swift05:36
*** mwheckmann has quit IRC05:40
*** rcernin has quit IRC05:42
*** dimasot has joined #openstack-swift05:43
*** trifon has joined #openstack-swift05:44
*** diazjf has joined #openstack-swift05:48
*** haomaiwa_ has quit IRC06:01
*** 17WAA30H9 has joined #openstack-swift06:01
*** SkyRocknRoll has joined #openstack-swift06:05
*** silor has joined #openstack-swift06:06
*** kei_yama has quit IRC06:10
*** venkat_p has joined #openstack-swift06:14
*** mahatic has joined #openstack-swift06:38
*** silor1 has joined #openstack-swift06:46
*** eranrom has joined #openstack-swift06:47
*** silor has quit IRC06:48
*** silor1 is now known as silor06:48
*** mac_ified has joined #openstack-swift06:49
*** 17WAA30H9 has quit IRC07:01
*** haomaiwang has joined #openstack-swift07:01
*** pchng_ has joined #openstack-swift07:07
*** rcernin has joined #openstack-swift07:07
*** pchng has quit IRC07:09
*** openstack has joined #openstack-swift07:21
*** mahatic has joined #openstack-swift07:30
*** jerrygb has joined #openstack-swift07:51
*** mac_ified has quit IRC07:52
*** mac_ifie_ has joined #openstack-swift07:52
*** jerrygb has quit IRC07:57
*** hseipp has joined #openstack-swift08:00
*** haomaiwang has quit IRC08:01
*** haomaiwang has joined #openstack-swift08:01
*** hseipp has quit IRC08:11
*** diazjf has quit IRC08:11
*** arnox has joined #openstack-swift08:11
*** dimasot has quit IRC08:19
*** venkat_p has quit IRC08:31
*** haomaiwang has quit IRC08:32
openstackgerritEran Rom proposed openstack/swift: Add thread level concurrency to container sync  https://review.openstack.org/22533808:33
*** haomaiwang has joined #openstack-swift08:36
*** ppai_ has joined #openstack-swift08:40
*** ppai has quit IRC08:44
*** venkat_p has joined #openstack-swift08:49
*** jordanP has joined #openstack-swift08:52
*** haomaiwang has quit IRC09:01
*** haomaiwang has joined #openstack-swift09:01
*** mahatic has quit IRC09:08
*** SkyRocknRoll has quit IRC09:15
*** joeljwright has joined #openstack-swift09:25
*** ChanServ sets mode: +v joeljwright09:25
*** jistr has joined #openstack-swift09:27
*** aix has joined #openstack-swift09:43
*** SkyRocknRoll has joined #openstack-swift09:44
*** dimasot has joined #openstack-swift09:46
*** aix has quit IRC09:52
*** mahatic has joined #openstack-swift09:57
*** ekarlso- has joined #openstack-swift09:59
*** ekarlso has quit IRC10:00
*** ekarlso- is now known as ekarlso10:00
*** haomaiwang has quit IRC10:01
*** haomaiwang has joined #openstack-swift10:01
*** jerrygb has joined #openstack-swift10:08
*** jerrygb has quit IRC10:13
mahaticacoles_: around?10:14
*** daemontool has joined #openstack-swift10:19
*** aix has joined #openstack-swift10:24
*** Guest99452 has quit IRC10:33
*** daemontool has quit IRC10:34
*** daemontool has joined #openstack-swift10:35
openstackgerritMerged openstack/swift: Transition to 'keymaster'  https://review.openstack.org/24490410:53
*** Fuz1on has joined #openstack-swift10:56
Fuz1onHello all10:56
Fuz1onis anybody there ?10:56
*** hseipp has joined #openstack-swift10:56
Fuz1oni got a question about log_custom_handlers, i dont really know where to put my logger ?10:57
Fuz1oni guess it's in /usr/lib/pythonX.X/dist-packages/swift10:57
Fuz1onbut i'm not really sure10:57
*** haomaiwang has quit IRC11:01
*** haomaiwang has joined #openstack-swift11:01
*** NM has joined #openstack-swift11:04
Fuz1oni'll give it a try11:05
Fuz1onl will mimic the sentry logger11:05
*** yatin has joined #openstack-swift11:05
*** haomaiwang has quit IRC11:07
*** jmccarthy has quit IRC11:24
*** jmccarthy has joined #openstack-swift11:25
openstackgerritAlistair Coles proposed openstack/swift: Decrypting Container Listing  https://review.openstack.org/21443811:34
*** acoles_ is now known as acoles11:34
acolesmahatic: hi11:35
mahaticacoles: hello! are you back? jusitce done? :)11:36
acolesmahatic: yes back to normal11:37
mahaticacoles: cool, do you have a few mins to chat about content-type encryption?11:38
acolessure11:39
acolesmahatic: sure11:39
mahaticacoles: great. 1) crypto-meta is getting stripped off in response here: https://github.com/openstack/swift/blob/master/swift/common/swob.py#L40311:39
mahaticacoles: I was wondering, if it is okay to put a condition there to check for "; meta=" in there and pass along if that is true11:40
mahaticacoles: for some context: I was working on patch 248377 and came across that issue11:42
patchbotmahatic: https://review.openstack.org/#/c/248377/ - Decrypt multi-part mime doc11:42
*** yatin has quit IRC11:43
acolesmahatic: :/11:43
acolesmahatic: good catch11:44
mahaticacoles: another worry is: 2) for multipart-mime, when it hits this: https://github.com/openstack/swift/blob/master/swift/common/swob.py#L1099, it is still looking for encrypted content-type length (which will be diff after decryption)11:45
mahaticacoles: for more on content-type length: here is where it starts - https://github.com/openstack/swift/blob/master/swift/common/swob.py#L118111:46
acolesmahatic: back to 1) - I am not sure that the right solution is to test for 'meta' in _resp_content_type_property(). Instead, I would suggest that _resp_content_type_property() should explicitly remove only a param starting charset=11:50
acolesmahatic: but I'd like to understand where that method is being called that triggers the problem (I am sure it could be a problem!)11:50
mahaticacoles: which one? _resp_content_type_property()?11:51
acolesmahatic: yes. but i think i see it, line 1187??11:52
*** JelleB is now known as a1|away11:52
mahaticacoles: https://github.com/openstack/swift/blob/master/swift/common/swob.py#L111611:52
acolesmahatic: yes. i meant where is the content_type property read - there's places that manipulate the resp content-type header and there's places that get/set the content-type property11:54
mahaticacoles: ok, in that case, yeah that would be 118711:55
acolesso is the problem you see that in the multipart boundary the content-type meta has been stripped off? because of line 118711:55
acolesyep!11:55
acolesmahatic: https://github.com/openstack/swift/blob/master/swift/common/swob.py#L412 also looks like it could cause problems11:58
acolesmahatic: those methods seem to assume that the only param is charset11:58
acolesmahatic: i wonder how swift_bytes avoids being stripped by same method? maybe its just luck that the content_type property isn't used?11:59
mahaticacoles: i think there is another method (or something that overwrites for swift_bytes. I *think*). Let me take a quick look12:00
mahaticI remember coming across that12:00
acolesthere is12:01
mahaticacoles: ok, and here in response, weŕe only reading _resp_charset_property llooking specifically for charset I believe? I didnt think this would cause a problem12:04
mahaticand looking*12:04
*** SkyRocknRoll has quit IRC12:09
mahaticoverride_bytes_from_content_type - i was looking for this one earlier12:11
*** jmccarthy has quit IRC12:11
*** [1]dimasot has joined #openstack-swift12:13
acolesmahatic: I even wonder why the charset param is stripped off the content-types in the multipart doc? maybe that is not intentional? the example here shows charset included http://www.w3.org/Protocols/rfc1341/7_2_Multipart.html12:15
*** dimasot has quit IRC12:17
*** [1]dimasot is now known as dimasot12:17
mahaticacoles: looking12:17
*** jmccarthy has joined #openstack-swift12:19
acolesmahatic: i.e. i am thinking that here https://github.com/openstack/swift/blob/master/swift/common/swob.py#L1187 it should actually read the content-type from the response headers, NOT via the content_type property, so that the charset is not lost. Otherwise AFAICT the response loses any record of charset.12:20
mahaticacoles: maybe the intention is that it sets here? https://github.com/openstack/swift/blob/master/swift/common/swob.py#L115812:22
*** SkyRocknRoll has joined #openstack-swift12:25
acolesmahatic: yes, but the problem i see is the use of the Response property attribute to retrieve content-type when creating the multipart doc. swob is swift's version of webob and swob.Response.content_type appears to do the right thing according to http://docs.webob.org/en/1.1/modules/webob.html#response. But I'm not sure the charset should be dropped from the multipart doc part.12:26
acolesmahatic: so my assertion is that line 1187 in swob should read content_type = self.headers.get('content-type')12:29
acolesmahatic: which would mean that both charset and crypto meta would appear in the multipart doc part12:30
acolesmahatic: i'll try asking torgomatic later. i'm sure he'll know The Right Thing :)12:31
mahaticacoles: :) ok. but what is L1131 doing? (!)12:32
mahaticacoles: is it setting the content-type header? but i thought we are retrieving and stripping things off and everything12:33
acolesmahatic: line 1131 is setting a default value. then see line 1150, updates with supplied values12:34
*** marcusvrn_ has joined #openstack-swift12:35
mahaticacoles: using  self.headers.get('content-type') in multipart makes sense. but then we are also calculating length there https://github.com/openstack/swift/blob/master/swift/common/swob.py#L1196 which will be length of encrypted value12:36
acolesmahatic: line 1196 is calculating the length of whatever is going to be written as the multipart boundary. So yes, that should include the length of the encrypted content-type and its meta param12:38
mahaticacoles: and somehow line 1103 is holding onto that value - i.e. in the decrypter response, it doesnt move forward if the length is not equivalent to encrypted value(or whatever was before)12:39
mahatic:/12:39
mahaticacoles: or maybe that is my mistake, and it is not supposed to be that way? as in on decrypter response, this whole response thing will go through the process of putting together those values again?12:40
acolesmahatic: yep, my expectation is that the decrypter will need to rebuild the multipart response body with new multipart boundaries each having decrypted content-types12:41
mahaticacoles: it does that currently (as in the output of my code), but except the content-type, expecting the encrypted length. Will check that out12:41
*** lpabon has joined #openstack-swift12:42
acolesmahatic: there are some helper methods in utils that may be useful for reading the multipart body e.g. swift/common/utils.py:347712:45
*** cdelatte has joined #openstack-swift12:45
mahaticacoles: running patch 248377 against patch 167828 passes, except for content-type assertion12:46
patchbotmahatic: https://review.openstack.org/#/c/248377/ - Decrypt multi-part mime doc12:46
patchbotmahatic: https://review.openstack.org/#/c/167828/ - Add functional test for multi-range GET requests.12:46
*** aix has quit IRC12:47
*** aix has joined #openstack-swift12:48
acolesmahatic: but if the crypto meta was being lost from the content-type then it wouldn't get decrypted so you'd expect that to assertion to fail, no?12:48
mahaticacoles: and i just ran the code putting some print in swob, inside those content_type and length stuff - interestingly it only goes through once, that showing up with encrypted values12:48
mahaticacoles: oh yeah, that was expected. just saying that i used those helper methods you were pointing out and i do have a multipart-doc output, with data decrypted (which the test asserts)12:49
acolesmahatic: cool. so maybe try chaning swob line 1187 to  content_type = self.headers.get('content-type') ??12:50
acoles*changing12:50
mahaticacoles: i also did that (not exactly self.headers, but as a temp workaround by filtering ; meta) and *then* I encountered the length issue that im talking about now :)12:51
acolesmahatic: oic12:53
mahaticacoles: im not sure if the entire response is constructed again i.e. all those values are processed again for decrypter, I was thinking, decrypter takes the response and modifies and then processes the same way it got  (same values for response stuff)12:54
mahaticacoles: sorry, by "all those values are processed again for decrypter" - i mean all those values that "Response" is holding... Well it still doesnt sound to make a lot of sense, but i only Response being called once, in this whole process :/12:56
mahaticonly see*12:56
*** jerrygb has joined #openstack-swift12:59
*** jerrygb has quit IRC12:59
*** jerrygb has joined #openstack-swift12:59
*** haomaiwa_ has joined #openstack-swift12:59
*** jerrygb_ has joined #openstack-swift13:00
*** haomaiwa_ has quit IRC13:01
*** haomaiwang has joined #openstack-swift13:01
*** jerrygb has quit IRC13:03
acolesmahatic: are you going to update your patch with any of the changes discussed here? or is it up to date?13:03
acolesmahatic: away for lunch13:04
mahaticacoles: I need to replace the self.get.headers and push it, will do so (And that will leave me with the length issue, trying to figure it out)13:05
mahaticacoles: sure, have a good lunch13:06
mahaticreplace with*13:06
*** SkyRocknRoll has quit IRC13:08
*** ppai_ has quit IRC13:11
mahaticacoles: i think i figured the length issue - i dont think im updating content-length value13:21
*** SkyRocknRoll has joined #openstack-swift13:21
mahaticacoles: thanks for looking into this!13:21
*** haomaiwang has quit IRC13:22
*** haomaiwa_ has joined #openstack-swift13:24
*** daemontool has quit IRC13:25
*** venkat_p has quit IRC13:25
acolesmahatic: ok, sounds like progress13:32
*** SkyRocknRoll has quit IRC13:32
mahaticacoles: sounds so13:33
*** daemontool has joined #openstack-swift13:38
eranromacoles: I am reviewing the rbac patch (202411), and wondering where is the policy.json from which it is derived (it is derived from some policy.json right?)13:44
*** jistr has quit IRC13:46
acoleseranrom: hi! i'm not sure if ho used a policy.json file to derive the scenarios. i remember he had a description of his methodology in a pastebin.13:58
acoleseranrom: http://paste.openstack.org/show/412312/ and links in that page13:58
acoleseranrom: i'm not sure if that is ho's 'top level' methodology description ^^13:59
*** haomaiwa_ has quit IRC14:01
*** haomaiwang has joined #openstack-swift14:01
eranromacoles: Thanks. will start from there (^^)14:04
acoleseranrom: maybe you would catch ho in channel early in your daytime14:04
*** tongli has joined #openstack-swift14:05
eranromacoles: yep will try that tomorrow14:05
*** daemontool has quit IRC14:12
*** daemontool has joined #openstack-swift14:13
*** blmartin has joined #openstack-swift14:22
*** pchng_ is now known as pchng14:23
*** hseipp has quit IRC14:31
*** hseipp has joined #openstack-swift14:33
*** NM has quit IRC14:42
*** j_king_ is now known as j_king14:42
*** janonymous__ has joined #openstack-swift14:43
*** mzhou has joined #openstack-swift14:47
*** zacksh_ is now known as zacksh14:47
*** aix has quit IRC14:54
*** petertr7 is now known as petertr7_away14:57
*** haomaiwang has quit IRC15:01
*** Asselin has joined #openstack-swift15:01
*** haomaiwa_ has joined #openstack-swift15:01
*** Asselin has left #openstack-swift15:01
*** aix has joined #openstack-swift15:01
*** openstackgerrit has quit IRC15:02
*** openstackgerrit has joined #openstack-swift15:02
*** petertr7_away is now known as petertr715:02
*** mwheckmann has joined #openstack-swift15:03
*** admin6 has joined #openstack-swift15:05
*** breitz has joined #openstack-swift15:08
*** foexle has joined #openstack-swift15:12
*** pchng_ has joined #openstack-swift15:15
*** pchng has quit IRC15:16
*** wbhuber_ has joined #openstack-swift15:17
*** wbhuber_ has quit IRC15:17
*** pdardeau has joined #openstack-swift15:17
*** pdardeau has quit IRC15:22
*** pdardeau has joined #openstack-swift15:23
*** mwheckmann has quit IRC15:27
*** mzhou has quit IRC15:28
*** willsama has joined #openstack-swift15:31
*** willsama has quit IRC15:31
*** daddyjoseph97 has joined #openstack-swift15:35
*** mwheckmann has joined #openstack-swift15:36
*** NM has joined #openstack-swift15:39
*** jlhinson has joined #openstack-swift15:42
*** daemontool_ has joined #openstack-swift15:48
*** jlhinson has quit IRC15:48
*** daemontool has quit IRC15:52
*** NM has quit IRC15:57
*** haomaiwa_ has quit IRC16:01
*** foexle has quit IRC16:01
*** haomaiwa_ has joined #openstack-swift16:01
*** mwheckmann has quit IRC16:01
*** blmartin has quit IRC16:03
*** petertr7 is now known as petertr7_away16:06
*** rcernin has quit IRC16:08
*** Pablo|off| has joined #openstack-swift16:14
*** Pablo|off| is now known as pcaruana16:15
*** eranrom has quit IRC16:16
*** hseipp has quit IRC16:17
*** hseipp has joined #openstack-swift16:17
*** pchng_ is now known as pchng16:20
*** petertr7_away is now known as petertr716:21
*** hseipp has quit IRC16:22
*** SkyRocknRoll has joined #openstack-swift16:24
*** aix has quit IRC16:24
*** klrmn1 has joined #openstack-swift16:26
*** blmartin has joined #openstack-swift16:26
*** diazjf has joined #openstack-swift16:27
*** diazjf1 has joined #openstack-swift16:28
*** klrmn1 has quit IRC16:30
*** trifon has quit IRC16:30
*** diazjf has quit IRC16:31
*** jistr has joined #openstack-swift16:33
notmynamegood morning16:41
joeljwrightmorning16:41
pdardeaumorning16:41
notmynameit's cool and foggy this am in san francisco. makes it hard to get started in the morning :-)16:42
notmynamereminder that there is NOT a meeting this week16:42
pelusemorning16:43
*** petertr7 is now known as petertr7_away16:44
*** mwheckmann has joined #openstack-swift16:46
mahaticgood morning16:47
mahaticnotmyname: we all can sympathise with that :)16:48
*** joeljwright1 has joined #openstack-swift16:48
*** petertr7_away is now known as petertr716:49
*** mwheckmann has quit IRC16:51
*** joeljwright has quit IRC16:52
peluseI dunno, its pretty nice here in AZ :)16:53
*** mwheckmann has joined #openstack-swift16:55
notmynamelooks like today* is the day that the gate is killing py26 support16:55
notmyname * maybe not today16:56
notmynameor rather, today oslo is dropping py26 and doing a major version bump and it's likely the gate stuff will be remove within a week16:56
notmynameso, whatever we have in python-swiftclient now is pretty close to what we will have in a last release before we bump the version and do a py26-free release16:57
joeljwright1sounds reasonable16:57
notmynamejoeljwright1: timburke: is there any open patch that we really shouldn't do a release without landing it first?16:59
*** haomaiwa_ has quit IRC17:01
*** 21WAAEGOI has joined #openstack-swift17:01
joeljwright1notmyname: not that I can think of17:01
joeljwright1I've just had a look at the list17:01
notmynameI'm looking now too17:01
notmynamethanks17:01
notmynamejoeljwright1: are you still working on patch 223319?17:03
patchbotnotmyname: https://review.openstack.org/#/c/223319/ - New API documentation for python-swiftclient17:03
joeljwright1notmyname: yes17:03
joeljwright1it still has a lot of work remaining17:03
joeljwright1and I was hoping to get the suggestions from tokyo17:04
notmynameok. is there something that can be landed sooner? smaller chunks?17:04
notmynameah yes. that. I'm still working on it too ;-)17:04
joeljwright1it's possible it can be split up17:04
joeljwright1but tbh I was using that patch as a way of getting suggestions17:05
joeljwright1I'm unlikely to get any more work done on it before the end of December because of my trip17:05
notmynameok17:05
joeljwright1I can probably just complete the sections I have planned as phase 117:06
joeljwright1(that is, complete the empty sections that are there now)17:06
notmynamejoeljwright1: that would be great. also, if you don't have somethign smaller, then a note in the comments about someone else picking it up would be good17:06
*** daemontool_ has quit IRC17:06
notmynamejoeljwright1: could you look at patch 230100?17:07
patchbotnotmyname: https://review.openstack.org/#/c/230100/ - Add py35 to default tox environments17:07
joeljwright11-liners that we obviously need17:08
joeljwright1I like those17:08
*** daemontool has joined #openstack-swift17:08
*** ir2ivps8 has joined #openstack-swift17:13
joeljwright1notmyname: the biggest question I have with the docs is what to do about the swiftclient.client docs17:16
joeljwright1I still have a few code examples to create for swiftclient.service17:16
joeljwright1but there is still a lack of guidance on how to choose client vs service vs cli17:17
joeljwright1and nothing beyond the docstrings for client17:17
notmynameso what's the question?17:18
*** sgundur has joined #openstack-swift17:19
joeljwright1what do we want to do about producing extra docs for swiftclient.client? Expand the docstrings? Produce another file with examples?17:19
*** 21WAAEGOI has quit IRC17:20
notmynameI definitely think we should, of course :-)17:20
joeljwright1and how much do we want to write about picking the correct api to use?17:20
notmynameI'm not sure of the best way. docstrings and separate docs are both good. really, it probably doesn't matter much, compared to what we have now (or rather what we don't have)17:20
*** rcernin has joined #openstack-swift17:21
notmynamepicking the correct API is the first place everyone should start17:21
notmynameis it's got to be good17:21
joeljwright1indeed, and the second place most people fall down is auth17:21
notmynameyup17:22
joeljwright1and the big issue with auth it that I'm fairly sure there is no one person who understands every path!17:22
joeljwright1I'm as guilty as most of knowing how to auth with my systems, but not really what all the options are17:23
*** admin6 has quit IRC17:23
joeljwright1and trying to get people involved in doc writing is… tricky…17:23
joeljwright1:D17:24
*** blmartin has quit IRC17:24
joeljwright1ok, I shall commit to trying to get my patch into a decent state before the new year17:25
joeljwright1and I'll try to enlist some help with the auth and choosing parts17:26
*** jerrygb_ has quit IRC17:26
*** janonymous__ has quit IRC17:26
joeljwright1(but I'm away on Friday until Dec 12th, so I shall be starting after that)17:27
notmynamethanks17:28
*** petertr7 is now known as petertr7_away17:29
*** NM has joined #openstack-swift17:33
*** jerrygb has joined #openstack-swift17:33
*** travisn has joined #openstack-swift17:35
notmynamehttps://pypi.python.org/pypi/django-storage-swift/1.2.5 was just updated. I love seeing stuff like that out there :-)17:35
*** jerrygb has quit IRC17:36
*** CaioBrentano has joined #openstack-swift17:39
*** jerrygb has joined #openstack-swift17:40
*** petertr7_away is now known as petertr717:41
*** aix has joined #openstack-swift17:45
*** jerrygb has quit IRC17:45
openstackgerritAlistair Coles proposed openstack/swift: Fix listing of SLO manifest bytes after POST or COPY  https://review.openstack.org/24821917:46
*** sc68cal has quit IRC17:46
acolesjrichli: ^^ it got more complicated since you mentioned POSTs in your review ;)17:47
*** sc68cal has joined #openstack-swift17:47
*** blmartin has joined #openstack-swift17:49
acolestorgomatic: are you here?17:52
notmynameacoles: I didn't see him at his desk just now. might be commuting currently17:53
*** zul has quit IRC17:53
acolesnotmyname: thanks. so turkey-fest hasn't started yet?17:53
notmynamethe official day is thursday. but different families do different things17:54
notmynamestarts for me very early on wednesday when we get on a plane17:54
acolesnotmyname: yeah i imagine a lot of folks travel this week17:55
*** eranrom has joined #openstack-swift17:56
*** NM has quit IRC17:57
*** zul has joined #openstack-swift17:58
*** CaioBren_ has joined #openstack-swift17:59
openstackgerritAlistair Coles proposed openstack/swift: Update .mailmap entry  https://review.openstack.org/24820218:02
*** CaioBrentano has quit IRC18:03
notmynameacoles: thanks. checking it now18:03
*** joeljwright1 has quit IRC18:04
notmynameacoles: looks good for what's there. but I see 4 more people in `git shortlog` that have hp.com addresses. Dragos, Dan, Jola, and Thomas18:05
notmynameacoles: I'm fine with approving what you have now, but do you know about those 4?18:05
acolesnotmyname: i was going to add a comment but you beat me - three i now for sure are no longer @hpe.com i.e.  Dan, Jola, and Thomas18:06
notmynameok18:06
notmynamethen let's leave it as-is for now18:07
notmynameit's not like it's hard to change the .mailmap later ;-)18:07
notmynamethanks for doing the research18:07
notmynameacoles: FWIW, this makes the AUTHORS file somewhat out of date, but I'll square that up with one commit myself when I add all the new contributors18:07
pelusenotmyname: is there a trick to getting patch 214206 to pass all func tests?  I've upgraded all my requirements and test-requirements and get a bunch of failures running func tests on this patch18:08
patchbotpeluse: https://review.openstack.org/#/c/214206/ - Modify functional tests to use testr18:08
acolesnotmyname: also i assume Dragos is not at hpe.com since the mail bounced, i just don't know them personally18:08
notmynamepeluse: locally? passed for me locally, but maybe what you're seeing is similar to what the gate sees18:08
acolesnotmyname: ah. you want me to update AUTHORS at same time (same review)?18:09
peluseyeah, locally.  FAILED (failures=33, skipped=12)18:09
notmynameacoles: no. don't worry about it. I'll do it later when I update it for a release18:09
acolesnotmyname: ok18:09
notmynameacoles: I've got a script which tells me what's different between shortlog and the AUTHORS frile18:09
*** arnox has quit IRC18:10
notmynamepeluse: trying it again locally18:14
pelusenotmyname: cool, I'll try again too.  maybe it will work the 3nd or 3rd time :)18:16
pelusenotmyname: I know my pip/pbr/setuptols are all latest/greatest and I went ahead and did --upgrade on both requirements and the updated test-requirements as well.  Is that not a good thing to do?18:17
*** jordanP has quit IRC18:17
*** aix has quit IRC18:18
notmynamethey had to be updated for other reasons lately. shouldn't be tied particularly to this specific patch though18:19
*** klrmn1 has joined #openstack-swift18:20
pelusenotmyname: thats what I thought but I had some obvious failures with imports/etc with whatever state all my dependences were in so --upgraded everything.  Til I did thtat they wouldnt even execute18:20
timburkenotmyname: on python-swiftclient, i'd kinda like to see https://review.openstack.org/#/c/190887/ land (since it give you a means to post data to an account and inspect the response), but there's enough going on there that it probably wouldn't be a quick review18:21
acolespeluse: thanks for your review on patch 231121, i'm back from hanging duty and will respond to your comments 'real soon'18:21
patchbotacoles: https://review.openstack.org/#/c/231121/ - Make ECDiskFile report all fragments found on disk18:21
peluseacoles: awesome! hope you didn't send any innocents to the gallows :)18:22
*** CaioBren_ has quit IRC18:23
acolespeluse: hmmm, its kinda hard to know :)18:23
peluseacoles: just kidding, if they were accused I'm sure they were guilty!18:23
*** CaioBrentano has joined #openstack-swift18:23
notmyname*shudder*18:23
* peluse wonders why he's never picked for jury duty...18:23
notmynameRan 380 tests in 305.450s18:24
notmynameOK (skipped=12)18:24
notmynamepeluse: ^18:24
notmynamepeluse: what's failing on your machined?18:24
pelusenotmyname: wow18:25
acolespeluse: heh.18:25
pelusenotmyname: ton of stuff.  running now, when its done I'll pick out a few and psate them in18:25
pelusegmmaha: how many of your func tests are failing?18:26
*** jerrygb has joined #openstack-swift18:27
*** mahatic has quit IRC18:27
peluseany core:  pls take a mn to look at a quick code coverage patch in need of 2nd +2.  patch 24061318:28
patchbotpeluse: https://review.openstack.org/#/c/240613/ - Unit tests for account/backend.py18:28
notmynamepatch 245266 really should land before a release18:28
patchbotnotmyname: https://review.openstack.org/#/c/245266/ - remove pbr from requirements.txt. It's not a run-t...18:28
notmynamepeluse: looking at that one18:29
openstackgerritAlistair Coles proposed openstack/swift: Stop staticweb revealing container existence to unauth'd requests  https://review.openstack.org/24886718:29
pelusenotmyname: gracias18:30
*** NM has joined #openstack-swift18:35
*** petertr7 is now known as petertr7_away18:41
*** wuhg has quit IRC18:41
*** jerrygb has quit IRC18:42
claygheyoh!18:42
pelusehola!18:45
*** NM has quit IRC18:46
*** jerrygb has joined #openstack-swift18:46
openstackgerritMerged openstack/python-swiftclient: Add py35 to default tox environments  https://review.openstack.org/23010018:46
pelusenotmyname: here's my fnc test failures on the testr thing: https://gist.github.com/anonymous/e036f1bab957ac81fde818:48
* peluse BRB18:49
*** wbhuber_ has joined #openstack-swift18:49
notmynamein coverage reports, what's the difference between a "missing" line statement of 1234-5678 and 1234->5678?18:50
notmynamewhat's the difference between the - and ->18:50
*** acoles is now known as acoles_18:50
*** jerrygb has quit IRC18:51
notmynamewith patch 240613, I get 608->609 in the missing column. with master I get 607-609. the patch should be adding coverage for 608 and 60918:52
patchbotnotmyname: https://review.openstack.org/#/c/240613/ - Unit tests for account/backend.py18:52
notmynamepeluse: ^18:52
*** daemontool has quit IRC18:54
*** trifon has joined #openstack-swift18:54
*** jerrygb has joined #openstack-swift19:03
*** wbhuber_ has quit IRC19:08
*** diazjf1 has quit IRC19:11
gmmahapeluse: i got 75 failed19:11
gmmahanotmyname: for 608 and 609, i was never able to very that 609 is being raised19:14
gmmahai was able to test for 608, but then 609 was always a puzzle.. had a similar one in the same file upto which i couldnt fix either19:14
*** silor has quit IRC19:17
*** diazjf has joined #openstack-swift19:28
*** petertr7_away is now known as petertr719:45
gmmahanotmyname: found where i was going wrong.. fixing the patch now..20:00
*** jordanP has joined #openstack-swift20:03
*** jordanP has quit IRC20:05
notmynamegmmaha: ah, great20:11
*** mwheckmann has quit IRC20:17
openstackgerritMerged openstack/swift: Added unit test cases for container/auditor.py  https://review.openstack.org/24035120:17
openstackgerritMerged openstack/swift: Update .mailmap entry  https://review.openstack.org/24820220:19
*** jistr has quit IRC20:23
*** CaioBren_ has joined #openstack-swift20:34
*** CaioBren_ has quit IRC20:36
*** CaioBrentano has quit IRC20:37
*** petertr7 is now known as petertr7_away20:43
*** petertr7_away is now known as petertr720:46
*** Zyric1 has joined #openstack-swift20:52
*** SkyRocknRoll has quit IRC20:53
*** jrichli has joined #openstack-swift20:54
openstackgerritGanesh Maharaj Mahalingam proposed openstack/swift: Unit tests for account/backend.py  https://review.openstack.org/24061321:10
*** jodah- has quit IRC21:11
*** anteaya has quit IRC21:11
gmmahanotmyname: is it ok if we re-arrange the import section to be alphabetical order?21:13
notmynameacoles_: you* broke my dashboard21:13
gmmahapurely cosmetic and also will help us comply with a pep8 rule i think21:13
notmynameacoles_: *actually the change from hp.com to hpe.com broke the dashboard21:13
notmynamegmmaha: it's not a pep8/flake/hacking rule we check, so there won't be any consistency or enforcement to keep it in whatever order you put it in21:14
*** travisn has quit IRC21:14
notmynamegmmaha: I'd suggest leaving it at-is21:14
gmmahanotmyname: ok.. Will let it be.. thanks21:15
gmmahawas more thinking we can remove it from the exceptions list and start checking for that rule.. ;)21:15
gmmahabut then its just my OCD!!21:15
*** jodah has joined #openstack-swift21:21
*** jerrygb has quit IRC21:22
*** jerrygb has joined #openstack-swift21:26
*** anteaya has joined #openstack-swift21:26
*** travisn has joined #openstack-swift21:28
*** jerrygb has quit IRC21:31
*** david-lyle has quit IRC21:31
*** daddyjoseph97 has quit IRC21:32
*** david-lyle has joined #openstack-swift21:34
*** jrichli has quit IRC21:36
Zyric1Hi everyone! I'm returning to a patch I started a few weeks ago https://review.openstack.org/#/c/241978/ and have created a new SAIO for it and inserted the changed files. I have tried running tox -e func, .unittests, .functtests, and .probetest and am having trouble re-creating the error jenkins found. Could anyone please advise me how to run the exact tests which failed the patch please?21:41
notmynamehello Zyric121:42
Zyric1Hi notmyname :)21:42
*** diazjf has quit IRC21:42
notmynameZyric1: do you know how to get the logs from jenkins to see what failed there?21:42
mattoliverauMorning21:43
notmynamemattoliverau: hi. I was just looking into geelong accommodation. I need to figure out some other logistics before I book a room/flight, though21:44
notmynamemattoliverau: seems like deakin univ is really small. is that the same location it was at last time? the maps makes it seem like it's just one square block21:44
notmynameZyric1: if not, I'll tell you how. just don't want to skip ahead in getting a solution21:45
Zyric1notmyname: To investigate I clicked the link of the failure and read the contents of console.html.gz which seems to suggest some kind of mapping issue with the parameters to config. I wanted to have a play around in the code but I can't recreate the problem locally.21:45
notmynameyeah21:45
notmynameso the error is at http://logs.openstack.org/78/241978/3/check/gate-swift-tox-func/e0994e6/console.html.gz#_2015-11-10_09_31_23_29821:45
mattoliveraunotmyname: We've found some hotel accommodation, let me get the name of one were using21:45
notmynamemattoliverau: oh, good. thanks21:45
notmynameZyric1: and it's interesting that it failed in the gate and not in the qa cluster21:48
notmynamehmm... /me as an idea21:48
gmmahals -lrt21:53
notmynameZyric1: I duplicated it21:53
notmynamejust now21:53
notmynameZyric1: ...a little more detective work now...21:54
Zyric1notmyname: Ah, nice! Which commands/tests did you use to duplicate it?21:54
*** david-lyle has quit IRC21:55
*** zaitcev has joined #openstack-swift21:56
*** ChanServ sets mode: +v zaitcev21:56
openstackgerritTim Burke proposed openstack/swift: Reverse-listings follow-up  https://review.openstack.org/24892421:56
mattoliveraunotmyname: just got word, we're staying at the Bayside Geelong.21:59
notmynamemattoliverau: thanks21:59
mattoliverauI think that was a good price point to location21:59
*** sgundur has quit IRC21:59
*** david-lyle has joined #openstack-swift22:03
*** david-lyle has quit IRC22:04
*** sgundur has joined #openstack-swift22:05
*** petertr7 is now known as petertr7_away22:06
notmynameZyric1: ok, so it's using the "in-process" fuctional tests. which are a little weird, admittedly, but what's happening is that there's a swift.conf file being generated that has the line "aliases = ['Policy-0']" and that's abviously wrong22:09
notmynameI'm not sure yet how that's getting stuck in there22:09
notmynameZyric1: duplicate it with `SWIFT_TEST_IN_PROCESS=true SWIFT_TEST_IN_PROCESS_CONF_DIR=/tmp tox -efunc`22:09
*** jerrygb has joined #openstack-swift22:11
notmynameZyric1: fyi search for "in-process" on http://docs.openstack.org/developer/swift/development_guidelines.html22:12
Zyric1notmyname: Many thanks, I'll look into that now.22:19
notmynameZyric1: here's what i kno22:19
notmynamethe storage policies are being loaded twice22:20
*** rcernin has quit IRC22:20
*** gmmaha has quit IRC22:20
notmynamethe first time, it's working ok, but I think it's creating the aliases attribute and the second load is making that get written out into a config file22:20
notmynameand str(list) ends up being the value ['Policy-0']22:20
notmynamewhich fails the parsing22:21
*** david-lyle has joined #openstack-swift22:21
*** gmmaha has joined #openstack-swift22:21
notmynameso I don't like the double loading, but i'm not sure if that's the problem or not. or at least if it is a problem it's not the only one22:21
notmynamepart of the issue, i think, is that the aliases attribute is a list and that's getting serialized to a string22:22
notmynamemaybe there needs to be a "human readable or config" attribute as a string and another as a list for parsing22:22
notmynamemaybe the patch simply needs to be more careful about when the aliases value is used22:23
claygnotmyname: this is something that's broke or something we're trying to fix22:24
notmynameclayg: depends on what's broke ;-)22:25
*** david-lyle has quit IRC22:25
notmynameI'm not sure if the double loading thing is what's broken or if it's the erroneous addition of the value into the config file. or both.22:26
Zyric1notmyname: Thanks for all the information, that's super useful. Is the double loading an intentional thing? If so to what end? I'll have a think and tinker with the aliases bit and see where that leads.22:28
*** tongli has quit IRC22:29
*** trifon has quit IRC22:30
*** lpabon has quit IRC22:33
notmynameTOO MUCH MAGIC!!!22:36
gmmahanotmyname: like peluse i am also getting error on functests with testr, but its varied errors on each run. 1st run - 68, 2nd run - 55, 3rd run 78, 4th run 44 :|22:37
*** tsg has joined #openstack-swift22:43
mattoliverauSwift: Where magic we don't understands happens.22:50
mattoliverauI was looking at the testr change yest arvo and having a few problems as well. I'm going to continue playing this morning.22:51
mattoliverauoh and hey gmmaha :)22:51
gmmahahey mattoliverau  :)22:52
notmynamemattoliverau: peluse: gmmaha: thank you for looking at those. unlike many other patches, that one has external time dependencies. the results of that work are what's given to the foundation board and what they approve for defcore stuff22:52
gmmahaok, last week i thought i was crazy..22:52
gmmahathank god its not just me..22:52
notmynameand we already missed the board meeting that happened in tokyo22:52
*** trifon has joined #openstack-swift22:53
*** pdardeau has quit IRC22:53
mattoliveraugmmaha: were all a little crazy really ;)22:53
gmmahahaha :D22:54
notmynamepay attention to this http://lists.openstack.org/pipermail/openstack-dev/2015-November/080294.html22:54
mattoliveraunotmyname: kk, time to get out my square peg round hole bat :P22:54
*** ChanServ changes topic to "Review Dashboard: https://goo.gl/iLt6Ld | Get an IRC bouncer at http://znc.in | Logs: http://eavesdrop.openstack.org/irclogs/%23openstack-swift/ | DocImpact changes http://lists.openstack.org/pipermail/openstack-dev/2015-November/080294.html"22:55
gmmahanotmyname: thanks.. will let this go for now..22:56
notmynamegmmaha: the testr failures? please don't let it go. I was saying that to encourage you to keep working on it ;-)22:57
gmmaha:D22:57
gmmahasince we missed the board meeting, i thought you were hinting towards letting it go until the next summit.. ;)22:58
notmynameI think there's another board meeting in the first half of december22:58
notmynamethen at the next summit22:58
gmmahaohh cool..22:58
notmynameand with the way defcore works, there's basically a year lead time. so if our tests show new things that can be tested for, it will take a year to get them to be officially tested22:59
tsgzaitcev, we are discussing on -infra if liberasurecode package is available for F22 - I see it in "approved" status here:  https://admin.fedoraproject.org/pkgdb/package/liberasurecode.  Do you know when it would appear in F22 updates?22:59
hogepodgehappy to answer any defcore questions people might have23:00
zaitcevtsg: I'm filing for F23 right not, and F22 has to follow it because version is the same.23:00
*** km has joined #openstack-swift23:00
notmynamehogepodge: just trying to get the testr changes in. getting weird failures in the gate23:00
notmynamehogepodge: when's the next board meeting?23:00
*** km is now known as Guest3116623:01
tsgzaitcev, ok thanks .. I will change https://review.openstack.org/#/c/247936/ to install liberasurecode only >=f2323:01
hogepodgeDecember 323:01
hogepodgeConference call23:01
notmynamehogepodge: yikes. which means that any new capabilities discovered from the in-tree tests won't be ready by then23:02
notmynamehogepodge: but my understanding (from our conversation at the summit) is that new tests for existing capabilities can be added pretty easily.23:03
*** david-lyle has joined #openstack-swift23:03
notmynamehogepodge: does that require board action? or it's just written down?23:03
hogepodgenotmyname: we should check with zehicle on when we want to set the new guidelines23:03
notmynamehogepodge: I'm much more concerned (short term) in adding new tests to the existing capabilities. i'm not as worried right now about adding new capabilities23:04
*** david-lyle has quit IRC23:05
hogepodgenotmyname: totally understand, for some reason I think we have until January, but I want to make sure23:05
notmynameok23:05
notmynamestill, not much time23:05
hogepodgeJust asked Rob to pop in and clarify.23:05
notmynamewait. have until january for what?23:05
*** zehicle has joined #openstack-swift23:06
zehicleo/23:06
hogepodgeget the swift in-tree tests added to the capabilities.23:06
notmynameok23:06
notmynamethat's better than "next week" what with thanksgiving this week23:06
hogepodgezehicle: what's our timing to get the swift in-tree tests added to existing capabilities?23:06
hogepodgezehicle: does it have to be ready by Dec 3 board meeting?23:06
hogepodgezehicle: I thought we had until January23:07
tsgzaitcev, sorry, may be I misunderstood - is F23 liberasurecode package already available, or it will be, after you "submit" it?  :)23:09
tsg(zaitcev, I still see it under "testing")23:10
zaitcevtsg: it sits there for 3 days unless someone gives it more "karma"23:11
zehicleto existing caps?  could happen for 2016.0123:11
zehiclejust need a patch for that23:11
zehiclehogepodge, no.23:11
notmynamezehicle: ok, so new tests to existing capabilities does not require a board action? just requires a patch to a json file?23:11
zehiclehogepodge, 2016.01 will likely really be 2016.02 (Feb meeting)23:11
tsgzaitcev, ok - do you have a tracker issue?23:12
zehiclenotmyname, it can only be before the board approves23:12
notmynamezehicle: what does that mean? before the board approves what?23:12
zaitcevtsg: The Vote Formerly Known As Karma is now called "Feedback" in the UI in https://bodhi.fedoraproject.org/updates/FEDORA-2015-3889c3fcba23:12
zehicleonce the Guideline is approved, we can't add tests23:12
notmynamezehicle: ok23:12
zehiclewe cannot add new capabilities to the draft23:13
notmynameright23:13
zehicletests are a level below caps23:13
notmynamezehicle: so what's the next guideline the board is approving? where are we now?23:13
zehicleso, new capabilities will have to wait until 2016.0723:13
notmynamezehicle: (thinking timeframes)23:13
notmynameok23:13
zaitcevtsg: until it's in stable, one can pull it from so-called "testing" repository, which is normally installed but not enabled by default.23:13
zehiclethe capabilities for 2016.07 have to be in before the Austin summit23:13
notmynamezehicle: including all the scoring?23:14
zehiclenotmyname, yes23:14
tsgzaitcev, got it.  We can assume that the CI slaves won't have the repo enabled by default so it won't be available23:14
notmynamezehicle: and the tests?23:14
zehiclenotmyname, ideally but there's some flexibility23:14
notmynameideally what?23:15
zehicleideally, we'd have all the tests for a Cap.  Can get by w/ most of the tests.23:15
zehicleCapabilties without tests would not be ok23:15
notmynamewhat about tests for existing capabilities?23:15
zehiclethose can come in now23:15
notmynameI'm not too worried about new capabilities yet23:15
zaitcevtsg: Probably a safe assumption. I checked and it's not on my laptop in F23. I guess it was split off into its own package or something.23:16
zehicleto the draft and future guidelines23:16
notmynameyeah, but the patch to get the tests integrated with tempest is ...struggling23:16
zehiclethey cannot go into approved ones.  we can only remove tests after approval23:16
notmynameso I'm trying to figure out what the rough time deadlines are23:16
tsgzaitcev, can I provide some level of testing and affect the "karma" in any way?23:16
notmynamezehicle: what's the next one that will be approved?23:16
tsgzaitcev, ie "feedback"23:16
zehiclenotmyname, 2016.0123:16
notmynamezehicle: it will be approved in january? or it is approved before? when should a patch be landed by?23:17
zehiclelate January (maybe early Feb)23:17
notmynameok, thanks23:17
zehiclethe patch should land in early Jan to be safe23:17
zehicle(sooner is better)23:18
notmynameof course :-)23:18
zaitcevtsg: If you have a Fedora account, yes.23:18
* zehicle DefCore is a tad distracted by the Oracle patch anyway23:18
notmynameI'm pretty sure I don't want to know what that is ;-)23:18
tsgzaitcev, ok let me try23:18
zehiclenotmyname, no, you probablly don't.  has to do w/ hypervisors and zones23:18
notmynameand oracle ;-)23:19
zehicleand easily combustable materials23:19
notmynamehogepodge: zehicle: thanks for the defcore info23:20
hogepodgesure23:21
notmynamehow does reading a config file not have a value but passing though ConfigParser() shows ky/val pairs?23:21
notmynameclayg: ^23:22
notmynameZyric1: still trying to figure out those config things on your patch. not sure yet what's going on. did you find anything?23:22
*** david-lyle has joined #openstack-swift23:23
zaitcevremote: FATAL: W refs/heads/f22 liberasurecode zaitcev DENIED by refs/heads/f[0-9][0-9]23:24
notmynameportante: I'm currently blaming you for in-proc func tests ;-)23:24
zaitcevtsg: oh sheesh, I guess it's F23 then23:24
portantenotmyname: yes, you should, that is what I used to help find bugs in swift23:24
portante;)23:24
notmynamelol23:24
notmynameportante: currently there's lots of magic and it's breaking the gate but not SAIO. so there23:25
portantebreaking the gate ... oh, yes, now I remember, openstack gate jobs, those things ... ;)23:25
notmynamemagic == I don't know how to explain what I'm seeing yet23:25
portantelet me know, I can help debug if you'd like23:25
*** david-lyle has quit IRC23:25
notmynameportante: yeah, you're back in this "oh I can just push code and it lands right away" fairy-tale land ;-)23:26
portante;)23:26
zehiclenotmyname, glad to help!23:26
tsgzaitcev: thanks - not sure I understand why it was denied for F22 - freeze? .. let me see if I can other folks to test F23 and update the request23:27
tsgs/can other/can get other23:28
zaitcevtsg: Yeah, seems way early. The f21 would be denied because it went into maintenance.23:28
tsgzaitcev: ok .. let me make sure that the f21 gate jobs are in fact non-voting at this point and scheduled for removal end of this month23:28
notmynameah ha! less magic now!23:29
notmynamethanks swifterdarrell for being my rubber duck23:29
zaitcevtsg: I'm movng on updating python-pyeclib in f23, so we have at least something complete before we deal with f22.23:29
openstackgerritGanesh Maharaj Mahalingam proposed openstack/swift: Unit tests for account/backend.py  https://review.openstack.org/24061323:30
notmynameZyric1: progress :-)23:30
*** kei_yama has joined #openstack-swift23:30
Zyric1notmyname: Sorry! No, not yet. I got a bit sidetracked with setting up my Outreachy blog, my bad.23:30
tsgzaitcev, ok .. hope you won't mind another update to pyeclib soon - we have several new updates on master and we are about to tag (after removing the bundled liberasurecode pkg)23:31
zaitcevtsg: Not at all, be my guest.23:31
tsgzaitcev: thanks!23:32
zaitcevtsg: Can I mix the upcoming PyECLib with liberasurede 1.1.0?23:32
tsgzaitcev: yes, in fact the upcoming PyECLib is also backward compatible with < 1.1.023:32
tsgzaitcev, its just that you need at least 1.1.0 for 'liberasurecode_rs_vand' if you want to use that for swift unit tests23:33
zaitcevtsg: It would be great if you and Kevin allowed for a window of 1 release back and forth, e.g. pyeclib 1.1.1 working with liberasurecode 1.1.0. Of course not with 1.0.9, that would be too much to ask.23:33
zaitcevtsg: I see, thanks.23:33
*** david-lyle has joined #openstack-swift23:35
notmynameah ha! found it23:36
notmynameZyric1: ^23:36
notmynameportante: ^ found the problem. still not particularly happy with you ;-)23:36
*** trifon has quit IRC23:36
notmynameturns out that setting up rings also happens to helpfully rewrite the config file. found with judicious printf debugging23:37
Zyric1notmyname: you're my hero! :)23:38
notmynameZyric1: well, not quite. it's a problem with your code ;-)23:38
portantenotmyname: sorry. :(23:39
notmynameZyric1: but now I know where to look, so the fix should be easier :-)23:39
portanteI am not causing problems in another environment, if that is any consolation. :)23:39
notmynameportante: no worries. think of it as "you're not forgotten" ;-)23:39
*** sgundur has quit IRC23:40
notmynameportante: I'd rather have you back causing problems in swift :-)23:40
Zyric1notmyname: while it may be my code that's the problem, I know my code a lot better than I understand rings and much of swift at the moment so your help with the debugging is super helpful23:40
portantethanks!23:40
notmynameZyric1: "your code as the problem" is a little strong :-)23:41
*** david-lyle has quit IRC23:41
*** david-ly_ has joined #openstack-swift23:41
notmynameZyric1: there's an interaction we didn't see at first, and that's what's causing problems23:41
notmynameZyric1: here's what's happening23:41
*** sgundur has joined #openstack-swift23:41
notmynameZyric1: the tox -e func job runs what's called in-process tests. (written originally by portante, hence my bugging him [in jest])23:42
notmynameZyric1: those are designed to let you run functional tests without having an external swift install23:42
notmynameZyric1: to do that, it sets up some defaults in configs, based on the sample config files, and starts up some processes23:43
notmynameZyric1: however, when it's setting up a swift.conf file (which includes the storage policy definitions), it calls get_info() on at least the first storage policy23:43
notmynamethat first one defaults to "Policy-0" as the name (for historic reasons)23:44
notmynameZyric1: so your patch adds in the aliases, and the swift.conf test setup iterates over what that responds with and writes it in a config23:44
notmynameZyric1: the aliases attribute referred to in teh config mapping is actually stored as a list, not a string. so when it's coerced to a string, you get the "['Policy-0']" form23:45
notmynameZyric1: and that "blows up", as they say23:45
notmynameZyric1: IMO here's how you should fix it. look at the "default" and "deprecated" values in the config map. they refer to a method that gives the right value, so you don't get the string coercion on the bools23:47
notmynameZyric1: I think this patch needs something similar. eg map aliases to "aliases_readable_list" or something23:48
notmynameZyric1: does that make sense?23:48
Zyric1notmyname: Yes, that makes much more sense! Thank you for the clear explanation :)23:49
notmynameZyric1: I'm writing a diff23:51
*** sgundur has quit IRC23:52
notmynameZyric1: also, just as a code style note, we've got version control for the code, so there's no reason to keep commented out code in the file23:52
*** sgundur has joined #openstack-swift23:53
*** ho has joined #openstack-swift23:54
hogood morning!23:55
mattoliverauho: morning23:59

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