Wednesday, 2026-10-28

*** darmach2 is now known as darmach14:34
gtema#startmeeting keystone15:01
opendevmeetMeeting started Wed Oct 28 15:01:56 2026 UTC and is due to finish in 60 minutes.  The chair is gtema. Information about MeetBot at http://wiki.debian.org/MeetBot.15:01
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:01
opendevmeetThe meeting name has been set to 'keystone'15:01
gtemaReminder: This meeting takes place under the OpenInfra Foundation Code of Conduct15:02
gtema#link https://openinfra.dev/legal/code-of-conduct15:02
gtema#topic roll call15:02
gtemad34dh0r53, xek, dmendiza[m], dmendiza, mharley, jph, gtema, cardoe, deydra15:02
d34dh0r53o/15:02
cardoeo/15:02
gtemaxek was around today, so a gentle ping15:03
gtemaand a new one for dmendiza 15:04
gtemahm, ok, going on15:04
gtema#topic review past meeting work items15:04
gtema#link https://meetings.opendev.org/meetings/keystone/202615:04
gtemathere were no action items logged last meeting15:05
gtemaas such we can jump next into15:05
gtema#topic liaison updates15:05
gtemaI do not have anything15:05
gtemaassume there is nothing else from anybody15:06
gtema#topic specification15:06
gtema#topic Secuirty Compliance Testing (dmendiza)15:06
gtema#link https://review.opendev.org/c/openstack/devstack/+/95796915:06
gtemano changes here since a while, last rebase happened 1 month ago15:07
gtemathere is really work needed, change is so old and fails15:07
gtemahoping dmendiza will find time to work on it sometime15:08
gtema#topic User Specified Project/User UUIDs (dmendiza, alee)15:08
gtemaI haven't seen any changes in specs since last reviews15:08
gtemagoing on15:09
gtema#topic keystone-rs (gtema)15:09
gtemathere was another "warm" discussion in the TC about the resolution yesterday15:09
gtemain general some members would like to see the rest of Keystone team explicilty +1-ing the resolution to signal it is a team effort15:10
gtemaon the project side itself I was spending now time doing deeper benchmarks against python code base to present the real figures into the resolution. Not sure it is going to be useful though15:11
gtemaas such I am now working on the rewrite of the resolution to frame it on the less arguable requirements and explicitly talking about starting a new project rather then simply rewriting Keystone15:12
gtemathis is the last try before I completely give up on that15:12
gtemaon the technical side of keystone-rs I have nearly completed implementing oauth2 DPoP15:13
gtemaservice grants (trust replacement) are also nearly completed15:13
gtemaand I started working on https://review.opendev.org/c/openstack/keystone-specs/+/1011888 which introduces an abstraction over the delegation so that OpenStack services can migrate only once on something that is plugable and allow them abstract from technical details of trusts and other means of delegations. Of course it comes at another "abstraction" level cost (in all means)15:15
gtemaonce we land the spec and "interface" implementation we can send out message to projects on what is the strategy with trusts15:16
gtemathat's it on that topic15:16
gtema#topic open discussion15:16
gtemacardoe, unfortunately I had no chance to look into the federated system scope deeper due to other priorities.15:17
cardoewanted to see if the keystoneauth typing improvements from stephenfin are okay with folks.15:17
cardoeno worries I understand15:17
gtemaI do not think I manage it this week as well and next week there is another conference I am participating15:17
gtematyping is surely fine15:17
gtemaunless we can really enforce typing in the runtime the benefit is not complete though15:18
gtemabut everybody is aware of that15:18
gtemabtw, my talk over the weekend about zero trust and our roadmap was very welcome by present german operators15:20
gtemaeverybody understands need and challenges though15:20
gtemabut nobody was objecting showing support for the work15:20
gtemaanything else for the open discussion?15:21
gtema#topic bug review15:21
gtema#link https://bugs.launchpad.net/keystone/?orderby=-id&start=015:22
gtemakeystone has one new bug https://bugs.launchpad.net/keystone/+bug/217206815:22
gtemaGreg already reviewed the referred patch, so it is in progress15:23
gtemaall other deliverables do not have new bugs15:24
gtemabut as everybody knows it doesn't mean we have nothing to do ;-)15:24
gtemawith that we are actually done15:26
gtema#topic conclusion15:26
gtemathanks to those who participated15:26
gtema#endmeeting15:26
opendevmeetMeeting ended Wed Oct 28 15:26:56 2026 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:26
opendevmeetMinutes:        https://meetings.opendev.org/meetings/keystone/2026/keystone.2026-10-28-15.01.html15:26
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/keystone/2026/keystone.2026-10-28-15.01.txt15:26
opendevmeetLog:            https://meetings.opendev.org/meetings/keystone/2026/keystone.2026-10-28-15.01.log.html15:26
d34dh0r53thanks @gtem15:31
d34dh0r53@gtema15:31
gtema:) welcome15:31
d34dh0r53ElementX is not an improvement :/15:31
gtemayou are so right, after few days fighting with it to support encryption the UX looks very weird15:32
opendevreviewMerged openstack/oslo.limit master: Capture outputs and logs  https://review.opendev.org/c/openstack/oslo.limit/+/101215817:04

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