<div dir="ltr">I think the design should be documented on the wiki.<div style>Major part of such agent should be corresponding RPC API which then is shared between services.</div><div style>That needs to be thought out and discussed.</div>
<div style><br></div><div style>Thanks,</div><div style>Eugene.</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Jul 4, 2013 at 12:27 PM, Oleg Bondarev <span dir="ltr"><<a href="mailto:obondarev@mirantis.com" target="_blank">obondarev@mirantis.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi folks,<div><br></div><div>While working on agent scheduling for LBaaS reference implementation (<a href="https://review.openstack.org/#/c/32137/" target="_blank">https://review.openstack.org/#/c/32137/</a>) 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. </div>

<div>I filed a blueprint on this - <a href="https://blueprints.launchpad.net/neutron/+spec/lbaas-common-agent-driver" target="_blank">https://blueprints.launchpad.net/neutron/+spec/lbaas-common-agent-driver</a></div><div>
So what do you guys think? Wishes/suggestions are welcome.</div>
<div><br></div><div>Thanks,</div><div>Oleg</div><div><br></div></div>
<br>_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br></div>