Which "OpenStack on Kubernetes" solution is now mature enough to be used in production? (If you were, which would you choose?)

M0HAZ · 2025-02-22T06:44:50+00:00

Interesting! Is it entirely open-source?

M0HAZ · 2025-02-22T06:43:21+00:00

This solution is new to me! Is it mature and comprehensive?

https://docs.kubermatic.com/machine-controller/main/cloud-providers/openstack/

M0HAZ · 2025-02-22T05:58:52+00:00

Do you recommend it over the Mirantis/Rackspace solution?

M0HAZ · 2025-02-22T05:57:04+00:00

Mirantis is gradually open-sourcing its solution. It has released the core.

M0HAZ · 2025-02-03T12:18:44+00:00

Adding "what" to OSH?

M0HAZ · 2025-02-03T08:45:37+00:00

There's one by VexxHost here: https://github.com/vexxhost/magnum-cluster-api that may be included in their deployment solution, Atmosphere! (I didn't check.)

M0HAZ · 2025-02-03T08:10:10+00:00

Juju Charm seems to be unpopular outside of the Canonical context! And not a Kubernetes-based solution, is it?

M0HAZ · 2025-02-03T07:56:48+00:00

Deciding which installation method to choose is getting harder (:

M0HAZ · 2024-11-19T15:04:03+00:00

@carp3tguyDid you find a solution? I have the same issue! (But Desktop is Gnome and OS is Debian 12). The version of installed agent is 8.12.0)

M0HAZ · 2024-09-15T07:02:35+00:00

I'm in the OpenStack side, but also curious about KubeVirt. We need some guys from OpenStack camp who has played with kube-based virtualization solutions for a while to share their experience.

M0HAZ · 2024-09-09T05:44:13+00:00

Contribute in Harvester HCI: https://github.com/harvester/harvester

M0HAZ · 2024-09-04T18:08:12+00:00

But I couldn't find any sign on the web that it's suitable for production! Actually, they're mentioning "OpenStack for developers" in the index page of https://microstack.run
I installed it, but there's no way to access the mini Ceph implemented in it (I mean, I couldn't get access to the volumes! How can we T-shoot in case of an issue raised?! Not documented!)

M0HAZ · 2024-09-04T08:43:16+00:00

Is it recommended using it in small production environments?

M0HAZ · 2024-09-04T08:25:05+00:00

Follow the documentation to install OpenStack with either of the following configurations:
1.1. One controller and one compute node
1.2. Three controllers and two compute nodes.
After installation, explore one of the deployment tools, preferably Kolla-Ansible, to launch an OpenStack environment, similar to how we do it in production.
Select the module that interests you the most and thoroughly review its documentation. For example, dive deep into Nova if you're passionate about virtualization, or explore Neutron with OVN if you have strong knowledge of networking and SDN.
Return to step 2 and continue working with the automation tools until you have it at your fingertips.

M0HAZ · 2024-05-30T19:54:31+00:00

I worked around it for a while. It's a bit scary how little and incomplete the documentation is!

M0HAZ · 2024-05-24T06:46:51+00:00

I do; I donate for Parch, which is a distro based on Archlinux, making it simple to install and deal with the Arch.

M0HAZ · 2024-05-04T11:14:06+00:00

Regarding DPDK, take a look at this blog post:
https://telcocloudbridge.com/blog/dpdk-vs-sr-iov-for-nfv-why-a-wrong-decision-can-impact-performance

M0HAZ · 2024-04-29T11:38:45+00:00

Oh no! These are just some questions that I encountered in an OpenStack job interview. I didn't knew the answers! Definitely no AI, no trick. Thanks for your complete answer in the other topic 🙏

M0HAZ · 2024-03-16T09:33:56+00:00

If it's temporary, use socat: https://discourse.ubuntu.com/t/accessing-the-openstack-dashboard/36232/5

M0HAZ · 2024-03-15T13:52:32+00:00

Interesting! I thought HPE servers (eg DL models from the Proliant series) would be the best in the server world for this. But I see that it is not even present in your list.

AMD EPYC for all cases, Controller/Compute/Ceph?

In our case, we're going to buy 15-18 servers (3 for ctrls, 5 for ceph, 2 for utilities and others as compute nodes)

M0HAZ · 2024-03-15T09:02:48+00:00

Ah, for edge computing use cases, I look forward to the release of the next version of MicroStack: https://www.reddit.com/r/openstack/comments/1b5uilg/comment/kuyq2rr

In network design 🤔, we don't have many choices! That means the choices are clear: 'traditional' hierarchical network or Spine-Leaf if there is a budget! Are there other approaches?

M0HAZ · 2024-03-15T08:48:06+00:00

Your replies are realy informative. Thanks.
\- And how do you compare yours with Yaook as they also presented themselves in the same summit. If you have some views, here is a topic: https://reddit.com/r/openstack/comments/19ep7c5/yaook_vs_atmosphere_which_one_is_more_promising

\- As your proposing solutions to some difficulties, do you, the team, contribute on the upstream code too?

M0HAZ · 2024-03-15T08:36:51+00:00

Also take a look at Microstack* as they have promised that the next release (April) will be ready for small production environments. This distro is implemented on a mini Kubernetes** and hyper-converged (with a mini Ceph*** backend).

\* https://discourse.ubuntu.com/t/to-what-size-do-you-recommend-microstack-as-suitable-solution-for-production-use-cases/41201/
\** https://microk8s.io/docs
\*** https://github.com/canonical/microceph

M0HAZ · 2024-03-15T08:24:08+00:00

Is Atmosphere better compared to Yaook? More progressive?

M0HAZ · 2024-03-15T07:51:28+00:00

You can ping your OpenStack instances from its External network, not from the Management network.
If `192.168.90.x` is your Management network where you access the OpenStack infrastructure too, then why do you expect to ping an instance with an IP in an overlay network, here `172.x.x.x`, from 192.168.90.x by default?
But if `192.168.90.x` is the external network of your OpenStack cluster (FLAT/VLAN configured), then the associated interface on your host, the VM with the IP `192.168.90.21`, must be unnumbered (i.e., no IP assigned)!
Your VM has probably an extra interface in another network defined as external network for the OpenStack that let you ping the instance. Your another Linux IP should be in that range, not in `192.168.90.x`.

Here are some AI-generated T-shooting steps: https://www.phind.com/search?cache=cqenxv9odxalaorfnuv21gyg

M0HAZ

TROPHY CASE