Wednesday, 2015-07-22

*** lyrrad has joined #openstack-swift00:00
*** jasondotstar has quit IRC00:01
*** robefran_ has joined #openstack-swift00:04
*** DericHorn-HP_ has joined #openstack-swift00:07
*** pberis2 has joined #openstack-swift00:08
*** hrou has quit IRC00:09
timurhey folks, I submitted a bug report a while back and was hoping to get some feedback on it: https://bugs.launchpad.net/swift/+bug/1475018. Do you think it's something that is likely to be fixed or left as Swift quirk?00:15
openstackLaunchpad bug 1475018 in OpenStack Object Storage (swift) "Either delimiter option is not properly documented or has a bug" [Undecided,New]00:15
notmynametimur: which patch did you submit for it (from the comments there)00:16
*** jasondotstar has joined #openstack-swift00:16
*** jasondotstar has quit IRC00:16
*** jasondotstar has joined #openstack-swift00:16
timurnotmyname: https://review.openstack.org/#/c/202302/00:16
*** robefran has quit IRC00:17
*** DericHorn-HP has quit IRC00:17
*** DericHorn-HP_ is now known as DericHorn-HP00:17
timurmost of the patch is a test of the behavior (I noticed that there were no tests for the delimiter behavior -- submitted one more to just add a couple: https://review.openstack.org/#/c/202303/)00:18
notmynametimur: thank you for the tests00:20
notmynametimur: honestly, i don't know yet00:21
notmynamebased on the commit message, it may be a bug00:21
notmynamehowever, "fixing" it is hard depending on how clients are affected00:21
timurnotmyname: it's probably not the intended behavior, but I'm not sure if anyone is relying on this quirk00:21
timurright00:21
notmynameyeah00:21
notmynameexactly00:22
*** ccavanna has joined #openstack-swift00:24
*** dmorita has joined #openstack-swift00:30
*** darrenc is now known as darrenc_afk00:35
*** lyrrad has quit IRC00:40
ho:q00:43
hosorry for it. I typed on wrong app....00:44
*** hrou has joined #openstack-swift00:44
*** DericHorn-HP has quit IRC00:54
*** jasondotstar has quit IRC00:56
*** darrenc_afk is now known as darrenc01:00
*** kutija has quit IRC01:07
ccavannaDoes anyone know about these tests? gate-tempest-dsvm-full01:09
ccavannaI keep getting errors from this test when I check in my code, but I am not sure how to run these tests locally.01:10
ccavannaI'm thinking it's related to this bug.01:12
ccavannahttps://bugs.launchpad.net/cinder/+bug/147673501:12
openstackLaunchpad bug 1476735 in Cinder "check failure in gate-tempest-dsvm-full-ceph; failure to import backup" [High,Confirmed]01:12
*** DericHorn-HP has joined #openstack-swift01:13
*** hrou has quit IRC01:14
*** hrou has joined #openstack-swift01:15
openstackgerritCarlos Cavanna proposed openstack/swift: Improving statistics sent to Graphite.  https://review.openstack.org/20265701:22
hoccavanna: i have no experiment to run tempest on my local env but clone https://github.com/openstack/tempest and configure it then execute tempest_run.sh might work.01:28
ccavannaho: Thanks. I just checked more and there are many reports of that test failing for the past few days.01:32
claygtimur: thanks for asking about a review - i left some thoughts - but it looks great - thanks for the help!01:49
*** kota_ has joined #openstack-swift01:49
*** ChanServ sets mode: +v kota_01:49
kota_morning01:50
claygkota_: !!!01:50
claygkota_: I feel like you have dozens of patches I haven't looked at01:50
claygkota_: can I review something for you?01:50
kota_clayg: please!!!!01:50
claygkota_: tell me which one01:50
claygpeluse: I didn't get as far as I'd hoped on those tests today01:50
claygpeluse: *but* after torgomatic dropped some knowledge on me I think I have a plan01:50
claygpeluse: just need to make sure no one erased the whiteboard while I was in meetings :'(01:51
kota_clayg: patch 201055 is highest priority I think01:51
patchbotkota_: https://review.openstack.org/#/c/201055/01:51
kota_that's a fix for a bug 1467677 and it is set as critical01:51
openstackbug 1467677 in OpenStack Object Storage (swift) "Server side copy with Single Ranged read not working with Erasure Coded Data" [Critical,In progress] https://launchpad.net/bugs/1467677 - Assigned to Kota Tsuyuzaki (tsuyuzaki-kota)01:51
claygoh yeah - that looked scary01:51
claygcloses a bug and everything01:52
*** DericHorn-HP has quit IRC01:52
kota_clayg: for community, I guess patch 199043 should be closed asap.01:53
patchbotkota_: https://review.openstack.org/#/c/199043/01:53
claygoh wow - ok so COPY with range param01:53
kota_clayg: yes, the first one is a fix for COPY with range.01:54
kota_that causes from the object-server response difference between EC and replicated.01:55
claygok, both of those look do-able - thanks!01:56
kota_on replicated case, we can trust the response status from get_response() call because the range will be already handled on object-server.01:56
kota_clayg: Thanks for taking care of me :)01:57
clayglol01:57
kota_Added a bit, on EC case, the range will be handled on proxy-server, strictly at calling the response (resp()) for starting response.01:59
kota_that's why the COPY request mishandle the content length and response status and it results in the bug.02:00
claygsure - that makes sense02:00
*** DericHorn-HP has joined #openstack-swift02:00
claygkota_: it *does* seem like the copy extraction would have been helpful here02:00
claygI'm sort of getting tired of "man this would be so much better/easier if copy and versions were just middleware!"02:01
kota_clayg: exactly, the copy middleware is a solution. do you bet to do so?02:02
*** jkugel has joined #openstack-swift02:03
claygidk, i just do whatever tdasilva tells me02:03
kota_lol02:03
claygi review, find bugs, he fixes them and add tests, I review again02:03
claygit's a painful process02:03
claygI assume at some point it will merge and I will stop complaining02:03
kota_make sense02:04
tdasilvalol02:04
*** annegent_ has quit IRC02:04
kota_if the copy middleware had depend on just master, I could make an effort to land instead of my patch.02:04
notmynamesee the "Big important stuff right now" on https://wiki.openstack.org/wiki/Swift/PriorityReviews02:04
kota_tdasilva!02:05
tdasilvakota_: let's land versioning first02:05
tdasilva:D02:05
notmynameand encryption needs the copy extration too02:05
tdasilvazaitcev had already given a +202:05
claygversioning hs *got* to be close02:05
tdasilvajust needs another one02:05
*** annegentle has joined #openstack-swift02:06
tdasilvaclayg: i fixed the latest bug you had found02:06
kota_ok, I'll be a volunteer02:06
tdasilvayay!02:06
claygtdasilva: I was sorta pissed when I found that stupid remove bug - I was about to +2 it - but by the time I wrote the functest I was like bah - we might as well go ahead and fix it :'(02:06
claygtdasilva: yah i was trying to tease out the fix somewhere between patch 35-38 - is x-versions-location the only header that get's set or removed?02:07
patchbotclayg: https://review.openstack.org/#/c/35/02:07
claygno patchbot02:07
tdasilvalol02:07
kota_lol02:07
hrouHey All, re: vinsh problem from earlier today, I took keystone out of my pipeline (left the OS_ ... set) and can repro:  swift list swiftfirstCont --os-storage-url=http://127.0.0.1:8080/v1/AUTH_b2c9f064ec32460eb487aca279a97d76  ValueError: No JSON object could be decoded.  So I can reproduce, did we know for a fact keystone was in play ? --debug will show "DEBUG:keystoneclient.auth.identity.v2" if OS_AUTH_02:08
hrouis set so I don't think that's key02:08
claygkeystone is not in the pipeline and it fails for you?  that worked for me!02:09
clayghrou: thanks for testing btw02:09
claygyou think the environ vars matter?02:10
tdasilvaclayg: yeah, when you send x-remove-versions-location, it just sets x-versions-location to ''02:10
*** annegentle has quit IRC02:10
hrouclayg, did you use curl or the swift client ? Seems like the problem lies there, I can use 'curl' just fine and get the html listing.02:10
claygtdasilva: that looks pretty sane to me!02:11
tdasilvakota_: are you going to be in Austin?02:11
claygkota_: say yes say yes!02:11
claygtdasilva: are YOU!?02:11
kota_yes!02:12
claygkota_: YES!02:12
tdasilvacool, i'll be there too02:12
tdasilvalooking forward to seeing you guys there02:12
kota_great :D02:12
clayghrou: yeah with curl (no auth token) -> html, with curl (x-autht-token) -> json, with cli (x-auth-token) -> json02:13
kota_i'm now writing a new spec for swift, maybe i could introduce it at Austin.02:13
tdasilvakota_: cool...what you working on?02:13
kota_I'm not sure it would be good.02:13
claygkota_: LOL02:13
kota_working on EC efficiation for global cluster.02:14
*** DericHorn-HP has quit IRC02:14
kota_strictly 2 data center EC.02:14
kota_sometimes custamer wants to ensure the saving objects if one data center gone also on EC case.02:15
kota_It absolutely needs equal or more than 2x data redanduncy but...02:16
kota_2x data (e.g. k=20, m=24) redanduncy decreases encoding/decoding peforemance sinificantly.02:17
kota_so i'm now thinking/writing a new way changing Swift handing instead of using such a large number of parities.02:19
claygkota_: I always assumed that multi-site EC for these DR scenarios would just want two replicas of the EC'd data - 10+4 over here and 6+2 over there.02:21
kota_According to spec process, I have to write idea and goals w/o patch design but I must think the design because I am a developer :P02:21
claygkota_: start with the use case, and design from the cluster operator up02:21
kota_clayg: yes, my idea is similar with yours.02:22
claygkota_: neat!02:22
kota_yes, start with the use case, I really agree!02:22
clayg:D02:22
*** blmartin has joined #openstack-swift02:23
clayghopefully some of the IBM/SoftLayer guys will be in austin - I think for some deployments a better container-sync implementation will be be exactly what the deployer needs02:24
claygdoes anyone remember or has seen the per-disk-rsync-module patch?02:24
*** gyee has quit IRC02:39
*** zaitcev has joined #openstack-swift02:39
*** ChanServ sets mode: +v zaitcev02:39
kota_wow, versions_write middleware has amazing number of patch sets.02:50
claygtdasilva: is amazing02:50
kota_absolutely02:51
*** peterbus_ has joined #openstack-swift02:53
*** blmartin has quit IRC02:53
*** DericHorn-HP has joined #openstack-swift02:57
*** DericHorn-HP has quit IRC02:58
*** nakagawamsa has joined #openstack-swift03:01
*** pberis2 has quit IRC03:01
*** DericHorn-HP has joined #openstack-swift03:02
*** DericHorn-HP has quit IRC03:13
*** sanchitmalhotra has joined #openstack-swift03:17
openstackgerritAzhagu Selvan SP proposed openstack/swift: Respect 'Accept' header in error responses  https://review.openstack.org/20419603:31
*** h00327910_ has quit IRC03:35
*** DericHorn-HP has joined #openstack-swift03:36
*** sanchitmalhotra has quit IRC03:36
openstackgerritAzhagu Selvan SP proposed openstack/swift: Respect 'Accept' header in error responses  https://review.openstack.org/20419603:36
*** sanchitmalhotra has joined #openstack-swift03:37
*** km_ has joined #openstack-swift04:03
*** km has quit IRC04:03
*** kei_yama has quit IRC04:04
*** kei_yama has joined #openstack-swift04:05
*** kota_ has quit IRC04:06
*** ho_ has joined #openstack-swift04:07
*** ho has quit IRC04:09
*** Kennan2 has joined #openstack-swift04:14
*** Kennan has quit IRC04:15
*** DericHorn-HP has quit IRC04:35
*** kota_ has joined #openstack-swift04:41
*** ChanServ sets mode: +v kota_04:41
*** ccavanna has quit IRC04:45
zaitcevDoes anyone remember if policy names permit special characters such as dots or colons?04:50
*** tsg has quit IRC04:52
claygzaitcev: we started really restrictive04:53
claygI think you only get stuff that will work in a header key04:54
claygso like ascii letters numbers and hyphen's04:54
claygI don't think you can even have underscores?04:54
claygit's in storage_policy.py IIRC04:54
kota_valid characters definitions is here? VALID_CHARS = '-' + string.letters + string.digits04:55
zaitcevkota_, clayg: I see, thanks.04:56
kota_clayg: thanks for reviewing patch 199043 :)04:56
patchbotkota_: https://review.openstack.org/#/c/199043/04:56
claygkota_: that shit is crazy04:57
claygi'm almost done with the EC Copy Range test04:57
claygi don't quite yet understand why it's not just better to wait and set content_length later04:57
*** darrenc is now known as darrenc_afk04:58
kota_to wait?04:59
claygwell that iter has to get kicked eventually - but I guess it's not until after we've already established backend connections?04:59
*** SkyRocknRoll has joined #openstack-swift05:00
claygyup ok05:00
kota_yup, there are 2 different iter in the EC resposne, one is range iter and the other is body iter.05:02
*** kutija has joined #openstack-swift05:03
kota_Normaly, if we need a single range, ResumingGetter will knock the unecessary iter but05:05
*** ho has joined #openstack-swift05:05
kota_it doesn't affect the backend resuming getter.05:05
claygare we talking about patch 201055 or the other one I already reviewed?05:05
patchbotclayg: https://review.openstack.org/#/c/201055/05:05
kota_yes,05:06
clayg499 copy range05:06
kota_ok, sorry.05:06
claygand the range iter matters here?05:06
*** kei_yama has quit IRC05:06
*** km_ has quit IRC05:06
kota_no relation between 199043 and 201055, they are isolated.05:07
*** ho_ has quit IRC05:07
claygok - so which one are we talking about - i'm working on 499 copy range - every time I think I have it; it slips05:07
*** ho has quit IRC05:07
kota_ok, I was misunderstanding you might talk about 19904305:08
kota_that's my fault.05:08
claygthe tests are great tho, and change *looks* simple - but it's down in the guts of swob and there's all these iters wrapping iters - it just hurts05:08
claygoh05:08
claygyeah we can talk about that one too05:08
claygthe two client disconnect messages on master are two ec_ndata connections05:08
claygI don't see how the range iters really play ... oh you're saying *thats* what's raising the Generater Exit?05:09
*** kei_yama has joined #openstack-swift05:09
kota_the Generater Exit raising is about 199043.05:10
claygyeah ok05:11
claygso patch 19904305:11
patchbotclayg: https://review.openstack.org/#/c/199043/05:11
kota_actually, the copy will succeed w/o 201055 but proxy handles the succeeded put as 499 client disconnected05:11
*** ppai has joined #openstack-swift05:11
claygsee now *you're* mixing the two05:11
claygoh wait... maybe you're just talking about 20105505:11
claygwhich one do you want to talk about :D05:12
kota_yes, for now I'm talking about 201055.05:12
claygI was done with 199043 for the moment unless you wanted to drop some knowledge on me - I *did* -1 it - so you may need to strighten me out05:12
kota_on the 201055 case, no GeneratorExit happned.05:12
claygI think I like 201055, but I'm still struggling05:12
claygok yeah so 20105505:12
claygthat's 499 copy range05:13
claygk05:13
kota_for example05:13
kota_the source object size is 100 bytes05:13
claygI think I don't understand why it worked on the replicated case05:13
kota_and then wants to copy the object with range:bytes=5-1005:14
kota_and ec segment size is 102405:14
kota_and k=2, m=1, so assuming actual fragment size 512 bytes.05:15
kota_proxy server will get whole bytes (i.e. 512 bytes) from object-server to decode the original segment.05:16
kota_the response from src_req.get_response() will be 200 and content_length will be 512.05:17
kota_proxy sever will set the 512 as target_req.content_length.05:17
kota_but actuall transfer byte size is just 5 bytes because of range header.05:18
claygyeah i get all that05:18
kota_it will make 499 client disconnected05:18
kota_thanks05:18
claygjust trying to understand the change - the bug makes perfect sense05:18
kota_oh, ok05:19
claygso before EC did swob not used to do any of this content_length manipulation?05:19
kota_In replicated case, the object-server response will be 206 partial conetn and src_resp.content_length will be 5.05:19
claygyup - see that now05:20
kota_so in replicated case, we don't have to consider about that on proxy, just transferring was enough.05:21
*** zaitcev has quit IRC05:21
claygkota_: yes but *why* is calling _respose_iter the *right* fix?05:22
claygi understand the bug and I've duplicated the code change resolves the issue05:22
claygbut why is this fix the right fix05:22
clayg"it works" is rarely good enough - _respose_iter is a under method - swob didn't expect you to need this05:22
kota_oic...05:23
claygI see that it fixes the content_length but why does it have to wait to do that in *that* method?05:23
claygwhy doesn't the source_resp that comes out of self.GET just have the right content-lenght on it05:24
*** hrou has quit IRC05:25
kota_so you means the _reponse_iter will be called, we should wait to do that.05:25
claygi don't really know - that's what I'm struggling with - it's quite possible this is the perfect fix - i just don't understand why05:26
kota_i guess we should take the right content_length before opening the backend target connection.05:26
claygoh05:26
claygECObjectController._fix_response_headers I think is not so correct about 'Content-Length'05:27
*** ho has joined #openstack-swift05:27
kota_or we should use just encoding: chunked without content length?05:27
claygI prefer to keep all the extra cunked bytes off the wire when we can05:28
kota_clayg: yup, _fix_reponse_headers just set original conent length.05:28
claygkota_: so but that's stupid right?05:28
kota_clayg:05:28
kota_right05:28
kota_but once i changed that, swift doesn't work well.05:29
claygwtf - how can it even do that?  what about a 404 response - or 50305:29
claygkota_: lol!05:29
kota_the content length set by _fix_response_headers seems to be referenced05:30
kota_maybe range calculation?05:30
claygoh i bet it does that but then swob fixes it05:30
clayg:P05:30
claygbecause if the body is a static html it can just call length05:30
claygand we already know that ranged requests will fix content length05:30
kota_i see05:31
clayggoodness gracious05:31
*** mahatic has joined #openstack-swift05:41
openstackgerritMatthew Oliver proposed openstack/swift: Add container and account reverse listings  https://review.openstack.org/12070905:43
kota_wait, src_response would *not* call _response_iter because the response doesn't be passed back to __call__, right?05:48
kota_handle_copy_request just uses the app_iter as just a data source like as wsgi.input05:49
kota_i might have to re-read swob implementation...05:50
claygkota_: yeah thats where I am05:50
claygkota_: but yeah I don't think the replicated case ever gets into this method - the content length is just right because the object server knows how to set it05:51
claygI'm pretty sure the GET method on the ECObjectController should do the same - but ultimately it's swob job to do all that range parsing bits05:51
kota_exactly05:51
claygit's just got it self setup to not do it until the last minute05:51
claygalthough it *could* do it anytime after you set the body/app_iter and content_length to the real obj size05:52
claygyou could do it in __init__ but the property setter interface lets you change .content_length after you __init__ with an app_iter :\05:52
kota_oh, sorry I have a meeting since 5 minutes later. I'm willing to make sure how we could improve this later.05:53
kota_thanks clayg!05:53
*** ktsuyuzaki has joined #openstack-swift05:55
*** ktsuyuzaki has quit IRC05:56
*** kota_ has quit IRC05:58
*** mahatic_ has joined #openstack-swift06:03
*** mahatic has quit IRC06:04
*** darrenc_afk is now known as darrenc06:05
*** mahatic has joined #openstack-swift06:06
*** mahatic_ has quit IRC06:07
*** mahatic has quit IRC06:14
jith_hi all, in dashboard->images(glance) what is the architecture field while creating images06:16
*** silor has joined #openstack-swift06:19
claygjith_: did you try in #openstack-glance already?06:20
claygjith_: you might try in #openstck-dev too06:20
*** silor1 has joined #openstack-swift06:20
jith_clayg: ya i tried in glance.. will try in dev too.. thanks06:20
claygit's good to try here - some swift people know people that use glance ;)06:21
*** silor has quit IRC06:24
*** silor1 is now known as silor06:24
*** mahatic has joined #openstack-swift06:24
jith_yes....  any one configured swift as backend for glance??06:25
*** ppai has quit IRC06:27
*** mahatic has quit IRC06:32
*** mahatic has joined #openstack-swift06:33
*** ppai has joined #openstack-swift06:39
*** mfalatic has quit IRC06:42
*** mahatic has quit IRC06:52
*** lyrrad has joined #openstack-swift06:53
claygkota_ there's you go - two -1's - last time you ask me for reviews06:56
*** hseipp has joined #openstack-swift07:04
mattoliverauclayg: lol, look at you commenting on a commit message in patch 202303, I'm so proud :P If you want to push up a new patch with a better commit message I'd be happy to +2 it ;)07:05
patchbotmattoliverau: https://review.openstack.org/#/c/202303/07:05
claygit's just free tests - timur asked in channel so I think he was looking for the feedback - we'll see what he says07:05
claygI do sorta honestly remember one time thinking that a prefix query with a delim, but when the prefix didn't *end* in the delim was basically non-sensical07:06
claygbut i guess that's not really one of the tests07:07
mattoliverauyeah, I was just battling prefixes + delimiters in the reverse listing patch, so found it funny to open up a review to some testing of the same kinda stuff.07:09
clayglol - right!07:09
claygyou probably could have written it better!07:09
mattoliverauclayg: so your back from holidays, and you do a late nighter. Great to have you back! :)07:10
claygthanks!07:11
*** mahatic has joined #openstack-swift07:17
*** kota_ has joined #openstack-swift07:20
*** ChanServ sets mode: +v kota_07:20
*** ktsuyuzaki has joined #openstack-swift07:23
ktsuyuzakiwow, my wi-fi at meeting room is not well...07:24
ktsuyuzakithis is kota_07:24
-openstackstatus- NOTICE: zuul is undergoing an emergency restart. Jobs will be re-queued but some events may be lost.07:24
openstackgerritKota Tsuyuzaki proposed openstack/swift: Fix 499 client disconnected on COPY EC object  https://review.openstack.org/20105507:25
*** lyrrad has quit IRC07:25
*** kota_ has quit IRC07:26
*** kota_ has joined #openstack-swift07:29
*** ChanServ sets mode: +v kota_07:29
claygkota_: I think that's already looking better07:31
*** ktsuyuzaki has quit IRC07:31
claygkota_: if you're still working on it I'll hang back - but I think the direction that you're taking there fits pretty well with my understanding of the problem07:32
claygkota_: I think it's worth nothing fix_response_headers will also fix the status - which is important for the error handling in the copy logic - because it checks for 4XX on the GET part and returns the immediately - which is key07:34
*** ktsuyuzaki has joined #openstack-swift07:34
ktsuyuzakiclayg: thanks, in my quick view, I also think my direction addressed yours so just let me have a time to review and to think. I'll ping you during today on gerrit, again after I confirmed the diff more deeply.07:35
*** kota_ has quit IRC07:36
claygi like your diff better than mine <blush>07:37
claygbut np, just ping me when it it needs another round07:38
openstackgerritHisashi Osanai proposed openstack/swift: Add functional test for access control (PUT) with Keystone  https://review.openstack.org/20241107:39
*** jordanP has joined #openstack-swift07:39
ktsuyuzakiclayg: perhaps, you hit another bug 1475499 during testing the range copy07:41
openstackbug 1475499 in OpenStack Object Storage (swift) "EC: proxy server returns wrong response on range GET" [Undecided,Confirmed] https://launchpad.net/bugs/1475499 - Assigned to Daisuke Morita (morita-daisuke)07:41
ktsuyuzakiclayg: the first hang curl on https://gist.github.com/clayg/cf1c39be98279ae3d7eb07:41
claygktsuyuzaki: heh - yeah that one "hung" waiting for the 62442704 bytes that would never come ;)07:42
ktsuyuzakii guess that's not only COPY07:42
ktsuyuzakialso affects GET07:42
claygoh no?  any unsatisfiable range on GET07:42
claygI tried it on master and I didn't think it hung like that?07:43
claygfor... some reason?07:43
ktsuyuzakireally? for EC object?07:43
claygoh... maybe it totally do.. no that doesn't make sense07:43
claygbha yeah - that's lame07:44
*** ppai has quit IRC07:46
openstackgerritTimur Alperovich proposed openstack/swift: Add two functional tests for delimiter.  https://review.openstack.org/20230307:47
*** kota_ has joined #openstack-swift07:49
*** ChanServ sets mode: +v kota_07:49
openstackgerritTimur Alperovich proposed openstack/swift: Add two functional tests for delimiter.  https://review.openstack.org/20230307:50
*** ktsuyuzaki has quit IRC07:51
*** ktsuyuzaki has joined #openstack-swift07:55
*** kota_ has quit IRC07:57
*** kota_ has joined #openstack-swift07:58
*** ChanServ sets mode: +v kota_07:58
openstackgerritHisashi Osanai proposed openstack/swift: Add functional test for access control (DELETE) with Keystone  https://review.openstack.org/20298607:58
*** ppai has joined #openstack-swift07:59
*** ktsuyuzaki has quit IRC08:00
openstackgerritHisashi Osanai proposed openstack/swift: Add functional test for access control (GET) with Keystone  https://review.openstack.org/20299408:01
*** ktsuyuzaki has joined #openstack-swift08:02
*** jistr has joined #openstack-swift08:03
openstackgerritHisashi Osanai proposed openstack/swift: Add functional test for access control (HEAD) with Keystone  https://review.openstack.org/20299708:04
*** kota_ has quit IRC08:04
openstackgerritClay Gerrard proposed openstack/swift: wip: tests for paul  https://review.openstack.org/20448508:06
openstackgerritHisashi Osanai proposed openstack/swift: Add functional test for access control (POST) with Keystone  https://review.openstack.org/20299908:07
openstackgerritHisashi Osanai proposed openstack/swift: Add functional test for access control (OPTIONS) with Keystone  https://review.openstack.org/20301208:09
*** aix has joined #openstack-swift08:10
*** ktsuyuzaki has quit IRC08:11
hojith_: fyi. http://docs.openstack.org/cli-reference/content/chapter_cli-glance-property.html08:11
*** kota_ has joined #openstack-swift08:15
*** ChanServ sets mode: +v kota_08:15
jith_ho: thanks :)08:16
-openstackstatus- NOTICE: zuul jobs are currently stuck while problems with gearman are debugged08:16
*** ChanServ changes topic to "zuul jobs are currently stuck while problems with gearman are debugged"08:16
openstackgerritClay Gerrard proposed openstack/swift: do container listing updates in another (green)thread  https://review.openstack.org/18908008:20
claygso that's it for me i think08:20
claygdose *anyone* remember the per-disk-rsync module patch?  Did I dream it?08:21
hoclayg: how about patch 192186 ?08:24
patchbotho: https://review.openstack.org/#/c/192186/08:24
claygho: yes!08:25
hoclayg: it's not your dream :)08:26
kota_clayg: http://paste.openstack.org/show/399105/ would resolve your curl stuck on https://gist.github.com/clayg/cf1c39be98279ae3d7eb08:29
claygyeah I must have been doing some testing wih that change in place08:29
kota_clayg: we need absolutely more improvement08:30
claygI think I like the trick where you add the resp.new_swob_method_that_makes_conditional_responses_not_stupid() into self._fix_response_headers too08:30
claygpatch it!08:30
clayggo go go kota!08:30
claygmattoliverau can plus +2 it and I'll +A in the am08:30
clayggo world team swift!08:31
kota_k, i wanna make sure you mean new_swob_method_that_makes_conditional_responses_not_stupid()...sorry.08:33
kota_should i change the method name on swob on current patch?08:35
hoacoles_wa08:35
hoacoles_away, donagh: around?08:35
claygwhat!?08:37
claygkota_: what did you name it08:37
kota_swob.Response.fix_response_headers08:37
claygit was like fix_response_headers - which was close - but it should also capture the idea that it fixes the response status too and whatever "conditional_range" is08:37
*** joeljwright has joined #openstack-swift08:38
*** ChanServ sets mode: +v joeljwright08:38
kota_ok08:38
claygI think it will also call close_if_possilbe(app_iter) on error - so - it does a lot08:38
*** kei_yama has quit IRC08:38
claygbut no, "new_swob_method_that_makes_conditional_responses_not_stupid" while an accurate name - was ment to be a joke and a placeholder08:38
claygit's a bit long to type08:39
kota_k08:39
kota_maybe just "fix_conditional_response" seems good from your patch on github.08:40
clayg+108:40
claygmattoliverau: didn't you really hate on us for the non-dry ecdiskfile stuff - go review https://review.openstack.org/#/c/198429/ already!08:42
*** rledisez has joined #openstack-swift08:48
*** ppai has quit IRC08:55
openstackgerritKota Tsuyuzaki proposed openstack/swift: Fix 499 client disconnected on COPY EC object  https://review.openstack.org/20105508:59
kota_oh I forgot rewrite commit log...09:01
hoacoles_away, donagh: as we agreed in last summit, I have been developing functional test for access control. I try to split into small patches so I would like to have reviews on patch 202411 first. I will submit several patches on it within two weeks.09:06
patchbotho: https://review.openstack.org/#/c/202411/09:06
claygwhoa - that's so meta09:07
claygho: http://stackoverflow.com/questions/6453235/what-does-damp-not-dry-mean-when-talking-about-unit-tests09:08
*** ppai has joined #openstack-swift09:08
claygho: not to say there's anything wrong with those tests - but first impression -> xac means nothing to me, and that RBAC_PUT table doesn't immediately provide a lot of insight into the expected behavior of the UUT09:10
openstackgerritKota Tsuyuzaki proposed openstack/swift: Fix 499 client disconnected on COPY EC object  https://review.openstack.org/20105509:10
claygho: don't listen to me - it's late - you know what they say the difference in good code vs bad code?  http://ptrace.fefe.de/wtfm.jpg09:11
claygi'm sure it'll make sense when I dig in ;)09:11
claygg'night all09:11
kota_done to fix some method name.09:11
kota_and commit log09:12
*** km has joined #openstack-swift09:24
*** nakagawamsa has quit IRC09:27
*** jasondotstar has joined #openstack-swift09:30
*** jasondotstar has quit IRC09:35
*** ppai has quit IRC09:45
*** ppai has joined #openstack-swift09:59
*** joeljwright1 has joined #openstack-swift10:07
hoclayg: thanks for the info. unnn... the style of the functional test was discussed in the summit ("policy.json" in log: https://etherpad.openstack.org/p/liberty-swift-contributors-meetup). the tests should be expressed as a matrix in the code and a line consists of condtions and an expected result in order to validate current access control behaviors and easy to understand expectation.10:07
hoclayg: I almost finished additional functional test for container acl now with same style... So I would like to discuss it tomorrow.10:07
*** joeljwright2 has joined #openstack-swift10:08
*** joeljwright has quit IRC10:10
*** joeljwright1 has quit IRC10:11
hoclayg: good night!10:11
*** SkyRocknRoll has quit IRC10:17
*** aix has quit IRC10:19
*** DericHorn-HP has joined #openstack-swift10:20
*** kota_ has quit IRC10:25
*** joeljwright2 has quit IRC10:46
*** jasondotstar has joined #openstack-swift10:48
*** robefran_ has quit IRC10:54
*** ppai has quit IRC10:58
*** joeljwright has joined #openstack-swift11:02
*** ChanServ sets mode: +v joeljwright11:02
*** joeljwright1 has joined #openstack-swift11:05
*** SkyRocknRoll has joined #openstack-swift11:05
*** joeljwright has quit IRC11:07
*** SkyRocknRoll has quit IRC11:08
*** mahatic has quit IRC11:10
*** ppai has joined #openstack-swift11:11
*** mahatic has joined #openstack-swift11:12
*** aix has joined #openstack-swift11:18
*** jkugel has quit IRC11:21
*** SkyRocknRoll has joined #openstack-swift11:25
*** DericHorn-HP has quit IRC11:30
*** ho has quit IRC11:36
*** mahatic has quit IRC11:43
openstackgerritOndrej Novy proposed openstack/swift: Rsync port in ring file.  https://review.openstack.org/19219811:49
*** SkyRocknRoll has quit IRC11:52
*** david-lyle has joined #openstack-swift11:52
onovyclayg, hi clay. if you have any more questions for 192198, i'm here to reply11:54
mattoliverauonovy: I think he's gone to bed, it is very late (or is it very early now) in the states.11:55
onovyah, ok, thanks11:55
onovyhow long takes code review? avg? :) i'm waiting 1mon+, and almost nothing happends :( https://review.openstack.org/#/c/192562/11:58
*** mahatic has joined #openstack-swift11:59
mattoliverauonovy: good question, depends on what's happening in the community and time of year. Or if we are frantically trying to get a major feature in the next release.12:02
mattoliverauSorry if sometimes it takes a while.12:02
onovynp, is there something what can i do for review?12:02
*** sanchitmalhotra has quit IRC12:04
mattoliverauonovy: Your doing the right thing, ask in here if it seems stalled. I'm about to goto bed (it's 10pm in Australia), but will add your change to the top of my list tomorrow :)12:04
onovythanks a lot, good night12:05
mattoliveraunight :)12:05
*** peterbus_ has quit IRC12:19
*** peterbusque has joined #openstack-swift12:20
openstackgerritChristian Schwede proposed openstack/swift: Removing commented out code in test/unit/account/test_backend.py  https://review.openstack.org/20457512:24
*** dmorita has quit IRC12:26
*** mfalatic has joined #openstack-swift12:27
*** tongli has joined #openstack-swift12:30
*** ppai has quit IRC12:31
*** km has quit IRC12:40
*** DericHorn-HP has joined #openstack-swift12:44
*** hrou has joined #openstack-swift12:54
*** annegentle has joined #openstack-swift12:56
*** haypo has joined #openstack-swift12:57
haypocschwede: hi. i replied to your comments on https://review.openstack.org/#/c/199034/12:57
haypocschwede: this patch is the shortest patch to reach the miletone "working tox -e py34" which will be a nice step to avoid Python 3 regressions on the tested code12:58
*** joeljwright1 has quit IRC12:58
*** minwoob has joined #openstack-swift12:59
*** joeljwright has joined #openstack-swift13:02
*** ChanServ sets mode: +v joeljwright13:02
cschwedehaypo: well, the change looks mostly ok to me, except the rfc822 workaround and pyeclib workaround in tox.ini. but looks like both issues are making progress, which is a good thing13:09
openstackgerritpaul luse proposed openstack/swift: Add ability for GET path to see/select alternate frag archs  https://review.openstack.org/20128313:10
*** robefran has joined #openstack-swift13:15
*** DericHorn-HP has quit IRC13:19
*** jkugel has joined #openstack-swift13:19
*** SkyRocknRoll has joined #openstack-swift13:21
*** david-lyle has quit IRC13:27
*** wer has joined #openstack-swift13:28
onovyhttps://review.openstack.org/#/c/192562/4/AUTHORS should i remove my name, as paul suggests and resend patch?13:48
*** wbhuber has joined #openstack-swift13:51
*** DericHorn-HP has joined #openstack-swift13:58
*** blmartin has joined #openstack-swift14:00
*** jrichli has joined #openstack-swift14:02
*** tsg has joined #openstack-swift14:07
wbhuberpeluse: what's involved in the tuned that tweaks settings for incremental performance?  code changes within diskfile?  even though the charts are straightforward, but what's involved between "untuned" and "tuned" remains ambiguous...14:12
*** SkyRocknRoll has quit IRC14:12
*** SkyRocknRoll has joined #openstack-swift14:13
mahaticjrichli, hi! I see that you have unit tests (for encrypter on PUT, POST etc and missing keys as well). Could you tell me what probe tests are supposed to be verifying?14:15
-openstackstatus- NOTICE: CI is currently recovering from an outage overnight. It is safe to recheck results with NOT_REGISTERED errors. It may take some time for zuul to work through the backlog.14:16
*** ChanServ changes topic to "CI is currently recovering from an outage overnight. It is safe to recheck results with NOT_REGISTERED errors. It may take some time for zuul to work through the backlog."14:16
jrichlimahatic - sure.  There are two cards in trello for the probetests.  One of them is:14:17
jrichliProbetest: PUT object, verify stored object is encrypted, verify container listing metadata is consistent and encrypted with container key14:17
jrichliThe first step is for you to setup your SAIO that includes the latest for encryption.14:18
mahaticjrichli, hmm, I did look at them. But aren't you already verifying "Stored object is encrypted" in your unit test?14:19
jrichlito do this, download the code from https://review.openstack.org/#/c/203454/14:19
jrichlitbh, acoles_away wrote that card.  I think that the purpose is to have an integrated test with the real encryption/decryption middleware and the crypto class.14:20
mahaticokay, that doesn't sound too straightforward14:25
*** haomaiwang has joined #openstack-swift14:25
jrichliI am happy to help with any questions you have.14:28
mahaticyes sure, I was looking at the code14:28
*** maestro has joined #openstack-swift14:28
maestrohi14:28
maestroi want to increase the speed download14:29
maestroin swift14:29
maestrowhat are the parameters to consider to do fine tune14:29
maestropresently am getting 75Mbps.. but still want to increase14:30
maestro75MBps14:30
jrichlimahatic: be sure not to look at the old review anymore.  Are you looking at what is there when you download patch 203454?14:32
patchbotjrichli: https://review.openstack.org/#/c/203454/14:32
mahaticjrichli, I didn't download that yet, I'm still looking at it directly over the link14:33
*** ChanServ changes topic to "Review Dashboard: http://goo.gl/8IUcKl | Summary Dashboard: http://goo.gl/qHus5v | Hackathon topics: https://etherpad.openstack.org/p/swift-midcycle-aug-2015 | Logs: http://eavesdrop.openstack.org/irclogs/%23openstack-swift/"14:35
-openstackstatus- NOTICE: CI is slowly recovering, please be patient while the backlog is worked through.14:35
*** jlhinson has joined #openstack-swift14:36
jrichlimahatic: ok.  that last patch in the chain is just adding account and container encryption, so it won't show you everything that has been added14:36
mahaticjrichli, okay. I haven't downloaded any code related to encryption (that hasn't been merged). Am I to start with this patch?14:37
jrichlimahatic - yes, start with that one.  When you download it, the dependent patches will also be downloaded so you will see it all together.14:38
mahaticoh okay. sure14:38
jrichlimahatic - mainly focus on encrypter, decrypter, trivialkeymaster and their unit tests.  those are the significant items that have been added.14:39
mahaticokay14:40
*** lpabon has joined #openstack-swift14:47
*** hrou has quit IRC14:53
*** hrou has joined #openstack-swift14:54
notmynamegood morning14:54
mahaticgood morning14:57
wbhubergood morning14:57
notmynameit's fun reading all the overnight (to me) conversations14:58
notmyname:-)14:58
notmynameclayg: thanks for fixing my pep814:59
onovynotmyname, hi, https://review.openstack.org/#/c/192562/4/AUTHORS should i remove my name, as paul suggests? thanks14:59
*** haomaiwang has quit IRC15:00
notmynameonovy: have you contributed to swift at all before, perhaps with a different email address?15:00
onovyno15:00
notmynameonovy: so, first off, thanks for the patch :-)15:00
*** marzif has quit IRC15:00
onovyyour are welcome :)15:00
notmynameonovy: the AUTHORS update is fine15:00
onovyok, thanks15:00
*** haomaiwang has joined #openstack-swift15:01
notmynameonovy: normally I do it all at once right before a release like peluse said, but it doesn't really matter when it happens15:01
*** _hrou_ has joined #openstack-swift15:01
notmynameand it seems you've done it "right" (in the right order instead of appended as some people do, and there's no reason to update the .mailmap file) so it makes my job easier15:02
notmynameso it's great15:02
*** joeljwright has quit IRC15:02
notmynameonovy: that's an interesting feature. I like it15:03
notmynameonovy: how are you using swift today?15:03
*** aix has quit IRC15:03
*** maestro has quit IRC15:04
*** hrou has quit IRC15:04
*** hrou has joined #openstack-swift15:04
*** _hrou_ has quit IRC15:06
*** fthiagogv has joined #openstack-swift15:06
*** fthiagogv_ has joined #openstack-swift15:07
*** david-lyle has joined #openstack-swift15:09
notmynameonovy: ok, after looking at it more, I'm slightly less excited about it15:09
*** tsg has quit IRC15:11
notmynameI'll leave comments in gerrit15:11
*** proteusguy has quit IRC15:13
*** annegentle has quit IRC15:13
*** annegentle has joined #openstack-swift15:14
*** acorwin has quit IRC15:15
*** alpha_ori has quit IRC15:15
*** haomaiwang has quit IRC15:18
*** haomaiwang has joined #openstack-swift15:19
*** alpha_ori has joined #openstack-swift15:19
*** silor1 has joined #openstack-swift15:19
*** annegentle has quit IRC15:20
*** breitz has quit IRC15:21
*** blmartin has quit IRC15:21
*** breitz has joined #openstack-swift15:22
*** silor has quit IRC15:22
*** silor1 is now known as silor15:22
*** acorwin has joined #openstack-swift15:22
openstackgerritMerged openstack/swift: Fix Associated Projects link on Getting Started  https://review.openstack.org/20416715:24
*** proteusguy has joined #openstack-swift15:25
*** silor has quit IRC15:31
*** zaitcev has joined #openstack-swift15:35
*** ChanServ sets mode: +v zaitcev15:35
*** chmouel has quit IRC15:44
*** aix has joined #openstack-swift15:46
*** aix has quit IRC15:46
*** Guest23745 has joined #openstack-swift15:47
*** nadeem has joined #openstack-swift15:47
*** Guest23745 has quit IRC15:47
*** nadeem has quit IRC15:48
*** nadeem has joined #openstack-swift15:49
*** tsg has joined #openstack-swift15:49
*** chmouel has joined #openstack-swift15:51
*** DericHorn-HP has quit IRC15:51
notmynameonovy: review left15:51
*** agentle_ has joined #openstack-swift15:52
claygnotmyname: you can still be excited about a good idea that just needs a bit more work!15:53
notmynamewell, I feel very conflicted about that15:53
claygoic, you're only *slightly less* - so *still excited*15:53
claygheh - about the feature?  I haven't really looked at it - torgomatic commented "this is a good idea" - so I assume it's a great idea.15:54
notmynameyeah, that was my first reaction too15:54
notmynameI'm not forgeting some timestamp stuff we generate on the storage nodes, am I?15:55
*** aix has joined #openstack-swift15:55
notmynameI guess the reconciler does that now, right? but otherwise all timestamps are generated on the proxy, right?15:55
notmynameit's a great patch. small scope, docs (including manpages), tested functionality. I'm really happy about that15:57
minwoobclayg: Quick question about https://bugs.launchpad.net/swift/+bug/139359216:02
openstackLaunchpad bug 1393592 in OpenStack Object Storage (swift) "proxy doesn't error limit nodes on put" [Undecided,New]16:02
redboyeah, but object servers need to be fairly close.  like for rejecting GETs to expired objects and removing tombstones16:02
*** agentle_ has quit IRC16:03
notmynameredbo: ah, yeah. good point16:03
minwoobclayg: It looks like the change needs to be made to swift.proxy.controllers.obj -- not sure where you're getting that the GET responses are incrementing the errors properly.16:04
minwoobclayg: Perhaps I've been looking at the wrong module?16:04
*** rledisez has quit IRC16:04
minwoobclayg: (instead of swift.proxy.controllers.obj).16:05
*** blmartin has joined #openstack-swift16:09
*** gyee has joined #openstack-swift16:12
*** jistr has quit IRC16:19
*** breitz has quit IRC16:21
*** mahatic has quit IRC16:23
peluseclayg, thanks for the tests.... about to roll those in.  Refactored the ugly function quite a bit, am planning on moving the helpers out to module level as well to facilitate easier test coverage.  Will let you know when ready for another look16:25
*** breitz has joined #openstack-swift16:28
*** jordanP has quit IRC16:30
*** jlhinson has quit IRC16:33
*** DericHorn-HP has joined #openstack-swift16:34
*** DericHorn-HP has quit IRC16:35
*** ozone227 has joined #openstack-swift16:48
notmynamemeeting agenda for today is at https://wiki.openstack.org/wiki/Meetings/Swift. please update if you have other stuff to highlight, and check out is you have anything to report on16:48
*** ozone227 has quit IRC16:48
*** jasondotstar has quit IRC16:50
*** silor has joined #openstack-swift16:53
*** silor has quit IRC16:57
*** silor has joined #openstack-swift16:59
claygminwoob: idk, I thought there was a patch one time where I did something about making error limiting better - maybe that bug is invalid?17:01
claygpeluse: you're welcome - hope they're helpful - please squash them as I'll probably write more tests as I review17:01
claygpeluse: i saw the refactor and I think that's on the right track - all that function(state) stuff did make me thinking of method(self) :D17:02
*** wbhuber has quit IRC17:03
*** blmartin has quit IRC17:04
claygminwoob: 99d5018 maybe?17:04
*** tsg has quit IRC17:04
*** silor1 has joined #openstack-swift17:07
*** wbhuber has joined #openstack-swift17:07
*** silor has quit IRC17:10
*** silor1 is now known as silor17:10
*** hseipp has left #openstack-swift17:12
jith_Hi all, i have configured the swift (SAIO) for devstack and used the seperate swift for glance backend.. but in horizon->system information , all the services are getting listed but the ip address and Enabled status of swift is not there.. how to make enable in horizon?17:12
*** jasondotstar has joined #openstack-swift17:13
*** janonymous has joined #openstack-swift17:14
*** marzif has joined #openstack-swift17:15
*** jlhinson has joined #openstack-swift17:17
*** aix has quit IRC17:20
*** marzif has quit IRC17:25
*** marzif has joined #openstack-swift17:26
*** thurloat_isgone is now known as thurloat17:31
*** marzif has quit IRC17:31
*** marzif has joined #openstack-swift17:32
*** tab____ has joined #openstack-swift17:48
*** acorwin has quit IRC17:49
*** acorwin has joined #openstack-swift17:52
peluseclayg, you there?17:53
claygpeluse: sure17:53
peluseso on the test you added test_ec_get_disk_layout()... the reason for the various # of responses is the basic logic of how I go after 'more'.  Basically 2 rules17:54
peluse1) if any of the initial ndata come back with 404, the regular node_iter hunts down more17:54
peluse2) if they are all OK but I don't have enough etag sets, I go after parity nodes (all of them)17:54
peluseso your test has the first 10 all working OK (2xx) but one mismatched etag so I go after parity nodes, not hndoff since I don't suspect a handoff is oinvolved because there was no 40417:55
pelusemake sense sort of?17:55
peluseoh, 3rd rule.  if there are alternates reporte, I go after those if I didn't get enough good responses....17:56
*** jasondotstar has quit IRC17:57
claygpeluse: so... update the test?  Or... update the code?18:01
*** marzif has quit IRC18:02
*** mahatic has joined #openstack-swift18:02
peluseclayg, I would say test since getting 210 2xx codes back but not having a set should not force us to the handoffs, there's no reason to beleive we'd find something there but we can be certain by issuing nparity reqeusts we'll likely get another FI that can be used to rebuild18:03
peluseugh, not 210, just 1018:03
*** Kennan has joined #openstack-swift18:04
*** Kennan2 has quit IRC18:04
peluseas a code change though, I could not issue all nparity requests, just the number that I need?18:04
*** marzif has joined #openstack-swift18:04
peluseguess I should draw a flow chart to help everyone see which nodes we check when < ndata and why....18:05
claygpeluse: yeah I mean we could just issue requests to 2 x replica count nodes and then thow out stuff we don't need - but historically we've sort of tried to connect to just enough nodes to service the request - I think we tried roughly to carry that idea into EC?18:05
claygpeluse: I sort of imagine it'd be like while not have_enough_nodes(): connect_to_another_node()18:05
peluseclayg, yeah, right now if I need just 1 more I always go after nparity.  Easy enough to change18:06
claygpeluse: oh... ok - i'm still digesting the code - so I'm trying to understand by poking at its behavior with tests18:06
peluseI'll play with is a bit and see how it shakes out... will let ya know18:06
peluseand I sooooo appreciate it too!18:06
claygpeluse: yeah sure!  so but if you could squash in those tests (and you know change them so they work or are better or w/e)18:07
peluseI'l push a small update here soon, just moving the helpers to module level and probably this one tweak we just talked about18:07
claygpeluse: I'd just really like to have those test rigs in there as I review the change18:07
peluseOK, so how do I do the actual squash?  Right now i just copied and pasted into my patch18:07
*** marzif_ has joined #openstack-swift18:07
peluseor is that OK?18:07
claygpeluse: yeah that wfm18:08
pelusecoolio18:08
pelusethey're in there, will be in next push here shortly....18:08
claygnext time you push as long as when I git review -d I have all that StubResponse get_response with crazy_faked_out_logged_connections stuff I'm happy18:08
claygpeluse: cool no rush - I think I have notmyname's async container updaters on my review list today18:08
notmynameyay :-)18:09
claygmaybe some of kota's stuff from last night18:09
claygOMG - EFFING versioned writes - need that so much18:09
claygoh... and the meeting18:09
peluseyay, meetings18:09
claygpeluse: well it's a swift meeting18:10
claygpeluse: so it's roughly "hang out with my favorite peeps online and give notmyname a hard time" - which is kind of the best meeting18:10
notmynamealso, it's kinda what you do every day ;-)18:10
*** marzif has quit IRC18:11
*** marzif_ has quit IRC18:19
*** mahatic has quit IRC18:20
*** mahatic has joined #openstack-swift18:23
*** wbhuber has quit IRC18:25
*** agentle_ has joined #openstack-swift18:26
peluseclayg, heh... so the change to go after just the right number of parity nodes (how many short we are of an etag set) works like a champ w/o having to change the test code but I'll annotate the code to show what its checking for so its clearer18:26
*** silor1 has joined #openstack-swift18:34
*** wbhuber has joined #openstack-swift18:36
*** jasondotstar has joined #openstack-swift18:36
claygzaitcev: did you intend to merge commented asserts in https://review.openstack.org/#q,Ibab5c7605860ab768c8aa5a3161a705705689b04,n,z <- cschwede is keen to remove them in patch 20457518:37
patchbotclayg: https://review.openstack.org/#/c/204575/18:37
*** silor has quit IRC18:38
*** silor1 is now known as silor18:38
zaitcevclayg: I need to look, give me a moment18:38
claygzaitcev: I was about to approve, but IIRC I've been known to leave commented stuff in tests because it makes it easier to debug the tests later - normally with a comment like "# this is useful for debugging" bug probably not always18:38
mahaticjrichli, hey, sorry I had stepped out for dinner. I did download the code. Could you tell me a little more on the probe test?18:39
mahaticjrichli, "the purpose is to have an integrated test with the real encryption/decryption middleware and the crypto class." You mean the current unit test covers only the encrypter middleware and does not test crypto?18:40
claygmahatic: are you working on probetests for encryption!?18:40
mahaticclayg, :D that's the plan ;) I started looking at it. Any help would be great!18:41
jrichlithere are some tests for each piece individually : so for example, the unit tests against the encrypter only test the encrypter, and mocks the other pieces18:41
claygmahatic: did you by any chance setup encryption using the crypto branch -> https://github.com/swiftstack/vagrant-swift-all-in-one/tree/crypto18:41
claygit does all the footer middleware stuff for you and the like18:41
claygit'd be nice to have any crypto specific updates merged there to help other reviews of crypto come on board more quikcly18:41
mahaticjrichli, right. but the probe test is expected to test it all together?18:42
claygjrichli: didn't we have a prioirtized list of big ticket outstanding unresolved issues for encyrption?18:42
claygjrichli: I didn't think that probetests was on the top of the list?18:42
jrichliclayg: I didn't know that vagrant was out there.  thanks!  I can look into pointing it to the latest.18:42
mahaticclayg, nope. I just downloaded the code from here: https://review.openstack.org/#/c/203454/18:43
jrichliclayg: There is a list of outstanding issues.  The problem is, there is design that has to happen in the high priority issues.18:43
claygmahatic: right so the code doesn't work unless you do the configuration stuff - the crypto branch can help you - or i'm sure jrichli has written down somewhere how to do it by hand18:43
claygjrichli: stupid design18:44
claygjrichli: where's acoles when you need him18:44
clayg@channel - does anyone in here know how to design software!?18:44
jrichli:-)  Yes, I think we can get more movement on some of those items when he returns.18:45
mahatic:)18:45
jrichlilol18:45
jrichliclayg: I am starting to take a stab at real footer support, but it will be challenging for me18:45
claygjrichli: you got this ;)18:45
jrichlithx!18:46
zaitcevclayg: commented on patch 20457518:47
patchbotzaitcev: https://review.openstack.org/#/c/204575/18:47
jrichlimahatic: It's probably best to start on the config and get encryption working on you SAIO.  We will make sure you get the same results when running functsts18:47
claygzaitcev: oh lol - they weren't even your commented assertions18:48
claygzaitcev: goodness - I just pass the buck to the first core in the blame :P18:48
zaitcevclayg: no, they were18:48
zaitcevclayg: but probably bitrotted by now18:48
claygzaitcev: ok cool - so let's pull 'em!18:49
claygzaitcev: thanks!18:49
mahaticjrichli, sure. Now that I downloaded the code, any doc or something that points to config stuff?18:49
claygmahatic: *ahem* crypto branch of vagrant-swift-all-in-one </shameful-plug>18:49
mahaticjrichli, or clone it from the vagrant one?18:49
*** silor has quit IRC18:50
jrichlimahatic: look at etc/proxy-server.conf-sample - and follow the instructions for adding the new middleware18:50
mahaticclayg, lol. you also pointed that jrichli would have something, I was just checking18:51
jrichliplus, add "fake_footers" middleware with "use = egg:swift#fake_footers"18:51
jrichliso the additions to the pipeline are:18:52
jrichlidecrypter trivialkeymaster encrypter fake_footers - and put those between dlo and proxy-logging18:52
claygjrichli: when you lay it all out like that it seems silly to have a whole branch *just* for that :\18:54
jrichliclayg: maybe there will be more later :-)18:54
claygjrichli: that's the ticket!18:55
mahaticjrichli, can I have your config file? a paste?18:56
jrichliok, one min18:56
openstackgerritpaul luse proposed openstack/swift: Add ability for GET path to see/select alternate frag archs  https://review.openstack.org/20128318:58
jrichlimahatic: this version sets DEBUG level logging for the new middleware http://paste.openstack.org/show/400888/19:00
*** jlhinson has quit IRC19:01
*** jlhinson has joined #openstack-swift19:01
*** mahatic_ has joined #openstack-swift19:12
*** changbl has joined #openstack-swift19:12
*** mahatic has quit IRC19:13
*** mahatic has joined #openstack-swift19:14
claygcan anyone else try to help out david on lp bug #147722919:17
openstackLaunchpad bug 1477229 in OpenStack Object Storage (swift) "Adding proxy-logging to the pipeline is not enough for access logging" [Undecided,New] https://launchpad.net/bugs/147722919:17
claygI feel like I keep saying - no dude what you're saying makes no sense; this works for everyone; need more info - and he's like - yeah it's totally broken, so do whatever you want19:18
*** mahatic_ has joined #openstack-swift19:19
*** mahatic has quit IRC19:20
mahatic_jrichli, okay done19:21
jrichlitry running the functests and see how many errors and failures you get19:21
mahatic_sure19:22
mahatic_jrichli, Entry point 'decrypter' not found in egg 'swift'  - what i get when do a startmain. I do have a an entry in proxy-server.conf19:27
mahatic_am I missing something?19:27
jrichlidid you run 'sudo python setup.py develop' and 'sudo python setup.py install' before trying to run?19:28
mahatic_jrichli, some issue there. Just noticed19:30
mahatic_proxy stuff19:30
jrichliwhat is the error?19:32
mahatic_no, this proxy is internal, intel. I'm running them again19:33
*** jasondotstar has quit IRC19:36
jrichliclayg, mahatic_ - speaking of internal, eventually you will also add this new middleware to the internal client pipeline.  But you can do that later.19:37
claygjrichli: heh - yeah good point - i mean it depends on the keymaster right?19:38
claygjrichli: like some keymaster may require a user token to get a key right?  like public access to encrypted objects won't work?19:38
claygjrichli: or are we not going to have keymasters like that?19:38
jrichliclayg: I still dont know much about how the internal client is used (other than it making internal requests in general)19:40
glangewe use it for log processing19:40
jrichliclayg: as for the keymaster needing a token, that depends.  the keystone token can be used19:41
jrichliglange: ok, thanks.  Is it also used for other things?19:42
glangenot sure, maybe some little tools that people have written, but the only big thing is log processing19:44
notmynameno internal client usage in container sync?19:44
hroustorlets use it ; )19:45
glangeyeah, looks like it is in there, but I assumed jrichli knew about all the swift codebase uses :)19:45
glangejust grep!19:45
jrichliglange: bad assumption :-)19:46
glangehaha19:46
glangestep 1, grep swift codebase!19:46
notmynameleaping to conclusions is more fun19:46
jrichliglange: yes.  i haven't been focused on digging into the internal client use yet19:46
jrichliglange: just figured i'd ask while we were on the topic19:47
glangeok19:47
glangewe use it sort of like notmyname's internal_proxy in https://github.com/notmyname/slogging19:47
jrichliand, now I know storlets use it - which will mean it needs the middleware19:48
notmynameglange: which was the exact same thing at one point ;-)19:48
*** fthiagogv_ has quit IRC19:58
*** marzif_ has joined #openstack-swift20:05
*** jasondotstar has joined #openstack-swift20:12
claygsince when does replication pick up a .data file delction without a hash invalidation?20:20
claygthe every-so-often do_listdir is for the suffix dirs - to make sure the keys in the hash match the dirs in the part20:21
openstackgerritHamdi Roumani proposed openstack/swift: Updated tox setup instructions on Development Guidelines  https://review.openstack.org/20474920:26
mahatic_jrichli, functests -> FAILED (SKIP=12, errors=78, failures=34) ^20:29
jrichlithat is more than what I get, so something is wrong20:30
openstackgerritCarlos Cavanna proposed openstack/swift: Improving statistics sent to Graphite.  https://review.openstack.org/20265720:30
mahatic_hmm, what's expected?20:31
jrichlimahatic_: I will give you a link to a paste with the list of expected problems.  you can look into some that aren't on that list to find out what's going on20:31
mahatic_sure20:31
jrichlimahatic_ : http://paste.openstack.org/show/401160/  has the expected errors/failures20:35
mahatic_jrichli, looking, thank you20:37
mahatic_jrichli, off to bed, will dig in tomm. thanks for the pointers!20:37
*** jasondotstar has quit IRC20:38
jrichlimahatic_: ok.  np!  good night20:38
*** fthiagogv has quit IRC20:40
*** mahatic_ has quit IRC20:43
*** jeblair is now known as CarolChanning20:45
*** CarolChanning is now known as jeblair20:45
*** ho has joined #openstack-swift20:48
hogood morning!20:50
mattoliverauMorning20:52
claygwe doing this thing!?20:53
*** hrou has quit IRC20:53
homattoliverau: morning!20:53
janonymouso/20:54
claygi know that eventlet greenthreads aren't racy like os threads wrt to statements like "a += 1" because of "cooperative" yielding and all that20:55
claygbut... pyhton has a thing with syncronization that will let you do atomic increments right?20:55
claygI thought it was collections.Counter - but that's totally a different thing20:55
redbow/in 320:56
claygohhh.. maybe itertools.count()20:56
*** agentle_ has quit IRC20:57
*** tongli has quit IRC20:57
*** tongli has joined #openstack-swift20:57
*** blmartin has joined #openstack-swift20:58
clayggd, if zzzeek doesn't know https://twitter.com/zzzeek/status/9989967126215065620:58
*** kota_ has joined #openstack-swift20:58
*** ChanServ sets mode: +v kota_20:58
*** blmartin has quit IRC20:59
kota_morning20:59
*** blmartin has joined #openstack-swift20:59
mattoliveraukota_: morning20:59
hokota_: morning!21:00
notmynamehello. last meeting just ended21:00
notmynametime for swift meeting in #openstack-meeting21:00
*** DericHorn-HP has joined #openstack-swift21:03
*** agentle_ has joined #openstack-swift21:08
claygoh man I don't think it is safe - and weirdly - it goes to fast?!  https://gist.github.com/clayg/d3630eeb3b6b680d631a21:08
*** tab____ has quit IRC21:12
*** david-lyle has quit IRC21:17
*** marzif_ has quit IRC21:25
*** geaaru has quit IRC21:27
*** hrou has joined #openstack-swift21:30
*** tongli has quit IRC21:37
*** tongli has joined #openstack-swift21:37
*** agentle_ has quit IRC21:43
*** tongli has quit IRC21:46
*** annegentle has joined #openstack-swift21:46
*** tongli has joined #openstack-swift21:46
*** jkugel has quit IRC21:46
*** tongli has quit IRC21:48
*** thurloat is now known as thurloat_isgone21:52
*** Nyny has joined #openstack-swift21:58
NynyHello, it's possible to hide XML list file?21:58
*** aerwin has joined #openstack-swift22:00
notmynameNyny: not sure I understand that question22:01
mattoliverauk, breakfast time. bbl22:01
tdasilvai'm guessing that's an apple swift question22:01
*** jasondotstar has joined #openstack-swift22:01
notmynameoh! maybe22:01
notmynameNyny: are you talking about the iOS programming language?22:01
MooingLemurunless container listing in format=xml22:01
notmynameNyny: we work on openstack-swift. the object storage system22:01
*** Kennan has quit IRC22:02
Nynyyes i speak about that, i have object storage on a provider and i would like to hide XML file that list all file in my container22:02
tdasilvasounds like austin hackathon agenda is going to be packed22:02
hoclayg: yesterday, I got your comment for patch 202411. I would like to have more comments which parts are wrong. I think you pointed out is not only the file name but alsomatrix testing???22:03
patchbotho: https://review.openstack.org/#/c/202411/22:03
*** Kennan has joined #openstack-swift22:03
claygho: maybe the matrix just needed some comments - which keys are what22:03
claygho: yeah giventhe option of a file named test_account_access_control.py and test_axc.py - I always prefer the one that means something.22:04
*** blmartin has quit IRC22:05
hoclayg: There are some comment on the patch L21-L47. kind of this?22:05
Nynynotmyname : hide this : http://goopics.net/data/532o87.png22:05
*** jrichli has quit IRC22:05
hoclayg: And L21-51 is correct one.22:06
claygho: oic - yeah just move that closer to the definition22:06
MooingLemurNyny: depending on the X-Container-Read setting, I suspect you just need to remove .rlistings22:06
claygho: another option is use dictionaries - since they're self documenting22:07
claygho: either way it's an amazing matric - so many scenarios!22:08
*** aerwin has quit IRC22:09
hoclayg: I used dic for my first version but a line become too long so i decided to use tupple and list then convert it to dic for a line.22:09
claygho: but it looks like some of the values are always None?22:09
Nynyok thanks im going to look for22:09
hoclayg: yeah, i thought it might use in the future. i have no plan to use "account_name" so far because it's decided by keystone.22:10
claygho: yeah idk, that's the thing that DAMP is talking about - DRY code is not about saving lines, it's about maintainability - I feel like a dictionary where un-used keys can be omitted would be easier to read/understand - and therefore - easier to maintain - but it's just a though22:10
hoclayg: i see. today i will finish to write the other functional test for container acl after that if account_name is not used, i will remove it.22:12
claygho: up to you - whatever feels like it will be easist to review/maintain - use your best judgement - just thowing out something to think about - thanks for working on this22:13
hoclayg: thanks for the comments. I will think about it :-)22:14
claygI've had this thing happen to me - and antadotically other software engineers have confessed it's a shared experience - where you start with two things and recognize they can be generalized to a common base with some paramaters or subclasses - whatever ...22:15
claygthen you have more things - eventually maybe half a dozen things thare are all basically variations of this common base that keeps getting smarter and smarter22:16
clayg... then finally you add the next thing and it starts getting complicated - eventually to the point where your generalized thing is special casing one off options just to support one of it's dependents22:16
*** wbhuber has quit IRC22:16
clayg... eventaully you have to break it up - pull it back apart into seperate things that you can maintain individually22:17
clayg(we sort went though this with some of the DiskFile and ObjectController stuff in swift)22:17
claygtaking the duplicate code and making it DRY has a good name - but taking the generalized code and pulling it apart (to my knowledge) - doesn't have a name?22:18
*** jasondotstar has quit IRC22:18
*** jlhinson has quit IRC22:18
NynyMooingLemur: remove .rlistings from the container?22:19
claygmaybe someon who's read gang of four more througly can remind me of a concept i'm forgetting?22:19
Nynyit's a file?22:19
claygNyny: it's an option to X-Container-Read-Acl22:20
notmynameNyny: do you want to get rid of one item or are you wanting to turn off the listing entirely?22:20
claygNyny: do you have the container set to be publicly accessible?  ".r:*"22:21
Nynyjust turn off the listing22:21
dfg_clayg: i found my saio problem. it was that my python-six was too old. and pip wouldn't upgrade it because it had been isntalled by the system or something. i had to apt-get remove python-six and then pip install it and it worked.22:21
Nynyyes i have a public container accessible by anyone22:21
claygdfg_: YOU'RE AWESOME - thanks for the report!22:22
hoclayg: yeah, I'm in front of complexity. gang of four sounds like peple who made 20? design patterns22:22
claygdfg_: does that mean you're up and running on *precise* !?22:22
claygho: yeah that's the stuff!22:22
dfg_clayg: ya i guess. you do feel less safe?22:22
dfg_do you22:22
claygdfg_: I live in constant terror that dfg_ might get swift working on precise22:23
dfg_:)22:23
clayglol22:23
claygok - so itertools.count - not thread safe - terrible22:24
claygback to testing when async container updates cause observalbe incosistencies in the container listings22:24
* notmyname lives in constant terror that clayg will review his code22:25
hoclayg: maybe "Patterns and Antipatterns" (Andrew Koenig)22:25
notmyname(but it's better for it)22:25
claygnotmyname: gholt was the worst - you could do something that is by all accounts pretty decent working testing and documented code22:26
*** jasondotstar has joined #openstack-swift22:27
claygnot only would he find half a dozen nits that you are terribly embarassed for submitting - but bugs - over and over again he'd point out my BUGS22:27
clayg:'(22:27
claygdefinately better for it22:27
notmynameyes. it happened to me too :-(22:27
* clayg misses gholt22:28
claygomg is swift client not green :'(22:33
claygguess I'll need that thread safe counter after all22:33
*** jasondotstar has quit IRC22:33
*** minwoob has quit IRC22:36
notmynameclayg: wehre are you seeing that?22:36
Nynyif X-Container-Read is not set, container listing access is public?22:37
notmynamehttp://logs.openstack.org/50/89250/111/check/gate-python-swiftclient-python26/0153d6f/testr_results.html.gz ?22:37
claygnotmyname: i have a script where I tried to make a swiftclient.Connction in a gt and it's not patched - i guess if i monkey patched it it would just work?22:38
claygoh oh - green like eventlet green22:38
notmynameah ok22:38
claygnotmyname: :p22:38
claygNyny: container listing access is NOT public22:38
claygNyny: unless you're not running auth?22:38
claygNyny: some auth systems' responses will include a Set-Cookie header - so if you're passing auth via your web browser I don't think there's a super great way to dissallow it22:39
claygbut if you don't have a read acl set and you get that xml in the browser you should verify real quick that visiting that url in a private browser session will 4XX22:40
Nynymy provider run with auth22:41
Nynyi try with private browser session, file listing still public22:42
claygsounds like acl or no auth to me22:42
claygNyny: can you check other containers?22:42
claygNyny: do you *want* the objects to public and just not the listing?  how did you accomplish this if not acls - most auth systems limit all requets to private authenticated users - so what's going on?22:43
Nynypublic objects (when i create container on my provider panel, i select "public container"), hide listing22:44
clayghrm....22:45
*** DericHorn-HP has quit IRC22:45
claygNyny: i don't get it - start validating things with curl22:47
claygNyny: when the web doesn't make sense - you've always got curl22:47
clayglong live curl22:47
claygzackmdavis: I don't want to hear about httpie22:48
torgomaticcurl means never having to say "wait, what requests was that sending again?"22:48
notmynametorgomatic: except for unicode ;-)22:48
notmynamebut thats the shell/terminal that's being "helpful"22:49
torgomaticwireshark means...22:49
claygI get it that ascii wasn't going to cut it - but we could have stopped with utf-8 - just been like "nope, that's enough with the charaters"22:49
zackmdavisclayg, I've never used httpie; did you mean to tab-complete someone else's name?22:49
claygzackmdavis: oh - sorry - i guess when I think of the kids new "interesting" hipster tools I think of zackmdavis22:50
zackmdavisclayg, buuuuut now that you mention it, this looks pretty cool https://github.com/jkbrzt/httpie; maybe I'll try it22:51
claygLOLLO22:51
claygi *just* said to myself "i get he'll go try it now"22:51
claygs/get/bet/22:51
*** DericHorn-HP has joined #openstack-swift22:51
claygzackmdavis folks, a scolar and a commedian - it's like torgomatic but without the jolly santa claus vibe22:52
*** DericHorn-HP has quit IRC22:53
torgomaticmy beard doesn't have *that* much gray in it22:53
torgomaticprobably22:53
claygnotmyname: ok in a trival test default is golden and 0.01 is observable pretty quickly :)23:01
claygthis contaienr has ~20K rows in it23:02
notmynameyay23:02
claygit's just a development environment - but the idea I think that we can go pretty low and be fine as long as we don't turn off the waiting is pretty solid23:02
claygnice work!23:02
hoall, in the meeting jrichli said acoles is going to back next week..., is he in vacation now?23:04
claygho: not really - I think he's like doing his job or something?23:05
openstackgerritSamuel Merritt proposed openstack/swift: functests: use assertIn and assertNotIn  https://review.openstack.org/20478523:06
hoclayg: thanks! now i understand the reason why i can not get in touch with hime :-)23:06
claygtorgomatic: man you're all about the death to python 2.623:06
torgomaticclayg: yeah, I do stuff like that when I get hung up on other problems. Feels like progress toward *something* at least.23:07
Nynycontrol list (ACL) is is that? http://goopics.net/i/532o8723:07
torgomaticI didn't notice it until I reviewed janonymous's patch to use assertTrue instead of assertIn; a lot of those assertions were pretty stupid-looking if you didn't have to worry about 2.623:08
claygnotmyname: nice23:08
claygNyny: no it's in the headers - not the body23:08
claygchrome and firefox both have nice tools to inspect the requests if you'd rather than that curl it might get you along the way23:09
*** thurloat_isgone is now known as thurloat23:09
Nynyset .rlistings in the header?23:10
Nynyto remove listing?23:11
Nynybooleen value?23:11
claygNyny: http://docs.openstack.org/developer/swift/misc.html#acls23:11
claygX-Container-Read is the header name, and the value is a csv with a weird arcane syntax23:12
*** km has joined #openstack-swift23:12
claygnotmyname: 500ms looks like the magic number23:12
claygnotmyname: well.. that's pleanty anyways - what did you go with 100ms?23:13
notmynameho: clayg: he was doing other HP stuff, but I think he's on vacation right now23:13
claygnotmyname: ah no 1000ms - perfect23:13
claygnotmyname: oh he is - nice work acoles_away !23:14
notmynameclayg: what's magic about 500ms?23:14
torgomaticshould be 1024ms; people won't question your made-up numbers if they're powers of 223:14
notmynameI chose 1s because, we'll it's probably in the goldilocks zone for the behavior23:14
hoclayg: +1 for acoles_away's vacation :)23:15
claygand an underpowered swift all in one trying to find a inconsistent listing after a successful PUT - it's just hard to do with a 500ms container_update_timeout23:16
claygnotmyname: 1s is goldilocks for smoothing out the update timeouts when the container go to eat the .pending?23:16
notmynameah, cool23:16
claygnotmyname: i forget what I did to test the container - oh yeah I had a timerouter_server.py23:17
claygnotmyname: let me try that again one more time, double check tests and put up the review - looks good23:17
notmyname1s is a guess. it's shorter than 3 and "reasonable" for being good enough for functionling systmes23:17
notmynamemostly I chose it because I didn't want the bikeshed about what it should be ;-)23:18
claygnotmyname: ok - well I think your intuation was good23:18
claygnotmyname: well - let's see23:18
*** jrichli has joined #openstack-swift23:19
NynyMy X Container Header : X-Container-Read: .r:*,.rlistings, how curl request to remove rlistings?23:20
claygcurl -H 'x-auth-token: <your-token>' https://<your-storage-domain>/v1/<your-account>/<your-continer>/ -XPOST -H 'x-container-read: .r:*' should do it23:22
claygis the trailing comma in the header?  is that the last value?  you have to write the whole acl you want as it will overwrite what's there23:23
*** jasondotstar has joined #openstack-swift23:25
Nynyit works thanks !23:27
claygNyny: do you think that's something you could help your provider change the default behavior with?23:28
claygNyny: or as a user of swift is there somewhere you originally looked for documentation on how to use the acl api that could have included more inforatmion about this topic?23:29
claygNyny: neway - glad you got it sussed - happy to help23:29
*** jlhinson has joined #openstack-swift23:31
NynyOn my provider panel im allowed to create different profil container : private, public and static, anyone have a different comportment23:31
Nynyjust public have rlistings by default23:32
claygi wonder what static is?23:32
claygnotmyname: ^ do you have any idea which provider this is?23:32
Nynyfor website, heberg static content23:32
Nynycss, img, js23:32
Nynyoptimize for, i thinksx23:33
claygNyny: maybe that's public w/o listings?23:33
Nynyprobably23:33
*** jlhinson has quit IRC23:33
notmynamenope23:33
hoclayg: sounds like hp's cloud.23:33
notmynameno, HP has "private" and "public" only23:34
hoclayg: they provide staticweb with CDN.23:34
Nynymy provider : http://www.ovh.com/fr/cloud/storage/object-storage.xml23:35
honotmyname: i see.23:35
notmynameah, ovh23:35
claygNyny: awesome!23:35
Nynyawesome? you like it?23:35
hogreat! ovn has OpenStack logo.23:36
notmynameovh actually has a pretty big swift deployment23:36
claygNyny: I like everyone who's using the open source storage engine built for the web - death to our amazon overloads23:36
claygI say as my kids are watching prime in the other room and I'm tying into a irssi screen running on a ec2 instance23:36
claygbut w/e23:37
notmynamelol23:37
*** kei_yama has joined #openstack-swift23:37
notmynamerunabove (a subsidiary of ovh) has the same thing: http://d.not.mn/runabove_container_type.png23:37
claygmattoliverau: dfg_: you think I could get some of that free rackspace could action?23:38
claygnotmyname: so *is* static public w/o the listings?23:38
notmynameoh, wow. "static" is a lot more than that (haven't checked acls yet)23:38
claygcause that would make a lot of sense acctually23:38
claygoic - k nm23:38
notmynameit has a whole bunch of default css/html/png files that populate it by default23:39
claygomg crazy - neat tho23:39
claygi love it when people build cool stuff on swift!23:39
notmynamestatic.AUTH-85633419797e494a8b0184a846a9bd4f.storage.bhs-1.runabove.io23:39
notmynamethat's the one I just created23:39
notmynamelook familiar? ;-)23:39
notmynameimportantly, check out what's in it23:39
Nyny+notmyname: what it it?23:40
notmynamebut it doesn't have staticweb set up!23:40
notmynamehttp://static.auth-85633419797e494a8b0184a846a9bd4f.storage.bhs-1.runabove.io/index.html23:40
notmynameNyny: that's a normal swift container listing23:40
notmynamethe xml23:40
notmynamewell, it's xml instead of plaintext or json23:40
claygnotmyname: browsers love to accept the xml23:41
notmynameoh yeha23:41
notmynamethat's why23:41
clayghttp://static.auth-85633419797e494a8b0184a846a9bd4f.storage.bhs-1.runabove.io/?format=json23:41
claygthis is FUN!23:41
claygSWIFT IS SO COOL!23:41
notmynameyup23:41
notmynamelol23:41
notmynamethis is why I sign up with all the swift hosters ;-)23:41
notmynameok, let me dig my creds out and see what the acls are23:42
claygnotmyname: thanks for doing that - it's a hoot to see what people are building out of this little project we get to play with23:42
notmynameno kidding! :-)23:42
Nynyon ovh.com, my static container don't have a file listing23:43
claygi really like the dns stuff - i wish I had a good idea how to productize that for people - it's a great integration feature23:43
Nynyand he directly redirect to the index like an heberg storage23:43
claygnotmyname: but like what are we gunna do - "yeah just give us creds to your bind servers and we'll write our you zone files - it'll be cool - trust me"23:43
Nynyexept if i failed x)23:44
notmynamehere's that container from runabove https://gist.github.com/notmyname/5c272e72acfb06d10d2123:45
notmynamecool. they're setting up staticweb, CORS, ACLs, and the default obejcts23:45
Nynyyes you've right, static content make an xml listing, my mistake23:45
notmynamewhy isn't staticweb working there?23:45
Nynywhat's the use of ".r:*" in the header?23:46
notmynameNyny: makes it public23:47
*** jlhinson has joined #openstack-swift23:47
notmynamethe long-form is ".referer:*" which means that any referer header is allowed, ie public23:47
Nynyha ok, ty23:47
claygnotmyname: idk, maybe the middlware isn't in the pipeline?  seems like they're setting up all the headers?23:47
notmynameto the SAIO, batman!23:48
mattoliverauclayg: sorry been in a meeting and about to head into another, I'll try and find someone to ping about that ;)23:51
notmynamehmm...works for me on the SAIO23:52
notmynamegives me index.html23:52
notmyname404 if index.html isn't found23:52
Nynyand what do you think about the OVH Object Storage price versus competitor (like amazon)? 0,01e per Go storage and 0,01e per Go output bandwidth23:52
claygnotmyname: i'd say it's not in the pipeline23:53
claygnotmyname: it generates extra requests sometimes - they might have pulled it23:53
notmynameclayg: it's in /info23:54
honotmyname, clayg: http://gaul.org/object-store-comparison/23:54
claygnotmyname: oh23:54
*** dmorita has joined #openstack-swift23:55

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