No downtime DB migrations
Registered by
Johannes Erdfelt
Some migrations can take a long time to finish, causing a service to be down for an unacceptable amount of time. The proposed solution is to switch to an expand, migrate, contract model where migrations occur while the services are running.
Since you can't have two blueprints with the same specification URL (already have a Glance blueprint registered):
https:/
Blueprint information
- Status:
- Not started
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- None
- Direction:
- Needs approval
- Assignee:
- Johannes Erdfelt
- Definition:
- New
- Series goal:
- None
- Implementation:
- Unknown
- Milestone target:
- None
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
If you are still working on this, please re-submit via nova-specs. If not, please mark as obsolete, and add a quick comment to describe why. --johnthetubaguy (20th April 2014)
(?)