Open Stack

On 08/14/2016 06:23 PM, Patrick East wrote:
<snip>
> I like the sound of a more unified way to interact with compute node
> services. Having a standardized approach for inter-service
> synchronization for controlling system resources would be sweet (even if
> it is just a more sane way of using local file locks). Anyone know if
> there is existing work in this area we can build off of? Or is the path
> forward a new cross-project spec to try and lock down some requirements,
> use-cases, etc.?
> 
> As far as spending time to hack together solutions via the config
> settings for this.. we'll its pretty minimal wrt size of effort compared
> to solving the large issue. Don't get me wrong though, I'm a fan of
> doing both in parallel. Even if we have resources jump on board
> immediately I'm not convinced we have a great chance to "fix" this for N
> in a more elegant fashion, much less any of the older releases affected
> by this. That leads me to believe we still need the shared config
> setting for at least a little while in Devstack, and documentation for
> existing deployments or ones going up with N.

So I think this breaks down into:

1) What are the exactly calls in os-brick that need this? What goes
wrong if they don't have it?

2) How do we communicate the need in a way that won't be missed by folks?

3) What is the least worst solution to this for Newton?

4) How do we make sure we don't do this again in future releases?

5) What is the more ideal long term solution here?

	-Sean

-- 
Sean Dague
http://dague.net