yahoo-eng-team team mailing list archive

[Brandon Logan <brandon.logan@xxxxxxxxxxxxx>]

Public bug reported:

If the neutron lbaas plugin could query the loaded drivers and determine
if a certain feature is supported that the API exposes, then certain
workarounds could be avoided.  This would allow the API to fail fast and
return back a meaningful error to the user explaining the issue instead
of the current options, fail slowly by throwing load balancer in ERROR
state or the driver does somethign different than what the user
intended.

Examples:
1) Currently the API allows for a PING health check, but HAProxy does not support this, but instead of throwing an error, it just uses a TCP health check underneath.

2) This would allow a driver to be able to support a workflow in which
it is responsible for allocating the VIP in whatever way it wants.
Currently a neutron port is created for the VIP in the plugin and passed
down to the driver.  A driver may want to do something different than
that to create a VIP.

One cause for concern is with this implemented, the neutron lbaas API
behavior would not be the same across all deployments.  However, with
the introduction of flavors and it causing the same thing, this
shouldn't be a problem if flavors is not a problem.

** Affects: neutron
     Importance: Undecided
         Status: New


** Tags: lbaas rfe

** Description changed:

  If the neutron lbaas plugin could query the loaded drivers and determine
  if a certain feature is supported that the API exposes, then certain
  workarounds could be avoided.  This would allow the API to fail fast and
  return back a meaningful error to the user explaining the issue instead
  of the current options, fail slowly by throwing load balancer in ERROR
  state or the driver does somethign different than what the user
  intended.
  
  Examples:
  1) Currently the API allows for a PING health check, but HAProxy does not support this, but instead of throwing an error, it just uses a TCP health check underneath.
  
  2) This would allow a driver to be able to support a workflow in which
  it is responsible for allocating the VIP in whatever way it wants.
  Currently a neutron port is created for the VIP in the plugin and passed
  down to the driver.  A driver may want to do something different than
  that to create a VIP.
+ 
+ One cause for concern is with this implemented, the neutron lbaas API
+ behavior would not be the same across all deployments.  However, with
+ the introduction of flavors and it causing the same thing, this
+ shouldn't be a problem if flavors is not a problem.

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

Title:
  LBaaS drivers can be queried to determine whether they support a
  feature the API exposes

Status in OpenStack Neutron (virtual network service):
  New

Bug description:
  If the neutron lbaas plugin could query the loaded drivers and
  determine if a certain feature is supported that the API exposes, then
  certain workarounds could be avoided.  This would allow the API to
  fail fast and return back a meaningful error to the user explaining
  the issue instead of the current options, fail slowly by throwing load
  balancer in ERROR state or the driver does somethign different than
  what the user intended.

  Examples:
  1) Currently the API allows for a PING health check, but HAProxy does not support this, but instead of throwing an error, it just uses a TCP health check underneath.

  2) This would allow a driver to be able to support a workflow in which
  it is responsible for allocating the VIP in whatever way it wants.
  Currently a neutron port is created for the VIP in the plugin and
  passed down to the driver.  A driver may want to do something
  different than that to create a VIP.

  One cause for concern is with this implemented, the neutron lbaas API
  behavior would not be the same across all deployments.  However, with
  the introduction of flavors and it causing the same thing, this
  shouldn't be a problem if flavors is not a problem.

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