Wednesday, 2021-11-03

*** redrobot2 is now known as redrobot05:58
mor3stimburke_, what will be the issue if we proceed with updating ring files if gz file is in obsolete state (assuming previous changes either reweight or additional of new drives)?05:59
reid_gGot keystone working with swift17:25
reid_gI'm a bit confused as to why17:25
reid_gI deleted my swift user from keystone and recreated it.17:26
DHEdidn't give the swift user the right permissions?17:28
reid_gOriginally I created it as openstack create --domain MyNonDefaultDomain --password-prompt swift; openstack role add --project myproject --user swift MyCustomRole17:30
reid_gToday I did openstack project create --domain default --description "Service Project" service; openstack user create --domain default --password-prompt swift; openstack role add --project service --user swift admin17:31
reid_gDoes swift user need to be in a project called service and have admin role to function?17:32
reid_gor does it just need admin role?17:32
timburke_reid_g, this was for the service user, used to validate the tokens swift receives? i think it'll depend on how keystone's configured... there's probably a way to get it working with non-default domain and non-default role, but idk myself17:36
reid_gI think so. It is the user that is specifed under authtoken (do you need authtoken with keystone or is that just to be able to use a token instead of user/pw?)17:38
timburke_is this for Swift api access, or S3 api?17:41
reid_gIt was for swift api17:42
timburke_so the request flow looks like this: client auths with keystone (most commonly, with username/password, but there are other ways), gets a token. client sends token when it talks to swift; swift passes the token to keystone to find out (1) whether it's valid and (2) assuming it is, what roles are associated with it17:45
timburke_the user specified in the authtoken section is the one that's validating tokens; to my knowledge the most common setup is like you've done now, to give it a role of "admin" in a "service" project17:46
reid_gMakes sense. Maybe the project doesn't matter so much as the admin role.17:49
reid_gIs authtoken required to use keystone?17:54
reid_gI guess it would be, otherwise how would swift know that you are allowed to access it.17:55
timburke_yes -- authtoken (owned by keystone) is responsible for talking to keystone and populating the WSGI env with role info, then keystoneauth (owned by swift) is responsible for comparing those roles against its operator_roles and reseller_admin_roles (as well as per-container ACLs) and deciding whether to allow or deny a particular request17:58
timburke_s3token is kind of the authtoken-equivalent for s3api users17:59
timburke_i've thought about exposing a new middleware that would wrap up authtoken, s3token, and keystoneauth so you could be assured that they were in the correct order and only have to define a single service user to be used by both authtoken and s3token... but haven't had the time/inclination to actually try to implement it18:02
reid_gYeah it's probably not that big of a gain18:05
reid_gnow to get s3 working and then I can do my testing18:11
reid_gLooks like it is working as well18:28
reid_gexciting18:28
reid_gfirst cluster I setup from scratch18:29
DHEre auth: administrative access is required to the Swift user for Keystone to be willing to decode arbitrary tokens for swift. Swift takes a user's token and shows it to Keystone to see the token's project, role(s), and when it expires for authentication19:26
reid_gMakes sense20:37
timburke__#startmeeting swift21:00
opendevmeetMeeting started Wed Nov  3 21:00:02 2021 UTC and is due to finish in 60 minutes.  The chair is timburke__. Information about MeetBot at http://wiki.debian.org/MeetBot.21:00
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:00
opendevmeetThe meeting name has been set to 'swift'21:00
timburke__who's here for the swift meeting?21:00
kotao/21:00
acoleso/21:00
mattolivero/21:01
timburke__as usual, the agenda's at21:02
timburke__#link https://wiki.openstack.org/wiki/Meetings/Swift21:02
timburke__just a couple things to talk about21:02
timburke__#topic request tracing21:02
timburke__mattoliver, i saw you pushed up some more patches, how's it going?21:02
mattoliverOk, I'm following up from ptg. The newest patchset removes a bunch of the initial cruft that's not really needed now that it has open tracing support.21:03
mattoliverI have more of my laptop to push up, more clean up21:04
timburke__👍 cool21:04
mattoliverAnd working on creating spans in make requests21:04
timburke__anything needed beyond more review?21:04
mattoliverAnd so it logs on timeout, ie when we don't get a response 21:04
timburke__sounds great21:05
acolesnice21:05
mattoliverSo can now see timed out requests (like kota suggested) but only added it to one place ATM. 21:05
kotaexcellent!21:06
mattoliverAnnoyingly we have a few different code paths to make requests.21:06
mattoliverWill push another revision up today, then if everyone likes the progress will squash it down into one patch21:06
timburke__👍21:07
timburke__next up21:07
timburke__# PTG action item progress21:07
mattoliverUmm.. oops, I mean.. making good progress :p 21:08
timburke__i went ahead and abandoned a bunch of patches, mostyl on old feature branches21:08
timburke__(sorry for any email noise)21:08
timburke__we merged the patch to drop a bunch of logging translations from the proxy-server21:09
timburke__(thanks acoles!)21:09
acolesI volunteered to tackle the backend servers but no progress yet21:10
timburke__and it sounds like seongsoocho is on the road to being able to translate docs21:10
mattoliverNice21:11
timburke__the only action item that actually has an established deadline is the interop feedback -- unfortunately, i still haven't responded on that yet21:11
timburke__i'll aim to do that this week21:11
mattoliverI had a long weekend, so haven't had as much time this week. Will create some etherpads and start filling them in regarding bug squash and defaults. 21:12
timburke__no worries! thanks mattoliver21:12
timburke__does anyone else have ptg action item progress to report?21:13
zaitcevI don't even remember what I promised at PTG. It feels like so long ago now.21:14
timburke__zaitcev, fwiw, i tried to capture ptg action items in the meeting agenda21:17
timburke__if there's anything i've forgotten, feel free to add it ;-)21:17
timburke__i'll keep them around and check in every so often. i expect it probably won't be weekly, but it seemed like we *did* manage to make some progress on things, so i figured we may as well highlight that21:18
timburke__that's all i've got21:18
timburke__#topic open discussion21:19
timburke__anything else we ought to bring up this week?21:19
timburke__all right -- let's make it a short meeting then :-)21:21
mattoliverkk :)21:21
timburke__thank you all for coming, and thank you for working on swift!21:21
timburke__#endmeeting21:21
opendevmeetMeeting ended Wed Nov  3 21:21:50 2021 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:21
opendevmeetMinutes:        https://meetings.opendev.org/meetings/swift/2021/swift.2021-11-03-21.00.html21:21
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/swift/2021/swift.2021-11-03-21.00.txt21:21
opendevmeetLog:            https://meetings.opendev.org/meetings/swift/2021/swift.2021-11-03-21.00.log.html21:21

Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!