Hey virtualizers,
Alright so I want to wrap my head around a proper storage setup when setting up ProxMox.
I installed in on metal, on a Xeon W 3670, my boot SSD is a 1TB WD Blue with a 2TB Seagate HDD.
So, should I be using ext fs? I'm not setting up any RAID volumes, so I don't know that I'll need ZFS just yet.
Also, should I allocate all of my boot disk to ProxMox?
What I was thinking initially is that I'd allocate 64GB to Proxmox as its boot volume, and then add a partition to the boot disk for each OS.
I should mention that what I'd like is to allocate a separate disk just as the home directory for my Linux VMs, and the very same for my Windows VMs.
Basically I want to be able to destruct my VM instances and their ephemeral storage as needed while keeping apps and docs in separate partitions as I would do in aws.
Also, what if at all should my swap disk space be?
As for my data storage partition, is there a way to make this an elastic storage volume in that the size of the volume increases to the capacity required by the files I save there, up to the max storage available? This would eliminate the need to do capacity planning, so I'd love to spin up elastic volumes if this is feasible.
See the screenshot attached for a visual of what I have in mind, and feel free to mark it up with corrections/recommendations.
<3
Khan
Alright so I want to wrap my head around a proper storage setup when setting up ProxMox.
I installed in on metal, on a Xeon W 3670, my boot SSD is a 1TB WD Blue with a 2TB Seagate HDD.
So, should I be using ext fs? I'm not setting up any RAID volumes, so I don't know that I'll need ZFS just yet.
Also, should I allocate all of my boot disk to ProxMox?
What I was thinking initially is that I'd allocate 64GB to Proxmox as its boot volume, and then add a partition to the boot disk for each OS.
I should mention that what I'd like is to allocate a separate disk just as the home directory for my Linux VMs, and the very same for my Windows VMs.
Basically I want to be able to destruct my VM instances and their ephemeral storage as needed while keeping apps and docs in separate partitions as I would do in aws.
Also, what if at all should my swap disk space be?
As for my data storage partition, is there a way to make this an elastic storage volume in that the size of the volume increases to the capacity required by the files I save there, up to the max storage available? This would eliminate the need to do capacity planning, so I'd love to spin up elastic volumes if this is feasible.
See the screenshot attached for a visual of what I have in mind, and feel free to mark it up with corrections/recommendations.
<3
Khan