Wednesday, 2014-05-28

*** matsuhashi has joined #openstack-swift00:01
*** mwstorer has quit IRC00:05
*** shakamunyi has quit IRC00:18
*** mlipchuk has quit IRC00:26
*** zhiyan_ is now known as zhiyan00:34
*** dmorita has joined #openstack-swift00:36
*** zhiyan is now known as zhiyan_00:36
*** sungju has joined #openstack-swift00:38
*** zhiyan_ is now known as zhiyan00:38
*** kenhui has joined #openstack-swift00:40
*** zhiyan is now known as zhiyan_00:41
*** shri has quit IRC00:44
*** Edward-Zhang has quit IRC00:58
*** mlipchuk has joined #openstack-swift01:10
openstackgerritgholt proposed a change to openstack/swift: Add debug logging to container sync requests  https://review.openstack.org/9591101:19
*** saschpe has quit IRC01:23
*** saschpe has joined #openstack-swift01:24
*** kenhui has quit IRC01:25
*** zhiyan_ is now known as zhiyan01:26
*** kenhui has joined #openstack-swift01:29
*** kenhui has quit IRC01:29
*** kenhui has joined #openstack-swift01:29
openstackgerritClay Gerrard proposed a change to openstack/swift: Fixes probe tests with non-zero default storage policy  https://review.openstack.org/8749201:34
openstackgerritA change was merged to openstack/swift: Add ability to remove subsections from /info  https://review.openstack.org/9445801:38
openstackgerritA change was merged to openstack/swift: Plumb insecure flag to functests  https://review.openstack.org/8843801:38
*** kenhui1 has joined #openstack-swift01:39
*** kenhui has quit IRC01:41
*** RockKuo_Office has joined #openstack-swift01:45
*** nosnos has joined #openstack-swift01:48
*** kenhui1 has quit IRC01:50
*** diegows has quit IRC02:09
*** judd7 has joined #openstack-swift02:30
*** ZBhatti_ has joined #openstack-swift02:31
*** mkerrin1 has joined #openstack-swift02:32
*** byeager has joined #openstack-swift02:32
*** judd7_ has quit IRC02:33
*** ZBhatti has quit IRC02:33
*** mkerrin has quit IRC02:33
*** ZBhatti_ is now known as ZBhatti02:33
*** byeager has quit IRC02:34
*** byeager has joined #openstack-swift02:35
*** zhiyan is now known as zhiyan_02:36
*** kenhui has joined #openstack-swift02:45
*** gyee has quit IRC02:49
*** zhiyan_ is now known as zhiyan02:49
*** kenhui has quit IRC02:51
*** kenhui has joined #openstack-swift02:51
*** haomaiwa_ has joined #openstack-swift02:59
*** byeager has quit IRC03:03
*** madhuri has quit IRC03:03
*** madhuri has joined #openstack-swift03:04
madhuriHi, Can anyone please help reviewing this https://review.openstack.org/#/c/85351/ ?03:04
*** Edward-Zhang has joined #openstack-swift03:09
claygmadhuri: do you need help getting started on a test for that change?03:15
*** kenhui1 has joined #openstack-swift03:15
*** zhiyan is now known as zhiyan_03:16
*** kenhui has quit IRC03:18
*** kenhui1 has quit IRC03:18
*** kenhui has joined #openstack-swift03:19
*** shakamunyi has joined #openstack-swift03:19
*** kenhui has quit IRC03:21
madhuriI will look for it to add03:22
*** zhiyan_ is now known as zhiyan03:22
openstackgerritA change was merged to openstack/python-swiftclient: change assertEquals to assertEqual  https://review.openstack.org/9360303:23
*** shakamunyi has quit IRC03:24
madhuriclayg: https://review.openstack.org/#/c/84819/ this too03:24
*** Midnightmyth has joined #openstack-swift03:31
*** Midnightmyth has quit IRC03:38
madhuriclayg: How is the container server or object server selected for processing any request?03:38
clayghttps://www.youtube.com/watch?v=o0YWRXJsMyM03:40
openstackgerritClay Gerrard proposed a change to openstack/swift: Add Storage Policy Documentation  https://review.openstack.org/9602603:40
openstackgerritClay Gerrard proposed a change to openstack/swift: Add Storage Policy Support  https://review.openstack.org/9602703:40
openstackgerritClay Gerrard proposed a change to openstack/swift: Update FakeRing and FakeLogger  https://review.openstack.org/9602803:40
openstackgerritClay Gerrard proposed a change to openstack/swift: Add Storage Policy support to Containers  https://review.openstack.org/9602903:40
openstackgerritClay Gerrard proposed a change to openstack/swift: Add Storage Policy support to Object Server  https://review.openstack.org/9603003:40
openstackgerritClay Gerrard proposed a change to openstack/swift: Add Storage Policy support to Object Updates  https://review.openstack.org/9603103:40
openstackgerritClay Gerrard proposed a change to openstack/swift: Add Storage Policy Support to the Auditor  https://review.openstack.org/9603203:40
openstackgerritClay Gerrard proposed a change to openstack/swift: Add storage policy support for the Replicator  https://review.openstack.org/9603303:40
openstackgerritClay Gerrard proposed a change to openstack/swift: Add Storage Policy Support to ssync  https://review.openstack.org/9603403:40
openstackgerritClay Gerrard proposed a change to openstack/swift: Put X-Timestamp in object 404 responses  https://review.openstack.org/9603503:40
openstackgerritClay Gerrard proposed a change to openstack/swift: Extend interface on InternalClient  https://review.openstack.org/9603603:41
openstackgerritClay Gerrard proposed a change to openstack/swift: Extend direct_client  https://review.openstack.org/9603703:41
openstackgerritClay Gerrard proposed a change to openstack/swift: Add container-reconciler daemon  https://review.openstack.org/9603803:41
openstackgerritClay Gerrard proposed a change to openstack/swift: Add reconciler probetest outline  https://review.openstack.org/9603903:41
openstackgerritClay Gerrard proposed a change to openstack/swift: Merge container storage_policy_index  https://review.openstack.org/9604003:41
openstackgerritClay Gerrard proposed a change to openstack/swift: Add Storage Policy Support to Accounts  https://review.openstack.org/9604103:41
openstackgerritClay Gerrard proposed a change to openstack/swift: Add functional tests for Storage Policy  https://review.openstack.org/9604203:41
openstackgerritClay Gerrard proposed a change to openstack/swift: Update swift-container-info to be storage policy aware  https://review.openstack.org/9604303:41
openstackgerritClay Gerrard proposed a change to openstack/swift: Enqueue misplaced objects during container replication  https://review.openstack.org/9604403:41
openstackgerritClay Gerrard proposed a change to openstack/swift: Add LRUCache to common.utils  https://review.openstack.org/9604503:41
openstackgerritClay Gerrard proposed a change to openstack/swift: Add Storage Policy Support to list_endpoints  https://review.openstack.org/9604603:41
openstackgerritClay Gerrard proposed a change to openstack/swift: Add Storage Policy Support to Container Sync  https://review.openstack.org/9604703:41
openstackgerritClay Gerrard proposed a change to openstack/swift: Add Storage Policy Support to Recon Middleware  https://review.openstack.org/9604803:41
openstackgerritClay Gerrard proposed a change to openstack/swift: Add Storage Policy support to the Account Reaper  https://review.openstack.org/9604903:41
*** zhiyan is now known as zhiyan_03:41
madhuriclayg: What all new features are up for this release?03:45
*** nosnos has quit IRC03:47
*** Edward-Zhang has quit IRC03:51
*** shakamunyi has joined #openstack-swift03:53
*** ppai has joined #openstack-swift03:54
*** zhiyan_ is now known as zhiyan04:13
*** matsuhashi has quit IRC04:15
openstackgerritA change was merged to openstack/swift: Add Ratelimit parameters to /info  https://review.openstack.org/8863304:20
*** psharma has joined #openstack-swift04:22
*** Edward-Zhang has joined #openstack-swift04:25
*** matsuhashi has joined #openstack-swift04:26
*** nosnos has joined #openstack-swift04:27
*** shakamunyi has quit IRC04:27
*** bkopilov has quit IRC04:29
*** kashyapk has joined #openstack-swift04:35
*** kashyapk has quit IRC04:36
*** bvandenh has joined #openstack-swift04:50
*** shakamunyi has joined #openstack-swift04:52
*** zhiyan is now known as zhiyan_04:53
zaitcevdaarn, I'm just getting to bed and SP reviews landed04:53
*** shakamunyi has quit IRC04:54
*** shakamunyi has joined #openstack-swift05:11
*** bvandenh has quit IRC05:12
*** zhiyan_ is now known as zhiyan05:14
*** zaitcev has quit IRC05:20
*** zhiyan is now known as zhiyan_05:25
*** shakamunyi has quit IRC05:40
*** baojg has joined #openstack-swift05:40
*** shakamunyi has joined #openstack-swift05:40
*** baojg_ has joined #openstack-swift05:47
*** baojg_ has quit IRC05:50
*** baojg_ has joined #openstack-swift05:50
*** baojg has quit IRC05:51
openstackgerritYuan Zhou proposed a change to openstack/swift: Update container storage_policy_index when auditing  https://review.openstack.org/8309305:53
*** yuanzz is now known as yuan05:54
*** mlipchuk has left #openstack-swift07:07
*** zhiyan_ is now known as zhiyan07:18
*** zhiyan is now known as zhiyan_07:27
*** haomaiwa_ has quit IRC07:28
*** haomaiwang has joined #openstack-swift07:28
*** bkopilov has joined #openstack-swift07:29
*** sungju has quit IRC07:30
*** haomai___ has joined #openstack-swift07:37
*** haomaiwang has quit IRC07:41
*** bvandenh has joined #openstack-swift07:41
*** nshaikh has joined #openstack-swift07:44
*** baojg_ has quit IRC07:49
*** baojg has joined #openstack-swift07:51
*** haomai___ has quit IRC08:05
*** haomaiwang has joined #openstack-swift08:05
*** haomai___ has joined #openstack-swift08:07
*** haomaiwang has quit IRC08:10
*** matsuhashi has quit IRC08:14
*** matsuhashi has joined #openstack-swift08:15
*** matsuhashi has quit IRC08:17
*** matsuhashi has joined #openstack-swift08:17
openstackgerritYuan Zhou proposed a change to openstack/swift: Allow to deprecate policy  https://review.openstack.org/8682708:19
*** sungju has joined #openstack-swift08:21
*** haomai___ has quit IRC08:22
*** haomaiwa_ has joined #openstack-swift08:22
*** nacim has joined #openstack-swift08:32
*** haomai___ has joined #openstack-swift08:37
*** sungju has quit IRC08:37
*** haomaiwa_ has quit IRC08:40
*** shakamunyi has quit IRC08:43
*** haomai___ has quit IRC08:57
*** haomaiwang has joined #openstack-swift08:58
*** haomai___ has joined #openstack-swift09:02
*** mlipchuk has joined #openstack-swift09:04
*** haomaiwang has quit IRC09:05
*** mlipchuk has quit IRC09:09
*** haomai___ has quit IRC09:17
*** haomaiwa_ has joined #openstack-swift09:17
*** zhiyan_ is now known as zhiyan09:19
*** nacim has quit IRC09:21
*** zhiyan is now known as zhiyan_09:28
*** haomaiwa_ has quit IRC09:35
*** haomaiwa_ has joined #openstack-swift09:35
*** zhiyan_ is now known as zhiyan09:37
*** shakamunyi has joined #openstack-swift09:40
*** shakamunyi has quit IRC09:45
*** zhiyan is now known as zhiyan_09:46
*** nacim has joined #openstack-swift09:48
*** sungju has joined #openstack-swift09:56
*** sungju has quit IRC09:59
*** mkollaro has joined #openstack-swift10:01
*** sungju has joined #openstack-swift10:01
*** sungju has quit IRC10:03
*** sungju has joined #openstack-swift10:09
*** mlipchuk has joined #openstack-swift10:21
*** nacim has quit IRC10:25
*** Edward-Zhang has quit IRC10:29
*** erlon has quit IRC10:39
*** erlon has joined #openstack-swift10:41
*** matsuhashi has quit IRC10:48
*** ppai has quit IRC10:49
*** diegows has joined #openstack-swift10:53
*** sungju has quit IRC10:55
*** judd7_ has joined #openstack-swift10:56
*** judd7 has quit IRC10:57
*** tdasilva has joined #openstack-swift11:01
*** ppai has joined #openstack-swift11:02
*** baojg has quit IRC11:09
*** baojg has joined #openstack-swift11:10
*** dmorita has quit IRC11:11
*** baojg has quit IRC11:15
*** saschpe has left #openstack-swift11:18
*** RockKuo_Office has quit IRC11:32
*** miqui has quit IRC11:51
*** sagar has joined #openstack-swift11:51
*** sagar is now known as Guest9575411:51
*** jamie_h has joined #openstack-swift11:52
*** pconstantine has quit IRC11:53
*** baojg has joined #openstack-swift11:54
*** Guest95754 is now known as sagar_11:54
sagar_Hello everyone. I am having problems installing swift and integrating it with keystone. Can I get some help?11:58
*** sagar_ has quit IRC12:08
*** sagar_ has joined #openstack-swift12:09
*** nacim has joined #openstack-swift12:10
sagar_Hello, I am trying to install the latest version of swift from icehouse. After authenticating with keystone, I am able to run successfully the command "swift stat", but the command "swift upload myfiles temp" throws the following error http://paste.openstack.org/show/81860/12:11
*** tdasilva has quit IRC12:14
*** psharma has quit IRC12:15
*** sagar_ has quit IRC12:15
*** ppai has quit IRC12:27
*** tdasilva has joined #openstack-swift12:31
*** tdasilva has left #openstack-swift12:44
*** tdasilva has joined #openstack-swift12:46
*** nosnos has quit IRC12:50
*** miqui has joined #openstack-swift12:53
*** nacim has quit IRC12:56
gholtDayum. Are my search settings wrong or does clayg actually own the whole front review page for Swift?12:57
gholtI guess it's storage policy review time, eh?12:57
*** baojg has quit IRC12:58
gholtI would also assume that means the "soft freeze" is in effect and folks should not hit merge on anything until we get the SP stuff sorted out.13:01
*** fifieldt has quit IRC13:02
gholtI believe this is the root change to start with: https://review.openstack.org/#/c/9602613:05
*** haomaiwa_ has quit IRC13:11
*** haomaiwang has joined #openstack-swift13:11
*** bkopilov has quit IRC13:18
*** bkopilov has joined #openstack-swift13:19
*** pberis has joined #openstack-swift13:22
*** pberis has quit IRC13:27
*** haomai___ has joined #openstack-swift13:28
*** haomaiwang has quit IRC13:30
gholtclayg: When we talked about split patchsets and one patchset before I'd mentioned split would be much better because any Joe should be able to merge them all to a single branch locally if they want. However, I didn't realize there'd be SO MANY. ;) Is there a way you could also post a single patchset version of all this for testing purposes for us?13:49
gholtIf it's just me, don't worry about it, I'll do the merge down of all the patches to a single branch. But if it's more than me, it'd save a lot of time overall if you pushed a merged patchset for us to leach off of. :D13:49
*** pberis has joined #openstack-swift13:52
*** nacim has joined #openstack-swift13:55
*** shakamunyi has joined #openstack-swift13:55
*** bvandenh has quit IRC13:59
*** zaitcev has joined #openstack-swift13:59
*** ChanServ sets mode: +v zaitcev14:00
*** nacim has quit IRC14:02
*** nacim has joined #openstack-swift14:22
*** foexle has joined #openstack-swift14:26
*** mlipchuk has quit IRC14:30
*** Midnightmyth has joined #openstack-swift14:42
*** kenhui has joined #openstack-swift14:43
*** kenhui has quit IRC14:43
*** kenhui has joined #openstack-swift14:43
*** diegows has quit IRC14:55
*** kenhui1 has joined #openstack-swift15:03
*** kenhui1 has quit IRC15:03
*** haomai___ has quit IRC15:04
*** kenhui1 has joined #openstack-swift15:06
*** kenhui has quit IRC15:06
*** nacim has quit IRC15:07
*** baojg has joined #openstack-swift15:13
*** shakamunyi has quit IRC15:16
*** shakamunyi has joined #openstack-swift15:18
*** bkopilov has quit IRC15:21
*** foexle has quit IRC15:28
gholtclayg: I think, maybe, this is the tail? https://review.openstack.org/#/c/96049/ If so, checking that out would get me what I want, right? A branch with everything in it?15:34
notmynamegood morning15:34
notmynamegholt: and ya, that was my plan. find the end and see if that got everything15:34
gholtIf so, there's a couple warnings with python setup.py build_sphinx. :)15:35
notmynameI see https://review.openstack.org/#/c/96026/ ans the first patch and https://review.openstack.org/#/c/96049/ as the last one15:39
notmynamegholt: so I confirm what you see15:39
*** foexle has joined #openstack-swift15:41
notmyname`git review -d 96049` will get you the full storage policy patches into one branch15:42
notmynameunfortunately, it looks like the "ratelimit in /info" patch landed after the storage policy stuff was proposed, so the SP branch isn't at the tip of master currently15:43
notmynameclayg: if there are minor issues in a particular patch, how do you want us to handle them? should we simply leave a comment and you'll do what's necessary? or should we push a patch over to fix the minor stuff?15:45
*** gyee has joined #openstack-swift15:46
*** GoJkOrS has joined #openstack-swift15:46
gholtnotmyname: Yeah, I should probably just cool it for a bit. :) Wait for you to send an email about it all. :D15:50
* notmyname suspects the answer is to just leave gerrit comments so that we don't have to get into the dependency chain management15:50
notmynamegholt: composing it now. don't wait for me :-)15:50
cschwede_notmyname: morning - and thanks for the RT! Hopefully I got everything right ;)15:54
notmynamecschwede_: looks great :-)15:54
cschwede_notmyname: cool :)15:54
gholtSweet, unit and functional tests passed here without having to change anything. Usually I have some screwed up minor detail that throws everything off.15:55
notmyname`git diff master | wc -l` ==> 2209015:55
gholtHaha15:55
creihtdang15:56
*** mkollaro has quit IRC15:56
notmyname`find . -name \*py | xargs wc -l` on master is 96754. with SP is 10720515:57
notmynameso about 11k added15:57
notmynameor about 10%15:57
gholtwc -l `find swift -name '*.py'` | sort -n = 33220 on master, 35548 with sp15:58
notmynamesee, it's only 2k lines added :-)15:58
notmynameand 9k of tests ;-)15:58
notmyname(guessing)15:58
gholtProbe tests failed for me though. Hmm.15:59
*** ChanServ changes topic to "Storage Policies have been proposed to master. Soft freeze in effect until these patches land | First SP patch: https://review.openstack.org/#/c/96026/ | Last SP patch: https://review.openstack.org/#/c/96049/"16:02
openstackgerritYuan Zhou proposed a change to openstack/swift: Update swift-object-info/swift-get-nodes to be storage policy aware  https://review.openstack.org/8273416:02
creihtaccording to sloccount16:04
creiht+1574 lines of code16:04
creiht+6537 lines of tests16:05
clayggholt: looks like you found the end of the patch set - but yeah I wouldn't mind posting everything in a single change too something like this -> https://github.com/clayg/swift/compare/sp-base16:06
notmynamecreiht: when you put it that way, it looks relatively tiny!16:06
creihtno comment16:06
cschwede_looks like something nice to read on the plane :)16:07
claygnotmyname: i can rebase ontop of anything at anytime - it's the emails to all of you that are going to get annoying16:07
gholtHeheh, filters can solve that. :)16:08
clayglet's get a days worth of reviews commented up - i'll fix everything at rebase in in the late evening again16:08
notmynameclayg: sounds good. thanks16:08
claygnotmyname: because of the rebase mess it's probably better to just leave comments16:08
notmynameclayg: I added my -2 to the start of the chain16:08
notmynameand agreed with that16:08
gholtI think maybe probe tests fail because of new info stuff or something.16:11
*** foexle has quit IRC16:12
gholtMaybe they also rely on some changes to saio I haven't yet made.16:12
gholtOh, hah, if I scroll up a bit I finally see "'module' object has no attribute 'SkipTest'" so uhm, maybe it's just that.16:13
clayggholt: oh heh, maybe i wrote a skip in there trying to be clever and never tested the skip :\16:15
gholtProbably just needs to use nose.SkipTest instead of unittest.SkipTest -- testing that now...16:16
claygoh, on py 2.6 it probably does - doh!16:18
gholtclayg: Yeah, that was it, just nose.SkipTest instead of unittest.SkipTest -- not sure which patchset I'd comment on that, or if this irc is good enough. :)16:18
claygbah, lame16:19
claygwell... which file ;)16:19
gholtHey, I'm quite happy that was all the tests found on my crazy set up. :)16:19
gholtJust two files: test/probe/test_container_merge_policy_index.py test/probe/test_container_sync.py16:20
clayggholt: do you want to just try to comment here -> https://github.com/clayg/swift/pull/1/files16:21
claygnot for this - i got this - but in general16:22
claygand thanks16:22
notmynameheh. I'm glad I just caught that. somehow my octogenarian grandparents were added to my "swift core" email list16:25
*** foexle has joined #openstack-swift16:25
glangenepotism16:26
brianclineoctogenarians everywhere want to know16:27
gholtHeheh16:29
gholtclayg: That's an option too. I'm open for any of the above. I'm guessing it'd be better to keep it all Gerrit for posteriors though.16:29
*** foexle has quit IRC16:31
clayggholt: oh that'd definately a good point - i was just thinking of your 'can't find the right review to comment on' problem...16:32
claygi guess a second squashed change wouldn't be that hard to maintain...16:32
gholtWell, there's the tail, which is fine, and git blame will tell me the rest.16:32
gholtSo I don't want to make more work when there are already solutions I can use. :D16:33
gholtI'll make the comments just to track stuff. You shouldn't have to track things you're told on irc too. That way you can just hit all the reviews once a night and go go go.16:33
clayggholt: ok, looks like jenkins had some review comments for me too already16:34
gholtYeah, Jenkins in the cases I saw was worse than useless. :)16:34
creihtcool tests initially pass here16:36
creihtnow to build docs and see if I can update my saio16:36
*** zaitcev has quit IRC16:41
claygumm... so when I was working on some of the stuff in https://review.openstack.org/#/c/96029/ I wrote these https://gist.github.com/clayg/83a504fd5aa96c077f6a - so... well just let me know if you have questions when you get to the container schema changes16:41
*** shri has joined #openstack-swift16:46
*** ozialien has quit IRC16:46
*** pconstantine has joined #openstack-swift16:48
*** baojg has quit IRC16:50
creihtat least the saio setup is easy with policies16:59
*** lpabon has joined #openstack-swift16:59
creihtand skipped func tests now run17:00
creihtsome probe test failures though17:01
* creiht waits for them to finish17:01
portanteso on one of my SAIOs unit tests fail with 7 errors and 1 failure17:05
portantedo I have to rebuild an SAIO to get the unit tests to work?17:06
*** bvandenh has joined #openstack-swift17:06
gholtportante: I didn't.17:06
portanteTypeError: sequence index must be integer, not 'str', at line 105, translate_container_headers_to_info17:06
portanteokay, I'll go look then17:07
*** diegows has joined #openstack-swift17:07
portantewait, maybe my deps are out of date ...17:07
gholtThat's sounds like... fun. Heheh.17:07
portante;)17:07
*** bvandenh has quit IRC17:08
claygoh this is usefulish -> https://review.openstack.org/#/q/status:open+project:openstack/swift+branch:master+topic:bp/storage-policies,n,z17:08
portanteclayg: thanks17:09
gholtAh yeah, not bad. Also, I finally found a use for those Gerrit stars. Marked the leading and trailing patchsets. :)17:09
*** zaitcev has joined #openstack-swift17:09
*** ChanServ sets mode: +v zaitcev17:09
clayggholt: nice!17:09
gholtOf course, that's just for me, but still I like it!17:09
claygportante: which changeset are you on?  there's been so much rebasing, i know all the tests will pass for each change on at least my environment, but some of the shuffling may have introduced some corners that don't appear in the final product17:10
portanteI started with the final patchset, 9604917:11
claygoh... well hehe - that should work ;)17:11
portanteclayg, but I might have some out-of-date deps in my SAIOs17:11
portanteI am running them under tox now to see if that works in my environment17:11
*** diegows has quit IRC17:18
GoJkOrSHey all, I am trying to setup a new region in swift and I am wondering how I get 1 copy of the data over to that new region and vice versa.  ie. region 1 has a new object come in, that object should have 3 copies in region 1 and 1 copy in region 2.  Is this possible?17:19
clayglol @ superdupernit:17:20
notmynameGoJkOrS: swift will take your 3 replicas and spread them out over the regions you have configured. so you will have 3 replicas total, and if you have two regions, you'll have at least one replica in each region17:21
claygk, i'm getting on a train for a bit - i'll work on some of the doc comments - thanks17:21
*** nshaikh has quit IRC17:21
GoJkOrSHum.  That is not the behavior that I am seeing.  I see all 3 copies in 1 region and nothing in the second region.  Let me do a bit more testing to see if what you describe is happening.17:22
notmynameGoJkOrS: did you set any write affinity?17:22
GoJkOrSI have not17:22
notmynameGoJkOrS: is this an existing cluster that you are adding a new region to?17:23
GoJkOrSYes.17:23
GoJkOrSI have 1 zone in each region also.17:24
notmynameGoJkOrS: is the other region a similar size (capacity) as the first one?17:24
GoJkOrS1 region is 6 nodes and the second is 5 nodes.  The nodes are all the same size.17:25
notmynameGoJkOrS: ok. does `swift-ring-builder` say that your ring is balanced?17:26
*** bkopilov has joined #openstack-swift17:26
GoJkOrS262144 partitions, 3.000000 replicas, 2 regions, 2 zones, 11 devices, 0.00 balance17:27
notmynameGoJkOrS: so far so good :-)17:28
notmynameGoJkOrS: so how's replication in the cluster? has it completed a full pass since you added the other region?17:28
GoJkOrSHow do i determine that?17:29
notmynameGoJkOrS: if you have the recon middleware installed, you can use `swift-recon --replication`17:29
notmynameGoJkOrS: otherwise you need to look in the logs and find the "replication pass complete" messages17:30
GoJkOrSOIC.  Ok.   Let me look.17:30
notmynameGoJkOrS: just looked at the code. the message is "Object replication complete.  (%.02f minutes)" and is logged at INFO level17:31
notmynameerr...just one space there17:31
notmynamein case you want to grep for it :-)17:31
GoJkOrSShould I look for that on a new node or an existing node?17:32
GoJkOrSAs in one from the original region or one on the new region.17:32
notmynameGoJkOrS: should be running on every node17:32
notmynameGoJkOrS: but since replication is push-based, look for it on the original region first17:32
*** bkopilov has quit IRC17:35
GoJkOrSMay 28 17:35:53 swift09 object-auditor Object audit (ZBF) "forever" mode completed: 0.04s. Total quarantined: 0, Total errors: 0, Total files/sec: 72.47 , Total bytes/sec: 0.00, Auditing time: 0.04, Rate: 0.9817:36
GoJkOrSis that the line?17:36
notmynameGoJkOrS: that's the auditor, not the replicator17:36
GoJkOrSMay 28 17:37:14 swift09 object-replicator Object replication complete. (0.00 minutes)17:37
GoJkOrSIC17:37
notmynamethat seems...optimistic ;-)17:38
GoJkOrSThere is very little in the original cluster.17:38
*** kenhui1 has quit IRC17:39
notmynameGoJkOrS: do you have a particular object you are looking at?17:41
GoJkOrSI am doing a du on the new devices and it shows 0.17:42
*** bena has joined #openstack-swift17:43
notmynameGoJkOrS: if you have a particular object, you can check where it's supposed to be in the cluster with `swift-get-nodes`17:43
notmynameGoJkOrS: then you can check that it's actually there17:43
benahi I am using s3curl to connect to swift openstack17:43
notmynameGoJkOrS: also, you should check that the rings are all the same on all the servers17:43
benaI run ./s3curl.pl --id 'testing:admin' --key 'intel123' --get -- -k -v -s http://10.1.0.10:808017:44
benabut recived an AccessDenied<17:44
portantezaitcev: on F19, looks like a sudo pip install -U xattr busts things up a bit17:45
portantecffi seems broken17:45
zaitcevportante: why would you even do that?!17:45
GoJkOrSok, thanks for the help.  I will keep working on it and will check back if I need any further help.17:45
portante:(17:45
portantefollowing the SAIO directions17:45
portantewhy wouldn't you do that?17:45
benado you know the account:user and password of openstack swift17:45
bena??17:45
zaitcevI never let pip anywhere near my boxes.17:45
*** jamie_h has quit IRC17:45
zaitcevWell, except under tox17:46
zaitcevI you want to use pip, install Ubuntu.17:46
notmynamebena: it's whatever you have configured in your auth system. there isn't just one. swift is a multi-tenant system17:46
portantezaitcev: perhaps then you can make some recommendations to the SAIO documentation for Fedora to not use pip and provide the proper things there?17:47
zaitcevportante: I keep patching it and then some jerk breaks it again. It was a tug of war since 2010.17:47
zaitcevportante: At least we got rid of that awful "Swift on RHEL" wiki page17:48
*** bkopilov has joined #openstack-swift17:49
*** bena_ has joined #openstack-swift17:49
bena_what is the default account:user and password swift17:50
bena_??17:50
*** bena has quit IRC17:50
notmynamebena_: what auth system are you using?17:50
bena_the default auth system17:51
notmynamebena_: there isn't a default. or there is, but only from the perspective of whatever install doc you followed17:51
notmynamebena_: "swift" doesn't have an account or password. users (with credentials) are given access to a swift account. the 401 you are getting is because the credentials you supplied either could not be authenticated or were authenticated but not authorized to access a swift account17:52
bena_./s3curl.pl --id <account>:<user> --key <password> --get -- -k -v -s http://10.1.0.10:808017:52
zaitcevportante: I'll come back and re-fix the development_saio.rst, however we still have an issue with our xattr that makes PYTHONPATH=$(pwd) required to run ./.unittests.17:52
bena_how you do to connect with s3curl?17:53
zaitcevportante: I was thinking about creating a fake egg around xattr.17:53
notmynamebena_: I've never used s3curl17:53
zaitcevbet he forgot to add swift3 into proxy pipeline17:54
portantezaitcev: okay, lemme try that17:55
portantethat is a bummer17:55
zaitcevportante: Functests work fine as-as, if that helps :-)17:55
portantezaitcev: unfortunately in my environment that pythonpath trick is not workin17:55
zaitcevportante: well, dropping xattr from requirements and python setup.py build help17:56
zaitcevportante: although I don't know what your specific issue is, it could be something else17:57
portantezaitcev: looks like "pip install -U xattr" from SAIO causes a new version of cffi to install, and things break17:57
*** lpabon has quit IRC17:57
zaitcevportante: maybe you need a sticky note with "rpm -e pip" on your laptop's bezel17:58
portantecute ;)17:59
zaitcevBy definition pip wreaks havoc with the system and there's no way to go back except a reinstall. That is why we always package everything and do not support pip.17:59
zaitcevBy we I mean Red Hat OpenStack team.18:00
zaitcevIt has its downsides, like the need to package every new thing Monty throws at us, like pbr.18:00
zaitcevpip is just as bad as Ruby gems18:01
*** lpabon has joined #openstack-swift18:01
portantezaitcev: okay, so this seems to work: pip uninstall cffi xattr; yum install python-cffi pyxattr18:01
*** lpabon has quit IRC18:01
* notmyname wishes "use packages" was a more common viewpoint in openstack18:01
zaitcevIt's something a latte-sipping SOMA hippies throw at their devops servers before they cash out of their startup18:01
notmynamezaitcev: I'll have you know I drink mochas! not lattes18:01
notmynamespeaking of which....18:02
* notmyname goes to brew another pot of locally roasted, artisinally crafted, fair-trade, shade-grown, etc, etc coffee18:03
portanteI spoke too soon, the unit tests fail with DistributionNotFound:xattr>=0.418:03
notmyname(did I get the words right?)18:03
zaitcevYeah, needs a fake egg or  dropping xattr from requirements and python setup.py build18:03
portanteugh18:03
portantereally?18:03
portanteI think we need a better answer on Fedora18:04
*** lpabon has joined #openstack-swift18:04
zaitcev>> do something about xattr.so and xattr>=4.0: create a fake egg (re 1020449)18:04
*** tdasilva has quit IRC18:04
zaitcevI agree, we do18:05
zaitcevbrb, going to visit a knee surgeon18:09
portantezaitcev: best of luck on that18:10
*** diegows has joined #openstack-swift18:14
notmynameknee surgeon? what's up with people working on swift getting hurt? me, mlanner, zaitcev, anyone else?18:19
*** mwstorer has joined #openstack-swift18:22
*** elambert has joined #openstack-swift18:34
*** lpabon has quit IRC18:34
claygback18:36
clayglol @ zaitcev's rant on pip18:38
brianclinenotmyname: my knees are growing increasingly unhappy as well18:41
brianclinenot something that should be happening at age 30, though it did start a few years ago18:42
brianclinemy involvement in swift also began a few years ago18:42
brianclinehuh18:42
*** gvernik has joined #openstack-swift18:42
creihtclayg: http://paste.ronin.io/cd48e89118:45
creihtI enabled policies on my saio, and I am getting those to errors18:45
claygcreiht: looking18:45
notmynameoh. thank you calendar reminder. swift team meeting in 15 minutes. full meeting: storage policies patches. choo choo!18:45
creihtwhen I run probetests18:45
notmyname(as in that's it. not as in we'll talk about it more)18:45
claygcreiht: did you run the functests?18:46
claygcreiht: you're on the final patchset?18:46
claygcreiht: did gholt ever get the probetests passing?18:47
claygcreiht: oh nm, I think he was just running them with the skips (no sp configured yet)18:47
claygcreiht: i'm guessing the saio instructions didn't include a "copy etc/swift/container-reconciler.conf-sample into /etc/swift/container-reconciler.conf" :P18:48
creihtlol18:48
creihtno18:48
creihtfunctests ran fine18:49
notmynameclayg: I'm looking over the docs, but my saio probe tests failed too. I think because of the lack of a reconciler config18:49
creihtI'll copy the reconciler config and try again18:49
claygcreiht: yeah they don't really hit the failure modes18:49
creihtright18:49
claygcreiht: did you mostly use policies_saio18:49
creihtclayg: yeah18:49
claygcreiht: I guess I should check both docs18:49
claygcreiht: k, thanks18:49
creihtI'll leave a note18:49
claygcreiht: awesome!18:49
* clayg says "did you even run this?" for creiht 18:50
creihtlol18:50
creihtit is actually going smoother than I expected :)18:50
claygcreiht: oh that's just cause you have't gotten too far into it yet18:50
creihthaha18:50
claygat least you guys will be able to slap me next week in CO18:51
creihtwell honestly I wasn't figuring I would get this far18:51
claygpeluse_: ^ props for decent doc!18:51
notmynameclayg: peluse_: are there different tmp and quarantine directories for different policies?18:55
claygnotmyname: that was a great comment by gholt - i'm going to look at adding that today - should be mostly tucked in DiskFile18:56
*** mjfork has joined #openstack-swift18:56
notmynamekk18:56
notmyname(ya, that's where I got it)18:57
mjforkas a user of 2 different swift clusters, is it possible to run container sync externally?  or does it require privileged access from the service provider side?18:58
notmynamemjfork: container-sync itself requires privileged access. but an external process to poll + GET/PUT would be functionally equivalent (or close).18:59
gvernika question. Each patch related storage policies depends on another patch which depends on another patch and so on... When i do for example something like that "git fetch https://review.openstack.org/openstack/swift refs/changes/40/96040/1 && git checkout FETCH_HEAD" will it automatically fetch all dependencies?19:00
notmynamemjfork: and whenever we have marconi (or some other distibuted, durable queue), we can make that much more flexible and efficient :-)19:00
cschwede_gvernik: yes, and you should use patch 96049 - it’s the last patch19:00
notmynamegvernik: if you get the last patch in the chain, you will get the whole chain19:00
notmynamegvernik: and you can use `git review -d <gerrit patch number>` to automatically make a branch for it and download it19:01
gvernikthanks19:01
mjforknotmyname: thanks.19:01
*** tdasilva has joined #openstack-swift19:02
creihtclayg: getting closer19:03
creihtnow I just have this error with probe tests19:03
creihthttp://paste.ronin.io/4bf1105f19:03
cschwede_anyone saw an error in testContainerListing (test.functional.tests.TestAccount) ?19:04
claygcreiht: hrmm... that should be the container-replicator19:04
creihthrm19:06
creihtfor saio19:06
creihtdo I need just one container-reconciler.conf19:06
claygcreiht: can you sanity check swift-init container-replicator once -nv19:06
creihtor do I need a separate one for each19:06
claygcreiht: just the one19:06
creihtk19:06
claygbut the merging of storage policy index happens in the container-replicator - the reconciler is just a queue chewer19:07
creihtclayg: running that seems to run without error19:08
creihtbut of course the test data will be gone since it resets for each test19:08
claygcreiht: well you can run just the one test "python ./swift/test/probe/test_container_merge_storage_policy_index.py -x" and it will halt leaving the environment messed up for you to inspect19:09
creihtk19:09
claygor "...py:TestContainerMergePolicyIndex.test_merge_storage_policy_index" if you wanna get real specific19:10
creihtdo you mean -v instead of -x?19:11
claygwell, -x says "stop at the first failure"19:11
creihtahh19:11
claygif you just run that one test then you don't really need it19:11
creihtwell -x is for nosetests and not python right?19:11
claygcreiht: oh... yeah run it with nose them :P19:12
creihteither way running that one test19:12
creiht:)19:12
creihthrm running that one test by iteself passed19:13
claygso looking at the timestamps in that paste those containers should have settled down... i would say maybe it was a weird timing/ordering thing... but we run the replicator twice to make sure that isn't really an issue19:13
clayg"we" - get_to_final_state does that19:14
*** mkollaro has joined #openstack-swift19:15
claygcreiht: oh we're supposed to be in that other channel19:16
creihtheh19:16
notmynameno, you're not :-)19:16
notmynameyou're doing what you're supposed to be doing right here :-)19:16
creihtlol19:17
creihtok running tests on just the .py by itself worked19:17
creihtrunning full thing again19:17
claygoh, that was quick19:18
creihtheh19:21
creihtclayg: ok now all tests pass19:21
creihtmaybe there is a rare race condition there?19:21
claygcreiht: well, i stick it in a for loop and see if I can get it to pop19:22
gholtI thought probe = "possible race obe" Okay, I'm not good at backronyms.19:22
creihtlol19:22
creihtyeah probably not a big deal19:22
creihtunless it happens a lot19:23
creihtpassed again19:26
creihtmeh19:26
creiht:)19:26
claygcreiht: i think once is too much, i say we cancel storage policies19:26
creihtso looks like I got saio setup with policies19:26
creihthaha19:26
gholtcreiht: How many unit tests do you skip per run atm?19:27
creihtrunning again to verify19:27
gholtCool, thanks! 72.002s here btw19:27
gholtEr, 74.002s that is..19:28
clayggholt: unittests should be able to mock out storage polices anytime they need more than one... i don't know why any unittests would skip short of something trying to be cleaver with a dependency that's tricky to build or something?19:28
*** tdasilva has quit IRC19:29
creihtgholt: 0 skipped in 85.171s19:29
gholtI'm just wondering if I don't have something set up right so it's not testing or something. Oh, I gotcha. Yeah, unit tests shouldn't care about my set up I guess.19:29
gholtI skip 3 unit tests and 3 func tests. each runs about the same, ~74s.19:30
claygso yeah I think some functests should skip if the system under test isn't exposing more than one storage policy19:30
claygwell.. there's lots of functests that may skip19:30
creihtI think I only skip 1 func test19:30
gholtI've also got some skpping domain name something something and something, so...19:30
clayggholt: if you can track down the names of those skipped unittests I'd love to know why19:30
creihtbut there were a lot more skipped when I didn't have a policy19:31
gholtYeah, I'll double check what I'm still skipping to be sure.19:31
gholt-v19:31
claygcreiht: a lot more functests skipped?19:31
creihtyeah19:31
creihtI *think*19:31
claygyeah i don't know how many ended up getting in19:31
creiht:)19:31
claygand I think it may like skip the *class* or something?  so i don't know how many S's you get19:31
creihtwhich is reasonable to me19:31
creihtjust double checked, I'm not skipping any functests currently19:33
creihtand 76.474s :)19:33
gholtOoh, I found another type toeken. I feel like I'm contributing!19:34
gholtLol, another typo (with my typo)19:34
creihtheh19:34
notmynamegholt: don't worry. someday you'll be a useful contributor to swift ;-)19:34
gholt:)19:35
notmyname(the ";-)" means I'm laughing, if that doesn't translate in text--text-mode jokes are awesome!)19:35
gholtIt'd almost be better if I misunderstood and got all in a huff. Heheheh19:35
clayglol19:36
*** tdasilva has joined #openstack-swift19:37
*** elambert has quit IRC19:38
notmynamehmm...probetests pass (with one skip) after I run `python ./setup.py develop`. wish I would have thought of that first19:39
claygnotmyname: probably the expirer or container-sync or something19:40
notmynameclayg: so, FYI on my SAIO, unit, func, and probe tests all pass. with one skip in probe tests19:40
notmynameclayg: perhaps. will the -v/-x thing work to find it?19:40
creihtnotmyname: yeah that is the same here19:40
claygyeah i'm glad tests are mostly working for folks - sans creiht weird thing, and whatever is going on with portante's setup19:40
claygnotmyname: umm.... yeah -v will show the names, maybe a bunch of other stuff...19:41
gholtclayg: Yeah, all my 3 skipped func tests are due to me not have object versioning enabled.19:41
notmyname*cough*RHEL*cough*19:41
gholtI should probably enable that or something.19:41
clayggholt: it's on by default in vagrant-swift-all-in-one, also has built in storage policy support and makes it easy to toggle features in configs on a saio because of conf.d19:42
claygheh19:42
clayggholt: oh and the autodoc script is sorta handy-ish (i obvioulsy didn't run it it or i would have seen all those build errors)19:43
gholt:) I'm not sure why I don't have it enabled or how I did that or how to undo it. But i'll learn19:43
clayggholt: but better late than never?19:44
claygsomething in like the container-server configs somehow?19:44
gholtSet ``allow_versions`` to ``True`` in the container server config19:44
gholtRight there in the doc/source/overview_object_versioning.rst :)19:44
*** diegows has quit IRC19:47
*** jogo has left #openstack-swift19:48
gholtCool, now 0 skipped func tests. I feel complete. Thank you all.19:49
notmynameah, yes. "SKIP: Unable to find container sync realms"19:50
notmynamegholt: copy etc/container-sync-realms.conf-sample to /etc/swift/ ?19:51
notmynameand rename19:51
gholtEr, I don't think that'd work but it might. Mine has:19:52
gholt$ cat /etc/swift/container-sync-realms.conf19:52
gholt[realm1]19:52
gholtkey = abc19:52
gholtcluster_name1 = http://127.0.0.1:8080/v1/19:52
*** diegows has joined #openstack-swift19:52
claygnotmyname: i'd be it's all right there in doc/source/overview_container_sync.rst :P19:53
claygnotmyname: I'd also bet that vagrant-swift-all-in-one has built in support19:53
notmynamelol19:53
claygyup, add container-sync-realms was the last commit ;)19:54
gholtHeheh19:54
*** bkopilov has quit IRC19:55
creihtclayg: also, probably should ad DocImpact to all the commits :)20:00
claygcreiht: #willfix20:00
creihthehe20:00
creihtbut the storage policies basics seem to be working on my saio20:00
creihtleft some notes on policies_saio.rst20:01
creihtgoint to take a break for a bit20:01
claygno no no don't stop - it gets better!20:03
creihthaha20:04
*** bkopilov has joined #openstack-swift20:14
peluse_been out all morning... looks like we've started rocking on SP20:18
claygdoes DocImpact go above or below the change-id and the implements bp thing?20:18
notmynameclayg: change-id has to be in the last paragraph. I'd put it right after the Implements line20:20
notmynameit == "DocImpact"20:20
claygdo late i'm going DocImpact\nImplements\nChange-Id20:20
claygs/do/too/20:20
notmynamethat's ok too :-)20:20
peluse_clayg:  have you started doing anything with the SP doc comments?  I will start addressing them now if not20:20
claygpeluse_: yeah i think i'm all caught up20:21
claygpeluse_: can you review yuan's changes or see about adding get_policy_string support to the /tmp and /quarantine dirs20:21
peluse_clayg:  way cool.  yes, I can do both - consider them done!20:22
peluse_clayg:  quesiton though, for the /tmp and /q dir deal, do I propose that to master and hunt down the right current patch in the proposed chain that has the base function and use that as a dependency as the best way to proceed?20:28
*** elambert has joined #openstack-swift20:30
*** gvernik has quit IRC20:30
*** mjfork has quit IRC20:35
peluse_clayg: or maybe better yet I could just push on patch https://review.openstack.org/#/c/96027/20:41
creihtso with swift-get-nodes, you have to know what ring the object is in20:43
creihtright?20:43
notmynamecreiht: I think yuan just proposed a WIP patch (to master?) this morning for that20:43
creihtoh cool20:44
notmynameah, to feature/ec https://review.openstack.org/#/c/82734/20:44
peluse_https://review.openstack.org/#/c/82734/20:44
peluse_duh, sorry20:44
notmyname:-)20:44
creihtso with that, you will still need to know what storage policy an object is in right20:45
peluse_I'll check with yuan tonight and see what the WIP is20:45
peluse_correct20:45
creihtwhich an operator isn't likely to know20:45
peluse_heh, maybe that's the WIP :)  Good point though20:45
creihtjust based on the url20:46
peluse_should be able to get it from the cont in the url, no?20:46
creihtso it seems to me either swift-get-nodes should be smart enough to look up what policy the container is20:46
creihtor have a tool to easily query policies for a given container20:46
peluse_that20:46
peluse_that's what I'm thinking, but I haven't looked at this patch yet.  I'll get Yuan the feedback though20:47
notmynameya. the nice thing about swift-get-nodes now is that it's completely offline20:47
creihtwell I guess swift-container-info could show that20:47
creihtnotmyname: yeah I know20:47
creihtthat's why I'm kinda waffling on it20:47
*** bena_ has quit IRC20:49
claygpeluse_: just make the change to feature/ec and I'll pull it into the chain?20:50
peluse_clayg:  roger20:51
claygcreiht: swift-container-info has the policy in it, so on a saio you can for db in $(find /srv/node*/*/container* -name \*.db); do swift-container-info $db | grep -i policy; done20:52
claygcreiht: otherwise you can hack something together with direct_client20:52
creihtyeah20:52
creihtI can just see it confusing for operators20:52
claygcreiht: swift-get-nodes always requires you "know the ring" depending on account/container/object-N - it's sorta weak for that20:52
creihtyeah I know20:52
claygcreiht: not sure I follow, but i'm open to suggestions20:52
creihtyeah I don't have a good answer either20:53
claygcreiht: yaun and peluse_ are working on it - I think we can make the tools better20:53
creihtcool20:53
creihtI'll wait to see what they come up with20:53
claygcreiht: are you trying to solve for like "given some number of ring locations what do the containers there think their storage policy is at the moment"?20:56
*** miqui has quit IRC20:56
creihtclayg: no, I'm thinking that I get a url from someone that is having issues20:56
creihtso I run a swift-get-nodes to figure out where the object is supposed to be20:57
claygah yeah - and that has to talk to the container servers20:57
creihtyeah I don't know what storage policy an object is20:58
openstackgerritOpenStack Proposal Bot proposed a change to openstack/python-swiftclient: Updated from global requirements  https://review.openstack.org/8925021:00
openstackgerritOpenStack Proposal Bot proposed a change to openstack/swift: Updated from global requirements  https://review.openstack.org/8873621:00
*** tdasilva has left #openstack-swift21:05
*** gyee has quit IRC21:14
*** shri has quit IRC21:25
*** diegows has quit IRC21:38
*** Midnightmyth has quit IRC21:42
peluse_clayg:  just noticed we'll have issues with > single digit policy indixies in a few places... I'll knock that out too and add a test case21:43
* clayg is trying to imagine where/how we backed in the assumption that polices will only be one digit21:44
notmynamepeluse_: simple! make sure they are base-36 and you've got enough storage policies for everyone!21:46
notmynamepeluse_: from a comment "Are there any rules about what are legal policy names?" <<-- is this "utf8 string less than a few k long" since it has to be in headers?21:48
* notmyname is imagining a storage policy with a name 3k bytes long21:49
claygnotmyname: sounds like a loaded question21:50
notmynamethe one in the comments or mine? :-)21:50
claygthe comment - like the next question is going to be "but what if someone creates a name like..."21:51
peluse_hehe21:52
peluse_FYI wrt the policy index issue its just how we're doing some parsing of dir names to extract the index... nothing to do with names on that one21:52
notmynameheh. the "yomamma" policy. it just disables the 413 response21:53
claygoh... hrmm... do we regex the dir listing or something?21:53
peluse_ base, policy_idx = dir.split('-', 1)21:53
claygseems legit21:53
claygthe 1 is the number of times to split21:54
claygso you get object, 123 == 'object-123'.split('-', 1)21:54
claygso you get object, -123 == 'object--123'.split('-', 1)21:54
peluse_oh cool, was just reading it wrong then.  never mind :)21:54
clayginstead of say 'object', '', '123' == 'object--123'.split('-') or something like that21:55
claygI like the 413 HTTP status on the yo momma joke - most people go for 40221:57
notmynamehmm...I just learned that there is a 431 response code specifically for headers being too big21:57
claygnotmyname: invinted to keep keystone in check no doubt21:58
*** ekarlso has quit IRC22:01
notmynamelol22:02
notmynameclayg: funny coincidence on that. the rfc that defined that response code was written by mark nottingham. it was accepted in 2012, which is about the same time RAX was doing lots of keystone shenanigans (IIRC). and at the time, mark was employed by rackspace.22:05
notmynameso it seems perfectly logical that the specific response header is a result of keystone ;-)22:05
* notmyname is bad at writing conspiracy theories22:08
gholtHeheh, so hopefully by tomorrow morning we'll all be done with the spell/grammar checking.22:16
*** ekarlso has joined #openstack-swift22:26
peluse_sheeeeit22:30
peluse_oops, wrong window :)22:31
brianclinethe judges will still allow it22:31
clayggholt: if the docs look good and the tests pass we're basically ready to merge right?22:33
notmynameI don't know if it's worth it at this point. POLICY and POLICY_INDEX are header names22:40
dfgclayg: just made a non-doc related comment- you just wait...22:40
claygyay yay yay!22:41
claygnotmyname: i was pretty sure at somepoint that those needed to change, but then I think i realized I didn't care.22:41
claygnotmyname: they do end up looking funny in tests next to a bunch of other headers22:41
notmynameclayg: ya, that's my only nit with them. it is a nit. but it's something I've had to recheck every time I've looked at the feature/ec branch22:42
claygnotmyname: I think we probably could get away with just using literal strings and trying not to typo - but having flake8 check it for you is nice too22:42
claygnotmyname: it must go away after you spend some time with it - still no time like the present if we wanna go hog wild with a search and replace?22:43
notmynameI'm not convinced that's it's worth it. let me get deeper into the patch chain and see what happens22:45
claygdfg: i can't wait any more - submit it now!22:45
dfgclayg: i think i built it up too much. I'm just glad I can sit in my beanbag to get through these reviews22:50
claygpeluse_: notmyname: do we get "I survived the storage policy merge" t-shirts?22:53
* clayg somehow still thinks we're all going to survive22:54
*** Edward-Zhang has joined #openstack-swift22:55
claygpeluse_: yuan's patches are looking good - I think i took the container-auditor-migration thing and probably the non-zero-default-probetest fix, i'm testing deprecate storage policy support change now22:55
notmynameclayg: http://imgur.com/NdO5Jq222:56
*** bkopilov has quit IRC22:59
peluse_clayg:  cool, I'm struggling with some VM issues with my SAIO so am moving slow right now (literally).  Argh23:00
claygpeluse_: vagrant destroy -f; vagrant up23:00
clayggo get coffee and come back to a fully configured working saio23:01
claygthere's been studies... 95% of the time it works everytime23:01
*** bkopilov has joined #openstack-swift23:13
peluse_clayg:  thx.  not sure if my vbox is falling down or I might have an SSD issue with my laptop... great timing23:13
claygawww that sucks - sorry bro23:13
*** ozialien has joined #openstack-swift23:19
claygpandemicsyn: i don't know what any of this means, but I *do* hate load-balancers so can I do this instead -> http://bits.shutterstock.com/2014/05/22/stop-buying-load-balancers-and-start-controlling-your-traffic-flow-with-software/23:19
peluse_clayg: best I can do on the shirt is a free generic Intel t-shirt next week but I can bring a sharpie with me :)23:20
*** kragniz has quit IRC23:32
claygyuan: peluse_: why is it a good idea to make it so you can't deprecate policy-0?23:38
claygyuan: peluse_: I guess you'd have a different way to enfoce a default... if you can't guarantee zero is available23:39
claygidk, maybe it'd acctually be ok if the default policy was deprecated - it would just force people to choose a policy on purpose when creating a container23:40
*** kragniz has joined #openstack-swift23:44
*** mkollaro has quit IRC23:45
*** gyee has joined #openstack-swift23:53
*** foexle has joined #openstack-swift23:56
*** bkopilov has quit IRC23:57

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