yahoo-eng-team team mailing list archive

Thread
Date

[Bug 1257038] Re: VMware: instance names can be edited, breaks nova-driver lookup

To: yahoo-eng-team@xxxxxxxxxxxxxxxxxxx
From: Thierry Carrez <thierry.carrez+lp@xxxxxxxxx>
Date: Wed, 05 Mar 2014 13:11:19 -0000
Reply-to: Bug 1257038 <1257038@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

** Changed in: nova
       Status: Fix Committed => 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/1257038

Title:
  VMware: instance names can be edited, breaks nova-driver lookup

Status in OpenStack Compute (Nova):
  Fix Released
Status in The OpenStack VMwareAPI subTeam:
  Fix Committed

Bug description:
  Currently the VMware Nova Driver relies on the VM name in vCenter/ESX
  to match the UUID in Nova. The name can be easily edited by vCenter
  administrators and break Nova administration of VMs. A better solution
  should be found allowing the Nova Compute Driver for vSphere to look
  up VMs by a less volatile and publicly visible mechanism.

  EDIT:
  A fix would make the link between vSphere and Nova more solid and involve using a vSphere metadata value that cannot be easily edited. Currently the UUID is stored as an extra config metadata property inside vSphere (associated with the instance's virtual-machine) and
  this value is not easy to accidentally change. That would make the link much more robust.

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