openstack/openstack-manuals
Code Issues Proposed changes

Fix live migration RPC compatibility

Browse Source 
Add warning message to admin guide to notice operator
the potential of data loss when they use live migration
between Icehouse and Juno compute nodes.

Change-Id: Ib906646fe335184f7a62d0967795a15f07155b59
Closes-Bug: 1441521
This commit is contained in:
thorking 2015-07-21 16:56:50 +08:00
parent 4f9e34951a
commit c5458ee1a0
2 changed files with 16 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
doc/admin-guide-cloud-rst/source/compute-system-admin.rst
View File

@ -697,6 +697,14 @@ Before starting a migration, review the Configure migrations section.
$ nova live-migration d1df1b5a-70c4-4fed-98b7-423362f2c47c HostC
Migration of d1df1b5a-70c4-4fed-98b7-423362f2c47c initiated.
.. warning::
When using live migration to move workloads between
Icehouse and Juno compute nodes, it may cause data loss
because libvirt live migration with shared block storage
was buggy (potential loss of data) before version 3.32.
This issue can be solved when we upgrade to RPC API version 4.0.
#. Check the instances have been migrated successfully, using
:command:`nova list`. If instances are still running on ``HostB``,
check the log files at :file:`src/dest` for nova-compute and nova-scheduler)

8
doc/admin-guide-cloud/compute/section_compute-system-admin.xml
View File

@ -550,6 +550,14 @@ ws = websocket.create_connection(
ID or name of the instance. Another example:</para>
<screen><prompt>$</prompt> <userinput>nova live-migration d1df1b5a-70c4-4fed-98b7-423362f2c47c HostC</userinput><computeroutput>
<![CDATA[Migration of d1df1b5a-70c4-4fed-98b7-423362f2c47c initiated.]]></computeroutput></screen>
<warning>
<para>When using live migration to move workloads between
Icehouse and Juno compute nodes, it may cause data loss
because libvirt live migration with shared block storage
was buggy (potential loss of data) before version 3.32.
This issue can be solved when we upgrade to RPC API version 4.0.
</para>
</warning>
</step>
<step>
<para>Check the instances have been migrated successfully, using