Tuesday, 2015-07-21

peluseoh, is that what that is for??00:00
torgomaticyep00:00
pelusethen its not duplicated code and both etag related code snippets are needed00:00
torgomaticotherwise you could get something that's either an FA from a different object, or in replicated-land, just a different object00:00
torgomaticyep, that's important00:00
torgomaticand confusing00:00
peluseyeah, that would suck a little00:00
* torgomatic is going to go put a comment on it00:01
peluseOK, so that's the etag_buckets thing in the _get_or_head_response() in my patch...00:01
pelusethe rest of the patch is about having the storage node communicate back other FIs that are available besides the one it has and then having the GET path circle back and try again using those if it doesn't have enough (in one etag bucket of course)00:02
peluseappreciate if you guys can take a gander.  the test mods to make it work had me hacking like a fool so it could be cleaned up a little for sure but right now it works w/the limited new test code that I added00:02
pelusealso added one property in diskfile that I don't really like as it required a change to mem_diskfile but was the quickest way I could see to plumb the alternate info back up the stack00:03
claygpeluse: so how far does it go past primaries into handoffs before circling back to primaries it through out?00:03
openstackgerritSamuel Merritt proposed openstack/swift: Add comment about ResumingGetter.used_source_etag  https://review.openstack.org/20387700:04
claygpeluse: what are the best new tests?00:04
peluseone sec...00:04
claygtorgomatic: so what if the resumer on EC ends up picking a node that has a duplicate fi (one that's already streaming from another node?)00:05
torgomaticclayg: everything fails horribly00:06
torgomaticI think you may have anticipated that answer ;)00:06
peluseclayg, wrt the how far question, the resumingGetter will go through the node_iter assuming its getting 404's until its exhausted.  then _get_or_head_response() will say "hey, I don't have enough but there are some nodes I talked to that have other FI's, let me try those" and a new node_iter with just those is used for anoter round of GETs00:06
claygtorgomatic: I think we picked the wrong set of failures to punt on00:06
torgomaticclayg: not the wrong set, just a subset of what it needs to be00:06
peluseheh, and the wrong day to stop sniffing glue00:06
*** nadeem has quit IRC00:07
torgomaticfor the specific case of resuming, we need to make sure it's the same etag *and* some other stuff00:07
*** DericHorn-HP has joined #openstack-swift00:07
torgomaticwhere "other stuff" is nothing for replication, but something for EC00:07
pelusethe new probe test for the etag_buckets thing is either from you or bill huber, not sure.  its TestECObjectHandoffOverwrite and is just basic right now but does exercise the etag_bucket idea well00:07
torgomaticif we get a different source etag, then it's no good, FIs, FAs, ECs, and PDQs notwithstanding00:07
pelusethe basic test for the alternate index thing is called test_alt_fragments_ok() and just tests one scenario now00:08
*** thurloat is now known as thurloat_isgone00:09
claygpeluse: it's a new test?00:11
claygin proxy.controllers.test_obj?00:11
torgomaticclayg: it's in the patch he referenced, yeah00:12
pelusetest_server.py class TestECMismatchedFA()00:12
claygpeluse: k, got it00:14
peluseclayg, once you read that test... I was thinking about a func to genercize shuffling the FA's around and feeding it various scenarios.. with GETs in between00:14
torgomaticyeah, a test helper for that would probably be useful, because we're gonna have a bunch of these00:15
peluseyup00:15
peluseI was more concerned about getting just one to work to start with :)00:15
claygyeah that'd be pretty great - although I think doing it in proxy test_server talking to real object-server's is a both a) heavy-handed b) harder to extend to different ec-schemes00:15
torgomaticsame etag, new FI; same etag, repeated FI; different etag...00:15
torgomaticmaybe it's not actually that many00:15
claygit'd be easier to do the generalization in test.proxy.controller.test_obj00:15
claygimho00:15
* peluse likes heavy handed shit :)00:16
peluseplus I'm not the test master that you are :):)00:16
claygpeluse: - yeah torgomatic too00:16
* peluse can barely mock his way out of a paper bag00:16
claygheh obj4_ring_path - maybe it's *not* that hard to add new scenarios - it's like proxy.test_server is slow already or anything00:17
claygs/it's like/it's not like/g00:17
peluseyeah, I needed more devices to setup a decent scenario and chaning the 3rd was going to involve a shitpile of other changes to unrelated tests00:18
clayg... yup00:18
peluseand I tell ya, at first I didn't make unique dev IDs on the ring and oh boy was that fun to debug in new test code...00:20
clayglol00:20
peluseI was like WTF?  How do I have primary nodes that are also handoffs???00:20
*** gyee has quit IRC00:20
*** chlong has joined #openstack-swift00:21
pelusehey I gotta run next door to the grocery store or my family wont have dinner tonight (I feed them every other night and tonight is bread *and* water) so I'll be back in 30-40 min....00:22
claygpeluse: I'd really like to see the new code in proxy.controllers.obj broken out into a few methods00:23
*** dmorita has joined #openstack-swift00:31
*** DericHorn-HP has quit IRC00:33
*** DericHorn-HP has joined #openstack-swift00:35
*** DericHorn-HP has quit IRC00:35
peluseclayg, can do... did you have something specific in mind or just less hacky?00:53
claygpeluse: heh - anything to break it up really00:54
peluseno problema00:55
peluseclayg, your contribution sugestion in the comments would be HUMONGOUS!00:56
claygpeluse: yeah - i'll work on that00:58
peluseand thanks for the quick comments too...01:02
claygpeluse: might help the next guy navigate the change too01:03
claygpeluse: oh... on second though I shouldn't have scored it - now probably no one will look at it till you push a new change?01:03
peluseyeah so thanks for nuthin' :)01:04
claygikr01:04
clayg:'(01:05
*** ccavanna has joined #openstack-swift01:14
*** haomaiwang has quit IRC01:24
*** bitblt has quit IRC01:29
*** kota_ has joined #openstack-swift01:40
*** ChanServ sets mode: +v kota_01:40
*** jasondotstar has joined #openstack-swift01:45
openstackgerritMatthew Oliver proposed openstack/swift: Add container and account reverse listings  https://review.openstack.org/12070902:43
*** jasondotstar has quit IRC02:47
*** barker has joined #openstack-swift03:05
*** mahatic has joined #openstack-swift03:05
*** sanchitmalhotra has joined #openstack-swift03:13
*** barker has quit IRC03:20
*** mahatic has quit IRC03:29
*** barker has joined #openstack-swift03:30
openstackgerritCarlos Cavanna proposed openstack/swift: Improving statistics sent to Graphite.  https://review.openstack.org/20265703:46
*** barker has quit IRC03:57
*** pbourke has quit IRC03:57
*** pbourke has joined #openstack-swift03:57
*** sanchitmalhotra1 has joined #openstack-swift04:00
*** sanchitmalhotra has quit IRC04:03
*** sanchitmalhotra has joined #openstack-swift04:03
*** annegent_ has joined #openstack-swift04:04
*** sanchitmalhotra1 has quit IRC04:05
*** annegentl_ has quit IRC04:07
*** sanchitmalhotra1 has joined #openstack-swift04:10
*** sanchitmalhotra has quit IRC04:12
openstackgerritMatthew Oliver proposed openstack/swift: Add container and account reverse listings  https://review.openstack.org/12070904:39
jith_hi all.. what is swift_store_key in configuring swift for glance backend... is it password for swift user??04:49
*** zaitcev has quit IRC05:07
*** hrou has quit IRC05:59
*** Kennan has quit IRC06:01
*** Kennan has joined #openstack-swift06:02
*** kota_ has quit IRC06:06
*** ho has joined #openstack-swift06:09
mattoliveraujith_: sorry I'm not sure, I haven't set it up. I'll have to go read the glace documentation.06:17
hoacoles_away, donagh: around?06:34
openstackgerritMerged openstack/swift: Add comment about ResumingGetter.used_source_etag  https://review.openstack.org/20387706:34
*** hseipp has joined #openstack-swift07:05
jith_mattoliverau: its ok.. thanks07:08
*** losingle has joined #openstack-swift07:30
mattoliveraujith_: swift_store_key is the key (password) of the swift user glace is using to connect to swift.07:34
mattoliveraujith_: http://docs.openstack.org/developer/glance/configuring.html#configuring-the-swift-storage-backend07:34
jith_mattoliverau: thanks a lot... Another doubt swift_store_auth_address is the the address of proxy layer which accepts connection right?? Inside proxy conf file i have mentioned the keystone authentication.... means the user of swift should get authenticated with keystone... so should i specify the direct keystone auth adddress or swift proxy address in swift_store_auth_address? sorry for the...07:38
jith_...trouble :)07:38
mattoliveraujith_: that's ok, I work with a glance core, but he is in a different timezone, so I can ask him or introduce you some other time. I haven't set it up before, but looks like you can set it to keystone if thats what your using for swift authentication. https://www.rdoproject.org/forum/discussion/252/use-swift-as-backend-for-glance/p107:45
*** jordanP has joined #openstack-swift07:50
*** losingle has quit IRC07:52
*** jistr has joined #openstack-swift07:55
jith_mattoliverau: thanks a lot.. sure.. sorry for late reply08:01
*** chlong has quit IRC08:04
*** wbhuber_ has quit IRC08:16
*** 20WABQBTM has joined #openstack-swift08:37
*** 20WABQBTM has quit IRC08:37
*** haomaiwang has joined #openstack-swift08:37
*** aix has joined #openstack-swift08:43
*** aix has quit IRC08:58
*** rvasilets__ has joined #openstack-swift09:09
*** aix has joined #openstack-swift09:28
*** Kennan has quit IRC10:02
*** Kennan has joined #openstack-swift10:03
*** aix has quit IRC10:04
*** aix has joined #openstack-swift10:15
*** chmouel_ is now known as chmouel10:25
hoacoles_away, donagh: around?10:44
*** silor has joined #openstack-swift10:50
*** dmorita has quit IRC10:59
*** silor has quit IRC11:07
*** rvasilets__ has quit IRC11:34
*** sanchitmalhotra1 has quit IRC11:35
openstackgerritHisashi Osanai proposed openstack/swift: Remove _keystone_identity method  https://review.openstack.org/20405012:08
*** silor has joined #openstack-swift12:10
*** robefran has quit IRC12:11
*** silor1 has joined #openstack-swift12:15
*** peterbusque has joined #openstack-swift12:15
*** chlong has joined #openstack-swift12:17
*** silor has quit IRC12:18
*** silor1 is now known as silor12:18
*** SkyRocknRoll has joined #openstack-swift12:25
*** barker has joined #openstack-swift12:25
*** barker has quit IRC12:27
*** km has quit IRC12:29
*** ho has quit IRC12:34
*** robefran has joined #openstack-swift12:43
*** kei_yama has quit IRC12:55
*** annegentl_ has joined #openstack-swift13:04
*** annegent_ has quit IRC13:06
*** tsg has joined #openstack-swift13:13
*** hrou has joined #openstack-swift13:18
*** SkyRocknRoll has quit IRC13:20
*** wbhuber has joined #openstack-swift13:22
*** janonymous has joined #openstack-swift13:22
*** ccavanna has quit IRC13:38
*** pbourke has quit IRC13:39
*** annegentl_ has quit IRC13:39
*** peterbusque has quit IRC13:50
*** rbrooker has joined #openstack-swift13:50
*** peterbusque has joined #openstack-swift13:50
openstackgerritjanonymous proposed openstack/swift: unit tests: Replace "self.assert_" by "self.assertTrue"  https://review.openstack.org/20409213:56
*** tongli has joined #openstack-swift13:56
openstackgerritjanonymous proposed openstack/swift: test/(functional, probe): Replace "self.assert_" by "self.assertTrue"  https://review.openstack.org/20409313:58
*** hrou has quit IRC14:00
*** breitz has quit IRC14:06
*** breitz has joined #openstack-swift14:06
*** amoturi has joined #openstack-swift14:12
*** jasondotstar has joined #openstack-swift14:13
*** hrou has joined #openstack-swift14:16
*** ccavanna has joined #openstack-swift14:16
*** jrichli has joined #openstack-swift14:22
*** jlhinson has joined #openstack-swift14:24
*** jkugel has joined #openstack-swift14:26
tdasilvagood morning14:29
*** david-lyle has quit IRC14:30
janonymousHi Folks, I had a small query that discussed it  on openstack-dev also, but through the response i am only able to understand a small part of it :14:33
janonymousMy Question is simple the jenkins gate jobs produce a neat testr_results.html.gz  of the failures through which it is very easy to track the problem like : http://logs.openstack.org/66/193866/10/check/gate-keystone-python27/bcfc010/ ; but in swift no such thing is present14:33
janonymousI think the answer lies in : http://git.openstack.org/cgit/openstack-infra/project-config/tree/jenkins/jobs/swift.yaml  ;     publishers:       - devstack-logs       - console-log14:34
janonymouswhich has an additional     - test-results  parameter in publisher : http://git.openstack.org/cgit/openstack-infra/project-config/tree/jenkins/jobs/keystone.yaml14:35
openstackgerritCarlos Cavanna proposed openstack/swift: Improving statistics sent to Graphite.  https://review.openstack.org/20265714:35
janonymousCould someone help me out on this...14:35
*** rbrooker has quit IRC14:37
*** annegentle has joined #openstack-swift14:37
openstackgerritpaul luse proposed openstack/swift: Add ability for GET path to see/select alternate frag archs  https://review.openstack.org/20128314:41
*** lpabon has joined #openstack-swift14:44
*** admin6 has joined #openstack-swift14:45
pelusejamielennox, I can try... taking a look now14:45
pelusehmmm, why are you asking in the swift channel if I may ask?14:48
pelusejanonymous, those last 2 comments were for you :)14:49
janonymousOhh.. :)14:49
janonymousi asked it on dev ... and the that's the answer i got14:50
janonymousso thought someone could answer here...14:50
*** wbhuber_ has joined #openstack-swift15:00
*** robefran has quit IRC15:04
*** hrou has quit IRC15:04
*** minwoob has joined #openstack-swift15:05
*** robefran has joined #openstack-swift15:06
*** wbhuber has quit IRC15:09
*** chlong has quit IRC15:09
*** wer has quit IRC15:09
*** jamielennox has quit IRC15:09
*** CrackerJackMack has quit IRC15:09
*** briancline has quit IRC15:09
*** sudorandom has quit IRC15:09
*** wbhuber_ is now known as wbhuber15:10
janonymouspeluse: Did you had a look ?15:10
*** proteusguy has quit IRC15:11
*** chlong has joined #openstack-swift15:15
admin6Hi all. I’m planning a swift deployment and currently trying to design the way I’ll store my objects into Swift.  Something not clear for me is how swift manage concurrent write access to a container under heavy load, between write lock into sqllite and replication between container nodes… Is there a documentation regarding this specific behavior?15:23
*** proteusguy has joined #openstack-swift15:26
*** thebloggu has joined #openstack-swift15:30
theblogguhas anyone here ever tried to run a swift aio in docker for tests? how can I use xfs inside the container (to support extended attributes)?15:32
*** hrou has joined #openstack-swift15:36
*** david-lyle has joined #openstack-swift15:38
chmouelthebloggu: i don't the answer but docker -v would just bind mount whatever filesystem you have15:40
chmouelunless you have your docker running on AUFS (default ubuntu i think) then you can't15:40
*** joeljwright has joined #openstack-swift15:43
*** ChanServ sets mode: +v joeljwright15:43
theblogguchmouel, right, so I should just mount an xfs filesystem with -v? isn't it possible to have a non persistent option?15:44
chmouelthebloggu: I think as long your /var/lib/docker is using the dm-lvm docker's driver then it *should* work15:45
theblogguchmouel, according to `docker info` it's using: `Storage Driver: devicemapper`. I'm asking this because I was using swift earlier and got a "No data available" when I tried to read an objects metadata (manually, in the swift node) and I thought the problem could be not having support for extended attributes in the filesystem (even though PUT/GET requests of objects to swift work without a problem, even with custom metadata)15:51
*** mfalatic has joined #openstack-swift15:56
clayghas anyone looked seriously at the per-device-rsync-modules?15:57
claygis the repliation version of swifterdarrell's server-per-disk15:57
claygI don't know where the patch is15:57
claygpeluse: k, i'm spinning up your ec GET fix now - gunna see what I can with a test15:59
*** annegentle has quit IRC15:59
*** nadeem has joined #openstack-swift16:02
*** nadeem has quit IRC16:02
*** nadeem has joined #openstack-swift16:03
*** jistr has quit IRC16:04
admin6I’m trying to design my future swift cluster. I have between 300.000  and 700.000 new files written every day (without counting read access to the objects). Do you think it’s reasonable regarding to concurrent access to the container sqlite file to create one container per day to store all my file?16:08
*** gyee has joined #openstack-swift16:08
claygadmin6: yeah one container per day would be fine16:13
*** peterbusque has quit IRC16:13
claygadmin6: do you have that kind of temporal knowledge when accessing the object?16:13
ccavannaclayg: I'll propose the documentation change we talked about yesterday in openstack-infra.16:13
*** peterbusque has joined #openstack-swift16:14
claygccavanna: the developer docs are in the swift tree16:14
claygccavanna: the swift all in one docs are something we "maintain"16:14
claygccavanna: where "maintain" ~= "trick people new to the project into helping us with"16:14
notmynamegood morning, world16:14
admin6clayg: temporal knowledge is not very important for me. my main concern is about concurrent write access to the container sqlite database16:15
ccavannaclayg: I fall into that category, perfectly :)16:15
ccavannaI think the change belongs to this page: http://docs.openstack.org/infra/manual/developers.html16:15
ccavannaBut I didn't see the doc for that under swift.16:15
claygadmin6: well why not do a hash ring?16:15
*** peterbusque has quit IRC16:15
*** peterbusque has joined #openstack-swift16:16
claygadmin6: concurrent write access to a single container is pretty solid to the tune of 100's per second16:17
claygare these half-million objects coming into a single contaier *all at once* or do they trickle in over the day?16:17
*** lpabon has quit IRC16:17
admin6clayg: its all over the day, with peak at some hours16:18
claygthe thing with multiple containers it that as they get.... idk ~4M replication can get pretty annoying16:18
claygadmin6: this helps speed out the occassional .pending eating slowdown during the object write path -> https://review.openstack.org/#/c/189080/16:19
admin6good to hear that I can tune up to 100 write per second on a single container16:20
claygadmin6: yeah the trickier part there is getting enough concurrency in the guys doing the uploads - and enough object disks to support all those iops - the containers may not be what limits you depending on the size of your cluster?16:21
claygccavanna: oh yeah - that page isn't us16:22
admin6clayg: ok, my cluster will start with about 400TB of data ans 600 Millions of objects16:23
claygadmin6: that's a great cluster!  congradulations!16:24
admin6clayg: one thing which is still not clear to me is how sql write to the container file and swift recplicas between the continers nodes works together.16:25
*** mgarza has joined #openstack-swift16:25
claygadmin6: is that 4 nodes 24 disks or so?16:26
claygadmin6: you know... container replication is kinda tricky... it's acctually one of the smarter parts of swift IMHO16:26
*** geaaru has joined #openstack-swift16:27
admin6clayg: I’m confident :-)16:27
claygadmin6: there's a bunch of tricks in there - but at the end of the day it goes row by row to make sure each replica for the container has the latest transaction for every object16:27
admin6clayg:… ok, never read that anywhere16:29
notmynameadmin6: clayg gives a good summary of http://docs.openstack.org/developer/swift/overview_replication.html#db-replication16:30
ccavannaclayg: unless you think it belongs somewhere else. But that page seemed appropriate because it documents the steps for checking in/out code, which led to my problem with the tools.16:30
notmynameccavanna: that page you linked is a great place for stuff that generally applies to all openstack projects. for stuff that's swift-specific, it's good to keep that in the swift source tree16:31
admin6All: thanks guys for your very expert answers (as always). I’ll dig deeper into that and will be back soon ;-)16:34
*** david-lyle has quit IRC16:34
claygnotmyname: oh that's a really great summary, i didn't know we had that!16:36
ccavannanotmyname: I didn't find any doc page in swift that deals with this. Maybe I can create a new section under: http://docs.openstack.org/developer/swift/development_guidelines.html16:36
notmynameccavanna: can you remind me what "this" is? ;-)16:37
hrouccavanna: I think the issues you ran into were not swift specific and could apply to other components ? So that's probably a good place;  Actually I was setting up a new VM this morning, followed SAIO instructions verbatim, and all tests (i.e. unit/probe/func) were 100% clean after (recent Ubuntu release).16:37
notmynamedfg_: ^ ;-)16:37
claygnotmyname: in fairness the saio docs start with "get a trusty vm"16:37
ccavannanotmyname: oh, right :). the issue was that after I rebased my changes, the swift scripts (such as swift-init) were out of sync with my code.16:38
notmynameclayg: what if I haven't spent that much time with the VM and dont' trust it yet?16:38
clayghrou: ok, now it again only this time with precise - and post the errors ;)16:38
ccavannaAnd I was not able to start swift because the version of swift required (swift==2.3.1.dev33) did not match my version of swift (swift==2.3.1.dev34)16:39
notmynameccavanna: ah, yeah. that's something that's general to openstack (ie anything using pbp/pip/setuptools and distro packages). probably would be good to document generally as a hint on how to solve it16:39
notmynameccavanna: IIRC16:39
*** admin6 has quit IRC16:39
hrouclayg: ; - )  I agree though when I've had issues before it generally comes down to which Ubuntu release (or release of OS ** blah **) you use.16:39
clayghrou: it's hard to keep a living document like that up-to-date for multiple distros :\16:40
hrouclayg:  Yea I can definitely see why that's a big pain!16:40
ccavannanotmyname: So I was thinking http://docs.openstack.org/infra/manual/developers.html16:40
ccavannaThat's where more or less this belongs. I can mention my case with Swift as an example.16:41
claygccavanna: worth a shot!16:41
notmynameccavanna: yeah, or maybe on http://docs.openstack.org/infra/manual/python.html#python-unit-tests (which I found linked on the "run unit tests" section of the doc you linked16:43
claygccavanna: if that doesn't work out for you (seriously good luck) - maybe a section that duplicates some of the "making your first change" part of that document in the swift developer docs - maybe the development guidelines should just a be a "developer guide" or something?16:43
*** vinsh has quit IRC16:46
*** vinsh has joined #openstack-swift16:46
*** jlhinson_ has joined #openstack-swift16:46
*** jlhinson has quit IRC16:46
ccavannaclayg: actually, I like that more. I'm not a big fan of duplicating documentation, but the advantage for Swift would be that everything will be in one place.16:48
*** david-lyle has joined #openstack-swift16:48
ccavannaIf you think that's more appropriate, I can easily make the changes to the Swift doc and propose it.16:49
notmynameccavanna: honestly, I don't think it matters where it is. what matters more is that it's available for new people coming in who might be hit with the problem.16:50
notmynameyou've got great experience there since you're relatively new to swift16:50
notmynameif you'd be more likely to look in the infra manuals (because of existing links/docs), then let's put it there. if you look to the in-tree swift docs first, let's put it there16:51
notmynameccavanna: so i think you've probably got a better sense of where to put it for new contributors than clayg or me (since we've been breathing swift for nearly 6 years) ;-)16:52
klrmnccavanna: both? =)16:52
notmynameklrmn: I'm ok with that too :-)16:52
*** vinsh has quit IRC16:52
ccavannaPersonally, I would have looked in Swift first, under Getting Started, in the Development section.16:55
ccavannaI can create a new topic, "Making your first change" or "Making your first contribution".16:55
*** jasondotstar has quit IRC16:56
openstackgerritClay Gerrard proposed openstack/swift: Fix Associated Projects link on Getting Started  https://review.openstack.org/20416716:58
notmynameclayg: what version of sphinx do you have installed?17:01
notmynameugh. distro packages vs pip strikes again? I had python-sphinx installed. got an error building docs. removed it (with apt-get), now it works. but I don't see sphinx in dpkg or pip freeze!17:06
notmyname*magic*17:06
claygnotmyname: vagrant-swift-all-in-one has an autodoc command - it's *magic*17:07
notmynameyeah, it's pretty sweet17:07
notmynamethat alone might make me start using vSAIO17:07
claygoslosphinx==2.5.017:07
claygSphinx==1.1.317:07
notmynameyeah, i've got oslosphinx, just not plain sphinx17:08
claygnotmyname: better install it!17:08
notmynamewhy? it works without it17:08
notmyname;-)17:08
clayglol!17:08
*** vinsh has joined #openstack-swift17:08
*** jordanP has quit IRC17:09
hrouFunny enough all the issues I've had also always come down to distro packages vs pip (e.g. when I was installing an older version of swift on a recent release), fixing said issues is an art form I find, it can be mediating ; )17:11
vinshHello swift.  Anyone have hints for me on the following? when I try to list a specific container... from many different clients.. I always get the following failure "simplejson.scanner.JSONDecodeError: Expecting value: line 1 column 1 (char 0)"17:11
vinshWondered if that was something obvious you could point me at to look into.17:11
notmynamevinsh: what's the request you are making? can you pastebin an example?17:12
vinshYes. One sec.17:12
vinshhttp://paste.openstack.org/show/396356/17:12
vinshOther containers in that tenant are fine.. something happened to this container (don't know what).  and now it bombs out.17:13
notmynameI wonder if there are some weird object names in that container17:13
vinshIn a proxy log you see a 200 from the request.17:13
vinshThis is a container the monasca guys are feeding stuff into.. so that's possible :)17:14
vinshI'm just unsure of a way to recover it or even look further.17:14
notmynamevinsh: do `swift --debug list OpenStackMetrics` and pastebin that (scrub tokens, if necessary)17:15
*** jasondotstar has joined #openstack-swift17:16
*** lpabon has joined #openstack-swift17:17
vinshgood idea... http://paste.openstack.org/show/396366/17:17
ccavannanotmyname: Can I ask you a question about some tests?17:18
notmynamevinsh: oh, interesting17:19
claygis that.... html?17:19
notmynamevinsh: first, see line 19. that's the equivalent curl request17:19
claygi have to admit - if *i* was a json parser I would also blow up on html17:19
vinshhah!17:19
vinshwhy is it sending me html today?17:20
notmynamevinsh: second (and to the problem), looks like it might be a contaienr with staticweb enabled?17:20
vinshOH...17:20
claygnotmyname: in tree static web will respect the accept-encoding or json query params17:20
notmynamewhich, honestly sounds like a bug in our client if it can't list staticweb containers17:20
notmynameclayg: yeah...but the pastebin...17:20
notmynameccavanna: of course17:20
claygnotmyname: it's a bug in the middleware if format=json returns html17:21
notmynameyeah, I thought staticweb ignored the staticweb part if a token is in the request (unless there is also x-web-mode: true)17:22
vinshHow can I check if static web is enabled on this container?17:22
claygstat -v17:22
vinshoh. -v. thanks17:22
clayghonestly i don't see it in the debug response headers17:22
notmynameclayg: doesn't staticweb filter that out for the auto-gen'd listings?17:23
vinshYeah, nothing listed17:23
notmynameoh ok17:23
*** aix has quit IRC17:23
notmynamewow. pip is up to version 7.1.0. I had 1.5.6 installed17:25
claygnotmyname: version *7* - i just installed 6 - what are these fools doing!?17:25
claygvinsh: i'm not 100% that html is totally stock staticweb - can you double check your pipeline?17:26
vinshwhat do you mean by that? The proxy node middleware pipeline?17:26
vinsh[filter:staticweb]17:27
vinshuse = egg:swift#staticweb17:27
vinshpipeline = catch_errors healthcheck proxy-logging cache ratelimit formpost tempurl authtoken staticweb slo keystone proxy-server17:27
claygvinsh: weird17:28
notmynameclayg: are you trying it locally yet? I'm in the middle of running some testins locally17:28
notmynametestins? what's that17:28
claygnotmyname: sigh - no :'(  but ok17:28
notmynameI can, but it will be a few minutes17:28
vinshclayg: The problem container shows Content-Type: text/html; charset=UTF-8 where as other containers show Content-Type: text/plain; charset=utf-817:32
vinshIve never messed with changing or setting content type... didn't know you could.17:32
notmynameyou don't/can't (directly) on a contianer17:32
*** hseipp has quit IRC17:33
vinshCan we tell the client/swift to force json ?17:35
notmynamethat's what the ?format=json is supposed to do17:35
vinsh:-/17:35
*** annegentle has joined #openstack-swift17:36
claygso it doesn't respect ?format=json17:37
claygbut it does respect x-auth-token17:37
clayger.. it does respect ?format=json with an auth token17:37
*** annegent_ has joined #openstack-swift17:39
notmynamethat's what I'd expect17:40
claygvinsh: idk, womm -> https://gist.github.com/clayg/b7dc5f06d03529a2532f17:40
claygvinsh: notmyname: so it looks like the x-container-metadata headers aren't returned when the request is trasnlated by static web17:41
claygso these options may be set but stripped out before we can see them17:41
*** annegentle has quit IRC17:41
claygit may very well be a bug in staticweb (what version is deployed?) - but as a work around if you have some containers working you may just need to POST to the container to disable those options17:41
claygyou can verify if they're set with swift-container-info if you have access to the container nodes17:42
vinshI do have access to the container nodes17:42
vinshLet me see if I understand.  You suggest we post to the container to turn static web off on it (it may be on but we are unsure).  then test?17:43
claygnotmyname: any chance keystone auth does somehting like env.pop('x-auth-token') before staticweb sees the response?17:43
openstackgerritRobert Francis proposed openstack/swift: Add functional test test_copy_to_same to test_object.py  https://review.openstack.org/20382017:43
claygvinsh: sees like worth a shot17:43
vinshawesome, thanks for taking time to look at this with.17:43
claygdoes anyone have the devstack/keystone swift development environ up?17:43
vinsh*me17:44
claygvinsh: yup :\17:44
hrouclayg, I have it setup on SAIO and vagrant, if that helps ?17:44
notmynameclayg: thanks. my tests just finished running17:45
openstackgerritJohn Dickinson proposed openstack/swift: Update test-requirements to match global requirements.  https://review.openstack.org/20417917:45
*** bitblt has joined #openstack-swift17:48
clayghrou: keystone?  on a vagrant-swift-all-in-one?17:49
vinshclayg: this is swift 2.2.2-0 btw. unsure of static web version.17:49
clayghrou: anyway - yeah we need someone to check staticweb listings with keystone17:49
claygvinsh: seems new enough to me!17:49
hrouclayg:  Yep on vagrant-swift-all-in-one (I installed keystone after the fact) and on a standalone SAIO (i.e. none vagrant).17:50
*** peterbusque has left #openstack-swift17:50
*** bitblt has quit IRC17:51
*** bitblt has joined #openstack-swift17:51
*** annegent_ has quit IRC17:51
clayghrou: can you add a option to vagrant-swift-all-in-one to setup a keystone that will pass functests?17:51
notmynamenice17:52
claygif you do that I'll let you off the hook for the staticweb thing17:52
clayg;)17:52
*** jasondotstar has quit IRC17:52
hrouclayg:  I actually haven't tried to run func tests on my vagrant-swift-all-in-one && keystone env but let me give that a go right now !17:53
clayggood luck!17:53
hrouclayg:  In terms of static web, why the vagrant dependency, could I not simply test that in my non-vagrant setup for you ? : )17:54
clayghrou: yeah any keystone + staticweb would work - i was just trying to get free keystone support in vagrant-swift-all-in-one17:54
clayghrou: the problem is really with keystone that unless it's actively maintained it rots17:55
clayghrou: that's why I tend to use my devstack vm for keystone stuff - just cause other people care to keep it working17:55
claygi just really need to write this test for peluse :D17:56
vinshHaving a hard time finding some docs on what I post to disable staic web.17:56
claygvinsh: swift post container -m x-web-listings:17:57
claygnope17:57
claygi was *close*17:57
hrouclayg:  Yea setting up keystone initially was a bit of a pain actually, so I can see issues (particularly if you move up your swift lvl).  I think getting it built into vagrant and working is a great idea so I'll look into that regardless.17:57
*** bitblt has quit IRC17:58
claygswift post -v container -m web-listings:17:58
clayghrou: sure np, good luck with that too, very helpful, thank you!17:58
*** bitblt has joined #openstack-swift17:58
claygvinsh: sorry my first command was wrong :\17:59
vinshContainer list now works.17:59
vinshBINGO.17:59
claygvinsh: bummer :\18:00
claygvinsh: i mean it's good for you i suppose :P18:00
*** silor has quit IRC18:00
vinsh:-o18:00
hrouclayg: Sure thing and thanks !  keystone is a requirement for various middleware we're using / developing and it'd help to have an easy to setup env (for folks starting the project).18:00
vinshYou really narrowed down on that quickly. Impressed :)18:00
hrouclayg:  I'll give the keystone + static web a go as well, but assuming you're doing the same, that's a race you're going to win any day ; )18:01
vinshhrou: what are you using to provision within your vagrant vms?18:01
vinshWonder if I can offer any help on the keystone part.18:01
clayghrou: i really do need to write these tests for paul - I'm acctually ignoring the fact that staticweb is probably broken with keystone18:02
occupantit's funny how the openstack people straight up tell you keystone is awful and you shouldn't use it18:02
*** annegentle has joined #openstack-swift18:02
claygoccupant: don't listen to swift people about the rest of openstack - we're not experts18:02
occupanterr swiftstack I mean18:02
vinshWe moved over to using fernet tokens with keystone.. and it works very well.18:02
notmynamevinsh: yeah, I've been wanting to try out fernet tokens18:02
vinshmfisch will hopefully do a talk on it in Tokyo.18:03
vinshwith some of the fernet guys.18:03
*** zaitcev has joined #openstack-swift18:03
*** ChanServ sets mode: +v zaitcev18:03
vinshclayg: hrou: If you do open a bug on this statickweb issue.  Please add me or send me the id.  Id love to learn more and follow.18:04
notmynamevinsh: I was just working on that :-)18:04
notmynamevinsh: bug tracker is at https://bugs.launchpad.net/swift/+bugs18:04
claygnotmyname: it's going to be unconfirmed until hrou finishes his keystone testing18:04
notmynamevinsh: filing it there would be a big help18:04
notmynameclayg: yeah18:04
vinshOk, i'll file it now.18:05
notmynamethanks18:05
hrouvinsh: Was just going to do a simple test to validate clayg / notmyname theory in my simple env, but you've just about confirmed it by disabling it.18:06
notmynamehrou: it would be good to see someone else with keystone who sees the bug18:06
hrounotmyname: yep !  Agreed just to make sure there's nothing else at play.18:06
hrouvinsh: btw did you have 'delay_auth_decision = true' set ?  (sorry if you included that already).18:08
*** lpabon has quit IRC18:08
vinshset to "1"18:09
*** CrackerJackMack has joined #openstack-swift18:13
*** sudorandom has joined #openstack-swift18:13
*** jamielennox has joined #openstack-swift18:15
*** thebloggu has quit IRC18:16
*** jamielennox is now known as jamielennox|away18:16
*** david-lyle has quit IRC18:21
*** jamielennox|away is now known as jamielennox18:23
openstackgerritAzhagu Selvan SP proposed openstack/swift: Respect 'Accept' header in error responses  https://review.openstack.org/20419618:24
ccavannaQuestion about a unit test. In particular: test_policy_index (test.unit.common.middleware.test_proxy_logging.TestProxyLogging) fails when I check in the code, but does not fail in my unit tests.18:26
ccavanna The failure is related to my code change. I compared my version of the test with the latest on the repository, but I see no differences.18:26
ccavanna(My code change, by the way, is the logging of graphite stats for the commands organized by policy)18:28
ccavannaThe error I see is as follows:18:29
ccavannaThis line of code:18:29
ccavannapolicy_name = POLICIES.get_by_index(policy_index).name18:29
ccavannafails with:18:29
ccavannaAttributeError: 'NoneType' object has no attribute 'name'18:29
ccavannaSo clearly  POLICIES.get_by_index(policy_index) is returning None.18:30
*** annegentle has quit IRC18:30
* notmyname has a lunch meeting18:31
ccavannaOne way for get_by_index to return None is if the index I pass is not valid ('' and None return 0, or the values is converted to int.)18:33
ccavannaRegardless of the code changes, I wonder why the test fails when I submit, but not in my unit tests.18:33
claygpeluse: so the test rig i want for the ec get stuff is a little further off from what we already have in proxy.controller.test_obj18:35
claygpeluse: I'm going to get on the train and think about what i want to do here18:36
claygccavanna: you need to wrap your test with the patch_policies decorator18:37
claygccavanna: you have a policy defined on your machine that is not defined on some other machine18:37
claygyou can probably just wrap the whole class - lots of tests use it - in test.unit.__init__.py - patch_policies - will solve all18:38
claygbbiab18:38
vinshclayg: notmyname: hrou: Static web related bug now filed: https://bugs.launchpad.net/swift/+bug/147678918:41
openstackLaunchpad bug 1476789 in OpenStack Object Storage (swift) "staticweb enabled container will not list json" [Undecided,New]18:41
openstackgerritGreg Lange proposed openstack/swift: go:  Adds memcache ring  https://review.openstack.org/20375818:48
*** jlhinson_ has quit IRC18:52
*** jasondotstar has joined #openstack-swift18:52
*** janonymous has quit IRC18:53
*** jlhinson has joined #openstack-swift18:55
openstackgerritAzhagu Selvan SP proposed openstack/swift: Respect 'Accept' header in error responses  https://review.openstack.org/20419618:55
*** breitz has quit IRC19:03
ccavannaclayg: Thanks for the tip. I patched the policies and now I can recreate the error.19:04
ccavannaclayg: is it worth keeping the patch (to keep one policy only) in the unit tests? That way there's a consistent policy setting for testing, like other tests do.19:05
*** breitz has joined #openstack-swift19:08
*** gyee has quit IRC19:11
*** amit213 has quit IRC19:14
*** amit213 has joined #openstack-swift19:14
*** breitz has quit IRC19:17
*** jasondotstar has quit IRC19:18
*** breitz has joined #openstack-swift19:18
*** annegentle has joined #openstack-swift19:25
claygccavanna: yeah always better to patch policies!19:30
openstackgerritCarlos Cavanna proposed openstack/swift: Improving statistics sent to Graphite.  https://review.openstack.org/20265719:33
*** david-lyle has joined #openstack-swift19:34
*** annegentle has quit IRC19:36
*** annegent_ has joined #openstack-swift19:37
claygwhere did I add Stub Reponses?19:54
claygwas that swiftclient?19:54
claygoh yeah, that was swiftclient - nm19:55
notmynamebah! python's getting in my way19:57
notmynamefoo = lambda: raise Exception()   # syntax error19:58
*** bitblt has quit IRC19:58
claygnotmyname: that's bs - bet it works in python319:58
redboyeah, I bet raise is a function19:58
notmynameprobably :-/19:58
redboSo you can call it from a statement and not just an expression.  Or whatever silly python sounding thing.19:59
claygredbo: see what problems you run into if you let your language have exceptions?  better to just use return codes and be done with it.20:00
clayglol @ statckovermind -> y = lambda: (_ for _ in ()).throw(Exception('foobar'))20:01
notmynamefails in py33 too20:01
notmynameclayg: if I submit code that does that, please -2 it ;-)20:02
zackmdavis`raise` is not a function20:03
redboyou should make a raise function and just have it raise its argument20:03
redbothen you could use it for lambdas everywhere20:03
claygredbo: no no no *print* is a function - obviously *raise* is a statement - don't be a plebeian20:04
claygthat's it we're making python420:06
claygmulligan!20:06
redbowell first we need to go add "from __future__ import raise_function" to all of our files20:07
claygredbo: oh you're right20:07
claygfrom six import where_the_fuck_is_it_this_week20:08
*** thebloggu has joined #openstack-swift20:09
vinshIs there some flag one could set in say object-server.conf to disable a specific service like maybe object-auditor? or just object-server?20:13
claygyou can't `f = lambda : yield 1` either - and oddly `def f(): <whatever you want>` if only it was pep8 :'(20:13
claygvinsh: you just take out the config section - and it wont' start20:14
vinshYeah. +120:14
claygor chmod -x the bin20:14
*** amoturi has quit IRC20:15
*** tongli has quit IRC20:36
*** ccavanna has quit IRC20:37
hrouHey All quick FYI re: static web and keystone ... so at this point I have such that it is indeed going through keystone first (i.e. X-Web_mode: true).  And in this setup it is working just fine20:45
*** joeljwright has quit IRC20:45
vinshWas maybe a rogue container on our end?20:46
hrouhttp://paste.openstack.org/show/397006/20:46
hrouSo 'test me' is the content of index.html20:46
hrouvinsh:  I think in your case you were deferring keystone though (i.e. not using 'X-Web-Mode: true') so I need to try that20:47
hrouA bit on and off but will try that next!20:47
vinsh:)20:47
clayghrou: so vinsh specific setup was *just* `x-container-meta-web-listings: true` and the fail was html response even with x-auth-token20:48
openstackgerritJohn Dickinson proposed openstack/swift: do container listing updates in another (green)thread  https://review.openstack.org/18908020:48
notmynameclayg: I think I took care of what we talked about yesterday ^20:48
vinshI don't know exactly what x-container was set to.. since we couldn't list or stat it.  I didn't check on a container node to see what it had.20:49
claygok, i'll dust off my timeouter_server.py script and try again20:49
hrouclayg:  Thanks let me try that I had - Meta Web-Listings: true20:49
hrou   Meta Web-Error: error.html20:49
hrou   Meta Web-Index: index.html20:49
hrou   - all set.20:49
claygvinsh: well could you try swift stat again now and see if anything else was set?  you made it sound like you just turned off that one key and it worked20:50
vinshyeah. that was all i turned off and it worked.20:50
clayg... err `swift post -m web-listings:` and it started working20:50
hrouYep he showed me the output, he had nothing static web set at all at this point; so you must have been right clayg i.e. just web-listing20:51
vinshexactly20:51
claygso that seems to be the relevant value - the x-web-mode headers, and the index.html with x-container-meta-index-blah-blah is not strictly the minimum test case for the issue you observed20:51
clayghrou: ok - but from your keystone test that works?20:51
clayghrou: ok - it'll have to stay unconfirmed for awhile :'(20:51
claygunless someone else has any idea what to try?20:52
*** robefran has quit IRC20:52
*** lyrrad has quit IRC20:52
hrouStill trying ; )  As you said, I'm not repro'ing 100% yet (but yea in general it looks like works so its not a rampant issue) more soon.20:52
*** lyrrad has joined #openstack-swift20:54
hrouvinsh, you didn't set 'X-Web-Mode' did you ?  Actually you were just using the swift client.21:02
vinshYeah, just the client21:03
*** annegent_ has quit IRC21:12
*** jasondotstar has joined #openstack-swift21:22
claygunless someone else has any idea what to try?21:32
*** jkugel has quit IRC21:33
*** annegentle has joined #openstack-swift21:34
hrouI have an idea, still working through it, at this point I can only get it to work with X-Web-mode (which we know vinsh) is not using, this is because keystone auth is failing without this (which makes sense, the odd part being I have delay_auth_decision = True).21:35
notmynamehrou: that's the same that vinsh had21:35
*** annegentle has quit IRC21:35
hrouI didn't think vinsh had x-web-mode set ?21:35
*** annegent_ has joined #openstack-swift21:35
hrou** sorry I didn't mean not working => the failure vinsh saw.21:36
*** jasondot_ has joined #openstack-swift21:36
hrou** I meant I was simply getting 403 on the container listing.21:36
*** jasondotstar has quit IRC21:39
*** kragniz has quit IRC22:01
*** kragniz has joined #openstack-swift22:02
*** jodah has quit IRC22:05
*** thebloggu has quit IRC22:06
*** minwoob has quit IRC22:08
*** jodah has joined #openstack-swift22:11
*** alpha_ori has quit IRC22:11
*** alpha_ori has joined #openstack-swift22:14
mattoliveraumorning22:21
*** jrichli has quit IRC22:24
*** mgarza has quit IRC22:24
notmynameyo22:25
*** nadeem has quit IRC22:34
*** ujjain has quit IRC22:34
pelusehola22:37
*** ujjain has joined #openstack-swift22:37
*** ujjain has joined #openstack-swift22:37
openstackgerritMichael Barton proposed openstack/swift: go: wait for availability on REPLICATE  https://review.openstack.org/20429222:46
*** haomaiwang has quit IRC22:49
*** lyrrad has quit IRC23:01
*** km has joined #openstack-swift23:01
*** lyrrad has joined #openstack-swift23:04
*** jasondot_ has quit IRC23:12
*** jasondotstar has joined #openstack-swift23:17
openstackgerritOpenStack Proposal Bot proposed openstack/swift: Updated from global requirements  https://review.openstack.org/8873623:17
*** DericHorn-HP has joined #openstack-swift23:18
*** kei_yama has joined #openstack-swift23:20
clayghrou: oh right, to test the w/o x-auth-token case you need to also `swift post container -r .r:*,.rlistings`23:23
claygnotmyname: patch 204292 <- the go people get all the cool stuff!23:26
patchbotclayg: https://review.openstack.org/#/c/204292/23:26
claygand all we have is stupid lambda's that don't even support raise statements23:26
*** zaitcev has quit IRC23:27
*** david-lyle has quit IRC23:28
*** lyrrad has quit IRC23:40
*** robefran has joined #openstack-swift23:44
*** ho has joined #openstack-swift23:45
*** jasondotstar has quit IRC23:47
hrouclayg, thanks ! That could have been it, Will give that a go in a bit (once I have access to my env again ; )23:49
*** jasondotstar has joined #openstack-swift23:50
*** wbhuber has quit IRC23:51
hogood morning!23:53
*** gyee has joined #openstack-swift23:54
mattoliverauho: morning23:58
*** jlhinson has quit IRC23:59
homattoliverau: morning!23:59

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