yahoo-eng-team team mailing list archive

[OpenStack Infra <1863605@xxxxxxxxxxxxxxxxxx>]

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

commit db93b704cecdb72e9c23c7a4c07786f67bcfe7b2
Author: LuyaoZhong <luyao.zhong@xxxxxxxxx>
Date:   Mon Feb 17 11:19:42 2020 +0000

    bug-fix: Reject live migration with vpmem
    
    Reject live migration if there are virtual persistent memory resources.
    Otherwise, if dest host has same vpmem backend file name as that used
    by instance, live migration will succeed and these files will be used
    but not tracked in Nova; if dest host has no those vpmems, it will
    trigger an error.
    
    Change-Id: I900f74d482fc87da5b1b5ec9db2ad5aefcfcfe7a
    Closes-bug: #1863605
    Implements: blueprint support-live-migration-with-virtual-persistent-memory


** 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/1863605

Title:
  live migration with vpmem will go to error in Train

Status in OpenStack Compute (nova):
  Fix Released

Bug description:
  We introduced vpmem support in Train release, including
  create/resize/cold migration, but not live migration(with
  libvirt/qemu).

  Since live migration will essentially rely on an libvirt xml, for vpmem there will be backend files configued in xml, if we live migrate an instance with vpmem under Train release, we may got two
  unexpected results:

  1. If the dest host has the same vpmem backend files as that used by instance on source host,
  the live migration will succeed but the vpmems consumed on dest host will not be tracked.

  2. If the dest host doesn't have those vpmems, the live migration will
  fail.

  We need reject the live migration with vpmem in nova conductor when do
  the precheck. And backport to T release.

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