Open Stack

Russell Bryant wrote:
> This service would act as a proxy for nova-compute in a couple of ways.
> 
> 1) The nova-compute service would use it as a proxy to accomplish
> certain tasks, such as targeted operations that need database access.
> 
> 2) Over time, it would be used as a proxy for other services that wish
> to execute some sort of compute action.  For example, instead of
> directly asking nova-compute to complete a long running operation, the
> nova-compute-proxy would take this operation and monitor its progress.

I'm not convinced nova-compute-proxy is the best name for this. It's a
bit of a mouthful and IMHO proxying has a "one-way" meaning into it...
If the proxying was only in one direction (compute -> db) that would
make perfect sense but if you add other more complex abstractions (like
nodes -> compute), I think "proxy" is a bit reductive. nova-controller ?

Otherwise my main gripe with it would be that this new service would be
compute-node-oriented, whereas the "nova-sink" approach was a bit more
generic (could one day be called by other nodes to access DB). But I
suspect you had the choice between the two approaches covered in the
summit session I missed :)

-- 
Thierry Carrez (ttx)
Release Manager, OpenStack