local-lvm with more than one SSD/nVME

[mokaz]

Hi folks,

I'm currently setting up my Proxmox setup with 3 nodes and local storage at the beginning.
Here are my hardware properties on each nodes:

1x 2.5' SSD Samsung EVO 250 512
1x M.2 nVME 1TB Samsung EVO 870

My idea is to setup Proxmox on the SSD drive, which fully works, no probs on that.
My only issue is currently that once setup I'm left with a "local-lvm" which is part of the data pool within the pve volume group.

What would be the safest way to add the 1TB storage to that "local-lvm" storage group?

My goal isn't storage perf, my goal is more to host VMs with networking needs and to be able to migrate these VMs in the occurrence of a node issue etc..
I've seen as well that in order to migrate VMs, identical volume groups are needed amongst the nodes, is this correct?

Indeed, I'm not really an LVM specialist yet =)

Thanks for your inputs,
Kind regards,
m.

 

[mira]

You could create a LVM thin storage on your NVMe and use that instead. Choose whatever name you like. Just make sure the name is the same on all 3 nodes.

You can create a new LVM thin by selecting the Node -> Disks -> LVM-Thin and click the `Create` button at the top.

 

[mokaz]

Hi Mira, thanks a lot, I'll see how I'll be doing that.. For the time being I went with ZFS on the 1TB nVME..
Love proxmox, really cool stuff !!!

 

[jaceqp]

Hi Mira, thanks a lot, I'll see how I'll be doing that.. For the time being I went with ZFS on the 1TB nVME..
Love proxmox, really cool stuff !!!

Why using ZFS on a single disk (well except zfs-snaps perhapse)?

 

[mokaz]

Good question Jaceqp =) TBH this is for my home lab, I've recently said bye bye to ESXi and i'm testing all I can to understand it.
And to be honest with you, what I want to understand is what does this all means in really really shitty situations.. Like L2 switch down, no more vLANs, no shared storage, main NAT/router NGFW down , VM based HA etc etc etc... So i'm just testing it all to see for myself =)

If you'd have a good way or your best practices in such a setup I'd be more than happy to read them really, as said I'm looking at simplicity and reliability over complexity and performance i would say.

Thanks Ladies and Gents =)
Kind regards,
M.

 

[mokaz]

And well yes, easy VMs fly out's from one node to the other, that would be neat..