Difference between revisions of "Checkpointing and live migration"
(link to criu) |
|||
| (2 intermediate revisions by one other user not shown) | |||
| Line 1: | Line 1: | ||
| + | <translate> | ||
| + | <!--T:1--> | ||
CPT is an extension to the OpenVZ kernel which can save the full state of a running VE and to restore it later on the same or on a different host in a way transparent to running applications and network connections. This technique has several applications, the most important being live (zero-downtime) migration of VEs and taking an instant snapshot of a running VE for later resume, i.e. CheckPointing. | CPT is an extension to the OpenVZ kernel which can save the full state of a running VE and to restore it later on the same or on a different host in a way transparent to running applications and network connections. This technique has several applications, the most important being live (zero-downtime) migration of VEs and taking an instant snapshot of a running VE for later resume, i.e. CheckPointing. | ||
| + | <!--T:2--> | ||
Before CPT, it was only possible to migrate a VE through a shutdown and subsequent reboot. The procedure not only introduces quite a long downtime for network services, it is not transparent for clients using the VE, making migration impossible when clients run some tasks which are not tolerant to shutdowns. | Before CPT, it was only possible to migrate a VE through a shutdown and subsequent reboot. The procedure not only introduces quite a long downtime for network services, it is not transparent for clients using the VE, making migration impossible when clients run some tasks which are not tolerant to shutdowns. | ||
| + | <!--T:3--> | ||
Compared with this old scheme, CPT allows migration of a VE in a way which is essentially invisible both for users of this VE and for external clients using network services located inside the VE. It still introduces a short delay in service, required for actual checkpoint/restore of the processes, but this delay is indistinguishable from a short interruption of network connectivity. | Compared with this old scheme, CPT allows migration of a VE in a way which is essentially invisible both for users of this VE and for external clients using network services located inside the VE. It still introduces a short delay in service, required for actual checkpoint/restore of the processes, but this delay is indistinguishable from a short interruption of network connectivity. | ||
| − | {{Note|In | + | <!--T:4--> |
| + | {{Note|In OpenVZ 7, CPT is replaced by our sub-project [http://criu.org CRIU]}} | ||
| − | |||
| + | == Online migration == <!--T:5--> | ||
| + | |||
| + | <!--T:6--> | ||
There is a special utility vzmigrate in the OpenVZ distribution intended to support VE migration. With its help one can perform live (a.k.a. online) migration, i.e. during migration the VE “freezes” for some time, and after migration it continues to work as though nothing had happened. Online migration can be performed with: | There is a special utility vzmigrate in the OpenVZ distribution intended to support VE migration. With its help one can perform live (a.k.a. online) migration, i.e. during migration the VE “freezes” for some time, and after migration it continues to work as though nothing had happened. Online migration can be performed with: | ||
<pre>vzmigrate --online <host> VEID</pre> | <pre>vzmigrate --online <host> VEID</pre> | ||
| + | <!--T:7--> | ||
During online migration all VE private data saved to an image file, which is transferred to the target host. | During online migration all VE private data saved to an image file, which is transferred to the target host. | ||
| + | <!--T:8--> | ||
In order for vzmigrate to work without asking for a password, ssh public keys from the source host should be placed in the destination host's <code>/root/.ssh/authorized_keys</code> file. In other words, command <code>ssh root@host</code> should not ask you for a password. See [[ssh keys]] for more info. | In order for vzmigrate to work without asking for a password, ssh public keys from the source host should be placed in the destination host's <code>/root/.ssh/authorized_keys</code> file. In other words, command <code>ssh root@host</code> should not ask you for a password. See [[ssh keys]] for more info. | ||
| − | == Manual Checkpoint and Restore Functions == | + | == Manual Checkpoint and Restore Functions == <!--T:9--> |
| + | <!--T:10--> | ||
<code>vzmigrate</code> is not strictly required to perform online migration. The <code>vzctl</code> utility, accompanied with some file system backup tools, provides enough power to do all the tasks. | <code>vzmigrate</code> is not strictly required to perform online migration. The <code>vzctl</code> utility, accompanied with some file system backup tools, provides enough power to do all the tasks. | ||
| + | <!--T:11--> | ||
A VE can be checkpointed with: | A VE can be checkpointed with: | ||
<pre>vzctl chkpnt VEID --dumpfile <path></pre> | <pre>vzctl chkpnt VEID --dumpfile <path></pre> | ||
This command saves all the state of a running VE to the dump file and stops the VE. If the option <code>--dumpfile</code> is not set, <code>vzctl</code> uses a default path <code>/vz/dump/Dump.VEID</code>. | This command saves all the state of a running VE to the dump file and stops the VE. If the option <code>--dumpfile</code> is not set, <code>vzctl</code> uses a default path <code>/vz/dump/Dump.VEID</code>. | ||
| + | <!--T:12--> | ||
After this it is possible to restore the VE to the same state executing: | After this it is possible to restore the VE to the same state executing: | ||
<pre>vzctl restore VEID --dumpfile <path></pre> | <pre>vzctl restore VEID --dumpfile <path></pre> | ||
If the dump file and file system is transferred to another HW node, the same command can restore the VE there with the same success. | If the dump file and file system is transferred to another HW node, the same command can restore the VE there with the same success. | ||
| + | <!--T:13--> | ||
It is a critical requirement that file system at the moment of restore must be identical to the file system at the moment of checkpointing. If this requirement is not met, depending on the severity of changes, the process of restoration can be aborted or the processes inside a VE can see this as an external corruption of open files. When a VE is restored on the same node where it was checkpointed, it is enough to not touch the file system accessible by the VE. When a VE is transferred to another node it is necessary to synchronize the VE file system before restore. <code>vzctl</code> does not provide this functionality and external tools (i.e. <code>rsync</code>) are required. | It is a critical requirement that file system at the moment of restore must be identical to the file system at the moment of checkpointing. If this requirement is not met, depending on the severity of changes, the process of restoration can be aborted or the processes inside a VE can see this as an external corruption of open files. When a VE is restored on the same node where it was checkpointed, it is enough to not touch the file system accessible by the VE. When a VE is transferred to another node it is necessary to synchronize the VE file system before restore. <code>vzctl</code> does not provide this functionality and external tools (i.e. <code>rsync</code>) are required. | ||
| − | == Step-by-step Checkpoint and Restore == | + | == Step-by-step Checkpoint and Restore == <!--T:14--> |
| + | <!--T:15--> | ||
The process of checkpointing can be performed in stages. It consists of three steps. | The process of checkpointing can be performed in stages. It consists of three steps. | ||
| + | <!--T:16--> | ||
First step – suspend the VE. At this stage CPT moves all the processes to a special beforehand known state and stops VE network interfaces. This stage can be done with: | First step – suspend the VE. At this stage CPT moves all the processes to a special beforehand known state and stops VE network interfaces. This stage can be done with: | ||
<pre>vzctl chkpnt VEID --suspend</pre> | <pre>vzctl chkpnt VEID --suspend</pre> | ||
| + | <!--T:17--> | ||
Second step – dumping VE. At this stage CPT saves the state of processes and global state of VE to an image file. All the process private data needs to be saved: address space, register set, opened files/pipes/sockets, System V IPC structures, current working directory, signal handlers, timers, terminal settings, user identities (uid, gid, etc), process identities (pid, pgrp, sid, etc), rlimit and other data. This stage can be done with: | Second step – dumping VE. At this stage CPT saves the state of processes and global state of VE to an image file. All the process private data needs to be saved: address space, register set, opened files/pipes/sockets, System V IPC structures, current working directory, signal handlers, timers, terminal settings, user identities (uid, gid, etc), process identities (pid, pgrp, sid, etc), rlimit and other data. This stage can be done with: | ||
<pre>vzctl chkpnt VEID --dump --dumpfile <path></pre> | <pre>vzctl chkpnt VEID --dump --dumpfile <path></pre> | ||
| + | <!--T:18--> | ||
Third step – killing or resuming processes. If the migration succeeds the VE can be stopped with the command: | Third step – killing or resuming processes. If the migration succeeds the VE can be stopped with the command: | ||
<pre>vzctl chkpnt VEID --kill</pre> | <pre>vzctl chkpnt VEID --kill</pre> | ||
| Line 47: | Line 64: | ||
<pre>vzctl chkpnt VEID --resume</pre> | <pre>vzctl chkpnt VEID --resume</pre> | ||
| + | <!--T:19--> | ||
The process of restoring consists of two steps. | The process of restoring consists of two steps. | ||
| + | <!--T:20--> | ||
The first step is to restore processes and to leave them in a special frozen state. After this step processes are ready to continue execution, however, in some cases CPT has to do some operations after a process is woken up, therefore CPT sets process return point to function in our module. This stage can be done with: | The first step is to restore processes and to leave them in a special frozen state. After this step processes are ready to continue execution, however, in some cases CPT has to do some operations after a process is woken up, therefore CPT sets process return point to function in our module. This stage can be done with: | ||
<pre>vzctl restore VEID --undump --dumpfile <path></pre> | <pre>vzctl restore VEID --undump --dumpfile <path></pre> | ||
| + | <!--T:21--> | ||
Second step – waking up processes or killing them if the restore process failed. After CPT wakes up process, it performs necessary operations in our function and continues execution. This stage can be done with: | Second step – waking up processes or killing them if the restore process failed. After CPT wakes up process, it performs necessary operations in our function and continues execution. This stage can be done with: | ||
<pre>vzctl restore VEID --resume</pre> | <pre>vzctl restore VEID --resume</pre> | ||
| Line 57: | Line 77: | ||
<pre>vzctl restore VEID --kill</pre> | <pre>vzctl restore VEID --kill</pre> | ||
| − | == See also == | + | == See also == <!--T:22--> |
| + | <!--T:23--> | ||
* http://criu.org/ | * http://criu.org/ | ||
| − | + | </translate> | |
[[Category: Technology]] | [[Category: Technology]] | ||
[[Category: Concepts]] | [[Category: Concepts]] | ||
Latest revision as of 17:34, 29 January 2018
<translate> CPT is an extension to the OpenVZ kernel which can save the full state of a running VE and to restore it later on the same or on a different host in a way transparent to running applications and network connections. This technique has several applications, the most important being live (zero-downtime) migration of VEs and taking an instant snapshot of a running VE for later resume, i.e. CheckPointing.
Before CPT, it was only possible to migrate a VE through a shutdown and subsequent reboot. The procedure not only introduces quite a long downtime for network services, it is not transparent for clients using the VE, making migration impossible when clients run some tasks which are not tolerant to shutdowns.
Compared with this old scheme, CPT allows migration of a VE in a way which is essentially invisible both for users of this VE and for external clients using network services located inside the VE. It still introduces a short delay in service, required for actual checkpoint/restore of the processes, but this delay is indistinguishable from a short interruption of network connectivity.
|
Note: In OpenVZ 7, CPT is replaced by our sub-project CRIU |
Contents
Online migration[edit]
There is a special utility vzmigrate in the OpenVZ distribution intended to support VE migration. With its help one can perform live (a.k.a. online) migration, i.e. during migration the VE “freezes” for some time, and after migration it continues to work as though nothing had happened. Online migration can be performed with:
vzmigrate --online <host> VEID
During online migration all VE private data saved to an image file, which is transferred to the target host.
In order for vzmigrate to work without asking for a password, ssh public keys from the source host should be placed in the destination host's /root/.ssh/authorized_keys file. In other words, command ssh root@host should not ask you for a password. See ssh keys for more info.
Manual Checkpoint and Restore Functions[edit]
vzmigrate is not strictly required to perform online migration. The vzctl utility, accompanied with some file system backup tools, provides enough power to do all the tasks.
A VE can be checkpointed with:
vzctl chkpnt VEID --dumpfile <path>
This command saves all the state of a running VE to the dump file and stops the VE. If the option --dumpfile is not set, vzctl uses a default path /vz/dump/Dump.VEID.
After this it is possible to restore the VE to the same state executing:
vzctl restore VEID --dumpfile <path>
If the dump file and file system is transferred to another HW node, the same command can restore the VE there with the same success.
It is a critical requirement that file system at the moment of restore must be identical to the file system at the moment of checkpointing. If this requirement is not met, depending on the severity of changes, the process of restoration can be aborted or the processes inside a VE can see this as an external corruption of open files. When a VE is restored on the same node where it was checkpointed, it is enough to not touch the file system accessible by the VE. When a VE is transferred to another node it is necessary to synchronize the VE file system before restore. vzctl does not provide this functionality and external tools (i.e. rsync) are required.
Step-by-step Checkpoint and Restore[edit]
The process of checkpointing can be performed in stages. It consists of three steps.
First step – suspend the VE. At this stage CPT moves all the processes to a special beforehand known state and stops VE network interfaces. This stage can be done with:
vzctl chkpnt VEID --suspend
Second step – dumping VE. At this stage CPT saves the state of processes and global state of VE to an image file. All the process private data needs to be saved: address space, register set, opened files/pipes/sockets, System V IPC structures, current working directory, signal handlers, timers, terminal settings, user identities (uid, gid, etc), process identities (pid, pgrp, sid, etc), rlimit and other data. This stage can be done with:
vzctl chkpnt VEID --dump --dumpfile <path>
Third step – killing or resuming processes. If the migration succeeds the VE can be stopped with the command:
vzctl chkpnt VEID --kill
If migration failed for some reason or if the goal was taking a snapshot of the VE state for later restore, CPT can resume the VE with:
vzctl chkpnt VEID --resume
The process of restoring consists of two steps.
The first step is to restore processes and to leave them in a special frozen state. After this step processes are ready to continue execution, however, in some cases CPT has to do some operations after a process is woken up, therefore CPT sets process return point to function in our module. This stage can be done with:
vzctl restore VEID --undump --dumpfile <path>
Second step – waking up processes or killing them if the restore process failed. After CPT wakes up process, it performs necessary operations in our function and continues execution. This stage can be done with:
vzctl restore VEID --resume
or
vzctl restore VEID --kill
See also[edit]
</translate>
