Use oslo-versioned-objects to help with dealing with upgrades.
We are looking to improve the way we deal with versioning (of all sorts db/rpc/
https:/
Versioned-objects will help us deal with DB schema being at a different version than the code expects. This will allow Heat to be operated safely during upgrades.
Looking forward as we pass more and more data over RPC we can make use of versioned-objects to ensure upgrades happen without spreading the version dependant code across the code base.
Blueprint information
- Status:
- Complete
- Approver:
- Angus Salkeld
- Priority:
- Medium
- Drafter:
- Angus Salkeld
- Direction:
- Approved
- Assignee:
- Michał Jastrzębski
- Definition:
- Approved
- Series goal:
- Accepted for kilo
- Implementation:
- Implemented
- Milestone target:
- 2015.1.0
- Started by
- Angus Salkeld
- Completed by
- Angus Salkeld
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
First objects - stack and raw template
Addressed by: https:/
Versioned objects - UserCreds
Gerrit topic: https:/
Gerrit topic: https:/
Addressed by: https:/
Versioned objects - Resource
Addressed by: https:/
Versioned object - SoftwareDeployment
Addressed by: https:/
Versioned objects - Event
Addressed by: https:/
Versioned objects - Snapshot
Addressed by: https:/
Versioned objects - ResourceData
Addressed by: https:/
Versioned object - WatchRule and WatchData
Addressed by: https:/
Versioned object - SoftwareConfig
Addressed by: https:/
Versioned object Service
Addressed by: https:/
Versioned-
Addressed by: https:/
Fixes StackWatchService to use objects in place of db
Addressed by: https:/
Versioned-
Addressed by: https:/
Fixes SoftwareConfigS
Addressed by: https:/
Unit test case migration for Resource object
Addressed by: https:/
Unit test case migration for Event object
Addressed by: https:/
Unit test case migration for Watch data and Rule object
Addressed by: https:/
Unit test case migration for Stack object
Gerrit topic: https:/
Addressed by: https:/
Register all objects