Le mardi 18 octobre 2022 à 08:39 +0200, Thomas Lamprecht a écrit : > > We plan to have such functionality in the datacenter manager, as that > should provide > a better way to manage such remotes and interfacing, in PVE it'd be > bolted on and > would require the need to manage this on every host/cluster > separately. > IOW. this is rather the lower level interface. > oh, ok! Make sense. I don't known too much about the roadmap, but when you say "the datacenter manager", do you plan to release some kind of external tool to manage multi-cluster ?
> It may still make sense to allow passing a remote via more private > channels, like the > environment or `stdin`, wouldn't be hard to do, just mark the target- > endpoint as optional > and fallback to $ENV{'..'} and maybe a json string from STDIN - which > an admin that wants > to use this lower level part directly can then even use with a file > config served via > bash input redicrection `qm remote-migration 1234 4321 > </etc/pve/priv/target-host.json` > > yep, something like that. Could be usefull in case of emergency, the night when you only have ssd access, don't remember the full syntax, the fingerprint, the token,... ^_^ (BTW, I have begin to test, the migration through the websocket tunnel is working really fine ! love it with the vmid reservation !) _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel