[openstack-dev] [Quantum][LBaaS] - LBaaS Extension in Quantum Plugin

balaji patnala patnala003 at gmail.com
Thu Mar 14 14:09:38 UTC 2013


Hi Eugene,

*
*
*>With current lbaas implementation the link that you've provided is not
actual as current implementation has adopted different architecture.*

Can you point me to the links for current implementation details.

As well the confusion is like the general Plug-in  and Agent architecture
[similar to OVS], we have in OS is like Plug-in will be in Controller and
Agent has to be on the Compute Node.

So, when we are trying for Service Insertion, do we need to have same
architecture as Plug-in and Agent above or it should be generic in such a
way that independent of underlying Hardware/Products, We should be able to
bring up services.

*>Current implementation only supports haproxy-on-the-host solution so it's
not suitable for hardware/VM LBs.*

So, is this similar to current L3_Agent daemon we have in Quantum for
Folsom release?

Thanks,
Balaji.P

On Thu, Mar 14, 2013 at 5:25 PM, Eugene Nikanorov
<enikanorov at mirantis.com>wrote:

> Hi Balaji,
> *
> *
> With current lbaas implementation the link that you've provided is not
> actual as current implementation has adopted different architecture.
>
> *> Can you please through some light on the Agent part of the
> architecture like where exactly the agent will be running like OpenStack
> Controller Node or OpenStack Compute Node.?*
> In grizzly, lbaas agent should run on some node - it could be compute node
> or network controller node.
> The only important is that there MUST be only one instance of lbaas agent
> running.
>
> Current implementation only supports haproxy-on-the-host solution so it's
> not suitable for hardware/VM LBs.
> Support for such use case is planned in the next release.
>
> Thanks,
> Eugene.
>
> On Thu, Mar 14, 2013 at 3:46 PM, balaji patnala <patnala003 at gmail.com>wrote:
>
>> Hi Ilya,
>>
>> As described in the document given in the below link:
>>
>> http://wiki.openstack.org/Quantum/LBaaS/Agent
>>
>> Agent part will be running on Compute Node or Controller Node ?.
>>
>> I guess it should be on the Controller Node only. As the driver
>> abstraction layer is for choosing the right driver for the device it has to
>> connect like Driver A to the Device Type A. etc. [This approach is for HW
>> device LB]
>>
>> If we want to have SW-based-LB like SLB VM, does the above architecture
>> is valid?
>>
>> Can you please through some light on the Agent part of the architecture
>> like where exactly the agent will be running like OpenStack Controller Node
>> or OpenStack Compute Node.?
>>
>> Thanks in advance.
>>
>> Regards,
>> Balaji.P
>>
>>  On Thu, Feb 7, 2013 at 8:26 PM, Ilya Shakhat <ishakhat at mirantis.com>wrote:
>>
>>> Hi Pattabi,
>>>
>>> Code for LBaaS agent and driver API is on review. You may check it from
>>> Gerrit topic https://review.openstack.org/#/c/20579. Instructions on
>>> how to run the code in DevStack environment are at
>>> http://wiki.openstack.org/Quantum/LBaaS/Agent. Driver API is documented
>>> at http://wiki.openstack.org/Quantum/LBaaS/DriverAPI
>>>
>>> Thanks,
>>> Ilya
>>>
>>>
>>> 2013/2/7 Avishay Balderman <AvishayB at radware.com>
>>>
>>>>   The basic lbaas driver is not committed yet – it is under review.****
>>>>
>>>> ** **
>>>>
>>>> *From:* Pattabi Ayyasami [mailto:pattabi at Brocade.com]
>>>> *Sent:* Thursday, February 07, 2013 3:06 AM
>>>> *To:* openstack-dev at lists.openstack.org
>>>> *Subject:* [openstack-dev] [Quantum][LBaaS] - LBaaS Extension in
>>>> Quantum Plugin****
>>>>
>>>> ** **
>>>>
>>>> Hi,****
>>>>
>>>> ** **
>>>>
>>>> I am in the process of adding vendor specific plugin implementation for
>>>> LBaaS as a service. I have my stand alone driver ready and would like to
>>>> integrate with the framework.****
>>>>
>>>> I looked at the latest Git Hub https://github.com/openstack/quantumrepository. I do not find any code that allows me to hook my plugin code to
>>>> the framework.****
>>>>
>>>> ** **
>>>>
>>>> Really appreciate if someone could provide me any pointers on how I go
>>>> about doing it.****
>>>>
>>>> ** **
>>>>
>>>> Regards,****
>>>>
>>>> Pattabi****
>>>>
>>>> _______________________________________________
>>>> OpenStack-dev mailing list
>>>> OpenStack-dev at lists.openstack.org
>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>>
>>>>
>>>
>>> _______________________________________________
>>> OpenStack-dev mailing list
>>> OpenStack-dev at lists.openstack.org
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>
>>>
>>
>> _______________________________________________
>> OpenStack-dev mailing list
>> OpenStack-dev at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> 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/20130314/dbba107a/attachment.html>


More information about the OpenStack-dev mailing list