-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Other] Items to be discussed in Team IaaS #46
Comments
In Yaook, we came across this topic: https://gitlab.com/yaook/operator/-/issues/272. Is this something we want to discuss in Team 1 some time maybe? I'd like to hear your experience regarding this and tips how we can improve our status quo. |
Another topic from Yaook (yes, I'm cleaning up issues): https://gitlab.com/yaook/operator/-/issues/18. How does osism/kolla-ansible handle this? Is there any prepared guideline how to constrain the different nova/neutron/cinder keystone service accounts so that they can only do exactly what they are allowed to do? The background is to limit the damage credentials which have been exposed in some way can do. |
|
|
|
|
|
|
@berendt shouldn't this (osism/issues#272) be discussed in Team OPS tomorrow? |
Not sure about this. It affects the ES service of the infrastructure layer. |
Discussion is ongoing and also moved to SIG monitoring. Thanks @berendt for raising it. |
|
Why do you want to remove mistral? We have clients as example that use mistral to schedule automated snapshots and backups. |
@flyersa afaik the reason is that there is a proposal upstream to deprecate Mistral: https://review.opendev.org/c/openstack/governance/+/866562 See this thread on OpenStack discuss: https://lists.openstack.org/pipermail/openstack-discuss/2022-December/031388.html However, apparently OVH is stepping up to maintain mistral, so this could change things. |
|
|
obsoleted by hedgedoc and the meeting preps there |
Items to be discussed in Sprint Planning / Refinement Team IaaS (Team 1)
The text was updated successfully, but these errors were encountered: