Open Stack

Excerpts from corvus's message of 2017-06-28 08:54:30 -0700:
> Monty Taylor <mordred at inaugust.com> writes:
> 
> > With that in mind, I believe the path should be for the new server
> > being written for the console-log streaming to be called "zuul-web"
> > and that it should serve the console-log websocket at /console-stream
> > or /console-log or something.
> >
> > We can then use our Apache frontend to serve /status from the
> > zuul-scheduler and /console-stream from zuul-web - and in the fullness
> > of time we can potentially move the webhooks and the status page from
> > the scheduler to zuul-web should we choose.
> >
> > Additionally, as we look at things like dashboards, they can go
> > directly into zuul-web and be written with aiohttp. As zuul-web is
> > stateless, it's a great candidate for a pure scaleout model.
> 
> I like this as a way forward.

Me too. It's easy to understand and I don't see any gotchas on first
glance.