[openstack-dev] [Neutron][LBaaS] Shim vs Agent Refactor

Brandon Logan brandon.logan at RACKSPACE.COM
Wed Jul 9 22:12:20 UTC 2014


Shim will become quite complicated due to the fact we won't be able to actually send any load balancer information to the driver until a load balancer is linked to a listener, pool, and member.  The reason is because for a vip to be created it needs attributes from a load balancer and listener.  A vip also has a required attribute of pool_id in the old API so all the old driver are expecting a pool_id.  So this means we need a pool first.  Since the subnet_id has been moved off the pool and onto the pool member, we will need to have a pool with at least one member before we can send all that information to the driver.

Now once that is done, it will probably get even crazier with updates and deletes to each one of those entities.

So should time and effort be spent on the shim, which is temporary and eventually thrown away. Or should time be spent on creating a new version of the agent and namspace driver based off the new driver interface, which will need to be done anyway?

Doing the shim could end up being faster than creating a new version of the agent, but since there are going to be a lot of crazy edge cases, I question the stability of it and the time it may take for it to become stable.

One problem with not doing the shim is the older drivers cannot be used with the new API and will have to be updated.  To this, I would argue that there is no benefit to using the new API with an old driver versus using the Old API with the old driver, right now.  Once L7 and TLS get in then yes there would be.

I'd just like to get people's ideas on this.

Thanks,
Brandon
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140709/70c9c7c7/attachment.html>


More information about the OpenStack-dev mailing list