Wednesday, 2016-03-16

*** openstack has joined #swift300:26
*** lyrrad has quit IRC00:50
openstackgerritTim Burke proposed openstack/swift3: run functional tests with 's3v4' enabled  https://review.openstack.org/27251604:03
timburkekota_: looking at http://logs.openstack.org/78/285678/1/check/gate-swift3-tox-keystone/7e3256c/console.html#_2016-03-15_11_32_01_021, the 5 failures are all resolved by https://github.com/boto/boto/pull/3176, and the error by https://github.com/boto/boto/pull/351304:07
timburkelooking at the canonical request (http://logs.openstack.org/78/285678/1/check/gate-swift3-tox-keystone/7e3256c/console.html#_2016-03-15_11_32_01_019) -- basically, x-amz-meta-bar2 should sort *after* x-amz-meta-bar, not before, and the host header should be localhost:8080, not localhost:8080:808004:10
kota_timburke: awesome!04:46
kota_timburke: Do we have no way to enable v4 auth via boto args?04:48
kota_looking at patch 27251604:49
patchbotkota_: https://review.openstack.org/#/c/272516/ - swift3 - run functional tests with 's3v4' enabled04:49
kota_or might be useful via os.environ at TestCase init?04:52
kota_IMO, if swift3 can handle both (v2 and v4) at the same time, i think we can merge the tox env and run all functests via both or them.04:53
kota_though, we should update the keystone constraint before we do that.04:54
timburkekota_: ...maybe? the only way i've done it locally is via ~/.boto config file. agreed though, for the purposes of testing in the gate, it'd be better to cover both auth options. although we may need to create a @skip_v4 decorator to skip the current failures (since those two PRs aren't merged yet)05:07
kota_timburke: \o/05:08
timburke(well, the config file and the env variable, via the keystone_s3v4 tox env)05:08
timburkei also submitted https://bugs.launchpad.net/swift3/+bug/1557260 as part of all of this05:09
openstackLaunchpad bug 1557260 in Swift3 "Swift3 functests should transition to using boto3" [Undecided,New]05:09
timburkejust figuring that boto3 is more likely to receive fixes05:10
kota_timburke: i know, it's great.05:10
kota_thanks!05:13
timburkeok, i'm up to 12 drafts comments (one of which still warrants follow-up; aside from that, lots of questions, no major issues) and a 70-ish line diff for my follow-up patch. i'm going to bed, will try to actually publish tomorrow05:43
kota_hmm... I got 67 errors when I ran 'tox -e keystone_s3v4' :/07:51
kota_looks like all of errors are 403 forbidden so I cannot authorize via the script... I don't get anything yet.07:52
kota_maybe some constraints for running well seems still not enough.07:53
kota_calling, IRC meeting will be held in March 16th (today/tommorow in your time).09:48
*** acoles_ is now known as acoles09:48
kota_it's still 21:00 UTC, please be careful for the time changed (PST->PDT)09:49
kota_If you have something to bring up, please add your agend to https://wiki.openstack.org/wiki/Meetings/swift309:50
*** openstackgerrit has quit IRC09:53
*** openstackgerrit_ is now known as openstackgerrit09:53
*** openstackgerrit has quit IRC09:53
*** openstackgerrit_ has joined #swift309:54
*** openstackgerrit_ is now known as openstackgerrit09:54
*** openstackgerrit_ has joined #swift309:55
*** openstackgerrit has quit IRC09:55
*** openstackgerrit has joined #swift309:56
kota_hmm... my local setup looks failed at keystone setup...11:01
*** openstackgerrit has quit IRC11:18
*** openstackgerrit has joined #swift311:18
kota_the diff from gerritt looks just versions of webob, wheel, oslo.messaging...11:29
*** georgem1 has joined #swift313:01
kota_looks like pki_setup failing but I'm wondering why it does. old keystone and new keystone at gerrit work. only new keystone at my local failed...14:09
*** georgem1 has left #swift314:11
kota_ugh...openstack command looks failed to get the tenant list /and create with 401 Unauthorized.14:31
kota_seems like more environ variable for that?14:31
kota_needed14:31
timburkekota_: were you still using patchset 6 from patch 272516? try patchset 7; the diff is just https://review.openstack.org/#/c/272516/6..7/swift3/test/functional/conf/keystone.conf.in16:11
patchbottimburke: https://review.openstack.org/#/c/272516/ - swift3 - run functional tests with 's3v4' enabled16:11
patchbottimburke: patch 272516 - swift3 - run functional tests with 's3v4' enabled16:11
timburkea few commits relevant to that 401: https://github.com/openstack/keystone/commit/37e9d6b (need to explicitly set admin_token), https://github.com/openstack/keystone/commit/5286b4a (admin_token_auth deprecated)16:20
timburkehttps://github.com/openstack/keystone/commit/a14d761 (admin_token_auth undeprecated), https://github.com/openstack/keystone/commit/d446e15 (added `keystone-manage bootstrap` command)16:21
*** acoles is now known as acoles_16:31
*** lyrrad has joined #swift316:34
*** acoles_ is now known as acoles16:47
*** chsc has joined #swift317:46
*** acoles is now known as acoles_19:52
*** acoles_ is now known as acoles20:30
*** acoles is now known as acoles_20:31
*** mattoliverau has quit IRC20:59
*** matt6434 has joined #swift320:59
*** matt6434 is now known as mattoliverau21:00
kota_timburke: that looks what I am looking for!21:02
kota_timburke: setup looks runnning well now, still waiting the result.21:02
*** acoles_ is now known as acoles21:02
timburkekota_: you may still get those 5 failures and 1 error. you'll want to either pip install boto from git, or just manually edit it in the tox env21:07
*** acoles is now known as acoles_22:02
kota_timburke: alright, 5 failures and 1 error I finally reached at you22:34
timburkewhich means there's 60+ passes :-)22:46
timburkealso, the logging in the failures verifies that we're using sigv422:46
kota_oh23:01
kota_logging broken?23:01
kota_hello meeting23:01
kota_looks like timburke was here.23:05
timburkehi kota_!23:05
kota_timburke: thank you so much to test/review the sigv4 patch!23:05
kota_timburke: I just in time sent an E-mail for Andrey including you in c.c.23:06
timburkesure! apparently we've finally gotten enough demand for it from customers that i could make it a real priority23:06
timburkethanks for that; i don't typically follow the mailing list much23:06
timburke(i suppose i should fix that)23:07
kota_alright, sounds good.23:07
kota_yeah, but I also had fault that I've been pending a lot of patches (including yours!) :/23:07
kota_so sorry...23:08
timburkeno worries on mine; i still need to get the tests passing. just haven't found time :(23:09
kota_yup, we should review a lot accross over projects (i mean, swift/swift3/swift-client, etc...)23:10
kota_recently, pyeclib also, storlets also on my side...23:10
timburkewheee!23:10
kota_hehe, and we need to land the encryption at crypt branch by summit :)23:11
timburkeyeah, i've been trying to load that in my head, too. then i get distracted again23:11
kota_:)23:12
timburkeit'll be nice for swift3, though; we can get server-side-encryption moving!23:12
kota_yup23:12
kota_timburke: so anything updates else from you?23:14
timburkenot really. mainly doing reviews23:14
kota_ok23:14
kota_from myside, a few things.23:14
kota_I think sigv4 staff is already we know and it's in reviewing/talking via E-mail so nothing special here if noyone else is here.23:16
kota_s/noyone/no one/23:16
kota_and one more23:16
kota_for dependency updates23:16
kota_while reviewing the sigv4 patch(and trying to solve environ issue), I've been realizing we need update some dependency/scripts/API's soon.23:17
timburkei think i'm in favor of waiting for a mitaka release from Keystone before updating there. not sure how aggressive we want to be about upgrading swift, though23:18
kota_e.g. current gerrit functional gate is against to swift-kilo and older Keystone than kilo23:18
timburkei thought it was a kilo keystone as well, just early kilo23:19
kota_yup, it fits my opinion and it make me to get headack sigv4 needs newer keystone.23:19
kota_and looks like pki_setup (included setup_keystone script) and v2 api deprecated23:20
kota_not look at in detail, just saw a few notes, conversations online.23:20
kota_v2 means keystone v2 api23:21
timburkeah, thanks :)23:22
kota_timburke: and also boto you suggested :)23:22
timburkespeaking of setup_keystone, i think we'll probably want to add a `set -e` toward the top; it should make it more obvious when our setup has gone bad and keep us from wasting time running a bunch of tests that will fail23:22
kota_looks good23:24
kota_alright, for now, I don't have strong opinion for this, but still worried about the env migration so it seems good time to consider to bump them past mitaka release.23:27
kota_timburke: thanks for your feedback :)23:27
timburkeyeah, that sounds good to me23:27
kota_that's all for me.23:28
timburkeme too. which works well; i've got to pick up my daughter :-)23:28
kota_timburke: thanks for joining, my daughter is playing by me at sofa23:30
kota_:-)23:30
kota_timburke: have a good time with her :)23:30
timburkeyou too!23:31
openstackgerritTim Burke proposed openstack/swift3: Signature v4 follow-up  https://review.openstack.org/29376023:32
*** chsc has quit IRC23:32
timburkeok, review's posted :) now i'm actually leaving23:35
notmynamegive account = AUTH_foo and container = my_c and my swift hostname as foo.bar, I'd use http://foo.bar/v1/AUTH_foo/my_c to do swift API requests23:58
notmynamewhat would I use for swift3 requests?23:58
notmynameAUTH_foo.foo.bar/my_c?23:59
notmynamemy_c.AUTH_foo.foo.bar?23:59

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