yahoo-eng-team team mailing list archive

[Miguel Angel Ajo <majopela@xxxxxxxxxx>]

Public bug reported:

Liberty introduced the RPC callback mechanism, which is mainly used by QoS so far, and planned
to be reused in general as notification for neutron versioned objects, when we have those more
widely implemented.

The mechanism relies on updating agents with fanout notifications per object version, as versioned
objects have the ability to downgrade themselves before serialization, allowing older agents
to still understand such objects.

We lack a mechanism to identify the running agent versions, and calculate, on realtime, the version
set that we need to fanout for every resource type we push through the API to the RPC callback
subscribers.

A devref with the logic was merged here:
https://review.openstack.org/#/c/241154/

Implementation is being developed on this topic:
https://review.openstack.org/#/q/topic:rpccallback-upgrades

** Affects: neutron
     Importance: Medium
     Assignee: Miguel Angel Ajo (mangelajo)
         Status: In Progress

** Changed in: neutron
   Importance: Undecided => High

** Changed in: neutron
     Assignee: (unassigned) => Miguel Angel Ajo (mangelajo)

** Changed in: neutron
   Importance: High => Medium

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1535247

Title:
  rpc callback mechanism does not support upgrades

Status in neutron:
  In Progress

Bug description:
  Liberty introduced the RPC callback mechanism, which is mainly used by QoS so far, and planned
  to be reused in general as notification for neutron versioned objects, when we have those more
  widely implemented.

  The mechanism relies on updating agents with fanout notifications per object version, as versioned
  objects have the ability to downgrade themselves before serialization, allowing older agents
  to still understand such objects.

  We lack a mechanism to identify the running agent versions, and calculate, on realtime, the version
  set that we need to fanout for every resource type we push through the API to the RPC callback
  subscribers.

  A devref with the logic was merged here:
  https://review.openstack.org/#/c/241154/

  Implementation is being developed on this topic:
  https://review.openstack.org/#/q/topic:rpccallback-upgrades

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1535247/+subscriptions