Monday, 2015-08-17

*** sanchitmalhotra1 has joined #openstack-swift00:01
*** changbl has joined #openstack-swift00:03
*** sanchitmalhotra has quit IRC00:03
*** jrichli has joined #openstack-swift00:11
*** sanchitmalhotra has joined #openstack-swift00:14
*** sanchitmalhotra1 has quit IRC00:16
*** sanchitmalhotra1 has joined #openstack-swift00:20
*** sanchitmalhotra has quit IRC00:22
*** sanchitmalhotra has joined #openstack-swift00:41
*** sanchitmalhotra1 has quit IRC00:43
*** peluse1 has joined #openstack-swift00:46
*** asettle has quit IRC00:54
*** sanchitmalhotra1 has joined #openstack-swift00:58
*** sanchitmalhotra has quit IRC01:00
*** sanchitmalhotra has joined #openstack-swift01:01
*** sanchitmalhotra1 has quit IRC01:02
*** nexusz99 has joined #openstack-swift01:03
*** sanchitmalhotra1 has joined #openstack-swift01:10
*** sanchitmalhotra has quit IRC01:12
*** sanchitmalhotra has joined #openstack-swift01:17
*** sanchitmalhotra2 has joined #openstack-swift01:19
*** sanchitmalhotra1 has quit IRC01:19
*** sanchitmalhotra has quit IRC01:21
*** sanchitmalhotra has joined #openstack-swift01:40
*** sanchitmalhotra2 has quit IRC01:42
*** rodrigod` has joined #openstack-swift01:54
*** rodrigod` is now known as rodrigods01:57
*** 6JTABTZX7 has joined #openstack-swift02:02
*** sanchitmalhotra1 has joined #openstack-swift02:09
*** peluse1 has quit IRC02:11
*** sanchitmalhotra has quit IRC02:11
*** wbhuber has quit IRC02:14
*** logan2 has quit IRC02:18
*** sanchitmalhotra has joined #openstack-swift02:25
*** sanchitmalhotra1 has quit IRC02:27
*** sanchitmalhotra1 has joined #openstack-swift02:36
*** sanchitmalhotra has quit IRC02:38
notmynameho: good mornign! did you make it back home ok?02:39
*** haigang has joined #openstack-swift02:39
*** hezhiqiang has joined #openstack-swift02:45
*** haigang has quit IRC02:46
*** hezhiqiang has quit IRC02:47
jrichlinotmyname: good to see you made it back ok.  Now I am worried about ho :-\ !02:50
notmyname:-)02:50
hohotmyname: yeah, i don't have any jet lag. thanks! :-)02:50
notmynameturns out he was right behind me the whole time!02:50
jrichliho: nice to hear!02:50
notmynameho: great!02:50
jrichliyou guys are at the ops thing?02:51
notmynamethat starts tuesday. (and is just a short drive away)02:51
jrichliah.  ok02:51
jrichliso ... I guess I dont like all mezcal :-)02:52
jrichlimy intuition failed me on that one02:52
notmynamelol02:52
notmynamesorry about that02:52
jrichlithats ok - I got the casa noble02:53
notmynamewhat did the new one taste like?02:53
jrichlirubber!02:53
notmynamelol02:53
notmynameok, I can help with that actually02:53
notmynamedepending on what else you have02:53
jrichliooo .. well, its gone.  i actually am suspecting it is not meant for human consumtion.02:54
notmynamelol02:54
notmynameok, then02:54
jrichliits ok.  i just need to find that one i liked the first night.  what was that exactly?02:55
jrichlithe illegal02:55
jrichlii remember02:55
*** logan2 has joined #openstack-swift02:57
notmynameya http://www.ilegalmezcal.com02:57
jrichlithx03:00
*** 6JTABTZX7 has quit IRC03:01
notmynameone of the first mezcals I had smelled like burning tires. and tasted similar. but I learned more, tasted more, and figured out what was good.03:02
*** haomaiwang has joined #openstack-swift03:02
jrichliI dont think I will just pick one without a recommendation next time!03:04
notmynamehappy to help, whenever03:05
*** dbarman has quit IRC03:05
*** peluse1 has joined #openstack-swift03:25
*** jrichli has quit IRC03:42
*** SkyRocknRoll has joined #openstack-swift03:43
*** sanchitmalhotra has joined #openstack-swift03:45
*** sanchitmalhotra1 has quit IRC03:47
*** mahatic has joined #openstack-swift03:53
*** haomaiwang has quit IRC04:01
*** haomaiwang has joined #openstack-swift04:01
*** hrou has quit IRC04:03
*** changbl has quit IRC04:04
*** sanchitmalhotra1 has joined #openstack-swift04:10
*** sanchitmalhotra has quit IRC04:12
*** sanchitmalhotra has joined #openstack-swift04:15
*** openstack has joined #openstack-swift04:19
openstackgerritHisashi Osanai proposed openstack/swift: Add functional test for access control (GET) with Keystone  https://review.openstack.org/20299404:25
*** peluse1 has quit IRC04:36
*** baojg has joined #openstack-swift04:48
openstackgerritHisashi Osanai proposed openstack/swift: Add functional test for access control (HEAD) with Keystone  https://review.openstack.org/20299704:49
*** haomaiwa_ has joined #openstack-swift04:49
*** haomaiwang has quit IRC04:49
openstackgerritHisashi Osanai proposed openstack/swift: Add functional test for access control (POST) with Keystone  https://review.openstack.org/20299905:00
*** haomaiwa_ has quit IRC05:01
*** haomaiwang has joined #openstack-swift05:02
openstackgerritHisashi Osanai proposed openstack/swift: Add functional test for access control (OPTIONS) with Keystone  https://review.openstack.org/20301205:08
*** SkyRocknRoll_ has joined #openstack-swift05:13
*** silor has joined #openstack-swift05:24
*** silor has quit IRC05:24
*** silor has joined #openstack-swift05:28
*** janonymous has joined #openstack-swift05:31
*** haomaiwang has quit IRC06:01
*** haomaiwa_ has joined #openstack-swift06:02
openstackgerritHisashi Osanai proposed openstack/swift: Add functional test for access control (PUT ACL) with Keystone  https://review.openstack.org/21360806:24
*** mahatic has quit IRC06:29
openstackgerritHisashi Osanai proposed openstack/swift: Add functional test for access control (PUT ACL) with Keystone  https://review.openstack.org/21360806:30
*** baojg has quit IRC06:39
openstackgerritHisashi Osanai proposed openstack/swift: Add functional test for access control (PUT ACL) with Keystone  https://review.openstack.org/21360806:47
*** geaaru has joined #openstack-swift06:54
*** sileht has quit IRC06:55
hogerrit is quite slow...06:55
*** sileht has joined #openstack-swift06:56
*** haomaiwa_ has quit IRC07:01
*** haomaiwang has joined #openstack-swift07:02
*** rledisez has joined #openstack-swift07:02
*** baojg has joined #openstack-swift07:03
-openstackstatus- NOTICE: Gerrit is currently under very high load and may be unresponsive. infra are looking into the issue.07:07
*** mahatic has joined #openstack-swift07:22
*** haomaiwa_ has joined #openstack-swift07:40
*** haomaiwang has quit IRC07:40
*** haomaiwa_ has quit IRC08:01
*** haomaiwang has joined #openstack-swift08:02
*** mahatic has quit IRC08:18
*** akle has joined #openstack-swift08:21
*** jistr has joined #openstack-swift08:21
*** baojg has quit IRC08:23
openstackgerritHisashi Osanai proposed openstack/swift: Add functional test for access control (PUT ACL) with Keystone  https://review.openstack.org/21360808:27
*** fbo has joined #openstack-swift08:29
*** mahatic has joined #openstack-swift08:30
openstackgerritHisashi Osanai proposed openstack/swift: Add functional test for access control (DELETE ACL) with Keystone  https://review.openstack.org/21362908:36
*** baojg has joined #openstack-swift08:39
*** haomaiwang has quit IRC08:43
*** haomaiwang has joined #openstack-swift08:44
*** ho has quit IRC08:44
*** kei_yama has quit IRC08:52
*** jordanP has joined #openstack-swift08:57
*** haomaiwang has quit IRC09:01
*** haomaiwang has joined #openstack-swift09:02
*** SkyRocknRoll_ has quit IRC09:09
openstackgerritCharles Hsu proposed openstack/python-swiftclient: Convert http response(byte string) to utf8 string.  https://review.openstack.org/21364009:11
*** DaveBCN has joined #openstack-swift09:12
*** akle has quit IRC09:17
openstackgerritCharles Hsu proposed openstack/python-swiftclient: Convert http response(byte string) to utf8 string in python3.  https://review.openstack.org/21364009:19
*** akle|2 has joined #openstack-swift09:26
*** SkyRocknRoll has quit IRC09:29
*** SkyRocknRoll_ has joined #openstack-swift09:31
*** SkyRocknRoll has joined #openstack-swift09:43
*** silor has quit IRC09:43
*** Guest47951 is now known as d0ugal09:49
*** d0ugal has quit IRC09:49
*** d0ugal has joined #openstack-swift09:49
*** DaveBCN has quit IRC09:55
*** acoles_ is now known as acoles09:59
*** haomaiwang has quit IRC10:01
acolesgood morning10:01
*** haomaiwang has joined #openstack-swift10:02
*** silor has joined #openstack-swift10:08
mahaticgood morning, acoles10:13
-openstackstatus- NOTICE: review.openstack.org (aka gerrit) is going down for an emergency restart10:23
*** ChanServ changes topic to "review.openstack.org (aka gerrit) is going down for an emergency restart"10:23
*** baojg has quit IRC10:24
*** baojg has joined #openstack-swift10:25
*** baojg has quit IRC10:48
*** ChanServ changes topic to "Review Dashboard: https://goo.gl/eqeGwE | Summary Dashboard: https://goo.gl/jL0byl | Hackathon topics: https://etherpad.openstack.org/p/swift-midcycle-aug-2015 | https://etherpad.openstack.org/p/swift_encryption_issues | Logs: http://eavesdrop.openstack.org/irclogs/%23openstack-swift/"10:49
-openstackstatus- NOTICE: Gerrit restart has resolved the issue and systems are back up and functioning10:49
*** haomaiwang has quit IRC11:01
*** haomaiwang has joined #openstack-swift11:02
*** leopoldj has joined #openstack-swift11:04
*** marcusvrn has joined #openstack-swift11:05
*** cdelatte has joined #openstack-swift11:15
*** delattec has joined #openstack-swift11:15
*** sakaYK has joined #openstack-swift11:23
*** sakaYK has quit IRC11:23
*** delattec has quit IRC11:26
*** cdelatte has quit IRC11:26
*** sanchitmalhotra has quit IRC11:36
*** haomaiwang has quit IRC11:36
*** leopoldj has quit IRC11:44
*** janonymous has quit IRC11:53
*** chlong has quit IRC11:59
*** robefran has quit IRC12:19
*** hrou has joined #openstack-swift12:33
onovyPLS https://review.openstack.org/#/c/192562/ https://review.openstack.org/#/c/192198/ someone for review? waiting ~2mons12:34
*** ekarlso has quit IRC12:44
*** ekarlso has joined #openstack-swift12:44
*** robefran has joined #openstack-swift12:49
*** jrichli has joined #openstack-swift12:50
openstackgerritKazuhiro MIYAHARA proposed openstack/swift: Fix disparsion-reports error message  https://review.openstack.org/21369712:52
*** robefran has quit IRC13:03
*** lifeless has quit IRC13:05
tdasilvagood morning13:11
*** haomaiwa_ has joined #openstack-swift13:13
*** dustins has joined #openstack-swift13:13
pgbridgegood morning13:16
*** dustins has quit IRC13:21
*** dustins has joined #openstack-swift13:26
*** lifeless has joined #openstack-swift13:28
*** cdelatte has joined #openstack-swift13:29
*** delattec has joined #openstack-swift13:29
*** NM has joined #openstack-swift13:30
*** lpabon has joined #openstack-swift13:39
*** changbl has joined #openstack-swift13:43
*** ccavanna has joined #openstack-swift13:45
*** SkyRocknRoll_ has quit IRC13:46
*** peluse1 has joined #openstack-swift13:50
*** petertr7_away is now known as petertr713:56
*** zul has joined #openstack-swift13:58
*** sakaYK has joined #openstack-swift13:59
*** breitz has joined #openstack-swift14:00
*** minwoob has joined #openstack-swift14:00
*** haomaiwa_ has quit IRC14:01
*** tongli has joined #openstack-swift14:01
*** haomaiwang has joined #openstack-swift14:02
*** lpabon has quit IRC14:03
*** chlong has joined #openstack-swift14:03
*** dustins has quit IRC14:06
*** bill_az has joined #openstack-swift14:06
*** dustins has joined #openstack-swift14:08
*** jkugel has joined #openstack-swift14:12
*** lpabon has joined #openstack-swift14:15
*** janonymous has joined #openstack-swift14:19
*** lpabon has quit IRC14:28
*** lpabon has joined #openstack-swift14:30
*** baojg has joined #openstack-swift14:43
*** NM has quit IRC14:43
jrichliacoles: I guess you made it back in one piece :-)14:43
jrichliacoles: for the 'encrypt-me' flag for probe tests, what do you think of setting the crypto override in the environment upfront instead of using a new flag?14:45
*** jlhinson has joined #openstack-swift14:48
*** annegentle has joined #openstack-swift14:48
acolesjrichli: yep not too bad a journey back14:48
acolesjrichli: the probe tests would (i imagine) send requests to the server so would not have access to the request environ to set a flag there. But an encrypt-me=False header could be mapped to crypto.override, by the keymaster i guess14:50
jrichliacoles: ok.  I didn't know what types of things the probetests could do - since they dont seem as restricted to testing the api as functests14:51
acolesjrichli: in general they still call the API but can also go dig around the backend servers, run/kill processes etc14:52
*** lpabon has quit IRC14:53
jrichliacoles: ok.  could we make the flag a crypto override, so its in the request only to say - don't encrypt?  this would map more directly to the current override concept.14:54
*** changbl has quit IRC14:55
*** wbhuber has joined #openstack-swift14:55
acolesjrichli: didn't we discuss having a probe test use BYOK (so enable rather than disable crypto) so that the test could then verify on disk cipher text?14:55
*** dustins has quit IRC14:57
jrichliacoles: yes, but I thought we also talked about being able to control the key used from a simulated key server.  we can do the BYOK for now, tho14:57
acolesjrichli: oic, so BYOK to force they key, and an override flag to force no generated key.14:59
acoless/they/the/14:59
jrichliacoles: yes, I think that is what I was thinking - good summary!14:59
*** changbl has joined #openstack-swift15:00
*** lpabon has joined #openstack-swift15:00
*** haomaiwang has quit IRC15:01
*** peluse1 has quit IRC15:01
*** dustins has joined #openstack-swift15:02
*** haomaiwang has joined #openstack-swift15:02
*** morgan_503 is now known as morgan_254915:06
*** esker has joined #openstack-swift15:08
*** baojg has quit IRC15:09
*** dustins has quit IRC15:10
*** haomaiwang has quit IRC15:12
*** ajiang_ has joined #openstack-swift15:13
jrichliacoles mahatic: I just summarized this in the trello card https://trello.com/c/8Y3yOJWZ/49-add-a-header-encrypt-flag-for-trivial-keymaster-to-use-in-probetests15:14
notmynamegood morning15:16
*** zul has quit IRC15:18
*** chlong has quit IRC15:18
*** tsubic has quit IRC15:20
janonymousMorning15:22
hurricanerixThanks again jrichli and IBM for hosting the hackathon.  I had a great time (especially the panic house thing).15:23
jrichlihurricanerix: you and all swifters are certainly welcome!  I am glad you enjoyed it.15:24
hroujrichli, acoles, glad you both made it back ! Nice summary jrichli, the one other point I recall is when you supply your own key we're going to want the probe test to find out the IV (but I recall acoles mentioned this would be possible), this is if you want to know the cipher text15:24
*** dustins has joined #openstack-swift15:26
acoleshrou: yes. so the test would PUT an obj with BYOK, then go find the obj on disk, read metadata to get IV (which is in plaintext sysmeta) then calculate expected on disk ciphertext (given BYOK value and IV) and compare.15:26
acoless/IV/nonce/ :)15:26
jrichliyes!  thanks acoles and hrou15:27
hrouacoles, I do like nonce better ; )  Yep perfect !15:27
hroujrichli, did you want me to update the trello ?  Though I realized I don't have permission to do that : )15:27
jrichlihrou - thanks for the offer.  since you dont have perms yet, i can do that.  notmyname: could you add hrou (Hamdi Roumani) to the encryption trello?15:29
notmynamehrou: what's your trello id?15:29
mattoliveraumorning15:30
hrounotmyname, thanks ! hamdiroumani15:30
notmynamedone15:31
notmynamealso added mahatic15:31
jrichlimattoliverau!  you aren't usually on now.15:31
notmynamehe stayed in texas!15:31
*** chlong has joined #openstack-swift15:31
hrounotmyname, thanks, and thanks jrichli for the update.15:31
jrichlinotmyname: thanks!  i will have one more for you to add soon - but i dont think jon has an account yet15:32
hroumattoliverau, how was the drive down ?  (or up I guess : - ).15:32
mahatichello!15:32
mahaticjrichli: cool cookies! :)15:32
jrichlimahatic: hello!15:32
notmynamejrichli: yeah, when is he getting his paperwork to contribute done?15:32
jrichlimahatic: thanks :-)15:32
mahaticnice pictures on twitter notmyname15:32
* mahatic reading scrollback15:33
jrichlinotmyname: he got is official stamp during this week - now just has to make all the accounts15:33
notmynamegreat15:33
jrichlinotmyname mattoliverau: oh, right ... with rackers.  Having fun?15:33
mattoliveraujrichli: yeah still in Texas, in SAT.15:33
*** chsc has joined #openstack-swift15:34
mattoliverauhrou: it was fine, much shorter then the inital flights the travel agent booked.15:34
*** dustins has quit IRC15:35
*** ccavanna has quit IRC15:35
notmynameemails and IRC buffers read, kids dropped off for first day of school. time to commute15:37
mattoliveraujrichli: yup, hurricanerix took mrda and I out shooting like real Texans yesterday :)15:37
* notmyname back online later15:38
hroumattoliverau, ha! yea can't believe they were suggesting that at some point : )15:38
*** chlong has quit IRC15:38
jrichlimattoliverau: was that out in the wild, or at a facility?15:39
mattoliveraujrichli: shooting range, middle of the day, really hot.. but we had fun :)15:40
jrichlinice!  Now you just need boots and a hat15:40
janonymousSounds cool :)15:40
*** chlong has joined #openstack-swift15:40
mattoliveraujrichli: lol, yup, then I'd be a real Texan ;)15:40
janonymousTexas Poker :D15:41
mattoliverauWell I guess I'd better write an update to the sharding spec reflecting hackathon while it''s still fresh.15:42
mattoliveraujanonymous: lol, hat first :P15:42
mrda...and fwiw, mattoliverau is a gun shark. He's a pretty good shot :)15:42
jrichli[10:26]  <notmyname> overall, I think it went well. it got off to a rough start, IMO, as we were figuring out the "schedule" and how to work together. but it ended (last 2 days) really well15:42
jrichli[10:27]  <notmyname> adn you and IBM did great as a host. it was great15:42
jrichlijanonymous: you mean Texas Hold'em?15:42
jrichlioops15:42
janonymousYup :P15:42
jrichlipaste didnt work out for me so well today15:42
mattoliveraumrda: lol, beginners luck.15:44
janonymousSounds crazy holidays guys.. seems like hangover part 4 ;)15:44
*** dustins has joined #openstack-swift15:50
*** robefran has joined #openstack-swift15:51
*** nadeem has joined #openstack-swift15:51
acolesmattoliverau: heh, so topgolf and topgun in same week15:53
mattoliverauacoles: lol, yup. And we drove past a topgolf here in SAT.. maybe I should have joined as a life member ;)15:56
*** lcurtis has joined #openstack-swift15:56
*** gyee has joined #openstack-swift15:56
mattoliverauacoles: how was the flight home?15:56
*** SkyRocknRoll has quit IRC15:56
*** SkyRocknRoll has joined #openstack-swift15:57
*** SkyRocknRoll has quit IRC15:57
acolesmattoliverau: not too bad thanks. got lucky with an empty seat next to me.15:57
acolesmattoliverau: turns out there is topgolf in uk. but nowhere near me.15:58
*** SkyRocknRoll has joined #openstack-swift15:58
mattoliverauacoles: roadtrip!!16:00
acoleslol16:01
jrichliacoles: globalization.  you travel across the ocean to see the same stuff :-)16:01
acolesjrichli: mattoliverau i bet the uk version has wooden clubs and you have to go pick up your own balls16:02
jrichliacoles: lol16:03
wbhuberacoles: also the uk version has higher wind speed, thanks to st.andrews!16:03
*** dosaboy_ has joined #openstack-swift16:04
*** dosaboy_ has quit IRC16:04
acoleswbhuber: that too ;)16:04
*** dosaboy has quit IRC16:04
mattoliveraulol16:04
pgbridgehard mode16:07
lcurtishello all...so trying to verify something... so I was under general impression that for a failed drive being swapped with a day that one would not have to set weight to zero--just simply replace drive16:07
lcurtisthough from Joe Arnold's book, recommending to remove the failed drive from the ring16:08
*** rledisez has quit IRC16:08
lcurtisabove should read a drive being swapped within a day16:08
*** dosaboy has joined #openstack-swift16:09
lcurtisshould i indeed be setting weight to zero for a failed drive16:09
lcurtis?16:10
lcurtisthen replacing?16:10
*** pbourke has quit IRC16:10
*** pbourke has joined #openstack-swift16:11
ctennisyou only need to set it to weight 0 if it will be an extended period of time before you replace it16:11
ctennisif it's going to be within the day, I woudn't worry about it16:11
hroujrichli, mattoliverau  I wonder if you could combine top golf and a shooting range, that way if someone is getting ahead if you score wise, you just start shooting their golf balls in flight16:12
*** jordanP has quit IRC16:12
jrichlihrou: lol16:13
*** david-ly_ is now known as david-lyle16:15
*** jistr has quit IRC16:19
lcurtisctennis: thanks16:19
ctennislcurtis: the only downside to leaving the disk in the ring is that operations that want to read/write to it will have some added latency as they try, fail, then move to the next disk.16:19
lcurtisokay...awesome16:21
lcurtismakes sense16:21
*** peluse1 has joined #openstack-swift16:24
peluse1acoles, yo, how was the trip home?16:24
acolespeluse1: ok thx. bit groggy today but not too bad.16:25
peluse1that's cool, takes me forever to recover from that kind of time change anymore...16:26
acolespeluse1: got your review on my todo but had cam back to some firefighting16:26
peluse1hey, I need to lobby hard for reviews on patch 212187 patch 213147 this week... next week a few SS guys (maybe clayg included) are coming to Chandler to help debug remaining issues on running EC under heavy load16:26
patchbotpeluse1: https://review.openstack.org/#/c/212187/16:26
peluse1two of them now :)16:26
peluse1patch 2134716:27
patchbotpeluse1: https://review.openstack.org/#/c/21347/16:27
peluse1hmm, patchbot didn't like listing two patches in one thingy....16:27
acolespeluse1: k. your one down from top of my list!16:27
peluse1acoles, sweet.  let me know if there's something I can look at for you in the meantime - be happy to16:27
acolesnah patchbot is like, 'one thing at a time man'16:28
peluse1acoles, also, what did you and clayg end up wrt plan for opt. GET?  you on diskfile and me on proxy?16:28
acolespeluse1: oh were we supposed to make a plan ? :P16:29
acolespeluse1: that split would work. at least i would start with diskfile changes then work out from there.16:29
peluse1heh, wasn't sure :)16:29
wbhuberpeluse1: what kind of remaining issues running EC under heavy load that you saw?16:29
acolesso if you get round to proxy changes then let me know when you make a start16:30
peluse1acoles, OK I will start on proxy probably today and just use the 2 headers we talked about as our i/f and dummy something up in my patch for testing...16:30
wbhuberare those issues the ones we discussed last week at hackathon (503 overwrite, etc.)?16:30
acolespeluse1: cool16:30
peluse1wbhuber, unclear because the cluster wasn't under my control.  I saw some exceptions but by the time I got to the cluster the benchmark team had already done like 6 things to it and I couldn't seem to get them trained to operate in debug mode...16:30
peluse1so I'm taking over the cluster next week :)16:31
wbhuberah, need a real person controller to see what went wrong.16:31
wbhuberdo keep minwoo and i in the loop with your findings.16:31
peluse1wbhuber, the last exception I was able to debug turned out to be a bogus log statement that clayg addressed and might already be merged16:31
wbhuberpeluse1: were you and bill able to saturate the cluster over the network while running workloads on EC?16:32
*** lyrrad has joined #openstack-swift16:33
peluse1wbhuber, no.  we couold no problem with 3x so we are confident in the HW and SW setup (finally) however they kept running into stupid little things that blocked us from really going ful throttle and since they are not staffed for doing SW debug they pretty much punted16:33
wbhuberpeluse1: at least they know how to punt.   minwoo and i are doing both SW debug and HW cluster setup.16:35
peluse1yeah, its been frustrating from both sides but at least they're letting me 'borrow' the full rack to get things in order before turning it back over to them for perf testing16:36
*** obiwandev has joined #openstack-swift16:38
peluse1wbhuber, if you have a chance and can take a look at those 2 patches I just mentioned that'd be great too16:48
*** lpabon has quit IRC16:50
*** mfalatic has joined #openstack-swift16:51
*** haypo has joined #openstack-swift16:51
*** mfalatic_ has joined #openstack-swift16:52
haypohello! is someone available to review my patch https://review.openstack.org/#/c/199034/ "Fix tox -e py34" -- it provides a basic python3 support to start working on porting swift to python316:52
haypoit allows to make the py34 gate voting to ensure that we don't go backward in python3 support16:52
haypoPyEClib 1.0.8 was tagged in Git two weeks ago, but there is no release on PyPI!? https://bitbucket.org/kmgreen2/pyeclib/issues/69/need-a-release-108-with-python-3-fixes16:53
haypo(PyEClib 1.0.8 includes my python3 changes, so my sed hack in tox.ini is no more needed)16:54
*** NM has joined #openstack-swift16:54
notmynameacoles: peluse1: patches welcome for patchbot ;-)16:55
*** mfalatic has quit IRC16:56
hayponotmyname: hi. i'm back from 2 weeks of holiday. i don't remind if you like my change or not :)16:56
peluse1haypo, I'l ping tsg wrt the pyeclib release16:56
haypoi have to read again the latest comments16:56
notmynamehaypo: I don't either ;-)16:56
hayponotmyname: haha, no problem16:57
haypopeluse1: oh, cool16:57
haypopeluse1: i don't understand why a version was tagged without tarball released on PyPI16:57
*** zaitcev has joined #openstack-swift16:57
*** ChanServ sets mode: +v zaitcev16:57
haypozaitcev: ah! you already voted +2 on the patch set 12 of https://review.openstack.org/#/c/199034/ you should revote ;) (i had to rebase my patch)17:04
peluse1haypo, texting with tsg - both of us are laptop-less today :(  He said they can't push latest to pypi because of a jerasure change17:04
peluse1eta getting close though17:05
haypopeluse1: ah? which change?17:05
haypopeluse1: a bug?17:05
zaitcevI wish someone made Kevin to cut releases and not just "push latest to pypi" and consider it done.17:05
peluse1haypo, I do't beleive so.  I don't want to mis-speak though.  The last push should be noon tpday17:06
notmynameyeah, we're working on improving the situation around pyeclib/liberasurecode, with regard to releases17:06
notmynameit was something I brought up with quite a few people last week at the hackathon. I should have a resolution for what to do Real Soon Now17:07
wbhubernotmyname: such as incorporating pyeclib into swift?  since it is not openstack material i don't think we reached a consensus on what to do with the package yet... right?17:10
hayponotmyname: pyeclib 1.0.8 installs liberasurecode 1.0.8, pyeclib has an embedded copy of liberasurecode-1.0.8.tar.gz17:11
haypofor me, it's the best option, but i heard that it's compromise17:11
zaitcevwbhuber: pyeclib did not shed all of C, it still builds an adapter for Python.17:11
notmynamewbhuber: no, it won't be in the swift source tree. it's more of getting more people with commit rights and where the official repo lives. with more people, especially those who are using it, we'll have better releases. the releases are the only real problem I'm aware of right now (although some of those issues are related to some internal coupling)17:14
*** obiwandev has quit IRC17:14
mattoliverauhrou: lol (sorry for the late response, I get pulling into meeting people in the office) :)17:18
hroumattoliverau, jrichli oh no worries at all !  Yea seems like a good franchise opportunity, best of both worlds ; - )17:19
peluse1notmyname, so my laptop is dead today so I'm on a different machine and had to start from scratch and haven't done so since that hacking update not too long ago.  I think it ight be breaking me as I can run unitests w/o issue but once I isntall tox things go to hell and I get like 28 tests fail.  I can't find that patch though that you pointed me to before where clayg commented "do this if things pass locally and fail in the gate"?17:23
hroupeluse1, 205977 ?17:25
hroupatch 20597717:26
patchbothrou: https://review.openstack.org/#/c/205977/17:26
peluse1yes, thanks :)17:26
hrouAnd you'll probably need tox -r as well btw17:26
peluse1trying it now...17:27
*** geaaru has quit IRC17:37
notmynameoh good :-)17:38
*** SkyRocknRoll has quit IRC17:39
peluse1hrou, so that didn't fix me but I resoted a snapshot from before I tried to install tox using pip and this time installed using apt-get and it works fine.  older version I supose - I dunno17:39
hroupeluse1, hmm odd, but does the older version predate that patch above that changed the test requirements ?  Let me know if you run into it again though!17:41
peluse1hrou, beats me :)  I did upgrade the test-reqs before trying with both the pip tox and the apt-get tox (1.6.0 BTW) and only the apt-get works for me at least17:42
hroupeluse1, : )  Interesting !  Let me know if you have issues again, the magic for me was -r which rebuilds the tox env (and as such the package versions)17:43
hroupeluse1, glad its working for you now though!17:43
peluse1hrou, will do.  since I have a working setup saved as snapshot I'll try upgrading tox and see if it works - if not I'll give up for now and just use the old one17:43
hroupeluse1, it'd be funny to see how many snapshots folks have while trying to setup something, I know when I was trying to get storlets, keystone, swift all working (which is an effort) I had over 20 snapshots at one point ; )17:44
peluse1hrou, nice!  yeah what did we do before VMs??17:48
*** lpabon has joined #openstack-swift17:50
*** dbarman has joined #openstack-swift17:50
dbarmanCan anyone tell me how the replication works?  How often does it send replication packets?  my swift-recon -r shows the last replication was 57 minutes ago17:51
dbarmanis there a way to speed up the replication process?17:51
dbarmanAlso, is there was to tell when the replication is 100% complete?17:52
hroupeluse1, cry a lot, or break things, depending on your personality, Kids these days just don't appreciate how easy it is : - )17:52
peluse1lol!17:52
mahaticjrichli: about the patch, you mean, remove from "encrypter.py"?17:54
*** lpabon has quit IRC17:55
mahaticjrichli: I thought you were talking about the test file! got it17:56
jrichlimahatic: yes.  and when you modify decrypter tests to stop using that method, then you can remove that method from the decrypter17:56
*** zul has joined #openstack-swift17:56
mahaticjrichli: right, thanks17:56
*** acoles is now known as acoles_17:58
dbarmanCan anyone tell me how the replication works?  How often does it send replication packets?  my swift-recon -r shows the last replication was 57 minutes ago17:59
*** dustins has quit IRC17:59
notmynamedbarman: you can find a lot of technical explanations of how different parts of swift work at http://docs.openstack.org/developer/swift/ and https://swiftstack.com/openstack-swift/18:00
*** dustins has joined #openstack-swift18:01
wbhuberpeluse: acoles: re: increasing durable quorum to parity + 1 to tell the world that an objec tis rebuildable with enough fragments, do we do it in the 2nd phase when we send a commit confirmation to participating object servers?  i'm looking inside _get_put_responses with need_quorum enabled.18:01
*** zhill has joined #openstack-swift18:02
*** lpabon has joined #openstack-swift18:02
haypopeluse1: maybe it's better to wait for the PyEClib release on PyPI18:04
haypopeluse1: instead of pushing my sed hack18:04
haypopeluse1: since we are now really close to an effictive release ;)18:04
peluse1haypo, yeah probably18:05
peluse1wbhuber, yes18:06
peluse1wbhuber, today its the sending of the commit messge that only requires 218:06
haypofor my "pep8" patch serie, i'm fine with keeping checks skipped18:07
haypowe just have to agree on which tests are revelant or not18:07
haypochecks*18:07
*** zhill_ has joined #openstack-swift18:07
peluse1wbhuber, look in _store_object() where min_conns is set to 218:07
*** zhill has quit IRC18:07
wbhuberyes18:07
haypoi may open a thread on openstack-dev to discuss pep8 in swift18:08
dbarmandustins: is it common for replication to wait over an hour?18:20
dbarmanthere other issue I am not sure about is.  I have two storage nodes.  Once is almost 100% full, the other one is just 7% full.  Doesn't it spread the data over all the nodes somewhat evenly?18:21
dustinsdbarman: Hmm? Sorry I don't quite know the context18:21
dbarmandustins:  Are you referring to my last inquiry or the question about the over 1 hour for replication?18:22
dustinsthe one you mentioned me on :)18:22
*** kutija has joined #openstack-swift18:23
ctennisin general yes it will dbarman18:23
dbarmandustins: ok.  The context is that I recently added a second node.  So swift started to replicate to the new node.  However, when I checked the replication status this afternoon, it indicated that the last replication was about 1 hour ago.  I am wondering why it is waiting to continue the replication or how I can tell if the replication is 100% complete18:24
dbarmanctennis:  nice to hear from you again.18:24
dbarmanctennis:  So does it just take a long time to attempt to move the data to the new node or do you think someting is wrong?18:25
ctennisdbarman: you need to post the layout of your ring files so we can verify you have them configured right.  Also please check for any additional errors.18:25
dustinsdbarman: I'll be honest, I don't really know the first thing about Swift (yet), I was just curious as to why you pinged me :P18:25
dustinsthat was the context I wanted, haha18:25
ctennisdbarman: I think something is wrong.  It would help if we could see log files as well.18:25
*** lpabon has quit IRC18:25
dbarmanctennis: ok.  what is the best way to show my ring file layout?18:26
dbarmanctennis: and the log files18:26
notmynamehaypo: what are you wanting to discuss on the mailing list about pep8 in swift that isn't discussed in here?18:26
ctennisswift-ring-builder object.builder and post the output somewhere list gist.github.com you can share18:26
ctennisfor log files, find a place you can upload and share and give a link18:26
dbarmanctennis:  ok.  you mean the syslog file, right?18:28
*** lpabon has joined #openstack-swift18:28
dbarmanctennis:  That is the only log I am aware of18:28
hayponotmyname: the question is to decide which checks should stay skipped18:28
ctennisdbarman whatever you can find to share18:28
hayponotmyname: i started to send patches to reduce the number of skipped checks18:29
dbarmanctennis:  lol.  ok18:29
hayponotmyname: i'm not really motivated to fix all pep8 checks, it's just a follow up of my patch to upgrade hacking from 0.8 to 0.1018:30
notmynamehaypo: for the time being, if there are style changes that are required for py3 (ie py27 formatting is simply not allowed/not supported in py3), then fix it. if it's something else, then don't18:30
notmynamethe list of stuff we currently don't check on is not a todo list of style fixes18:30
hayponotmyname: there is a single check related to python3, and janonymous already wrote a patch for it18:30
hayponotmyname: samuel likes 3 of my patches18:31
haypohttps://review.openstack.org/#/c/213491/ pep8: replace deprecated calls to assert_()18:31
notmynamegreat18:31
haypohttps://review.openstack.org/#/c/213494/ pep8: Fix usage of the l10n _('...') function18:31
haypohttps://review.openstack.org/#/c/213495/ pep8: Don't override '_' symbol18:31
hayponotmyname: my current patches, https://review.openstack.org/#/q/status:open+project:openstack/swift+branch:master+topic:pep8,n,z18:31
*** annegentle has quit IRC18:32
notmynamestyle changes are one of the things that are a "doesn't matter, default to yes" sort of change. it's not something that is prioritized, and it shouldn't have a ton of time spent on it. there's a *lot* of other things going on that need the mental effort18:33
notmynamegotta run for a bot18:34
hayponotmyname: tox -e pep8 has different kind of checks. some of them finds real bugs18:35
hayponotmyname: like H702 "Formatting operation should be outside of localization method call" - https://review.openstack.org/#/c/213494/18:36
*** silor has quit IRC18:38
dbarmanctennis:  will have logs posted shortly18:42
openstackgerritBill Huber proposed openstack/swift: Quorum on durable response is too low  https://review.openstack.org/21382219:01
*** mahatic has quit IRC19:01
*** sakaYK has quit IRC19:02
wbhuberpeluse: for the patch 213822, let me know if you'd like more testing on putters that have adequate successes (i.e. statuses > min_of_responses).19:02
patchbotwbhuber: https://review.openstack.org/#/c/213822/19:02
*** annegentle has joined #openstack-swift19:05
openstackgerritJanie Richling proposed openstack/swift: Encrypter and Decrypter middleware - object body only  https://review.openstack.org/19419119:06
*** lpabon has quit IRC19:13
*** lpabon has joined #openstack-swift19:19
peluse1wbhuber, looks like clayg just commented on exactly that!19:22
wbhuberpeluse1: yes, lol.  GMTA.19:22
dbarmanctennis: can't upload files to github.  is there somewhere else I can upload the logs files to?19:23
ctennishow big are they?19:23
*** lpabon has quit IRC19:23
*** petertr7 is now known as petertr7_away19:24
dbarmanctennis: one's about 100MB the other about 30MB19:27
ctennisI dunno, maybe something like dropbox?19:28
ctennisor google drive19:28
ctennisor amazon s319:28
dbarmanctennis:  oh boy.. ok19:28
*** petertr7_away is now known as petertr719:29
*** silor has joined #openstack-swift19:31
dbarmanctennis:  try this: https://drive.google.com/folderview?id=0B1e8GRJ1mpZTfmZHY1BhRmNmbmY2cC1jb2xxeTNwNHEzSU9mUXpXU0ZBZHZTbm5BY1VfbUU&usp=sharing19:33
dbarmanctennis:  let me know if you can view the files or not19:36
openstackgerritMerged openstack/swift: Fix some minor typos  https://review.openstack.org/21337819:36
ctennisdbarman: all of the quarantine information is a bad sign19:37
ctennisdbarman: on the drives that are full, how much data is in the objects/ directory vs. how much is in the quarantine directory?19:37
dbarmanctennis: where is the quarantine directory?19:38
ctennison the disk19:38
ctennisyour object replicator is far from being done running19:40
ctennisAug 17 14:19:57 OSSN1 object-replicator: 167/2047 (8.16%) partitions replicated in 93002.61s (0.00/sec, 290h remaining)19:40
ctennisAug 17 14:24:57 OSSN1 object-replicator: 167/2047 (8.16%) partitions replicated in 93302.62s (0.00/sec, 291h remaining)19:40
ctennisAug 17 14:29:57 OSSN1 object-replicator: 167/2047 (8.16%) partitions replicated in 93602.62s (0.00/sec, 292h remaining)19:40
*** annegentle has quit IRC19:42
*** annegentle has joined #openstack-swift19:43
dbarmanctennis:  that is what I thought.  So that is why I was wondering that the swift-recon -r showed the last replication as over an hour ago. what do you think?19:45
ctennisnot sure19:45
ctenniswas your cluster just 2 disks before?19:45
dbarmanctennis:  I just did it again. now it says it has been 2 hours since most recent completion19:46
dbarmanyes, it was two disks on the first node and now the second node has 2 more disks19:46
ctennisperhaps that's just on the new node where the data is being replicated to and not from19:47
ctennisyes that's right, your new node is only taking about 2 hours to run through replication19:47
dbarmanthis is what it does:  [2015-08-17 15:45:36] Checking on replication [replication_time] low: 80, high: 154, avg: 117.2, total: 234, Failed: 0.0%, no_result: 0, reported: 2 Oldest completion was 2015-08-14 17:13:19 (3 days ago) by 10.0.0.51:6000. Most recent completion was 2015-08-17 16:51:54 (2 hours ago) by 10.0.0.52:6000. ===============================================================================19:47
ctennisright, so your old node has been 3 days since it completed19:48
ctennisbecause it's still in the middle of trying to complete19:48
dbarmanfriday is when I put the second node in play19:48
dbarmanie. 3 days ago19:48
ctenniskeep in mind, going from 2 disks to 4 disks isn't going to buy you much..swift wanted to keep 3 copies of data anyway and you only had two copies to begin with, so you didn't double your capacity19:49
dbarmanI was afraid of that19:49
dbarmanbut I should get 50% increase???19:49
ctennisyeah19:50
minwoobzaitcev: Can you expound on what you mean in https://review.openstack.org/#/c/198909/ ?19:50
dbarmanit just seems strange that it's been 2 hours.  in the earlier stages it was updating every 15 minutes or even faster19:51
dbarmanI am wonder if it stopped for some reason.  Did you see any error in the logs that might be an issue?19:52
dbarmanWhat should I do about quarantine (not sure where it is located).  Should they be deleted?  Does swift remove them automatically?19:52
ctennisit didn't stop.  All of the new data coming onto that node has to be scanned by the replicator which is adding to the time19:52
ctennisonce things settle down it will go back to ~15 minutes or wahtever you saw before19:52
ctennisI don't know what you tell you about the quarantine, swift just moves the data into the quarantine directory on the same disk as it existed before and lets you decide what to do with it.  The amount of quarnatine data you have indicates to me something is gravely wrong.19:53
onovynotmyname, hi, what about Tokyo summit? we didn't finish discussion :)19:54
dbarmanYeah, my hash pre/suffix values were incorrect on the second node.  once I corrected it the quarantine logs stopped.  pretty sure that was the source of the problem.19:54
dbarmanDo you know where the quarantine is located, I think I should just delete them19:54
ctennisit's on the same disks as your swift data, in a directory called "quarantine"19:55
onovymattoliverau, hi, did you had time for 192562 please?19:55
dbarmanI meant before pre/suffix hash values were wrong on the second node19:55
notmynameonovy: oh yeah. you were asking if it's "worth it", right?19:55
onovynotmyname, yep19:55
onovy[09:07:05] <onovy> notmyname, get "hot news" and meet another developers / admins of openstack swift.19:55
onovymy last message :)19:55
notmynameonovy: right19:55
notmynameonovy: I *always* think in-person and face-to-face conversation is good :-)19:56
dbarmanis it safe to delete the quarantine folder?19:56
dbarmanor it's contents19:56
notmynameonovy: so in that sense, Tokyo (and every openstack summit) is "worth it"19:56
ctennisit's safe, as long as you're not concerned about losing all of the data associated with it19:56
onovynotmyname, ok. so it's possible to meet some of dev/core-devs here and it's time to talk19:57
notmynameonovy: but it's like other tech conferences. you'll get out of it what you look for. if you're looking for a lot of conversations with people and wanting to meet people and you make that happen, it will be great!19:57
notmynameonovy: and if you want to learn more and go listen to a lot of talks, you can do that too19:57
dbarmanwell, I assume the data is bogus since my hashing was wrong.  What do you think?19:57
notmynameonovy: yes. most core devs and many people who are active in here will be there19:57
ctennisdbarman: the data doesn't change, just where it gets stored.  The risk is you may be deleting data you cannot recover/retrieve.  If you're okay with that, then delete.19:58
onovyperfect, i will try to come19:58
*** mfalatic_ has quit IRC19:58
*** mfalatic has joined #openstack-swift19:58
zaitcevminwoob: I do not like the "except Exception" construct, because I had an experience with them consuming unexpected exceptions. It is a condition that is difficult to debug. I allow for them to get caught in one place in a program. That's just me, however.19:59
onovynotmyname, so thanks. is there something what can i do for review of my patch please? waiting ~2mons and feature freeze is near.20:00
dbarmanother than deleted what is typical for quarantine?  can it be recovered? if so, in what method/way?20:02
ctenniswould take some work.  beyond my pay grade.20:02
notmynameonovy: I'm not sure where you are based, but know that Japan has some tougher visa requirements. please look into it today. http://lists.openstack.org/pipermail/openstack/2015-August/013749.html20:03
dbarmanlol20:03
onovyeu/cz20:03
dbarmanlooks like the quarantine folder is large.  I am trying to figure out it's size.  would du -hs tell me anything?20:04
dbarmanI am trying it but it is just sitting there..hmmm..20:04
ctennisthere's a lot of disk activity, give it a few minutes20:04
dbarmangood point20:05
*** silor1 has joined #openstack-swift20:05
dbarmanI will see if it ever responds20:05
minwoobzaitcev: It's better to have them in those places, so we know where it is caught, no?20:05
zaitcevminwoob: You're assuming that logging is reliable, but it's not.20:06
*** silor has quit IRC20:07
*** silor1 is now known as silor20:07
onovynotmyname, visa is not needed for eu/cz, so it's ok.20:09
notmynamegreat. I'm glad you checked20:09
onovyperfect and what about review? i'm really unmotivated about this long process20:10
claygonovy: what patch?20:13
notmynameonovy: which patch. I'm not currently mapping IRC to gerrit in my head ;-)20:13
onovyhttps://review.openstack.org/#/c/192198/20:14
onovyhttps://review.openstack.org/#/c/192562/20:14
onovythis two20:14
dbarmanctennis:  wow, du -hs command is still running, no response yet!20:15
claygonovy: looks like you've had reviews and made changes based on feedback - it just feel off the radar - pinging people in channel (particuarlly the people who have already reviewed them) is exactly what you're supposed to do20:16
claygonovy: I haven't looked at the recon patch - so I'll let mattoliverau torgomatic and notmyname review that (hit them up tomorrow if they don't)20:16
onovythanks20:16
claygI've already got the rsync one starred - it's a big change - so don't expect to hear anything from me until tomorrow - but you're welcome to ask me again if I have any first impressions20:17
notmynameand it looks like I owe you a review on the recon time sync patch20:17
notmynameonovy: at a meta level, though, I'm sorry those have been open for such a long time. it's something we're working on chaning, and it's something we specifically talked about last week at the swift hackathon.20:18
notmynameI hope we'll be getting better in the future (but I realize that's small comfort to you now about these patches)20:19
claygnotmyname: although in fairness I don't think we came up with anything I expect to make the situation drastically different other than...20:19
clayga) ask for reviews (it's not rude) b) help with reviews (obviously we have too many)20:19
notmynamethere were a couple of things, I think. yeah, those were some of them20:20
notmynameI've got it in my notes. haven't had time to collect it all yet :-)20:20
onovyexactly i'm thinking about employ in one person for part/full time for Swift coding in our company, but it's hard when review process takes so long20:20
claygonovy: if you want to employ them full time you should have them do reviews full time20:20
*** jlhinson has quit IRC20:20
onovythats good point20:21
*** jlhinson has joined #openstack-swift20:21
onovyi have already done few reviews and i'm not sure if it is usefull20:21
claygonovy: -1's are the most useful20:21
notmynameit is!20:21
onovyalready gave some -1 :)20:22
clayg+1's are only useful if they were "I checked this out and ran it, all the tests (including probe & func) pass on my machine, code is all readable, commit clearly explains the change and references launchpad/bugs/DocImpact, it has new unittests, unittests fail if you remove the change, and here's some additional notes for reviews to help them get started testing this change functionally"20:23
*** dbarman1 has joined #openstack-swift20:26
dbarman1ctennis: you still around?20:26
ctennisyes20:26
onovyok20:26
dbarman1still no go on the du command.  Seem reasonable?20:27
ctennisnot sure20:27
dbarman1lol20:27
dbarman1ok.20:27
claygonovy: do you have the review dashboard -> https://wiki.openstack.org/wiki/Swift/PriorityReviews20:27
onovyyep, it's in topic here20:27
clayggoing after the old changes is a good way to help keep the fodder down - or if you want to get more involved (social capital) you can grab some of the big high priority reviews and help out20:28
claygonovy: great!  you could also go dig up a change that's pending from one of the people that have done reviews for you and stick a -1 on that20:28
clayg... you know - unless by some off chance it's acctually ready to merge - then feel free to +1, or ping a core maintainer and let them know you think you found a change that's good to merge!20:29
claygonovy: good luck!20:30
onovythanks a lot :)20:30
claygc20:44
*** silor has quit IRC20:45
tdasilvanotmyname: hi, can you share a link to the community graphs you talked about last week?20:46
openstackgerritMinwoo Bae proposed openstack/swift: Error handling of DiskFileNoSpace()  https://review.openstack.org/19890920:46
notmynametdasilva: https://github.com/notmyname/git-stats20:48
*** robefran has quit IRC20:49
notmynametdasilva: gotta run ./build_swift_gerrit_history.sh and then ./swift_contrib_stats.py20:49
notmynametdasilva: and probably update it to not use my gerrit id and local paths ;-)20:50
tdasilvanotmyname: cool, thanks!20:50
onovyzigo, hi, are you here?20:51
*** dustins has quit IRC20:52
*** dbarman has quit IRC20:55
*** dbarman1 has quit IRC20:55
openstackgerritBill Huber proposed openstack/swift: Quorum on durable response is too low  https://review.openstack.org/21382221:06
claygwbhuber: I may be naming the "phases" of the ec PUT business in correctly21:12
claygwbhuber: replication has getexpect and getresponse21:12
claygwbhuber: most of the time in unittests when it's needed the fake's getexpect will return 10021:13
claygwbhuber: in EC land there's *another* 100 continue and the fake grew some arms to deal with introducing failures there - whatever *that* pahse is called - the second 100-continue - that's a different failure than when you just give the fake connect a 50321:14
onovymattoliverau, thanks! :)21:14
*** zul has quit IRC21:14
wbhuberclayg: ah, gotcha.21:14
claygand since that "second" phase (or whatever it's called) has to do with durables - seems like an interesting place to play with errors21:14
mattoliverauonovy: sorry I didn't answer before, I'm not at my computer too much today :)21:14
claygmattoliverau: how's that san antonio heat!?21:14
mattoliverauclayg: its cooler then Austin (but only be a few degrees) :(21:15
mattoliverauclayg: luckly the castle is nice and cool :)21:16
wbhubermattoliverau: that's rather odd.  SAT is actually 60 miles south of Austin - you should be feeling more heat than Austin21:16
claygmattoliverau: yay AC!21:16
wbhuberAustin got much cooler after the hackathon.21:16
wbhuberGuess it got too heated when you guys were here.21:16
mattoliverauwbhuber: well it feels cooler, maybe I'm now just aclimatised ;)21:16
claygwbhuber: lol!21:16
mattoliverauwbhuber: lol, it was great to meet you in person :)21:17
wbhubermattoliverau: likewise and i hope you remember the two signs "good morning and good night."21:17
mattoliverauwbhuber: I'll make sure I practice for next time!21:18
wbhubermattoliverau: i think it is a combination of you getting acclimatized & weather cooling down.  that's the icing of your trip.21:18
onovywhat do you think about setting ionice/nice of daemons directly in swift configuration files? we are using cron job for this, but it's not perfect.21:19
mattoliverauwbhuber: ready for me to travel back home to winter21:19
wbhubermattoliverau: it's really that brisk back home enough to wear a trapper hat?21:20
mattoliverauwbhuber: nah, it's Australia.. never really gets that cold ;)21:21
wbhuber;-)21:21
*** robefran has joined #openstack-swift21:29
openstackgerritMatthew Oliver proposed openstack/swift: Make swift-ring-builder filename usage more consistent  https://review.openstack.org/20978721:31
mattoliveraucschwede:  ^^ that patchset is just replacing some tabs with spaces that you placed in the test.21:32
mattoliverauthis is weird, I'm used to acoles_ and cschwede to start coming online now.. but they wont cause I'm not in my timezone. So I guess cschwede will see that later.21:34
notmynamemattoliverau: now you know how the rest of us feel about our european friends21:35
mattoliverauyeah :( why can't they be like clayg and never sleep.21:35
onovynobody needs ionice?21:43
openstackgerritOpenStack Proposal Bot proposed openstack/swift: Updated from global requirements  https://review.openstack.org/8873621:45
notmynameonovy: and there you go. the timing recon patch has been marked as approved21:46
claygnotmyname: oh sure - take the ducks21:46
onovynotmyname, noway! :)21:47
notmynametake the ducks? mattoliverau and torgomatic reviewed it21:47
onovycool21:47
notmynamewhat is "take the ducks"?21:47
clayglol21:47
mattoliverauclayg: are you calling me a duck :P21:48
claygapparently this is not a widely used euphemism21:49
claygit's a billards term for balls that are close to the pocket21:50
claygi.e. "the easy ones"21:50
clayghttps://en.wiktionary.org/wiki/Appendix:Glossary_of_pool,_billiards_and_snooker21:50
notmynameclayg: google says it's this: http://www.wikihow.com/Take-Care-of-Ducks21:50
onovynotmyname, lol21:51
claygnotmyname: yeah that's it21:51
hrouwow I love the fact there is a part 3 "activities for the ducks", apparently they like to swim : )21:52
*** wbhuber has quit IRC22:00
*** petertr7 is now known as petertr7_away22:01
*** jkugel has quit IRC22:01
*** hrou has quit IRC22:05
mattoliverauclayg: a duck in cricket (yes that game you don't understand) is a batter getting out with 0 runs.22:06
*** NM has quit IRC22:06
notmynameI understand it more now, thanks to mattoliverau and acoles_22:06
jrichlilol, the things you can learn on swift IRC!22:07
notmyname(at swift hackathons)22:07
mattoliveraunotmyname: then we've done our jobs well :)22:07
jrichliyes, we all learned how to select good tequila. :-)22:09
* jrichli is outta here22:11
*** jrichli has quit IRC22:11
notmynamemattoliverau: ok, here's what I learned about cricket:22:12
notmynameCricket is a game where Batman" has to protect Christian "hay" Bales from the bowler.22:12
notmynameThe bowler is called such because he wears a bowler hat. After Batman hits the ball away from the hay bales, he switches places with someone at another wicket (a stick in the ground).22:12
notmynameThe more times he runs to the wicket, the more points he scores. The trick is that everyone moves around the field during the game, including the bowler.22:12
notmynameGames last for days and days and they take tea-time breaks. The winner gets to burn down the other team's hay bales, thus the name given to the big tournament: The Ashes.22:12
mattoliveraunotmyname: lol! close enough :P22:13
notmynameI left the part out where there are 60 ways to get someone out while they are runnign to the wicket. sometimes even without them getting to a wicket at all22:14
*** nadeem has quit IRC22:14
mattoliverauand now you know about ducks22:15
notmynameah! that's it! the visiting team brings ducks and has to hold them during the game. the winner takes the ducks home. thus, "taking the ducks"22:16
notmynamealso, I had to be careful to not s/u/i/ there ;-)22:16
*** jlhinson has quit IRC22:16
mattoliveraunotmyname: lol, I'd love you see you start up cricket in SFO with those rules :P22:18
openstackgerritOpenStack Proposal Bot proposed openstack/swift: Updated from global requirements  https://review.openstack.org/8873622:20
mattoliveraunotmyname: so mrda sent me this.. and it'll clear up cricket for you :P22:20
mattoliverauYou have two sides, one out in the field and one in. Each man that's in the side that's in goes out, and when he's out he comes in and the next man goes in until he's out. When they are all out, the side that's out comes in and the side that's been in goes out and tries to get those coming in, out.22:20
mattoliverauSometimes you get men still in and not out. When a man goes out to go in, the men who are out try to get him out, and when he is out he goes in and the next man in goes out and goes in.22:20
mattoliverauThere are two men called umpires who stay all out all the time and they decide when the men who are in are out. When both sides have been in and all the men have been out, and both sides have been out twice after all the men have been in, including those who are not out, that is the end of the game!22:20
mattoliverau</sarcasm>22:21
notmynamethat actually makes sense to me now! ;-)22:21
mattoliveraulol22:22
*** marcusvrn has quit IRC22:23
mattoliverauk, I'm getting a lift back to my hotel now22:24
torgomaticwhat the duck just happened in here22:27
peluse1i didn't know tere were fellow pool players in the community... do they have pool tables in Tokyo?  :)22:28
*** annegentle has quit IRC22:30
* peluse1 off to Apple store to try and get laptop fixed...22:30
*** zul has joined #openstack-swift22:33
*** esker has quit IRC22:33
*** chlong has quit IRC22:34
*** minwoob has quit IRC22:38
*** lpabon has joined #openstack-swift22:44
*** km has joined #openstack-swift22:57
*** dbarman1 has joined #openstack-swift23:01
*** ho has joined #openstack-swift23:03
*** zul has quit IRC23:04
*** hrou has joined #openstack-swift23:07
*** nadeem has joined #openstack-swift23:10
hogood morning!23:11
*** lcurtis has quit IRC23:17
*** kei_yama has joined #openstack-swift23:17
*** sakaYK has joined #openstack-swift23:20
*** lpabon has quit IRC23:22
openstackgerritHisashi Osanai proposed openstack/swift: Add functional test for access control (PUT ACL) with Keystone  https://review.openstack.org/21360823:37
*** nadeem has quit IRC23:39
openstackgerritHisashi Osanai proposed openstack/swift: Add functional test for access control (DELETE ACL) with Keystone  https://review.openstack.org/21362923:39
openstackgerritHisashi Osanai proposed openstack/swift: Add functional test for access control (GET ACL) with Keystone  https://review.openstack.org/21393423:55

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