yahoo-eng-team team mailing list archive

[LuyaoZhong <605708285@xxxxxx>]

Public bug reported:

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.

** Affects: nova
     Importance: Undecided
     Assignee: LuyaoZhong (luyaozhong)
         Status: In Progress

** Description changed:

  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.
+ the precheck. And backport to T release.

-- 
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):
  In Progress

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