Tuesday, 2015-08-25

*** bi_fa_fu has joined #openstack-swift00:12
*** bi_fa_fu has quit IRC00:14
*** chlong has quit IRC00:18
*** flwang has joined #openstack-swift00:20
*** kevinc_ has quit IRC00:21
*** tellesnobrega_ has joined #openstack-swift00:22
*** tellesnobrega_ has quit IRC00:23
*** tellesnobrega_ has joined #openstack-swift00:23
*** tellesnobrega_ has quit IRC00:24
*** onovy has quit IRC00:25
*** zul has joined #openstack-swift00:34
*** onovy has joined #openstack-swift00:35
*** flwang has quit IRC00:40
*** zaitcev has quit IRC00:46
*** zaitcev has joined #openstack-swift00:49
*** ChanServ sets mode: +v zaitcev00:49
*** nakagawamsa has joined #openstack-swift00:49
hokota_: I would like to get in touch with kazuriho. could you tell my irc name to him?00:59
*** 64MADOHP4 has joined #openstack-swift01:12
*** hrou has joined #openstack-swift01:15
*** flwang has joined #openstack-swift01:21
*** 64MADOHP4 has quit IRC01:24
*** miya-test has joined #openstack-swift01:27
*** miya-test has quit IRC01:28
*** kota_ has joined #openstack-swift01:28
*** ChanServ sets mode: +v kota_01:28
kota_hello01:28
kota_I'm back from vacation.01:28
hokota_: welcome back! did you spend good vacation?01:29
*** gyee has quit IRC01:29
timburkehi kota_! i hope vacation was nice :)01:29
kota_ho: definitely, it was nice.01:30
hokota_: great!01:30
kota_timburke: hi, nice work about swift3, I am going to start a tons of reviewer work from today :/01:30
timburkekota_: heh, no rush. actually, i think that queue isn't even very long01:31
openstackgerritMatthew Oliver proposed openstack/swift: Follow up patch to fix a multiline import NITPIC  https://review.openstack.org/21647901:32
mattoliveraukota_: morning!01:32
kota_timburke: ok, thanks01:33
kota_mattoliverau: morning!01:33
kota_mattoliverau: could you review my spec about global ec cluster? (about patch 209447)01:35
patchbotkota_: https://review.openstack.org/#/c/209447/01:35
*** asd112z has joined #openstack-swift01:35
mattoliveraukota_: hai! But it'll have to be after lunch cause I'm about to go out to a lunch meeting01:36
kota_mattoliverau: it's ok, not so urgent to me, thanks!01:37
openstackgerritMerged openstack/python-swiftclient: flake8 ignores same hacks as swift  https://review.openstack.org/20290901:38
csmartmattoliverau: stop spying on me01:40
* csmart slaps tonyb01:40
mattoliveraucsmart: mwahahaha, never!01:40
csmart:-)01:40
tonybWell that escaleted quickly01:41
mattoliveraulol01:41
csmart:-D01:43
mattoliverausigh, spent ages trying to figure out why I couldn't start kota_'s change so I could come back later.. to realise I couldn't see it cause I wasn't logged in via the web-UI (I use gertty alot).. I think I need more caffine :P01:51
mattoliveraus/start/star/01:52
zaitcevYou totally do, it appears.01:53
*** miyahara has joined #openstack-swift01:53
kota_miyahara: welocome to IRC!01:54
miyaharakota_: thank you.01:55
openstackgerritMerged openstack/python-swiftclient: Add minimal working service token support.  https://review.openstack.org/18264002:02
*** haomaiwang has joined #openstack-swift02:05
*** kota_ has quit IRC02:07
homiyahara: welcome!02:19
miyaharaho: thank you!02:20
*** _hrou_ has joined #openstack-swift02:20
homiyahara: I would like to discuss about your patch.02:20
miyaharaOK.02:21
homiyahara: my concern now is raise at L181 in swift-dispersion-report. is it necessary?02:22
homiyahara: i wrote it in the previous comment.02:22
*** hrou has quit IRC02:23
*** nexusz99 has joined #openstack-swift02:23
homiyahara: this is a command so i prefer to not print traceback in this case.02:24
*** flwang has quit IRC02:26
homiyahara: and i prefer to replace "raise at L185 in internal_client.py" to ClientException. The exception is already handled so it's better to wrap here.02:27
homiyahara: here is my memo (use for the review) : http://paste.openstack.org/show/426557/02:30
homiyahara: what do you think?02:30
miyaharaho: Do you mean that "if err has http_status, it is not necessary to raise err" ?02:31
*** jrichli has joined #openstack-swift02:34
*** bkopilov has quit IRC02:34
miyaharaIf so, I agree to your proposal "raise at L181 in swift-dispersion-report is unnecessary."02:36
homiyahara: yeah, i'm not sure why exceptions raise there.02:37
homiyahara: if the code got 403, a traceback will be outputted.02:38
miyaharaho: I see.02:41
homiyahara: if you fix my second comment (replace to clientexception), it's better to split except block for ClientEx and Ex02:56
homiyahara:  i will wirte above comments on gerrit.02:56
*** kota_ has joined #openstack-swift02:58
*** ChanServ sets mode: +v kota_02:58
*** haomaiwang has quit IRC03:01
miyaharaho: Now, I discussed this topic with kota_ , and I got new conclusion.03:01
*** haomaiwang has joined #openstack-swift03:02
miyaharaho: Can you discuss this topic 1 hour later?03:05
homiyahara: great!03:05
homiyahara: i think it's not necessary. you discussed my concerns with kota_, i just wanted to tell them to reduce our mis-understanding in gerrit because of our english. :-)03:10
homiyahara: i'm looking foward to reading your next patch :-)03:11
*** sanchitmalhotra has joined #openstack-swift03:13
*** links has joined #openstack-swift03:24
*** ppai has joined #openstack-swift03:26
*** asd112z has quit IRC03:31
*** sanchitmalhotra1 has joined #openstack-swift03:37
*** sanchitmalhotra has quit IRC03:39
miyaharaho: OK. I make new patch. Thank you.03:45
notmynamegood evening03:47
kota_notmyname: good evening03:47
miyaharanotmyname: good evening03:47
*** ppai has quit IRC03:48
homiyahara: you are welcome :-) btw should I put "-san" after your irc name? your irc name is same as family name so i'm not sure i write your irc name without "-san"03:48
honotmyname: good evening!03:49
miyaharaho: I don't care. Please call me "miyahara".03:56
homiyahara: sure!03:57
zaitcevDo you guys remember the term for addressing without honorifics? I think it sounded like "yobishite", but I can't find it.03:58
kota_zaitcev: maybe you want "yobisute"03:59
hozaitcev: yobisute is right word03:59
kota_lol04:00
hoyou won :-)04:00
zaitcevkota_, ho: thanks a lot, that was what I was looking for.04:00
*** haomaiwang has quit IRC04:01
*** 17WAAILMU has joined #openstack-swift04:01
*** ppai has joined #openstack-swift04:02
hozaitcev: you are welcome. you study japanese hard :P04:06
zaitcevho: Sorry, not really hard.04:06
zaitcevho: But hopefuly it comes handy in October. I got a room in Ueno, so I'm going to commute.04:07
hozaitcev: study japanese from tv (animation) is a good idea. oh, you can have experience for "rush hour in tokyo"04:09
mattoliveraukota_: I had a look at your spec, looks great, there are spelling errors etc, which I assume others will start -104:12
mattoliveraukota_: -ing so had a first draft at correcting http://paste.openstack.org/show/426660/04:12
kota_mattoliverau: Thanks!04:13
mattoliverauI'm happy with how it is now (minus some spelling corrections) but ^^ had a go at rewording just in case it becomes stuck in review hell.. happy to push it up if your happy for me to.04:13
mattoliveraukota_: ^04:14
notmynamemy plan for tokyo is to not let kota_ and ho out of my sight04:14
mattoliveraunotmyname: good plan ;)04:14
jrichli+104:14
kota_lol04:16
housuful info. i don't live in tokyo, i'm afraid to get there (too big city for me) :-)04:17
notmynamenew plan: ho is staying in my hotel the week of the summit ;-)04:17
kota_i guess dmorita and miyahara could be volunteers, too.04:17
notmyname:-)04:17
holol04:17
zaitcevCome on. Spread your wings in The International Edo.04:18
notmynamein seriousness, though, I will be grateful for any help in Japan you can provide while we're there :-)04:18
mattoliveraukota_: I like the way you think ;)04:18
*** bkopilov has joined #openstack-swift04:18
hoi have to study about tokyo04:19
zaitcevBesides, the Summit is in Shinagawa, which is a kind of a foreigner's corral. It's right next door to Roppongi, where all the embassies are.04:19
mattoliveraukota_: maybe ntt will need to hold  a swift party :)04:19
openstackgerritMerged openstack/swift: Quorum on durable response is too low  https://review.openstack.org/21382204:20
notmynamemattoliverau: we (swiftstack) will be doing a low-key swift one like we did in vancouver. or that's the plan so far :-)04:20
kota_mattoliverau: I hope it, too and now planning but not yet determined I can do so.04:20
notmynamebut NTT should do one too!04:20
kota_yup04:21
mattoliveraunotmyname: I want to go to many swift parties!04:21
zaitcevMaybe I can still come...04:21
mattoliverauzaitcev: maybe..04:21
mattoliverau:P04:21
jrichlime too ... more swift parties04:22
kota_notmyname: have you plan the date already?04:22
mattoliverauOkonomiyaki party, a suhi train party04:22
kota_I dont't want the ones hold in the same day.04:22
notmynamekota_: that would be bad!04:23
notmynamewe haven't set any day yet. have you?04:23
kota_notmyname: not yet.04:23
mattoliverauWell make sure your both in communication when you do!04:23
notmynameactually I'm a little confused on how it's working this time. seems that everything starts on tuesday morning? and the confenrence and summit 100% overlap for tuesday through friday04:24
kota_notmyname: I'm not sure when almost of attendees would land tokyo...04:24
notmynamekota_: yeah, that's another issue04:24
redboI'm hoping it turns out everyone actually speaks english but they're angry about it, like in Paris.04:25
kota_notmyname: yes, all of summit starts from tuesday.04:25
notmynameI am getting in early, but leaving on friday night. reasonable days seem like they'd be monday-thursday nights04:25
jrichliredbo: +104:25
notmynameredbo: except the taxi drivers. then they're just angry with you about it04:25
mattoliverauyeah good point, I'd assume Monday for me then as I don't need a jetlag day.. but maybe I could come on the weekend.. I'll have to discuss it with the bosses04:25
zaitcevnotmyname: It was a surprised for me too. I arrive on Saturday, because I did not even think to examine the schedule.04:26
notmynamezaitcev: I know, right?04:26
notmynameyeah, I'm getting in saturday night too (at about 10:30pm local time)04:26
zaitcevWell, then.... Sunday night is Akiba night then.04:27
kota_zaitcev: lol04:27
mattoliverauI'm looking forward to it, maybe I'll need to try and get in on the weekend then (tho can't promise anything) :)04:28
kota_nights through monday-thursday seems better. ok, I am going to plan around there (but can't promise for now)04:30
kota_thanks04:31
notmynamekota_: ok, great. If you come up with something, let me know and I'll work around it04:31
kota_notmyname: sure04:31
*** sanchitmalhotra has joined #openstack-swift04:35
*** trifon has quit IRC04:35
*** sanchitmalhotra1 has quit IRC04:37
*** abhirc has quit IRC04:37
*** abhirc has joined #openstack-swift04:38
*** SkyRocknRoll has joined #openstack-swift04:42
*** abhirc has quit IRC04:42
*** abhirc has joined #openstack-swift04:47
*** abhirc has quit IRC04:48
*** abhirc has joined #openstack-swift04:48
*** jrichli has quit IRC04:54
*** 17WAAILMU has quit IRC05:01
*** haomaiwang has joined #openstack-swift05:02
*** abhirc has quit IRC05:04
*** silor has joined #openstack-swift05:16
*** trifon has joined #openstack-swift05:18
*** silor has quit IRC05:20
*** silor has joined #openstack-swift05:25
*** asd112z has joined #openstack-swift05:32
*** kota_ has quit IRC05:47
openstackgerritMerged openstack/swift: Fix typo of a comment in replicator  https://review.openstack.org/21645305:49
*** asd112z has quit IRC05:51
*** links has quit IRC05:57
*** links has joined #openstack-swift06:00
*** haomaiwang has quit IRC06:01
*** haomaiwang has joined #openstack-swift06:01
*** zaitcev has quit IRC06:07
*** baojg has joined #openstack-swift06:10
*** serverascode has quit IRC06:12
*** mahatic has joined #openstack-swift06:13
openstackgerritSamuel Merritt proposed openstack/swift: Allow pep8 of a single file  https://review.openstack.org/21654506:16
*** baojg has quit IRC06:16
*** serverascode has joined #openstack-swift06:17
*** baojg has joined #openstack-swift06:19
*** _hrou_ has quit IRC06:34
nakagawamsaHi all, could you tell me about version confliction of requrement packages?06:41
nakagawamsaI think, Ubuntu 14.04 cannot be satisfied with requirement version of six and eventlet,because 14.04's repository doesn't have required version of those packages.06:41
nakagawamsaSo we need to add latest repository if we deploy swift in Ubuntu 14.04.06:41
nakagawamsaBut SAIO document doesn't reffer to it, so I think we should modify SAIO document.06:41
nakagawamsaCould you tell me that my worrying is incorrect? or this is already discussed matter?06:41
*** baojg has quit IRC06:42
*** baojg has joined #openstack-swift06:43
lifelessnakagawamsa: how are you installing ?06:47
*** mahatic has quit IRC06:48
*** mahatic has joined #openstack-swift06:48
nakagawamsalifeless: following SAIO document, <http://docs.openstack.org/developer/swift/development_saio.html>06:49
lifelesshuh those docs are old06:55
lifelesswe recommend pip install -e .06:55
lifelessnot setup.py develop06:55
lifelesspip will install what you need06:55
lifelessanyhow, what error are you hving?06:55
nakagawamsaIn my understanding, pip cannot update packages which installed by OS (like apt-get)06:58
lifelessI want to know06:58
lifelessare you theorising about a problem06:58
lifelessor have you experienced a problem ?06:58
nakagawamsatheorising06:59
nakagawamsa"pip -r requirement.txt" can not update six/eventlet packages with error07:00
*** haomaiwang has quit IRC07:01
*** haomaiwang has joined #openstack-swift07:02
*** rledisez has joined #openstack-swift07:02
openstackgerritOpenStack Proposal Bot proposed openstack/python-swiftclient: Updated from global requirements  https://review.openstack.org/8925007:11
openstackgerritOpenStack Proposal Bot proposed openstack/swift: Updated from global requirements  https://review.openstack.org/8873607:12
lifelessnakagawamsa: with appropriate privileges it can07:13
nakagawamsapip install is run with sudo.07:18
nakagawamsaand pip community said OS installed packages will not updated by pip07:19
nakagawamsa<https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771794>07:22
openstackDebian bug 771794 in python-pip "pip silently removes/updates system provided python packages" [Serious,Fixed]07:22
nakagawamsaif my understanding is mistaken, please tell me. (my english skill is poor)07:24
lifelessnakagawamsa: I think you should test this07:26
lifelessrather than theorising07:26
lifelessDebian have patched pip, so its not necessarily going to do what pip would normally07:26
*** mahatic has quit IRC07:30
*** silor has quit IRC07:34
nakagawamsalifeless: ok, thanks a lot. I retry check now.07:34
nakagawamsaI think I need to retry two process.07:35
nakagawamsa1.original SAIO document process07:35
nakagawamsa2.using pip install -e process which you gave me07:35
nakagawamsaCould you give me document which uses "pip install -e" ?07:35
lifelesssorry, not really - its written down in mailing list posts and so on, but not yet in the swift docs07:36
nakagawamsaok, i try to seach it.07:38
nakagawamsaAnd if i find it and needed, I would like to try to modify SAIO document, ok?07:38
lifelesssure07:45
*** akle has joined #openstack-swift07:52
*** jordanP has joined #openstack-swift07:52
*** bkopilov has quit IRC07:54
*** mahatic has joined #openstack-swift07:55
*** haomaiwang has quit IRC08:01
*** haomaiwang has joined #openstack-swift08:01
*** asd112z has joined #openstack-swift08:03
*** asd112z has quit IRC08:08
openstackgerritMerged openstack/swift: New troubleshooting case in documentation.  https://review.openstack.org/21574408:10
openstackgerritMerged openstack/swift: Minor cleanup handoff mode warnings  https://review.openstack.org/21585808:11
*** jistr has joined #openstack-swift08:12
*** acoles_ is now known as acoles08:23
openstackgerritMerged openstack/swift: Use correct Storage-Policy header for REPLICATE requests  https://review.openstack.org/21585708:31
*** joeljwright has joined #openstack-swift08:31
*** ChanServ sets mode: +v joeljwright08:31
*** haomaiwang has quit IRC08:41
*** haomaiwang has joined #openstack-swift08:42
*** akle has quit IRC08:46
openstackgerritAlistair Coles proposed openstack/python-swiftclient: Stop Connection class modifying os_options parameter  https://review.openstack.org/21624008:47
*** ho has quit IRC08:54
*** akle has joined #openstack-swift09:05
*** haomaiwang has quit IRC09:09
*** haomaiwang has joined #openstack-swift09:10
*** marzif has joined #openstack-swift09:21
*** marzif has quit IRC09:31
*** marzif has joined #openstack-swift09:31
*** sanchitmalhotra has quit IRC09:31
*** joeljwright1 has joined #openstack-swift09:34
*** jordanP has quit IRC09:36
*** joeljwright has quit IRC09:37
*** joeljwright has joined #openstack-swift09:41
*** ChanServ sets mode: +v joeljwright09:41
*** joeljwright1 has quit IRC09:43
*** joeljwright has quit IRC09:46
*** joeljwright has joined #openstack-swift09:50
*** ChanServ sets mode: +v joeljwright09:50
*** aix has joined #openstack-swift09:50
*** aix has quit IRC09:52
*** aix has joined #openstack-swift09:53
openstackgerritKazuhiro MIYAHARA proposed openstack/swift: Fix dispersion-reports error message  https://review.openstack.org/21369709:58
*** nexusz99 has quit IRC10:05
openstackgerritAlistair Coles proposed openstack/swift: Fix swob.Range docstring  https://review.openstack.org/21664910:09
*** haomaiwang has quit IRC10:09
*** haomaiwa_ has joined #openstack-swift10:10
*** baojg has quit IRC10:11
openstackgerritMerged openstack/swift: Follow up patch to fix a multiline import NITPIC  https://review.openstack.org/21647910:28
*** eandersson has joined #openstack-swift10:29
*** miyahara has quit IRC10:37
*** SkyRocknRoll has quit IRC10:39
*** bwall has quit IRC10:49
*** dmorita has quit IRC10:50
*** SkyRocknRoll has joined #openstack-swift10:57
*** lpabon has joined #openstack-swift11:01
*** asd112z has joined #openstack-swift11:03
openstackgerritMerged openstack/swift: Fix use of delimiter in account listings  https://review.openstack.org/21642711:04
openstackgerritMerged openstack/swift: pep8: Fix usage of the l10n _('...') function  https://review.openstack.org/21349411:04
*** asd112z has quit IRC11:08
*** haomaiwa_ has quit IRC11:09
*** haomaiwa_ has joined #openstack-swift11:10
*** joeljwright has quit IRC11:23
onovynotmyname, clayg, mattoliverau: hi, do you have time for small review pls? https://review.openstack.org/#/c/210736/11:25
*** nakagawamsa has quit IRC11:44
*** kairo_ has quit IRC11:48
*** lpabon has quit IRC11:50
*** marcusvrn_ has joined #openstack-swift11:53
*** km has quit IRC12:07
*** haomaiwa_ has quit IRC12:09
*** haomaiwang has joined #openstack-swift12:10
*** petertr7_away is now known as petertr712:11
*** annegentle has joined #openstack-swift12:28
*** bill_az has joined #openstack-swift12:31
*** kei_yama has quit IRC12:31
*** lpabon has joined #openstack-swift12:31
*** jordanP has joined #openstack-swift12:32
*** petertr7 is now known as petertr7_away12:33
*** ppai has quit IRC12:34
*** petertr7_away is now known as petertr712:35
*** SkyRocknRoll has quit IRC12:42
*** gustavo has joined #openstack-swift12:45
*** annegentle has quit IRC12:50
gustavoHi guys, I'm running a production Swift cluster setup with authentication using swauth.  I'm not using any other openstack component. Swift version: Folsom (1.7.4). I would like to upgrade to Swift 2.2.0. Should I migrate to keystone ?12:51
*** dustins has joined #openstack-swift12:52
*** joeljwright has joined #openstack-swift12:56
*** ChanServ sets mode: +v joeljwright12:56
openstackgerritOpenStack Proposal Bot proposed openstack/swift: Updated from global requirements  https://review.openstack.org/8873612:56
*** chlong has joined #openstack-swift12:56
onovygustavo, not needed13:01
onovywe have 2.3.0 swift cluster with swauth in production13:01
onovyit always depends on size of cluster. for many users and many auth request it's better to have Keystone13:02
onovyfor other usecases is swauth fine13:02
openstackgerritMerged openstack/swift: Fix 500 for bogus Range request to 0-byte object.  https://review.openstack.org/21531713:07
gustavoonovy, Thanks for the reply! I'm using php-cloudfiles to access to swift cluster but this library is deprecated and not available any more. I read that php-opencloud is the replacement, but it library only works with keystone isn't it?13:08
onovynot using php-* at all, sry13:08
onovybut i think it should be compatible with any auth backend13:09
onovymust go, bye13:09
gustavoonovy, thanks very much !13:09
*** haomaiwang has quit IRC13:09
*** haomaiwang has joined #openstack-swift13:10
*** annegentle has joined #openstack-swift13:11
*** annegentle has quit IRC13:12
*** annegentle has joined #openstack-swift13:14
*** breitz has joined #openstack-swift13:19
*** pgbridge has joined #openstack-swift13:20
*** changbl has quit IRC13:21
*** links has quit IRC13:23
openstackgerritOpenStack Proposal Bot proposed openstack/swift: Updated from global requirements  https://review.openstack.org/8873613:24
*** bill_az has quit IRC13:26
*** hrou has joined #openstack-swift13:29
*** breitz has quit IRC13:34
*** lpabon has quit IRC13:38
*** lpabon has joined #openstack-swift13:42
*** bapalm has quit IRC13:44
*** bapalm_ is now known as bapalm13:51
*** breitz has joined #openstack-swift13:52
*** thumpba has joined #openstack-swift13:53
*** trifon has quit IRC13:56
openstackgerritAlistair Coles proposed openstack/swift: Fix EC GET backend stream iteration state  https://review.openstack.org/19904313:58
acoleskota clayg ^^ i just fixed some minor stuff on this patch before +2'ing13:58
*** petertr7 is now known as petertr7_away14:00
*** haomaiwang has quit IRC14:09
*** chsc has joined #openstack-swift14:10
*** haomaiwang has joined #openstack-swift14:10
*** petertr7_away is now known as petertr714:13
*** jlhinson has joined #openstack-swift14:21
*** asd112z has joined #openstack-swift14:32
*** asd112z has quit IRC14:33
*** asd112z has joined #openstack-swift14:33
*** asd112z has quit IRC14:34
*** asd112z has joined #openstack-swift14:34
*** petertr7 is now known as petertr7_away14:41
*** annegentle has quit IRC14:41
*** annegentle has joined #openstack-swift14:41
*** petertr7_away is now known as petertr714:42
*** links has joined #openstack-swift14:43
*** ccavanna has quit IRC14:46
*** ccavanna has joined #openstack-swift14:46
mahaticacoles: looks like I need this patch 216240 merged to push mine14:47
patchbotmahatic: https://review.openstack.org/#/c/216240/14:47
acolesmahatic: do you depend on that?14:47
mahaticacoles: I have changes on the same file (client.py)14:48
acolespython14:49
acolesoops!14:49
acolesmahatic: do they conflict? if so you couldl rebase your change onto the other patch14:49
mahaticacoles: actually I don't think they do. But then if that gets merged before, I will not have the latest code on my code14:51
mahaticlatest code on the pushed patch*14:52
*** jrichli has joined #openstack-swift14:53
acolesmahatic: its fine, push your patch, gerrit takes care of rebasing on latest master as patches get merged, unless a rebase fails, in which case it will let you know.14:54
acolesmahatic: you only need to rebase on other patch if you need its change14:54
mahaticacoles: oh cool. thanks for letting me know, will do14:55
*** minwoob has joined #openstack-swift14:59
*** redbo has quit IRC15:06
*** kevinc_ has joined #openstack-swift15:07
*** dustins has quit IRC15:08
*** redbo has joined #openstack-swift15:09
*** ChanServ sets mode: +v redbo15:09
*** haomaiwang has quit IRC15:09
*** haomaiwang has joined #openstack-swift15:10
*** lpabon has quit IRC15:13
*** lpabon has joined #openstack-swift15:17
*** thurloat is now known as thurloat_isgone15:23
*** nadeem has joined #openstack-swift15:24
*** tsg has joined #openstack-swift15:25
*** ccavanna has quit IRC15:26
*** joeljwright has quit IRC15:27
*** tsg_ has joined #openstack-swift15:35
*** tsg has quit IRC15:35
*** tsg_ has quit IRC15:36
*** links has quit IRC15:44
*** lpabon has quit IRC15:44
*** ccavanna has joined #openstack-swift15:52
*** changbl has joined #openstack-swift15:55
*** thurloat_isgone is now known as thurloat15:57
*** petertr7 is now known as petertr7_away15:58
*** jordanP has quit IRC16:00
*** aix has quit IRC16:08
*** haomaiwang has quit IRC16:09
*** haomaiwa_ has joined #openstack-swift16:10
*** thurloat is now known as thurloat_isgone16:12
*** marzif has quit IRC16:12
*** lpabon has joined #openstack-swift16:16
*** jistr has quit IRC16:17
*** lpabon has quit IRC16:25
*** marzif has joined #openstack-swift16:28
*** vinsh_ is now known as Vinsh16:31
*** bkopilov has joined #openstack-swift16:32
*** rledisez has quit IRC16:36
*** bwall has joined #openstack-swift16:39
*** andrew_____ has joined #openstack-swift16:40
*** andrew_____ has quit IRC16:40
*** trifon has joined #openstack-swift16:41
*** gyee has joined #openstack-swift16:43
*** takotuesday has joined #openstack-swift16:45
takotuesdayHey everyone, I need some help in figuring out the best way to verify if a file exists within my swift container. I am trying to do this in python. I've been looking at the python swiftclient but the best Ive been able to come up with in that API is get_object16:46
ctennisI'm not particularly sure what you're asking takotuesday, if you're trying to verify if an object exists you can just do an HTTP head to the object16:48
*** lpabon has joined #openstack-swift16:50
*** lpabon has quit IRC16:55
pelusetorgomatic, clayg - chatted a bit about this one at the hackathon... error handling change for Ec patch 21133817:06
patchbotpeluse: https://review.openstack.org/#/c/211338/17:06
openstackgerritTushar Gohad proposed openstack/swift: Restrict PyECLib version to 1.0.7  https://review.openstack.org/21405417:07
openstackgerritTim Burke proposed openstack/python-swiftclient: Accept gzip-encoded API responses  https://review.openstack.org/18495617:08
*** silor has joined #openstack-swift17:09
*** silor has quit IRC17:09
*** haomaiwa_ has quit IRC17:09
*** haomaiwang has joined #openstack-swift17:10
*** silor has joined #openstack-swift17:11
*** rjaiswal has joined #openstack-swift17:14
rjaiswalnotmyname: Hi thr, a question regarding swift proxy server17:18
*** andrew_____ has joined #openstack-swift17:19
andrew_____hi, are there a grok pattern for swift logs publicly available (for logstash)?17:20
*** petertr7_away is now known as petertr717:20
*** esker has joined #openstack-swift17:24
*** themadcanudist has joined #openstack-swift17:29
themadcanudisthey guys, can you safely "sqlite X vacuum" a container db (and all its replicas)?17:30
ctennisandrew_____: perhaps this? http://docs.openstack.org/developer/swift/_sources/logs.txt17:32
ctennishttps://github.com/openstack/swift/blob/master/doc/source/logs.rst for a slightly nicer version17:32
*** lpabon has joined #openstack-swift17:35
*** esker has quit IRC17:37
rjaiswalunderstand that the proxy server might issue HEAD after a specific timeout, can this be controlled via configuration?17:39
*** mahatic has quit IRC17:39
rjaiswalanyone ^^^^17:41
*** dustins has joined #openstack-swift17:43
torgomaticrjaiswal: the proxy doesn't spontaneously make requests; it's all done in response to client requests17:45
*** themadcanudist has left #openstack-swift17:46
rjaiswaltorgomatic: yes, so when a client issues a swift upload command, the proxy might issue a HEAD if the previous command for the same container was before some time limit?17:48
torgomaticrjaiswal: yes, the proxy may HEAD the container to confirm that it exists. same for the account.17:49
torgomaticit is configurable17:49
*** dustins has quit IRC17:50
rjaiswalok, so i was told that for all such HEAD requests that originate from middleware, there will always be a swift.source in the env17:50
rjaiswalhowever, when i tested in devstack with a swift upload <con-name> <obj> command, i saw HEAD requests with no swift.source17:51
torgomaticprovided that the middleware sets swift.source, this is true; I believe all the ones in the Swift source tree do, but third-party middlewares don't automatically get 8t17:51
torgomaticrjaiswal: well, the proxy server isn't middleware17:51
rjaiswalyeah, i meant the proxy server itself17:51
claygmorning17:52
rjaiswalis there a scenario when the swift upload command could result in a HEAd without a swift.source?17:52
peluseclayg, morning17:52
acolesclayg: i left some comments on patch 215360 plus a diff with some ideas17:52
patchbotacoles: https://review.openstack.org/#/c/215360/17:52
peluseclayg, just completed a cool test....17:52
torgomaticright... so you've asserted (a) requests from middleware have swift.source in the environment, (b) the proxy can make account/container HEAD requests, and (c) you see requests logged with no swift.soruce17:52
torgomatic*source17:53
torgomaticI see no inconsistencies here17:53
peluse(1) write (2) take a pile of drives offline (3) stop ec recon (4) overwrite (5) read and confirm no client errors and 2 etag buckets used on ocacssion (6) run ec recon (7) re-read and confirm all single etag bucket17:54
rjaiswaltorgomatic: so when i do swift upload, i do see one HEAD request with swift.source set to RL, followed by a PUT, but then i see another HEAD without a swift.source set17:54
rjaiswaltorgomatic: i was thinking that the HEADs due to an upload would have the swift.source set17:55
claygacoles: I had a diff that turned the node_iter into a instance of a NodeIter class that had a nodes_left property17:56
torgomaticrjaiswal: only if they're done by middleware; if the proxy server (swift.proxy.server.Application) does it, then there's no swift.source17:56
acolesclayg: is that up on gerrit?17:56
claygacoles: in the diff you have doesn't that go back to only spawning one GET waiting on, then seeing we need another, spawning it, waiting on it, seeing we need another....17:57
rjaiswaltorgomatic: ok17:57
claygacoles: here was NodeIter -> https://gist.github.com/clayg/e4c54ff9ab1331cc67d317:57
claygacoles: the 416's are tricky, if you get enough "bad gets" the current behavior is to return the 416 (enough in this context is ec_ndata for some reason)17:58
rjaiswaltorgomatic: which is that configurable option in proxy server to control the timeout?17:58
torgomaticrjaiswal: it's something like recheck_account and recheck_container, I think17:59
rjaiswalin the proxy-server.conf?17:59
torgomaticyes17:59
*** mahatic has joined #openstack-swift17:59
rjaiswalok, checking18:00
claygpeluse: awesome!  you put your etag_bucket patch on there to get the no client error behavior!?18:00
rjaiswaltorgomatic: maybe this?https://github.com/openstack/swift/blob/master/etc/proxy-server.conf-sample#L9118:01
peluseclayg, correct18:01
torgomaticrjaiswal: yeah, that looks rihg18:01
torgomatic*right18:01
rjaiswaltorgomatic: thanks18:01
peluseclayg, pretty cool to see it work on a real cluster.  if you have an updated version from your end this week we can run it as well18:01
torgomaticnp18:01
rjaiswaltorgomatic: one last q, is there anyway to find out if a request originated in the proxy and not middleware?18:03
rjaiswallike those HEADs that the proxy would do the check for account/container existence18:04
acolesclayg: i don't think so, *every* time a get completes it evaluates if another may be needed. So the number of gets "in-flight" should always be enough to satisfy ec_ndata if they all land in best_etag bucket. As soon as a get lands in a different etag bucket or is bad, another gets spawned.18:04
* acoles intended that at least :)18:04
torgomaticrjaiswal: absence of swift.source? I think that's what you determined earlier.18:04
acolesclayg: nodes_left will be useful!18:05
*** arringtp_ has quit IRC18:05
rjaiswaltorgomatic: but thats also for requests that originate from clients, right18:05
torgomaticrjaiswal: yes, that's true18:05
torgomaticrjaiswal: correlate by txid; if you see multiple requests with the same txid, you can figure out what happened when and why18:06
acolespeluse: nice!18:06
rjaiswaltorgomatic: i am trying to fix a bug in ceilometermilldeware.swift, its a middleware that emits events for swift api requests, the problem is that it ignores the swift.source, it should only emit event for requetss that originate from client18:07
claygacoles: ah, hrm.. ok thanks for that pointer - i was obviously misreading it18:07
rjaiswalso i am trying to figure out a way to distinguish client requests from ones that originate in Swift, swift.source can tell us those that originate in middleware18:07
torgomaticrjaiswal: a middleware won't *see* HTTP requests made by the proxy, so don't worry about those18:07
claygacoles: still not quite sure about 416's - if we don't do *something* with len(bad_gets) I think we'd have to exahust the node_iter :\18:08
torgomaticit'll only see requests made by clients or by middlewares to its left in the pipeline18:08
rjaiswaltorgomatic: yes, that makes sense, but i saw 2 HEADS, with the latter one without a swift.source, so confused18:09
*** haomaiwang has quit IRC18:09
torgomaticrjaiswal: try requests with curl; swiftclient might be making more than one request per invocation18:09
acolesclayg: yeah, agree, need to keep track of bad_gets to give up early rather than exhaust the iter pointlessly.18:10
*** haomaiwang has joined #openstack-swift18:10
claygacoles: so what's the right number to return 416's at?18:10
claygtorgomatic: ^18:10
rjaiswaltorgomatic, ok, so you suspecting the second HEAD originated from client18:10
clayghow many 416 response needed on EC GET to return 416?18:10
*** marzif has quit IRC18:11
claygtorgomatic: in the "ideal"18:11
claygacoles: how about parity + 1 !?18:11
rjaiswaltorgomatic: got it, so relying on swift.source to filter out requests that have a value for it should be a good enuf18:11
acolesclayg: hmmm18:11
torgomaticclayg: uh... I dunno18:12
torgomaticrjaiswal: theoretically, yes18:12
claygacoles: bah - with handoffs you never quite know!  there could be enough 206's out there somewhere - if you just keep looking!18:12
claygyou could hit 5 416's and still find 10 206's on the rest of the primaries and one handoff18:12
torgomaticclayg: one? Then you know that there exists (or existed) a version of the object for which the client's range is not satisfiable18:12
torgomaticso blah blah eventual consistency, it's something clients should expect18:13
rjaiswaltorgomatic: so, if swiftclient makes more than 1 request for a upload, is it incorrect, in theory, by swiftclient18:13
acolesclayg: we have 2*(parity+data) nodes so don't we need 4xx from 2*parity + data before giving up?18:13
acoles4xx from 2*parity + data + 1 I mean18:13
acolesclayg: or 1 as torgomatic says ?!? :P18:14
claygacoles: well that's the weird thing 4XX will just be skipped in the node iter - it's only 416 that leeks into the ECObjController18:14
*** lpabon has quit IRC18:14
torgomaticrjaiswal: that's not what I'm saying at all. I'm saying that swiftclient might make more than one request for an upload, so to test the hypothesis that swift.source is sufficient to distinguish client requests from non-client requests, you should use curl so you know how many client requests were made18:14
acolesclayg: aaaahhh18:15
claygwell call them "bad" responses but it's really *just* 41618:15
*** joeljwright has joined #openstack-swift18:15
*** ChanServ sets mode: +v joeljwright18:15
claygor something like that - the ResummingGetter has an "is_success" qualifier that's like 2XX or 416 (IIRC)18:15
acolesclayg: got it18:15
rjaiswaltorgomatic: got it18:16
claygacoles: "is_good_source"18:16
*** lpabon has joined #openstack-swift18:16
claygrjaiswal: got it18:16
clayg^ torgomatic you do acoles now!18:16
acolesclayg: i gotta run. will think on 416s some more and take a look at your NodeIter class.18:19
claygacoles: ok bye bye!18:19
*** tab has joined #openstack-swift18:20
*** tab is now known as Guest5594618:20
*** Guest55946 has quit IRC18:20
*** tab___ has joined #openstack-swift18:21
*** acoles is now known as acoles_18:22
claygmattoliverau: doesn't concurrent GET's expose GreenAsyncPile._inflight or something?18:27
claygmattoliverau: heck yeah it do!  @proerpty inflight!18:28
*** jrichli has quit IRC18:31
*** dustins has joined #openstack-swift18:33
rjaiswaltorgomatic: or i could use the --debug option when i use swiftclient to post or upload and i could possibly see the different curl requests being made18:34
*** haomaiwang has quit IRC18:42
*** flwang has joined #openstack-swift18:44
*** haomaiwang has joined #openstack-swift18:45
claygmattoliverau: _infligth is interesting - it turned out it wasn't really what I was looking for.18:47
claygI wanted to know how many times do I have to call next to get all of the responses I've spawned - which is different from _inflight (since _inflight is decremented when the response finishes, not when I consume it)18:48
claygso _inflight could be zero, but I have 3 "pending" responses still "outstanding" (they're done, I just haven't eaten 'em yet)18:48
*** changbl has quit IRC18:49
*** marzif has joined #openstack-swift18:52
claygi think _inflight works for concurrent GET's tho because you just need the first one that finished - if it finished and inflight got decremented the next wait will break18:53
*** changbl has joined #openstack-swift18:59
*** takotuesday has left #openstack-swift19:00
*** dustins has quit IRC19:04
claygacoles_: I know you're off - but man - I am *digging* on your diff - I added in the node_iter.nodes_left and it looks good19:09
*** haomaiwang has quit IRC19:09
claygacoles_: I don't know how I missed it before the spawning the of the extra requests as soon as your pending requests drop below the amount that could come to reach ec_ndata - so good19:09
claygacoles_: THANKS!19:09
*** haomaiwa_ has joined #openstack-swift19:10
*** jlk has joined #openstack-swift19:15
jlkHas anybody been able to run swift-proxy in such a way that you can pdb walk through the keystone middleware auth routine? I've got a bug somewhere in there where it's trying ot read a cert file I'm passing along, and it's failing hard.19:15
jlkI can't get pdb to attach, and epdb isn't exactly being helpful either.19:16
jlk(or I'm not using it right)19:16
*** lpabon has quit IRC19:17
*** andrew_____ has quit IRC19:22
*** lpabon has joined #openstack-swift19:24
*** mfalatic has quit IRC19:33
*** gyee has quit IRC19:42
*** marzif_ has joined #openstack-swift19:44
*** haomaiw__ has joined #openstack-swift19:46
*** haomaiwa_ has quit IRC19:46
*** marzif has quit IRC19:46
claygjlk: try to set workers = 0 (no fork) - then start it with swift-proxy-server /etc/swift/proxy-server.conf(.d) verbose19:49
claygjlk: i'm not 100% sure that will work - but it might getyou close19:49
claygtorgomatic: acoles_: so I'm not sure exactly the correct number of 416 - but it has to be <= ec_ndata19:53
claygtorgomatic: acoles_: if it's good enough for a 200 it's got to be good enough for a 416!19:53
peluseclayg, so FYI on this cluster with 3x repl we get a few .5 sec connection TO at the proxy under decent 64MB write load.  Same thing under EC we see quite a few more (but not a crazy amount).  Any thoughts on the origin of the .5 sec val and if it makes sense to consider adjusting the default?19:55
*** proteusguy has joined #openstack-swift19:55
*** dustins has joined #openstack-swift19:56
peluseclayg, (BTW if we turn it up the TO's go away, we only tried a gross value though, from .5 to 5)19:56
jlkclayg: thanks. I finally figured out the issue.19:58
claygpeluse: connection TO - that's weird20:02
* clayg thinks20:02
*** pberis has joined #openstack-swift20:02
claygpeluse: are you running replication_ip/replication_port?20:03
claygpeluse: it could be that ssync is chewing up some responsiveness in the obj server (compared to rsync repliation?)20:03
claygpeluse: you could throw this theory out by turning off ec_recon20:03
peluseclayg, yeah, we can try that20:04
claygpeluse: other possibility is cpu work blocking up the eventlet hub in the proxy20:04
peluseclayg, cpu is not heavily loaded during test20:05
claygpeluse: eventlet has the (weird?) behavior that if you set a timeout and then starve the hub - if the t/o is spent by the time you get back around to service the gt (even if it's ready!) it'll blow the timeout20:05
openstackgerritNadeem Syed proposed openstack/swift: go: Collecting runtime metrics  https://review.openstack.org/21685520:05
peluseclayg, maybe 40% on each proxy20:06
claygpeluse: well it may not be just the cpu *load* - eventlet might not be using the cpu entirely efficiently20:07
claygpeluse: even if pyeclib releases the GIL (i have no idea if it does) - since we're not doing the cpu in an os.thread (we don't want to because of context-switching overhead) the hub is "blocked" while doing the call to c library is doing math20:08
claygi wouldn't think normally it'd be noticeable (compared to a half-dozen python function calls) - unless maybe the segment_size is really high?20:08
claygpeluse: i'm just trying to think of ways that a proxy might timeout a backend connection - hub starvation comes to mind20:09
*** haomaiw__ has quit IRC20:09
claygone thing that can starve a hub is blocking call to c library - one thing that's different between replication is a blocking call to pyeclib - so it's an idea - need to think about how we could quantify or rule it out20:10
peluseclayg, yeah, BTW running the same test with kota's not_client_connection patch seems to result in fewer (so far none) timeouts under same conditions20:10
*** haomaiwang has joined #openstack-swift20:10
pelusemaybe the logging??20:10
*** petertr7 is now known as petertr7_away20:11
peluseclayg, yeah these are all PUTs so I could dummy that call up pretty easy20:11
claygmaybe - what's your syslog configuration?  I thought we foced it to use udp - so that should be ok - i think20:11
pelusedefaults20:11
*** flwang has quit IRC20:12
peluseI'm just sayin' - they're few and far between to begin with but so far still none w/kota's patch.  will let it run for ten min and see (that resulted in a dozen before)20:12
claygpeluse: maybe something in kota's patch is causing backend connections to get cleaned up better - so the object servers are more responsive - this is a good line of testing I think!20:12
*** flwang has joined #openstack-swift20:12
claygok, good observations - can you point me at *which* of kota's patches we're talking about?20:13
claygI remember he had a few that had to do with response codes, or content-length, client disconnect logging, ecappiter generator exit error - i can't remember the specifics20:13
pelusepatch 19904320:14
patchbotpeluse: https://review.openstack.org/#/c/199043/20:14
peluseahhh, just had a few.  so maybe helped a little but not gone (again we see with repl as well).  Will try w/EC recon turned off on all nodes20:16
claygoh - you see the connection timeouts on replication too?  yeah that could just be average run of the mill object-server disk wait starvation20:17
claygyeah i misread what you said earlier - thanks for clarifying20:18
peluseclayg, yeah could be.  we just noticed more with EC so wanted to mention it20:18
claygpeluse: turn up your object server works to like 4 x #of-disks20:18
claygpeluse: or go server per port!! whoooowhooooo20:19
wbhuberpeluse: how recent is proxy/controllers/obj.py on your cluster? the bug, 1488610, seems to indicate that the lines are a bit off from what i am having right now.20:19
claygwbhuber: he's master++20:20
peluseclayg, right now workers is 32 and disks is 10 (plus OS + SSD)20:20
*** joeljwright has quit IRC20:21
claygpeluse: well that's not bad then - 40 would be ok too tho!  or more maybe!?  burn those cpus to the floor!20:22
pelusewbhuber, yeah sorry I'm not sure which patch I was on but for that bug it doesn't matter.  you can repro on master by shutting down a storage node and then doing some IO20:22
peluseclayg, I'll try 40000 and see how that works :)20:22
peluseclayg, FYI shutting off EC recon doesn't affect things.  Will try > workers then just blow it off and move onto something more important...20:23
claygpeluse: k, I don't think kota's patch should really be having an impact - there's probably just some variance - do the same test 10 times w/ and w/o and it might turn out to be about the same regardless20:24
openstackgerritMerged openstack/swift: Add container sync probe test to SAIO default set  https://review.openstack.org/20580420:25
peluseclayg, agreed20:26
*** dustins has quit IRC20:27
*** pberis has quit IRC20:33
claygwbhuber: I'm not sure why common.utils.LogAdapter.exception is catching that exception log and translating it to a plain error log message (w/o traceback)20:33
wbhuber%s, not %(path)s?20:34
wbhuberjust spitting out an idea20:34
wbhuberdon't have the tools to test that one out20:34
*** lpabon has quit IRC20:34
torgomaticclayg: so for EC GET, you have <total> nodes, and they're all either unused, 2xx, or not-2xx20:35
peluseclayg, FYI 64 workers didn't help.  seems like kind of a nit so we're moving on to reconstructor tests...20:35
*** MVenesio has joined #openstack-swift20:35
torgomaticand I'm going to call not-2xx "4xx" because it doesn't have a minus sign in it and I'm about to use it as a variable20:35
torgomaticso total = unused + 2xx + 4xx20:35
torgomaticand total - 4xx = unused + 2xx20:36
claygwbhuber: I think you'll want to try a tight unittest around ECPutter.connect with http_connect mocked out to raise a socket.error with ECONNREFUSED20:36
torgomaticthen observe that if unused + 2xx < ec_ndata, then we're done. We can't possibly get a successful reconstruction as we don't have enough pieces.20:36
claygwbhuber: well even that may not be entirely enough because the debug_logger might behave slightly differently than the real adapted logger20:36
torgomaticso we can stop trying more nodes once unused + 2xx < ec_ndata, or equivalently, once total - 4xx < ec_ndata20:36
claygtorgomatic: wow - you totally just highschool algebra'd me20:37
torgomaticI don't get to break out the algebra stick often20:38
wbhuberclayg: why don't we use self.logger.exception instead of self.app.exception_occurred?  i guess real.adapted.logger = self.logger.exception whereas debug_logger exists where it is now20:39
claygtorgomatic: *but* if I have my request_node_count set crazy high - and I get ec_ndata + nparity 416's - like how many 404's do I really want to consume before I give you back your 416?20:39
claygtorgomatic: I mean - it *could* be "out there" "reconstructable" - or maybe it is *toally* reconstructed and on the primaries - it just can't service your stupid range request?20:40
claygwbhuber: the benifit of app.exception_occurred is really all about the node erorr limit tracking20:40
torgomaticclayg: well, if you want to be 100% certain that there's no way to make this GET work, then the answer is total_nodes - ec_ndata + 120:40
torgomaticgiving up earlier is probably a good idea, though, because that's a lot of work every time someone fatfingers an extra 0 onto their range request20:41
*** pberis has joined #openstack-swift20:41
*** gyee has joined #openstack-swift20:41
notmynameyo20:41
claygI was just suggesting that in a unittest what you observe from debug_logger may not be a perfect proxy for what the real logger would do in the server - but if there's a differce it's a bug in our fake and should probably be fixed - i'm just thinking through how you might try and duplicate the issue - it *seems* like that code path should go through that adapted logger's .excpetion method and peluse should have never seen th20:42
* notmyname is a an OpenStack Trove day today20:42
wbhuberclayg: yeah, i am going to see if i can create something of a mock out of this20:42
claygtorgomatic: yeah that's why I figured once you have ec_ndata 416's that's probably good enough - if we had that many 206's we'd return it - I think 416's are just another kind of etag bucket - if you get enough to fill a "rebuildable" - take it and don't look back20:43
claygwbhuber: good luck!20:43
*** lpabon has joined #openstack-swift20:43
*** lpabon has quit IRC20:43
claygpeluse: quit using our software and you wouldn't find all these arcane bugs20:44
wbhuberclayg: lol20:44
claygtorgomatic: anyway - i have a patch - i'll push it up20:44
torgomaticclayg: sounds good20:44
wbhuberclayg: it could be just how the format is mapped up from adapter logger's exception method...20:45
claygwbhuber: that would be an unexpected surprise!20:46
claygtorgomatic: did you see peluse's note about connection timeout's in his benchmark run?  *connection* timeouts.  i wish we had that "better eventlet logging" patch in for him so we look at if the object-server is getting getting gummed up in eventlet land20:49
*** changbl has quit IRC20:53
claygcharz: bah!  you just can't please some people!  => lp bug #148860820:53
openstackLaunchpad bug 1488608 in OpenStack Object Storage (swift) "stats output in reconstructor.py gives wrong device count" [Undecided,New] https://launchpad.net/bugs/148860820:53
*** eranrom has joined #openstack-swift20:53
*** ccavanna has quit IRC20:53
*** tsg has joined #openstack-swift20:53
eranromGreetings. acoles, clayg thanks for reviewing the probe tests additions.20:55
notmynamethere's not been anything added to the meeting agenda by anyone. other than a "what's the status of ...", I don't have anything either20:55
*** tsg_ has joined #openstack-swift20:55
notmynameanyone have something that needs to be in the meeting tomorrow?20:55
claygnotmyname: oh oh oh - let's skip!20:55
*** tsg has quit IRC20:55
notmynameclayg: maybe. let's see if there is something important first :-)20:55
*** tsg_ is now known as tsg20:55
notmynamealso, I'll want to check/alert the people who are asleep right now20:56
eranromyou got me alerted and I am definately sleeping20:56
notmynameeranrom: :-)20:57
notmynameeranrom: actually, I talked about that with Rowen last week. I'm sorry about keeping you up late. I honestly didn't realize it was so late for you. if you do have stuff in a meeting, I want to make sure it's the first agenda item so you can get to bed20:58
eranromyep, Ronen updated me, thanks! I guess IL is still not in the worst time zone...20:59
notmyname(oh, sorry. ronen)20:59
notmynameyeah, mahatic gets that award in bangalore21:00
eranromanyway, I do not think I have anything for the agenda tomorrow, but will have a fresh patch soon fixing Clays good comments.21:00
notmynamegreat21:00
claygeranrom: awesome!  and please do poke me before it gets to be another long cycle w/o feedback - i'll try to stay on top - but I'm basically a terrible person :'(21:03
notmynamekota_: ho: mattoliverau: cschwede: acoles_: please ping me if you have anything to bring up in the meeting21:04
eranromclayg: sure will do! Thanks!21:04
*** tab___ has quit IRC21:08
openstackgerritClay Gerrard proposed openstack/swift: EC GET path: require fragments to be of same set  https://review.openstack.org/21218721:08
claygpeluse: torgomatic: ^ after acoles showed me the light it's basically poetry in code form21:09
*** haomaiwang has quit IRC21:09
*** haomaiwang has joined #openstack-swift21:10
*** hrou has quit IRC21:14
openstackgerritEran Rom proposed openstack/swift: Container-Sync to iterate only over synced containers  https://review.openstack.org/20580321:15
*** nadeem has quit IRC21:30
openstackgerritSamuel Merritt proposed openstack/swift: Make the object auditor's run-once mode run once.  https://review.openstack.org/21644921:31
openstackgerritMinwoo Bae proposed openstack/swift: EC: Handoff node to push existing fragment to the correct location.  https://review.openstack.org/19684821:37
*** rjaiswal has quit IRC21:40
openstackgerritMerged openstack/swift: test/(functional/probe):Replace python print operator with print function (pep H233, py33)  https://review.openstack.org/20660321:43
*** thumpba has quit IRC21:48
*** eranrom has left #openstack-swift21:54
*** tsg has quit IRC21:56
*** pgbridge has quit IRC21:57
*** MVenesio has quit IRC22:00
claygminwoob: ping!22:00
minwoobclayg: Hi!22:01
minwoobclayg: I think this is right.22:02
minwoobclayg: partner_primary (node) is placed with the extra fragment.22:03
minwoob(Which simulates ring rebalance causing fragments of the same object to be placed on the same node).22:04
minwoobclayg: Reconstructor then fixes the situation on the "new primary".22:05
*** rjaiswal has joined #openstack-swift22:07
minwoobOr vice versa -- it has now become a handoff node.22:07
*** aix has joined #openstack-swift22:07
claygminwoob: yeah... I think that's only one half of the story - not bad to have a test for it - but... I think your change had more to do with what happens when you run the reconstructor on say the downed primaries left hand partner (who would discover the frag missing from the downed primary already exists on the *other* primary and *not* rebuild it)22:08
claygwe would expect that after running *someone's* reconstructor with the change in the patch that it would *not* rebuild the object (GET should still work) but instead *wait* for the other reconstructor to run.22:08
claygso maybe the test is more than halfway there22:08
claygminwoob: I think there's a helper method used in one of the other ec probe tests that will find anodes left and right hand partners22:09
*** haomaiwang has quit IRC22:09
claygif you enumerate them explicitly you may be have to move the handoff frag to the left hand partner, run reconstructor on right hand partner (verify it's *not* reconstrcuted) then run reconstructor on the right hand partner and verify it's reverted22:10
*** haomaiwa_ has joined #openstack-swift22:10
claygminwoob: also, for my own personal edification - can you tell me what shutil.move will do if you give it a path that overlaps with another?  does it just *merge* the two?  I feel like if I tried to `mv /srv/node1/sdb1/objects/0 /srv/node2/sdb2/objects/0` and /srv/node2/sdb2/objects/0 already exists I'd get an EEXIST22:11
claygbut the mv shell utility may have different behavior than the shutil.move22:12
*** chsc has quit IRC22:12
minwoobclayg: It depends on whether dest is a file or folder.22:12
minwoobclayg: If it's a file, I think it will overwrite it.22:12
minwoobclayg: If it's a folder, I believe it will place src in dest.22:13
clayghrmm... actually 412 might not be quite right - you should `import pdb; pdb.set_trace()` right there - pause the test - and the go run find on your file system until you're convinced it moved things in the right place like you think22:13
*** tsg has joined #openstack-swift22:14
minwoobGot it.22:17
mattoliverauMorning22:23
*** flwang has quit IRC22:23
*** flwang has joined #openstack-swift22:24
*** pberis has quit IRC22:24
*** tsg has quit IRC22:24
*** tsg has joined #openstack-swift22:28
claygminwoob: i'm not sure if you'd played with pdb & nosetests much - if not be sure to give nose the --verbose --no-caputure (I always just use -vsx) so you can see your debugger prompt - but if you run `nosetests /path/to/probe/test_thing.py:TestCaseName -vsx` it should work (mostly)22:30
claygmattoliverau: good morning!22:30
minwoobclayg: Thanks for the tip!22:30
minwoobmattoliverau: morning!22:30
minwoobclayg: Yeah, alternatively I normally use the PyCharm debugger as it's the environment I've been using, but with probe tests for some reason they freeze even when I attach the processes.22:33
minwoobclayg: Right now might be a good opportunity though, to familiarize with pdb & nosetests.22:34
*** silor1 has joined #openstack-swift22:35
*** jlhinson has quit IRC22:35
claygminwoob: oh that's cool tho - you'll have to show me that at the next hack-a-thon!22:36
minwoobclayg: Sure. We're all using it over here, btw.22:37
minwoobKind of as our default tool.22:37
*** silor has quit IRC22:38
*** silor1 is now known as silor22:38
minwoobWell, not kind of. For real.22:38
*** ho has joined #openstack-swift22:44
claygnotmyname: I think there should be a limit to the number of things we can have on the priority review queue :\22:46
*** tsg has quit IRC22:47
*** asd112z has quit IRC22:59
*** km has joined #openstack-swift23:00
*** wbhuber has quit IRC23:07
hogood morning!23:07
claygho: good morning23:08
*** haomaiwa_ has quit IRC23:09
*** 64MADOR5X has joined #openstack-swift23:10
*** silor has quit IRC23:11
*** minwoob has quit IRC23:13
hoclayg: hello23:14
mattoliverauho: morning23:18
homattoliverau: morning!23:19
*** kei_yama has joined #openstack-swift23:25
*** dmorita has joined #openstack-swift23:26
*** minwoob has joined #openstack-swift23:26
*** bitblt has joined #openstack-swift23:28
*** bitblt has quit IRC23:28
*** changbl has joined #openstack-swift23:29
*** marzif_ has quit IRC23:29
*** kevinc_ has quit IRC23:30
*** minwoob has quit IRC23:32
*** pberis has joined #openstack-swift23:33
*** ccavanna has joined #openstack-swift23:35
honotmyname: +1 for clayg's comment and I would like to know registered by "who" in Starred Patches (by core), if possible.23:35
claygnotmyname: and a pony23:36
*** tsg has joined #openstack-swift23:37
*** annegent_ has joined #openstack-swift23:42
*** marcusvrn_ has quit IRC23:45
*** annegentle has quit IRC23:45
*** CR7 has joined #openstack-swift23:46
*** kota_ has joined #openstack-swift23:49
*** ChanServ sets mode: +v kota_23:49
kota_good morning23:52
*** pberis has quit IRC23:52
tonybnotmyname: Can you -W and then +W https://review.openstack.org/#/c/215786/ it seems to be stuck :/23:52

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