Build’s Name: The One Hypervisor
Operating System/ Storage Platform: Proxmox/ Local ZFS
CPU: Intel Xeon E5-2620v3
Motherboard: Supermicro X10SRi-F
Chassis: Supermicro CSE216E16-R1200LPB
Drives: TBD(Probably 24 Seagate Savvio 15K.2 ST9146852SS 146GB 15K 2.5" SAS)
RAM: 4x 16GiB Samsung M393A2G40DB0-CPB DDR4
Add-in Cards: Intel 910 800GiB PCIe SSD, LSI 9207-8i HBA
Power Supply: Redundant Supermicro PWS-1K21P-1R
Other Bits:
Usage Profile:
One Hypervisor to rule them all, One Hypervisor to find them,
One Hypervisor to bring them all and in the nested world bind them
L0-hypervisor for nested virtualization
Background
I have recently been promoted to 'Operative Datacenter Chief' and need to up my game in 'alternative' hypervisors like Proxmox and XenCenter as I am an Hyper-V and vSphere guy. Not being able to purchase the required hardware for multinode clustering and whatnot I need to bind them in my current hardware.
I've made some early tests using Proxmox and local ZFS storage on consumer SSDs (4x 250GiB Samsung 840 EVO) and so far I like it.The plan is to populate the chassis with 24 used Seagate Savvio 15k.2 146GiB SAS2-drives in a striped, mirrored VDEV for 1.7TiB storage and use the Intel 910 as SLOG and L2ARC.
Nitty Gritty Bits to Consider
How to distribute the Intel 910?
The Intel 910 is based on four 200GiB flash modules and as this strictly is a lab environment the 'requirement' for mirrored SLOG isn't really there, but performance is. perhaps 2x 200GiB striped VDEVs as SLOG and 2x 200GiB striped VDEVs as L2ARC is the way to go.
Alternatives to Proxmox
The L0-hypervisor will never be member of a cluster or distributed storage so Proxmox might be a little over the top for that. Perhaps any other distribution with ZFS-on-root, KVM and a decent web-vmm will suffice
Operating System/ Storage Platform: Proxmox/ Local ZFS
CPU: Intel Xeon E5-2620v3
Motherboard: Supermicro X10SRi-F
Chassis: Supermicro CSE216E16-R1200LPB
Drives: TBD
RAM: 4x 16GiB Samsung M393A2G40DB0-CPB DDR4
Add-in Cards: Intel 910 800GiB PCIe SSD, LSI 9207-8i HBA
Power Supply: Redundant Supermicro PWS-1K21P-1R
Other Bits:
Usage Profile:
One Hypervisor to rule them all, One Hypervisor to find them,
One Hypervisor to bring them all and in the nested world bind them
L0-hypervisor for nested virtualization
Background
I have recently been promoted to 'Operative Datacenter Chief' and need to up my game in 'alternative' hypervisors like Proxmox and XenCenter as I am an Hyper-V and vSphere guy. Not being able to purchase the required hardware for multinode clustering and whatnot I need to bind them in my current hardware.
I've made some early tests using Proxmox and local ZFS storage on consumer SSDs (4x 250GiB Samsung 840 EVO) and so far I like it.
Nitty Gritty Bits to Consider
How to distribute the Intel 910?
The Intel 910 is based on four 200GiB flash modules and as this strictly is a lab environment the 'requirement' for mirrored SLOG isn't really there, but performance is. perhaps 2x 200GiB striped VDEVs as SLOG and 2x 200GiB striped VDEVs as L2ARC is the way to go.
Alternatives to Proxmox
The L0-hypervisor will never be member of a cluster or distributed storage so Proxmox might be a little over the top for that. Perhaps any other distribution with ZFS-on-root, KVM and a decent web-vmm will suffice
- Step 1 - Reallocation of existing hardware
As more and more demons appear in my head regarding the storage, I've decided to swap the four Samsung EVO 840 for the Intel 910 in my workstation and start out with a zfs-stripe of 4x200GiB for initial vm-storage. When the decision for storage has been made, the Intel 910 will serve as SLOG and L2ARC (if needed).
Last edited: