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/
And it has be accepted. https:/
Also heat's versioned objects is base on oslo. oslo.versionedo
Versioned-objects will help us deal with DB schema being at a different version than the code expects. This will allow Neutron 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:
- None
- Priority:
- Undefined
- Drafter:
- Ihar Hrachyshka
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- Obsolete
- Series goal:
- None
- Implementation:
- Unknown
- Milestone target:
- next
- Started by
- Completed by
- Armando Migliaccio
Related branches
Related bugs
Sprints
Whiteboard
Nov-09-2015(armax): If someone is interested in pursuing it, this must be re-submitted according to guidelines defined in [1]
[1] http://
To be rebooted.
-----------------
Oct-19-2015(armax): This will have to looked into. Assigning to Ihar for further triaging.
@Ihar: do we have an RFE for this? I recall you mentioned interest in this area.
Mere introduction of oslo.versionedo
We probably need more fine grained RFEs reported in LP for each aspect of upgrade story. We'll have upgrade discussions on summit next week and afterwards we'll come up with more specific requests.