Clunky to add ZFS pool storage on 2nd machine in cluster, bug or intended?

[DeFreeze]

Hello. Been messing with Proxmox last few days getting to know it. Running 2 servers in a cluster, with a QDevice on a 3rd server for the quorum thing.
On to the clunk: I log on to the web gui with the IP of node 1 to manage my cluster. After creating a ZFS pool on the 2nd server PVE2, I name it pve2-ssd-zfs, I go to the datacenter tab to add that storage, but it does not show up. Only the ZFS pool from PVE1 is there


BUT, if I log on to the web gui with the IP of node 2, I am allowed to add it.


This seems a little clunky from a cluster management perspective, is this a bug or is it intended?

Otherwise, having lots of fun with it, support material out there for this software seems very good.

 

[fiona]

Hi,
yes, currently only the local node is scanned for available storages. There is an enhancement request to improve the situation and @shrdlicka already sent patches for it.

But if the storage should play the same role on both nodes, I'd suggest you name the ZFS pool the same on both nodes and use a single storage configuration for both nodes. This is required for replication and can make other operations like migration smoother.

 

[DeFreeze]

Hello!
Thanks for the quick reply. I'll take a look at at naming them the same and do some experimentation with that.

 

[fabian]

that is the preferred way anyhow if you use it for the same purposes on both nodes, as it avoids manual mapping for things like migration

 

[DeFreeze]

Hello again. After trying some different things, how would you set this up? I might be doing it wrong, but naming them the same just gives me an error saying it's "already defined". Any help appreciated.


Update: As soon as I post this I see the "Add Storage" option. Will unticking this keep the storage out of the datacenter tab and therefore you can name them the same? Is that the idea?

 

[DeFreeze]

Okay, so when I googled "add storage" I got this thread. https://forum.proxmox.com/threads/same-storage-names-on-different-nodes.109817/

I was a little worried it wouldn't move the disks over when done like this, but after a live migration test, it does report in the UI that the disks have moved over and don't get left behind on the old node.

Even though this is elegant once it's up and running, I feel it could be easier or more intuitive to get to this point. The process of making it on node 1, where "Add Storage" has to be ticked, and then making it again with the same name on node 2 but making sure "Add Storage" is unticked, then removing the limits in the datacenter storage menu is a little confusing.
That said, it's working now, thanks

 

[fiona]

Even though this is elegant once it's up and running, I feel it could be easier or more intuitive to get to this point. The process of making it on node 1, where "Add Storage" has to be ticked, and then making it again with the same name on node 2 but making sure "Add Storage" is unticked, then removing the limits in the datacenter storage menu is a little confusing.
That said, it's working now, thanks

That will be improved in the future thanks to a patch by @aaron

 

[DeFreeze]

That patch describes the problem perfectly. Looking forward to the patch. Thanks for the reply.