From d555ebfcd8ec9451427a848944aa03c6628bf228 Mon Sep 17 00:00:00 2001 From: Yuko Fukuda Date: Tue, 18 Mar 2014 04:57:54 +0000 Subject: [PATCH] Typo: "libvritd" should be "libvirtd" Closes-Bug: #1293932 Change-Id: Id14dea4babd8b15219423f5e787cba90fbeeb78b --- doc/security-guide/ch055_security-services-for-instances.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/security-guide/ch055_security-services-for-instances.xml b/doc/security-guide/ch055_security-services-for-instances.xml index fc46dd7914..a24c1982f1 100644 --- a/doc/security-guide/ch055_security-services-for-instances.xml +++ b/doc/security-guide/ch055_security-services-for-instances.xml @@ -211,7 +211,7 @@ gpg --verify SHA256SUMS.gpg SHA256SUMSsha256sum -c SHA256SUMS 2>&1 | grep
Encrypted Live Migration - If your use case involves keeping live migration enabled, then libvirtd can provide tunneled, encrypted live migrations. That said, this feature is not currently exposed in OpenStack Dashboard, nor the nova-client commands and can only be accessed through manual configuration of libvritd. Encrypted live migration modifies the live migration process by first copying the instance data from the running hypervisor to libvirtd. From there an encrypted tunnel is created between the libvirtd processes on both hosts. Finally, the destination libvirtd process copies the instance back to the underlying hypervisor. + If your use case involves keeping live migration enabled, then libvirtd can provide tunneled, encrypted live migrations. That said, this feature is not currently exposed in OpenStack Dashboard, nor the nova-client commands and can only be accessed through manual configuration of libvirtd. Encrypted live migration modifies the live migration process by first copying the instance data from the running hypervisor to libvirtd. From there an encrypted tunnel is created between the libvirtd processes on both hosts. Finally, the destination libvirtd process copies the instance back to the underlying hypervisor.