← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1396405] [NEW] why neutron agent use loop to detect the port's change, not use rpc call ?

 

Public bug reported:

I found that all neutron agent has a loop to detect the hypervisor's ports change and create port for instance, 
But I found that neutron plugion will send a RPC  call with fucion:AgentNotifierAPI, 
if agent can write a function in RPCCall Back, it can get the message and then create the port.

so I feel puzzled, why agent does not use rpc callback function to
create port, but use loop to make it?

** Affects: neutron
     Importance: Undecided
         Status: New

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

Title:
  why neutron agent use loop to detect the port's change, not use rpc
  call ?

Status in OpenStack Neutron (virtual network service):
  New

Bug description:
  I found that all neutron agent has a loop to detect the hypervisor's ports change and create port for instance, 
  But I found that neutron plugion will send a RPC  call with fucion:AgentNotifierAPI, 
  if agent can write a function in RPCCall Back, it can get the message and then create the port.

  so I feel puzzled, why agent does not use rpc callback function to
  create port, but use loop to make it?

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


Follow ups

References