| 2020-02-17 12:10:04 |
LuyaoZhong |
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. |
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. |
|
