instance directory naming update to use uuid
Bug #1186944 reported by
Yaguang Tang
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Medium
|
Yaguang Tang | ||
Grizzly |
Fix Released
|
Medium
|
Gary Kotton | ||
VMwareAPI-Team |
Fix Released
|
Critical
|
Unassigned |
Bug Description
The VMware Hyper still use instance-000000xx template to name instance directory. which will face the same problem that libvirt
faces. so change the directory naming of VMware Hyper.
Changed in nova: | |
assignee: | nobody → Yaguang Tang (heut2008) |
tags: | added: vmware |
Changed in nova: | |
importance: | Undecided → Medium |
milestone: | none → havana-2 |
Changed in nova: | |
status: | Fix Committed → Fix Released |
tags: | removed: grizzly-backport-potential in-stable-grizzly |
tags: |
added: vmware-co-preferred removed: vmware |
tags: | added: vmware |
tags: | removed: vmware-co-preferred |
Changed in openstack-vmwareapi-team: | |
status: | New → Fix Released |
Changed in openstack-vmwareapi-team: | |
importance: | Undecided → Medium |
Changed in openstack-vmwareapi-team: | |
importance: | Medium → High |
importance: | High → Critical |
Changed in nova: | |
milestone: | havana-2 → 2013.2 |
To post a comment you must log in.
if you are going to change the name of the instance directory, we should probably change the name of the instance itself as well. This is the primary means by which the VM is identified for later changes, as the driver does not store any vCenter UUIDs.