Thursday, 2018-07-19

*** itlinux_ has joined #openstack-swift00:21
*** itlinux has quit IRC00:23
*** Anticimex has quit IRC00:41
*** mikecmpbll has quit IRC00:44
*** Anticimex has joined #openstack-swift00:46
*** itlinux_ has quit IRC00:49
*** itlinux has joined #openstack-swift01:17
*** mahatic has quit IRC01:38
*** mahatic has joined #openstack-swift01:41
*** mathiasb has quit IRC01:44
*** itlinux has quit IRC02:19
*** psachin` has joined #openstack-swift02:36
*** zhongjun__ has quit IRC03:44
*** links has joined #openstack-swift04:08
*** ccamacho has quit IRC04:21
*** pcaruana has joined #openstack-swift04:23
*** pcaruana has quit IRC04:34
*** hoonetorg has quit IRC05:20
*** ccamacho has joined #openstack-swift05:25
*** beisner has quit IRC05:29
*** DuncanT_ has joined #openstack-swift05:30
*** beisner_ has joined #openstack-swift05:30
*** serverascode_ has joined #openstack-swift05:30
*** serverascode has quit IRC05:30
*** portdirect has quit IRC05:30
*** lxkong_ has joined #openstack-swift05:30
*** portdirect_ has joined #openstack-swift05:30
*** portdirect_ is now known as portdirect05:30
*** DHE has quit IRC05:31
*** lxkong has quit IRC05:31
*** DuncanT has quit IRC05:31
*** lxkong_ is now known as lxkong05:31
*** portdirect is now known as Guest7295205:32
*** hoonetorg has joined #openstack-swift05:36
*** DHE has joined #openstack-swift05:44
*** threestrands has quit IRC05:49
*** cshastri has joined #openstack-swift05:50
*** threestrands has joined #openstack-swift06:09
*** threestrands has quit IRC06:09
*** threestrands has joined #openstack-swift06:09
*** nguyenhai has joined #openstack-swift06:13
*** nguyenhai_ has quit IRC06:17
*** gkadam has joined #openstack-swift06:26
*** threestrands has quit IRC06:36
*** pcaruana has joined #openstack-swift06:37
*** gkadam has quit IRC06:38
*** openstackgerrit has quit IRC07:04
*** rcernin has quit IRC07:29
*** mikecmpbll has joined #openstack-swift07:39
*** mikecmpbll has quit IRC07:41
*** gkadam has joined #openstack-swift08:11
*** gkadam is now known as gkadam-brb08:12
*** mikecmpbll has joined #openstack-swift08:36
*** tesseract has joined #openstack-swift08:41
*** viks_ has joined #openstack-swift08:50
*** beisner_ is now known as beisner09:34
*** afazekas|pto is now known as afazekas09:39
*** links has quit IRC10:49
*** links has joined #openstack-swift11:12
*** tommylikehu has joined #openstack-swift11:24
tommylikehuhey guys, how can I know what features or big changes have been made in swift during this cycle? other projects have specs, but I found nothing in the swift-specs repo.11:26
*** mikecmpbll has quit IRC11:38
mattoliverautommylikehu: yeah, we dont use specs, we found they were just a place to put down ideas, we release so often we don't choose 1 or 2 things to work on just release when ready. So ideas of what we want and what people are working on can be found at our ideas page: https://wiki.openstack.org/wiki/Swift/ideas. Priority reviews are where we track things that need to be looked at and are important, especially leading up to11:41
mattoliverau a release: https://wiki.openstack.org/wiki/Swift/PriorityReviews. But most importantly the changelog. Because unlike other OpenStack projects we cut a release 3 - 4 times a cycle. When things get done. We do try and align a release with the rest of OpenStack however.  For example, here are our release map. Which shows all our leases mapping to the OpenStack ones: https://wiki.openstack.org/wiki/Swift/version_map11:41
tommylikehuthanks! mattoliverau, so according to the link you shared: https://wiki.openstack.org/wiki/Swift/version_map, the changes in 2.18.0 includes all of the landed features during Rocky?11:49
mattoliverautommylikehu: The rocky release should be around the end of Aug so we'll try and fit one more release before then.. but yeah. the Changelogs for 2.16-2.18 will be in the rocky release as will probably a 2.19 (or something).12:02
mattoliverauif your going to go only by openstack realeases that is. if your going to upgrade swift for regularly then you could already be running some of the features ;)12:03
mattoliveraus/for/more/12:03
*** mikecmpbll has joined #openstack-swift12:09
DHEyeah, swift actually stands fairly well on its own away from the rest of openstack (well, maybe keep keystone for authentication)12:23
DHEso it tends to be a bit different in that regard12:23
tdasilvamattoliverau, tommylikehu: I just updated the version_map, according to the changelog 2.17.0 was the Queens release12:39
tdasilvamattoliverau, tommylikehu: so Rocky will be 2.18-2.19 (most likely)12:40
*** Guest72952 is now known as portdirect12:41
-openstackstatus- NOTICE: logs.openstack.org is offline, causing POST_FAILURE results from Zuul. Cause and resolution timeframe currently unknown.12:58
*** ChanServ changes topic to "logs.openstack.org is offline, causing POST_FAILURE results from Zuul. Cause and resolution timeframe currently unknown."12:58
*** ChanServ changes topic to "OpenStack Swift object storage | Logs: http://eavesdrop.openstack.org/irclogs/%23openstack-swift/ | Meetings: https://wiki.openstack.org/wiki/Meetings/Swift | Review Dashboard: http://not.mn/reviews.html"13:41
-openstackstatus- NOTICE: logs.openstack.org is back on-line. Changes with "POST_FAILURE" job results should be rechecked.13:41
tommylikehutdasilva:  thanks:)13:48
*** ccamacho has quit IRC13:49
*** ccamacho1 has joined #openstack-swift13:49
*** bkopilov has quit IRC14:10
*** cshastri has quit IRC14:12
rledisezhi. i heard (longtime ago) that authtoken middleware not having request id in the logs was fixed, but i still have the issue. did I miss something?14:48
rledisezJul 19 16:39:21 127.0.0.1 proxy-server: Authorization failed for token14:48
rledisezJul 19 16:39:21 127.0.0.1 proxy-server: Invalid user token14:48
rledisez(swift 2.15, keystoneauth1 3.3, keystonemiddleware 4.21)14:48
*** zhongjun__ has joined #openstack-swift14:50
*** ccamacho1 has quit IRC15:10
*** pcaruana has quit IRC15:12
*** gkadam-brb is now known as gkadam15:21
*** admin6_ has quit IRC15:53
notmynamegood morning15:59
notmynamerledisez: we'd changed somethng to fill the last gaps in swift's code so that messages have the transid on them. but auth_token is a different thing, since it's not using the same log configuration as swift (not in swift's codebase)16:09
notmynamewould be somewhat interesting to figure out where the breakdown is and make it set one. I'm not sure how possible that is16:09
rledisezok, so i misunderstood, i though it was fixed for auth_token. i'll try to have a look into it eventualy16:13
*** mikecmpbll has quit IRC16:53
*** tesseract has quit IRC16:56
*** links has quit IRC17:03
*** gkadam has quit IRC17:09
*** psachin` has quit IRC17:13
*** armaan has joined #openstack-swift18:07
*** mathiasb has joined #openstack-swift19:01
*** itlinux has joined #openstack-swift19:06
*** armaan has quit IRC19:19
cwright_Hi, I have a Pike installation of Swift with Keystone v3 for auth.19:25
cwright_I want to loop through the list of project names and run `swift stat` on each of them.19:25
cwright_I'm a little unclear on what combination of admin creds I need to provide, and which param to use to provide the customer project.19:25
cwright_Can anyone help clarify this for me?19:25
*** cwright_ is now known as cwright19:26
notmynamecwright: swift has the concept of a "reseller admin" that is a token with read/write permission for everything (technically not, but it's simpler to describe this way)19:29
notmynameIIRC there's a keystone middleware config setting for setting the keystone role that's marked as a super user19:30
notmynameyeah. there it is. https://github.com/openstack/swift/blob/master/etc/proxy-server.conf-sample#L42219:31
notmynameso you set that setting in the swift proxy config according to whatever admin/root/whatever role you have in keystone19:32
notmynamethen you auth against keystone to get a token with that role19:32
notmynamethen you can use that token id do do any requests to swift (ie HEAD every account). when you make the request (in your case, `swift stat`) you need to pass in the storage url to use19:33
notmynameif you have the token already, you can pass that in. or you can just use the keystone creds to get a token each time19:33
cwrightnotmyname: hey there :)19:34
cwrightThanks, that helps a lot. I remember this now, had forgotten that the original admin user didn't have ResellerAdmin role added19:34
*** openstackgerrit has joined #openstack-swift19:40
openstackgerritJohn Dickinson proposed openstack/python-swiftclient master: authors/changelog update for next release  https://review.openstack.org/58408119:40
notmynameauthors/changelog proposal for swiftclient release ^ tdasilva, mattoliverau, timburke_19:41
openstackgerritJohn Dickinson proposed openstack/python-swiftclient master: authors/changelog update for next release  https://review.openstack.org/58408119:57
corvusnotmyname: where is the current location for this docs content?  https://docs.openstack.org/mitaka/user-guide/cli_swift_static_website.html#static-website20:12
notmynamecorvus: good question. it's not exactly the same as what's on https://docs.openstack.org/swift/latest/middleware.html#staticweb but it's close. are you looking for something specific?20:15
corvusnotmyname: yeah -- specifically i was trying to determine what a "pseudo-directory" is.  the mitaka docs have a sentence that says: "If you create sub-directories for your site by creating pseudo-directories in your container, the index page for each sub-directory is displayed by default. If your pseudo-directory does not have a file with the same name as your index file, visits to the20:19
corvussub-directory return a 404 error."20:19
corvusnotmyname: i wondered if that means that you must upload a directory marker (0 byte application/directory object) at /foo, or if merely foo/index.html existing was enough to say that there is a "pseudo-directory"20:20
notmynamecorvus: let me check on that in the context of staticweb.20:24
corvusnotmyname: (also, just as doc reader feedback -- if the directory marker objects aren't required for this, it's not clear to me from the staticweb doc what they would be for)20:29
notmynamecorvus: yeah, it doesn't look like they are required. and if they exist, then staticweb will "do the right thing" instead of return the contents of the empty directory marker object.20:30
notmynamecorvus: a long long time ago, swift did this thing called "path" listings that was a pseudo-directory structure sort of thing. in order to have stuff roll up under a pseudo directory, you had to have directory marker object20:31
notmynamemerely a long time ago, we added prefix/delimiter listing functionality. it is slightly different, but mostly an overlapping superset of pseudo directories.20:32
notmynameso that's what people should use now20:32
notmynamehowever, we intentionally did not remove the "path" listing thing. and it is seen in a few places like staticweb20:32
notmyname(also note that staticweb allows you to set a container header to set the directory marker content type, if you don't want it to be application/directory)20:33
notmynameso .... no. no need to use a directory marker of "foo/" in order to make staticweb listings and index files work properly for content at "foo/index.html"20:34
notmyname(it's better without directory markers)20:34
corvusnotmyname: thanks!20:34
notmynamethis is good reading https://tools.ietf.org/html/draft-ietf-httpbis-bcp56bis-0620:49
*** lifeless has quit IRC21:01
*** armaan has joined #openstack-swift21:02
*** lifeless has joined #openstack-swift21:06
*** armaan has quit IRC21:14
*** geaaru has joined #openstack-swift21:20
*** geaaru has quit IRC21:30
*** macsun has joined #openstack-swift21:47
*** acoles has quit IRC21:47
*** rcernin has joined #openstack-swift21:58
*** acoles has joined #openstack-swift22:03
*** ChanServ sets mode: +v acoles22:03
*** itlinux has quit IRC22:22
*** itlinux has joined #openstack-swift22:42
*** rcernin_ has joined #openstack-swift22:47
*** rcernin has quit IRC22:49

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