dfea1c130e
PVE::ReplicationTools::destroy_all_snapshots - never delete local disks
2017-05-08 08:47:28 +02:00
be1d5bc192
PVE::ReplicationTools::sync_guest - do not add snapname to disks_status
...
Because it is not used at all.
2017-05-08 07:57:04 +02:00
c9a16105d4
PVE::ReplicationTools:sync_disk - use $lastsync instead of $job->{lastsync}
...
Because tghis is the parsed (untainted) value, and we pass this a parameter
to cleanup_snapshot.
2017-05-08 07:39:47 +02:00
81fa35e539
PVE::ReplicationTools::sync_guest - use integer compare for lastsync
2017-05-08 07:36:20 +02:00
ed283475d4
PVE::ReplicationTools::get_snapshot - remove dead code
...
This function makes no sense and is not used.
2017-05-08 06:55:12 +02:00
cba200746c
PVE::ReplicationTools: new helper get_ssh_cmd()
2017-05-08 06:42:24 +02:00
8ef98169e3
PVE::ReplicationTools::cleanup_snapshot - make sure ip is defined
2017-05-08 06:28:58 +02:00
7e5b531380
use 'eq' instead of regex for simple equality test.
2017-05-06 17:20:52 +02:00
efcdabfb36
PVE::ReplicationTools - coding style cleanup
2017-05-05 17:48:29 +02:00
e4d5d5f2aa
PVE::ReplicationTools::get_node_ip() - fix arguments for mtunnel
2017-05-05 15:45:27 +02:00
fa5e729eac
PVE::ReplicationTools - add missing "use PVE::INotify;"
2017-05-05 15:38:52 +02:00
be304991e7
PVE::ReplicationTools - remove unused var $cluster_nodes
2017-05-05 15:36:01 +02:00
e9b759ac30
PVE::ReplicationTools - only use required modules (remove Time::Local)
2017-05-05 15:36:01 +02:00
d884a78870
PVE::ReplicationTools - remove useless call to cfs_update
2017-05-05 15:27:08 +02:00
e0992d57e1
pvesr: rename list => jobs, call API
...
to avoid code duplication. I also removed the functioanlity to query
jobs on other nodes, because it is clumsy and not really needed.
2017-05-05 10:31:51 +02:00
6b1d6cee44
replica: get_syncable_disks: skip disks with replica=0
2017-04-28 11:31:46 +02:00
618a0d9b96
replica: add missing import
2017-04-28 11:27:59 +02:00
828d9073b3
replica: cleanup
2017-04-28 10:33:51 +02:00
663510b86d
This patch will include storage asynchronous replication.
...
It is possible to synchronise a volume to an other node in a defined interval.
So if a node fail there will be an copy of the volumes from a VM
on an other node.
With this copy it is possible to start the VM on this node.
2017-04-28 10:05:27 +02:00
