shared storage by zfs-dataset not zpool

[tpham]

Hi,

I want to do live migration but I notice that proxmox enforces that when using zpool, the name of the dataset and zpool have to be the same on both promox servers. I would like to know if we can change that policy such that promox would enforce one of the following policies instead:

1. Shared name ----
ie: my-local-zfs-share
server a: rpool/data

server b: spare_zpool/proxmox.storage

PS: It is not possible to create different local shares with the same name, so I think this is harder to archive than method# 2.



2. Dataset name:

instead of using this config:
zfspool: my-local-zfs-share
pool rpool/data
content rootdir,images
nodes proxmox0,pvespare
sparse 0

we would have something like this:
zfsdataset: my-local-zfs-share
dataset proxmox0:rpool/data pvespare:spare_zpool/proxmox.storage
content rootdir,images
nodes proxmox0,pvespare
sparse 0


I am not sure if any of the developers thought of the limitation of using the same zpool name and dataset name for shared storage. As for me, I see some limitations in this design.


Thanks,

TP

 

[wolfgang]

Hi,

you can migrate to an different storage, but you have use the command line.

see

qm help migrate

I am not sure if any of the developers thought of the limitation of using the same zpool name and dataset name for shared storage. As for me, I see some limitations in this design.

This is a complete other approach and do not fit in Proxmox VE storage concept.[/CODE]