Am 30.10.2012 12:25, schrieb Dietmar Maurer:
so pve-common get's updated first removed the file and then the pve-cluster
get's installed after pve-common gets updated.
Yes, that is the theory. In practice, updates can fail at various stages, and
users do strange things.
Maybe we can simply pass 'ciphers' inside $opts in
PVE::AbstractMigrate->migrate()
So you prefer to have a cipher Option in $opts of sub migrate instead of
having an additional parameter called $ssh_opts?
Var A:
sub migrate {
my ($class, $node, $nodeip, $vmid, $opts) = @_;
$opts->{cipher} //= 'blowfish';
Var B:
$ssh_opts = ['-c', 'blowfish'];
sub migrate {
my ($class, $node, $nodeip, $vmid, $opts, $ssh_opts) = @_;
Greets
Stefan
_______________________________________________
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
