Skip to content
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

Closed
5 tasks done
fkr opened this issue Apr 20, 2022 · 35 comments
Closed
5 tasks done

[Other] Items to be discussed in Team IaaS #46

fkr opened this issue Apr 20, 2022 · 35 comments
Assignees
Labels
IaaS Issues or pull requests relevant for Team1: IaaS

Comments

@fkr fkr added IaaS Issues or pull requests relevant for Team1: IaaS community labels Apr 20, 2022
@fkr fkr self-assigned this Apr 20, 2022
@fkr fkr changed the title [Other] Items to be discussed in CW 17 [Other] Items to be discussed in Team IaaS Apr 20, 2022
@berendt
Copy link
Member

berendt commented Apr 27, 2022

@horazont
Copy link
Member

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.

@horazont
Copy link
Member

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.

@fkr
Copy link
Member Author

fkr commented May 13, 2022

@berendt
Copy link
Member

berendt commented May 13, 2022

@berendt
Copy link
Member

berendt commented May 19, 2022

@berendt
Copy link
Member

berendt commented May 25, 2022

@fkr
Copy link
Member Author

fkr commented May 31, 2022

@fkr
Copy link
Member Author

fkr commented Jun 1, 2022

@fkr
Copy link
Member Author

fkr commented Jun 22, 2022

@fkr
Copy link
Member Author

fkr commented Jun 23, 2022

@fkr
Copy link
Member Author

fkr commented Jul 6, 2022

  • hands-on session osism inventories merging / multi-region deployments - 13.07. - 12:05 - @fkr will send invite to scs-tech

@fkr
Copy link
Member Author

fkr commented Jul 11, 2022

@fkr
Copy link
Member Author

fkr commented Jul 14, 2022

  • zuul for scs

@berendt
Copy link
Member

berendt commented Jul 27, 2022

@fkr
Copy link
Member Author

fkr commented Jul 27, 2022

@berendt shouldn't this (osism/issues#272) be discussed in Team OPS tomorrow?

@berendt
Copy link
Member

berendt commented Jul 27, 2022

@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.

@fkr
Copy link
Member Author

fkr commented Jul 28, 2022

Discussion is ongoing and also moved to SIG monitoring. Thanks @berendt for raising it.

@itrich itrich removed the community label Aug 15, 2022
@berendt
Copy link
Member

berendt commented Nov 8, 2022

* Heat is deprecated in favor of more generic Infrastructure as Code tools like Terraform
   as of now and will be removed in the future (exact removal date is not yet known)
 * Magnum (currently available as Technical Preview) will be removed in favor of Gardener and
   Cluster API
 * Mistral (currently available as Technical Preview) will be removed
 * Swift (currently available as Technical Preview) will be removed in favor of Ceph RGW
 * Trove (currently available as Technical Preview) will be removed in favor of Kubernetes
   database operators

@berendt
Copy link
Member

berendt commented Nov 9, 2022

@berendt
Copy link
Member

berendt commented Nov 10, 2022

@berendt
Copy link
Member

berendt commented Nov 28, 2022

@berendt
Copy link
Member

berendt commented Nov 28, 2022

@berendt
Copy link
Member

berendt commented Nov 28, 2022

@flyersa
Copy link

flyersa commented Dec 12, 2022

* Heat is deprecated in favor of more generic Infrastructure as Code tools like Terraform
   as of now and will be removed in the future (exact removal date is not yet known)
 * Magnum (currently available as Technical Preview) will be removed in favor of Gardener and
   Cluster API
 * Mistral (currently available as Technical Preview) will be removed
 * Swift (currently available as Technical Preview) will be removed in favor of Ceph RGW
 * Trove (currently available as Technical Preview) will be removed in favor of Kubernetes
   database operators

Why do you want to remove mistral? We have clients as example that use mistral to schedule automated snapshots and backups.

@fkr
Copy link
Member Author

fkr commented Dec 13, 2022

@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.

@berendt
Copy link
Member

berendt commented Jan 18, 2023

@berendt
Copy link
Member

berendt commented Feb 2, 2023

@berendt
Copy link
Member

berendt commented Feb 7, 2023

@berendt
Copy link
Member

berendt commented Feb 7, 2023

@berendt
Copy link
Member

berendt commented Feb 7, 2023

@berendt
Copy link
Member

berendt commented Feb 9, 2023

@berendt
Copy link
Member

berendt commented Feb 11, 2023

@berendt
Copy link
Member

berendt commented Feb 12, 2023

@tibeer tibeer mentioned this issue Mar 29, 2023
@fkr
Copy link
Member Author

fkr commented Jan 4, 2024

obsoleted by hedgedoc and the meeting preps there

@fkr fkr closed this as completed Jan 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
IaaS Issues or pull requests relevant for Team1: IaaS
Projects
None yet
Development

No branches or pull requests

5 participants