Agreed with Artur, we ended up with a BP instead of a bug because bugs
bump owners back and forth. I closed the bug as Invalid, BP is still for
Pike.
** Changed in: neutron
Status: Triaged => In Progress
** Changed in: neutron
Status: In Progress => Invalid
** Changed in: neutron
Assignee: Justin Hammond (justin-hammond) => (unassigned)
** Changed in: neutron
Milestone: pike-1 => None
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1522102
Title:
[RFE] use oslo-versioned-objects to help with dealing with upgrades
Status in neutron:
Invalid
Bug description:
This is a rework and re-submission of the old blueprint:
https://blueprints.launchpad.net/neutron/+spec/versioned-objects
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
Also heat's versioned objects is base on oslo. oslo.versionedobjects
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 dependent code across the code base.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1522102/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : [email protected]
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
