proxmox-mirrors/pve-docs
1
0
Fork 0
mirror of https://git.proxmox.com/git/pve-docs synced 2025-07-09 22:49:43 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

pvecm/migration: try using better english

Browse Source 
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
This commit is contained in:
Thomas Lamprecht 2016-11-30 12:09:57 +01:00 committed by Dietmar Maurer
parent 2225402cf5
commit a9baa444f1
1 changed files with 32 additions and 26 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

58
pvecm.adoc
View File

@ -918,29 +918,32 @@ networks where you can transfer 10 Gbps or more.
Migration Network Migration Network
~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~
By default {pve} uses the network where the cluster communication happens By default, {pve} uses the network in which cluster communication
for sending the migration traffic. This is may be suboptimal, for one the takes place to send the migration traffic. This is not optimal because
sensible cluster traffic can be disturbed and on the other hand it may not sensitive cluster traffic can be disrupted and this network may not
have the best bandwidth available from all network interfaces on the node. have the best bandwidth available on the node.
Setting the migration network parameter allows using a dedicated network for Setting the migration network parameter allows the use of a dedicated
sending all the migration traffic when migrating a guest system. This network for the entire migration traffic. In addition to the memory,
includes the traffic for offline storage migrations. this also affects the storage traffic for offline migrations.
The migration network is set as a network in the CIDR notation. This
has the advantage that you do not have to set individual IP addresses
for each node. {pve} can determine the real address on the
destination node from the network specified in the CIDR form. To
enable this, the network must be specified so that each node has one,
but only one IP in the respective network.
The migration network is represented as a network in 'CIDR' notation. This
has the advantage that you do not need to set a IP for each node, {pve} is
able to figure out the real address from the given CIDR denoted network and
the networks configured on the target node.
To let this work the network must be specific enough, i.e. each node must
have one and only one IP configured in the given network.
Example Example
^^^^^^^ ^^^^^^^
Lets assume that we have a three node setup with three networks, one for the We assume that we have a three-node setup with three separate
public communication with the Internet, one for the cluster communication networks. One for public communication with the Internet, one for
and one very fast one, which we want to use as an dedicated migration cluster communication and a very fast one, which we want to use as a
network. A network configuration for such a setup could look like: dedicated network for migration.
A network configuration for such a setup might look as follows:
---- ----
iface eth0 inet manual iface eth0 inet manual
@ -966,25 +969,28 @@ auto eth2
iface eth2 inet static iface eth2 inet static
address 10.1.2.1 address 10.1.2.1
netmask 255.255.255.0 netmask 255.255.255.0
# [...]
---- ----
Here we want to use the 10.1.2.0/24 network as migration network. Here, we will use the network 10.1.2.0/24 as a migration network. For
For a single migration you can achieve this by using the 'migration_network' a single migration, you can do this using the `migration_network`
parameter: parameter of the command line tool:
---- ----
# qm migrate 106 tre --online --migration_network 10.1.2.0/24 # qm migrate 106 tre --online --migration_network 10.1.2.0/24
---- ----
To set this up as default network for all migrations cluster wide you can use To configure this as the default network for all migrations in the
the migration property in '/etc/pve/datacenter.cfg': cluster, set the `migration` property of the `/etc/pve/datacenter.cfg`
file:
---- ----
# [...] # use dedicated migration network
migration: secure,network=10.1.2.0/24 migration: secure,network=10.1.2.0/24
---- ----
Note that the migration type must be always set if the network gets set. NOTE: The migration type must always be set when the migration network
gets set in `/etc/pve/datacenter.cfg`.
ifdef::manvolnum[] ifdef::manvolnum[]
include::pve-copyright.adoc[] include::pve-copyright.adoc[]