Wednesday, 2015-08-19

*** hezhiqiang has quit IRC00:01
kairoho: http://pastebin.com/GwdDdci3 Do you want I update in the ask?00:02
hokairo: thanks! no it's fine. you got 401 not 403. wait a minutes00:03
*** ccavanna has joined #openstack-swift00:07
*** kevinc___ has quit IRC00:08
*** ccavanna has quit IRC00:09
hokairo: there is no info in the token. L6 in the debug log and code is here: https://github.com/openstack/keystonemiddleware/blob/master/keystonemiddleware/auth_token/__init__.py#L71600:09
hokairo: I'm not sure but your authtoken section in proxy-server.conf doesn't follow https://github.com/openstack/swift/blob/stable/kilo/etc/proxy-server.conf-sample#L284.00:14
hokairo: can you try this? http://paste.openstack.org/show/421196/00:17
kairoho: sure. I got it on restart of proxy-server http://paste.openstack.org/show/421217/00:24
kairoho: I'll try. one minute.00:24
kairoho: the same error. 40100:30
hokairo: you replaced the section and got 401. how about "L6 in the debug log"?00:37
kairoho: sorry, I'm confused. https://github.com/openstack/keystonemiddleware/blob/master/keystonemiddleware/auth_token/__init__.py#L716 My __init__.py don't have this same line.00:41
hokairo: sorry. in kilo https://github.com/openstack/keystonemiddleware/blob/stable/kilo/keystonemiddleware/auth_token/__init__.py#L632 is the one.00:44
*** lyrrad has quit IRC00:46
hokairo: I checked the installation guide and realized your configuration is latest way (proxy-server.conf is old...)00:46
hokairo: please re-replace it.00:48
*** nadeem has quit IRC00:48
kairoho: this   https://git.openstack.org/cgit/openstack/swift/plain/etc/proxy-server.conf-sample?h=stable/kilo00:50
kairoho: I used this sample.00:51
*** lpabon has joined #openstack-swift00:53
*** gyee has quit IRC00:55
kairoho: Do you have some proxy-server.conf sample updated?00:57
*** lpabon has quit IRC00:58
*** darrenc is now known as darrenc_afk01:07
hokairo: i created curl version of head account. http://paste.openstack.org/show/421275/01:11
hokairo: is my saio's proxy-server.conf sample fine?01:12
*** _hrou_ has joined #openstack-swift01:13
hokairo: you use right part of X-Subject-Token: as a token.01:13
*** hrou has quit IRC01:14
openstackgerritMerged openstack/swift: Make swift-ring-builder filename usage more consistent  https://review.openstack.org/20978701:20
kairoho: I'll try :) Thanks.01:21
*** darrenc_afk is now known as darrenc01:21
kairoho: the curl worked well01:27
*** sanchitmalhotra1 has joined #openstack-swift01:33
*** nexusz99_ has joined #openstack-swift01:35
*** nexusz99 has quit IRC01:35
hokairo: means "head account worked well"?01:35
*** sanchitmalhotra has quit IRC01:35
hokairo: my saio's setting regarding auth. http://paste.openstack.org/show/421276/01:36
*** wbhuber has joined #openstack-swift01:38
kairoho: yeah. the curl version of head account. But curl -i http://ctl1srv:8080/v1/AUTH_dc182f2c475846889c7cb68602439d84 -I -H "X-Auth-Token: <token>" not.01:41
kairoho: I'll try this auth01:41
hokairo: did you set right part of X-Subject-Token for <token>?01:42
*** nakagawamsa has joined #openstack-swift01:44
hokairo: it's better to validate token first. use: http://paste.openstack.org/show/421295/01:45
kairoho: yes. but I received the same 401.01:46
hokairo: if there are info in the token, there is a problem with swift configuration. if not, there is a problem with keystone configuration.01:55
claygg'night01:58
openstackgerritMerged openstack/swift: Doc instructions for post rebase steps  https://review.openstack.org/20866902:01
kairoho: I'll review the the keystone configuration.02:01
*** haomaiwang has joined #openstack-swift02:05
*** jrichli has joined #openstack-swift02:06
hoclayg: good night!02:07
*** baojg has joined #openstack-swift02:15
openstackgerritTim Burke proposed openstack/python-swiftclient: flake8 ignores same hacks as swift  https://review.openstack.org/20290902:22
*** annegentle has quit IRC02:25
mattoliveraunotmyname: Melbourne Australia voted worlds most livable city (I think 5th year in a row) which is why you need to visit ;) http://www.cnn.com/2015/08/17/travel/most-liveable-city-2015/02:26
*** annegentle has joined #openstack-swift02:26
*** annegentle has quit IRC02:32
*** baojg has quit IRC02:35
hokairo: I summarized the script: http://paste.openstack.org/show/421329/ . hope it works :-)02:36
hotorgomatic: thanks for the review! yay! :-)02:38
jrichlimattoliverau hrou: wow, both Vancouver and Toronto made it to the top 5.  Go Canada!  Of course, 'Oz' is in there twice as well ;-)02:42
_hrou_jrichli, mattoliverau, yea Toronto is always 4th in these.  I was going to say notmyname is a lot closer to 3 out of the 5, but I guess there's nothing like #1 ; )02:45
*** baojg has joined #openstack-swift02:48
hugokuo@clayg @timburke Keystone V3 works with new version of keystone middleware https://github.com/openstack/keystonemiddleware. This middleware includes keystone domain concept.02:49
hugokuoAnyone needs information about keystone V3 + Swift. Feel free to ping me02:50
hohugokuo: hi, swiftclient + keystone v3 works? i usually use curl so i don't know it02:51
*** dbarman1 has quit IRC02:53
*** _hrou_ is now known as hrou02:55
*** wbhuber has quit IRC02:56
timburkehugokuo: so is an old version of keystonemiddleware the most likely explanation for https://ask.openstack.org/en/question/80290/swift-account-head-failed-401-unauthorized-kilo-centos-7/ ?02:57
*** haomaiwang has quit IRC03:01
*** jrichli has quit IRC03:01
*** jrichli has joined #openstack-swift03:02
*** haomaiwang has joined #openstack-swift03:02
hugokuocurl -i http://ctl1srv:8080/v1/AUTH_dc182f2c475846889c7cb68602439d84 -I -H "X-Auth-Token: 706f5084859f46c0a85218b14d3fd76c"03:03
hugokuoINFO:swiftclient:RESP STATUS: 401 Unauthorized03:03
hugokuoIt is.03:03
hugokuoThe debug information indicates the toekn sent to proxy but proxy either can't validate it with Keystone or the token was wrong.   It's more like proxy can't validate the token due to 1) The user is not in default domain  2) The service admin user's credential is wrong03:05
hugokuoFor this case, the user can try to validate a user in default domain. If it works that mean he has old version of keystone middleware03:05
hugokuo1) Ensure the service admin's credential is correct in middleware  2) To access Swift by a user in default domain via keystone v2 API. 3) Check the middleware version.03:07
*** kei_yama has quit IRC03:07
*** sanchitmalhotra has joined #openstack-swift03:11
*** kei_yama has joined #openstack-swift03:12
*** sanchitmalhotra1 has quit IRC03:13
*** rodrigods has quit IRC03:16
*** csmart has quit IRC03:18
*** rodrigods has joined #openstack-swift03:19
*** csmart has joined #openstack-swift03:21
*** sanchitmalhotra1 has joined #openstack-swift03:24
*** sanchitmalhotra has quit IRC03:26
*** raginbajin has quit IRC03:27
*** raginbajin has joined #openstack-swift03:29
*** logan2 has quit IRC03:31
*** ccavanna has joined #openstack-swift03:37
*** haigang has joined #openstack-swift03:47
openstackgerritJanie Richling proposed openstack/swift: Decrypting Container Listing  https://review.openstack.org/21443803:48
*** fandi_ has joined #openstack-swift03:48
fandi_hi all03:49
fandi_how to install swift-stack with dev env on virtual box ?03:49
*** fandi_ has quit IRC03:49
jrichlifandi_ : if you want a one-node swift cluster, you can use vagrant https://github.com/swiftstack/vagrant-swift-all-in-one03:51
*** hezhiqiang has joined #openstack-swift03:52
openstackgerritpaul luse proposed openstack/swift: EC GET path: require fragments to be of same set  https://review.openstack.org/21218703:58
*** haomaiwang has quit IRC04:01
*** km has quit IRC04:01
*** haomaiwang has joined #openstack-swift04:02
*** km has joined #openstack-swift04:02
*** kei_yama has quit IRC04:03
*** kei_yama has joined #openstack-swift04:03
*** jlhinson has joined #openstack-swift04:05
*** jamespag` has quit IRC04:05
notmynamegood evening04:10
*** raginbajin has quit IRC04:10
*** ppai has joined #openstack-swift04:13
*** raginbajin has joined #openstack-swift04:28
*** jrichli has quit IRC04:54
*** hrou has quit IRC04:55
*** baojg has quit IRC04:59
*** haomaiwang has quit IRC05:01
*** haomaiwa_ has joined #openstack-swift05:02
*** SkyRocknRoll has joined #openstack-swift05:05
*** mahatic has joined #openstack-swift05:06
*** mahatic_ has joined #openstack-swift05:07
*** mahatic has quit IRC05:07
honotmyname: good evening!05:11
notmynameho: hi! I was just working on my travel to tokyo05:11
honotmyname: great!05:12
honotmyname: do you have a plan to put some holiday after it?05:12
notmynameno. while I enjoy traveling, I don't like to be gone longer than that if my wife isn't with me. I don't want to leave her alone with the kids for that long05:13
*** kei_yama has quit IRC05:14
*** km has quit IRC05:15
*** kei_yama has joined #openstack-swift05:15
honotmyname: yeah, I joined the hack-a-thon, then back I feel some cool atomosphere in my house :-) in tokyo we have some good sighseeing place such as asakusa, tukiji and so on.05:16
notmynamebut I am getting in a day early05:16
notmynameyeah, I'd like to see what I can while I'm there :-)05:16
honotmyname: yay!05:16
*** silor has joined #openstack-swift05:17
*** silor1 has joined #openstack-swift05:19
mahatic_notmyname: I'm seeing you around here for the first time, at this hour!05:20
*** silor has quit IRC05:21
*** silor1 is now known as silor05:21
notmynameif this is the first time you've seen me online at this time... ;-)05:25
notmynamemahatic_: how are things? :-)05:26
mahatic_notmyname: hehe, yeah. Everything good! It was hilarious to read on your knowledge about cricket on IRC :P05:28
notmynameheh05:28
*** jith_ has joined #openstack-swift05:29
mahatic_I'm also actually doing some tokyo travel work - documents05:29
mahatic_documents for visa05:29
notmynameoh good05:29
*** jrichli has joined #openstack-swift05:31
jith_hi all i have done with SAIO setup.. But certain test cases are getting failed in unittests, functests and probetests.. is it mean that swift is not configured properly.. how to see the log for these testcases05:32
notmynamejith_: correct. all tests should pass in a SAIO05:33
notmynamejith_: you can use `./.unittests -vv` to get more info about what tests are being run.05:33
notmynamebut the failure message should be printed when the test run finishes05:34
jith_notmyname: thanks05:35
jrichlimahatic: rebase on patch 214438 instead of the one I had mentioned earlier.  It adds handling of container listings.05:35
patchbotjrichli: https://review.openstack.org/#/c/214438/05:35
*** jrichli has quit IRC05:35
*** jlhinson has quit IRC05:38
mahatic_jrichli: sure, will do05:38
jith_notmyname: how to change the maximum uploading size of 5GB in swift?? i mean without segmenting i need to upload the data above with size 7 GB05:40
hohugokuo: cool. one question. how to confirm "validate a user in default domain"?05:42
notmynamejith_: it's set in swift.conf. see the message at https://github.com/openstack/swift/blob/master/etc/swift.conf-sample#L8905:42
jith_notmyname: thanks :)05:44
*** hezhiqiang has quit IRC05:45
hugokuoho: Two steps : 1) Use service admin's token to fetch that user's information of the incoming token via V3 and V2 API. 2) V3 suppose to return the domain information to you05:45
*** hezhiqiang has joined #openstack-swift05:45
zaitcevjith_: But you really should not bother, because no matter how far you change it, there's going to be a longer object. My advice would be to learn to live with segmentation. I think the CLI segments automatically for you.05:46
hohugokuo: is it same understanding with my previous post? (3) in http://paste.openstack.org/show/421329/05:47
hugokuoho: correct05:50
hohugokuo: thanks!05:53
*** sanchitmalhotra has joined #openstack-swift05:57
*** baojg has joined #openstack-swift05:58
*** sanchitmalhotra1 has quit IRC06:00
*** haomaiwa_ has quit IRC06:01
*** haomaiwa_ has joined #openstack-swift06:02
notmynamesome pics from last week06:13
notmynamehttp://d.not.mn/hackathon_pics/bbq.jpg06:14
notmynamehttp://d.not.mn/hackathon_pics/cookies.jpg06:14
notmynamehttp://d.not.mn/hackathon_pics/dinner.jpg06:14
notmynamehttp://d.not.mn/hackathon_pics/golf1.jpg06:14
notmynamehttp://d.not.mn/hackathon_pics/golf2.jpg06:14
notmynamehttp://d.not.mn/hackathon_pics/lunch.jpg06:14
notmynamehttp://d.not.mn/hackathon_pics/panicroom.jpg06:14
notmynamehttp://d.not.mn/hackathon_pics/people1.jpg06:14
notmynamehttp://d.not.mn/hackathon_pics/people2.jpg06:14
notmynamehttp://d.not.mn/hackathon_pics/sign.jpg06:14
notmynamehttp://d.not.mn/hackathon_pics/topics1.jpg06:14
notmynamehttp://d.not.mn/hackathon_pics/topics2.jpg06:14
notmynameand good night06:15
hothe bbq was so delicious :-)06:18
mahatic_nice! lots of fun and work!06:23
*** sanchitmalhotra1 has joined #openstack-swift06:27
*** akle|2 has joined #openstack-swift06:28
*** sanchitmalhotra has quit IRC06:29
*** wshao has joined #openstack-swift06:40
*** wshao has quit IRC06:41
jith_zaitcev: thanks really... ya but i made swift as glance backend... so i cant able to upload images(>5GB) to glance using glance client and also using dashboard06:43
zaitcevjith_: that makes no sense06:43
zaitcevjith_: I'm not familiar with Glance intimately, but I know for sure that it segments VM images automatically and transparently. You don't need to configure anything for it to happen.06:44
jith_zaitcev: i m not getting error when i upload images greater than 5GB in glance... but when i launch instance from it.. its not getting launched... other images below 5GB is getting launched06:46
jith_zaitcev: will check again06:46
zaitcevHmm.06:46
zaitcevjith_: That may be a problem. However, it could be something like Swift updater not working right and Glance using DLO that needs up-to-date container listings.06:48
zaitcevSadly I cannot investigate it for you.06:49
jith_zaitcev: thanks for the informative answer...  Any way to check the swift processes(like swift updater) seperately ?06:51
zaitcevI'd start by using Glance credentials with Swift CLI to look at images it uploaded, including those that get segmented and see if CLI can download them.06:52
zaitcevBut I don't know where to go further06:52
zaitcevWell, Glance has its own CLI, so you can pretend to be Nova06:53
zaitcevBTW, make sure Nova's compute nodes aren't out of temporary space.06:53
zaitcevIt's going to be the height of irony if they only have 5 GB left in /var by a gigantic coincidence...06:54
*** ppai_ has joined #openstack-swift06:54
*** ppai has quit IRC06:56
*** StevenK has quit IRC06:58
*** StevenK has joined #openstack-swift06:59
*** haomaiwa_ has quit IRC07:01
*** haomaiwang has joined #openstack-swift07:01
*** rledisez has joined #openstack-swift07:02
*** geaaru has joined #openstack-swift07:07
*** sileht has joined #openstack-swift07:15
*** SkyRocknRoll has quit IRC07:30
*** ppai_ has quit IRC07:35
jith_zaitcev: thanks will check it... sorry for late reply07:45
*** ppai_ has joined #openstack-swift07:48
*** zaitcev has quit IRC07:54
*** rledisez1 has joined #openstack-swift07:58
*** rledisez has quit IRC07:58
*** haomaiwang has quit IRC08:01
openstackgerritKazuhiro MIYAHARA proposed openstack/swift: Fix dispersion-reports error message  https://review.openstack.org/21369708:01
*** haomaiwang has joined #openstack-swift08:02
*** jordanP has joined #openstack-swift08:20
*** acoles_ is now known as acoles08:25
*** jistr has joined #openstack-swift08:34
openstackgerritOpenStack Proposal Bot proposed openstack/swift: Updated from global requirements  https://review.openstack.org/8873608:39
*** ho has quit IRC08:41
*** sanchitmalhotra has joined #openstack-swift08:44
*** sanchitmalhotra1 has quit IRC08:47
*** haigang has quit IRC08:52
*** haigang has joined #openstack-swift08:52
*** haigang has quit IRC08:52
*** haigang has joined #openstack-swift08:53
*** haigang has quit IRC08:53
*** haigang has joined #openstack-swift08:53
*** aix has joined #openstack-swift08:54
*** kei_yama has quit IRC08:55
*** haomaiwang has quit IRC09:01
*** haomaiwa_ has joined #openstack-swift09:02
*** joeljwright has joined #openstack-swift09:11
*** ChanServ sets mode: +v joeljwright09:11
*** hezhiqiang has quit IRC09:15
*** hezhiqiang has joined #openstack-swift09:15
*** SkyRocknRoll has joined #openstack-swift09:21
*** sanchitmalhotra1 has joined #openstack-swift09:32
*** ppai_ has quit IRC09:33
*** sanchitmalhotra has quit IRC09:34
*** sanchitmalhotra has joined #openstack-swift09:44
*** sanchitmalhotra1 has quit IRC09:46
*** ppai_ has joined #openstack-swift09:47
*** mahatic_ has quit IRC09:52
*** haomaiwa_ has quit IRC10:01
*** haomaiwang has joined #openstack-swift10:02
openstackgerritMerged openstack/swift: Keep user id and project id in subrequests env  https://review.openstack.org/21214910:06
*** nakagawamsa has quit IRC10:07
*** hezhiqiang has quit IRC10:18
*** baojg has quit IRC10:26
*** baojg has joined #openstack-swift10:27
*** baojg has quit IRC10:31
*** mahatic has joined #openstack-swift10:39
*** mahatic has quit IRC10:47
*** nexusz99_ has quit IRC10:48
*** mahatic has joined #openstack-swift10:54
*** mahatic has quit IRC10:58
acoleskairo: did you get your keystone auth sorted? looks like ho was helping. i left a comment on your ask, think problem may be that authtoken middleware is failing to auth with keystone, which means it cannot validate the x-auth-token in the account HEAD request.11:08
*** haomaiwang has quit IRC11:12
*** cdelatte has joined #openstack-swift11:31
*** delattec has joined #openstack-swift11:31
openstackgerritpaul luse proposed openstack/swift: EC GET path: require fragments to be of same set  https://review.openstack.org/21218711:44
acolespeluse: here?11:48
openstackgerritpaul luse proposed openstack/swift: EC GET path: support use of alternate fragments on object servers  https://review.openstack.org/21314711:55
pelusehi11:55
acolespeluse: i will review your same set frags patch today11:55
pelusecool, thanks11:56
pelusethey are both up to date/ready11:57
acolesk11:57
acolespeluse: you're #2 on list, lunch is #1 ;)11:58
pelusefood should always come first!11:59
jith_hi all.. what is this error.. when i try to start/restart the processes. Unable to modify max process limit. Running as non-root?12:01
pelusejith_, see https://wiki.openstack.org/wiki/TroubleshootingSwift - it OK12:06
* peluse off for breakfast...12:07
*** robefran has quit IRC12:10
jith_peluse: thanks12:14
jith_hi all, in saio setup i m able to start only the server of proxy,object,container and account processes.. what i have to do to start the other process such as container-updater, container auditor, object auditor etc??12:25
*** chlong has joined #openstack-swift12:26
jordanPjith_, try swift-init all start12:27
*** wbhuber has joined #openstack-swift12:33
*** logan2 has joined #openstack-swift12:39
*** haomaiwang has joined #openstack-swift12:39
*** haigang has quit IRC12:39
*** mahatic has joined #openstack-swift12:46
*** SkyRocknRoll has quit IRC12:49
*** ccavanna has quit IRC12:58
*** wbhuber has quit IRC12:59
*** bill_az has joined #openstack-swift13:01
acolespeluse: am i being dumb, or does test_GET_with_misplaced_frags have nothing to do with the etag buckets change? in patch 21218713:03
patchbotacoles: https://review.openstack.org/#/c/212187/13:03
*** petertr7_away is now known as petertr713:11
*** hrou has joined #openstack-swift13:11
*** lpabon has joined #openstack-swift13:13
*** annegentle has joined #openstack-swift13:13
*** esker has joined #openstack-swift13:14
*** lpabon has quit IRC13:16
*** ppai_ has quit IRC13:17
*** dustins has joined #openstack-swift13:19
*** lcurtis has joined #openstack-swift13:22
*** NM has joined #openstack-swift13:22
*** ppai_ has joined #openstack-swift13:30
*** robefran has joined #openstack-swift13:37
*** annegentle has quit IRC13:37
kairoacoles: sorry I was out. Thank you.13:43
kairoacoles: I found the problem. The problem is the users services passwords (swift, glance, nova etc) has the special caracters and in all services the password are between "" or ''. But on proxy-server.conf if I use "" or '' doesn't work.13:43
*** mriedem has joined #openstack-swift13:46
mriedemis there someone around that is able to create a stable/juno branch for python-swiftclient? there are some capped/uncapped dependency issues involving swiftclient on stable/juno we need to resolve per bug 148657613:49
openstackbug 1486576 in python-swiftclient "version 2.3.1 on stable/juno has uncapped futures which breaks dep resolution with capped taskflow" [Undecided,New] https://launchpad.net/bugs/148657613:49
mriedemthe stable/juno branch would be created from the 2.3.1 tag of python-swiftclient13:49
*** blmartin has joined #openstack-swift13:51
peluseacoles, it does sorta :)13:53
peluseacoles, it was written before the patch but the idea is to simulate the actual behavior of the bug that started all of this13:55
peluseacoles, and the other new test routine is specically based on the implementation of the fix13:55
acoleskairo: ok glad you found it. could be difference in way other services read config using oslo.config vs swift ConfigParser :/13:55
acolespeluse: its a cool test, just had me scratching my ehad :)13:56
acoleshead even13:56
peluseacoles, there is a sorta wording challenge in that test code though, tere's a var named 'handoff_node' that actually isn't a handoff, or even a parity node, because of the shuffling of the nodes in node_iter.  It's just 'another node'13:56
*** wbhuber has joined #openstack-swift13:56
acolespeluse: yeah i got a comment about that.13:58
peluseacoles, but yeah I guess it's not totally tied to etag_buckets, it was part of the last larger patch set that included some fixes and tets from both myself and clayg :)13:58
*** mahatic has quit IRC13:58
acolespeluse: the handoff nodes are parity nodes i think, but then you make a data node return content from a parity node13:58
*** mahatic has joined #openstack-swift13:58
peluseacoles, BTW I have to take off for a few hours.  You'll probably be gone when I get back but thanks again for looking through these!13:59
acolesand all the etags are good right? in that test?13:59
*** ccavanna has joined #openstack-swift13:59
*** mriedem is now known as mriedem_meeting13:59
peluseacoles, they're not even parity because of node shuffling... they can be anything!13:59
acolespeluse: k. i'm confused then :)13:59
peluseacoles, yes, all the etags are good in that case.  I was thinking of the probe tests that does an overwrite when I was tying this one to the etag buckets fix13:59
acolesk i will leave comments on gerrit in case i miiss you later14:00
jith_jordanP: thanks... it was working14:00
peluseacoles, yeah, I know... so primary nodes in this case would be 0-14 then they're shuffled in the node_iter because that's how we do things.  So slicing the first data or last parity doesn't get you what you might think14:00
mattoliveraumorning14:00
peluseacoles, you end up getting 'something' from the first 10 (slicing off data) and 'something' for the last 4 (slicing parity) but any node can be in any order at this point...14:01
peluseacoles, OK, gotta go....14:01
wbhuberacoles: i've several questions related to the low durable quorum comments you've left.  i'll pan them out later in the morning - need some time to think through them.14:01
*** robefran has quit IRC14:02
acoleswbhuber: sure. it was a bit of a brain dump, but basically your patch is good but we need to do more :)14:02
mattoliveraupeluse: I saw your email in intel/rackspace phone meeting today, are you attending it? I will be :)14:02
*** robefran has joined #openstack-swift14:02
acolesmattoliverau: morning !?!14:02
mattoliverauacoles: evening then :P (nah I'm still in Texas, so morning)14:04
wbhuberacoles: yes, "we need to do more" is what i'm trying to dissect to get the patch up and running.14:04
mattoliverauI fly back tomorrow afternoon14:04
*** petertr7 is now known as petertr7_away14:10
kairoacoles: can I report this for future people using the installation doc?14:12
acoleskairo: yes, you can report a bug on that install doc from link at bottom of the pages (swift team do not maintain those docs) and/or report a bug on swift project https://bugs.launchpad.net/swift14:14
acoleskairo: if you can include characters you found that broke in the bug report that would help14:15
acoleskairo: thanks!14:15
*** thumpba has joined #openstack-swift14:15
kairoacoles: I'll do that. thanks!14:17
hroukairo:  What led you to find the issue ?  Debugging these swift / keystone always seems to be a pain, ho did a really good job yesterday with you (and I took notes for my own future use) : )14:17
mahaticacoles: hello, query on "encrypt" flag,  how would the existing failing probe tests know not to use encryption? Modify them to check a client header? (the client header- which I am to add in TVM). Advice please14:21
notmynamegood morning14:22
mahaticgood morning!14:23
acolesmahatic: notmyname good morning14:23
acolesmahatic: yes the existing probe tests would need to be modified to send the disable encrypt header14:24
mahaticgood evening to me ;)14:24
acolesoops14:24
acolesmahatic: i'm still not certain whether we have encryption off by default (so no mods to existing tests) and 'enable' it for new probe tests by sending a key in a header, or on by default and disable in existing tests where necessary.14:25
kairohrou: hrou: well. I made all tests passed by ho. The errors appears only using the proxy (this really helped me). Now in the morning, I saw the msg from acoles (in my ask). I review the user password. First time I put the same password. But after I thought in try a simple password. Didn't work with "" and I thought in try without and works well. I went back and tried recreate the problem again. And14:25
kairoI found this. :)14:25
*** jrichli has joined #openstack-swift14:26
hroukairo, that's awesome, great works.  Thanks for the clarification !   I'll add that to my 'debugging keystone' issue list.14:26
kairothanks everybody! Sorry my bad english :)14:26
kairohrou: I like troubleshootings. I'm sysadmin and I need do it everyday :P14:27
mattoliveraunotmyname: morning, hows the OPs meetup going?14:27
acoleskairo: nice.14:27
hrouacoles, mahatic - can we just always include the header in those probe tests (assuming they're ignored if crypto is not in the pipeline) ?14:28
notmynamemahatic: going well enough. not much talk on swift (other than "yeah, swift doesn't give us any problems")14:28
hroukairo, yea that's the issue, I'm not at all a sys admin but need to pretend to be at times ; )  Thanks again !14:28
notmynamemattoliverau: ^14:28
mattoliverau\o/14:28
notmynameyesterday i talked to Time Warner Cable (a large US cable provider). they are using swift and have no problems14:29
acoleshrou: mahatic yes we should be able to always send a header an it be ignored14:29
notmynameacoles: yesterday I talked to Steve who says he sits next to you in bristol14:29
mattoliverauthats some of the feedback I've gotten here.. some ops in RPC want more swift experience but the damn thing is too stable (my paraphrase)14:29
acolesnotmyname: Steve P! yeah that makes sense14:30
hrouacoles, mahatic - right so I wonder just pass in the "no encrypt" headers for now always in those 2 probe tests.  But yea longer term may re evaluate depending on the approach taken.14:30
notmynameacoles: yeah, I had a good conversation with him and a couple of other people (someone on the "tools" side, IIRC) from HP14:30
acolesnotmyname: he's a smart guy14:31
notmynameI talked to dhellmann about some potential things we can do wrt hacking/flake8/whatever to get back to a whitelist of style checks (very low priority right now though)14:32
hrounotmyname, re TWC, not sure if you recall but vinsh a month ago or so from there : )14:32
notmynamehrou: I think you accidentally a word14:32
vinshSwift. thats my full time job at TWC.14:33
notmynamevinsh: ah! great :-)14:33
acolesvinsh: hi14:33
notmynamevinsh: you're not at the ops summit, are you?14:33
openstackgerritMerged openstack/swift: move global statement up a few lines  https://review.openstack.org/21400014:33
vinshI skipped out on it, have 5 team members there though.14:33
notmynameright. I had lunch with them yesterday14:33
hrouvinsh, ah, hey ! : ), notmyname yep sorry missed the "vinsh was online a month ago ..."14:34
kairohrou: it's my first time with OpenStack. On really I work with IBM Power/Linux/VMWare. I create this poor tool http://poweradm.org using Python (https://github.com/kairoaraujo/PowerAdm). In future I look contribute with openstack.14:34
vinshI'm busy scoping a large erasure code swift cluster that took priority.14:34
mahaticacoles: hrou would it not need any workaround (the headers) if crypto is not in the pipeline? as in a check?14:34
notmynamevinsh: cool. the EC support in swift is very new, so please ask questions and share experiences related to it in here :-)14:34
hroumahatic, you meaning adding the extra headers ?  Would they not just be ignored ? jrichli is online too so she can chime in as well now.14:35
vinshI have 8 object and 6 proxy nodes high horsepower on the way to setup and test it.14:35
vinsh216TB/object 36 disks each.14:35
vinsh6 10gig ports per node.14:35
*** thurloat_isgone is now known as thurloat14:35
mahatichrou: right, I mean the extra headers. Not sure if I figured it completely, will check back on that.14:36
hroukairo, that's really great !  Fairly new to openstack and swift as well.14:36
hroumahatic, yea its the lightest weight option for now (assuming they're ignored), but longer term who knows if we go with byok or what not.14:37
tdasilvanotmyname, vinsh: can you share how you are using swift? i'm assuming to store videos???? can you share any info like number of objects, cluster size, etc (a la HP and rackspace) ?14:37
*** NM has quit IRC14:37
*** mriedem_meeting is now known as mriedem14:37
vinshMight as well throw a question out there... Our proxy logs have almost a 1-1 "invalid token rejected downstream" message for every client request.  I feel this might be because I have 'v3' as part of my auth_uri.. but we needed to use v3 so that it can request that a service catalog is not returned in token validation.14:38
acolesmahatic: hrou unexpected headers will mostly be ignored14:38
*** jlhinson has joined #openstack-swift14:38
hrouacoles, perfect great.14:38
vinshtdasilva: Our current production swift is multi-region.  4 zones. 4 replicas. (2 in each)  It backs twc internal users desktop backup clients as well as serves web traffic for internal and extrenal sites.  it also does glance image backups and about 100 other things.  Mostly large image backups and any range of data stored.14:39
mahaticacoles: okay, thanks (I still don't think I understood the flow, will look into it more)14:39
notmynamevinsh:  I'm told that TWC isn't yet using it for streaming videos, but it's used for a lot of the content for their web properties. oh cool! lots of backups too14:40
vinshtdasilva: For videos, we are exploring erasure coding  (due to cost of the massive volume to store)14:40
vinshnotmyname: those 8object 6proxies are what I will test streaming on.14:40
notmynamecool14:40
vinshthe proxies are all nvme drives and 6 10gig ports 2.6Ghzx2 18 core cpus.14:40
*** petertr7_away is now known as petertr714:40
vinshWe don't know what sort of cpu erasure coding will eat up for video streaming.. so will start big and see.14:41
tdasilvavinsh: nice!14:41
wbhubervinsh, will you be able to share high level benchmarking numbers as a result of running workloads (video streaming) on EC?14:41
vinshHeck yes!14:42
tdasilvavinsh: last week there were some discussions about making some enhancements to global replication and one of the questions clayg had was how are people using multi-region14:42
vinshfor production we have used multi-region from the start.14:42
acolesvinsh: sounds like a problem with authtoken talking to keystone, can you paste proxy logs somewhere. keystone v3 should work14:43
acolesvinsh: also bump log level to debug to see more from authtoken14:44
vinshwbhuber: I have learned how to use ssbench so far, so I plan to use that against the EC cluster.. see if the numbers I get there make sense compared to what I got out of current production.14:44
tdasilvavinsh: we listed basically two use cases for multi-region. one is using a region as a DR site and another is where people are actually writing and reading data from both regions14:44
vinsh(yes I benchmarked against prod :-o )14:44
vinshacoles: Good call on debug. gathering some logs for ya.14:45
vinshtdasilva: That is pretty right on for how we use it... DR was primary concern.14:45
acolesvinsh: and if you can paste your proxy-server.conf14:45
*** annegentle has joined #openstack-swift14:46
*** NM has joined #openstack-swift14:47
vinshacoles: http://paste.openstack.org/show/421904/ is proxy-server.conf14:47
*** annegentle has quit IRC14:47
hrouacoles, vinsh, kairo - getting my notepad back out for another keystone/swift debug session ; )14:47
*** annegentle has joined #openstack-swift14:47
vinshacoles: and here are some log snips: http://paste.openstack.org/show/421905/14:48
vinshevery get seems to work.. but prints the invalid user token message as well.14:48
acolesvinsh: oh right, so no 401's just log noise?14:49
notmynameI've got to drive down to the ops meetup now. I'll be online off and on throughout the day (and yes there's still the team meeting today)14:49
vinshyeah14:49
vinshhrou: hopefully this is more obvious of a thing :)14:50
hrouvinsh, I put my notebook away, once I read the not 401 comment ; ) jk14:51
*** ppai_ has quit IRC14:52
*** kevinc_ has joined #openstack-swift14:52
*** minwoob has joined #openstack-swift14:58
*** zaitcev has joined #openstack-swift15:01
*** ChanServ sets mode: +v zaitcev15:01
*** logan2 has quit IRC15:01
acolesvinsh: hmmm, not sure. if token is invalid but access permitted then must be anonymous auth, which looks like either its a container sync request or you have public ACL15:04
acolesvinsh: debug log may give you more clues as to why the token is not validated15:05
*** logan2 has joined #openstack-swift15:05
vinshI think its all web traffic15:06
vinshso image loads of web pages15:06
*** zul has joined #openstack-swift15:07
*** chenhuayi has joined #openstack-swift15:09
acolesvinsh: i haven't played with anonymous auth much but a container ACL can grant access such that no auth token is required. that could explain the log pattern.15:10
acoleshttp://docs.openstack.org/developer/swift/misc.html#module-swift.common.middleware.acl <-- ACL format15:11
*** blmartin_ has joined #openstack-swift15:11
vinshacoles: debug log http://paste.openstack.org/show/421960/15:12
vinshYeah, its always 'Authorizing as anonymous" then transaction works.. then invalid token message15:12
*** chsc has joined #openstack-swift15:13
*** blmartin has quit IRC15:14
vinshacoles: Would you expect the proxy node to log an invalid token message for every anonymous request?15:15
acolesheh i was going to suggest a grep for 'via referer ACL '15:15
acolesvinsh: from reading authtoken code, yes, it appears to log every time15:15
vinshRight on, so its just annoying log chatter then :)15:16
vinshConfusing to the operator.. but no harm done.15:16
acoleslooks that way - authtoken is not swift maintained - its from keystonemiddleware project - so don't blame us :)15:17
vinshlol, I hear ya :)15:17
acolesvinsh: some of the *debug* level you see is coming from keystoneauth https://github.com/openstack/swift/blob/master/swift/common/middleware/keystoneauth.py#L56515:19
vinshacoles: Very interesting.  Thank you for helping me understand this one, appears to be a cosmetic issue only... user gets its data.15:21
acolesvinsh: np. will be v interesting to hear how your EC cluster comes along.15:21
*** zul has quit IRC15:23
*** petertr7 is now known as petertr7_away15:26
*** petertr7_away is now known as petertr715:27
petertr7Hey torgomatic, I had a question about Tempurls. The docs say that signatures are checked against all of the 4 secret keys (2 account level, 2 container level). I'm currently getting invalid tempurls  when I create signatures with the container key but no issues with the account key. Any thoughts?15:31
portantepeluse: optane drives, are you working with them? http://www.technologyreview.com/news/540411/intels-reinvention-of-the-hard-drive-could-make-all-kinds-of-computers-faster/15:31
vinshacoles: I'll keep you all well informed, I won't be able to get it going alone :)15:31
*** haomaiwang has quit IRC15:40
*** sanchitmalhotra has quit IRC15:40
*** dustins has quit IRC15:44
*** zul has joined #openstack-swift15:45
*** petertr7 is now known as petertr7_away15:49
*** sanchitmalhotra has joined #openstack-swift15:52
*** zul has quit IRC15:55
*** cebruns_ is now known as cebruns16:01
*** SkyRocknRoll has joined #openstack-swift16:08
*** amandap has quit IRC16:09
*** dustins has joined #openstack-swift16:09
*** SkyRocknRoll has quit IRC16:10
*** amandap has joined #openstack-swift16:12
*** SkyRocknRoll has joined #openstack-swift16:12
*** lyrrad has joined #openstack-swift16:17
*** gyee has joined #openstack-swift16:20
*** SkyRocknRoll has quit IRC16:21
*** lyrrad has quit IRC16:22
*** rledisez1 has quit IRC16:24
*** petertr7_away is now known as petertr716:24
*** lyrrad has joined #openstack-swift16:27
*** jistr has quit IRC16:30
*** jordanP has quit IRC16:30
notmynamemattoliverau: seems that there is a lot of desire (or at least interest) in ansible modules for deploying swift. is the stuff you've worked on public?16:30
wbhubernotmyname: that's what i have been hearing too.  chef seems to be running in the back mirror view of the ansible.  folks around here are suggesting ansible as the deployment automation tool.16:31
wbhuberbecause of the convenience and easy-to-create scripts using ansible16:32
*** thumpba has quit IRC16:32
notmynameyeah, I'd like to see some publicly available (and officially referenced in upstream docs) tools for ansible/chef/puppet/salt/etc. stuff to remove barriers for people to install/deploy swift16:33
*** petertr7 is now known as petertr7_away16:34
hrouwbhuber, notmyname  I've used this i nthe past: https://github.com/Open-I-Beam/swift-install, but I should check on the status.16:34
*** nadeem has joined #openstack-swift16:35
*** SkyRocknRoll has joined #openstack-swift16:35
jrichliI just asked around here, and we have some that we are using that are in a github, but it is probably not something for an "official" reference at this point.  I will find out about the plans, though.16:38
*** zul has joined #openstack-swift16:40
tdasilvanotmyname: https://github.com/matthewoliver/swift-ansible16:42
notmynamethanks16:42
tdasilvanotmyname: i'm planning to use that too for some tests i'd like to run here, so being able to setup a cluster and tear it down after tests is really key16:42
tdasilvanotmyname: mattoliverau added the ability to even specify a patch in case you want to test that16:43
notmynamecool16:45
*** zul has quit IRC16:47
*** zul has joined #openstack-swift16:49
*** mriedem has left #openstack-swift16:49
*** dustins has quit IRC16:52
*** thurloat is now known as thurloat_isgone16:54
*** thurloat_isgone is now known as thurloat16:54
*** dustins has joined #openstack-swift16:56
jith_hi all.. what all i should reset if my VM (SAIO setup) restarted... because when i start the services using swift-init main start.. it is getting hanged16:58
*** sanchitmalhotra has quit IRC17:00
*** sanchitmalhotra has joined #openstack-swift17:01
*** resker has joined #openstack-swift17:04
*** wbhuber is now known as wbhuber_17:05
*** petertr7_away is now known as petertr717:07
*** dbarman has joined #openstack-swift17:08
*** esker has quit IRC17:08
torgomaticpetertr7: I'd make sure your Swift is new enough to support container tempurls; it's a pretty recent feature17:10
petertr7torgomatic, Thanks a bunch. Unfortunately I'm on Juno =(17:12
torgomaticpetertr7: so I'm going to assume that you've verified the presence of the tempurl keys on the container via a HEAD request; the only other thing to check is that the object requested is within the container that has the keys17:14
*** geaaru has quit IRC17:14
torgomaticit's a scoping thing; account keys get you objects in the account, but container keys only get you objects in the container17:15
petertr7Hi torgomatic, I confirmed that indeed the container has the proper header ("X-Container-Meta-Temp-URL-Key")17:16
petertr7And the object is definitely in the container (deleted object, reuploaded it)17:16
acolestorgomatic: wasn't container tempurl new in kilo?17:19
torgomaticacoles: maybe? I have a hard time keeping track17:19
torgomaticwhat tag was juno again?17:19
acoles2.2.0 ?17:20
*** dbarman has quit IRC17:21
torgomatic2.2.0 doesn't have it but 2.3.0 does17:21
torgomaticnotmyname: what tag did we call "Juno"?17:22
*** resker has quit IRC17:22
acolesyup so says the changelog17:22
torgomaticand by "we" I mean "you"17:22
notmynametempurl was in 2.3.0 and 2.3.0 == kilo17:22
petertr7Ohh I see. Thanks for clearing this up everyone, much appreciated!17:22
*** zul has quit IRC17:23
torgomaticoh here we go, correlate these dates https://wiki.openstack.org/wiki/Releases with dates on the tagged commits, and it makes sense17:24
petertr7that's so well organized17:25
*** joeljwright has quit IRC17:30
*** hezhiqiang has joined #openstack-swift17:37
notmynamewe squeezed some swift stuff into the ops summit just now. questions about deployment and any issues therein17:38
notmynamefirst line on the etherpad is "swift is the most solid part of our openstack deployment+1+1"17:38
notmyname:-)17:38
egonThat's a great add, since we've got some operational comments about running it.17:39
*** kevinc_ has quit IRC17:42
openstackgerritSamuel Merritt proposed openstack/swift: Add OpenStack release names to changelog  https://review.openstack.org/21472817:44
mattoliveraunotmyname: yup my stuff is in 2 forms. 1 was merged and refactored into OSAD, and I still have a simpler version (tdasilva is referring to) which I have been maintaining which I use for my own test clusters.17:46
*** jordanP has joined #openstack-swift17:49
openstackgerritSamuel Merritt proposed openstack/swift: Add OpenStack release names to changelog  https://review.openstack.org/21472817:49
mattoliverauOSAD is used by Rackspace RPC and can be found here: https://github.com/stackforge/os-ansible-deployment17:50
mattoliverauThat does all of openstack including swift.17:51
mattoliverauNOTE: that OSAD is moving from stackforge to openstack if it hasn't already.17:51
*** breitz has quit IRC17:51
acolestorgomatic: for some reason i also struggle with ordering those release names :) number ordering i can do!17:52
*** breitz has joined #openstack-swift17:52
torgomatic:)17:52
mattoliverauThe simpler one I use, that tdasilva was talking about is: https://github.com/matthewoliver/swift-ansible it isn't feture complete as I've only been adding to it as I've needed it.17:53
*** ccavanna_ has joined #openstack-swift17:54
*** aix has quit IRC17:55
*** ccavanna has quit IRC17:57
*** brnelson has quit IRC17:57
*** brnelson has joined #openstack-swift17:58
*** dbarman has joined #openstack-swift18:03
*** janonymous has joined #openstack-swift18:04
*** kevinc_ has joined #openstack-swift18:04
*** annegentle has quit IRC18:04
*** acoles is now known as acoles_18:05
*** jordanP has quit IRC18:08
*** dbarman has quit IRC18:08
*** dbarman has joined #openstack-swift18:09
*** dbarman has quit IRC18:15
*** dbarman has joined #openstack-swift18:16
*** jith_ has quit IRC18:24
*** dbarman has quit IRC18:25
*** dbarman has joined #openstack-swift18:25
*** dbarman has quit IRC18:29
*** bapalm has quit IRC18:31
claygi like mattoliverau being around in the daytime18:32
*** bapalm has joined #openstack-swift18:32
*** dmorita has joined #openstack-swift18:36
*** dmorita has quit IRC18:36
peluseacoles_, scratch what I said earlier about that patch wrt data vs parity & shuffle.  Totally wrong and based on a bogus mental model of being able to tell a data node from a parity node via - that you can't do w/default shuffle mode but clearly the first 10 (whatever they are) in that case would be data.  I'll change the name of the var in the test...18:37
pelusevia node index that is... why did this keyboard skip a whole word?? :)18:37
claygpeluse: which test?  i'm looking at patch 212187 now18:42
patchbotclayg: https://review.openstack.org/#/c/212187/18:42
*** sanchitmalhotra1 has joined #openstack-swift18:46
*** esker has joined #openstack-swift18:46
peluseclayg, one that you wrote :)  one sec....18:48
*** sanchitmalhotra has quit IRC18:48
peluseclayg, test_GET_with_misplaced_frags() the name of 'handoff_node' should be 'parity_node'18:49
openstackgerritTim Burke proposed openstack/python-swiftclient: Drop flake8 ignores for already-passing tests  https://review.openstack.org/21475218:50
*** zul has joined #openstack-swift18:50
peluseclayg, acoles_, OK I'm changing my tune yet again on the statement that "the first ndata nodes from node_iter are data nodes even though tis shuffled" because the first ndata nodes on initial PUT will likely be different from a subsequent GET - yes??18:52
*** sanchitmalhotra1 has quit IRC18:52
claygpeluse: yeah I'm not sure I beleive that the first ndata nodes from the node_iter would be data nodes (vs. parity) - but does any code in the proxy really care?  it's all primaries to him...18:54
claygpeluse: acoles_: also, sorry my tests suck18:55
*** kevinc_ has quit IRC18:55
claygpeluse: so i've got a few things I'm going to clarify for myself before I push comments/diffs18:55
claygpeluse: acoles_ has some good fixups on there already I think - do you wanna push those first and then see if anything I have is still relevant?18:56
peluseclayg, the only 'thing' in the proxy that cares (sorta) is that a GET to all data will result in a concat in the EC lib instead of a rebuild.  A mix of data+parity will always require rebuild19:00
peluseclayg, sure to your last comment19:01
peluseclayg, so if EC didn't shuffle we'd get a free perf opt on GET19:01
claygpeluse: I think most people run with node_sort to timing?19:02
* peluse rememembers a patch somewere that someone proposed to add parms to policies and shuffle policy was one of them, wonder what hapened to that....19:02
claygpeluse: yeah we really need per-policy proxy app tunings like that :\19:02
peluseclayg, really?  I would have assumed the def (shuffle)19:02
claygpeluse: oh yeah maybe that's the *default*19:03
peluseclayg, I know there was a patch at one point.  WOuld be nice for EC to not shuffle since it buys us nothing19:03
peluseother than confusion :)19:03
claygpeluse: well... it spreads the load around the disks19:03
openstackgerritVictor Stinner proposed openstack/swift: pep8: fix warning F812  https://review.openstack.org/21349619:03
openstackgerritVictor Stinner proposed openstack/swift: pep8: replace deprecated calls to assert_()  https://review.openstack.org/21349119:03
openstackgerritVictor Stinner proposed openstack/swift: pep8: Don't override '_' symbol  https://review.openstack.org/21349519:03
openstackgerritVictor Stinner proposed openstack/swift: pep8: Fix usage of the l10n _('...') function  https://review.openstack.org/21349419:03
pelusespread shmed19:03
claygpeluse: i'd have to be a significant hit on cpu to be worth giving up all the other things the proxy is doing right19:04
claygpeluse: 100ms of latency waiting on a backend connection - or an extra stream on an already busy disk - is going to have a big impact - i'm don't know rebuilt vs. data conact?19:04
claygplus there's a ttfb vs overall throughput tradeoff19:05
openstackgerritVictor Stinner proposed openstack/swift: pep8: fix warning F812  https://review.openstack.org/21349619:05
openstackgerritVictor Stinner proposed openstack/swift: pep8: replace deprecated calls to assert_()  https://review.openstack.org/21349119:05
openstackgerritVictor Stinner proposed openstack/swift: pep8: Fix hacking H232 warnings (octal)  https://review.openstack.org/20614919:05
openstackgerritVictor Stinner proposed openstack/swift: pep8: Don't override '_' symbol  https://review.openstack.org/21349519:05
openstackgerritVictor Stinner proposed openstack/swift: pep8: Fix usage of the l10n _('...') function  https://review.openstack.org/21349419:05
claygpeluse: you can try doing different sorting - if we had sorting per policy it'd be interesting to add a "strict ring order" sorting (maybe?)19:06
claygpeluse: if you have a hot storage tier strict ring order + concurrent gets may do better at warming up the first primary of each part with the data for that part - leaving the other nodes more room to warm up their page cache with data from the other parts they are the primaries for19:07
haypocschwede: hi. i chose to write a patch serie because otherwise will conflict because all of the them modify the same line in tox.ini, the ignore= line19:08
haypocschwede: i modified my patch serie to remove rejected patches19:08
*** sanchitmalhotra has joined #openstack-swift19:08
peluseclayg, agreed19:08
*** annegentle has joined #openstack-swift19:13
*** esker has quit IRC19:16
*** silor has quit IRC19:16
peluseportante, I wish they'd tell us how to map marketing names of stuff they do press releases on to internal project names... there are a few things that PR could be about but it doesn't have enough detail (or the internal codename) for me to tell :)19:26
*** hezhiqiang has quit IRC19:38
*** petertr7 is now known as petertr7_away19:41
*** petertr7_away is now known as petertr719:41
*** mahatic has quit IRC19:42
*** gyee has quit IRC19:47
*** esker has joined #openstack-swift19:50
*** dbarman has joined #openstack-swift19:52
*** esker has quit IRC19:54
*** esker has joined #openstack-swift19:55
*** gyee has joined #openstack-swift19:56
*** alejandrito has joined #openstack-swift19:59
*** annegentle has quit IRC19:59
*** alejandrito_ has joined #openstack-swift20:00
*** alejandrito has quit IRC20:00
*** thurloat is now known as thurloat_isgone20:05
*** alejandrito_ has quit IRC20:18
openstackgerritpaul luse proposed openstack/swift: EC GET path: require fragments to be of same set  https://review.openstack.org/21218720:24
*** janonymous has quit IRC20:25
*** SkyRocknRoll has quit IRC20:28
*** mahatic has joined #openstack-swift20:30
*** mahatic has quit IRC20:31
*** robefran has quit IRC20:32
*** blmartin_ has quit IRC20:32
openstackgerritpaul luse proposed openstack/swift: EC GET path: support use of alternate fragments on object servers  https://review.openstack.org/21314720:34
*** petertr7 is now known as petertr7_away20:34
*** petertr7_away is now known as petertr720:37
*** annegentle has joined #openstack-swift20:45
notmynameswift team meeting in 15 minutes.20:45
mattoliveraunotmyname: peluse and I are in a meeting20:46
notmynameack20:46
*** ho has joined #openstack-swift20:46
claygneat20:46
notmynameI think this seems to be mostly a summary of the hackathon, and also ho has a topic he proposed20:46
*** aerwin has joined #openstack-swift20:47
hogood morning!20:48
aerwino/20:50
pelusemattoliverau, but only one meeting :)  there's room for at least one other20:50
*** dustins has quit IRC20:50
mattoliveraulol, true20:50
*** annegentle has quit IRC20:53
*** ccavanna_ has quit IRC20:53
*** mjfork has joined #openstack-swift20:53
*** annegentle has joined #openstack-swift20:54
*** mahatic has joined #openstack-swift20:54
mjforkI am debugging long running requests and am seeing GET requests fail with 20s timeouts talking to the container servers.  What would cause a get to go to a container server?20:55
*** blmartin has joined #openstack-swift20:56
*** acoles_ is now known as acoles20:57
ctennisI think it makes an initial request to determine ACL settings if you have the rights to read the object20:58
ctennisit should then cache it in memcache for a period of time20:58
*** esker has quit IRC20:58
mattoliveraupeluse: just in time for the swift meeting20:59
notmynamemattoliverau: wait, you're already done with your meeting?20:59
notmynamethat was fast20:59
mattoliverauwell it helps when intel and rackspace (peluse and I) had the same list :)20:59
notmynamewonder how that happened ;-)21:00
*** zul has quit IRC21:00
notmynameok, meeting time21:00
mattoliveraugood communication within the swift communuty21:00
notmynameexactly!21:00
*** barker has joined #openstack-swift21:01
*** petertr7 is now known as petertr7_away21:07
acolespeluse: sorry i didnt get to the second patch, alt frags, will do tomorrow21:08
acolespeluse: had to go walk the dog!21:08
*** hezhiqiang has joined #openstack-swift21:09
*** hezhiqiang has quit IRC21:14
*** robefran has joined #openstack-swift21:15
*** blmartin_ has joined #openstack-swift21:15
*** blmartin has quit IRC21:18
*** hrou has quit IRC21:20
*** jrichli has quit IRC21:26
*** jrichli has joined #openstack-swift21:26
peluseacoles, heh, thanks!!!21:27
*** barker has quit IRC21:37
*** nadeem has quit IRC21:38
*** nadeem has joined #openstack-swift21:39
*** nadeem has quit IRC21:39
*** nadeem has joined #openstack-swift21:40
openstackgerritTim Burke proposed openstack/python-swiftclient: Drop flake8 ignores for already-passing tests  https://review.openstack.org/21475221:55
claygredbo: yeah per-policy constraints would be pretty safe/sane I think21:57
redbothat would probably be the easiest solution21:57
*** mahatic has quit IRC21:58
homattoliverau: could you check patch 138342?21:58
patchbotho: https://review.openstack.org/#/c/138342/21:58
jrichlinotmyname: awe, you didn't say the ending phrase.21:59
*** acoles is now known as acoles_21:59
*** dbarman has quit IRC21:59
*** blmartin_ has quit IRC21:59
notmynamejrichli: I did22:00
notmynamejrichli: ah, I didn't it was in my buffer, but then I said somethign else :-)22:00
jrichli:-)  at least I know you are still feeling thankful!22:01
hotoday i overslept so i parked my car in front of the office. i have to move it to right place before colleagues come to here ;-)22:02
*** esker has joined #openstack-swift22:03
* notmyname closes his laptop to get back to the ops summit22:04
*** hrou has joined #openstack-swift22:04
*** resker has joined #openstack-swift22:07
*** resker has quit IRC22:08
*** esker has quit IRC22:09
*** tonyb has joined #openstack-swift22:10
*** annegentle has quit IRC22:17
*** jrichli has quit IRC22:18
*** esker has joined #openstack-swift22:21
claygpeluse: wow, test_GET_with_mismatch_etag is a fair bit more readable this go round - thanks!22:28
*** sanchitmalhotra1 has joined #openstack-swift22:28
*** sanchitmalhotra has quit IRC22:30
*** wbhuber_ is now known as wbhuber22:34
*** esker has quit IRC22:54
*** jlhinson has quit IRC22:54
*** esker has joined #openstack-swift22:54
*** NM has quit IRC22:55
*** lyrrad_ has joined #openstack-swift22:58
*** lyrrad has quit IRC22:59
*** lyrrad_ is now known as lyrrad22:59
*** bill_az_ has joined #openstack-swift23:00
*** bill_az has quit IRC23:01
*** km has joined #openstack-swift23:02
*** lcurtis has quit IRC23:04
*** zul has joined #openstack-swift23:06
*** zul has quit IRC23:12
claygso if someone sends a request with if-match: not-the-etag how many nodes do we think we should hit before we give up?23:12
torgomaticclayg: one that doesn't 404?23:13
claygI think if we get get a 416 (range not satisfiable) we return it immediately - but if we get a 412 - we'll keep trying until we exahust the node iter23:13
torgomaticwell, that's unfortunate23:13
claygtorgomatic: is it?  i'm not really sure what's the expected behavior23:14
claygtorgomatic: like if someone is trying to do some sort of optomistic overwrite protection maybe trying more nodes is a good idea?23:14
torgomaticclayg: I mean, if the proxy learns that the object (a) exists and (b) this copy doesn't match, that's good enough to return early IMO23:14
claygtorgomatic: yeah there has to be some diminishing returns, after you get back one or two 412's23:15
claygthe behavior is sort of insane with EC, the resumming getters just go go go!  I think the fake ring limits my test cases requests to "only" 2823:16
claygI'm not sure 2 x replicas was really ever what anyone wanted - I think someone wanted 6 handoffs and they just happened to think "hey that's twice as many as my replica count!  maybe that's useful" and then it turned out for replica counts != 3 it was not useful :'(23:18
torgomaticyeah, the goal was enough nodes for read-after-write consistency with new objects; 2*primaries is definitely overdoing it for EC23:19
claygtorgomatic: so request_node_count is the total number of nodes, not the number of handoffs?23:22
torgomaticclayg: I think so?23:22
claygyeah i guess it is23:22
*** kei_yama has joined #openstack-swift23:25
*** chlong has quit IRC23:28
*** aerwin has quit IRC23:29
*** nadeem has quit IRC23:31
*** dbarman has joined #openstack-swift23:35
claygpeluse: bah, so I was convinced that the handling of bad requests was suboptimal with your change and rewrote a bunch of the handling in when iterating the response pile to break when len(bad_responses) >= min_gets23:39
claygI wrote some tests and not only did it work out what you were doing was fine (because you only spawn when 200's >= num_gets) - but my code ended up making an extra request if you only get 9 out of 10 bad_responses23:39
claygso it was basically *exactly* the opposite of what I set out to prove; you were right, i was wrong, your code was better, my code stunk :'(23:40
*** zul has joined #openstack-swift23:41
claygstill I'd bet getting ndata 416's is almost never needed23:42
*** barker has joined #openstack-swift23:54
*** sanchitmalhotra has joined #openstack-swift23:58

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