On Mon, 2023-02-27 at 07:23 -0800, Jay Faulkner wrote:
> I've worked at a handful of places running OpenStack at large scale in
> production. In many of those cases, we used the built-in service runner
> (eventlet WSGI in at least some cases) and put an HTTP{s} proxy in front.
>
> I agree we should probably consider more commonly used-in-production
> options; but we shouldn't throw out the existing eventlet wsgi server
> support without explicit technical reasons. Why do you think it's not a
> serious option?
kolla used to default to useing the eventlet services untill a few release ago (victoria).
so its a preferctly reasonable thing to do.

with that said i belvie some service removed the console entry point for using eventlet
(keystone removed it in newton https://github.com/openstack/keystone/tree/mitaka-eol/keystone/server)
and some never supported that configuration (placement started as a generic wsgi app). 
there was a move away form supporting and shiping eventlet console script it over the years.

nova still provides one but its mostly deprecated at this point although i dong think it is offically.

we do not test it anymore and have not for several years at this point.

i think devstack can technially still deployit with nova-api but its been at least 3 or 4 years since that was
used in ci.

again kolla did use it for production usage as recently as victoria and in principal nova-api console script
is fit for production use but i am not aware of anyoen deploying it that way since kolla changed to using apache.


>
> Thanks,
> Jay Faulkner
> Ironic PTL
> TC Member
>
> On Mon, Feb 27, 2023 at 6:49 AM Thomas Goirand <thomas@goirand.fr> wrote:
>
> > On 2/21/23 19:34, Sean Mooney wrote:
> > > just using the eventlet webserver
> >
> > This isn't a serious option... :/
> >
> > Cheers,
> >
> > Thomas Goirand (zigo)
> >
> >
> >