Referencing Instances Across a Complex Deployment
With the addition of zones to OpenStack, we now have a complication in addressing instances, since currently instances are referenced by their Primary Key, which is an auto-incremented integer. This is part of the current Rackspace API. Adding zones, which each have their own database, means that there is no guarantee of uniqueness among these PKs. We need to discuss alternatives, weighing how well they work, and how they would affect both current code as well as the APIs.
Blueprint information
- Status:
- Complete
- Approver:
- Vish Ishaya
- Priority:
- Essential
- Drafter:
- Ed Leafe
- Direction:
- Approved
- Assignee:
- Ed Leafe
- Definition:
- Approved
- Series goal:
- Accepted for diablo
- Implementation:
-
Implemented
- Milestone target:
-
2011.3
- Started by
- Ed Leafe
- Completed by
- Vish Ishaya
Whiteboard
First appeared in diablo-2
result of discussion was to switch to UUIDs for everything
- Another idea worth considering would be to assign a primary ipv6 address to every instance; these are equivalent to UUIDs (128-bit integers). Then, if desired, deployments could use DNS to locate the instance across zones without revealing any additional internal structure. So we could change the spec to use UUIDs, but these could be replaced by ipv6 addresses later without changing the API or database.
Work Items
Dependency tree
* Blueprints in grey have been implemented.
