Local disk storage and clusters

  • Thread starter Thread starter ibonny
  • Start date Start date
I

ibonny

Guest
Hi evereyone,

I've set up several clusters, and I noticed something really annoying. If I create several local storage areas on several nodes, and I log into the master, how can I see the storage areas on the other nodes? I've found out that only the master's storage areas show up. I know that if I make NFS shares, I can see the same storage on all the nodes, but I want to take advantage of the disk space on each node. When I create a VM, it does appear to use the proper space on each node, but the local ISO repositories I've set up get really confused. Especially if an ISO storage area is named something different from the master.

Any ideas when this functionality will be available?

Ian
 
ibonny said:
Hi evereyone,

I've set up several clusters, and I noticed something really annoying. If I create several local storage areas on several nodes, and I log into the master, how can I see the storage areas on the other nodes? I've found out that only the master's storage areas show up.
Click to expand...

yes, local storage is only seen on the node you are. Log into the other nodes to see the local storage there.
 
Hi Dietmar,

I've actually tried to do that, but this causes other issues: If I'm logged in to the node instead of the master, I can't create new storage for that particular node... it always says "access denied", since its not the master (I'm assuming). Is there a way to create storage for that node (for example, a new ISO repository) without having to kick the node out of the cluster, adding it, and re-joining it?

Ian
 
Dietmar, another weird thing I'm experiencing is this: VM data stores appear to use the node's disk space when you create a new VM. But the ISO datastores are always the master's ISO datastore, not any of the node's. On top of that, some of the ISOs I have in the master's datastore tend to "disappear" from the list depending on the node I'm creating the VM on. They don't disappear off the master's disk directory, but they just aren't available to some of the VMs when I create them off the master's cluster list.

Ian
 
you need to create storages on the master, thats the design. (only local storage is not cluster-wide visible)
 
Thanks, Tom! That explains a lot. BTW, I think Proxmox is one of the best products I've found for virtualization in a long time. I had it up and running within about 10-15 minutes, and clustering almost just as fast. It blows VMware Server and is a great cost-effective model replacement for VMware ESXi. Thanks for bringing us a great piece of software!

Ian
 
OK, to further this design... I have some nodes that use external storage, which wouldn't be under /var/lib/vz, it would be under "/localmount/vz" (or whatever), since only the OS is on the root partition and the partition isn't big enough:I'm using Ubuntu, not the Proxmox distribution. When I do a migration, I don't want the VM going to /var/lib/vz... and from what I understand, and see, its not possible to specify a "destination storage location". I understand where you say that storage is only managed on the master, but do I add the path from the master and then just make sure I use it only with the one node?

Ian
 
You must log in or register to reply here.
Top Bottom