Open Stack

Just to add a little flavor and a slightly different twist from what Stephen wrote:

- The logging noop driver is indeed a good first place to start.

- The haproxy reference driver is the *only* driver that utilizes the lbaas-agent, and it’s being deprecated soon, so…

Most vendor implementations have some sort of outside agent/daemon of their own that can be interacted with directly. So unless you need to make async driver calls and you have no mechanism to do that yourself, I would avoid doing things the way the current haproxy driver is doing them.

For a driver that transforms neutron objects into REST calls and then converts the responses, I’d suggest taking a look at the octavia driver after the logging noop driver.

Please don’t hesitate to hop into #openstack-lbaas with any questions, in addition to here.

Thanks,
doug



> On Sep 10, 2015, at 7:53 PM, Stephen Balukoff <sbalukoff at bluebox.net> wrote:
> 
> Srikumar--
> 
> I'm not aware of any particular write-up. The best advice I have is to start with the logging noop driver and refer to the reference haproxy namespace driver to see what these are doing to implement the functionality of LBaaS v2.
> 
> Sorry! I wish I had better news for you.
> 
> Stephen
> 
> On Fri, Sep 4, 2015 at 10:36 AM, Srikumar Chari <srikumar at appcito.net <mailto:srikumar at appcito.net>> wrote:
> Hello,
> 
> I am trying to write an custom lbaas v2.0 driver. Was wondering if there's a document on how to go about that. I see a number of implementations as part of the source code but they all seem to be different. For instance HAProxy is completely different when compared to the other vendors. I am assuming that HAProxy is the "standard" as it is the default load balancer for OpenStack. Is there a design doc or some kinda write up?
> 
> This thread was the closest I could get to a write-up: https://openstack.nimeyo.com/21628/openstack-dev-neutron-lbaas-need-help-with-lbaas-drivers <https://openstack.nimeyo.com/21628/openstack-dev-neutron-lbaas-need-help-with-lbaas-drivers>.
> 
> I guess I could reverse engineering the HAProxy namespace driver but I am probably going to miss some of the design elements. Any help/pointers/links would be great.
> 
> thanks
> Sri
> 
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe <http://OpenStack-dev-request@lists.openstack.org/?subject:unsubscribe>
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev>
> 
> 
> 
> 
> -- 
> Stephen Balukoff
> Principal Technologist
> Blue Box, An IBM Company
> www.blueboxcloud.com <http://www.blueboxcloud.com/>
> sbalukoff at blueboxcloud.com <mailto:sbalukoff at blueboxcloud.com>
> 206-607-0660 x807
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150910/5feba995/attachment.html>