Monday, 2018-08-13

*** ejat has quit IRC00:59
kota_enjoy notmyname on your vacation01:19
kota_good morning the world01:19
mattoliveraukota_: morning01:59
*** psachin has joined #openstack-swift02:44
kota_mattoliverau: o/02:55
*** viks_ has joined #openstack-swift04:47
*** rcernin has quit IRC04:54
*** rcernin has joined #openstack-swift04:54
*** psachin has quit IRC05:04
*** openstackgerrit has quit IRC05:18
*** links has joined #openstack-swift05:30
*** quicker_io has joined #openstack-swift05:39
*** pavelkv has joined #openstack-swift05:55
*** pcaruana has joined #openstack-swift05:59
pavelkvlukaslemes: yes, it is possible, but be sure that Keystone is production ready (becaouse swauth tokens are checked in Keystone too). It is important to use authtoken and keystoneauth before swauth06:01
pavelkvfor example use: pipeline = catch_errors gatekeeper healthcheck proxy-logging cache container_sync bulk tempurl ratelimit authtoken keystoneauth swauth container-quotas account-quotas copy slo proxy-logging proxy-server06:02
pavelkvAnd set delay_auth_decision = True in filter:authtoken section06:02
*** pcaruana has quit IRC06:05
*** quicker_io has quit IRC06:16
*** lukaslemes has joined #openstack-swift06:17
lukaslemeshi, thx;06:17
*** pcaruana has joined #openstack-swift06:19
lukaslemespavelkv: same pipeline config when i would use tempauth??  and is it best practies for all auth metohod difrent reseler_prefix? Becuse when i dont set it i get errors06:19
*** rcernin has quit IRC07:03
*** psachin has joined #openstack-swift07:14
mattoliveraulukaslemes: all auths need a different reseller_prefix, that's what reseller_prefix's are for.07:16
*** lukaslemes has quit IRC07:20
*** ccamacho has joined #openstack-swift07:40
*** pcaruana has quit IRC07:43
*** cbartz has joined #openstack-swift07:55
*** quicker_io has joined #openstack-swift07:55
*** mikecmpbll has joined #openstack-swift07:56
*** pcaruana has joined #openstack-swift07:57
*** cbartz has quit IRC08:00
*** cbartz has joined #openstack-swift08:00
*** mikecmpbll has quit IRC08:05
*** mikecmpbll has joined #openstack-swift08:08
*** quicker_io has quit IRC08:14
*** psachin has quit IRC08:17
*** psachin has joined #openstack-swift08:20
*** ccamacho has quit IRC09:21
*** ccamacho has joined #openstack-swift09:39
pavelkvlukaslemes: I don't know if it is good practise. We have the same prefix because we migrate users from swauth to keystone so the ID must be the same. If you would like to have swauth and keystone projects simultaneously, you can - swauth creates IDs with "-" and keystone alphanumeric only so there should not be a coflict. But admin can set ID in swauth so it is safe to configure different prefix as10:10
pavelkvMatt answered.10:10
*** quicker_io has joined #openstack-swift10:24
*** ccamacho has quit IRC10:31
*** ccamacho has joined #openstack-swift10:32
quicker_iohi, i have a bit trouble with config swift auth methods keystone, swauth and tempauth together. I added tempauth10:32
quicker_iopipline like this:  authtoken keystoneauth swauth tempauth10:33
quicker_ioand when i call pipline like this:  authtoken keystoneauth swauth tempauth get 40110:33
quicker_iowhen i call swift stat --debug -A http://127.0.0.1:8080/auth/v1.0/ -U test:testerA -K testingA -V 1 get 40110:34
*** threestrands has quit IRC10:36
*** links has quit IRC10:44
*** links has joined #openstack-swift10:49
*** mikecmpbll has quit IRC10:49
*** mikecmpbll has joined #openstack-swift10:49
*** links has quit IRC10:50
*** geaaru has quit IRC10:54
*** geaaru has joined #openstack-swift10:59
*** mikecmpbll has quit IRC11:00
*** mikecmpbll has joined #openstack-swift11:01
mattoliverauquicker_io: did you set different reseller prefixes for each one?11:07
pavelkvquicker_io: do you have delay_auth_decision = True in filter:authtoken section?11:25
quicker_iomattoliverau: yes for tempauth, swauth and keystone use different prefix12:01
quicker_iomattoliverau: i got 401 only when use tempauth accounts, i got 401 immediately when call swift stat --debug -A http://127.0.0.1:8080/auth/v1.0/ -U test:testerA -K testingA , i dont get authtoken utl12:04
*** jistr is now known as jistr|call12:32
*** psachin has quit IRC12:56
*** jistr|call is now known as jistr13:04
tdasilvagood morning13:23
*** mvkr has quit IRC13:29
tdasilvapavelkv any chance you might be able to add those instructions re keystone and swauth to the docs?13:31
*** mvkr has joined #openstack-swift13:59
*** mikecmpb_ has joined #openstack-swift14:03
*** mikecmpbll has quit IRC14:05
*** ccamacho has quit IRC14:50
*** ccamacho has joined #openstack-swift14:56
*** cbartz has quit IRC15:13
*** quicker_io has quit IRC15:17
*** pcaruana has quit IRC15:37
*** SkyRocknRoll has joined #openstack-swift15:49
*** SkyRocknRoll has quit IRC16:00
*** geaaru has quit IRC16:07
*** SkyRocknRoll has joined #openstack-swift16:13
*** gyee has joined #openstack-swift16:23
*** ccamacho has quit IRC16:31
*** mikecmpb_ has quit IRC16:33
*** pcaruana has joined #openstack-swift16:40
*** mvkr has quit IRC16:48
*** itlinux has joined #openstack-swift16:49
*** eandersson has quit IRC17:32
timburkeso i'm working on cleaning up some of our gate tests, and on p 591064 AJaeger did a great job of reminding me about the cross-branch problems of project-config changes17:35
patchbothttps://review.openstack.org/#/c/591064/ - openstack-infra/project-config - Drop legacy-swift*-dsvm-functional-identity-v3-onl... - 0h 4m 48s spent in CI17:35
timburkewhat do people think about dropping legacy-swift-dsvm-functional-identity-v3-only from stable branches? my first thought was, "oh, crap, that's right... maybe we *do* still want that..."17:35
timburkebut the more i thought about it, it's non-voting anyway, and i don't think i've ever seen us introduce a regression on v3 support... our auth bits generally just *don't change*, and i *really* don't think they'd change on a stable branch. so maybe it's ok to just drop it?17:36
*** ianychoi_ has joined #openstack-swift17:38
*** mvkr has joined #openstack-swift17:39
*** ianychoi has quit IRC17:41
*** pcaruana has quit IRC17:59
tdasilvatimburke: just tring to wrap my head around this...why drop only v3 jobs and not legacy-swift-dsvm-functional? AJaeger in his comment mentioned handling in our repo? could we setup the same job to run against only against stable? or even better yet, could we change project-config definition to only run against stable?18:15
timburketdasilva: so legacy-swift-dsvm-functional is already v3 only for queens and beyond -- i still want to test that integration, we just don't have a way to still cover v2 going forward (short of standing up some old version of keystone... which is probably doable, but it's not a real high priority for me)18:19
timburkei've got another patch to get legacy-swift-dsvm-functional out of project-config, too (p 591114), and it depends on us moving the job in-tree (p 589270). but i need to learn more about how to fix up the other projects that use it and, more generally, how zuul job definitions get shared across projects18:20
timburke*grumble, grumble* p 591114 p 58927018:22
patchbothttps://review.openstack.org/#/c/591114/ - openstack-infra/project-config - Remove legacy-swift-dsvm-functional job from swift - 0h 4m 59s spent in CI18:22
patchbothttps://review.openstack.org/#/c/589270/ - swift - Move legacy-swift-dsvm-functional job in-tree - 9h 43m 38s spent in CI18:22
timburke(as a side-note, i don't *really* want to land the in-tree jobs patch until there's a plan forward for the project-config changes, 'cause that'd just be wasteful to have two jobs that are ostensibly equivalent)18:24
timburkeyou can confirm the v3-only-ness by (for example) looking for the string "/v2" in http://logs.openstack.org/70/589270/11/check/legacy-swift-dsvm-functional/5a8b3d2/logs/screen-keystone.txt.gz -- it's flat-out never used18:27
*** SkyRocknRoll has quit IRC18:29
*** geaaru has joined #openstack-swift18:31
*** geaaru has quit IRC19:16
*** lxkong_ has joined #openstack-swift19:17
*** geaaru has joined #openstack-swift19:19
*** geaaru has quit IRC19:19
*** mgagne_ has joined #openstack-swift19:24
*** lxkong has quit IRC19:25
*** serverascode_ has quit IRC19:25
*** tommylikehu has quit IRC19:25
*** ujjain has quit IRC19:25
*** mgagne has quit IRC19:25
*** Miouge has quit IRC19:25
*** charz has quit IRC19:25
*** lxkong_ is now known as lxkong19:25
*** Miouge- has joined #openstack-swift19:25
*** ujjain has joined #openstack-swift19:27
*** ahale has quit IRC19:27
*** ahale has joined #openstack-swift19:32
*** openstackgerrit has joined #openstack-swift19:33
openstackgerritThiago da Silva proposed openstack/swift master: Update saio sample config files  https://review.openstack.org/58670319:33
openstackgerritTim Burke proposed openstack/swift master: Add IPv6 DSVM tests  https://review.openstack.org/59149719:55
tdasilvajust realized that a saio VM requires at least 2GB of ram, only 1gb and unit tests fail20:06
timburke:-( i wonder where the bloat comes from... and whether we can bring that memory footprint down20:06
timburketdasilva: how does it fail?20:06
tdasilvatimburke: lost my scrollback now that i fixed the issue, but there were two tests under test/unit/common   one was a really large container listing and the other was "fallocate"  i think....20:08
tdasilvai might start another vm to recreate it20:09
timburkei guess my big question at the moment is, can those tests pass if run *in isolation* in a 1GB vm?20:10
tdasilvatest_static_web_pretend_to_be_giant_json20:13
timburkeick. yeah, my bad: https://github.com/openstack/swift/blob/2.18.0/test/unit/common/middleware/test_listing_formats.py#L27020:17
timburkei can surely make that work better. like, have a generator expression for the response body and pre-calc the resulting content-length20:19
timburke:-( and the test isn't even testing what i thought it was testing...20:32
openstackgerritMerged openstack/swift master: Stop holding on to sys.exc_info tuples quite so much  https://review.openstack.org/57047720:47
openstackgerritTim Burke proposed openstack/swift master: Add IPv6 DSVM tests  https://review.openstack.org/59149720:56
openstackgerritTim Burke proposed openstack/swift master: Fix up test_static_web_pretend_to_be_giant_json  https://review.openstack.org/59152020:58
timburketdasilva: see if ^^^ works better. cut it down by like a factor of 620:59
timburkemakes me glad there was already the sanity check20:59
timburkeand if cutting down the input size is enough, i'm not gonna worry about the generator21:00
openstackgerritTim Burke proposed openstack/swift master: Add IPv6 DSVM tests  https://review.openstack.org/59149721:09
openstackgerritTim Burke proposed openstack/swift master: Stop logging overlapping tracebacks  https://review.openstack.org/54680821:16
openstackgerritTim Burke proposed openstack/swift master: Fix the deletion of non-existent keys  https://review.openstack.org/57584221:19
openstackgerritTim Burke proposed openstack/swift master: Include '-' in multipart ETags  https://review.openstack.org/57586021:20
timburkerebase party!21:20
openstackgerritTim Burke proposed openstack/swift master: Include '-' in multipart ETags  https://review.openstack.org/57586021:22
openstackgerritTim Burke proposed openstack/swift master: Add IPv6 DSVM tests  https://review.openstack.org/59149721:26
*** itlinux has quit IRC21:26
openstackgerritMerged openstack/swift master: Update saio sample config files  https://review.openstack.org/58670321:26
*** rcernin has joined #openstack-swift22:01
openstackgerritTim Burke proposed openstack/python-swiftclient master: Use Swift's in-tree DSVM test  https://review.openstack.org/59152822:03
openstackgerritTim Burke proposed openstack/python-swiftclient master: DNM: horribly break auth  https://review.openstack.org/59153022:29
mattoliveraumorning22:52
openstackgerritTim Burke proposed openstack/python-swiftclient master: Use Swift's in-tree DSVM test  https://review.openstack.org/59152823:09
openstackgerritTim Burke proposed openstack/python-swiftclient master: DNM: horribly break auth  https://review.openstack.org/59153023:09
openstackgerritTim Burke proposed openstack/python-swiftclient master: Use Swift's in-tree DSVM test  https://review.openstack.org/59152823:11
openstackgerritTim Burke proposed openstack/python-swiftclient master: DNM: horribly break auth  https://review.openstack.org/59153023:11
openstackgerritTim Burke proposed openstack/python-swiftclient master: Use Swift's in-tree DSVM test  https://review.openstack.org/59152823:15
tdasilvatimburke: i added myself as a reviewer to p 59152023:37
patchbothttps://review.openstack.org/#/c/591520/ - swift - Fix up test_static_web_pretend_to_be_giant_json - 0h 27m 38s spent in CI23:37
tdasilvabeen kinda buried in p 57586023:37
patchbothttps://review.openstack.org/#/c/575860/ - swift - Include '-' in multipart ETags - 10h 2m 43s spent in CI23:37
timburketdasilva: cool, thanks23:37
openstackgerritTim Burke proposed openstack/python-swiftclient master: DNM: horribly break auth  https://review.openstack.org/59153023:38
timburkealso good :-D23:38
tdasilvatimburke: been testing manually to see the data on disk, kinda cool, at the same time scary that we now have 3 different etags23:38
timburkeyep... definitely the biggest worry about all this for me. at least with p 337960 i could say with a straight face that i was just exposing a secondary etag that was already present... the presence of a third (and needing to make it work with conditional requests!) is a bit icky23:41
patchbothttps://review.openstack.org/#/c/337960/ - swift - Include SLO ETag in container updates (MERGED) - 14h 52m 37s spent in CI23:41
tdasilvatimburke: that error " Unable to verify integrity of data download..." comes from what tool? s3cmd?23:42
timburkei think that one came from CyberDuck... i forget the exact message that s3cmd would spit out...23:43
timburkeit may have been buried in debug/info logs, and the big thing you notice is that you seem to be uploading a lot more than you expected23:44
tdasilvak23:53

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