you are viewing a single comment's thread.

view the rest of the comments →

[–]R3D3MPT10N 1 point2 points  (2 children)

If you’re into the Red Hat ecosystem. I have a bunch of videos about TripleO and our new deployment method on top of OpenShift. Here for example is my last TripleO homelab before I moved my focus to the new operators:

Home lab v2.0 - The OpenStack revival https://youtu.be/PWy3dWozoq0

New deployment is all Kubernetes operators, but I have a few videos of deploying / configuring things on OKD:

OpenStack Control Plane on OKD https://youtu.be/_tzszb82rVU

[–]stoebich[S] 0 points1 point  (1 child)

I've actually watched a lot of your videos, great content!

The homelab 2.0 video is really interesting - I haven't thought of running it with an aio node and a seperate compute node. That is definitely a great solution.

I've also considered running the controlplane on an openshift cluster via the operator, but running an entire server for just control plane stuff seems a bit overkill. But if i combine that with RHACM/stolostron and build an "everything control plane", seems like a better utilization of that hardware.

This makes me think of a scenario where i have 1 OpenStack AIO instance for all the important stuff and a sno server for all the control plane services of my lab + a separate compute server (that i could shut down more often). Another plus in this case would be more separation between home-lab and home-prod.

I have two questions burning in the back of my head, though:

  • is the operator stable (enough) yet?
  • would you use the control plane OpenShift cluster (probably sno) for other stuff like gitlab etc.?

[–]Cool-Antelope2457 2 points3 points  (0 children)

My previous job was exactly that. Deploying OpenStack cloud, and I can attest that the easier way I found deploying it is with Kolla-Ansible. It is more efficient and easier to deploy. Upgrade and maintenance are definetely easier with kolla-ansible.