<div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr">Hi, Michael & Adam:<div> </div><div> I only need to confirm the eventlet has no conflict with amphora-agent. Because I</div><div> just need to use eventlet in amphora-agent.</div><div><br></div><div> Michael:</div><div> 1、The os-ken is managed by OpenStack Community now, and neutron-dynamic-routing's</div><div> default driver also is os-ken. I think we should be consistent with the community for later maintenance.</div><div> 2、For the current application scenario, exabgp is a bit too heavy. If use exabgp we need to manage an</div><div> extra service and need to write adaption code for different Linux distributions.</div><div> 3、We can more accurately get the bgp speaker and bgp peer's status and statistics by use Os-Ken's functions,</div><div> for example, peer_down_handler, peer_up_handler, neighbor_state_get. I didn't find similar function in Exabgp.</div><div> 4、Personally, I am more familiar with os-ken.</div><div><br></div><div> Adam:</div><div> Os-Ken is a python library, it implemented bgp protocol. Os-ken manages bgp speaker by starting a green thread.</div><div> So, I need to use eventlet in amphora-agent code.</div><div><br></div><div> Extra illustration:</div><div> Last week, I found the monkey_patch of eventlet will result in gunicorn does not work properly. But now, I resolved</div><div> the problem. We must pass `os=False` to eventlet.monkey_patch when we call eventlet.monkey_patch, if not, the</div><div> gunicorn master process will not exit never.</div><br></div></div></div></div></div></div></div><br><div class="gmail_quote"><div dir="ltr">Michael Johnson <<a href="mailto:johnsomor@gmail.com">johnsomor@gmail.com</a>> 于2019年1月9日周三 上午1:00写道：<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Yes, we do not allow eventlet in Octavia. It leads to a number of<br>
conflicts and problems with the overall code base, including the use<br>
of taskflow.<br>
Is there a reason we need to use the os-ken BGP code as opposed to the<br>
exabgp option that was being used before?<br>
I remember we looked at those two options back when the other team was<br>
developing the l3 option, but I don't remember all of the details of<br>
why exabgp was selected.<br>
<br>
Michael<br>
<br>
On Mon, Jan 7, 2019 at 1:18 AM Jeff Yang <<a href="mailto:yjf1970231893@gmail.com" target="_blank">yjf1970231893@gmail.com</a>> wrote:<br>
><br>
> Hi Michael,<br>
> I found that you forbid import eventlet in octavia.[1]<br>
> I guess the eventlet has a conflict with gunicorn, is that?<br>
> But, I need to import eventlet for os-ken that used to implement bgp speaker.[2]<br>
> I am studying eventlet and gunicorn deeply. Have you some suggestions to resolve this conflict?<br>
><br>
> [1] <a href="https://review.openstack.org/#/c/462334/" rel="noreferrer" target="_blank">https://review.openstack.org/#/c/462334/</a><br>
> [2] <a href="https://review.openstack.org/#/c/628915/" rel="noreferrer" target="_blank">https://review.openstack.org/#/c/628915/</a><br>
><br>
> Michael Johnson <<a href="mailto:johnsomor@gmail.com" target="_blank">johnsomor@gmail.com</a>> 于2019年1月5日周六 上午8:02写道：<br>
>><br>
>> Hi Jeff,<br>
>><br>
>> Unfortunately the team that was working on that code had stopped due<br>
>> to internal reasons.<br>
>><br>
>> I hope to make the reference active/active blueprint a priority again<br>
>> during the Train cycle. Following that I may be able to look at the L3<br>
>> distributor option, but I cannot commit to that at this time.<br>
>><br>
>> If you are interesting in picking up that work, please let me know and<br>
>> we can sync up on that status of the WIP patches, etc.<br>
>><br>
>> Michael<br>
>><br>
>> On Thu, Jan 3, 2019 at 11:19 PM Jeff Yang <<a href="mailto:yjf1970231893@gmail.com" target="_blank">yjf1970231893@gmail.com</a>> wrote:<br>
>> ><br>
>> > Dear Octavia team:<br>
>> > The email aims to ask the development progress about l3-active-active blueprint. I<br>
>> > noticed that the work in this area has been stagnant for eight months.<br>
>> > <a href="https://review.openstack.org/#/q/l3-active-active" rel="noreferrer" target="_blank">https://review.openstack.org/#/q/l3-active-active</a><br>
>> > I want to know the community's next work plan in this regard.<br>
>> > Thanks.<br>
</blockquote></div>