Re: [openstack-dev] [Heat] Multi-engine design feedback requested

2013-08-30 Thread Jason Dunsmore
Heat devs,

There's been some good discussion on the Etherpad:
https://etherpad.openstack.org/vJKcZcQOU9

I've added a "Votes" section under alternate options 1-5.  Please read
over the discussion and add your vote.

Thanks,
Jason


On Thu, Aug 29 2013, Jason Dunsmore wrote:

> Heat devs,
>
> Liang pointed out a race-condition in the current multi-engine
> implementation that will be difficult to fix without a DB lock.  I've
> discussed the multi-engine design with my teammates and written up a few
> alternative designs here:
> https://etherpad.openstack.org/vJKcZcQOU9
>
> Every design has its own downsides, so I was hoping to get some feedback
> from the core devs as to which one is preferable.
>
> Feel free to add comments in-line.  Please don't click "Clear Authorship
> Colors" ;)
>
> Thanks,
> Jason
>
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


[openstack-dev] [Heat] Multi-engine design feedback requested

2013-08-29 Thread Jason Dunsmore
Heat devs,

Liang pointed out a race-condition in the current multi-engine
implementation that will be difficult to fix without a DB lock.  I've
discussed the multi-engine design with my teammates and written up a few
alternative designs here:
https://etherpad.openstack.org/vJKcZcQOU9

Every design has its own downsides, so I was hoping to get some feedback
from the core devs as to which one is preferable.

Feel free to add comments in-line.  Please don't click "Clear Authorship
Colors" ;)

Thanks,
Jason

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev