| *** mhen_ is now known as mhen | 02:54 | |
| *** ykarel_ is now known as ykarel | 07:14 | |
| *** ykarel_ is now known as ykarel | 12:31 | |
| opendevreview | Artem Goncharov proposed openstack/keystonemiddleware master: Escape access_rules path literals in auth_token matching https://review.opendev.org/c/openstack/keystonemiddleware/+/1016057 | 14:02 |
|---|---|---|
| opendevreview | Artem Goncharov proposed openstack/keystonemiddleware stable/2026.2: Escape access_rules path literals in auth_token matching https://review.opendev.org/c/openstack/keystonemiddleware/+/1016058 | 14:02 |
| opendevreview | Artem Goncharov proposed openstack/keystonemiddleware stable/2026.1: Escape access_rules path literals in auth_token matching https://review.opendev.org/c/openstack/keystonemiddleware/+/1016059 | 14:03 |
| opendevreview | Artem Goncharov proposed openstack/keystonemiddleware stable/2025.2: Escape access_rules path literals in auth_token matching https://review.opendev.org/c/openstack/keystonemiddleware/+/1016060 | 14:08 |
| andreykurilin | gtema: Hi! unfortunately, I do not think I could get our project managers to approve keystone-rust at this stage. since it is outside openstack governance, it will not only require a new security certification, but it will make the process harder. we would also need to extend our CICD pipelines to support Rust, which is a minor issue but still extra work given our limited rust experience. | 14:31 |
| gtema | no problem. Just a heads-up - the project started as an extension to add SCIM and quickly figured out it is far more complex that one thinks at the first sight | 14:33 |
| andreykurilin | heh, I do not have a limited scope, so I hope I can achive scim support with minimal efford / without patching keystone core | 14:35 |
| andreykurilin | I will keep an eye on new keystone rust implementation, but not being part of os governance is number one blocker for adoption | 14:36 |
| gtema | I thoght similarly until I started implementing this and ended up rewriting whole keystone - current code base is just a can of worms | 14:37 |
| gtema | and to your point above - ceph is also not part of os governance and still not a single cloud runs without it - those are poor justifications used by people ignoring the fact that in the bottom of every software there is some core component maintained outside of any governance. We are working on getting rust project under some governance, but it doesn't change anything in the software | 14:41 |
| andreykurilin | gtema: in my case, ceph is provided by a separate team, so it's neither my problem nor part of the security certification I'm responsible for. lol. But I get your point, and I partially agree. Being under some org governance does not change the code itself, but it does make people, especially those unfamiliar with the core development team, more comfortable adopting something new. | 15:59 |
| andreykurilin | Is is relatively easy to start an internal conversation (with some business justification) about introducing a new service that follows openstack upstream recommendations (especially if it is already been adopted by Kolla, which we rely on). But seeing project is under the openstack-experiments namespace, it makes top management and security folks harder to convince checking pros and cons. | 16:00 |
| gtema | depending on the outcome of the TC resolution (https://review.opendev.org/c/openstack/governance/+/998652) it will either move under openstack or get a completely new name (and likely apply to openinfra project, rather than openstack) | 16:02 |
| andreykurilin | it is not an easy path :) Good luck! | 16:18 |
| gtema | thanks. Feel free to leave comments on the resolution to show what the "consumers" of the OpenStack think | 16:19 |
| opendevreview | Merged openstack/keystone stable/2026.2: Clear the request local cache when a request starts https://review.opendev.org/c/openstack/keystone/+/1015602 | 20:07 |
Generated by irclog2html.py 4.1.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!