Make evacuate more robust (partial)
Right now, evacuate makes decisions based on circumstantial data, which is very dangerous. We should make it explicit so that it doesn't make bad decisions and delete data, just because it thinks an evacuate may have happened.
Blueprint information
- Status:
- Complete
- Approver:
- John Garbutt
- Priority:
- Medium
- Drafter:
- Dan Smith
- Direction:
- Approved
- Assignee:
- Dan Smith
- Definition:
- Approved
- Series goal:
- Accepted for liberty
- Implementation:
- Implemented
- Milestone target:
- 12.0.0
- Started by
- John Garbutt
- Completed by
- John Garbutt
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Add robustify-evacuate spec
Gerrit topic: https:/
Addressed by: https:/
Add migration_type to Migration database model
Addressed by: https:/
Add migration_type to Migration object
Addressed by: https:/
Set migration_type for existing cold migrations and resizes
Addressed by: https:/
WIP: API support for migration_type
Addressed by: https:/
Make live migration create a migration object record
Addressed by: https:/
Allow querying for migrations by source_compute only
Addressed by: https:/
Make evacuate leave a record for the source compute host to process
Addressed by: https:/
Add some notifications to the evacuate path
Addressed by: https:/
Make evacuate update the migration object along the way
Addressed by: https:/
Fix incorrect enum in Migration object
Gerrit topic: https:/
Addressed by: https:/
Define migration states and transitions and use when changing status