adding local storage to cluster members

  • Thread starter Thread starter jekader
  • Start date Start date
J

jekader

Guest
Hi everyone.

So, I'm running Proxmox VE v1.7. Two nodes in a cluster, each only with local storage, configured by default during install.

Now I want to add more local LVM storage to the nodes. I've installed the hard drives, ran pvcreate and lvcreate on each node, created logical volumes of the same name.

What do I do now? Create a storage device on each node or just the master?
With this model, if I create a VM using this storage on one node, will I be able to migrate it to the other node to the same storage? Or must I use DRBD in order for that to work?

Thanks in advance for the advice!
 
Last edited by a moderator:
jekader said:
Hi everyone.

So, I'm running Proxmox VE v1.7. Two nodes in a cluster, each only with local storage, configured by default during install.

Now I want to add more local LVM storage to the nodes. I've installed the hard drives, ran pvcreate and lvcreate on each node, created logical volumes of the same name.

What do I do now? Create a storage device on each node or just the master?
With this model, if I create a VM using this storage on one node, will I be able to migrate it to the other node to the same storage? Or must I use DRBD in order for that to work?

Thanks in advance for the advice!
Click to expand...
Hi,
if you want to use the storage independed on each node, you must only define the lvm-storage on the master. PVe assume that the storage is available on each node (and don't know about's that's different storages is - so your gui show not the right free/used-values for all storages!).
Live migration can't work - the content wasn't copied and not available on both nodes.

If you want live migration (and a cleaner storage-config) use DRBD (mark "shared storage" in the storage gui.

Udo
 
I don't need live migration. Here's what I want to happen:
2 nodes in a cluster, each has local storage1 and storage2
storage1 volume is the default one, with VMs, ISOs and templates
storage2 is an LVM volume for VM HDD's
if I create a VM on node1 on storage2, then shut it down and migrate to node2, will the HDD image be moved to the storage2 volume of node2?

The problem is that storage1 has almost no free disk space, and I want to extend it. If the thing I wrote above doesn't work, what's the recommended approach on increasing storage space?
 
Last edited by a moderator:
I've made an experiment to see how it goes. Here are the results so far:
1) there were some problems for PVE to unterstand volume groups with digits, so I deleted them and created new ones with letters only.
2) after creating the logical volume on the master, it automatically created on the slave, using the volume group of the same name.
3) It works locally, I can create VMs on this volume.
4) Read/Write performance is really nice!
5) migration doesn't work :( qmigrate just says
Code: 
can't migrate 'lvmstorage:vm-114-disk-1' - storagy type 'lvm' not supported

so LVM storage must be shared in order for the migration to work, qmigrate can't transfer LVM volumes.

Now there are two options available for my situation:
1) use DRBD
2) grow the pvedata volume/partition and store VM HDD's as files, thus limiting performance.

Probably I'll stick with the first option, and do as Udo advised - make two pairs of mirrored disks so that each node mainly accesses it's own disk, and the second one has the other node's data for quick failover in case of emergency.
 
You must log in or register to reply here.
Top Bottom