Ok, here is the wiki page describing lbaas common agent:
https://wiki.openstack.org/wiki/Neutron/LBaaS/CommonAgentDriver
Thanks,
Oleg
On Thu, Jul 4, 2013 at 9:50 PM, Eugene Nikanorov wrote:
> No, I meant server side, e.g. plugins or plugin drivers.
> RPC api should be designed in such way that
No, I meant server side, e.g. plugins or plugin drivers.
RPC api should be designed in such way that allows sending messages to
proper device driver.
Thanks,
Eugene.
On Thu, Jul 4, 2013 at 12:51 PM, Oleg Bondarev wrote:
> Hi Eugene,
>
> >...RPC API which then is shared between services.
> Did y
Hi Eugene,
>...RPC API which then is shared between services.
Did you mean device drivers rather than services?
Thanks,
Oleg
On Thu, Jul 4, 2013 at 12:42 PM, Eugene Nikanorov
wrote:
> I think the design should be documented on the wiki.
> Major part of such agent should be corresponding RPC AP
I think the design should be documented on the wiki.
Major part of such agent should be corresponding RPC API which then is
shared between services.
That needs to be thought out and discussed.
Thanks,
Eugene.
On Thu, Jul 4, 2013 at 12:27 PM, Oleg Bondarev wrote:
> Hi folks,
>
> While working on
Hi folks,
While working on agent scheduling for LBaaS reference implementation (
https://review.openstack.org/#/c/32137/) I thought that it would be useful
to unify existing agent to make it suite any vendor who wants to use async
mechanism and agent scheduling.
I filed a blueprint on this -
https
