Link Compute Objects by ID
The ``ComputeNode``, ``Service``, and ``Instance`` objects form the primary
data model for our compute nodes. Instances run on compute nodes, which are
managed by services. We rely on this hierarchy to know where instances are
(physically) as well as which RPC endpoint to send messages to for management.
Currently, the linkage between all three objects is a relatively loose and
string-based, association using the hostname of the compute node and/or the
``CONF.host`` values. This not only makes an actual/intentional rename very
difficult, but also risks breaking critical links as a result of an
*accidental* one.
Blueprint information
- Status:
- Complete
- Approver:
- sean mooney
- Priority:
- Undefined
- Drafter:
- Dan Smith
- Direction:
- Approved
- Assignee:
- Dan Smith
- Definition:
- Approved
- Series goal:
- Accepted for bobcat
- Implementation:
-
Implemented
- Milestone target:
- None
- Started by
- Sylvain Bauza
- Completed by
- Sylvain Bauza
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Populate ComputeNode.
Addressed by: https:/
Add compute_id columns to instances, migrations
Addressed by: https:/
Add dest_compute_id to Migration object
Addressed by: https:/
Add compute_id to Instance object
Addressed by: https:/
Online migrate missing Instance.compute_id fields
Addressed by: https:/
Add online migration for Instance.compute_id
[20230612 bauzas] Spec got approved for Bobcat https:/