Enforce unique instance uuid in data model
The instances.uuid column in the data model is not unique but by definition a UUID should be unique, and given how it's used within nova and across other openstack services like glance, neutron, ceilometer, etc, it should be unique. Furthermore, there are Foreign Keys created against instances.uuid so it should be unique (this is a requirement for DB2 support and blueprint db2-database).
The instances.uuid field is enforced to be unique at the nova objects layer today (see nova.objects.
The related nova-spec provides the detailed information on the blueprint design.
Blueprint information
- Status:
- Complete
- Approver:
- John Garbutt
- Priority:
- Low
- Drafter:
- Matt Riedemann
- Direction:
- Needs approval
- Assignee:
- Matt Riedemann
- Definition:
- Approved
- Series goal:
- Accepted for kilo
- Implementation:
- Implemented
- Milestone target:
- 2015.1.0
- Started by
- John Garbutt
- Completed by
- Matt Riedemann
Related branches
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Enforce unique instance uuid in data model
Gerrit topic: https:/
Addressed by: https:/
WIP: Enforce unique instance uuid in data model
Not all the reviews have +2s and are not all are close to approval, so moving to juno-3. But please move this back to juno-2, should you get your patches approved in time. --johnthetubaguy 21st July 2014
Gerrit topic: https:/
Sorry, this does not have enough positive reviews to make it for juno-3, please resubmit for kilo. For more information, please contact me (johnthetubaguy) via IRC or email. --johnthetubaguy 2nd September 2014
Addressed by: https:/
(Re)Propose "Enforce unique instance uuid in data model"
Approved now spec is approved for kilo. --johnthetubaguy 14th October 2014
Work Items
Dependency tree
* Blueprints in grey have been implemented.