Stable Compute Node UUIDs
Nova has long had a dependency on an unchanging hostname on the
compute nodes. This spec aims to address this limitation, at least
from the perspective of being able to detect an accidental change and
avoiding catastrophe in the database that can currently result from a
hostname change, whether intentional or not.
Blueprint information
- Status:
- Complete
- Approver:
- Sylvain Bauza
- Priority:
- Undefined
- Drafter:
- Dan Smith
- Direction:
- Approved
- Assignee:
- Dan Smith
- Definition:
- Approved
- Series goal:
- Accepted for antelope
- 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:/
Add virt/node module for stable uuids
Addressed by: https:/
Pass service ref to init_host(), if exists
Addressed by: https:/
Add get_available_
Addressed by: https:/
WIP: Persist existing node uuids locally
Addressed by: https:/
Make resource tracker use UUIDs instead of names
Addressed by: https:/
WIP: Detect host renames and abort startup
[20230116 bauzas] Spec approved for 2023.1 cycle https:/
Addressed by: https:/
Fixup patch for stable-compute-uuid series
Addressed by: https:/
TURBOWIP: Add a host/node consistency check
Addressed by: https:/
Check our nodes for hypervisor_hostname changes
Addressed by: https:/
Move comment about _destroy_
Addressed by: https:/
Abort startup if nodename conflict is detected
Addressed by: https:/
Stable compute uuid functional tests
Addressed by: https:/
Add docs for stable-compute-uuid behaviors
[20230210 bauzas] Series is fully implemented, incl. docs
