Stop using both flavors and instance types, as they are synonyms
Nova currently uses the terms flavor and instance type interchangeably in both user facing tools and in code. Lets pick just one.
Blueprint information
- Status:
- Started
- Approver:
- Russell Bryant
- Priority:
- Undefined
- Drafter:
- Joe Gordon
- Direction:
- Needs approval
- Assignee:
- Matt Riedemann
- Definition:
- Review
- Series goal:
- None
- Implementation:
-
Good progress
- Milestone target:
- None
- Started by
- Joe Gordon
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
"russellb: stick with our own terminology (flavor) except when specifically doing EC2 handling IMO" ~ 2013-3-4
Gerrit topic: https:/
Addressed by: https:/
Rename nova.compute.
Addressed by: https:/
Rename functions in nova.compute.
Addressed by: https:/
Change db.api.
Addressed by: https:/
Use db.flavor_ instead of db.instance_type_
Addressed by: https:/
Clarify instance_type vs flavor in nova-manage
Addressed by: https:/
Remove instance_type* proxy methods from nova.db.api
Gerrit topic: https:/
Addressed by: https:/
Rename virtapi.
Addressed by: https:/
More instance_type -> flavor renames in db.api
Addressed by: https:/
Rename InstanceType exceptions to Flavor
Addressed by: https:/
Rename instance_type parameter in migrate_
Addressed by: https:/
Rename instance_type to flavor in baremetal virt driver
Addressed by: https:/
Rename instance_type to flavor in test_utils.py
Addressed by: https:/
Rename instance_type to flavor in nova.tests.utils
Addressed by: https:/
Rename instance_type to flavor in xenapi virt driver
Addressed by: https:/
Rename instance_type to flavor in hyper-v virt driver
Addressed by: https:/
Rename instance_type to flavor in vmware virt driver tests
Addressed by: https:/
Rename instance_type to flavor in libvirt virt driver tests
Addressed by: https:/
Rename instance_type to flavor in nova.network tree
Addressed by: https:/
Rename instance_type to flavor in nova.cloudpipe
Addressed by: https:/
Rename instance_type to flavor in nova.utils and nova.compute.utils
Addressed by: https:/
Rename instance_type to flavor in notifications
Addressed by: https:/
Remove get_instance_type from nova.compute.api
Unapproved - please re-submit via nova-spec --johnthetubagy (20th March 2014)
Removed from next, as next is now reserved for near misses from the last milestone --johnthetubaguy
Addressed by: https:/
Rename instance_type to flavor in notifications
Addressed by: https:/
Virt: change instance_type to flavor
Addressed by: https:/
object-ify flavors manager side of the RPC
Work Items
Work items:
Rename files from instance_type(s) to flavor(s): DONE
Rename variables: INPROGRESS
Make sure instance_type is only in EC2 handling code: INPROGRESS
Make sure instance_type is not in python-novaclient: TODO
Update nova docs: TODO
Remove nova.db.api proxies: DONE
Rename nova.virt.
Rename instance_type_get in the APIs: TODO
Rename arg in migrate_
Final pass on tests and misc cleanup: TODO
Rename exceptions: DONE
Rename DB models: TODO
Cleanup nova.test.utils: INPROGRESS
