4 ms·

It's easier to turn an OptiPlex into NAS. Actually you could pass-through entire SATA stack as a PCI device into TruNAS running in Proxmox VM so it sees SATA po

It's easier to turn an OptiPlex into NAS. Actually you could pass-through entire SATA stack as a PCI device into TruNAS running in Proxmox VM so it sees SATA ports natively, with all goodies such as SMART.

znpy 3y ago
If you just need to run a few containers, you might want to take a look at TrueNas (Scale) rather than Proxmox.
- belthesar 3y ago
  Depending on the use case, this is definitely an option. I personally prefer using Proxmox under my Container Orchestration hardware because, as it seems to always eventually do, my home lab has become production, and being able to do software patches of the underlying system without service outages is really desirable. I've been agonizing and going back and forth between various potential solutions for this for a couple months now, with the most recent attempt being "Deploy k3s, with a fully separate control plane from the worker nodes, and run all of those atop a Proxmox cluster because being able to migrate VMs across nodes and also stand up isolated workloads to test out other solutions makes changing things in the future far less risky". That said, I was running the Homelab on effectively a single Unraid hyperconverged NAS/compute layer before then, and that worked wonders for quite a long time. I wouldn't consider Unraid my first choice now, given the advancements in TrueNAS SCALE in the time since I chose it as the solution, but the concept of NAS + Container Orchestrator as hyperconverged homelab today is quite attractive.
  - justinclift 3y ago
    > ... being able to do software patches of the underlying system without service outages is really desirable. Yeah, that's what I was looking at Proxmox (8.x) for recently as well, but it never made it through basic qualification testing. VM migration's would randomly hang forever about 25% of the time. Definitely not a case of bad network interconnect either. :( I'm using Ryzen 5000 series cpus on all the test gear though, and recently saw a mention that it may have been a known problem that's fixed. But not super keen on wasting more time. What sort of cpus are your hosts using, and are you using your VMs with Ceph as their storage? :)
    - belthesar 3y ago
      Great question! I haven't gotten that far yet. I have Proxmox running on a 12th gen i5 currently, and my other two compute nodes, a 3rd gen i7 laptop and a 7th gen i5, are currently still serving production workloads, so I haven't had a chance to set up a cluster yet. That said, I don't mind limiting features to lowest common denominator for the k3s control plane node, as I don't need gobs of power for it or advanced CPU features, and I imagine that's the pain you might be facing (though I'm new to Proxmox, so who can say?) That said, I do have a NAS that I can provide both NFS and iSCSI storage to, so I imagine if I run NFS as the backing storage, I shouldn't have to worry about clustered file systems. Each compute does have local storage, but the plan is to provide that via a CSI for workloads that don't need to be highly available or where fault tolerance isn't a concern.
      - justinclift 3y ago
        As a data point, the vm migration hangs aren't happening in testing any more. Looks like there really was a fix added to Proxmox recently. Can proceed with more testing now. :)

znpy 3y ago

If you just need to run a few containers, you might want to take a look at TrueNas (Scale) rather than Proxmox.

belthesar 3y ago
Depending on the use case, this is definitely an option. I personally prefer using Proxmox under my Container Orchestration hardware because, as it seems to always eventually do, my home lab has become production, and being able to do software patches of the underlying system without service outages is really desirable. I've been agonizing and going back and forth between various potential solutions for this for a couple months now, with the most recent attempt being "Deploy k3s, with a fully separate control plane from the worker nodes, and run all of those atop a Proxmox cluster because being able to migrate VMs across nodes and also stand up isolated workloads to test out other solutions makes changing things in the future far less risky". That said, I was running the Homelab on effectively a single Unraid hyperconverged NAS/compute layer before then, and that worked wonders for quite a long time. I wouldn't consider Unraid my first choice now, given the advancements in TrueNAS SCALE in the time since I chose it as the solution, but the concept of NAS + Container Orchestrator as hyperconverged homelab today is quite attractive.
- justinclift 3y ago
  > ... being able to do software patches of the underlying system without service outages is really desirable. Yeah, that's what I was looking at Proxmox (8.x) for recently as well, but it never made it through basic qualification testing. VM migration's would randomly hang forever about 25% of the time. Definitely not a case of bad network interconnect either. :( I'm using Ryzen 5000 series cpus on all the test gear though, and recently saw a mention that it may have been a known problem that's fixed. But not super keen on wasting more time. What sort of cpus are your hosts using, and are you using your VMs with Ceph as their storage? :)
  - belthesar 3y ago
    Great question! I haven't gotten that far yet. I have Proxmox running on a 12th gen i5 currently, and my other two compute nodes, a 3rd gen i7 laptop and a 7th gen i5, are currently still serving production workloads, so I haven't had a chance to set up a cluster yet. That said, I don't mind limiting features to lowest common denominator for the k3s control plane node, as I don't need gobs of power for it or advanced CPU features, and I imagine that's the pain you might be facing (though I'm new to Proxmox, so who can say?) That said, I do have a NAS that I can provide both NFS and iSCSI storage to, so I imagine if I run NFS as the backing storage, I shouldn't have to worry about clustered file systems. Each compute does have local storage, but the plan is to provide that via a CSI for workloads that don't need to be highly available or where fault tolerance isn't a concern.
    - justinclift 3y ago
      As a data point, the vm migration hangs aren't happening in testing any more. Looks like there really was a fix added to Proxmox recently. Can proceed with more testing now. :)