Open Stack

Excerpts from corvus's message of 2017-06-09 13:11:00 -0700:
> Clark Boylan <cboylan at sapwetik.org> writes:
> 
> > I'm wary of this simply because it looks a lot like repeating
> > OpenStack's (now failed) decision to stick web servers in a bunch of
> > python processes then do cooperative multithreading with them along with
> > all your application logic. It just gets complicated. I also think this
> > underestimates the value of using tools people are familiar with (wsgi
> > and flask) particularly if making it easy to jump in and building
> > community is a goal.
> 
> I agree that mixing an asyncio based httpserver with application logic
> using cooperative multithreading is not a good idea.  Happily that is
> not the proposal.  The proposal is that the webserver be a separate
> process from the rest of Zuul, it would be an independently scaleable
> component, and *only* the webserver would use asyncio.
> 

I'm not totally convinced that having an HTTP service in the scheduler
that gets proxied to when appropriate is the worst idea in the short term,
since we already have one and it already works reasonably well with paste,
we just want to get rid of paste faster than we can refactor it out by
making a ZK backend.

Even if we remove paste and create a web tier aiohttp thing, we end up
writing most of what would be complex about doing it in-process in the
scheduler. So, to tack gearman on top of that, versus just letting the
reverse proxy do its job, seems like extra work.