Understanding the responses from lbaas agent to plugin

asked 2014-08-06 08:50:10 -0600

vs38 gravatar image

updated 2014-08-13 19:32:41 -0600

smaffulli gravatar image

hi can anybody explain this responses. i am really blocked in understanding this responses.


i would like know about scenarios that each responses are applicable. also please point me to the documentation or any so that i can get better understanding.

edit retag flag offensive close merge delete


somebody please respond i am really blocked here...!! when a pool/pool member configuration is active..!!

vs38 gravatar imagevs38 ( 2014-08-07 00:38:15 -0600 )edit

2 answers

Sort by ยป oldest newest most voted

answered 2014-08-13 14:45:54 -0600

vs38 gravatar image

updated 2014-08-13 19:31:30 -0600

smaffulli gravatar image

hope this data will help another newbie like me, here is the sequence.

  1. User sends REST API request to Quantum, it is routed to the corresponding Extension and Plugin.
  2. Plugin performs validation of request (schema conformance, values and references check, etc). If validation succeed, HTTP 202 is returned, if not - one of 40x codes (depending on reason).
  3. DB object is updated and object is moved to PENDING_UPDATE state. Request is transformed into task and pushed into queue. The device corresponding to object is locked.
  4. The worker scans queue and picks any task for unlocked device. The task is transmitted to Agent
  5. Agent with help of Driver changes configuration of LB appliance.
  6. If some other user request arrives to the Plugin it is processed a usual way, except of rejecting attempts to update object in PENDING_UPDATE state. If request succeeds Plugin pushes it into queue. If the request is for the locked device, it remain in the queue until device is unlocked.
  7. Once Agent completes work, it replies Plugin with the status. DB is updated and object is moved into ACTIVE or ERROR state. Device is unlocked.

source https://wiki.openstack.org/wiki/Neutr...

edit flag offensive delete link more

answered 2014-08-08 12:33:47 -0600

mpetason gravatar image

Here is a start:


After that you'll probably want to go into the source code to see what it is actually doing for each status. Or what scenarios would cause each status to trigger.

Older source code:


OpenStack provided documentation through their docs site:


edit flag offensive delete link more

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower


Asked: 2014-08-06 08:50:10 -0600

Seen: 113 times

Last updated: Aug 13 '14