yahoo-eng-team team mailing list archive

[OpenStack Infra <1823043@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.opendev.org/650444
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=abe041ae1cc42d9a3ade187b7c930b7c6c3a9d5f
Submitter: Zuul
Branch:    master

commit abe041ae1cc42d9a3ade187b7c930b7c6c3a9d5f
Author: Matt Riedemann <mriedem.os@xxxxxxxxx>
Date:   Fri Apr 5 17:04:59 2019 -0400

    Document restrictions for moving servers between availability zones
    
    There was nothing clearly documented about move operations with
    respect to AZ restrictions, i.e. when a server can move between
    zones or not, and how forcing a target host during evacuate or
    live migration can break tracking of the instance for it's orginally
    intended zone. This adds documentation around that topic.
    
    Change-Id: I7466826780ea8a6b3d3df93f0e85f009a437b743
    Closes-Bug: #1823043


** Changed in: nova
       Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1823043

Title:
  Docs insufficiently clear on the intersection of availalability zones,
  force, and cold and live migrations

Status in OpenStack Compute (nova):
  Fix Released

Bug description:
  
  It's hard to find a single place in the nova docs where the impact of availability zones (including default) on the capabilities of live or cold migrations is clear

  In https://docs.openstack.org/nova/latest/user/aggregates.html
  #availability-zones-azs is probably a good place to describe what's
  going on. Some of the rules are discussed in IRC at

  http://eavesdrop.openstack.org/irclogs/%23openstack-nova/%23openstack-
  nova.2019-04-03.log.html#t2019-04-03T15:22:39

  The gist is that when a server is created, if it is created in an AZ
  (either an explicit one, or in the default 'nova' zone) it is required
  to stay in that AZ for all move operations unless there is a force,
  which can happen in a live migrate or evacuate.

  (Caveats abound in this area, see the IRC log for more discussion
  which may help to flavor the docs being created.)

  The reasoning for this, as far as I can tell, is that requesting an AZ
  is a part of the boot constraints and we don't want the moved server
  to be in violation of its own constraints.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1823043/+subscriptions