Use oslo-versioned-objects to help with dealing with upgrades.

Registered by lvmxh

We are looking to improve the way we deal with versioning (of all sorts db/rpc/rest/templates/plugins). Nova has come up with the idea of versioned objects, that Ironic has also now used. This has now been proposed as an oslo library: https://review.openstack.org/#/c/127532/
And it has be accepted. https://github.com/openstack/oslo.versionedobjects

Versioned-objects will help us deal with DB schema being at a different version than the code expects. This will allow Designate 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.

Now designate has just implemented itself db object.
We should improve it.
1. migrate it to oslo.versionedobjects
2. support version register.

Blueprint information

Status:
Not started
Approver:
None
Priority:
Undefined
Drafter:
lvmxh
Direction:
Needs approval
Assignee:
lvmxh
Definition:
New
Series goal:
None
Implementation:
Unknown
Milestone target:
None

Related branches

Sprints

Whiteboard

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.