yahoo-eng-team team mailing list archive

[Drew Thorstensen <thorst@xxxxxxxxxx>]

The issue with the PowerVM driver is actually in neutron.  I set up a
libvirt environment, and the difference is that the PowerVM VIF is for
some reason in a BUILD state, where as it is ACTIVE in libvirt.

If the PowerVM VIF was in an ACTIVE state, this wouldn't occur, and no
neutron events would need to be waited for.

I'll investigate what's going on with the port state for networking-
powervm.  The state up is being sent...so this requires some
verification.


It is true that the nova instance.host isn't updated until after the spawn in nova.  That could be investigated...but this is the root reason why PowerVM is seeing different behavior than Libvirt.

** Project changed: nova => networking-powervm

** Changed in: networking-powervm
     Assignee: Wen Zhi Yu (yuywz) => Drew Thorstensen (thorst)

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

Title:
  instance.host not updated on evacuation

Status in networking-powervm:
  In Progress

Bug description:
  I'm working on the nova-powervm driver for Mitaka and trying to add
  support for evacuation.

  The problem I'm hitting is that instance.host is not updated when the
  compute driver is called to spawn the instance on the destination
  host.  It is still set to the source host.  It's not until after the
  spawn completes that the compute manager updates instance.host to
  reflect the destination host.

  The nova-powervm driver uses instance events callback mechanism during
  plug VIF to determine when Neutron has finished provisioning the
  network.  The instance events code sends the event to instance.host
  and hence is sending the event to the source host (which is down).
  This causes the spawn to fail and also causes weirdness when the
  source host gets the events when it's powered back up.

  To temporarily work around the problem, I hacked in setting
  instance.host = CONF.host; instance.save() in the compute driver but
  that's not a good solution.

To manage notifications about this bug go to:
https://bugs.launchpad.net/networking-powervm/+bug/1535918/+subscriptions