← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1192192] Re: Nova initiated Live Migration regression for vmware VCDriver

 

The support matrix clarifies that this is not supported and the code
raises an exception. The VMWare folks surely know this limitation of
their driver. End users and developers are therefore informed. I see no
need to keep this bug report open.

** Changed in: nova
       Status: Confirmed => Opinion

-- 
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/1192192

Title:
  Nova initiated Live Migration regression for vmware VCDriver

Status in OpenStack Compute (nova):
  Opinion

Bug description:
  Nova's Live Migration feature should work with hosts in the same
  cluster.  We can't specify hosts in a cluster to move between! That
  makes the live-migration feature effectively disabled.

  > I've found here
  > <https://wiki.openstack.org/wiki/HypervisorSupportMatrix>that ESX/VC
  > drivers supports live-migration, also i found related method in
  > code, it uses vmware API "MigrateVM_Task" function.
  >
  > But i couldn't understand how i should use live-migration:
  >
  >    - standalone ESXi hosts not supports any migration. Therefore
  >    VMWareESXDriver also not supports migration. Correct, if am wrong.
  >    - In case vCenter (VMWareVCDriver) i could use vMotion to migrate VMs
  >    between members of cluster. But nova sees cluster as a single "host" and
  >    thru "nova live-migration VM" scheduler raise exception "NoValidHost: No
  >    valid host was found."
  >
  > My question is: What is the use-case of
  > this<https://github.com/openstack/nova/blob/stable/grizzly/nova/virt/vmwareapi/vmops.py#L1018>function

  See: http://docs.openstack.org/trunk/openstack-compute/admin/content
  /live-migration-usage.html

  Note: one possible fix for this is to implement a migration strategy
  that can move between hosts not in the same cluster.

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