Now what about EUC replacements. That’s the more sticky situation.
For those who don’t know, EUC stands for end user computing.
Why is so hard to setup VMs for employees? Maybe I’m missing something but it seems like a matter of just creating a virtual machine with a GPU attached.
The list for those that don’t want to read the whole article:
- Proxmox
- XCP-ng
- OpenNebula
- SUSE Harvester
- Oracle VM VirtualBox
Not even an honorable mention for QEMU?
I like Virtualbox, use it myself in several instances but I would never consider it a replacement for VMware.
I use VirtualBox right now. My daily driver windows 10 guest is so slow, that pushing the start button comes with a 20s wait. Looking at the performance monitor while this is happening, nothing pops outs as the culprit. Plenty of resources left.
I’ve always sworn to VirtualBox, but I’m going to ask my boss for a workstation pro license next time I see him.
What i miss honnestly is KVM.
I don’t know about the others but proxmox uses KVM.
Ahh I didnt know that honnestly. never really used proxmox my self. thought it was its own thing. I do know that openstack ussage it as well.
I can relly recommend proxmox. Some years ago we switched from a 60.000€ dell VMWare Storage/Server-Setup to a three Host proxmox Setup for about half the price (to be fair, add 5-10k for Setup for our local Linux Team because we did not know much about proxmox). Mainly because we were able to place one of the Hosts in our Warehouse (connected with 10g Fiber) so there theoretically will be no harm to our production in case of water/fire/whatever in the server room because the one system can instantly take over (after some learning it works Like a Charm). I had some concerns regarding ceph, but for us it has proven Rocksolid, even while we had some real weird Switch issues it always recovered fast and without issues as soon as the connection was there. A big issue were the licensing terms for Microsoft products because with three amd-systems you have a lot of cores to buy licenses for - so we had a good excuse to substitute and cut out some products that only supported Windows environments.
Can anyone weigh in on whether any of these can be used for a cluster?
I use VMware in my homelab via vMUG, and I’m sure that’s going to get destroyed next, so I’m looking for an alternative that can allow for running VMs across hosts using shared storage with migrations between hosts. I’d prefer FOSS, but the only hypervisor I know supports all of this right now is hyper-V. I really REALLY don’t want to use hyper-v… Most of my workloads are Linux, with a handful of Windows servers that I use for an internal domain and testing.
Maybe OpenStack or OpenNebula?
Any suggestions?
Why wouldn’t you use Proxmox?
Proxmox is amazing
For some cases, yes. I don’t think its mature in many ways and the company is small and very local.
I love it for my homelab, but I’m not sure about production.
I just don’t see us switching our 17 datacenters to proxmox. Azure HCI, perhaps, but most likely we’ll stick with vmware, at least in the foreseeable future.
The weird thing to me about the majority of VMware environments I see is that they exist to prop up and extend Microsoft environments.
Microsoft is hostile towards this use case because having your own cloud competes with their cloud products.
VMware was a commodity product that exists because they know how desperately IT professionals need to keep these Windows systems running with some level of reliability with advanced backup and replication strategies. And it was good.
After trying out proxmox I can say that:
- VM performance under windows is much faster on vmware. I think this boils down to the drivers for storage. I could go more into detail but not here.
- Containers and Linux VMs are offering me more than I ever really hoped for in proxmox.
But now I’m starting to think what the alternatives are really. VMware was a windows first virtualization platform. Other virtualization platforms in the open source ecosystem really put things like Linux first. Having to race to get to the point of hosting windows systems with constantly increasing licensing prices has really diminished the value to me of virtualization over all for windows.
I think we as a community need to move away from windows on the server and embrace technologies like containers,docker,podman, Kubernetes and phase out reliance on Windows.
For starters, does anybody have a rock solid setup guide for a Kubernetes Active Directory System?
Active directory doesn’t normally go with Kubernetes. What are you asking?
Yeeahh… I’m thinking (hoping) he means an alternative LDAP/IDP, like Keycloak or Authentik…? Wanting to reduce reliance on Windows = kicking AD to the curb, too.
There is Samba AD but that will very much not run in kubernetes
I’m fooling around with a few samba AD docker containers. I ask because I’ve phased almost everything else out of my lab environment.
The problem with Samba AD in a container or Samba in container is that Samba isn’t designed to be run in a temporary environment. You could run it in a LXC container but anything beyond that will break things in the short or long term.
I figured you could get around some of the storage limitations with something like persistent volume claims. I’m testing it out at the moment. I am a big fan of LXC.
I see a few people have created docker Samba Containers and I’m giving them a whirl. Can’t say much for stability but I think it’s an interesting experiment.
I know in the past smb server didn’t work in LXC containers because certain kernel modules caused conflicts.
A man can dream.
If you manage to create persistent containers how are you going to update them down the road? Like I have said previously, Samba isn’t designed in a way that allows for effectively hot swapping system components.
It seems like it would better to create a VM template and then setup a fail over cluster. Just make sure you have a time server somewhere on the network.
If you are dead set on containers you could try LDAP in a container. I just don’t think active directory was built for Linux containerization.