Open Stack

Hi All,

Horizon provided the feature to allow user edit existing flavors, no matter
it is currently used by any instances or not. While Nova doesn't provide
this kind of ability, Horizon achieved this by deleting the old flavor
first and create a new flavor with the requested properties. And the flavor
ID will be changed to a new UUID.

This causes problem when display instances with latest Nova, Horizon
display flavor name by request flavor details using the flavor id returned
by get_instance request, because Nova now moved flavor to api_db, and when
a flavor got deleted, it will be directly removed from the DB, and when
displaying, the field will be "Not Available".

Should we stop support editing existing flavors? It is actually
deleting-and-create.

Maybe we should  at least add WARNING notes about  this when editing
flavors, about how it is actually done and what kind of influence will be
to the existing instances.

Nova now(> microversion 2.47) can reply embedded flavor details including
ram, vcpus, original_name etc.

Since we provided this flavor editing feature and we displayed "name" as a
identifier, after we done some flavor edit, even we fix the above mentioned
problem and displayed the correct flavor name, the flavor details will be
different than the actual instance type.

Thoughts?

BR,

Kevin Zheng
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20170803/36957299/attachment.html>