Open Stack

Jeff,

Eventlet cannot be included in the main Octavia controller side code or
added to our main requirements.txt, but that technically doesn't apply to
the pre-built amphora images. They use a different requirements system and
since it won't actually be used by any of the real Octavia services (os-ken
is just some other software that will run independently inside the amphora,
right?) it should actually be fine. In fact, I would assume if it is a
requirement of os-ken, you wouldn't have to explicitly list it as a
requirement anywhere, as it should be pulled into the system by installing
that package. At least, that is my early morning take on this, as I haven't
really looked too closely at os-ken yet.

   --Adam Harwell (rm_work)

On Mon, Jan 7, 2019, 01:25 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.
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20190108/3800d430/attachment.html>