openstack
/
security-doc
Code Issues Proposed changes

Cleaning up grammer and wording, avoiding 2nd person 

Updating description of encrypted live migration process to avoid 2nd person
perspective, cleaning up grammer and wording to improve clarity.

Change-Id: Ibf0cfac2a4f6c592269c5921397aa3a70c1db4ab
Closes-Bug: #1344374
This commit is contained in:
Dan Sneddon 2014-07-22 18:09:24 -04:00
parent 674a7e6929
commit 3c106fb749
1 changed files with 6 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
security-guide/ch_security-services-for-instances.xml
View File

@ -220,7 +220,12 @@
</section>
<section xml:id="security-services-for-instances-idp191072">
<title>Encrypted live migration</title>
<para>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.</para>
<para>If there is a sufficient business case for keeping live migration enabled, then libvirtd can provide encrypted tunnels for the live migrations. However, this feature is not currently exposed in either the OpenStack Dashboard or nova-client commands, and can only be accessed through manual configuration of libvirtd. The live migration process then changes to the following high-level steps:</para>
<orderedlist>
<listitem><para>Instance data is copied from the hypervisor to libvirtd.</para></listitem>
<listitem><para>An encrypted tunnel is created between libvirtd processes on both source and destination hosts.</para></listitem>
<listitem><para>Destination libvirtd host copies the instances back to an underlying hypervisor.</para></listitem>
</orderedlist>
</section>
</section>
</section>