I couldn't find any update on this feature, is there any progress?
yes, there is: https://lists.proxmox.com/pipermail/pve-devel/2022-September/054148.htmlI couldn't find any update on this feature, is there any progress?
How about now? Unsure how to navigate the mailing list.Hi,
yes, there is: https://lists.proxmox.com/pipermail/pve-devel/2022-September/054148.html
But it's not applied yet, it's still a work-in-progress.
Yes, cli only for now since 7.3 With qm commandHow about now? Unsure how to navigate the mailing list.
How about now? Unsure how to navigate the mailing list.
qm remote-migrate <srcvmid> <dstvmid> 'apitoken=PVEAPIToken=root@pam!migrator=efgD9b785-f0f3-47bb-8553-26F1166c6ed0,host=remotehost.fqdn' --target-bridge vmbr0:vmbrX,vmbr1:vmbry --target-storage localstorage:deststorage --online
Certain storage combinations only work online (e.g. our RBD plugin doesn't implement offline export/import currently), but others work just fine offline (e.g. ZFS -> ZFS, dir -> dir).works online only currently
For the purposes of the discussion, a standalone server is a one node cluster.My question of course has not been asked yet and that is concerning the migration (live or not-live) betwixt a cluster of nodes and a singular node not part of any cluster at all.
For the purposes of the discussion, a standalone server is a one node cluster.
Cross-cluster migration is one of the steps that needed to be taken to make something like that usable. A datacenter manager is planned (can't give any ETA though): https://forum.proxmox.com/threads/multi-datacenter-management.66830/page-2All,
Please allow me to proffer this hypothetical:
If one has two different clusters each with 3 nodes ("cluster1" and "cluster2") along with a single un-clustered node "node-unclustered". Is there a "Datacenter view" that will show you all of cluster1 and its nodes, cluster2 and its nodes, and the unclustered node?
Stuart, N3GWG
qm remote-migrate 2644 2644 apitoken='PVEAPIToken=xxxxxxxxxxxx',host=10.0.3.106,fingerprint=XX:XX:XX,port=8006 --target-storage osdpool --target-bridge vmbr0:vmbr0 --online
does the apitoekn have acl/permissions on the storage ?I tried to do a test migration from one cluster to another:
Code:qm remote-migrate 2644 2644 apitoken='PVEAPIToken=xxxxxxxxxxxx',host=10.0.3.106,fingerprint=XX:XX:XX,port=8006 --target-storage osdpool --target-bridge vmbr0:vmbr0 --online
But always show an error "remote: storage 'osdpool' does not exist!"
The target name exists.
What I'm doing wrong ?
Thanks