Default 5 Flavors ids should be in the form of UUID instead of 1,2,3,4,5

Registered by sandeep nandal

Summary
=======
IDs of the default 5 flavors must be in UUID form, like other newly created flavors have. There are very rare chance, that a user will create flavor with the name in UUID form, but there are chances, when a user may create flavor with names as 1,2,3,4, or 5. And this will create ambiguity in CLI usage.

Motivation
========
The default 5 flavors of openstack contains the ids :- 1,2,3,4,5 respectively.
If we create more flavors with the names as 1,2,3,4 or 5 then problem arises.
For ex, if user pass the name of newly created flavor as 1 while booting up the instance, then the instance will be booted up considering the input as ID of flavor instead of name of flavor.
But 1 ID is allocated to preexisting flavor. This way wrong flavor will be chosen for booting up the instance.

Description
=========
The default 5 flavors must have IDs as in the UUID form, like other newly created flavors have. There are very rare chance, that a user will create flavor with the name in UUID form, but there are chances, when a user may create flavor with names as 1,2,3,4, or 5.

During creating instance, user needs to provide flavor as argument.
Create instance uses either flavor id or flavor name as same argument to boot up the instance.
During this process, flavor details are fetched considering flavor argument as ID and if it finds some flavor with given ID, then it returns flavor.
But if it doesn't find the flavor with the given ID, then only it tries to look for flavor by considering the argument as flavor name.

The default 5 flavors of openstack contains the ids :- 1,2,3,4,5 respectively.
If we create more flavors with the names as 1,2,3,4 or 5 then problem arises.

For ex, if user pass the name of newly created flavor as 1 while booting up the instance, then the instance will be booted up considering the input as ID of flavor instead of name of flavor.
But 1 ID is allocated to preexisting flavor. This way wrong flavor will be chosen for booting up the instance.

UX
===
- No change is needed for User Interface, User Interface will remain same.

Testing
======
Proper Tests would be added to check the system's behavior after adding this feature.

Outside Dependencies
==================
None.

Requirements Update Required
========================
No specific Update is required for this change, if some external module is planned to be used for this functionality, then we only we will have to update the requirements list.

Doc Impact
=========
There will not be any changes to the User Interface due to this. OpenStack Documentation will be updated in order to inform the user about the changes that will be introduced.

Blueprint information

Status:
Not started
Approver:
None
Priority:
Undefined
Drafter:
sandeep nandal
Direction:
Needs approval
Assignee:
None
Definition:
New
Series goal:
None
Implementation:
Unknown
Milestone target:
None

Related branches

Sprints

Whiteboard

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.