Le 05/03/2025 à 11:35:25-0600, Vladimir Kozhukalov a écrit Hi,
Couple additional clarifications:
Thanks.
- Openstack-Helm and Kolla are independent projects with different approaches to deployment/upgrades. Openstack-Helm deploys Openstack on top of K8s (which is a container orchestrator). Kolla also deploys Openstack in containers but it utilizes Ansible for managing containers. Containers are just a convenient way of delivering software when you depend less on the software installed on the host. Due to this, containerized applications are usually considered a bit easier to upgrade. Containers are a thin layer that almost doesn't affect the performance but at the same time allows you to manage resources more carefully.
- If you decide to go with K8s and Openstack-Helm then keep in mind that K8s itself requires some resources to operate. And you should have a good understanding of the K8s concepts. Nowadays managing K8s itself isn't difficult at all. Kubeadm is an official tool, but there are other options.
Yes I know (at my expense ;-) ) the k8s is also some nightmare ;-) ;-) But what I not sure I understand is with openstack-helm is «where» the openstack will run ? Is it going to run on worker manage by the k8s ? Because in my k8s (openshift/okd) are running on manually deploy kvm VM, and for our purpose those kvm are pretty «small» (mostly run website). Or the openshift-helm running inside the k8s will deploy the openstack in some bare-metal server ? And those bare-metal server will continue to run if the k8s «disappear» ?
- Openstack-Helm is image agnostic and brings all necessary scripts/ configuration files with it. So potentially it can be used with Kolla images but we didn't test it with them. Openstack-Helm builds its own images [1].
Ok. Thanks. Regards JAS -- Albert SHIH 🦫 🐸 Observatoire de Paris France Heure locale/Local time: mer. 05 mars 2025 18:50:46 CET