[octavia] What is our next plan about 'l3-active-active' blueprint?

Michael Johnson johnsomor at gmail.com
Tue Jan 8 17:00:24 UTC 2019

Yes, we do not allow eventlet in Octavia. It leads to a number of
conflicts and problems with the overall code base, including the use
of taskflow.
Is there a reason we need to use the os-ken BGP code as opposed to the
exabgp option that was being used before?
I remember we looked at those two options back when the other team was
developing the l3 option, but I don't remember all of the details of
why exabgp was selected.


On Mon, Jan 7, 2019 at 1:18 AM Jeff Yang <yjf1970231893 at gmail.com> wrote:
> Hi Michael,
>     I found that you forbid import eventlet in octavia.[1]
>     I guess the eventlet has a conflict with gunicorn, is that?
>     But, I need to import eventlet for os-ken that used to implement bgp speaker.[2]
>     I am studying eventlet and gunicorn deeply. Have you some suggestions to resolve this conflict?
> [1] https://review.openstack.org/#/c/462334/
> [2] https://review.openstack.org/#/c/628915/
> Michael Johnson <johnsomor at gmail.com> 于2019年1月5日周六 上午8:02写道:
>> Hi Jeff,
>> Unfortunately the team that was working on that code had stopped due
>> to internal reasons.
>> I hope to make the reference active/active blueprint a priority again
>> during the Train cycle. Following that I may be able to look at the L3
>> distributor option, but I cannot commit to that at this time.
>> If you are interesting in picking up that work, please let me know and
>> we can sync up on that status of the WIP patches, etc.
>> Michael
>> On Thu, Jan 3, 2019 at 11:19 PM Jeff Yang <yjf1970231893 at gmail.com> wrote:
>> >
>> > Dear Octavia team:
>> >       The email aims to ask the development progress about l3-active-active blueprint. I
>> > noticed that the work in this area has been stagnant for eight months.
>> > https://review.openstack.org/#/q/l3-active-active
>> >       I want to know the community's next work plan in this regard.
>> > Thanks.

More information about the openstack-discuss mailing list