Migrate instances in Administrator Guide

Bug #1665860 reported by Bernd Bausch
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
openstack-manuals
Fix Released
Medium
Bernd Bausch

Bug Description

This bug tracker is for errors with the documentation, use the following as a template and remove or add fields as you see fit. Convert [ ] into [x] to check boxes:

- [X] This doc is inaccurate in this way:

There are several issues with this page. I have the feeling that it's an older text (pre-Mitaka perhaps) that was adapted to the openstack client. It needs more modernization than that.

It only covers live migrations and doesn't explain cold migration or evacuation.
The note at the beginning talks about the "nova live-migration" command, then the remainder of the text uses the openstack client.
It requires the reader to specify the migration destination. This may be a limitation of the openstack client, but it's more convenient to leave the selection of the destination host to Nova (the "nova live-migration" command allows that; the openstack client doesn't, it seems).
The warning at point 5 covers migration between Juno and Icehouse hosts and says "This issue can be solved when we upgrade to RPC API version 4.0". The reader (that's me:) doesn't understand anything about RPC versions. Which versions are used in Icehouse and Juno? And Newton? Can we install RPC version 4 on Juno and Icehouse? This warning is confusing.
Point 6 uses "openstack server list" to check whether the migration was successful. Unfortunately this command doesn't tell on which host the instance is running; "nova list --all-tenants --fields name,host" would be better, or "openstack server show".
Commands that allow monitoring, aborting and force-completing migrations are not mentioned.

- [X] This is a doc addition request.
      In the sense that I think this page needs more content.

- [ ] I have a fix to the document that I can paste below including example: input and output.

If you have a troubleshooting or support issue, use the following resources:

 - Ask OpenStack: http://ask.openstack.org
 - The mailing list: http://lists.openstack.org
 - IRC: 'openstack' channel on Freenode

-----------------------------------
Release: 0.9 on 2017-02-17 23:19
SHA: e5c8ead8bcb43c3d74cc9c47429b6fe228fcdff6
Source: https://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/admin-guide/source/compute-live-migration-usage.rst
URL: https://docs.openstack.org/admin-guide/compute-live-migration-usage.html

Tags: admin-guide
Changed in openstack-manuals:
status: New → Confirmed
importance: Undecided → Medium
Changed in openstack-manuals:
assignee: nobody → Bernd Bausch (berndbausch)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to openstack-manuals (master)

Fix proposed to branch: master
Review: https://review.openstack.org/441748

Changed in openstack-manuals:
status: Confirmed → In Progress
Changed in openstack-manuals:
assignee: Bernd Bausch (berndbausch) → Alexandra Settle (alexandra-settle)
Changed in openstack-manuals:
assignee: Alexandra Settle (alexandra-settle) → Bernd Bausch (berndbausch)
Changed in openstack-manuals:
assignee: Bernd Bausch (berndbausch) → Joseph Robinson (joseph-r-email)
Changed in openstack-manuals:
assignee: Joseph Robinson (joseph-r-email) → Bernd Bausch (berndbausch)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to openstack-manuals (master)

Reviewed: https://review.openstack.org/441748
Committed: https://git.openstack.org/cgit/openstack/openstack-manuals/commit/?id=184743edfd2f9e1fe9d3f0289e6d7e5fcde9e33b
Submitter: Jenkins
Branch: master

commit 184743edfd2f9e1fe9d3f0289e6d7e5fcde9e33b
Author: Bernd Bausch <email address hidden>
Date: Mon Mar 6 14:41:39 2017 +0900

    Rewrite of Admin Guide Live Migration Usage

    The Live Migration Usage page was outdated and lacked
    information.

    Change-Id: I85ba063e0de6cbe0f06966d9e2067825d591d093
    Closes-Bug: #1665860

Changed in openstack-manuals:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.