DevOps, Virtualizacion, Linux, Seguridad y un poco mas..
In a previous article, we saw how to integrate Harvester in Rancher UI, and from there we were able to request a new K8s cluster with just a few clicks. Now is Virtual Machine time. How fast can we deploy a Linux VM.
Look at https://arielantigua.com/weblog/2023/12/harvester-hci-en-el-homelab/
For installing Harvester.
Linux VM.
This is easier than expected. You just need an img or qcow2 file imported into Harvester. Navigate to Images and click Create.
For a few months, I’ve been reading about Ceph and how it works, I love distributed stuff, maybe the reason is that I can have multiple machines and the idea of clustering has always fascinated me. In Ceph, the more the better!
If you have multiple machines with lots of SSD/NVME the Ceph performance will be a lot different than having a 3-node cluster with only one OSD per node. This is my case, and the solution has been working well.
Installing Ceph on Proxmox is just a few clicks away, is already documented in https://pve.proxmox.com/wiki/Deploy_Hyper-Converged_Ceph_Cluster
At first, I have two nodes and the state of Ceph was faulty.
The crush_map created by Proxmox is a 3-host configuration, that adds at least one OSD to the cluster, in this picture, there were only 2 hosts with 1 OSD each.
The Ceph documentation states that you need more than 3-4 host to have a decent performance, but this is a Homelab, I cannot afford to be running more than 3 machines for this.
Just installed Proxmox on the 2nd machine.
Ceph is the future of storage; where traditional systems fail to deliver, Ceph is designed to excel. Leverage your data for better business decisions and achieve operational excellence through scalable, intelligent, reliable, and highly available storage software. Ceph supports object, block and file storage, all in one unified storage system.
That’s the official definition from Ceph website. It’s it true?
I don’t know. Want to find out!
Since few weeks ago I’ve been in the planning stage to install and configure Ceph in a 3-node cluster, everything done via Proxmox UI. One of the main issues with this solution, the storage devices. how’s that?
Well.. it doesn’t like Consumer SSD/Disks/NVME.
BoM:
Note: The storage listed here will be used for Ceph OSD, there is a dual 10GbE card on each host for replication.
I have a pair of 970 EVO Plus (1TB) that were working fine with vSAN ESA, decide to move to Intel Enterprise NVMe because a lot of information around the web points to bad performance with this type of NMVe.
The Supermicro machine is already running Proxmox, lets the Ceph Adventure begins!
This picture is one of the Z440, is full in there!!
Let’s do this.
I think this is the second English-post in the entire history of this blog. Be gentle with me.
KubeVirt, is a known name for the people already doing containers, a normal player for people in the OpenShift world, but why if you come from others environment (VMware?) is like this doesn’t exist or is just being ignore?
If you can read Spanish and go back in the post history of this site, you can see that when is about VMs, VMware was the only option, not the same with Kubernetes, I started playing with K8s since 2018 and by that time, VMware didn’t have an offering that can compete with K8s. so I stick with K8s installed directly with kubeadm or the Rancher’s offering (RKE, RKE2 and K3s).
Why did I do a little recap?
Because is time to start trying new solutions to manage our VMs.
I love Harvester, love the fact that it can connect to Rancher UI and can be managed from the same place that I already have my containers, but is so resource intensive! The same host that was running Proxmox and ESXi can’t cope with the demand, I hope that this solution keeps growing and get my hands on others! (looking at you Platform9!).
My next steps, read more about plain KubeVirt to know more how this thing works behind the nice UI provided by Rancher or OpenShift… wish me luck !