Support online upgrades
This is going to take quite a bit of work. Things to consider here:
* getting all API->DB calls remoted to conductor
* Properly versioning objects and making them compatible between versions
* Ditto for RPC APIs
* How we do DB migrations
* all the docs.
This is going to be partially code, partially user docs, and partially developer/reviewer docs.
Blueprint information
- Status:
- Not started
- Approver:
- None
- Priority:
- High
- Drafter:
- Jim Rollenhagen
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- Discussion
- Series goal:
- Accepted for mitaka
- Implementation:
- Unknown
- Milestone target:
- None
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Make object methods remotable again
Do we need a spec for that? I create a etherpad for this, but a spec should be better. https:/
Addressed by: https:/
Isolate ir-api from DB
Addressed by: https:/
Add Code Review Guide for Ironic
Gerrit topic: https:/
Addressed by: https:/
Add a test to enforce object version bump correctly
Gerrit topic: https:/
Addressed by: https:/
Add a config option [upgrade_
Hi Jim, I've created an RFE bug - https:/
//vdrok 2015-12-15
Addressed by: https:/
Refactor install-guide to configure API/Conductor seperately