Use VersionedObjectSerializer for RPC push/pull interfaces

Bug #1507654 reported by Ihar Hrachyshka
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
neutron
Won't Fix
Low
Artur Korzeniewski

Bug Description

Instead of reimplementing the serialization in neutron, allow oslo.versionedobjects to handle it by using their own serializer.

Tags: qos oslo
Changed in neutron:
importance: Undecided → Low
tags: added: oslo qos
Changed in neutron:
status: New → Confirmed
assignee: nobody → Ihar Hrachyshka (ihar-hrachyshka)
Changed in neutron:
assignee: Ihar Hrachyshka (ihar-hrachyshka) → Artur Korzeniewski (artur-korzeniewski)
status: Confirmed → In Progress
Revision history for this message
Nate Johnston (nate-johnston) wrote :

Is there a change being worked on that addresses this, Artur?

Revision history for this message
Artur Korzeniewski (artur-korzeniewski) wrote :

Hi Nate,
the patch: https://review.openstack.org/#/c/269056/
is converting the standard RPC serializer to Oslo VersionedObjectSerializer.

So the case is resolved there, but we decided that since no object is pushed via standard RPC interface, we do not want this change to be merged. Objects are pushed via RPC callback mechanism, and there is no problem with sending the OVO over that one.

Revision history for this message
Miguel Angel Ajo (mangelajo) wrote :

moved to won't fix until other endpoints use OVOs, and then we can reconsider this.

Changed in neutron:
status: In Progress → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.