VMware: better display names on the backend

Registered by Gary Kotton

Currently it is terribly difficult to debug issues on the back end. On of the pain points is the way in why the back end objects are named. This blueprint will do two things:
1. It will make use of folder name for OpenStack objects. Currently all of the objects are in the root folder and this does not give an admin an easy way to troubleshoot tenant issues. The proposal is to place all instance, images etc. into specific folders.
2. Instances are currently named with the UUID of the instance. This does not give the admin any context. The idea how is to the the display name in addition to the instance

The above visual naming makes an admins life's a whole lot easier.

NOTE: this code is backward compatible. New instances will be created in the folder and have the new naming convention. Old instances are still managed as before. This is due to the fact that they have the instanceUUID property set and this is used for the instance management.

Blueprint information

John Garbutt
Gary Kotton
Gary Kotton
Series goal:
Accepted for mitaka
Milestone target:
milestone icon mitaka-3
Started by
Gary Kotton
Completed by
John Garbutt

Related branches



Gerrit topic: https://review.openstack.org/#q,topic:bp/vmware-better-display-names,n,z

Addressed by: https://review.openstack.org/165060
    VMware: add in folder support on VC

Addressed by: https://review.openstack.org/166608
    VMware: improve instance names on VC

Sorry, we have now hit the non-priority feature freeze for Liberty. You will need to resubmit this blueprint for Mitaka or apply for an exception. For more details on why this is happening, and the rest of the process details, please see: https://wiki.openstack.org/wiki/Nova/Liberty_Release_Schedule
--johnthetubaugy 3rd July 2015

Addressed by: https://review.openstack.org/259753
    VMware: cleanup unit test global variable


Work Items

This blueprint contains Public information 
Everyone can see this information.